(Per http://jira.jboss.com/jira/browse/JBREM-659)
Have update all the places where ClassLoader.loadClass() was being called and
either replaced with Class.forName() call or changed to use the
ClassLoaderUtility class. These changes have been made to HEAD, remoting_2_x
and remoting_1_4
anonymous wrote : Is there a patched jboss-remoting.jar for JBoss AS 4.0.5.GA
that has a fix for this issue?
I have compiled a patched version of jboss-remoting.jar, and it seems to work
with JDK6. I'm looking for someone to host the fixed version.
See
I say it needs to be fixed, it is still not fixed in 5.0 beta so no sign of a
change...
...anyone know how to hack it?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3999287#3999287
Reply to the post :
I took a second look at the related bugs, and found this:
anonymous wrote : I am the submitter of the bug. After analysing the related
bugs, it seems that this change is an intended change (and not a regression).
See the evaluation of bug #6446627 and bug #4872868. It seems that some
products
Damn...I guess we can only wait for 6.0 update 1 :(
EJB3 remote interfaces are totally unusuable atm, since this happens with
collections too.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994489#3994489
Reply to the post :
http://jira.jboss.com/jira/browse/JBREM-651
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994409#3994409
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3994409
___
jboss-user
So is this a JDK6 bug? I know the behavior was changed, but is it broken in
JDK6, or do the other software just have catching up to do?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994439#3994439
Reply to the post :
I view it as a bug and it appears to have been accepted as such.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6434149
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994470#3994470
Reply to the post :
This is a known bug in JBoss Remoting v1.4.x. For some reason, the fix has not
been backported to the 1.4 branch. This is especially odd since the 2.x
versions can't replace v1.4.x directly, and thus JBoss 4 users are left
hanging or being told to fix the problem by building from CVS (this
