Using just Tomcat as the servlet container.
Having one webapp be the "services" webapp, which has the Avalon Container and a bunch of components. This webapp owns the service manager, and makes it available to all webapps by placing it into the JNDI that Tomcat provides in some way.
Other webapps would have the Avalon Framework, and code to retrieve the service manager by name from Tomcat's JNDI, and then can use it to find services to call (which are running in that other webapp).
I'm still fuzzy on JNDI and what Tomcat provides... has anyone does this with Tomcat? What's needed to get that service manager into the JNDI space? Tomcat's context seems to be read only once the webapp starts going...
Just where in the JNDI name space would this go? Do we have a standard in the Avalon Framework?
Can the service manager be bound in from within a running webapp (in a servlet's init code, for example)? How does that work?
A working example of using JNDI to bind an Avalon container's service manager from one webapp and use it elsewhere would help me. Anybody got one?
Thanks.
- Glenn
On Sunday, September 28, 2003, at 09:39 AM, Leo Sutic wrote:
Two cases:
1. You want to have a service manager within one servlet.
2. You want to share a service manager among servlets.
Case 1: Have one big servlet that has the service manager.
Case 2: Using JBoss, I either:
a) Bind the configuration for a service manager as a Serializable object in the JNDI tree
or
b) Bind the service manager itself as a non-serializable object in the JNDI tree.
(a) requres that *something* creates the configuration objects and (b)
still
requires that *something* creates the service manager instance. I use an
MBean for that.
/LS
-----Original Message----- From: Glenn R. Golden [mailto:[EMAIL PROTECTED] Sent: den 26 september 2003 19:39 To: Avalon framework users Subject: Re: Framework / non-Framework question
I'm not very familiar with this - can you tell me more, specifically, how you use JNDI to find Avalon service manager or components?
Thanks.
- Glenn
On Friday, September 26, 2003, at 12:59 PM, Leo Sutic wrote:
---------------------------------------------------------------------From: Glenn R. Golden [mailto:[EMAIL PROTECTED]
But I wonder if this has already been addressed by the Avalon community, and if so, if there's a more elegant solution.
I use JNDI for that purpose.
/LS
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
