Hello,
Created a bug report in the given address and id is 1029905
Thanks,
Ranjith Pillai
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3848588#3848588
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3848588
You asked this question in this forum on the 14th September, why are you asking it
again?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3848488#3848488
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3848488
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,
If you do:
Enumeration e = Thread.currentThread().getContextClassLoader().getResources()
and enumerate, do you get what you need?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3848494#3848494
Reply to the post :
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
Open a bug report on sourceforge with an example to speed up the resolution.
http://sourceforge.net/tracker/?group_id=22866atid=376685
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3848513#3848513
Reply to the post :
