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 <server>/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:
<parameter name="modifyUserWSDLPortAddress">false</parameter>
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:
<wsdl:service name="BindpointService">
<wsdl:port name="BindpointServiceSOAP"
binding="ns1:BindpointServiceSOAP">
<soap:address location="http://localhost:8080/"/>
</wsdl:port>
</wsdl:service>
But, when I deploy it, the WSDL I get from the web server is:
<wsdl:service name="BindpointService">
<wsdl:port name="BindpointServiceSOAP"
binding="ns1:BindpointServiceSOAP">
<soap:address location="http://169.254.86.84:8080/bp_server/services/BindpointService
"/>
</wsdl:port>
</wsdl:service>
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.
<parameter name="hostname" locked="true">myhost.com</parameter>
-Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Michael Bauer
[EMAIL PROTECTED]
http://www.codechimp.net
