Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10859

Schema validatation doesn't work in mtom enabled provider service

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.3.0.ER1
    • EAP_EWP 5.2.0
    • Web Services
    • None
    • Hide

      Send a message with an XOP element in it to a @WebServiceProvider endpoint with mtom-enabled and schema-validation-enabled set to true.

      Show
      Send a message with an XOP element in it to a @WebServiceProvider endpoint with mtom-enabled and schema-validation-enabled set to true .
    • Release Notes
    • Hide
      In previous versions of JBoss EAP 5, if a message with an XOP element was sent to a @WebServiceProider with mtom-enabled and schema-validation-enabled set to true, a validation error similar to following would be encountered:
      <screen>
      19:02:50,096 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-/127.0.0.1:8080-1) Interceptor for
      {http://provider.gss.redhat.com/}
      HelloWS#
      {http://provider.gss.redhat.com/}
      hello has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not parse the XML stream caused by: org.xml.sax.SAXParseException: cvc-type.3.1.2: Element 'file' is a simple type, so it must have no element information item [children]..
      </screen>

      This issue has been resolved in this release and schema validation works as expected.
      Show
      In previous versions of JBoss EAP 5, if a message with an XOP element was sent to a @WebServiceProider with mtom-enabled and schema-validation-enabled set to true, a validation error similar to following would be encountered: <screen> 19:02:50,096 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-/127.0.0.1:8080-1) Interceptor for { http://provider.gss.redhat.com/ } HelloWS# { http://provider.gss.redhat.com/ } hello has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not parse the XML stream caused by: org.xml.sax.SAXParseException: cvc-type.3.1.2: Element 'file' is a simple type, so it must have no element information item [children].. </screen> This issue has been resolved in this release and schema validation works as expected.
    • Documented as Resolved Issue
    • NEW

      19:02:50,096 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-/127.0.0.1:8080-1) Interceptor for

      {http://provider.gss.redhat.com/}

      HelloWS#

      {http://provider.gss.redhat.com/}

      hello has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not parse the XML stream caused by: org.xml.sax.SAXParseException: cvc-type.3.1.2: Element 'file' is a simple type, so it must have no element information item [children]..
      at org.apache.cxf.databinding.source.XMLStreamDataReader.read(XMLStreamDataReader.java:160)
      at org.apache.cxf.databinding.source.XMLStreamDataReader.read(XMLStreamDataReader.java:75)
      at org.apache.cxf.databinding.source.XMLStreamDataReader.read(XMLStreamDataReader.java:60)
      at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:203)
      at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:262)
      at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
      at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:237)

              rh-ee-klape Kyle Lape
              rh-ee-klape Kyle Lape
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: