Uploaded image for project: 'JBoss WFK 2'
  1. JBoss WFK 2
  2. WFK2-65

Grails applications cannot be deployed to EAP unless OSGi is disabled

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.2.0.GA, 2.5.0.GA, 2.6.0.GA
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Target Release:
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      To workaround this issue, disable adding of OSGi headers while packaging your Grails applications by adding the following configuration into the BuildConfig.groovy configuration file:

      grails.project.war.osgi.headers = false

      Show
      To workaround this issue, disable adding of OSGi headers while packaging your Grails applications by adding the following configuration into the BuildConfig.groovy configuration file: grails.project.war.osgi.headers = false
    • Release Notes Docs Status:
      Documented as Known Issue
    • Release Notes Text:
      Hide
      OSGi is not enabled in JBoss Enterprise Application Platform 6, and artifacts produced by Grails 1.3.9 miss a Package-Import of javax.naming in the bundle. To work around the issue, disable adding of OSGi headers while packaging your Grails applications by adding the following configuration into the BuildConfig.groovy configuration file:

      grails.project.war.osgi.headers = false
      Show
      OSGi is not enabled in JBoss Enterprise Application Platform 6, and artifacts produced by Grails 1.3.9 miss a Package-Import of javax.naming in the bundle. To work around the issue, disable adding of OSGi headers while packaging your Grails applications by adding the following configuration into the BuildConfig.groovy configuration file: grails.project.war.osgi.headers = false
    • Bugzilla References:

      Description

      Description of problem:

      Grails applications with OSGi can't be deployed on EAP.

      As a workaround, adding OSGi headers to generated WAR file can be disabled (see [2]).

      Steps to Reproduce:
      1. create a Grails application (grails create-app)
      2. package the application (grails war)
      3. deploy the application to EAP

      Actual results:
      deployment fails with following error:

      ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service thread 1-7) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle resModule: [grails-app:0.1.0]

      (...)
      Caused by: org.jboss.osgi.resolver.XResolverException: Unable to resolve Module[grails-app:0.1.0]: missing requirement [Module[grails-app:0.1.0]] package; (&(package=javax.servlet)(version>=2.5.0)(!(version>=3.0.0)))

      Expected results:
      application is deployed correctly

      Additional info:
      [1] https://issues.jboss.org/browse/AS7-2941
      [2] https://docspace.corp.redhat.com/docs/DOC-88882 (section 'Grails')

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                emil.cervenan Emil Cervenan
                Reporter:
                maschmid Marek Schmidt
                Tester:
                Emil Cervenan
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: