Affects Version/s: 6.2.0 CE RC3
Fix Version/s: 6.2.0 CE RC3
Similar Issues:Show 5 results
Some Application Servers may not be able to load Module Framework, like JBoss EAP 5.1 (because of JBoss BUG). That makes portal unusable. This story allows portal to continue by using dummy implementation of module framework.
What is that URL with a problem? Its this one:
JBoss 5 does not like URLs like this - actually this exception is thrown by File() constructor, as URL is opaque. It has to be like this:
When url is opaque (without a path), JBoss will throw this exception.
Can we change this URL from the outside? There are two framework properties that looks relevant:
However, changing them to please JBoss does NOT fix the issue, as they are not used.
The core problem is in org.eclipse.osgi.baseadaptor.HookRegistry, method mergeFileHookConfigurators. There is a code like this:
getResources() returns Enumeration of URLs that JBoss doesn't like.
The JBoss patch can be activated with:
Finally, this brings new osgi-related exceptions related to version syntax of system packages.