[jboss-jira] [JBoss JIRA] Commented: (AS7-1236) copied lib directory in the deployments directory results in deployment
[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-1236:
---------------------------------------
There is no requirement that an ejb deployment has to be packaged in an ear or a war. So
if the scanner sees a .jar, it assumes it's an ejb deployment and tries to deploy it.
This isn't new behavior; the scanner in AS 5 and 6 if it sees a directory it checks if
its filename matches one of the expected extensions; if yes it tries to deploy it as an
exploded deployment; if no it recurses into it looking for deployments. I believe the same
is true in AS 3 and 4 as well.
The only difference in AS 7 is we write out the .failed files.
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
Assignee: Brian Stansberry
Fix For: 7.0.0.Final
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