unexpected ProcessAnnotatedType in Wildfly 8CR1

[matt.drees]

Hi Weld folks,

I'm trying to run one of my apps on Wildfly 8CR1 (currently it runs on jboss 7.1).  I ran into a problem that is related to different behavior in Weld 2.1.1.Final.

(For a little bit of background, see my post to reastesy-dev)

The root cause seems to be a ProcessAnnotatedType event being raised for a class that lives in a third-party library I use: http://grepcode.com/file/repo1.maven.org/maven2/net.derquinse/derquinse-common-jaxrs/1.0.34/net/derquinse/common/jaxrs/B…

This library's jar derquinse-common-jaxrs-1.0.34.jar has no beans.xml and has no scope-annotated class or session beans. If I'm reading the spec correctly, this means this jar is not a bean archive and none of its classes should trigger ProcessAnnotatedType events.  So I think weld is misbehaving.  Does that sound right to you?

Let me know if you'd like me to create a jira.

Thanks!

Matt Drees

[mkouba]

Hi Matt,

I believe this commit is causing the issue:

https://github.com/wildfly/wildfly/commit/49b6dfbcadfc8d0f9a47092834a57a65561b0993

This is what Bill meant with the sentence "We made a change in wildfly that all JAX-RS instances are managed by CDI because of managed beans and such".

So it's WildFly integration code which triggers Weld discovery. I'm not quite sure whether this complies with JAX-RS spec...

[jharting]

Yes, this is a WildFly integration problem. Please file a WildFly JIRA issue.

[matt.drees]

Thanks Martin & Jozef.  That makes sense.

Jira created here: [WFLY-2859] Treating all JAX-RS components as CDI Beans has some negative consequences - JBoss Issue Tracker