We are doing exactly that. Although our project is still in the very early stages, we have our EJBs returning Data Transfer Objects which are just Java Beans. We then wrote a BeanGenerator that calls a method on a service class that invokes the EJB and returns the DTO. It then passes the DTO to Betwixt which converts it to SAX events. I posted the BeanGenerator on the list a few days ago.
Ralph > -----Original Message----- > From: Bastian Breithaupt [mailto:[EMAIL PROTECTED] > Sent: Monday, September 08, 2003 2:33 PM > To: [EMAIL PROTECTED] > Subject: EJB + Cocoon, "Best Practices" > > > Hi! > > I would like to set up a Model2 application with Cocoon end > EJBs. Cocoon would be the presentation layer (also the > controller layer?) and the business logic would be > represented by the EJBs. (?) > > Are there any "Best Practices" for Cocoon working with EJBs? > (suggestions, links, publications, documentation, ...) > > I suppose, calling the EJB-API is done by Cocoon-Actions...? > (for example by using business delegation pattern) > > When using flow scripts, does it make sense to use actions? > (how mature is flow script?) > > Any help, hint, link, ... is appreciated. > > Thank you in advance, > > Bastian > ______________________________________________________________ > ________________ > 38xTestsieger - WEB.DE FreeMail - Deutschlands beste E-Mail > Jeden Monat mit 10% mehr Leistung! http://f.web.de/?mc=021138 > > > --------------------------------------------------------------------- > 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]
