On Tue, Feb 25, 2003 at 07:03:39PM -0800, Jason Carreira wrote: > > -----Original Message----- > > From: James Cook [mailto:[EMAIL PROTECTED] > > > > > > And eventually SLSB -> Action -> Web Tier? > > > > > > > > > > Well, one would hope not. Again, it's dependent on how you're > > > using you Actions. > > > > Gotcha, I just thought that was his intent because he said he > > wanted to > > wrapper his HTTP calls. > > > > I thought he just wanted to chain actions together to implement several > pieces of workflow as reusable command objects. > >
That's exactly his (my) point. :) You probably don't want to model your web-application 1:1 to method calls on the session facade - the web-tier might collect information to 'add a customer' and 'add attributes to customer' in one screen. In the ejb tier this is represented as two method calls on a SLSB. Let's say that there is a second screen where you can 'add attributes to an existing customer' - you'd want to use the same WW-action (AddCustomerAttribuesAction) in both screens. In the first screen you'd chain the actions (CreateCustomerAction -> AddCustomerAttributesAction), and in the second screen you'd just use the second action. In both screens you want all input to be committed in one transaction. I.e if you fail to 'add attributes to customer' you want the 'add a customer' to rollback as well. Pwew - a little wordy, but I think you get the idea :) As stated in an earlier post, we'll probably go with a UserTransaction in the web-tier any way :) //Anders -- |===================================| | Anders Engstr�m | | [EMAIL PROTECTED] | | http://www.gnejs.net | |===================================| |Your mind is like an umbrella. | |It doesn't work unless you open it.| | /Frank Zappa | |===================================|
pgp00000.pgp
Description: PGP signature
