[
https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-20071:
-------------------------------------
[~giannitom] I've read the spec pages for reference:
_The Web application class loader must load classes from the WEB-INF/classes directory
first, and then from library JARs in the WEB-INF/lib directory. Also, except for the case
where static resources are packaged in JAR files, any requests from the client to access
the resources in WEB-INF/ directory must be returned with a SC_NOT_FOUND (404) response.
_
This seems to be not a bug, but rather according to spec. Users who use exploded
deployment should not be placing their resources in the WEB-INF folder or it will be met
with a 404.
Allow deploying exploded jars to war/WEB-INF/lib
------------------------------------------------
Key: JBIDE-20071
URL:
https://issues.jboss.org/browse/JBIDE-20071
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.2.3.Final
Environment: JBoss Developer Studio 8.1.0.GA
Reporter: Vsevolod Golovanov
Assignee: Rob Stryker
Labels: new_and_noteworthy
Fix For: 4.3.0.Beta2
There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying
expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason
seemed to be that the server at the time refused to deploy such structure. Maybe the
server was in the wrong? This was fixed in AS7-4704.
Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least
Weld, EJB, JSF seem to work fine.
The main use case for this is creating a modular web application, with different parts
implemented in separate projects. Hot deploying of resources, such as Facelets'
XHTMLs, is crucial for development. So the JARs need to be exploded.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)