You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Raj Floyd <ra...@gmail.com> on 2011/03/16 10:13:30 UTC
wsdl2java: -impl option
Hi,
The tool wsdl2java -impl option generates the service implementation class.
The class has the mention of WSDL location through @WebService annotation.
My question is:
1. What is the advantage of specifying the WSDL location versus not
specifying as you can still get the WSDL upon publshing the service by
invoking http://....?wsdl URL
2. To my understanding, it seems WSDL is an abstract artifact and therefore
even if I have the existing WSDL, I still need to provide the implementation
business logic for my service generated from the said WSDL.
Thx
Raj
Re: wsdl2java: -impl option
Posted by Raj Floyd <ra...@gmail.com>.
Coming to my first question:
Does it mean the WSDL will be generated in that specified location with the
specified name?
Raj
On Wed, Mar 16, 2011 at 2:43 PM, Raj Floyd <ra...@gmail.com> wrote:
> Hi,
>
> The tool wsdl2java -impl option generates the service implementation class.
> The class has the mention of WSDL location through @WebService annotation.
> My question is:
>
> 1. What is the advantage of specifying the WSDL location versus not
> specifying as you can still get the WSDL upon publshing the service by
> invoking http://....?wsdl URL
>
> 2. To my understanding, it seems WSDL is an abstract artifact and therefore
> even if I have the existing WSDL, I still need to provide the implementation
> business logic for my service generated from the said WSDL.
>
> Thx
>
> Raj
>
>
>
>
Re: wsdl2java: -impl option
Posted by Raj Floyd <ra...@gmail.com>.
Thanks Dan.
On Wed, Mar 16, 2011 at 11:23 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Wednesday 16 March 2011 5:13:30 AM Raj Floyd wrote:
> > Hi,
> >
> > The tool wsdl2java -impl option generates the service implementation
> class.
> > The class has the mention of WSDL location through @WebService
> annotation.
> > My question is:
> >
> > 1. What is the advantage of specifying the WSDL location versus not
> > specifying as you can still get the WSDL upon publshing the service by
> > invoking http://....?wsdl URL
>
> If you specify the wsdlLocation, then at runtime, we can return the
> original
> WSDL (with slight modifications like the soap:address). Things like
> annotations and schemas and such can be maintained. Without the
> wsdlLocation, we have to generate a new WSDL at runtime which wouldn't have
> all of that.
>
> Also, if the WSDL has things like WS-Policy fragments in it, we'll need the
> WSDL at runtime to act on those policies.
>
>
> > 2. To my understanding, it seems WSDL is an abstract artifact and
> therefore
> > even if I have the existing WSDL, I still need to provide the
> > implementation business logic for my service generated from the said
> WSDL.
>
> Right.
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://dankulp.com/blog
> Talend - http://www.talend.com
>
Re: wsdl2java: -impl option
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday 16 March 2011 5:13:30 AM Raj Floyd wrote:
> Hi,
>
> The tool wsdl2java -impl option generates the service implementation class.
> The class has the mention of WSDL location through @WebService annotation.
> My question is:
>
> 1. What is the advantage of specifying the WSDL location versus not
> specifying as you can still get the WSDL upon publshing the service by
> invoking http://....?wsdl URL
If you specify the wsdlLocation, then at runtime, we can return the original
WSDL (with slight modifications like the soap:address). Things like
annotations and schemas and such can be maintained. Without the
wsdlLocation, we have to generate a new WSDL at runtime which wouldn't have
all of that.
Also, if the WSDL has things like WS-Policy fragments in it, we'll need the
WSDL at runtime to act on those policies.
> 2. To my understanding, it seems WSDL is an abstract artifact and therefore
> even if I have the existing WSDL, I still need to provide the
> implementation business logic for my service generated from the said WSDL.
Right.
--
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com