All I can see right now, certainly not the answer you'd like, is to
switch to a WSDL (contract)-first web service, i.e., deploy your web
service Java-first as you presently have it, grab the WSDL from the
browser, and use that to create a WSDL-first web service[1][2].
Contract-first development is not a bad way to go anyway[3]. But
perhaps someone else can think of a solution for you that will allow you
to remain Java-first.
Glen
[1] http://www.jroller.com/gmazza/entry/web_service_tutorial
[2]
http://cxf.apache.org/docs/defining-contract-first-webservices-with-wsdl-generation-from-java.html
[3]
http://static.springsource.org/spring-ws/site/reference/html/why-contract-first.html
On 07/30/2012 02:27 PM, Alejandro wrote:
I'm using javax.xml.bind.annotation.Facets (@Facets) to put restrictions,
ranges, lengths, etc. So my xsd inside the wsdl have all this stuff.
Regards.
Alejandro
--
View this message in context:
http://cxf.547215.n5.nabble.com/SchemaValidation-tp5711721p5711727.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza
