> -----Original Message----- > From: Anders Engström [mailto:[EMAIL PROTECTED] > > > 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 :).
We've just gone through a big refactoring here to pull business logic out of EJBs and into POJOs that are called by EJBs because we have lots of little services that were all calling each other. With each EJB call you get context switching, transaction demarcation or at least checking for its existence, security checks, etc. So what we've done is to make the EJBs entry points only and have business logic in POJOs. > > > 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 See above. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
