Couldn't application wide resources (perhaps including "environment
variables" be represented as objects stored in the JNDI namespace? that way
both EJB and client objects could retrieve them? JNDI seems to be a nice
solution for storing/searching etc for global objects?
Thus you would only need 1 entry in the DD which points the the jndi entry
that represents global objects etc?
Rob Masters
Comcare Australia
[EMAIL PROTECTED]
http://www.comcare.gov.au
> -----Original Message-----
> From: Rickard �berg [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, 19 May 1999 15:27
> To: [EMAIL PROTECTED]
> Subject: Re: Customization & Introspection
>
> Matthias David wrote:
> > What is your opinion on that? What about Entity Beans and customization?
> > And why is there no mechanism to introspect an Enterprise JavaBean like
> > the BeanInfo class on JavaBeans (javax.ejb.EJBMetaData is not the same
> > thing. You still need to do the "low-level" reflection on your own!) ?
> > Especially, I'm asking that, because customization & introspection is a
> > main topic when talking about component systems generally. But with EJB
> > this seems to be different.
>
> For customization you should use deployment descriptors, especially in
> EJB1.1 where the DD does alot of work for you in terms of hooking up
> needed resources in a very nice way. Useing JavaBeans Customization
> could work I guess but there are drawbacks. For example, using
> Customizers implies saving the state in a serialized form which then
> could be used by the container. If the bean is not carefully constructed
> a simple update to it makes the serialized form useless (due to
> different serialization Id's). Also, all containers wont have GUI's,
> especially embedded ones.
>
> No, I kinda like the XML descriptor way of doing customization. Only
> problem is that it doesn't allow application wide settings. If you have
> an environment variable that all beans in a jar needs to have then you
> must add it to all beans, which then becomes a maintenance problem
> (update needs changing in several places). This could be fixed if
> references and environment entries were allowed on both entity and
> global level though (i.e. "env-entry" should be a child of
> "enterprise-beans").
>
> /Rickard
>
> --
> Rickard �berg
>
> Computer Science student@LiTH
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> Homepage: http://www-und.ida.liu.se/~ricob684
>
> ==========================================================================
> =
> 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".
===========================================================================
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".
