[jbosstools-issues] [JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib

[Vsevolod Golovanov (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079218#comment-13079218 ] 

Vsevolod Golovanov commented on JBIDE-20071:
--------------------------------------------

Project structure is:
* EAR
** EJB
** WAR
*** JAR-UI-1
*** JAR-UI-2

(JAR-UIs are in WAR's WEB-INF/lib directory.)

Yes, JAR-UIs have:
# classes;
# JSF/Facelet resources: XHTMLs, images, css, js...

Servlets look at JAR-UI's META-INF/web-fragment.xml and combine it with web.xml. JSF looks up resources in META-INF/resources.

Changes to classes get applied by Eclipse/JBDS on the fly as usual.
But changes to JSF resources don't get picked up. IDE/Tools deploy them, the new files are there, but VFS still returns old files from the temporary directory (more ramblings [here|http://stackoverflow.com/questions/28326523/hot-deploying-resources-in-war-libs]).
I've checked that when placing exploded JAR-UI in WAR/WEB-INF/lib:
* server does start;
* when changing a JSF resource, and reloading a page, it does use the updated resources.

> 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
>
> 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?
> 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.3.15#6346)