Making camel deployment config part of jboss-all.xml

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Making camel deployment config part of jboss-all.xml

Thomas Diesler-2
Hi Jason,

it has been suggested to make camel specific deployment config (processed by the camel subsystem) part of jboss-all.xml. Would that be acceptable?


cheers
—thomas

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Making camel deployment config part of jboss-all.xml

Stuart Douglas

jboss-all.xml is pluggable, any subsystem can hook into it. It delegates to the appropriate parser based on the namespace, the same way standalone.XML does.

Stuart


On Tue, 24 Feb 2015 10:29 pm Thomas Diesler <[hidden email]> wrote:
Hi Jason,

it has been suggested to make camel specific deployment config (processed by the camel subsystem) part of jboss-all.xml. Would that be acceptable?


cheers
—thomas
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Making camel deployment config part of jboss-all.xml

Thomas Diesler-2
Ok, thanks. Should we still support a standalone descriptor (i.e. jboss-camel.xml) or is it sufficient to go with jboss-all.xml?

—thomas

On 24 Feb 2015, at 16:36, Stuart Douglas <[hidden email]> wrote:

jboss-all.xml is pluggable, any subsystem can hook into it. It delegates to the appropriate parser based on the namespace, the same way standalone.XML does.

Stuart


On Tue, 24 Feb 2015 10:29 pm Thomas Diesler <[hidden email]> wrote:
Hi Jason,

it has been suggested to make camel specific deployment config (processed by the camel subsystem) part of jboss-all.xml. Would that be acceptable?


cheers
—thomas
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev