[esb-issues] [JBoss JIRA] Updated: (JBESB-2972) Extend locations for loading jars in as5 deployments

[Kevin Conner (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBESB-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Conner updated JBESB-2972:
--------------------------------

              Summary: Extend locations for loading jars in as5 deployments  (was: ESB deployments don't see classes in the lib dir of the.esb archive)
           Issue Type: Feature Request  (was: Bug)
          Component/s: Deployment
    Affects Version/s: 4.7


Updated summary.

The location for loading jars hasn't changed, what has changed is the way in which the app server now handles sub-deployments.

In as4 the app server would recursively locate jars/deployments and add them into the classpath or deploy them.  This is no longer the case in as5.

> Extend locations for loading jars in as5 deployments
> ----------------------------------------------------
>
>                 Key: JBESB-2972
>                 URL: https://jira.jboss.org/jira/browse/JBESB-2972
>             Project: JBoss ESB
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Deployment
>    Affects Versions: 4.7
>            Reporter: Aaron Pestel
>
> It appears that the default folder in .esb archives for picking up dependent jars has changed from "lib" to "jars".  This is does not map to the default JBDS ESB project which creates a "lib" directory and will break existing deployments of .esb files that have jars in the /lib directory of the .esb archive.
> This was created as a result of:  https://jira.jboss.org/jira/browse/SOA-1588

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira