"[EMAIL PROTECTED]" wrote : Just to review, this error only happens when using jdk 1.6, but works with jdk 1.5, right? Yepp. anonymous wrote : I can make the update to use the other forName() method signature as you mentioned, but only problem is that current code base is for 2.0.0 release, which is going to be impossible to test with the current code base. Not sure, whether I understood this correctly. Anyway, IMHO forName should be ok and perhaps even safer, since if available, it obeys the security managers hint ;-)
anonymous wrote : Do you mind opening a jira issue against JBossRemoting project for this with link to this forum thread? Done. See http://jira.jboss.com/jira/browse/JBREM-508 - hope its enough info ;-) anonymous wrote : If you have a test case specific to remoting (without using ejb3, but just remoting) that would be awesome. Unfortunately I have not and haven't had the chance yet, to dive into the remoting test suite :(. But anyway, you are probably much, much faster, doing this right ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951868#3951868 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951868 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
