[jboss-jira] [JBoss JIRA] (AS7-141) Deployment fails with empty classpath manifest

[Peter Hinds (JIRA)]

    [ https://issues.jboss.org/browse/AS7-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12946459#comment-12946459 ] 

Peter Hinds commented on AS7-141:
---------------------------------

Hi John,

A quick query, I have found that auto-deploying (copy to \jboss-eap-6.2\standalone\deployments) an ear which contains a war with an empty class path in the war MANIFEST.MF still fails, whereas deploying through the Admin GUI (localhost:9990) deploys OK.

My EAP version is 6.2.0 GA, which is built on AS 7.3 so this fix should be included. Being a newcomer to JBoss, is the autodeploy a completely separate component? If so, should I raise a new issue?

For reference, when I auto-deploy the ear with the war containing an empty classpath, the server.log gives a fairly indescript error:

[14:55:22] Peter Hinds (AMT-SYBEX): Deployment content C:\jboss-eap-6.2\standalone\deployments\meterflow-web-ear-JBOSS_PORT.1.1.ear appears to be incomplete and is not progressing toward completion. This content cannot be auto-deployed.

It was only by chance I found that by removing the MANIFEST.MF empty classpath in the war, that I was able to auto-deploy the ear.
                
> Deployment fails with empty classpath manifest
> ----------------------------------------------
>
>                 Key: AS7-141
>                 URL: https://issues.jboss.org/browse/AS7-141
>             Project: Application Server 7
>          Issue Type: Bug
>    Affects Versions: 7.0.0.Alpha1
>            Reporter: Max Rydahl Andersen
>            Assignee: Stuart Douglas
>             Fix For: 7.0.0.Beta1
>
>         Attachments: jbossas7-deploy-example.war
>
>
> If you war has a MANIFEST.MF with empty classpath you get an error even though empty Class-Path: is present (and afaik valid).
> This is btw. how Eclipse defaults to create a war with no jar dependencies thus it would fail for a lot of folks ;)
> 11:53:53,682 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "jbossas7-deploy-example.war"
> 11:53:53,706 WARN  [org.jboss.vfs] (MSC service thread 1-1) VFS was unable to set the URLStreamHandlerFactory.  This will have unpredictable results
> 11:53:53,731 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001:Failed to start service jboss.deployment.unit."jbossas7-deploy-example.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbossas7-deploy-example.war".PARSE: Failed to process phase PARSE of deployment "jbossas7-deploy-example.war"
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:109)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1367)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
> 	at java.lang.Thread.run(Thread.java:680) [:1.6.0_22]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Class Path entry  in "/content/jbossas7-deploy-example.war"  not found. 
> 	at org.jboss.as.server.deployment.module.ManifestClassPathProcessor.deploy(ManifestClassPathProcessor.java:123)
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:103)
> 	... 4 more
> I'm attaching a simple war showing this.

--
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