[jboss-jira] [JBoss JIRA] Closed: (JBAS-5106) a jar file inside a jar file inside an ear file is deployed as not in the ear

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-5106?page=all ]

Adrian Brock closed JBAS-5106.
------------------------------

    Resolution: Incomplete Description

This  bug  report is incomprehensible.

Please provide:
* Example deployment(s) showing the problem
* Expected behaviour
* Actual behaviour

Even better would be to provide a unit test like the ones that already exist for deployment structure:
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/branches/Branch_4_2/testsuite/src/main/org/jboss/test/deployers/
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/branches/Branch_4_2/testsuite/src/resources/deployers/
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/branches/Branch_4_2/testsuite/imports/sections/deployers.xml?view=log

> a jar file inside a jar file inside an ear file is deployed as not in the ear
> -----------------------------------------------------------------------------
>
>                 Key: JBAS-5106
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5106
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-4.2.2.GA
>         Environment: windows, jrockit
>            Reporter: David Cervigni
>
> esb3 sessions beans inside a jar inside a jar  (it was an error in my case but it was so) inside the main ear was deployed without the "ear name" prefix
> the archive was:
> ear file
>     ------>module.jar
>                        -------->nested.jar file
> the nested jar was deployed as it was outside the ear

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