[
https://issues.jboss.org/browse/AS7-1301?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler commented on AS7-1301:
-------------------------------------
The framework supports the notion of configurable system packages that can be loaded from
the system bundle.
Every bundle must be able load these packages from the system class loader
??The Framework must always delegate any package that starts with java. to the parent
class loader.??
In our implementation we define a system dependency for every host bundle. Currently I do
it like this
{code}
// Add a system dependency
SystemPackagesPlugin plugin = injectedSystemPackages.getValue();
PathFilter systemPackagesFilter = plugin.getSystemPackageFilter();
PathFilter sysImportFilter = systemPackagesFilter;
PathFilter sysExportFilter = PathFilters.acceptAll();
moduleDependencies.add(DependencySpec.createSystemDependencySpec(sysImportFilter,
sysExportFilter, null));
{code}
Please note the 'null' for the system paths. I could define this set explicitly,
which would require an update for every jdk version, right? Meanwhile, I think a fallback
to JDKPaths.JDK is ok and we can revisit when I look at framework bootstrap performance.
Update OSGi to be compatible with JBoss Modules 1.1 series
----------------------------------------------------------
Key: AS7-1301
URL:
https://issues.jboss.org/browse/AS7-1301
Project: Application Server 7
Issue Type: Task
Components: OSGi
Reporter: David Lloyd
Assignee: Thomas Diesler
Fix For: 7.1.0.Alpha1
JBoss Modules 1.1 has two significant changes. First, jaxpmodule is eliminated. Second,
the system module is no more - instead there's a dependency type for the system class
loader.
I currently have an updated AS in my
http://github.com/dmlloyd/jboss-as/tree/upgrades
branch.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira