[weld-dev] CODI and JBoss AS 6 final: ProjectStageActivationExtension didn't implement the Extension interface
Dan Allen
dan.j.allen at gmail.com
Fri Dec 31 12:39:53 EST 2010
It's more than likely geronimo-jcdi jar that's causing the problem. Weld
looks to see if Extension class equals Extension class and since there are
two independent instances on the classpath, it breaks the comparison. 9/10
this is the source of a class not found problem.
Java EE APIs should never be provided by an archive when deploying to a
compliant app server. If you were moving from Tomcat to JBoss AS it's
important to keep that in mind.
I doubt the apache-commons libraries would present a problem, so you can
likely leave those.
-Dan
On Fri, Dec 31, 2010 at 11:00 AM, Pete Muir <pmuir at redhat.com> wrote:
> Aha, as I thought you are bundling in the war all sorts of stuff which AS6
> provides (and doesn't support overriding simply by placing in the war).
>
> Try removing at least:
>
> * geronimo*
> * javassist
> * jsr250-api
> * myfaces-api
> * myfaces-impl
> * openwebbeans*
> * scannotation
>
> you may also need to remove commons-XXX which duplicate that in the AS
>
> HTH
>
>
> On 31 Dec 2010, at 15:42, Michael Schütz wrote:
>
> > Please see attached screenshot.
> >
> > Thanks
> > Michael
> >
> > 2010/12/31 Pete Muir <pmuir at redhat.com>
> > No idea.
> >
> > What jars are placed in WEB-INF/lib?
> >
> > On 31 Dec 2010, at 15:19, Michael Schütz wrote:
> >
> > > Thanks for reply, Pete.
> > >
> > > Already spoke to CODI team. They do implement Extension. Doesn't look
> like CODI bug for them.
> > >
> > > So, does this CDI POM config look strange:
> > > <!-- MyFaces CODI -->
> > > <dependency>
> > > <groupId>org.apache.myfaces.extensions.cdi.core</groupId>
> > > <artifactId>myfaces-extcdi-core-api</artifactId>
> > > <version>${myfaces_codi.version}</version>
> > > <scope>compile</scope>
> > > </dependency>
> > >
> > > <dependency>
> > > <groupId>org.apache.myfaces.extensions.cdi.core</groupId>
> > > <artifactId>myfaces-extcdi-core-impl</artifactId>
> > > <version>${myfaces_codi.version}</version>
> > > <scope>runtime</scope>
> > > </dependency>
> > > <dependency>
> > > <groupId>org.apache.myfaces.extensions.cdi.modules</groupId>
> > > <artifactId>myfaces-extcdi-jsf20-module-api</artifactId>
> > > <version>${myfaces_codi.version}</version>
> > > <scope>compile</scope>
> > > </dependency>
> > >
> > > <dependency>
> > > <groupId>org.apache.myfaces.extensions.cdi.modules</groupId>
> > > <artifactId>myfaces-extcdi-jsf20-module-impl</artifactId>
> > > <version>${myfaces_codi.version}</version>
> > > <scope>runtime</scope>
> > > </dependency>
> > >
> > >
> > > Cheers
> > > Michael
> > >
> > > 2010/12/31 Pete Muir <pmuir at redhat.com>
> > >
> > > On 31 Dec 2010, at 14:37, Michael Schütz wrote:
> > >
> > > > Hi to all,
> > > >
> > > > would like to run CODI/MyFaces example within JBoss AS 6 final.
> > > > Getting:
> > > > WeldBootstrapBean state=Create: java.lang.RuntimeException: Service
> class or
> > > >
> g.apache.myfaces.extensions.cdi.core.impl.projectstage.ProjectStageActivationExtension
> didn't implement the Extension interface
> > > >
> > > > at
> org.jboss.weld.util.ServiceLoader.loadClass(ServiceLoader.java:261)
> [:6.0.0.Final]
> > > >
> > > > at
> org.jboss.weld.util.ServiceLoader.loadService(ServiceLoader.java:233)
> [:6.0.0.Final]
> > > > at
> org.jboss.weld.util.ServiceLoader.loadServiceFile(ServiceLoader.java:194)
> [:6.0.0.Final]
> > > >
> > > > at
> org.jboss.weld.util.ServiceLoader.reload(ServiceLoader.java:157)
> [:6.0.0.Final]
> > > >
> > > > at
> org.jboss.weld.util.ServiceLoader.iterator(ServiceLoader.java:346)
> [:6.0.0.Final]
> > > > at
> org.jboss.weld.bootstrap.ExtensionBeanDeployer.addExtensions(ExtensionBeanDeployer.java:93)
> [:6.0.0.Final]
> > > >
> > > > at
> org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:333)
> [:6.0.0.Final]
> > > >
> > > > at
> org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.boot(BootstrapBean.java:92)
> [:6.0.0.Final]
> > > >
> > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) [:1.6.0_21]
> > > >
> > > > at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> [:1.6.0_21]
> > > > at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> [:1.6.0_21]
> > > >
> > > > Everything runs fine within Tomcat7.
> > > >
> > > > Already posted question at Weld forum without having much success:
> http://seamframework.org/Community/CODIAndJBossAS6FinalProjectStageActivationExtensionDidntImplementTheExtensionInterface
> > > >
> > > > What I would like to know:
> > > > 1) Is it not supposed to run?
> > >
> > > I would guess it is, but you should check with the CODI team.
> > >
> > > > 2) Is it project configuration issue?
> > >
> > > Possibly, it looks like it does really impl Extension so check you
> aren't bundling the CDI API in your war accidentally.
> > >
> > > > 3) Is it a bug? (JBoss, Weld? JIRA issue already filed)
> > >
> > > Probably not in JBoss or Weld.
> > >
> > > >
> > > >
> > > > thanks a lot
> > > > Michael
> > > > _______________________________________________
> > > > weld-dev mailing list
> > > > weld-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/weld-dev
> > >
> > >
> > > _______________________________________________
> > > weld-dev mailing list
> > > weld-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/weld-dev
> >
> >
> > <codi_webinf_lib.png>
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
>
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20101231/8a793d46/attachment.html
More information about the weld-dev
mailing list