Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 72518 invoked by uid 500); 2 Nov 2001 19:48:13 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 72475 invoked from network); 2 Nov 2001 19:48:13 -0000 Importance: Normal Subject: SOAPBodyElement serialization bug To: axis-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "David Melgar" Date: Fri, 2 Nov 2001 14:48:14 -0500 X-MIMETrack: Serialize by Router on D04NM208/04/M/IBM(Release 5.0.8 |June 18, 2001) at 11/02/2001 02:48:15 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I am writing a client that works with DOM elements. This was working with alpha 2. It is no longer working. The problem I'm running into is when a SOAPBodyElement is created from a DOM element, then serialized to a string, the element names all end up as null. The testcase below is very simple illustration of the problem. SOAPBodyElement converted to a string shows up as "". import javax.xml.parsers.DocumentBuilder; import javax.xml.parsers.DocumentBuilderFactory; import org.w3c.dom.Element; import org.apache.axis.message.SOAPBodyElement; public class Testcase1 { public static void main (String args[]) { try { DocumentBuilder docBuilder = DocumentBuilderFactory.newInstance ().newDocumentBuilder(); Element base = docBuilder.newDocument().createElement("tmp"); SOAPBodyElement body = new SOAPBodyElement(base); System.out.println("Body:" + body); } catch (Exception e) { e.printStackTrace(); } } } David Melgar Web Services Toolkit Development Emerging Technologies dmelgar@us.ibm.com