2009/1/15  <[email protected]>:
>
> I think a cooler way would be to have different WSDL generated, so the
> client stubs don't even have the fields in their generated classes.  But
> how can I make one interface publish 2 different WSDLs and is there a way
> to autogenerate the WSDLs (as I am doing), but perform some kind of
> filtering on how the POJOs are published to WSDL?

PS there are good arguments for working WSDL-first, especially when
you're supporting external clients whose code you have no control
over.

http://static.springframework.org/spring-ws/sites/1.5/reference/html/why-contract-first.html

Andrew.

-- 
New site launched: http://biotext.org.uk/

I am retiring my old email addresses.
Please use [email protected] where firstname = andrew.

Reply via email to