[wildfly-dev] Making camel deployment config part of jboss-all.xml

[Thomas Diesler]

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 <stuart.w.douglas at gmail.com> 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 <tdiesler at redhat.com <mailto:tdiesler at redhat.com>> 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?
> 
> Relates to: https://github.com/wildfly-extras/wildfly-camel/issues/199 <https://github.com/wildfly-extras/wildfly-camel/issues/199>
> 
> cheers
> —thomas
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/wildfly-dev <https://lists.jboss.org/mailman/listinfo/wildfly-dev>_______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20150225/924a06f8/attachment.html