> No, that code again go and call listenerManager.getEPRforService(..), > which I was using. I walked through the code, and > listenerManager.getEPRforService(..) work fine with other transports, > but with tomcat, it reads the port off the first request. When in > doubt (before the request arrives) it give 8080, which is the case > thilina was complaining . > I think that is the intended behavior, because the same code should work for both client side and the server side. > For my usecase, I can not wait for the first request as what I am > developing is a management agent. for now, I wrote a code to parse > tomcat server.xml. > Well, what you are doing is ok, iff you are going to use your application in tomcat. A better approach would be either feed the port number using axis2.xml or web.xml
Deepal
