Hi Srinath, Recently I tried doing this and ended up getting 8080 even if the port is changed, which forced me to switch back to passing the port number as a JVM property. Please make sure you test this with a port other than 8080.... Also let me know if it's working now :)...
thanks, Thilina On Wed, Dec 17, 2008 at 10:21 AM, Srinath Perera <[email protected]> wrote: > I did not see a way to get a TransportListener from config contex, > however, in the listener manager, there is something called getEPR > forService(), which I think will do the trick. Will try it and let you > know. > > Thanks deepal, Azeez !!! > > Srinath > > > On Wed, Dec 17, 2008 at 10:09 AM, Deepal jayasinghe <[email protected]> > wrote: > > Hi Srinath, > > > > Nice to see you asking a question in the list :) > > You can get the reply to address as follows > > - first get the configuration context > > - from that you can get something called TransportListener > > - from that you can ask for a reply to address. > > > > Thank you! > > Deepal > >> Hi All; > >> > >> Is there a way to find the current tomcat port using Axis2 (I need it > >> to set a replyto address)? Ideally I want to find the service port at > >> the start up, before any request arrived. If that does not work, I > >> might be able to live with getting it with message context. Does the > >> message context property TRANSPORT_ADDR give what I want to find? > >> > >> Thanks very much > >> Srinath > >> > >> > > > > > > -- > > Thank you! > > > > > > http://blogs.deepal.org > > http://deepal.org > > > > > > > > -- > ============================ > Srinath Perera: > Indiana University, Bloomington > http://www.cs.indiana.edu/~hperera/<http://www.cs.indiana.edu/%7Ehperera/> > http://www.bloglines.com/blog/hemapani > -- Thilina Gunarathne - http://thilinag.blogspot.com
