[jboss-jira] [JBoss JIRA] Commented: (JBAS-4927) Code added in 4.2.1 breaks web app that works in 4.2.0
Francisco Reverbel (JIRA)
jira-events at lists.jboss.org
Tue Nov 27 14:30:46 EST 2007
[ http://jira.jboss.com/jira/browse/JBAS-4927?page=comments#action_12389458 ]
Francisco Reverbel commented on JBAS-4927:
------------------------------------------
This looks a client-side issue. Try adding just jboss-iiop-client.jar to the client classpath (server/default/lib, if the client is running within default JBossAS config).
In order to make the dynamic generation of IIOP stubs simpler and more efficient, the generated stubs are *not* JBoss independent: they are derived from org.jboss.proxy.ejb.DynamicIIOPStub and use various classes from the package org.jboss.iiop.rmi.marshal. Hence the need for jboss-iiop-client.jar at the client side.
> Code added in 4.2.1 breaks web app that works in 4.2.0
> ------------------------------------------------------
>
> Key: JBAS-4927
> URL: http://jira.jboss.com/jira/browse/JBAS-4927
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service
> Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
> Environment: linux, java5
> Reporter: Greg Bridges
> Assigned To: Stefan Guilhen
> Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
>
>
> Code was added in version 4.2.1 to the WebAppClassLoader class to override the findClass() operation.
> I have a web app that uses the sun rmi-iiop to connect to remote applications (which worked fine before). The stubs for my code are located in my deployed jars in the war.
> At line 98 in WebAppClassLoader.java, a call is made to attempt to run the iiopstubcompiler. It gets a ClassDefNotFound on the IIOPStubCompiler class, which then bypasses the catch block (which is looking for a RuntimeException). It looks like the intent was to run the super.findClass() if there is any trouble, but that doesn't happen due to the catch block being bypassed.
> If I change the code to catch Throwable or add a catch for ClassDefNotFound which runs super.findClass(), the app works as it did before.
--
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
More information about the jboss-jira
mailing list