> -----Original Message----- > From: James Cook [mailto:[EMAIL PROTECTED] > > Maybe I'm missing it, but moving action execution to the > EJB-tier is a good idea why? Why not just code some POJO's to > perform the business logic on the EJB-tier. For more > complicated workflow, the workflow engines are specifically > designed to handle configuration-based execution paths.
It depends on how you're using Webwork and your Actions. If you're using Webwork as a generic command pattern implementation and not writing web-specific Actions, then this makes sense. If you're writing web-specific code, then this definitely doesn't make sense. > > > 4. Your idea of an Action Chain executor SLSB is also > > interesting, although I hate to see it go SLSB -> Action -> SLSB > > And eventually SLSB -> Action -> Web Tier? > Well, one would hope not. Again, it's dependent on how you're using you Actions. Jason ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
