cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Shults (JIRA)" <j...@apache.org>
Subject [jira] Created: (CXF-3233) JAXB xsd validation working on incoming messages but not outgoing messages
Date Thu, 06 Jan 2011 17:08:45 GMT
JAXB xsd validation working on incoming messages but not outgoing messages
--------------------------------------------------------------------------

                 Key: CXF-3233
                 URL: https://issues.apache.org/jira/browse/CXF-3233
             Project: CXF
          Issue Type: Bug
          Components: Bus
    Affects Versions: 2.3.1
         Environment: webLogic
            Reporter: Benjamin Shults


Using CXF 2.3.1.

Generated Java from WSDLs using JAXB.

Using 

    <jaxws:properties>
        <entry key="schema-validation-enabled" value="true" />
    </jaxws:properties>

in the client configuration.

My test creates an object that fails this particular requirement of the WSDL:

    <xsd:simpleType name="UUID.Content">
        <xsd:annotation>
            <xsd:documentation xml:lang="EN">
                Universally Unique Identifier
                </xsd:documentation>
        </xsd:annotation>
        <xsd:restriction base="xsd:token">
            <xsd:length value="36" />
            <xsd:pattern
                value="[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}"
/>
        </xsd:restriction>
    </xsd:simpleType>

However, the message is marshalled and makes it all the way through the outgoing interceptor
chain.

The WSDL is one-way: input-only.

wsdlLocation is specified in an annotation in the Impls.

Interestingly, incoming messages that fail validation of this same constraint are blocked
by the interceptor chain during unmarshalling.

I'm testing on WebLogic.  I could also test on WebSphere is needed.

Other XSD validation failures (such as a missing required element) are being caught by the
outgoing marshaller.

The reason that we upgraded to 2.3.1 from 2.2.6 was that we were seeing similar issues on
the inbound messages.  In 2.3.1, complete XSD validation occurs for inbound messages but not
for outbound ones.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message