cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Pangburn (JIRA)" <>
Subject [jira] [Updated] (CXF-5365) 2.7.7 schema validation seems broken
Date Mon, 28 Oct 2013 23:38:31 GMT


Jesse Pangburn updated CXF-5365:


To run these, expand in the 2.7.6 or 2.7.7 samples folder accordingly.  Then in one terminal
mvn -P server
This starts up two different services (same types, different URL only).  One is configured
in Java to have schema validation on, the other is configured in spring to have schema validation

Correspondingly, there are two client profiles.  They are run like this:
mvn -P client
mvn -P clientspring
The "clientspring" profile targets the Spring configured service.  Both of these profiles
send two messages- one which doesn't violate schema and one which does.

In 2.7.6, both profiles correctly send the first message and then the second message generates
a schema error.  In 2.7.7, both messages in both profiles are accepted and the response is
sent normally with no errors.  So schema validation is either off entirely, or it's not engaging
because the schema files referred to by the WSDLs import each other.

> 2.7.7 schema validation seems broken
> ------------------------------------
>                 Key: CXF-5365
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.7.7
>            Reporter: Jesse Pangburn
>              Labels: schema, validation
>         Attachments:,
> Turning on schema validation in 2.7.7 seems to have a number of problems.  In the case
of my own embedded CXF, it does validate but fails with schemas that have circular references
to each other (not illegal according to W3C spec or their schema validator tool online).
> So I wrote a test sample but found that in the test sample that it doesn't validate the
schema at all- just lets the bad elements go through with no error.  The 2.7.6 version of
the sample properly throws an error- and all I did to create the 2.7.6 version was to copy
the sample folder under 2.7.6 and search/replace 2.7.7 in the pom.xml with 2.7.6.
> For this issue, I think we should try to solve why 2.7.6 properly throws an exception
on a request with a bad schema and why 2.7.7 does not.  I'll check separately if the resolution
to this fixes my initial problem and if it doesn't then I'll create a separate issue for that
along with a test case.
> I will attach the test sample after creating the issue.

This message was sent by Atlassian JIRA

View raw message