[jboss-jira] [JBoss JIRA] Issue Comment Edited: (AS7-1301) Update OSGi to be compatible with JBoss Modules 1.1 series
[
https://issues.jboss.org/browse/AS7-1301?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler edited comment on AS7-1301 at 7/26/11 9:26 AM:
--------------------------------------------------------------
How is the client supposed to calculate the system loader paths? Internally I see JDKPaths
being used.
public static DependencySpec createSystemDependencySpec(final PathFilter importFilter,
final PathFilter exportFilter, final Set<String> loaderPaths)
was (Author: thomas.diesler):
How is the client supposed to calculate the system loader paths? Internally I see
JDKPaths being used.
public static DependencySpec createSystemDependencySpec(final PathFilter importFilter,
final PathFilter exportFilter, final Set<String> loaderPaths) {
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