Re: [seam-dev] [cdi-dev] Enabling extensions
Hi Pete,
From my experience this is a problem, especially for (partial)
integration
tests within a maven based build infrastructure. In the end we had to
move
certain META-INF/services/javax.enterprise.inject.spi.Extension files from
extension jars to the final deployment artifact or use System Properties
(!) to disable them;(.
Jens
On 12.09.11 16:51 "Pete Muir" <pmuir(a)redhat.com> wrote:
Seam team, and others on the CDI EG,
Looking for feedback on an issue Marius and I discussed in CDI 1.0. This
is potentially an issue - we weren't sure if people had seen it in the
real world, hopefully you may have seen feedback in the forums or at
conferences.
This relates closely to the interceptor/decorator/alternative enabling
discussion.
Typically an extension class is packaged in a jar, along with a
META-INF/services/javax.enterprise.inject.spi.Extension file which
enables it. However, this means that an application, or another
extension, has no way of disabling extensions.
Is this a problem, really? Or just theoretically.
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev