Schema Validation Error
When I try to add the following to my beans.xml file to validate the schema I get the following error. beans.xml: Error: Nov 17, 2007 4:25:23 PM org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.binding.soap.SoapFault: "null" is not a valid SOAP version. at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMes sage(ReadHeadersInterceptor.java:90) at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMes sage(ReadHeadersInterceptor.java:56) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorC hain.java:207) at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:402) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResp onse(HTTPConduit.java:1948) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTP Conduit.java:1791) at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66) at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:575) at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingI nterceptor.handleMessage(MessageSenderInterceptor.java:62) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorC hain.java:207) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:254) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:205) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:135) at $Proxy39.isSSEntitled(Unknown Source) at com.avaya.tsd.safe.ws.test.TestSvoService.testIsSSEntitled(TestSvoServic e.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUn it3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.ja va:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe stRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe stRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRun ner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRu nner.java:196) Obviously it doesn't like something in my Schema/XSD but what's this about "valid SOAP version"? If I take this validation out of the beans.xml it works fine. Any ideas what's going on? Thanks, David
Re: schema validation
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-8727C: 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.
Re: schema validation
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-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: schema validation
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-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
schema validation & mtom
Am am getting schema validation erros when I have mtom enabled for my service. Is the default ordering of the interceptors wrong? Can I change the ordering? 08-Nov-2007 15:18:45 org.apache.cxf.ws.addressing.soap.MAPCodec encodeAsExposed INFO: To : http://www.w3.org/2005/08/addressing/anonymous 08-Nov-2007 15:18:45 org.apache.cxf.ws.addressing.soap.MAPCodec encodeAsExposed INFO: RelatesTo : urn:uuid:32472e5d-de97-41e7-9355-bc3d2febda5a 08-Nov-2007 15:18:45 org.apache.cxf.ws.addressing.soap.MAPCodec encodeAsExposed INFO: Action : http://www.xxyyzz.com/ws/de/IdentityManagement/GetIdentity 08-Nov-2007 15:18:45 org.apache.cxf.phase.PhaseInterceptorChain doIntercept INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault: Marshalling Error: cvc-type.3.1.2: Element 'Data' is a simple type, so it must have no element information item [children]. at org.apache.cxf.jaxb.JAXBEncoderDecoder.marshall(JAXBEncoderDecoder.java:179) at org.apache.cxf.jaxb.io.DataWriterImpl.write(DataWriterImpl.java:42) at org.apache.cxf.interceptor.AbstractOutDatabindingInterceptor.writeParts(AbstractOutDatabindingInterceptor.java:84) at org.apache.cxf.interceptor.BareOutInterceptor.handleMessage(BareOutInterceptor.java:68) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207) at org.apache.cxf.interceptor.OutgoingChainInterceptor.handleMessage(OutgoingChainInterceptor.java:74) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:73) at org.apache.cxf.transport.servlet.ServletDestination.doMessage(ServletDestination.java:79) at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:235) at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:140) at org.apache.cxf.transport.servlet.CXFServlet.invoke(CXFServlet.java:278) at org.apache.cxf.transport.servlet.CXFServlet.doPost(CXFServlet.java:256) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xxyyzz.de.ws.xfire.core.filter.AuditFilterBean.doFilter(AuditFilterBean.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:107) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy12.doFilter(Unknown Source) at com.xxyyzz.de.ws.xfire.core.filter.AuditingFilter.doFilter(AuditingFilter.java:67) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRu
schema validation
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? -- View this message in context: http://www.nabble.com/schema-validation-tf4770643.html#a13646130 Sent from the cxf-user mailing list archive at Nabble.com.
