[ https://issues.jboss.org/browse/AS7-3719?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-3719: ----------------------------------- I don't have any experience with Grails, so I can't say what's wrong. Can you please open a forum thread for discussion here https://community.jboss.org/en/jbossas7?view=discussions so that someone might be able to help you with this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3719?page=com.atlassian.jira.plugin.s... ] David Pugh commented on AS7-3719: --------------------------------- There already is a discussion opened about this https://community.jboss.org/message/715968#715968 I only posted a bug here because we can't find the solution to the issue. The same war file will work with JBoss 4.2.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3719?page=com.atlassian.jira.plugin.s... ] David Pugh commented on AS7-3719: --------------------------------- All of the OSGI workarounds for that other bug (https://issues.jboss.org/browse/AS7-2941) have been rejected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3719?page=com.atlassian.jira.plugin.s... ] David Pugh commented on AS7-3719: --------------------------------- Hello, I wasn't exactly sure how to disable OSGI, but removed it from subsystem in standalone.xml and now grails DOES load properly. I do get this Warning: 13:13:34,031 WARN [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFact ory' But grails does work properly once OSGI is disabled. I guess Jboss AS was thinking that grails was OSGI rather than a standard web app. Thank you for your patience. David -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3719?page=com.atlassian.jira.plugin.s... ] Graeme Rocher commented on AS7-3719: ------------------------------------ Building the Grails war with: {code} grails -Dgrails.project.war.osgi.headers=false war {code} Will remove the OSGi headers from the WAR file which is what is confusing JBoss 7. The above can also be configured in BuildConfig.groovy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3719?page=com.atlassian.jira.plugin.s... ] Graeme Rocher updated AS7-3719: ------------------------------- Attachment: MANIFEST.MF Attached is an example manifest. This works when deploying to other OSGi containers like Virgo. No idea if it is a JBoss or Grails bug. Seems to me JBoss shouldn't be treating it as a OSGi bundle if "Webapp-Context:" is specified? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3719?page=com.atlassian.jira.plugin.s... ] Radim Kolář commented on AS7-3719: ---------------------------------- I got same error as you: WARN [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFact ory' but real error message is in xxxx.war.failed file: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host.\"/nxd-0.1\"" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host.\"/nxd-0.1\": JBAS018040: Failed to start context"},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"nxd-0.1.war\".jboss.security.jacc Missing[JBAS014861: <one or more transitive dependencies>]"]}}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3719?page=com.atlassian.jira.plugin.s... ] Radim Kolář commented on AS7-3719: ---------------------------------- Actually it seems that grails spring-security-core is to blame because plain grails hello world app deploys and runs fine on 7.1.3-SNAPSHOT. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira