Hi again, I think that there is a typo on the documentation. On the MyVirtualHostFactory example,
new MyVirtualHostDTO(broker, dto.id) should be new MyVirtualHost(broker, dto.id) Cheers, Pablo On Tue, Apr 24, 2012 at 10:03 AM, Pablo Guerrero <[email protected]> wrote: > Hi Hiram, > > Thanks for the update on the documentation, it clarifies some important > points. > > About extending the data model, I've been trying to extend the > CustomServiceDTO to provide configuration for our plugins, but I've > not been able to do it in a clean way. I can cast to Element, as > explained at the end, but I still get warnings, and the code it's not > really clean. > > I've tried also many variants of what is described in Extending the > Data Model, but now I can see that the extension of CustomServiceDTO > is not supported. Do you think it would be possible to add support for > extension to CustomServiceDTO too? In my opinion that would be much > cleaner than casting to Element. > > Thanks, > Pablo > > On Mon, Apr 23, 2012 at 6:10 PM, Hiram Chirino <[email protected]> wrote: >> In general the apollo extensions documentation [1] needs lots of love. >> I've just just updated it to list all the extension points which it >> supports. >> I've also added a section which explain how to extend the default virtual >> host implementation and how to hook into the configuration system. The doc >> updates should show up on the website in a couple of hours. >> >> Let me know if that's starting to help. We still need a sections similar to >> to the 'Using a custom VirtualHost implementation' section for each >> extensible part of Apollo. >> >> [1]: >> http://activemq.apache.org/apollo/versions/99-trunk-SNAPSHOT/website/documentation/extending-guide.html >> >> On Mon, Apr 23, 2012 at 2:11 AM, Lionel Cons <[email protected]> wrote: >> >>> I'm not familiar with the way Apollo plugins interact with apollo.xml. >>> >>> I have the feeling that we would need the following: >>> 1. define which parts of apollo.xml can be extended by plugins >>> 2. allow a given plugin to register the namespace it is using >>> 3. define namespace to XSD file/url mappings (inside plugin? outside?) >>> 4. assemble all this so that apollo.xml can be fully validated >>> 5. make sure all this works with multiple plugins loaded at the same time >>> >>> Maybe 1 and 3 should be discussed here? >>> >>> Once the picture is clear, we can log this in JIRA... >>> >>> Cheers, >>> >>> Lionel >>> >> >> >> >> -- >> >> ** >> >> *Hiram Chirino* >> >> *Software Fellow | FuseSource Corp.* >> >> *[email protected] | fusesource.com* >> >> *skype: hiramchirino | twitter: >> @hiramchirino<http://twitter.com/hiramchirino> >> * >> >> *blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>* >> >> * >> * >> >> * >> *
