> yes. I will keep what you need in mind - I think it will be easily > accessible.
Good. > You've probably already told me at least once, but I'm still not entirely > clear if you are developing something that (while implementing jsr77) is > jboss specific or if it is intended to run on any app server. The JSR-77 implementation is JBoss specific because it has to map the JBoss internal data structure to the JSR-77 data structure. As already said JSR-77 does not offer code by a model how the presented data looks like. > I'm wondering since I think it would be useful to have mbeans representing > deployment units, where the mbeans can participate in the mbean dependency > stuff. So you could make one part of your app wait for another part to be > deployed. I already did this with RARDeployment, so > ConnectionFactoryLoaders wouldn't get started until the connector they > needed was there. Could the management beans you are working on be used > for that? To make it work, from my point of view, all you need is to call > ServiceController.registerAndStartService after your mbean is created. The > "start" part doesn't have to be implemented or do anything. I am not quite sure and must have a look at it. The problem I see is that I don't know exactly what I am waiting for (we have n-application, up to 3n-modules and m*3n components). Andy _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
