You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Stefan <sh...@hotmail.com> on 2011/03/14 15:02:29 UTC
confused by the import in a WSDL
Hello,
I use the tool wsdl2java to create a java bean. The WSDL file what I used
looks like this:
http://cxf.547215.n5.nabble.com/file/n3556334/notificationConsumerService.wsdl
notificationConsumerService.wsdl
In the option , I cann't understand the meaning of "....?wsdl=1".
Could you please give me some knowledges if you know about this, thanks~~
Stefan
--
View this message in context: http://cxf.547215.n5.nabble.com/confused-by-the-import-in-a-WSDL-tp3556334p3556334.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: confused by the import in a WSDL
Posted by Stefan <sh...@hotmail.com>.
thanks ,Daniel
--
View this message in context: http://cxf.547215.n5.nabble.com/confused-by-the-import-in-a-WSDL-tp3556334p3704613.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: confused by the import in a WSDL
Posted by Daniel Kulp <dk...@apache.org>.
On Monday 14 March 2011 10:02:29 AM Stefan wrote:
> Hello,
> I use the tool wsdl2java to create a java bean. The WSDL file what I used
> looks like this:
> http://cxf.547215.n5.nabble.com/file/n3556334/notificationConsumerService.w
> sdl notificationConsumerService.wsdl
> In the option , I cann't understand the meaning of "....?wsdl=1".
> Could you please give me some knowledges if you know about this, thanks~~
> Stefan
With java first, this will usually occurr when you specify different
targetNamespaces (or don't specify at all) in the @WebService annotations for
the SEI interface and the service impl. The easy fix is to make sure the
@WebService annotation on both specify the exact same targetNamespace.
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com
Re: confused by the import in a WSDL
Posted by Stefan <sh...@hotmail.com>.
hallo Benson,
Thanks for you reply.
I tried to open the address
http://localhost:8080/myfirstwebservice/notificationConsumerService?wsdl=1
,when the service is running, and what I can see is this xml file.
http://cxf.547215.n5.nabble.com/file/n3556448/notificationConsumerService.wsdl%3D1.xml
notificationConsumerService.wsdl%3D1.xml
--
View this message in context: http://cxf.547215.n5.nabble.com/confused-by-the-import-in-a-WSDL-tp3556334p3556448.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: confused by the import in a WSDL
Posted by Stefan <sh...@hotmail.com>.
Hello Benson,
I have an idea about the location =
"http://localhost:8080/myfirstwebservice/notificationConsumerService?wsdl=1".
I just think that under this endpoint I can find the wsdl file with
namespace="http://docs.oasis-open.org/wsn/bw-2". The important thing is the
namespace , not the location. Of cause I can modify the location =
"http://localhost:8080/myfirstwebservice/notificationConsumerService?wsdl=2",
have I right?
Thanks~~
Stefan
--
View this message in context: http://cxf.547215.n5.nabble.com/confused-by-the-import-in-a-WSDL-tp3556334p3556467.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: confused by the import in a WSDL
Posted by Benson Margulies <bi...@gmail.com>.
If your web service ends up splitting across multiple target
namespaces, it can't all be one XML document, and that import grabs
the 'second' namespace. I can't see through the URL you posted to
check in more detail.
On Mon, Mar 14, 2011 at 10:02 AM, Stefan <sh...@hotmail.com> wrote:
> Hello,
> I use the tool wsdl2java to create a java bean. The WSDL file what I used
> looks like this:
> http://cxf.547215.n5.nabble.com/file/n3556334/notificationConsumerService.wsdl
> notificationConsumerService.wsdl
> In the option , I cann't understand the meaning of "....?wsdl=1".
> Could you please give me some knowledges if you know about this, thanks~~
> Stefan
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/confused-by-the-import-in-a-WSDL-tp3556334p3556334.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>