cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ken Barozzi" <>
Subject Re: Cocoon and EJB
Date Thu, 07 Sep 2000 20:57:18 GMT
----- Original Message ----- 
From: "James Scott" <>

> Nicola Ken Barozzi wrote:
> > 
> > ----- Original Message -----
> > From: "James Scott" <>
> > > Hello all-
> > >
> > > I'm wondering if there's a better way to this and eliminate a layer of calls
> > > (right now I have at least 3: cocoon -> producer -> ejb -> possible
> > > classes).
> > 
> > IMO it's not an issue. If you look at a fairly _normal_ stacktrace, you can see
> > in any program something like 10-15 layers; AWT or Swing are _full_ of them.
> > Anyway Cocoon is a sort of Producer container, it instantiates the right elements
> > in the chain and lets them do the work.
> That's fair. I knew from the docs that XSP templates get compiled into producers
> so I didn't think they'd be any more efficient. I can see that they'll be easier
> to maintain and let me get out of some of the tedium of outputting XML.


> > EJB are, to put it maybe a little too simple, beans.
> > Well, XSPs are excellent for beans.
> > Are you sure you need then when the SQL taglib might be enough?
> I think EJBs are appropriate to this project because we're trying to construct
> reusable components.   Encapsulating the business logic in EJBs and using XSP to
> format the output will give us a great deal of reusability, I think. I'd rather
> consolidate the SQL in a handful of EJB source files than have it spread across
> many XSP files. EJBs will also allow easy access from non-browser clients.

Simple beans can do the trick also.
Remember that in some cases EJB can sloooow things down!
I know I'm repeating, but SQL incapsulation is done via beans,
E or not.
Look at the Sun J2EE site for a comparison.

Happy to help :-)


View raw message