You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2002/07/31 19:02:34 UTC
DO NOT REPLY [Bug 11337] New: -
Axis bug - Beta 3
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11337>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11337
Axis bug - Beta 3
Summary: Axis bug - Beta 3
Product: Axis
Version: beta-3
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Critical
Priority: Other
Component: Basic Architecture
AssignedTo: axis-dev@xml.apache.org
ReportedBy: cgopalswamy@csc.com
Problem:
(case 1) Using complex data types as input parameters in calling service method
find() followed by calling service method create() causes a SAX parsing error
in the server Axis engine.
(case 2) But calling the methods in reverse order (create() then find()) does
not cause the error. Using the TCPMon utility it was determined that the sent
XML from the client was identical in both cases.
With DEBUG Logging turned on at the server it was determined that the XML form
data created was incorrect/incomplete in case 1 - see file below. See Line 20
(02.07.12 12:53:42:161 EDT) of the badlog.txt file for the problem XML.
The EAR/WAR file (AxisLinkEJB2Bug.ear) with source code is included below.
The test client is also in the EAR/WAR for convenience. Also, attached is
relevent portion of Websphere servers log file (badlog.txt). The WSDL file is
attached (linkEJB.wsdl). Finally, attached is the XML form data extracted from
the Log file (badXMLtxt.txt). All the files are in axisbeta3bug.zip.
We are running on Websphere 4.0 server with Windows 2000 OS - 500 Meg RAM.
Files send to axis-dev@xml.apache.org