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@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@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev