[
https://issues.apache.org/jira/browse/CXF-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979667#action_12979667
]
Benjamin Shults edited comment on CXF-3233 at 1/10/11 1:38 PM:
---------------------------------------------------------------
I discovered that weblogic uses weblogic.apache.xerces.parsers.SAXParser
instead of org.apache.xerces.parsers.SAXParser. I'll test whether forcing
weblogic to use the apache class fixes this.
EDIT: it did not fix this issue. However, forcing weblogic to use
org.apache.xerces.parsers.SAXParser does fix validation using Spring Framework
classes... not relevant to this bug, though.
was (Author: benjishults):
I discovered that weblogic uses weblogic.apache.xerces.parsers.SAXParser
instead of org.apache.xerces.parsers.SAXParser. I'll test whether forcing
weblogic to use the apache class fixes this.
> 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
> Assignee: Freeman Fang
> Fix For: NeedMoreInfo
>
>
> 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.
