Rickard �berg wrote:
> Alternatives to implement application wide settings include using
> Properties/ResourceBundles in the ejb-jar, or serializing a
> configuration object into the jar and using Beans.instantiate() to
> retrieve it.
Or creating a SessionBean that is accessed by other beans to get the
application properties, e.g.
class MyApplicationBean implements SessionBean
{
public java.util.Properties getProperties()
{
// get properties from 'this' bean's environment.
}
... other methods from SessionBean
}
Now the deployer just has to set environment properties on the
MyApplicationBean, to which all other beans in the same application
come to get their configuration.
===========================================================================
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".
