[
https://issues.jboss.org/browse/WFLY-6821?page=com.atlassian.jira.plugin....
]
Lin Gao commented on WFLY-6821:
-------------------------------
This Jira is created to track the changes in WildFly main repository.
After discussion in
https://github.com/wildfly/wildfly-core/pull/1332, to fix this overlay
problem, both WildFly core and WildFly will be changed.
Not possible to overlay non existing file in WAR - mark the sub
deployment which will be mounted exploded
---------------------------------------------------------------------------------------------------------
Key: WFLY-6821
URL:
https://issues.jboss.org/browse/WFLY-6821
Project: WildFly
Issue Type: Bug
Components: EE
Affects Versions: 10.0.0.Final
Reporter: Lin Gao
Assignee: Lin Gao
Priority: Critical
It is either bug in how deployments are treated or how overlay/vfs work.
Steps to reproduce:
1. deploy undexploded war with jar inside
2. add overlay that will add non existing file in jar
Result: exception:
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776:
Failed to get content for deployment overlay
WEB-INF/lib/overlayed.jar//META-INF/x/file.txt at
WEB-INF/lib/overlayed.jar//META-INF/x/file.txt
Caused by: java.io.FileNotFoundException:
/content/shell.war/WEB-INF/lib/overlayed.jar/META-INF/x/file.txt"}}
at
org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67)
at
org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37)
at
org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayUtils.setupOverlay(OverlayUtils.java:76)
at
org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase.testOverlay(OverlayNonExistingResourceTestCase.java:67)
Expectation:
should work. It actually does work, if war is really exploded or
'if(exploded)' part in overlay is removed from overlay processor and everything
is handled via:
https://github.com/stuartwdouglas/wildfly-core/blob/a75af9118c4062fafb899...
This is part of the fix of above issue, which depends on WFCORE-761.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)