cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Neward" <...@tedneward.com>
Subject RE: Generated code from WSDL
Date Sat, 17 Mar 2007 07:49:32 GMT
I'd like to suggest that this behavior be changed; given WSDL's (mistaken)
decision to include physical service endpoint information in a WSDL
document, lots of people[1] are breaking WSDL documents up into two parts,
one containing the "interface" definitions by which to generate the proxy
APIs, and the other containing the physical service definitions that can be
swapped in & out as necessary to represent actual physical addresses (for
easier movement between testing & production, for example).

I understand that the tool now uses the service builder, but frankly, if the
cost of doing this is the loss of this kind of codegen scenario, then it's a
bad refactoring and should be backed out.

<warning type='criticism' goal='constructive' style='tough-love'>
And FWIW, answers of "We did it this way deliberately" are not really
answers to questions. At the least, the answers should include "why" it was
done that way, and what the thought process was when the decision was made
to throw away functionality from previous versions. So no, IMHO, the below
*didn't* answer the question.
</warning>

Ted Neward
Java, .NET, XML Services
Consulting, Teaching, Speaking, Writing
http://www.tedneward.com

> -----Original Message-----
> From: James Mao [mailto:james.mao@iona.com]
> Sent: Friday, March 16, 2007 3:58 AM
> To: cxf-user@incubator.apache.org
> Subject: Re: Generated code from WSDL
> 
> Hi Fred,
> 
> In JAX-WS RI, if you feed a wsdl which contains no physical contract, it
> will give you, and generate no code at all
> "warning: WSDL document does not define any services"
> 
> However in CXF, previously we can generate the SEI, type code(generated
> from schema in wsdl by delegating to jaxb2),  and no Service
> Code/Client/Server main line code will be generated.
> 
> Now, after refactoring, it's impossible for wsdlto tool to generate any
> code from a wsdl missing service definition, because we reuse the
> service builder in rt/core which has to start from the service defined
> in wsdl.
> 
> Hope this answered your question.
> 
> Regards,
> James.
> >
> > I posted this to the IRC channel, but didn't hear a response.  Anyone
> > know?
> >
> > Anyone know off-hand if JAX-WS *requires* that a WSDL document have a
> > physical contract (binding and service definitions) in order to render
> > usably generated code?  In other words, is there a way for me to
> > instantiate a proxy/stub/whateveryoucallit from code I've generated
> > that does not contain any such physical contract?
> >
> > (I find that all I get are interfaces, if I omit the physical parts of
> > the contract)
> >
> > I was under the (obviously mistaken) impression that the codegen stuff
> > can be done in the absence of a physical description, but obviously
> > that was hopelessly naive of me... :)
> >
> 
> 
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.11/722 - Release Date: 3/14/2007
> 3:38 PM
> 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.11/722 - Release Date: 3/14/2007
3:38 PM
 


Mime
View raw message