<p dir="ltr">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.</p>
<p dir="ltr">Stuart<br>
</p>
<br><div class="gmail_quote">On Tue, 24 Feb 2015 10:29 pm Thomas Diesler <<a href="mailto:tdiesler@redhat.com">tdiesler@redhat.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi Jason,<div><br></div><div>it has been suggested to make camel specific deployment config (processed by the camel subsystem) part of jboss-all.xml. Would that be acceptable?</div><div><br></div><div>Relates to: <a href="https://github.com/wildfly-extras/wildfly-camel/issues/199" target="_blank">https://github.com/wildfly-extras/wildfly-camel/issues/199</a></div><div><br></div><div>cheers</div><div>—thomas</div></div>______________________________<u></u>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/<u></u>mailman/listinfo/wildfly-dev</a></blockquote></div>