Interceptor bindings on manually installed beans

[meetoblivion]

(This is for CDI 1.0/ Weld 1.1.10)

Hey, so I've run into an interesting issue (interesting in that our deployment structure is a little convoluted).

What we've essentially done is created some JBoss Modules that deploy as libraries, that our main app then loads via jboss-deployment-structure.xml and some CDI extensions.  IN the CDI extensions, we have lines like this:

void beforeBeans(@Observes final BeforeBeanDiscovery bbd, final BeanManager bm) {

    bbd.addAnnotatedType(bm.createAnnotatedType(FooManager.class));

}

On this FooManager, we have an interceptor binding, like this one:

@PrincipalHasRoles("foo_admin")

public FooResult updateFoo(final Foo foo) {

          ...

}

Which I would expect to get invoked using the interceptor, because the interceptor is listed in my beans.xml.  The interceptor does work when I annotated on my REST API (because the REST API lives in the war file, not in the library JARs).

So am I wrong in believing that this should work? Do I need to handle any other start up events in Weld to make the interceptor work in this library?

[jharting]

Which beans.xml? For this to work you would need to enable the interceptor in the same archive FooManager belongs to which may not be possible. This is much simpler with Weld 2.0

[meetoblivion]

Jozef,

It's in both beans.xml currently.  I also added the interceptor annotation on both the interface and implementation, no luck.  This is what my interceptor binding looks like:

@InterceptorBinding

@Target({ TYPE, METHOD })

@Retention(RUNTIME)

@Documented

public @interface PrincipalHasRoles {

    @Nonbinding

    String[] value() default {};

}

[jharting]

What version of JBoss AS is that? Since a certain version of JBoss AS a jboss module with beans.xml should be picked up as a bean archive, thus it would not be necessary to register FooManager programatically any longer and interceptor would work.

[meetoblivion]

I'm using JBoss 7.1.1

If this is something that may work fine in 7.2/EAP 6.1 I'm all eyes.

[jharting]

Yes I think EAP 6.1 will pick the jboss module with beans.xml as a bean archive. Therefore, you won't need to register FooManager via extension and therefore the interceptor enabled in beans.xml should be applied. Let me know if the assumption is correct.

[meetoblivion]

So, upgrading to EAP 6.1 didn't work.  Same result.

I may have described it a little off.  All of my modules are sitting in the deployments folder.  Is it possible to put my JARs into modules, even if they include things like JPA or EJBs?

[jharting]

Why do you register FooManager via an extension, then?

[meetoblivion]

Since it's cross different deployment modules, it's not considered part of the web archive's deployment module.  The work around includes listing the deployment in jboss-deployment-structure.xml and then using an extension to register it from one archive to another.

[meetoblivion]

Ok, I created a small module.  I put it into the modules directory and marked it as a dependency in jboss-deployment-structure.xml

I put a standard beans.xml in the archive.

I added a dep in my WAR file to this archive in the modules.

However, I ended up getting an unsatisfied dependency exception, so it looks this doesn't work as described.