Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-872

Log4J bundle fails to install due to javax.swing imports

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Minor
    • None
    • 7.0.0.CR1
    • OSGi
    • None
    • Hide

      There is a workaround, simply add javax.swing to the org.osgi.framework.system.packages.extra property in standalone.xml...

      Show
      There is a workaround, simply add javax.swing to the org.osgi.framework.system.packages.extra property in standalone.xml...

    Description

      The following bundle is quite commonly used: http://ebr.springsource.com/repository/app/bundle/version/detail?name=com.springsource.org.apache.log4j&version=1.2.15&searchType=bundlesByName&searchQuery=log4j

      It's the springsource osgi-ified version of Log4J version 1.2.15

      It installs without problems in Felix and Equinox but when installing it in AS7 it fails on a mandatory import of javax.swing?

      There's a few things fishy about this:
      1. why does the log bundle have this mandatory dependency? That probably a bug in the bundle, but anyway.
      2. is the framework required to export javax.swing?
      I always thought it wasn't but then on the other hand it works with Felix and Equinox, so it should work with us too... Especially such a common bundle should install smoothly IMHO.

      12:15:09,520 ERROR [org.jboss.osgi.framework.internal.AbstractBundleState] (MSC service thread 1-4) Could not resolve bundle: com.springsource.org.apache.log4j:1.2.15: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [com.springsource.org.apache.log4j:1.2.15]
      	at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:157)
      	at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:551)
      	at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:185)
      	at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:489)
      	at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:135)
      	at org.jboss.as.osgi.deployment.BundleStartTracker$1.serviceStarted(BundleStartTracker.java:107)
      	at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1322) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
      	at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:47) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
      	at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1850) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8]
      	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23]
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23]
      	at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
      Caused by: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[com.springsource.org.apache.log4j:1.2.15]: missing requirement [Module[com.springsource.org.apache.log4j:1.2.15]] package; (package=javax.swing)
      	at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(FelixResolver.java:117)
      	at org.jboss.osgi.resolver.spi.AbstractResolver.resolve(AbstractResolver.java:148)
      	at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:155)
      	... 11 more

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              dhildenb@redhat.com David Hildenbrand
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: