On Thu, 8 Apr 1999, Anthony Eden wrote:
> Has anyone come across a situation where an EJB could also be a JavaBean. By
> this, I am suggesting that the JavaBean can be customized in a JavaBeans
> compliant builder and then be distributed to an EJB compliant container and
> executed as an EJB?
>
> Is this totally out there? Are there unresolvable conflicts between the two
> design patterns? Have I forgotten my medicine?
>
> Thanks for your thoughts.
Interesting question. Off the top of my head, I don't see any reason why
this couldn't be done:
- the requirements for a Java class to be a bean are pretty
minimal
- the java.beans classes and the javax.ejb classes are pretty
orthogonal
Admittedly, I haven't done much with "plain old" JavaBeans in quite some
time, so there might be some problem that I'm not seeing.
I'm not sure how distribution would work; IIRC "plain old" Beans are
JARred as serialized class instances, whereas EJBs are JARred as
serialized deployment descriptors. If there's a way around this, it should
work OK -- Customizers and the like should just be ignored by the EJB
deployment process, and the EJB stuff should be ignored by the JavaBean
environment.
Has anyone tried this yet?
===========================================================================
Tom Valesky -- [EMAIL PROTECTED]
http://www.patriot.net/users/tvalesky
===========================================================================
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".
