Re: [JBoss-dev] JMX 1.2, remoting, and jmx-remoting commited to 3.2 branch

[Jeff H. <jh...@vo...>]

Tom/Scott,

The modules remoting and jmx-remoting weren't integrated into the main 
build and weren't being built into the main distribution. I fixed this 
and also setup the default detector/connectors to be automatically 
deployed as part of the default jboss-service.xml.

I've committed this fix to the branch. 

Jeff



Tom Elrod wrote:

> Just finished backporting JMX 1.2, jboss remoting, and jboss jmx 
> remoting to the 3.2 branch.  This puts the 3.2 branch at basically the 
> same code that is at HEAD in regards to the jboss-mx, jboss-remoting, 
> and jboss-jmx-remoting modules.  The tag before the commit is 
> 'before_JMX_1_2_checkin' and after commit is 'after_JMX_1_2_checkin'.
>
> There are still a few testsuite testcases that are still failing and 
> will be working on fixing them over the next couple of days (mostly 
> related to using dom4j now instead of jdom within jmx, which affects 
> deployment in some cases).  There are a lot of test failing now 
> compared to a few days back, but think many are not related to my 
> commit (such as the web services, which were failing before commit).  
> If you find something that does not work that you think is due to this 
> commit, please let me know.
>
> Now for the details...
>
> These changes will affect the 'jboss-3.2' module, 'Branch_3_2' branch.
>
> - Added dom4j.jar to the thirdparty lib and libraries.ent
> - Updated ManagementBean to support new methods within MBeanServer 
> interface.
> - Added org.jboss.mx.util.InstanceOfQueryExp back into 3.2 Branch (was 
> not part of original port).
> - Added dom4j.jar to the system/src/main/org/jboss/Main.java jmxLibs 
> attribute so would be included in the output when doing build.
> - Updated files in testsuite (mainly import corrections):
>
> JNDIPersistence
> JNDISecurity
> PrincipalInterceptor
> ProxyFactoryInterceptor
> SRPCacheInterceptor
> OnTimerPersistenceTestCase
> PrincipalInterceptor
> SecurityInterceptor
> NBMBeanTestCase.java
>
> Updated XMBean to accept both w3c and dom4j Element as parameter to 
> constructor.  This allows to be compatible with older code (using w3c) 
> and new code (where XMLMetaData requires dom4j Element).
>
> Removed:
>
> jmx\src\main\org\jboss\mx\interceptor\Invocation.java
> jmx\src\main\org\jboss\mx\interceptor\InvocationException.java
> jmx\src\main\org\jboss\mx\interceptor\MBeanAttributeInterceptor.java
> jmx\src\main\org\jboss\mx\interceptor\ModelMBeanInterceptor.java
> jmx\src\main\org\jboss\mx\interceptor\ObjectReferenceInterceptor.java
> jmx\src\main\org\jboss\mx\interceptor\PersistenceInterceptor2.java
> jmx\src\main\org\jboss\mx\interceptor\StandardMBeanInterceptor.java
> jmx\src\main\org\jboss\mx\server\StandardMBeanInvoker.java
>
> And, of course, hundreds of files updated within jboss-mx module, as 
> well as adding jboss-remoting and jboss-jmx-remoting modules.
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> JBoss-Development mailing list
> JBo...@li...
> https://lists.sourceforge.net/lists/listinfo/jboss-development