Ah yes, turns out that I can't enable interceptors if the JARs are not read
by Weld, which I can't do because of classloading isolation.
I tried to explicitly add the interceptors but failed to do so, therefore I
closed the issue and introduced another Furnace implementation - still in
Alpha stage  which runs on a single Weld instance and works as expected.
Em 25 de jul de 2017 05:42, "Martin Kouba" <mkouba(a)redhat.com> escreveu:
Ok, so when looking at FURNACE-145 and FURNACE-32 the problem seems to be
related to how Forge addons are isolated, right?
Dne 18.7.2017 v 17:48 George Gastaldi napsal(a):
Yes, please find attached a ZIP containing two addons.
To reproduce it, follow the steps:
1) Unzip the attached file (say in /tmp)
2) Start Forge
3) Run addon-build-and-install --project-root /tmp/infinispan
4) Run addon-build-and-install --project-root /tmp/foo
5) Stop Forge and start it again
6) In another bash window, run tail -f ~/.forge/log/forge.log and you
should see the Weld output.
7) If no errors are found, running the command "x" should print something
@Matej, same error using @Priority :(
I am still investigating
Principal Software Engineer
Red Hat <https://www.redhat.com>
Joinville - Santa Catarina
ggastald(a)redhat.com <mailto:email@example.com> M: +55-47-99711-1000
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
Red Hat <
Red Hat <
On Tue, Jul 18, 2017 at 10:12 AM, Antoine Sabot-Durand <asd(a)redhat.com
Can you send us some code that we can easily run to reproduce your
On Tue, Jul 18, 2017 at 9:50 AM Matej Novotny <manovotn(a)redhat.com
Forge addons are far from my range of expertise so I am just
going to shoot in the dark here :)
Make sure you have beans.xml (with discovery mode all and
enabled interceptor) in both JARS - the one which contains the
interceptor, as well as the one trying to use it.
If that doesn't work, try to tackle the interceptor a bit and
use @Priority as a means of enablement (this enables interceptor
globally as opposed to beans.xml which does that on
Might not be what you seek but might also give us some
additional information on whats going wrong.
----- Original Message -----
> From: "George Gastaldi" <ggastald(a)redhat.com
> To: "Weld" <weld-dev(a)lists.jboss.org
> Sent: Tuesday, July 18, 2017 1:37:15 AM
> Subject: [weld-dev] WELD-001417 while enabling interceptors
in JBoss Forge addons
> Hello Welders !
> Not sure if this is the right mailing list, but worth a shot ;)
> I am trying to enable a CDI interceptor inside JBoss Forge
addons but I am
> facing a hard time making Weld understand that. The
interceptor classes are
> in the classpath but I keep getting this error:
> WELD-001417: Enabled interceptor class
> does not match an interceptor bean: the class is not found,
or not annotated
> with @Interceptor and still not registered through a portable
> not annotated with @Dependent inside an implicit bean archive
> I have beans.xml with annotated-mode="all". I even added the
> the interceptor class, but no luck. The current thread
> resolve the interceptor class also.
> I've opened https://issues.jboss.org/browse/FURNACE-145
> on the subject, in case someone feels brave enough to help me
out on this
> I appreciate any help!
> Best Regards,
> George Gastaldi
> Principal Software Engineer
> Red Hat
> Joinville - Santa Catarina
> ggastald(a)redhat.com <mailto:firstname.lastname@example.org> M:
> TRIED. TESTED. TRUSTED.
> @redhatnews Red Hat Red Hat
> weld-dev mailing list
> weld-dev(a)lists.jboss.org <mailto:email@example.com>
weld-dev mailing list
weld-dev mailing list