[
https://issues.jboss.org/browse/WFLY-1277?page=com.atlassian.jira.plugin....
]
Thomas Diesler updated WFLY-1277:
---------------------------------
Description:
We currently support single XML file deployments with a name pattern like this
{code}
*-context.xml
{code}
or contained in other deployment types like this
{code}
META-INF/*-context.xml
{code}
Existing user deployments of either form would be treated as spring camel context
deployments, which they are probably not.
A single XML file deployment is perhaps also questionable because it can only reference
camel components, processors, beans, etc. that are already registered in the system.
A safer option would be to only process deployment of type
{code}
*-camel-context.xml
META-INF/jboss-camel-context.xml
{code}
was:
We currently support camel system context definitions like this
{code}
<subsystem xmlns="urn:jboss:domain:camel:1.0">
<camelContext id="system-context-1">
<![CDATA[
<route>
<from uri="direct:start"/>
<transform>
<simple>Hello #{body}</simple>
</transform>
</route>
]]>
</camelContext>
</subsystem>
{code}
Define Camel context definition format for deployments
-------------------------------------------------------
Key: WFLY-1277
URL:
https://issues.jboss.org/browse/WFLY-1277
Project: WildFly
Issue Type: Task
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Labels: camel
We currently support single XML file deployments with a name pattern like this
{code}
*-context.xml
{code}
or contained in other deployment types like this
{code}
META-INF/*-context.xml
{code}
Existing user deployments of either form would be treated as spring camel context
deployments, which they are probably not.
A single XML file deployment is perhaps also questionable because it can only reference
camel components, processors, beans, etc. that are already registered in the system.
A safer option would be to only process deployment of type
{code}
*-camel-context.xml
META-INF/jboss-camel-context.xml
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira