Yes, but EPR is a better way to get the info from rather than hacking
around message context properties.
Srinath, FYI, see:
http://svn.apache.org/viewvc/webservices/commons/trunk/modules/transport/modules/http/src/org/apache/axis2/transport/http/ListingAgent.java?view=markup
extractHostAndPort is what pulls the host and port from the request URI.
In particular, ServiceContext.getMyEPR() was implemented *exactly* for the
purpose of setting a replyTo address in WS-Addressing.
Sanjiva.
Deepal Jayasinghe wrote:
In Srinth's case there is no issue since he gets the request first, and
message context has everything he needs. And even he can construct the
reply to address from the TO address.
Deepal
Srinath, doesn't ServiceContext.getMyEPR() give you the info you need?
Sanjiva.
Srinath Perera wrote:
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
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
Blog: http://sanjiva.weerawarana.org/
