How to setup Weld Listener (in Jetty) to reuse existing Bean Manager?

[tomdush]

Hello,

I'm writing a standalone Java application which use Jetty to start web application.

In web.xml, I have :

<listener>
  <listener-class>org.jboss.weld.environment.servlet.BeanManagerResourceBindingListener</listener-class>
</listener>
<listener>
  <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>
</listener>

But, the second listener (org.jboss.weld.environment.servlet.Listener) don't use Bean Manager which is created in main method. It create a second Bean Manager !

Thus, my beans "ApplicationScopped" are instantiate twice...

Do you have any suggestion to have only one application context ?

Thanks,

TD

[mkouba]

Hi Tom,

I don't think it's possible. If you start Weld using SE extension (http://docs.jboss.org/weld/reference/latest/en-US/html/environments.html#d0e5495) and run embedded Jetty and deploy a different web application (with Weld servlet extension) then these are logically two different/isolated apps (even though they run on the same JVM). I'm not sure how embedded Jetty classloading works but I wouldn't experiment with this. Do you need CDI services in your standalone app at all? And what is the motivation for having a shared app context?

[tomdush]

Thanks,

My application is "modular". Embedded Jetty is created by a module which is instantiated and configured by CDI.

Another module create RMI interface. Events coming from this module must be propagated to WebApp module and vice versa.

But maybe this module can be created by Weld servlet extension (from 1st module)...