[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1236:
---------------------------------------
It is legal to include non-deployment subdirectories under deployments/ as a means of
organizing content for whatever purpose the user may have. If the scanner finds a
directory whose name does not end in .ear, .jar, .rar, .sar or .war it assumes that
directory is just for organizational purposes and will recurse into it looking for
deployments. That is what is happening here. Unzipping an archive such that WEB-INF is a
directory not under another directory named X.war is a user error.
The scanner can handle this a bit more gracefully by checking for a directory named
WEB-INF or META-INF and if found logging a ERROR message and not recursing into it looking
for deployments. I'll add that in response to this JIRA. If you unzip an ear this way
though, you'll get an ERROR message about the META-INF dir, but it's going to go
ahead and try and deploy the modules in the ear since they are not located under
META-INF.
copied lib directory in the deployments directory results in
deployment
------------------------------------------------------------------------
Key: AS7-1236
URL:
https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira