Namespace seems to be different.
xmlns:tns="http://servicemix.apache.org/samples/ServiceManagerAssembly";
xmlns:NSR="http://servicemix.apache.org/servicemanagerassembly";
Though if this is the problem, I'm kinda surprised the http bc was able to find
the jsr181 su. Maybe its something else.
Benamin wrote:
They are already the same. Any other ideas? Here is the wsdl:
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Rev: 356052 $ $Date: 2005-12-11 14:41:20 -0800 (dim., 11 dc. 2005) $
-->
<wsdl:definitions name="ServiceManagerAssembly"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:tns="http://servicemix.apache.org/samples/ServiceManagerAssembly";
xmlns:typens="http://servicemix.apache.org/samples/ServiceManagerAssembly/types";
targetNamespace="http://servicemix.apache.org/samples/ServiceManagerAssembly";>
<wsdl:types>
<xsd:schema
targetNamespace="http://servicemix.apache.org/samples/ServiceManagerAssembly/types";
elementFormDefault="qualified">
<xsd:element name="GetNSR">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="request"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="GetNSRResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="response"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="UnknownNSRFault">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="request"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
<wsdl:message name="GetNSRRequest">
<wsdl:part name="payload" element="typens:GetNSR"/>
</wsdl:message>
<wsdl:message name="GetNSRResponse">
<wsdl:part name="payload" element="typens:GetNSRResponse"/>
</wsdl:message>
<wsdl:message name="UnknownNSRFault">
<wsdl:part name="payload" element="typens:UnknownNSRFault"/>
</wsdl:message>
<wsdl:portType name="NSR">
<wsdl:operation name="GetNSR">
<wsdl:input message="tns:GetNSRRequest"/>
<wsdl:output message="tns:GetNSRResponse"/>
<wsdl:fault name="UnknownNSR"
message="tns:UnknownNSRFault"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="NSRSOAPBinding" type="tns:NSR">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"; />
<wsdl:operation name="GetNSR">
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
<wsdl:fault name="UnknownNSR">
<soap:fault use="literal" name="UnknownNSR" />
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="NSRService">
<wsdl:port binding="tns:NSRSOAPBinding" name="soap">
<soap:address location="http://localhost:8192/NSRService/"; />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Adrian Co wrote:
try changing the endpoint attribute in the http xbean.xml to match the
port name of the wsdl
Benamin wrote:
That didn't work either. Same result.
pgodot wrote:
Try http://localhost:8192/NSRService/?wsdl
-----Original Message-----
From: Benamin [mailto:[EMAIL PROTECTED]
Sent: jeudi, 10. mai 2007 17:00
To: [email protected]
Subject: jsr problems
I am trying to expose a web service called NSRService such as in the
wsdl-first example. When I browse to
http://localhost:8192/NSRService/main.wsdl, it doesn't display the wsdl.
Any ideas on why it might not be able to find it? I will list my xbeans
for
jsr and http below:
<beans xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0";>
<classpath>
<location>.</location>
</classpath>
<jsr181:endpoint
pojoClass="org.apache.servicemix.samples.servicemanagerassembly.NSRImpl"
wsdlResource="classpath:externalsystem.wsdl"
style="document" />
</beans>
<beans xmlns:http="http://servicemix.apache.org/http/1.0";
xmlns:NSR="http://servicemix.apache.org/servicemanagerassembly";>
<http:endpoint service="NSR:NSRService"
endpoint="soap"
role="consumer"
locationURI="http://localhost:8192/NSRService/";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
soap="true"
soapAction="getNSR" />
</beans>
