- 
        1. Re: JBoss returns incorrect ear exploded directory name: Pledarranl Sep 16, 2004 2:51 PM (in response to ranjithpillai)You asked this question in this forum on the 14th September, why are you asking it again? 
- 
        2. Re: JBoss returns incorrect ear exploded directory name: Pleranjithpillai Sep 16, 2004 3:35 PM (in response to ranjithpillai)Hello, 
 Unfortunately I didn't get any help. This is a showstopper now. I am sure I am not the first one deploying an ear in Jboss application server and trying to obtain a URL based on application context. So I thought if I explain it further and repost, that may get more attention.
 Thanks,
 Ranjith Pillai
- 
        3. Re: JBoss returns incorrect ear exploded directory name: Plekabirkhan Sep 16, 2004 4:09 PM (in response to ranjithpillai)If you do: 
 Enumeration e = Thread.currentThread().getContextClassLoader().getResources()
 and enumerate, do you get what you need?
- 
        4. Re: JBoss returns incorrect ear exploded directory name: Pleranjithpillai Sep 16, 2004 5:58 PM (in response to ranjithpillai)Hello, 
 I tried that and the problem still exists. This call returns ..
 17:37:17,703 INFO [STDOUT] Path under enumeration->
 file:/opt/websat/jboss/jboss-3.2.5/server/tux610/tmp/deploy/
 tmp52975application.ear!/ssa/config/tux610/ssa-config.xml
 If you notice the exploded ear directory name is given as "tmp52975application.ear!" . Actually the correct name is tmp52975application.ear-contents.
 Also I am wondering why did it return the protocol "file:/" in front of URL.
 Any help will be deeply appreciated.
 Thanks,
 Ranjith Pillai
- 
        5. Re: JBoss returns incorrect ear exploded directory name: Plestarksm64 Sep 16, 2004 6:15 PM (in response to ranjithpillai)Open a bug report on sourceforge with an example to speed up the resolution. 
 http://sourceforge.net/tracker/?group_id=22866&atid=376685
- 
        6. Re: JBoss returns incorrect ear exploded directory name: Pleranjithpillai Sep 17, 2004 10:51 AM (in response to ranjithpillai)Hello, 
 Created a bug report in the given address and id is 1029905
 Thanks,
 Ranjith Pillai
 
     
     
    