|
From: Rob H. <ro...@ca...> - 2004-11-06 15:25:43
|
Nick, We won't be competing to an appserver, but by JMX-enabling the core Spring classes you will have a lot more runtime control over your Spring beans. Rob Nick Minutello writes: >> The long term goals for Spring JMX are quite broad since we want to add >> support for interacting with Spring via JMX and hook in JMX as a way of >> modifying Spring managed beans and have those changes persisted to some >> store. > > What is the intended purpose/usage here? > Sounds like spring is moving on from a "complementing" role (to an > appserver) to a competing one - or do I misunderstand it... :-) > >> Currently we have a reflection-based assembler that exposes all >> methods and all properties, > Sounds like what I want. > >> and a source metadata-based assembler that >> exposes only those methods and properties that you mark in your source code. > Source code?? > I guess I will have a look at the tests.. > >> There is a short piece on this in the >> Spring Wiki, plus Craig Walls did some coverage on his blog at >> http://jroller.com/page/habuma. The best resource to check out are the tests > Thanks, I will have a read.. > > Cheers, > Nick > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |