WELD 2.2.5.Final broke deploy and arquillian test

[wangliyu]

Hi,

one change in the WELD 2.2.5.Final was to change default isolation from false to true, so certain application or arquillian tests will break.

For example, my application has war file, it include a lot module jar file, only one jar has interceptor/producers, the rest can use it with WELD 2.2.4.Final, but with WELD 2.2.5.Final, it failed to run (can't find the interceptors), unless I add @Priority or turn on

<context-param>

  <param-name>org.jboss.weld.environment.servlet.archive.isolation</param-name>

  <param-value>false</param-value>

  </context-param>

And in the arquillian test, I created war archive, it included the jars and also the test classes, if I don't turn on the context param, it will fail deployment, and can't find the producer method as well.

Why need to change the default setting? can we change it back in the future release?

Thanks

[mkouba]

Hi,

this is intentional and will not change back. At last Weld servlet container integration follows the spec. See also my blog post - Weld 2.2.5 - servlet container integration done correctly, and Weld documentation - Bean Archive Isolation.

[wangliyu]

The behavior changes caused the @Alternative broke, I have a jar that contain the @Producer methods, and in arquillian test, I have to use @Alternative to provide different implementation, the @Alternative sit in different jar, then when I run the arquillian test, it broken, basiclly the @Alternative is never alternative, it still try to use the original @Producer methods. is there any work around of that other than flat deployment?

[wangliyu]

Never mind, I figured, so I have to @Priority to @Alternative, @Interceptor to enable the global.