On Tue, Feb 25, 2003 at 12:46:57PM -0800, Jason Carreira wrote: > > > > -----Original Message----- > > From: James Cook [mailto:[EMAIL PROTECTED] > > > > Sorry but this doesn't make much sense to me. When you say Actions, I > > guess you are not referring to WW actions. If you are, I > > think you may > > need to re-read some documentation. :-) > > I think his suggestion makes sense. It's a valid pattern, IMHO. > >
[snip] > 3. Pull the code out of your SLSBs into POJOs and create a new wrapper > SLSB which puts together these POJO calls in the correct order / > workflow and call that from your Action. > I assume your talking about something like a "Business Delegate" for WW-Actions? This actually a pretty good idea - although it would result in business components (SLSB's) that are dependent on the visual design of the web application (which might not be a bad thing depending on how you look at your application design :). > 4. Your idea of an Action Chain executor SLSB is also interesting, > although I hate to see it go SLSB -> Action -> SLSB > I don't see why slsb (WWActionExecutioner) -> action (ww) -> slsb (business facade) would be a bad thing. Care to elaborate? :) //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
