This content has been marked as final.
Show 3 replies
-
1. Re: MBeanServer in client JAR
dimitris Oct 12, 2004 4:48 AM (in response to damien)I'm not aware why the change was made, just before 3.2.4 was out. Looking into the CVS tree version 1.160.2.155 of build/build.xml:
<!-- Copy the generated client libraries --> <mkdir dir="${install.client}"/> <copy tofile="${install.client}/jmx-client.jar" file="${_module.output}/lib/jboss-jmx-core.jar" />
jmx-client.jar is then included as part of jbossall-client.jar.
What's the conflict you get when running your client application?
I guess the easy solution is to pick the jboss client jars individually,
e.g. jboss-client.jar + jboss-common-client.jar + ..., or remove
org.jboss.mx.* & javax.management.* from jbossall-client.jar -
2. Re: MBeanServer in client JAR
starksm64 Oct 12, 2004 10:41 AM (in response to damien)There are objects that can be pulled down via jmx calls that need the jboss jmx implementation classes. Not all of the org.jboss.mx classes in the jbossall-client.jar are actually needed so it can be trimmed down depending on your usage.
-
3. Re: MBeanServer in client JAR
damien Oct 12, 2004 3:00 PM (in response to damien)Ok. Thanks for the input. I think the answer for me is only including the JARs that I need.
Otherwise, we'll have to bring the dom4j.jar dependency into our client classpaths. That is actually how we found out about this - our client processes wouldn't start because of a NoClassDefFound error. The JBoss JMX stuff depends on dom4j.