[jboss-jira] [JBoss JIRA] (WFLY-4009) Cannot externalise camel-cdi & deltaspike

[Thomas Diesler (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014476#comment-13014476 ] 

Thomas Diesler edited comment on WFLY-4009 at 10/23/14 2:14 AM:
----------------------------------------------------------------

Weld seems to call CamelExtension.startConsumeBeans(...) before Bean CamelContextMap is initialised.

To reproduce

{code}
git clone -b issue#15 https://github.com/tdiesler/wildfly-camel.git
cd wildfly-camel; mvn clean install -DskipTests
cd itests/target/wildfly-8.1.0.Final; bin/standalone.sh -c standalone-camel.xml
{code}



was (Author: thomas.diesler):
To reproduce

{code}
git clone -b issue#15 https://github.com/tdiesler/wildfly-camel.git
cd wildfly-camel; mvn clean install -DskipTests
cd itests/target/wildfly-8.1.0.Final; bin/standalone.sh -c standalone-camel.xml
{code}


> Cannot externalise camel-cdi & deltaspike
> -----------------------------------------
>
>                 Key: WFLY-4009
>                 URL: https://issues.jboss.org/browse/WFLY-4009
>             Project: WildFly
>          Issue Type: Bug
>          Components: CDI / Weld
>    Affects Versions: 8.1.0.Final
>            Reporter: Thomas Diesler
>            Assignee: Stuart Douglas
>
> Currently, there is a webapp deployed as part of the camel subsystem that contains
> * camel-cdi
> * deltaspike-core-api
> * deltaspike-core-impl
> * deltaspike-cdictrl-api
> Generally it seems that every webapp needs to package these in order for camel-cdi to work. We would however like to replace these embedded jars with references to the already existing modules.
> GitHub Issue: https://github.com/tdiesler/wildfly-camel/issues/15



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)