[ 
https://issues.apache.org/jira/browse/CXF-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed CXF-1540.
---------------------------

    Resolution: Invalid

This is not a bug (actually it could be a minor bug in the JAXB spec.).  Both 
CXF's wsdl2java and Metro's wsimport act the same way.

First paragraph of Section 2.1 ("Definitions") of the JAX-WS specification of 
May 2007 states that the package naming structure must follow that of Appendix 
D of the JAXB 2.1 specification.  Rule #2 of the latter says: "Remove the 
trailing file type, one of .?? or .??? or .html." in determining the package 
name.  Actually, it should say, "Remove the trailing file type, one of .? or 
.?? or .??? or .html.", because that is how JAXB works--I sent an email to the 
comments list of the JAXB specification letting them know about that.




> Maven cxf-codegen-plugin (probably wsdl2java) not creating correct default 
> package names
> ----------------------------------------------------------------------------------------
>
>                 Key: CXF-1540
>                 URL: https://issues.apache.org/jira/browse/CXF-1540
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.0.5
>            Reporter: Glen Mazza
>            Priority: Minor
>
> For the below WSDL, the default package name is stripping off a zero in the 
> package name.  
> It is giving a package name of:
> package org.example.doubleit._1_0_0;
> but it should be:
> package org.example.doubleit._1_0_0_0;
> Note if I change the namespace to end in characters it comes out correctly:
> http://www.example.org/DoubleIt/1.0.0.0/abc
> Correctly turns out to:
> package org.example.doubleit._1_0_0_0.abc;
> Using the Maven plugin given in: http://issues.apache.org/jira/browse/CXF-1539
> <?xml version="1.0" encoding="UTF-8"?>
> <wsdl:definitions name="DoubleIt" 
>    xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
>    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>    xmlns:tns="http://www.example.org/DoubleIt/1.0.0.0";
>    targetNamespace="http://www.example.org/DoubleIt/1.0.0.0";>
>    <wsdl:types>
>       <xsd:schema targetNamespace="http://www.example.org/DoubleIt/1.0.0.0";>
>          <xsd:element name="DoubleIt">
>             <xsd:complexType>
>                <xsd:sequence>
>                   <xsd:element name="numberToDouble" type="xsd:integer"/>
>                </xsd:sequence>
>             </xsd:complexType>
>          </xsd:element>
>          <xsd:element name="DoubleItResponse">
>             <xsd:complexType>
>                <xsd:sequence>
>                   <xsd:element name="doubledNumber" type="xsd:integer" />
>                </xsd:sequence>
>             </xsd:complexType>
>          </xsd:element>
>       </xsd:schema>
>    </wsdl:types>
>    <wsdl:message name="DoubleItRequest">
>       <wsdl:part element="tns:DoubleIt" name="parameters" />
>    </wsdl:message>
>    <wsdl:message name="DoubleItResponse">
>       <wsdl:part element="tns:DoubleItResponse" name="parameters" />
>    </wsdl:message>
>    <wsdl:portType name="DoubleItPortType">
>       <wsdl:operation name="DoubleIt">
>          <wsdl:input message="tns:DoubleItRequest" />
>          <wsdl:output message="tns:DoubleItResponse" />
>       </wsdl:operation>
>    </wsdl:portType>
>    <wsdl:binding name="DoubleItBinding" type="tns:DoubleItPortType">
>       <soap:binding style="document"
>          transport="http://schemas.xmlsoap.org/soap/http"; />
>       <wsdl:operation name="DoubleIt">
>          <soap:operation soapAction=""/>
>          <wsdl:input><soap:body use="literal"/></wsdl:input>
>          <wsdl:output><soap:body use="literal"/></wsdl:output>
>       </wsdl:operation>
>    </wsdl:binding>
>    <wsdl:service name="DoubleItService">
>       <wsdl:port name="DoubleItPort" binding="tns:DoubleItBinding">
>          <soap:address 
>             location="http://localhost:8080/doubleit/services/doubleit"/>
>       </wsdl:port>
>    </wsdl:service>
> </wsdl:definitions>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to