[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-549) remove dependancy on concurrent.jar within remoting client

[Ron Sigal (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBREM-549?page=all ]

Ron Sigal updated JBREM-549:
----------------------------

    Fix Version/s:     (was:  2.4.0.Beta2 (Pinto))

Removed fix version.

> remove dependancy on concurrent.jar within remoting client
> ----------------------------------------------------------
>
>                 Key: JBREM-549
>                 URL: http://jira.jboss.com/jira/browse/JBREM-549
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.0.0.Beta2 (Boon)
>            Reporter: Tom  Elrod
>
> Currently, the remoting clients will require concurrent.jar to be on the classpath because org.jboss.util.id.GUID is used to create the client session id.  Problem is that org.jboss.util.id.GUID is what requires concurrent.jar.  So will either need to modify the code within jboss common repository or find another class to use for generating the client session id.
> java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/SynchronizedLong
>         at org.jboss.util.id.UID.<clinit>(UID.java:56)
>         at org.jboss.util.id.VMID.create(VMID.java:259)
>         at org.jboss.util.id.VMID.getInstance(VMID.java:223)
>         at org.jboss.util.id.GUID.<init>(GUID.java:65)
>         at org.jboss.remoting.Client.<init>(Client.java:133)
>         at org.jboss.remoting.Client.<init>(Client.java:210)
>         at org.jboss.remoting.Client.<init>(Client.java:191)
>         at org.jboss.test.remoting.transport.InvokerClientTest.init(InvokerClientTest.java:80)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira