cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Leamon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-3095) Jax WS - Schema validation fails after 5th request
Date Thu, 28 Oct 2010 00:06:19 GMT

    [ https://issues.apache.org/jira/browse/CXF-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925609#action_12925609
] 

Patrick Leamon commented on CXF-3095:
-------------------------------------

I think I've figured out the difference.  In 2.0.11 the provided schema's (via schemaLocations)
were being used as base schemas.  In 2.2.10 and 2.2.11 it is using schemas generated from
the jaxb classes and javax.jws annotated classes only.

Looking at the wsdl, these are slightly different.  The xsd's we have are something like:
{code:xml}
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://example.com/location-service"
xmlns:com="http://example.com/common-types" xmlns:util="http://example.com/location-types"
attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://example.com/location-service">
    <xs:annotation>
        <xs:documentation>
				Bare Elements
			</xs:documentation>
    </xs:annotation>
    <xs:import namespace="http://example.com/common-types"/>
    <xs:import namespace="http://example.com/location-types"/>

    <xs:element name="serviceFault" type="com:ServiceFault"/>
    .... etc ....
{code}

So our wsdl in 2.0.11 has this included.  In 2.2.10 + 2.2.11 this seems to be ignored and
we get something like this:
{code:xml}
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ns0="http://example.com/common-types"
xmlns:ns1="http://example.com/location-types" attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://example.com/location-service">
    <xs:import namespace="http://example.com/location-types"/>

    <xs:element name="serviceFault" type="ns0:ServiceFault"/>
    .... etc ....
{code}

instead.  Note that in the schema for 'http://example.com/location-types' there is an import
for 'http://example.com/common-types'

Why the change?  Is this related to the problem I'm seeing or just a side effect.

> Jax WS - Schema validation fails after 5th request
> --------------------------------------------------
>
>                 Key: CXF-3095
>                 URL: https://issues.apache.org/jira/browse/CXF-3095
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.2.10
>         Environment: running in tomcat 6
>            Reporter: Patrick Leamon
>
> I'm having very odd schema validation issues since moving from cxf 2.0.11 to cxf 2.2.10.
> The beans.xml I'm using to configure the web service looks something like:
> {code:xml}
>     <jaxws:endpoint id="LocationServiceId"
>                     implementor="com.blah.LocationServiceImpl"
>                     address="/services/location">
>         <jaxws:properties>
>             <entry key="schema-validation-enabled" value="true" />
>         </jaxws:properties>
>         <jaxws:schemaLocations>
>             <jaxws:schemaLocation>classpath:xsd/common-types.xsd</jaxws:schemaLocation>
>             <jaxws:schemaLocation>classpath:xsd/location-types..xsd</jaxws:schemaLocation>
>             <jaxws:schemaLocation>classpath:xsd/location-service.xsd</jaxws:schemaLocation>
>         </jaxws:schemaLocations>
>     </jaxws:endpoint>
> {code}
> The first five requests that I send to this web service function correctly.  Any further
requests result in:
> Unmarshalling Error: cvc-elt.1: Cannot find the declaration of element 'ns1:locationElement'
> Previously in 2.0.11 this was working fine, regardless of the number of requests being
sent.

-- 
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