Does anybody have any thoughts on this? Both are important to the concurrency work but 2) is a little more important as I can't integrate the concurrency code with Geronimo without disabling some other functionality.
Thanks, Jarek On Wed, Feb 20, 2008 at 4:12 PM, Jarek Gawor <[EMAIL PROTECTED]> wrote: > I have a couple of questions about module builders/deployers and > plugin support in Geronimo: > > 1) I have a plugin that contains a NamingBuilder. Once I install this > plugin, that NamingBuilder will not be called during module deployment > until I 'register' it with the NamingBuilders gbean (e.g. in > plugins/j2ee/j2ee-deployer/src/main/plan/plan.xml or config.xml). The > questions is, can we make this more dynamic? It would be great just to > install the plugin and have the NamingBuilder to be invoked > automatically without any additional configuration steps. > > 2) The AdminObjectRefBuilder is always trying to process _all_ > resource-env-ref entries (AdminObjectRefBuilder is just an example in > this case). However, as things evolve (Java EE 5 -> 6) and new > resource env. types are added, it does not scale to keep updating the > AdminObjectRefBuilder to handle these new types. So I think it would > be nice to install a new builder that would handle these new types > only. But that would require communicating with the > AdminObjectRefBuilder and somehow telling it to ignore the new types. > The question is, what would be the best way of doing it? Or maybe we > need a different way of processing the DDs? > > Jarek >
