Re: [Axis2] soap:address location is no whats in the WSDL file...Help please
I currently don't have an axis2.xml. On a JBoss system, with a compressed WAR containing all the axis2 jars and files, where would be the best place to put one? I am thinking /conf with the rest of the config files. This way, when I get to an HA setup with multiple app servers, I can have appropriate settings in each if necessary. And, in case anyone else runs into this, I fixed my local dev box by adding this to my services.xml: false Its not a great long-term solution, as one would like to keep non- static configuration information out of a compiled WAR for portability, but its a quick-fix to get it working. On May 7, 2008, at 12:32 AM, Deepal Jayasinghe wrote: I have an interesting problem. I have an Axis2 service deployed with a WSDL file. The WSDL file has the following service tag: binding="ns1:BindpointServiceSOAP"> http://localhost:8080/"/> But, when I deploy it, the WSDL I get from the web server is: binding="ns1:BindpointServiceSOAP"> http://169.254.86.84:8080/bp_server/services/BindpointService "/> What's interesting is that this web service is deployed in JBoss, and that JBoss instance is set to bind, by default, to 127.0.0.1. What else is interesting is that the IP address that's appearing in the location URL is some ICANN address that doesn't even reply to a ping. Where is this coming from? How do I make Axis2 use my actual bind address? Just add the following parameter into axis2.xml. myhost.com -Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Michael Bauer [EMAIL PROTECTED] http://www.codechimp.net
Re: [Axis2] soap:address location is no whats in the WSDL file...Help please
I have an interesting problem. I have an Axis2 service deployed with a WSDL file. The WSDL file has the following service tag: binding="ns1:BindpointServiceSOAP"> http://localhost:8080/"/> But, when I deploy it, the WSDL I get from the web server is: location="http://169.254.86.84:8080/bp_server/services/BindpointService"/> What's interesting is that this web service is deployed in JBoss, and that JBoss instance is set to bind, by default, to 127.0.0.1. What else is interesting is that the IP address that's appearing in the location URL is some ICANN address that doesn't even reply to a ping. Where is this coming from? How do I make Axis2 use my actual bind address? Just add the following parameter into axis2.xml. myhost.com -Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] soap:address location is no whats in the WSDL file...Help please
I have an interesting problem. I have an Axis2 service deployed with a WSDL file. The WSDL file has the following service tag: binding="ns1:BindpointServiceSOAP"> http://localhost:8080/"/> But, when I deploy it, the WSDL I get from the web server is: binding="ns1:BindpointServiceSOAP"> http://169.254.86.84:8080/bp_server/services/BindpointService "/> What's interesting is that this web service is deployed in JBoss, and that JBoss instance is set to bind, by default, to 127.0.0.1. What else is interesting is that the IP address that's appearing in the location URL is some ICANN address that doesn't even reply to a ping. Where is this coming from? How do I make Axis2 use my actual bind address? Michael Bauer [EMAIL PROTECTED] http://www.codechimp.net
