You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Craig Tataryn (JIRA)" <ji...@apache.org> on 2009/11/02 18:20:59 UTC
[jira] Created: (CXF-2516) Schema resolution when Schemas in Jar
separate from endpoint implementation
Schema resolution when Schemas in Jar separate from endpoint implementation
---------------------------------------------------------------------------
Key: CXF-2516
URL: https://issues.apache.org/jira/browse/CXF-2516
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Affects Versions: 2.2.3
Environment: Windows XP, Spring 2.5.6
java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
J9VM - 20081105_025433_lHdSMr
JIT - r9_20081031_1330
GC - 20081027_AB)
JCL - 20081106_01
Reporter: Craig Tataryn
I'm going to attach a project which will demonstrate the problem.
Essentially I have a Web Service Implementation in a WebService module. I have separated out the schemas and wsdls into a module called WebServiceSchemasAndWSDL. The SchemasAndWSDL project is a dependency of the WebService project. If I turn on xsd-validation for my endpoint, when validation runs it will complain that it can't find certain schemas, for example:
<pre>
org.apache.cxf.wsdl.EndpointReferenceUtils$SchemaLSResourceResolver
resolveResource
WARNING: Could not resolve Schema for COCT_MT090102CA.xsd
</pre>
COCT_MT090102CA.xsd is not referenced *directly* from the WSDL, it's actually referenced from one of the schemas the WSDL references.
STRUCTURE OF THE PROJECTS:
*WebService Project:*
src/main/java/my/pack/WebServiceImpl.java
/src/main/resources/config/spring/endpointBeans.xml
*WSDLandSchemas Project:*
src/main/generated/... <-- all the JAXB generated resources from the Schemas/WSDL including the service interface being implemented in the WebService project
src/main/resources/wsdl/WebService.wsdl
src/main/resources/telus/Schemas
src/main/resources/telus/schemas/coreschemas
So COCT_MT090102CA.xsd exists in the 3rdParty directory (i.e. telus/Schemas) within the WSDLandSchemas project (which is on the classpath for the WebService project). The WSDL references a schema in that same directory and it's that schema which has an <xsd:include schemaLocation="COCT_MT090102CA.xsd"/>
I'll attach the schema validation errors which occure, as well as the sample project.
My original problem centered around the fact that if I separated out the wsdl from the schemas (i.e. put the wsdl directly into the WebService project, and ran cxf-codegen-plugin from there) it could never figure out the refereces that the schemas in telus/Schemas had to xsds in telus/schemas/coreschemas. But one problem at a time I suppose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2516) Schema resolution when Schemas in Jar
separate from endpoint implementation
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-2516:
-----------------------------
Fix Version/s: 2.1.8
> Schema resolution when Schemas in Jar separate from endpoint implementation
> ---------------------------------------------------------------------------
>
> Key: CXF-2516
> URL: https://issues.apache.org/jira/browse/CXF-2516
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.2.3
> Environment: Windows XP, Spring 2.5.6
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT - r9_20081031_1330
> GC - 20081027_AB)
> JCL - 20081106_01
> Reporter: Craig Tataryn
> Assignee: Daniel Kulp
> Fix For: 2.1.8, 2.2.5
>
> Attachments: CXFSchemaProblem.zip, out.txt
>
>
> I'm going to attach a project which will demonstrate the problem.
> Essentially I have a Web Service Implementation in a WebService module. I have separated out the schemas and wsdls into a module called WebServiceSchemasAndWSDL. The SchemasAndWSDL project is a dependency of the WebService project. If I turn on xsd-validation for my endpoint, when validation runs it will complain that it can't find certain schemas, for example:
> <pre>
> org.apache.cxf.wsdl.EndpointReferenceUtils$SchemaLSResourceResolver
> resolveResource
> WARNING: Could not resolve Schema for COCT_MT090102CA.xsd
> </pre>
> COCT_MT090102CA.xsd is not referenced *directly* from the WSDL, it's actually referenced from one of the schemas the WSDL references.
> STRUCTURE OF THE PROJECTS:
> *WebService Project:*
> src/main/java/my/pack/WebServiceImpl.java
> /src/main/resources/config/spring/endpointBeans.xml
> *WSDLandSchemas Project:*
> src/main/generated/... <-- all the JAXB generated resources from the Schemas/WSDL including the service interface being implemented in the WebService project
> src/main/resources/wsdl/WebService.wsdl
> src/main/resources/telus/Schemas
> src/main/resources/telus/schemas/coreschemas
> So COCT_MT090102CA.xsd exists in the 3rdParty directory (i.e. telus/Schemas) within the WSDLandSchemas project (which is on the classpath for the WebService project). The WSDL references a schema in that same directory and it's that schema which has an <xsd:include schemaLocation="COCT_MT090102CA.xsd"/>
> I'll attach the schema validation errors which occure, as well as the sample project.
> My original problem centered around the fact that if I separated out the wsdl from the schemas (i.e. put the wsdl directly into the WebService project, and ran cxf-codegen-plugin from there) it could never figure out the refereces that the schemas in telus/Schemas had to xsds in telus/schemas/coreschemas. But one problem at a time I suppose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-2516) Schema resolution when Schemas in Jar
separate from endpoint implementation
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772716#action_12772716 ]
Daniel Kulp commented on CXF-2516:
----------------------------------
Just a clarification....
I managed to get your usecase working, but required some changes to the wsdl. There may be a bug in the Schema factory things in the JDK. It seems that it's only doing the first "xsd:import" of a given namespace. If I change the wsdl to have a second schema with that targetNamespace which then includes everything instead of importing, then just does as import in the original schema, it seems to work now work fine.
> Schema resolution when Schemas in Jar separate from endpoint implementation
> ---------------------------------------------------------------------------
>
> Key: CXF-2516
> URL: https://issues.apache.org/jira/browse/CXF-2516
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.2.3
> Environment: Windows XP, Spring 2.5.6
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT - r9_20081031_1330
> GC - 20081027_AB)
> JCL - 20081106_01
> Reporter: Craig Tataryn
> Assignee: Daniel Kulp
> Fix For: 2.2.5
>
> Attachments: CXFSchemaProblem.zip, out.txt
>
>
> I'm going to attach a project which will demonstrate the problem.
> Essentially I have a Web Service Implementation in a WebService module. I have separated out the schemas and wsdls into a module called WebServiceSchemasAndWSDL. The SchemasAndWSDL project is a dependency of the WebService project. If I turn on xsd-validation for my endpoint, when validation runs it will complain that it can't find certain schemas, for example:
> <pre>
> org.apache.cxf.wsdl.EndpointReferenceUtils$SchemaLSResourceResolver
> resolveResource
> WARNING: Could not resolve Schema for COCT_MT090102CA.xsd
> </pre>
> COCT_MT090102CA.xsd is not referenced *directly* from the WSDL, it's actually referenced from one of the schemas the WSDL references.
> STRUCTURE OF THE PROJECTS:
> *WebService Project:*
> src/main/java/my/pack/WebServiceImpl.java
> /src/main/resources/config/spring/endpointBeans.xml
> *WSDLandSchemas Project:*
> src/main/generated/... <-- all the JAXB generated resources from the Schemas/WSDL including the service interface being implemented in the WebService project
> src/main/resources/wsdl/WebService.wsdl
> src/main/resources/telus/Schemas
> src/main/resources/telus/schemas/coreschemas
> So COCT_MT090102CA.xsd exists in the 3rdParty directory (i.e. telus/Schemas) within the WSDLandSchemas project (which is on the classpath for the WebService project). The WSDL references a schema in that same directory and it's that schema which has an <xsd:include schemaLocation="COCT_MT090102CA.xsd"/>
> I'll attach the schema validation errors which occure, as well as the sample project.
> My original problem centered around the fact that if I separated out the wsdl from the schemas (i.e. put the wsdl directly into the WebService project, and ran cxf-codegen-plugin from there) it could never figure out the refereces that the schemas in telus/Schemas had to xsds in telus/schemas/coreschemas. But one problem at a time I suppose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-2516) Schema resolution when Schemas in Jar
separate from endpoint implementation
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-2516:
--------------------------------
Assignee: Daniel Kulp
> Schema resolution when Schemas in Jar separate from endpoint implementation
> ---------------------------------------------------------------------------
>
> Key: CXF-2516
> URL: https://issues.apache.org/jira/browse/CXF-2516
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.2.3
> Environment: Windows XP, Spring 2.5.6
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT - r9_20081031_1330
> GC - 20081027_AB)
> JCL - 20081106_01
> Reporter: Craig Tataryn
> Assignee: Daniel Kulp
> Attachments: CXFSchemaProblem.zip, out.txt
>
>
> I'm going to attach a project which will demonstrate the problem.
> Essentially I have a Web Service Implementation in a WebService module. I have separated out the schemas and wsdls into a module called WebServiceSchemasAndWSDL. The SchemasAndWSDL project is a dependency of the WebService project. If I turn on xsd-validation for my endpoint, when validation runs it will complain that it can't find certain schemas, for example:
> <pre>
> org.apache.cxf.wsdl.EndpointReferenceUtils$SchemaLSResourceResolver
> resolveResource
> WARNING: Could not resolve Schema for COCT_MT090102CA.xsd
> </pre>
> COCT_MT090102CA.xsd is not referenced *directly* from the WSDL, it's actually referenced from one of the schemas the WSDL references.
> STRUCTURE OF THE PROJECTS:
> *WebService Project:*
> src/main/java/my/pack/WebServiceImpl.java
> /src/main/resources/config/spring/endpointBeans.xml
> *WSDLandSchemas Project:*
> src/main/generated/... <-- all the JAXB generated resources from the Schemas/WSDL including the service interface being implemented in the WebService project
> src/main/resources/wsdl/WebService.wsdl
> src/main/resources/telus/Schemas
> src/main/resources/telus/schemas/coreschemas
> So COCT_MT090102CA.xsd exists in the 3rdParty directory (i.e. telus/Schemas) within the WSDLandSchemas project (which is on the classpath for the WebService project). The WSDL references a schema in that same directory and it's that schema which has an <xsd:include schemaLocation="COCT_MT090102CA.xsd"/>
> I'll attach the schema validation errors which occure, as well as the sample project.
> My original problem centered around the fact that if I separated out the wsdl from the schemas (i.e. put the wsdl directly into the WebService project, and ran cxf-codegen-plugin from there) it could never figure out the refereces that the schemas in telus/Schemas had to xsds in telus/schemas/coreschemas. But one problem at a time I suppose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-2516) Schema resolution when Schemas in Jar
separate from endpoint implementation
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-2516.
------------------------------
Resolution: Fixed
Fix Version/s: 2.2.5
> Schema resolution when Schemas in Jar separate from endpoint implementation
> ---------------------------------------------------------------------------
>
> Key: CXF-2516
> URL: https://issues.apache.org/jira/browse/CXF-2516
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.2.3
> Environment: Windows XP, Spring 2.5.6
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT - r9_20081031_1330
> GC - 20081027_AB)
> JCL - 20081106_01
> Reporter: Craig Tataryn
> Assignee: Daniel Kulp
> Fix For: 2.2.5
>
> Attachments: CXFSchemaProblem.zip, out.txt
>
>
> I'm going to attach a project which will demonstrate the problem.
> Essentially I have a Web Service Implementation in a WebService module. I have separated out the schemas and wsdls into a module called WebServiceSchemasAndWSDL. The SchemasAndWSDL project is a dependency of the WebService project. If I turn on xsd-validation for my endpoint, when validation runs it will complain that it can't find certain schemas, for example:
> <pre>
> org.apache.cxf.wsdl.EndpointReferenceUtils$SchemaLSResourceResolver
> resolveResource
> WARNING: Could not resolve Schema for COCT_MT090102CA.xsd
> </pre>
> COCT_MT090102CA.xsd is not referenced *directly* from the WSDL, it's actually referenced from one of the schemas the WSDL references.
> STRUCTURE OF THE PROJECTS:
> *WebService Project:*
> src/main/java/my/pack/WebServiceImpl.java
> /src/main/resources/config/spring/endpointBeans.xml
> *WSDLandSchemas Project:*
> src/main/generated/... <-- all the JAXB generated resources from the Schemas/WSDL including the service interface being implemented in the WebService project
> src/main/resources/wsdl/WebService.wsdl
> src/main/resources/telus/Schemas
> src/main/resources/telus/schemas/coreschemas
> So COCT_MT090102CA.xsd exists in the 3rdParty directory (i.e. telus/Schemas) within the WSDLandSchemas project (which is on the classpath for the WebService project). The WSDL references a schema in that same directory and it's that schema which has an <xsd:include schemaLocation="COCT_MT090102CA.xsd"/>
> I'll attach the schema validation errors which occure, as well as the sample project.
> My original problem centered around the fact that if I separated out the wsdl from the schemas (i.e. put the wsdl directly into the WebService project, and ran cxf-codegen-plugin from there) it could never figure out the refereces that the schemas in telus/Schemas had to xsds in telus/schemas/coreschemas. But one problem at a time I suppose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-2516) Schema resolution when Schemas in Jar
separate from endpoint implementation
Posted by "Craig Tataryn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Tataryn updated CXF-2516:
-------------------------------
Attachment: out.txt
CXFSchemaProblem.zip
Attaching the sample project. There is a sample request you can use within the WebService directory (sampleRequest.xml). Also, out.txt contains stderr messages from the schema validation.
> Schema resolution when Schemas in Jar separate from endpoint implementation
> ---------------------------------------------------------------------------
>
> Key: CXF-2516
> URL: https://issues.apache.org/jira/browse/CXF-2516
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.2.3
> Environment: Windows XP, Spring 2.5.6
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT - r9_20081031_1330
> GC - 20081027_AB)
> JCL - 20081106_01
> Reporter: Craig Tataryn
> Attachments: CXFSchemaProblem.zip, out.txt
>
>
> I'm going to attach a project which will demonstrate the problem.
> Essentially I have a Web Service Implementation in a WebService module. I have separated out the schemas and wsdls into a module called WebServiceSchemasAndWSDL. The SchemasAndWSDL project is a dependency of the WebService project. If I turn on xsd-validation for my endpoint, when validation runs it will complain that it can't find certain schemas, for example:
> <pre>
> org.apache.cxf.wsdl.EndpointReferenceUtils$SchemaLSResourceResolver
> resolveResource
> WARNING: Could not resolve Schema for COCT_MT090102CA.xsd
> </pre>
> COCT_MT090102CA.xsd is not referenced *directly* from the WSDL, it's actually referenced from one of the schemas the WSDL references.
> STRUCTURE OF THE PROJECTS:
> *WebService Project:*
> src/main/java/my/pack/WebServiceImpl.java
> /src/main/resources/config/spring/endpointBeans.xml
> *WSDLandSchemas Project:*
> src/main/generated/... <-- all the JAXB generated resources from the Schemas/WSDL including the service interface being implemented in the WebService project
> src/main/resources/wsdl/WebService.wsdl
> src/main/resources/telus/Schemas
> src/main/resources/telus/schemas/coreschemas
> So COCT_MT090102CA.xsd exists in the 3rdParty directory (i.e. telus/Schemas) within the WSDLandSchemas project (which is on the classpath for the WebService project). The WSDL references a schema in that same directory and it's that schema which has an <xsd:include schemaLocation="COCT_MT090102CA.xsd"/>
> I'll attach the schema validation errors which occure, as well as the sample project.
> My original problem centered around the fact that if I separated out the wsdl from the schemas (i.e. put the wsdl directly into the WebService project, and ran cxf-codegen-plugin from there) it could never figure out the refereces that the schemas in telus/Schemas had to xsds in telus/schemas/coreschemas. But one problem at a time I suppose.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.