Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 65258 invoked by uid 500); 7 Apr 2002 20:33:52 -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 65243 invoked from network); 7 Apr 2002 20:33:52 -0000 X-Originating-IP: [24.100.242.176] From: "kel" To: Subject: XML Literal Encoding Date: Sun, 7 Apr 2002 16:36:49 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0036_01C1DE52.6A36DEF0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: X-OriginalArrivalTime: 07 Apr 2002 20:33:58.0047 (UTC) FILETIME=[8B29EAF0:01C1DE73] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_0036_01C1DE52.6A36DEF0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Currently I would like to create a Web Service interface for a Java = program. I would probably create a wrapper for it and the wrapper would = probably take an XML document as input, and then instantiates the Java = objects after processing the document and call the backend Java program. = In Apache SOAP, there is the literal encoding which does these by DOM = processing (client specifies literal encoding in the Call object, passes = in an Element, and the Service gets an Element). However, DOM = processing would be too expensive and I would like to know how the AXIS = framework can achieve this with SAX processing. Can someone please kindly point me to the right direction with the = following requirements: -clients can pass in XML data (literal encoding so that the engine does = not touch the contents?) -service gets the data and can process it with SAX (or stream if = possible). Regards, Kel ------=_NextPart_000_0036_01C1DE52.6A36DEF0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

Currently I would like to create a Web = Service=20 interface for a Java program. I would probably create a wrapper = for it and=20 the wrapper would probably take an XML document as input, and then = instantiates=20 the Java objects after processing the document and call the backend Java = program. In Apache SOAP, there is the literal encoding which does = these by=20 DOM processing (client specifies literal encoding in the Call object, = passes in=20 an Element, and the Service gets an Element). However, DOM = processing=20 would be too expensive and I would like to know how the AXIS framework = can=20 achieve this with SAX processing.

Can someone please kindly point me to = the right=20 direction with the following requirements:

-clients can pass in XML data (literal = encoding so=20 that the engine does not touch the contents?)

-service gets the data and can process = it with SAX=20 (or stream if possible).

Regards,

Kel

------=_NextPart_000_0036_01C1DE52.6A36DEF0--