[
https://issues.jboss.org/browse/JBREM-808?page=com.atlassian.jira.plugin....
]
Ron Sigal closed JBREM-808.
---------------------------
Resolution: Rejected
Remove dependencies on ObjectNameFactory from JBoss JMX
-------------------------------------------------------
Key: JBREM-808
URL:
https://issues.jboss.org/browse/JBREM-808
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.2.2.SP1, 2.4.0.Beta1 (Pinto)
Reporter: julien1
Fix For: 2.5.3.Beta (Flounder)
It happens when my POJO has not been bound on the transporter server, it looks like the
transporter client is trying to do some fail over.
This make JBoss Remoting depends on the JBoss JMX implementation. That makes JBoss
Remoting more difficult to embed and reuse.
I think that the ObjectNameFactory class could be easily ported to JBoss Remoting without
any harm done. However perhaps JBoss Remoting has more dependencies on JBoss JMX that I
don't know that would prevent to remove such dependency.
[junit_] Exception in thread "main" java.lang.NoClassDefFoundError:
org/jboss/mx/util/ObjectNameFactory
[junit_] at
org.jboss.remoting.transporter.InternalTransporterServices.<clinit>(InternalTransporterServices.java:41)
[junit_] at
org.jboss.remoting.transporter.TransporterClient.findAlternativeTarget(TransporterClient.java:330)
[junit_] at
org.jboss.remoting.transporter.TransporterClient.invoke(TransporterClient.java:301)
[junit_] at $Proxy0.getInfo(Unknown Source)
[junit_] at
org.jboss.portal.test.framework.driver.remote.RemoteTestDriverClient.getInfo(RemoteTestDriverClient.java:107)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira