Mate, please forgive me for saying this, but thank god somebody else has
encountered the same problem. I thought it was my uncanny knack of
managing to break whatever release comes my way.
In my case, what I find curious is that the ant-task generates the wsdl
with out an error.
This is the ant task that I use:
<target name = "_java2wsdl" depends="project">
<axis-java2wsdl output = "${gen.dir}/HouseHold.wsdl"
classname = "com.soapaxisapi.HouseholdReceiver"
namespace = "urn:HouseHold"
location =
http://localhost:8080/household_ss2/published_services/HouseHold";>
<mapping namespace= "urn:HouseHold"
package = "com.soapaxisapi" />
</axis-java2wsdl>
<copy
todir="${web.root.services}" >
<fileset dir = "${gen.dir}"
includes = "**/*.wsdl" />
</copy>
</target>
The resulting Household.wsdl is the following:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="urn:HouseHold"
xmlns:impl="urn:HouseHold" xmlns:intf="urn:HouseHold"
xmlns:apachesoap="http://xml.apache.org/xml-soap";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>
<!--WSDL created by Apache Axis version: 1.2RC2
Built on Nov 16, 2004 (12:19:44 EST)-->
<wsdl:message name="getAnswerRequest">
</wsdl:message>
<wsdl:message name="getAnswerResponse">
<wsdl:part name="getAnswerReturn" type="xsd:string"/>
</wsdl:message>
<wsdl:portType name="HouseholdReceiver">
<wsdl:operation name="getAnswer">
<wsdl:input name="getAnswerRequest"
message="impl:getAnswerRequest"/>
<wsdl:output name="getAnswerResponse"
message="impl:getAnswerResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HouseHoldSoapBinding"
type="impl:HouseholdReceiver">
<wsdlsoap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="getAnswer">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="getAnswerRequest">
<wsdlsoap:body use="encoded"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:HouseHold"/>
</wsdl:input>
<wsdl:output name="getAnswerResponse">
<wsdlsoap:body use="encoded"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";
namespace="urn:HouseHold"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HouseholdReceiverService">
<wsdl:port name="HouseHold" binding="impl:HouseHoldSoapBinding">
<wsdlsoap:address
location="http://localhost:8080/household_ss2/published_services/HouseHo
ld"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
So, when I connect to the following address "
http://localhost:8080/household_ss2/published_services/HouseHold.wsdl";,
the wsdl is definitely there. This is the address that appears in the
binding stub. Is this the correct address that the client should connect
to? Is that why I am getting a 404? I mean the ant task produces the
stubs and so on for me with no problem.
I've been knocking my head off a brick wall over this one. I mean
jws?wsdl just is not robust enough. Please can anybody help?
Paul Thomas
-----Mensaje original-----
De: Michael Laccetti [mailto:[EMAIL PROTECTED]
Enviado el: s�bado, 05 de marzo de 2005 20:28
Para: [email protected]
Asunto: Axis + Tomcat 400 Error
Every time I try to use the AdminClient to deploy a service, list a
service,
etc, I get a 400 error.
The client returns the following:
Exception: AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (400)HTTP method POST is not supported by this URL
faultActor:
faultNode:
faultDetail:
{}:return code: 400
And the server spits out a standard 400 error message that the POST is
not
supported. Anybody know why, or how to fix this? I checked the list
archives,
and while this has cropped up before, there was no real explanation as
to how to
fix it.
Mike
