Return-Path: Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: (qmail 99397 invoked from network); 2 Nov 2009 17:21:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Nov 2009 17:21:24 -0000 Received: (qmail 43317 invoked by uid 500); 2 Nov 2009 17:21:24 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 43254 invoked by uid 500); 2 Nov 2009 17:21:23 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 43241 invoked by uid 99); 2 Nov 2009 17:21:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Nov 2009 17:21:22 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Nov 2009 17:21:20 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 62921234C48D for ; Mon, 2 Nov 2009 09:20:59 -0800 (PST) Message-ID: <737858146.1257182459398.JavaMail.jira@brutus> Date: Mon, 2 Nov 2009 17:20:59 +0000 (UTC) From: "Craig Tataryn (JIRA)" To: issues@cxf.apache.org Subject: [jira] Created: (CXF-2516) Schema resolution when Schemas in Jar separate from endpoint implementation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org 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:
org.apache.cxf.wsdl.EndpointReferenceUtils$SchemaLSResourceResolver
resolveResource
WARNING: Could not resolve Schema for COCT_MT090102CA.xsd
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 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.