Thank you for your mail. Avaleo office is closed from December 23 to January 2 were we will address you request. If you have urgent requests it's possible to call the following persons: - From December 23th to December 27th (both days included) please call Niels Dyrnesli on +45 40741496. - From December 28th to January 1 (both days included) please call Anders Kofoed +4529442941 Kind regards Anders Kofoed Avaleo ApS
-----Original Message----- Reply-To: "Jakarta Commons Users List" <[email protected]> From: "Anders Kofoed" <[EMAIL PROTECTED]> To: "Jakarta Commons Users List" <[email protected]> X-FuseMail-Forward: 1 Subject: Out Of Office until 2nd January 2007 Date: Tue, 26 Dec 2006 14:40:47 -0600 > Thank you for your mail. > > Avaleo office is closed from December 23 to January 2 were we will address > you request. > If you have urgent requests it's possible to call the following persons: > > - From December 23th to December 27th (both days included) please call Niels > Dyrnesli on +45 40741496. > - From December 28th to January 1 (both days included) please call Anders > Kofoed +4529442941 > > Kind regards > Anders Kofoed > Avaleo ApS > -----Original Message----- > Reply-To: "Jakarta Commons Users List" <[email protected]> > Date: Tue, 26 Dec 2006 15:40:14 -0500 > From: "Rahul Akolkar" <[EMAIL PROTECTED]> > To: "Jakarta Commons Users List" <[email protected]> > Subject: Re: [Chain]: Frameworks and Products using chain api > > On 12/20/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: > > > On 12/20/06, Virender Singh <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi, > > > > > > > > I am analysing commons-chain for use in our framework. Are there any > > > > frameworks/products that are using commons-chain api? I have heard of > > > > struts-chain. I do not have any idea as to how much is it in use? The > > > > list > > > > of products would help in convincing the team to use the api and that it > > > > is > > > > not another framework on which some work was done and then left in > > > > oblivion. > > > > > <snip-struts-and-shale-usecases/> > > > > > > Chain fits best in a scenario where there is a detailed straight line > > > flow, > > > and you can define your tasks in finely grained reusable pieces > > > ("Commands" > > > in the Chain vocabulary) that can be assembled into customized sequences > > > for > > > each task. Chain fits worst when you are trying to use it as a control > > > architecture for a workflow with lots of conditional branches. For that > > > case, you might look at a state machine architecture like the one > > > supported > > > by Commons SCXML[2] instead. > > > > > <snap/> > > And there are scenarios where leveraging both libraries ( [chain] and > > [scxml] ) makes sense (typically by calling a command chain from > > executable content within a SCXML document). Here [i] is a related > > post from the archives. > > -Rahul > > [i] > > http://marc.theaimsgroup.com/?l=jakarta-commons-user&m=114375623812367&w=2 > > > Craig > > > > > > [1] http://shale.apache.org/ > > > [2] http://jakarta.apache.org/commons/scxml/ > > > > > > > > > Thanks, > > > > Virender > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
