> -----Original Message-----
> From: Geoff Howard [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 14, 2002 4:57 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: sexy open source
> So far, every time I hear someone talk about using EJB's and
> cocoon, the
> topic gets bundled with deploying cocoon in the appserver
> itself, which pegs
> you to one front end machine and causes all of your display
> logic (cocoon)
> to run on the same disks and cpus as your ejb logic. Is no
> one using EJB's
> on a remote (conceptually remote, even if it's on the same
> machine for now)
> server from within cocoon?
tell me what makes cocoon different from any other client EJB app? I just don't see the difference. if you may call EJBs from remote Java clients, what would prevent you from doing it from Cocoon's components?
only thing you need is the proper classpath, with all those client .jar (necessary to obtain JNDI contexts) and remote/home interfaces from the tree.
