AW: AW: AW: Missing Method/Opeartion Parameters in WSDL
Hi Daniel, thank you very much for your answer! I added the targetNamespace (http://repurchaseresellnoreturn.xyz) annotation within the interface (package xyz.RepurchaseResellNoReturnRequester) and the implementation class (package xyz.RepurchaseResellNoReturnRequester.impl), but I still got the split WSDL. However this is OK for me... I just wanted to understand. Greetings André -Ursprüngliche Nachricht- Von: Daniel Kulp [mailto:dk...@apache.org] Gesendet: Mittwoch, 28. September 2011 16:17 An: users@cxf.apache.org Cc: Janus, Andre Betreff: Re: AW: AW: Missing Method/Opeartion Parameters in WSDL It has to do with the namespaces. The @WebService annotation on the "impl" class likely either doesn't have a targetNamespace attribute (in which case it will derive from the package name for the impl) or it's different than the targetNamespace for the SEI interface.Thus, the WSDL get's "split" with the stuff from the SEI going into one (the portType and messages and such) and the stuff from the service impl (binding and service) going into the other. This is correct per jaxws spec. The easy "fix" is to add a targetNamespace attribute to the @WebService annotation to make it match the SEI. Dan On Wednesday, September 28, 2011 1:50:52 PM andre.ja...@t-systems.com wrote: > Hi Freeman, > > thank you very much!!! > > After using http://x.x.x.x/xyz/services/RepurchaseResellNoReturnRequester? > wsdl=RepurchaseResellNoReturnRequester.wsdl instead of > http://x.x.x.x/xyz/services/ RepurchaseResellNoReturnRequester?wsdl I got > the complete WSDL. > > I thought the "?wsdl" after the Service name is enough to get the > complete WSDL. Why do I get only the binding part? That is diffenrent > to the XFire behaviour or different to many other Web Services I know. > However...with the other URL I got the complete WSDL and that´s wat I need. > Thanks again! > > Greetings > André > > -Ursprüngliche Nachricht- > Von: Freeman Fang [mailto:freeman.f...@gmail.com] > Gesendet: Mittwoch, 28. September 2011 12:17 > An: users@cxf.apache.org > Betreff: Re: AW: Missing Method/Opeartion Parameters in WSDL > > No, it's not the complete wsdl, there must be wsdl:types and > wsdl:messages and wsdl:portType in location="http://x.x.x.x/xyz/services/ > RepurchaseResellNoReturnRequester? > wsdl=RepurchaseResellNoReturnRequester.wsdl" > namespace="http://repurchaseresellnoreturn.xyz.de/ "> > You can find your parameters from wsdl:types. > > Freeman > On 2011-9-28, at 下午5:49, > wrote: > > > Hello Freeman, > > > > > > > > here´s the complete WSDL: > > > > > > > > > name="RepurchaseResellNoReturnRequester" > > targetNamespace="http://www.springframework.org/schema/beans > > " xmlns:ns1="http://repurchaseresellnoreturn.xyz.de/"; > > xmlns:ns3="http://schemas.xmlsoap.org/soap/http > > " xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > xmlns:tns="http://www.springframework.org/schema/beans > > " xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema > > "> > > > > http://x.x.x.x/xyz/services/ > > > > RepurchaseResellNoReturnRequester? > > wsdl=RepurchaseResellNoReturnRequester.wsdl" > > namespace="http://repurchaseresellnoreturn.xyz.de/ > > "> > > > > > > > > > > > type="ns1:RepurchaseResellNoReturnRequester"> > > > > > > > transport="http://schemas.xmlsoap.org/soap/http > > "/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
AW: AW: Missing Method/Opeartion Parameters in WSDL
Hi Freeman, thank you very much!!! After using http://x.x.x.x/xyz/services/RepurchaseResellNoReturnRequester? wsdl=RepurchaseResellNoReturnRequester.wsdl instead of http://x.x.x.x/xyz/services/ RepurchaseResellNoReturnRequester?wsdl I got the complete WSDL. I thought the "?wsdl" after the Service name is enough to get the complete WSDL. Why do I get only the binding part? That is diffenrent to the XFire behaviour or different to many other Web Services I know. However...with the other URL I got the complete WSDL and that´s wat I need. Thanks again! Greetings André -Ursprüngliche Nachricht- Von: Freeman Fang [mailto:freeman.f...@gmail.com] Gesendet: Mittwoch, 28. September 2011 12:17 An: users@cxf.apache.org Betreff: Re: AW: Missing Method/Opeartion Parameters in WSDL No, it's not the complete wsdl, there must be wsdl:types and wsdl:messages and wsdl:portType in http://x.x.x.x/xyz/services/ RepurchaseResellNoReturnRequester? wsdl=RepurchaseResellNoReturnRequester.wsdl" namespace="http://repurchaseresellnoreturn.xyz.de/ "> You can find your parameters from wsdl:types. Freeman On 2011-9-28, at 下午5:49, wrote: > Hello Freeman, > > here´s the complete WSDL: > > name="RepurchaseResellNoReturnRequester" > targetNamespace="http://www.springframework.org/schema/beans > " xmlns:ns1="http://repurchaseresellnoreturn.xyz.de/"; > xmlns:ns3="http://schemas.xmlsoap.org/soap/http > " xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:tns="http://www.springframework.org/schema/beans > " xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema > "> > http://x.x.x.x/xyz/services/ > RepurchaseResellNoReturnRequester? > wsdl=RepurchaseResellNoReturnRequester.wsdl" > namespace="http://repurchaseresellnoreturn.xyz.de/ > "> > > type="ns1:RepurchaseResellNoReturnRequester"> > transport="http://schemas.xmlsoap.org/soap/http > "/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > binding="tns:RepurchaseResellNoReturnRequesterSoapBinding" > name="RepurchaseResellNoReturnRequesterImplPort"> > http://x.x.x.x/xyz/services/ > RepurchaseResellNoReturnRequester"/> > > > > > -Ursprüngliche Nachricht- > Von: Freeman Fang [mailto:freeman.f...@gmail.com] > Gesendet: Mittwoch, 28. September 2011 11:35 > An: users@cxf.apache.org > Betreff: Re: Missing Method/Opeartion Parameters in WSDL > > Hi, > > I can't see the operations parameters are missing, what you pasted > here is only the binding part. > I believe you can find all your parameters from http://x.x.x.x/xyz/ > services/RepurchaseResellNoReturnRequester? > wsdl=RepurchaseResellNoReturnRequester.wsdl where should have schema > and message part. > > Freeman > On 2011-9-28, at 下午4:17, > wrote: > >> Hi, >> >> I got a question regarding the WSDL generated by CXF: >> >> Using a Java-first approach I want to use the generated WSDL >> (availabe under .../services/...?wsdl) to give third-party systems an >> description of my web service methods. But the WSDL looks very poor, >> because the Method/Operation Parameters are missing: >> >> > targetNamespace="http://www.springframework.org/schema/beans";
AW: Missing Method/Opeartion Parameters in WSDL
Hello Freeman, here´s the complete WSDL: http://www.springframework.org/schema/beans"; xmlns:ns1="http://repurchaseresellnoreturn.xyz.de/"; xmlns:ns3="http://schemas.xmlsoap.org/soap/http"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:tns="http://www.springframework.org/schema/beans"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://x.x.x.x/xyz/services/RepurchaseResellNoReturnRequester?wsdl=RepurchaseResellNoReturnRequester.wsdl"; namespace="http://repurchaseresellnoreturn.xyz.de/";> http://schemas.xmlsoap.org/soap/http"/> http://x.x.x.x/xyz/services/RepurchaseResellNoReturnRequester"/> -Ursprüngliche Nachricht- Von: Freeman Fang [mailto:freeman.f...@gmail.com] Gesendet: Mittwoch, 28. September 2011 11:35 An: users@cxf.apache.org Betreff: Re: Missing Method/Opeartion Parameters in WSDL Hi, I can't see the operations parameters are missing, what you pasted here is only the binding part. I believe you can find all your parameters from http://x.x.x.x/xyz/ services/RepurchaseResellNoReturnRequester? wsdl=RepurchaseResellNoReturnRequester.wsdl where should have schema and message part. Freeman On 2011-9-28, at 下午4:17, wrote: > Hi, > > I got a question regarding the WSDL generated by CXF: > > Using a Java-first approach I want to use the generated WSDL (availabe > under .../services/...?wsdl) to give third-party systems an > description of my web service methods. But the WSDL looks very poor, > because the Method/Operation Parameters are missing: > > targetNamespace="http://www.springframework.org/schema/beans";> >http://x.x.x.x/xyz/services/ > RepurchaseResellNoReturnRequester? > wsdl=RepurchaseResellNoReturnRequester.wsdl" > namespace="http://repurchaseresellnoreturn.xyz.de/ > "> > > name="RepurchaseResellNoReturnRequesterSoapBinding" > type="ns1:RepurchaseResellNoReturnRequester"> > transport="http://schemas.xmlsoap.org/soap/http > "/> > > style="document"/> > > use="literal"/> > > name="resell1Response"> > use="literal"/> > > [...] > > Here is the Java Source: > > @WebService > public interface RepurchaseResellNoReturnRequester > > [...] > > @WebResult(name = "out", targetNamespace = "") >@RequestWrapper(localName = "resell1", targetNamespace = > "http://repurchaseresellnoreturn.xyz.de > ") >@WebMethod(operationName = "resell1") >@ResponseWrapper(localName = "resell1", targetNamespace = > "http://repurchaseresellnoreturn.xyz.de > ") >VORepurchaseResellNoReturnTransferContainer resell(@WebParam(name = > "in0", targetNamespace = "") String fileNumber, >@WebParam(name = "in1", targetNamespace = "") Date > salesDate, >@WebParam(name = "in2", targetNamespace = "") BigDecimal > salesPrice, >@WebParam(name = "in3", targetNamespace = "") String > resellingCenter, >@WebParam(name = "in4", targ
Missing Method/Opeartion Parameters in WSDL
Hi, I got a question regarding the WSDL generated by CXF: Using a Java-first approach I want to use the generated WSDL (availabe under .../services/...?wsdl) to give third-party systems an description of my web service methods. But the WSDL looks very poor, because the Method/Operation Parameters are missing: http://www.springframework.org/schema/beans";> http://x.x.x.x/xyz/services/RepurchaseResellNoReturnRequester?wsdl=RepurchaseResellNoReturnRequester.wsdl"; namespace="http://repurchaseresellnoreturn.xyz.de/";> http://schemas.xmlsoap.org/soap/http"/> [...] Here is the Java Source: @WebService public interface RepurchaseResellNoReturnRequester [...] @WebResult(name = "out", targetNamespace = "") @RequestWrapper(localName = "resell1", targetNamespace = "http://repurchaseresellnoreturn.xyz.de";) @WebMethod(operationName = "resell1") @ResponseWrapper(localName = "resell1", targetNamespace = "http://repurchaseresellnoreturn.xyz.de";) VORepurchaseResellNoReturnTransferContainer resell(@WebParam(name = "in0", targetNamespace = "") String fileNumber, @WebParam(name = "in1", targetNamespace = "") Date salesDate, @WebParam(name = "in2", targetNamespace = "") BigDecimal salesPrice, @WebParam(name = "in3", targetNamespace = "") String resellingCenter, @WebParam(name = "in4", targetNamespace = "") String centerIdType, @WebParam(name = "in5", targetNamespace = "") String sourceSystem); And here is a part of the services.xml: Has anyone an idea, what I can do? I previouisly used XFire for the same Source and got an WSDL with definitions of all Parameters. Thanks in advance! André
