> Is someone has already made a design with an appserver and a ODMS?
> In particular, have you use
> * Only Session bean,
> * Some Entity bean
> * what type of ODBMS ?
Yes, we're setting up such an architecture. We want to build collaborative
applications with complex business objects and constraints.
We are planning to use no entity beans and only stateless session beans.
Reasons:
* entity beans constrain us too much (for instance w.r.t. querying, db
clustering, indexing)
* relationships/inheritance is too difficult with entity beans
=> we prefer to use persistent objects as domain objects
* relative benefits w.r.t. OODB are minor (for instance no O/R mapping)
And yes, we do need to write a large amount of support software on top of
EJB before we can write applications (for instance business constraints,
client caching, ...).
I am happy to discuss this in more detail if people are interested.
regards,
Bert
PS: For products, we're considering Weblogic + ObjectStore/Javlin
===========================================================================
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".
