Subject: RE: Array deserialization
problem
03/20
Good stuff!
-Original Message-
From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 20, 2002 9:26 AM
To: [EMAIL PROTECTED]
Subject: RE: Array deserialization problem
Russell and I talked about this problem, and I am going to implement a
feature (today) which will
Actually, they are defined in the wsdd, they seem to be simply missing from
the Stub.
Sylvain.
-Original Message-
From: Russell Butek [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 19, 2002 9:34 PM
To: [EMAIL PROTECTED]
Subject: RE: Array deserialization problem
Ah! I misunderstood
cc:
Subject: RE: Array deserialization
problem
03/19/2002 08:34
/19/2002 11:48:31
AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject:RE: Array deserialization problem
This means to me that I cannot used the extended types.
My API is defined with arround a base type but what I am carrying on the
wire is the extended types.
Without th
Sent: Tuesday, March 19, 2002 11:12 AM
To: [EMAIL PROTECTED]
Subject: RE: Array deserialization problem
The --all option GENERATES all mappings, but since all mappings aren't
USED, we don't force anything (ie., the stub) to use them.
Russell Butek
[EMAIL PROTECTED]
"St-Germain, Sy
]
To:[EMAIL PROTECTED]
cc:
Subject: RE: Array deserialization problem
I found it, the Stub constructor is not defining all the mapping for the
types I need.
I am currently calling WSDL2Java with -stav, when you guys implemented the
-all option to generate the classes for all types define
I found it, the Stub constructor is not defining all the mapping for the
types I need.
I am currently calling WSDL2Java with -stav, when you guys implemented the
-all option to generate the classes for all types defined, is it possible
that was forgotten or left aside the change to the Stub th
