Return-Path: 
 <issues-return-23732-apmail-cxf-issues-archive=cxf.apache.org@cxf.apache.org>
X-Original-To: apmail-cxf-issues-archive@www.apache.org
Delivered-To: apmail-cxf-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 774B5E395
	for <apmail-cxf-issues-archive@www.apache.org>;
 Mon,  7 Jan 2013 02:28:14 +0000 (UTC)
Received: (qmail 61997 invoked by uid 500); 7 Jan 2013 02:28:14 -0000
Delivered-To: apmail-cxf-issues-archive@cxf.apache.org
Received: (qmail 61961 invoked by uid 500); 7 Jan 2013 02:28:13 -0000
Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cxf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cxf.apache.org>
List-Post: <mailto:issues@cxf.apache.org>
List-Id: <issues.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list issues@cxf.apache.org
Received: (qmail 61946 invoked by uid 99); 7 Jan 2013 02:28:13 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jan 2013 02:28:13 +0000
Date: Mon, 7 Jan 2013 02:28:13 +0000 (UTC)
From: "iris ding (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12618821.1354677716147.88682.1357525693527@arcas>
In-Reply-To: <JIRA.12618821.1354677716147@arcas>
References: <JIRA.12618821.1354677716147@arcas>
Subject: [jira] [Commented] (CXF-4676) Partial WSDL support in CXF
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

iris ding commented on CXF-4676:
--------------------------------

Hi Freeman,

Do you mean test in rt\databinding\sdo? below is my test results:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.cxf.sdo.HelloWorldDynamicTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.831 sec
Running org.apache.cxf.sdo.HelloWorldStaticTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.2 sec

Results :

Tests run: 6, Failures: 0, Errors: 0, Skipped: 0

No failures.

                
> Partial WSDL support in CXF 
> ----------------------------
>
>                 Key: CXF-4676
>                 URL: https://issues.apache.org/jira/browse/CXF-4676
>             Project: CXF
>          Issue Type: Bug
>          Components: Services
>    Affects Versions: 2.6.2
>            Reporter: iris ding
>            Assignee: Freeman Fang
>         Attachments: cxf-4676.patch
>
>
> I have one SEI defined as below:
> @WebService(wsdlLocation="WEB-INF/wsdl/AddNumbersImplPartial1Service.wsdl")
> public class AddNumbersImplPartial1 {
>        
>         public int addTwoNumbers(int number1, int number2) throws AddNegativeNumbersException {
>                 if (number1 < 0 || number2 < 0) {
>                         throw new AddNegativeNumbersException("Negative number submitted !! ", "Numbers: " +
>                                                               number1 + ", " + number2);
>                 }
>                 return number1 + number2;
>         }
> }
> The WEB-INF/wsdl/AddNumbersImplPartial1Service.wsdl is not complete, it only contains to the porttype part:
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <definitions
> targetNamespace="http://serverpartial1.partialwsdl.annotations/" 
> name="AddNumbersImplPartial1Service"
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
> xmlns:tns="http://serverpartial1.partialwsdl.annotations/"
> xmlns="http://schemas.xmlsoap.org/wsdl/">
>   <types>
>     <xsd:schema>
>       <xsd:import namespace="http://serverpartial1.partialwsdl.annotations/" schemaLocation="AddNumbersImplPartial1Service_schema1.xsd"/>
>     </xsd:schema>
>   </types>
>   <message name="addTwoNumbers">
>     <part name="parameters" element="tns:addTwoNumbers"/>
>   </message>
>   <message name="addTwoNumbersResponse">
>     <part name="parameters" element="tns:addTwoNumbersResponse"/>
>   </message>
>   <message name="AddNegativeNumbersException">
>     <part name="fault" element="tns:AddNegativeNumbersException"/>
>   </message>
>   <portType name="AddNumbersImplPartial1">
>     <operation name="addTwoNumbers">
>       <input message="tns:addTwoNumbers"/>
>       <output message="tns:addTwoNumbersResponse"/>
>       <fault name="AddNegativeNumbersException" message="tns:AddNegativeNumbersException"/>
>     </operation>
>   </portType>
>  
> </definitions>
> Now if I put the war file into tomcat and let it use CXF, the service can not be deployed successfully. In CXF, when it calls WSDLServiceFactory.create, it will simply get the service name from wsdl file and in our case, since it is empty, it will throw exception and service deployment failed. you can reference below part:
> javax.wsdl.Service wsdlService = definition.getService(serviceName);
>             if (wsdlService == null) {
>                 throw new ServiceConstructionException(new Message("NO_SUCH_SERVICE_EXC", LOG, serviceName));
>             }
> But per jaxws 2.2 spec, in chapter 5.2.5.5:
> 5.2.5.5 Application-specified PortType
> No metadata document contains a definition for the sought-after service S, but a metadata document, say
> D, contains a definition for the WSDL portType whose qualified name, say P, matches that specified by the
> endpoint being published. In this case, a JAX-WS implementation MUST create a new description for S,
> including an appropriate WSDL binding element referencing portType P. The metadata document D MUST
> be imported/included so that the published contract uses the definition of P provided by D. No schema generation
> occurs,as P is assumed to embed or import schema definitions for all the types/elements it requires.
> Like in the previous case, the implementation MUST override any location and schemaLocation attributes.
> It is an error if more than one metadata document contains a definition for the sought-after portType
> P.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira