/01/2009 09:48 -
Scott W Sinclair/JPMCHASE
15/01/2009 12:12
To
users@cxf.apache.org
cc
andrew.cl...@gmail.com, users@cxf.apache.org
Subject
Re: Entitlements in webservices
Hi Andrew,
Yes, manually controlling the WSDL is a great idea, I guess then I am
also moving to a more contract
@cxf.apache.org
cc
andrew.cl...@gmail.com, users@cxf.apache.org
Subject
Re: Entitlements in webservices
Hi Andrew,
Yes, manually controlling the WSDL is a great idea, I guess then I am
also moving to a more contract first approach :)
Thanks Regards,
Scott Sinclair
JP Morgan Chase
45, Waterloo
2009/1/15 scott.w.sincl...@jpmchase.com:
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
6HS
Scotland
Desk Phone : (+44)-141-228-5450 (direct)
e-mail : scott.w.sincl...@jpmchase.com
Andrew Clegg and...@nervechannel.com
Sent by: andrew.cl...@gmail.com
15/01/2009 11:49
Please respond to
users@cxf.apache.org
To
users@cxf.apache.org
cc
Subject
Re: Entitlements in webservices
Contract first is definitely the way to go, but you COULD try something like:
Create the SEI interface and types that it references JUST using the public
data.Create subclasses of all the types that add the extra fields for the
internal stuff.
Have an abstract impl that does most of the
