Joerg! we implemented a similar system to bind to our EJBs. it makes me wonder whether this kind of system should be present in the standard cocoon package. i'd really like to see a a selector which can also generate sax events, so you can trigger a sequence of backend actions which give output. in our system, the output gets collected into a hashmap which a custom generator transforms into sax events.
> -----Original Message----- > From: Joerg Heinicke [mailto:[EMAIL PROTECTED] > Sent: Sunday, September 21, 2003 6:29 PM > To: [EMAIL PROTECTED] > Subject: Re: EJB + Cocoon, "Best Practices" > > > We used EJB + Cocoon 2.0.4 for our project ConWeb. We have an > EJBConnectorAction that handles the authorization and calls a > WorkFlowBean with the request information. This one is > calling actions > doing the business logic. It returns the workflow information in a > HashMap, the sitemap decides on this information which > generator to call > (e.g. simple XML or FilterGenerator). The FilterGenerator knows the > components to call in the backend, especially a prepared > FilterDocument. > The FilterGenerator gets the SAX events directly from the backend > without any XML binding. The advantage is the cacheability of the > FilterDocuments. They can be reused on the next request (the > caching is > only not implemented in the generator until now). The architecture is > highly pluggable. > > Joerg > > Bastian Breithaupt wrote: > > > 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 > > > --------------------------------------------------------------------- > 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]
