The problem does seem to be resolved in the latest snapshot. The
problem with the 1.2.1 release is it produced typeDesc code that looked
like:
elemField.setXmlName(new
javax.xml.namespace.QName("http://test.axis.com/wsdl2java/";,
"testDate"));
elemField.setXmlType(new
javax.xml.nam
It's added -- I've also done some work to get the Axis JMS integration
with weblogic working if you are interested
-mike
-Original Message-
From: Davanum Srinivas (JIRA) [mailto:[EMAIL PROTECTED]
Sent: Monday, August 22, 2005 2:55 PM
To: [EMAIL PROTECTED]
Subject: [jira] Commented: (
I've created the issue as critical, we can work with the patch I've
created for now
http://issues.apache.org/jira/browse/AXIS-2115
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 12, 2005 4:00 PM
To: axis-dev@ws.apache.org
Subject: Re: axis 1
Title: Message
Axis 1.2.1, as a client, seems to be failing to
deserialize responses properly and completely fails when parsing a date returned
from an Axis 1.1 document/literal service. Listed below are 3 scenarios
where the same WSDL was used to
generate the client and serverside binding
