Paul wrote: ||| Ryan, ||| ||| ><snip/> ||| >Basically, I want to create a Server Application with just two blocks, ||| >MyBlock and Jo. MyBlock depends on Jo. MyBlock sets up a ComponentManager ||| >or ContainerManager and stores it in a JNDI tree, then calls the deployWar ||| >method of the Jo block. At Phoenix shutdown MyBlock calls undeployWar ||| >and then disposes the ComponentManager/ContainerManager. ||| > ||| This is interesting and should work as you want. You are talking of the ||| CM in the JNDI tree because you hope you can achieve it (communication) ||| without a socket connecton?
Yep. ||| Good lateral thinking to publish the CM. I guess it would work, but ||| publishing to JNDI is not so trivial. It is one of a few small things I ||| am stuck on with AltRMI. Yeah, I don't really know much about JNDI. What kinds of problems are you running into? ||| >Does this make sense? Thoughts? Better ideas? ||| > ||| I think it makes sense. We have some small issues with Jo and it's ||| parent classloaders for servlet (all jars in SAR-INF/libs are visible to ||| servlets), but you should be able to get your app working by careful ||| avoiding of duplicate jars in the war file. Okay, I'll keep that in mind. Thanks for the feedback! Ryan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
