[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=13100181#comment-13100181 ] 

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

Sorry, I'm bit zealous about this task, but I feel like Max misread Marcel's comment.
If Wildfly startup time is 3x slower, then that's a Wildfly or its component performance issue.
[~nogotiated], how much longer does full publish take, x seconds before the change, y seconds after?


I did split our war project into separate webfragment projects. Al the moment they contain around 2000 files (xhtml, resources, classes) total. Their total build output size is 10 MB. Didn't notice performance issues with full publish in JBDS9.0.0.Beta2, and no server startup slowdown with Wildfly 8.2.0.Final.

Of course, copying a lot of files is always slower than copying one big file. That's just how filesystems and HDDs work.
If JBT wants to allow controlling explodiness (other than explode all or nothing, which it does now), then maybe should go all the way and allow to configure explodiness of individual (sub-)deployments?

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