axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Börkel <...@ap-ag.com>
Subject RE: When is Axis 1.2 expected to be "final"?
Date Mon, 19 Jul 2004 13:57:19 GMT
HI!

> -----Original Message-----
> From: Glen Daniels [mailto:glen@thoughtcraft.com] 
> Sent: Freitag, 16. Juli 2004 16:04
> To: axis-dev@ws.apache.org
> Cc: dims@yahoo.com; Thomas Börkel
> Subject: Re: When is Axis 1.2 expected to be "final"?

> dims, I just noticed the change you made on December 9th to
> org.apache.axis.wsdl.fromJava.Types.  With this change, we 
> ALWAYS emit the
> type mapping from the default type mapping registry if it 
> exists, and NEVER
> the one from the service-specific type mapping - this seems 
> very very bad.
> That means if a given service has remapped any of the default 
> types, there
> will be an inconsistency between the generated WSDL and the 
> actual runtime
> behavior....  This is part of the problem with Thomas' bug, 
> since if the
> code were the old way you would see "soapenc:string" in the 
> WSDL instead of
> "xsd:string".  I'm putting this back the way it was, which 
> may actually fix
> the .NET issue!  If .NET was having a problem because the types didn't
> agree, and not because it doesn't support the soapenc types 
> (this actually
> seems pretty likely to me, esp if it used to work), this 
> should fix it.  I'm
> attaching the updated Types.java file - Thomas, if you could 
> try your test
> again with this one (making sure to use the newly generated 
> WSDL), that
> would be great.

With this change, the resulting WSDL is exactly the same as before. And the problem is also
the same.

Regards,
Thomas

Mime
View raw message