[
https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugi...
]
Vsevolod Golovanov commented on JBIDE-20071:
--------------------------------------------
[~giannitom], no, it doesn't occur with Wildfly, that's part of the premise of
this task. I have a webapplication running right now with resources and classes in lib
jars (see above comments).
As far as I know, Java EE specs don't say anything about exploded deployments at all.
If you bring the spec into the question, then exploded ears, wars and ejbs may justifiably
not work for the same reason as jars in war libs.
So it is a JBoss AS bug.
If there is a bug. Can you attach the sample project?
It was already implemented in this task, that this explodiness is enabled only for
selected server versions which are known to support it. So if there is a bug, the server
version support should be amended.
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)