Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <901400531.1122391519820.JavaMail.jira@ajax.apache.org>
Date: Tue, 26 Jul 2005 17:25:19 +0200 (CEST)
From: "Rodrigo Ruiz (JIRA)" <axis-dev@ws.apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Commented: (AXIS-2140) CLONE -Java2WSDL not generating
 nillable attribute for primitive wrapper types
In-Reply-To: <270217031.1122390858110.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/AXIS-2140?page=comments#action_12316761 ] 

Rodrigo Ruiz commented on AXIS-2140:
------------------------------------

It also happens when using parameters of "wrapper holder" types. If I have a method in the server with a signature:

public void process4(IntegerWrapperHolder v1, LongWrapperHolder v2, ShortWrapperHolder v3);

The generated stub has the following signature:

public void process4(IntHolder v1, LongHolder v2, ShortHolder v3) throws java.rmi.RemoteException;


> CLONE -Java2WSDL not generating nillable attribute for primitive wrapper types
> ------------------------------------------------------------------------------
>
>          Key: AXIS-2140
>          URL: http://issues.apache.org/jira/browse/AXIS-2140
>      Project: Apache Axis
>         Type: Bug
>   Components: WSDL processing
>     Versions: 1.0
>  Environment: Operating System: Windows NT/2K
> Platform: All
>     Reporter: Rodrigo Ruiz
>      Fix For: current (nightly)

>
> In previous versions, Java2WSDL generated soapenc mappings,
> in which nillable is implicit.  Now it generates xsd mappings,
> it needs to generate a nillable attribute for wrapper types,
> as in JAX-RPC 1.0 section 5.3.1.  It does this for members
> of complex types, but does NOT for stand-alone parameters.
> Thus: Long  -> Java2WSDL ->  xsd:long  -> WSDL2Java ->  long

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira