Uploaded image for project: 'JBoss Modules'
  1. JBoss Modules
  2. MODULES-13

Ability limit imported packages

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • 1.0.0.Beta2
    • None
    • None
    • None

      Consider this

      Bundle-SymbolicName: jbosgi323-bundleA
      Import-Package: org.jboss.test.osgi.container.classloader.support.a

      Bundle-SymbolicName: jbosgi323-bundleB
      Export-Package:
      org.jboss.test.osgi.container.classloader.support.a,
      org.jboss.test.osgi.container.classloader.support.b

      So moduleA has a dependency on moduleB because A imports package 'a' which B exports.
      However, loading a class from package 'b' through A is expected to fail, because A does not import nor contain package 'b'

      Currently this usecase fails (i.e. the class from b can be loaded through A) because you cannot control the paths that a module imports.

              johnbailey_jira John Bailey (Inactive)
              tdiesler@redhat.com Thomas Diesler
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: