Hi Dan,
Thanks for your help as always - looks like upgrading to 2.0.3 & upgrading XMLSchema resolved this issue. The only issue I have with this now is with xsd:restriction - they are not annotated, not supported, so am forced to reference the wsdl, not big deal, this works I am however still having problems with the schema validation & mtom. Its faily obvious why its breaking, however I would thought that there could be some iffing about butting around the mtom (attachement in/out interceptor).. i.e. before mtom'ing perform schema validation if enabled, and them remove mark as being validated... Or is it designed to work this way? dkulp wrote: > > > Forgot to mention, 2.0.3 is being voted on now. You can download the > release candidate from: > http://people.apache.org/~dkulp/stage_cxf/2.0.3-incubator-take1/dist/ > > (That may fix your mtom validation issue as well, not really sure though) > > Dan > > > On Thursday 08 November 2007, Daniel Kulp wrote: >> On Thursday 08 November 2007, Adrian C wrote: >> > With jaxb if schema validation is turned on should validation work >> > if the wsld is not defined for the webservice? Am seeing errors when >> > I do this - I though that the schema/wsld could be generated from >> > the classes? >> >> In theory, it should. I'm not sure how well tested it is though. >> >> I'd love to see any test cases if there is an issue. Also, >> definitely try with 2.0.3. We upgraded to a newer version of >> XmlSchema to fix SOME issues where the schema was losing some needed >> information. (such as whether a base64 thing was mtom enabled or >> not). Thus, 2.0.3 may fix some of the isssues. > > > > -- > J. Daniel Kulp > Principal Engineer > IONA > P: 781-902-8727 C: 508-380-7194 > [EMAIL PROTECTED] > http://www.dankulp.com/blog > > -- View this message in context: http://www.nabble.com/schema-validation-tf4770643.html#a13666392 Sent from the cxf-user mailing list archive at Nabble.com.
