[
https://issues.apache.org/jira/browse/CXF-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982194#action_12982194
]
Freeman Fang commented on CXF-3233:
-----------------------------------
Generate java code from wsdl is build time action, it doesn't mean will build
servicemodule from wsdl during runtime.
Did you check logs for your client side?
You should see the output like
org.apache.cxf.service.factory.ReflectionServiceFactoryBean buildServiceFromWSDL
or
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromClass
which will tell you how the servicemodel build.
No, I didn't test it on WebLogic 10.0 or WebSphere 6.1, I don't have those j2ee
container at hand and I don't think it's a j2ee container specific problem.
How you use client side code? And how you specify wsdlLocation annotation?
If you can append a runnable testcase, I believe it would be very helpful to
figure things out.
> 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 10.0, WebSphere 6.1
> 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.
