Hi,

So let's say I'm using Tomcat embedded and OWB.  I bootstrap OWB using its
normal function, and I have impl, web and resource on my classpath.  When I
ask for the ContainerLifecycle service, I get back a WebContainerLifecycle
since I have web on the classpath.  So I'm wondering, does it make sense to
create a fake servlet context in this scenario?  I believe if I do that,
OWB will treat these as two different contexts and as a result the
instances won't be shared.

I'm almost thinking this would require a new plugin in OWB that did a lot
of the same work, however it allows the sharing of the context.  Thoughts?

John

Reply via email to