Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 76087 invoked from network); 9 Sep 2003 20:22:09 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 9 Sep 2003 20:22:09 -0000 Received: (qmail 40634 invoked by uid 500); 9 Sep 2003 20:21:25 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 40613 invoked by uid 500); 9 Sep 2003 20:21:25 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 40571 invoked from network); 9 Sep 2003 20:21:24 -0000 Received: from unknown (HELO MAIL.myadguys.com) (209.10.249.135) by daedalus.apache.org with SMTP; 9 Sep 2003 20:21:24 -0000 Received: by mail.myadguys.com with Internet Mail Service (5.5.2656.59) id ; Tue, 9 Sep 2003 16:21:28 -0400 Message-ID: From: Tim Olson To: "'users@cocoon.apache.org'" Subject: RE: EJB + Cocoon, "Best Practices" Date: Tue, 9 Sep 2003 16:21:26 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N to get EJBs into cocoon, we have a custom Action / Generator pair. the action can be configured to make any EJB call (uses reflection) and stuff the results into a HashMap. the custom generator then sends that hashmap through Castor to generate SAX events. it's very nice, since we can turn any series of ejb calls into XML data with just a few lines of sitemap code. note: remote interfaces are tricky to castorize so use the value object (aka data transfer object) pattern. we eschewed flow scripts and wrote our own action engine, but i should post separately about that. > -----Original Message----- > From: Bastian Breithaupt [mailto:bastian_b@web.de] > Sent: Monday, September 08, 2003 5:33 PM > To: users@cocoon.apache.org > 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: users-unsubscribe@cocoon.apache.org > For additional commands, e-mail: users-help@cocoon.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org