> -----Original Message-----
> From: Fajeau, Philippe [SMTP:[EMAIL PROTECTED]]
>
> Our application has a fairly complex Domain Object Model, and many
> classes.
> I can't imagine making all these classes EJB. That would be a huge
> overhead
> (code wise and at run-time), and would not make a lot of sense, since most
> of the classes do not need to be invoked remotely. However, many classes
> do
> have a need for persistency and/or transaction support (if not as an
> initiator, at least as a participant). Let's call BO (Business Objects)
> the
> objects that are not EJB but contain some business logic.
>
> I would like to get clarification on a few points:
>
> + Does anyboddy know of pointers on how to design a fairly complex object
> model with EJBs in a pragmatic fashion (i.e. having something that can be
> deployed at the end, addressing the different trade off that need to be
> made). Most of the litterature I have read just provide simplistic
> examples
> of how to make an EJB, and do not address the real design of a decent size
> distributed application.
>
>
[Chip Wilson]
I wrote an article published in the August '99 issue of Component Strategies
that addresses your questions in some detail. It's called "Application
Architectures with Enterprise JavaBeans", and should be on the newsstand
soon if not already. I have used the architecture recommended there in a
real world application with a very complex DOM and the project is being
successfully deployed.
===========================================================================
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".
