This content has been marked as final.
Show 2 replies
-
1. Re: 3.6.3 Optional Packages
thomas.diesler Aug 31, 2009 2:48 AM (in response to thomas.diesler)Ales sais,
Just found this in RequirementDependencyItem// Optional requirement if (requirement.isOptional() || requirement.isDynamic()) setResolved(true);
-
2. Re: 3.6.3 Optional Packages
adrian.brock Sep 14, 2009 12:10 PM (in response to thomas.diesler)The issue here is that the dynamic import metadata isn't getting mapped to
a PackageRequirement at the moment (see OSGiBundleClassLoadingDeployer for the TODO).
The reason I haven't done it, is because the OSGi metadata lets you specify
the packages using wildcards, while the current jboss implementation
only lets you do explicit package names.
See
org.jboss.classloading.spi.dependency.policy.DynamicClassLoaderPolicyFactory
and related classes.
I could make your test work (since it doesn't use wildcards) but that wouldn't be the
full solution.
There's a similar issue for the "uses" constraint.