To: [EMAIL PROTECTED]
Subject: Bug in WSDL2JAVA?
Hello!
I'm using wsdl2java to generate source code from a wsdl,
and I don't
known why in the source code and in the deploy file, with
qname appears
something as ns:>SignResponse when I understand that I shoud be
ns:SignRequest. Cou
To: [EMAIL PROTECTED]
Subject: Bug in WSDL2JAVA?
Hello!
I'm using wsdl2java to generate source code from a wsdl,
and I don't
known why in the source code and in the deploy file, with
qname appears
something as ns:>SignResponse when I understand that I shoud be
ns:SignRequest. Cou
rtínez [mailto:[EMAIL PROTECTED]
> Sent: Dienstag, 4. Januar 2005 11:30
> To: [EMAIL PROTECTED]
> Subject: Bug in WSDL2JAVA?
>
>
> Hello!
>
> I'm using wsdl2java to generate source code from a wsdl,
> and I don't
> known why in the source code
Hello!
I'm using wsdl2java to generate source code from a wsdl, and I don't
known why in the source code and in the deploy file, with qname appears
something as ns:>SignResponse when I understand that I shoud be
ns:SignRequest. Could you tell me if there is a bug or I'm doing
something wrong
Hi Steve-
thanks for the prompt response! that clears it up.
false alarm - no bug. :)
-c
On Thu, Mar 11, 2004 at 06:35:51PM +0100, [EMAIL PROTECTED] wrote:
> Hi
>
> If you use the same name in both the Request and Response message then it is
> translated as an IN/OUT parameter. As such a
Hi
If you use the same name in both the Request and Response message then it is
translated as an IN/OUT parameter. As such a holder class will automatically be
used and substituted. If this is not what you want i.e. you want the method to
return a string then call the foo in the Response somthi
howdy all-
i'm working with axis, and am trying to convert a wsdl into java client stubs
and server side skeletons. i'm having much success in most of my wsdls, but
one is giving me problems. i believe i've located a bug in axis. here is the
interface portion of my wsdl:
Hi,
I've noticed something that appears to be a bug in WSDL2Java. If the class
used to generate the service contains a method that returns a Map (or takes
a Map as a parameter) then the signature of the corresponding stub
classes/interfaces use 'HashMap' instead of 'Map
I ran into this very peculiar problem. Can someone tell me if this is a
bug with wsdl2java or if it's something of my own doing. My wsdl file
looks like the following.
The stubs created for these two calls look like
I have moved to the nightly build for different reasons, one of it was to
fix the problem of non-synchronization between the deploy.wsdd and the BindingStub.
The deploy.wsdd contains the name of the port as the service name. (the port
element found under the service element:
example:
ylvain" <[EMAIL PROTECTED]> on 02/01/2002 09:20:22
AM
Please respond to [EMAIL PROTECTED]
To:"Axis-User (E-mail)" <[EMAIL PROTECTED]>
cc:
Subject:bug in wsdl2java
Hi all,
I can reproduce this strange situation, I think it is a bug.
Problem: Generated stub for
Hi all,
I can reproduce this strange situation, I think it is a bug.
Problem: Generated stub for method addFolder keeps defining the method
signature with return type void when returned part name and type are the
same as one of the input param. As shown below.
12 matches
Mail list logo