<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 8, 2015 at 5:06 PM, Tristan Tarrant <span dir="ltr"><<a href="mailto:ttarrant@redhat.com" target="_blank">ttarrant@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":3s1" class="a3s" style="overflow:hidden">The child extension would be responsible for<br>
parsing/serializing its own section of the XML, service registration, etc.<br>
Is this planned ?</div></blockquote></div><br><br></div><div class="gmail_extra">Why plan something that is already doable :-)<br></div><div class="gmail_extra">Well in a way at least, code that handles certain sub resource can be be anywhere, even in external module/dependancy.<br></div><div class="gmail_extra">All infinispan subsystem would need to do is .registerChild(new CacheStoreResourceDefinitionDefinedInDifferentModule())<br></div><div class="gmail_extra">well at least as long as you use new parser constructs, this would be trivial.<br></div><div class="gmail_extra">otherwise extra wiring for parser would be needed.<br><br></div><div class="gmail_extra">We do have similar setup for including parts of threads subsystem in other subsystems.<br></div><div class="gmail_extra"><br>--<br></div><div class="gmail_extra">tomaz<br></div><div class="gmail_extra"><br><br></div></div>