hi rick,
: I am considering using Castor with JBoss and am trying to work out the
most
: appropriate architecture for my application. I'm also using Tomcat for a
: servlet front end for this app, with Struts MVC architecture and custom
JSP
: tags.
you should try webwork (www.sourceforge.net/projects/webwork) as an
alternative if you haven't done so yet - I found it as the cleanest solution
to MVC-for-the-web today.
: In addition, I'm looking at using EJBDoclet, which I've found does a
: very nice job of generating the EJB classes & interfaces.
yep, and you can also generate the dataholder classes automatically, which
you can directly reuse in the webwork frontend.
: 1. I would like to use Castor to manage persistence of EJB BMP entity
: beans, given JAWS' inability at the moment to support dependent objects.
An
yep, this is a real problem until ejb2.0.
one thought I had recently was automatic generation of session beans with
finder-like methods using doclet approach, that would return collections of
the dataholders automatically (using jdbc). this would solve 1->n
relationships problem in data structures. corresponding CMP entities could
provide the creation, updating, deletion of such records. this would not
provide a *real* automatic persistence, and probably would not be portable,
but would suffice for most routine find'n'display tasks.
: 2. I would like to avoid duplicating data objects as much as possible. One
: thing that I've noticed with the whole J2EE architecture is that there is
a
: lot of opportunity to duplicate objects that do roughly, or exactly, the
: same thing.
using webworks+ejbdoclet, there is minimal duplication of behavior, see
above.
regards,
--andrius
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
