Hey
Jorgen Thelin wrote:
> Or perhaps better still would be a standard way to start / run some sort
> of mini "servlet processes" within the same JVM as the EJB container.
> Basically like Rickard's XS eXtensible Server framework ideas, but with
> standardized hooks to plug things together in other servers too.
That's my que I guess :-)
Yes, something like that would be very nice. Since EJB is only a 90%
solution some way to plugin those last 10% would be a good thing.
I have been thinking about the following workaround:
Bind a Reference to a JNDI name. When looked up the ObjectFactory in the
Reference could create a RMI-object and set a static variable in the RMI
class to this instance. Whenever that ObjectFactory is called again it
would return the statically bound instance instead of creating a new
one.
Rather ad hoc, but could work in many cases.
This however has some drawbacks:
* Reliance on the JNDI impl. to live in a JVM
* I don't think this'll work with clustering, as one would mostly need a
singleton/cluster
* Need some way to set the Reference up automatically. Not possible with
todays J2EE application structure.
/Rickard
--
Rickard �berg
@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".
