On 4/28/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> try latest Nightly / CVS and THEN file a bug :)
I've just done, but nothing works so, I'll regress to Axis 1.2
RC2 and I'll file a bug report as soon as I can.
However, there's one thing with RC2 that makes me puzzled
Its SOAP env
try latest Nightly / CVS and THEN file a bug :)
-- dims
On 4/28/05, Sergio Bossa <[EMAIL PROTECTED]> wrote:
> > You should file a bug about wsdl2java with an attached example if you want
> > it fixed ...
>
> I've just done.
>
> Should I file a bug report also for the array deserialization prob
> You should file a bug about wsdl2java with an attached example if you want it
> fixed ...
I've just done.
Should I file a bug report also for the array deserialization problem?
It seems to me very absurd that Axis 1.2 RC3 broke array deserialization ...
--
Sergio Bossa
Author and Developer
You should file a bug about wsdl2java with an attached example if you
want it fixed ...
Tim
Sergio Bossa wrote:
Did you regenerate the client stub using Axis 1.2RC3 wsdl2java?
I do not use wsdl2java stubs: it produces a buggy fault
implementation, generating a MontagSOAPFault_Element.java c
> Did you regenerate the client stub using Axis 1.2RC3 wsdl2java?
I do not use wsdl2java stubs: it produces a buggy fault
implementation, generating a MontagSOAPFault_Element.java class file
instead of a MontagSOAPFault class, so I have to correct it by hand,
which is very annoying.
I posted an he
Did you regenerate the client stub using Axis 1.2RC3 wsdl2java?
If so, then I would expect it to send a message that looks something like this:
http://montag.sourceforge.net/ns/wsdl/local";>
/resources
{ //[EMAIL PROTECTED]
ts
1113390437052
Anne
On 4/27/05, Sergi
