[jboss-jira] [JBoss JIRA] (AS7-6281) Non existing external modules should be ignored in ManifestClassPathProcessor

Ales Justin (JIRA) jira-events at lists.jboss.org
Sat Jan 5 17:11:08 EST 2013


Ales Justin created AS7-6281:
--------------------------------

             Summary: Non existing external modules should be ignored in ManifestClassPathProcessor
                 Key: AS7-6281
                 URL: https://issues.jboss.org/browse/AS7-6281
             Project: Application Server 7
          Issue Type: Enhancement
          Components: Class Loading
    Affects Versions: 7.1.3.Final (EAP)
            Reporter: Ales Justin
            Assignee: Stuart Douglas


If MANIFEST.MF Class-Path points to invalid external path,
it should be ignored, and warning logged.

Instead of failing whole deployment,
where actually it could still work.

e.g.

18:01:45,857 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.module.spec.service."deployment.external./home/codegen/dependencies/java/stable/dependencies/libs/guava-11.0.1.jar".main: org.jboss.msc.service.StartException in service jboss.module.spec.service."deployment.external./home/codegen/dependencies/java/stable/dependencies/libs/guava-11.0.1.jar".main: java.io.FileNotFoundException: /home/codegen/dependencies/java/stable/dependencies/libs/guava-11.0.1.jar (No such file or directory)
	at org.jboss.as.server.moduleservice.ExternalModuleSpecService.start(ExternalModuleSpecService.java:65) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list