On 2001.12.06 14:01:03 -0500 Bill Burke wrote: > MBeans in 2.4.x are really really simple and easy to understand. It's > also easy to understand the flow of initialization. IMHO, anything new > in 3.0 should be an extension of 2.4.x for more advanced configurations. > I'm hoping that 3.0 will move back to 2.4.x's simplicity, but be > extendible for more advanced users like Marc suggested.
I think it's simpler to write a small config file with exactly the config I need for what I'm doing than mess with trying to find the right place in jboss.jcml and figure out what I need to add/subtract without breaking stuff. Since I always get it wrong 15 or 20 times before it works, I enjoy being able to redeploy just my stuff rather than restarting the entire server. For the alleged simplicity of 2.4 configuration.... how many people using say Oracle do you think turned off hsqldb DefaultDS? Or realized it wasn't magic, they could change DefaultDS to use Oracle? I think whats needed is some documentation and examples. > > > > > Another question. How do I write initializer > > mbeans? > > > What I mean by an > > > initializer is something that runs AFTER all mbean > > > components and EJBs have > > > been deployed. Like WebLogic startup-up classes. > > > How can I write something > > > like this in the new architecture. > > > > This is unclear. > > > > I want to have an MBean that can do stuff once all other components are > loaded. Stuff like, preload Entity Beans and such. Is there a way to > create a dependency between all EJBs and the MBean I want to write? Probably not at the moment, I have a bunch of ideas, but it will be a while. Basically I'd like to create mbeans for each deployment unit, similar to the RARDeployment mbean, which is used to force ConnectionFactoryLoaders to wait for the rar they use. If Andreas's mangement mbeans are far enough along you could find out what the object name for the mbean representing your ejb package is and use an anonymous mbean dependency on it in the mbean you want to wait. You might also be able to use anonymous mbean dependencies to the Containers. However both of these ideas require the mbeans in question to participate in the dependency tracking by registering with ServiceController, which I doubt they do. Another idea that would work today would be to write an mbean that explicitly deploys your ejb package (see JBossTestServices for some example code, although this is more complicated than you need, just call J2eeDeployer with the path to the package) and have the other mbeans depend on it. BTW an anonymous mbean dependency is like this: <mbean-ref>JBOSS-SYSTEM:service=myservice</mbean-ref> where there is no corresponding property on the mbean. It > used to be the AutoDeployer deployed all EJBs before the next MBean was > loaded. Why was this changed? (Or was it changed?) I think this was accidental behavior. david jencks > > > > ---- > View: http://jboss.org/forums/thread.jsp?forum=66&thread=4977 > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
