[jira] Updated: (FELIX-1158) Strange NoClassDefFoundError in WebLogic 9.2 when creating URLStreamHandlersProxyFactory
[ https://issues.apache.org/jira/browse/FELIX-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard S. Hall updated FELIX-1158: --- Fix Version/s: felix-1.8.0 Strange NoClassDefFoundError in WebLogic 9.2 when creating URLStreamHandlersProxyFactory Key: FELIX-1158 URL: https://issues.apache.org/jira/browse/FELIX-1158 Project: Felix Issue Type: Bug Components: Framework Affects Versions: felix-1.2.1 Reporter: Don Brown Assignee: Karl Pauls Fix For: felix-1.8.0 Attachments: FELIX-1158.diff This bug really makes no sense, and the fix makes even less, but here it goes: In WebLogic 9.2, in some cases, the URLHandlers class is unable to create a URLStreamHandlersProxyFactory due to a NoClassDefFoundError. The really weird bit is you can load the class using the class's classloader just fine via loadClass(). Attached is the hack that implements this workaround. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1158) Strange NoClassDefFoundError in WebLogic 9.2 when creating URLStreamHandlersProxyFactory
[ https://issues.apache.org/jira/browse/FELIX-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Don Brown updated FELIX-1158: - Attachment: FELIX-1158.diff Strange NoClassDefFoundError in WebLogic 9.2 when creating URLStreamHandlersProxyFactory Key: FELIX-1158 URL: https://issues.apache.org/jira/browse/FELIX-1158 Project: Felix Issue Type: Bug Components: Framework Affects Versions: felix-1.2.1 Reporter: Don Brown Attachments: FELIX-1158.diff This bug really makes no sense, and the fix makes even less, but here it goes: In WebLogic 9.2, in some cases, the URLHandlers class is unable to create a URLStreamHandlersProxyFactory due to a NoClassDefFoundError. The really weird bit is you can load the class using the class's classloader just fine via loadClass(). Attached is the hack that implements this workaround. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
