Jim,
> As far as the OO arguments earlier, I have another point. I
> have a rich OO model
> and I use entity beans. The way to achieve this is to keep
> your OO in Value
> Objects. Entity Beans encapsulate these value objects,
> persist them and still
> benefit from the business logic.
I think I have a similar solution:
- UI via servlet that calls session bean
- session bean calls business logic layer (plain java classes)
- session bean calls persistence layer. I'm still investigating what
technology I will use for persistence: could be CMP, BMP, DAO, JDO, castor,
toplink, Cocobase....
So if I try to understand your architecture: compared to mine, if you would
put your business logic in your value objects those value objects become
what I call the business layer? What do your value objects look like? Could
you maybe post some code snippet of an entity bean that illustrates the
idea?
geert
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
