Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 45840 invoked from network); 3 Dec 2004 07:35:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 3 Dec 2004 07:35:56 -0000 Received: (qmail 91886 invoked by uid 500); 3 Dec 2004 07:35:51 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 91861 invoked by uid 500); 3 Dec 2004 07:35:50 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 91851 invoked by uid 99); 3 Dec 2004 07:35:50 -0000 X-ASF-Spam-Status: No, hits=0.8 required=10.0 tests=INVALID_TZ_GMT X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from relay3.slt.lk (HELO relay3.slt.lk) (203.115.0.25) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 02 Dec 2004 23:35:49 -0800 Received: from extreme (localhost [127.0.0.1]) by relay3.slt.lk (8.12.10+Sun/8.12.10) with ESMTP id iB37Vr4C005479 for ; Fri, 3 Dec 2004 13:32:01 +0600 (GMT) Message-Id: <200412030732.iB37Vr4C005479@relay3.slt.lk> Reply-To: From: "Eran Chinthaka" To: Subject: RE: [Axis2] Re: Full infoset support Date: Fri, 3 Dec 2004 13:37:14 +0600 Organization: LSF MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <41B00FD3.3040706@cs.indiana.edu> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTZBv/tTbu72yPWTdaaj98b4lL0ZQAAzhLg X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N >> >>i know i may be PITA but please do put [Axis2] somewhere in email >>subject ... [Chinthaka] Alek, Axis2 was there in the subject. My email filters got it correct. >> >>my reply is below. >> >>Ajith Ranabahu wrote: >> >>>Since this issue was taken up in the last IRC session and ended with >>>no conclusion, I suppose we should talks about this seriously and take >>>a decision. So I am going to put forward the qeustion in simple terms >>>and put up my answer with reasons. >>> >>>Q - Do we need full XML infoset support with OM? >>> >>>A - No. >>> >>> >>please define what is exactly full XML infoset support? >> >>for me it is: AXIOM API must support XML Infoset and allow an API >>implementation that implements all XML infoset if it finds it necessary >>but default OM implementation is optimized for SOAP. >> >>i think Web Services are more than just SOAP and precluding use of >>XML/HTTP would be an error (especially that it is so easy to support). >> >>the only parts of XML Infoset that we may not want to support are those >>not required by SOAP (mostly related to PIs and DTDs as they are >>prohibited in SOAP 1.2 message for details see >>http://www.w3.org/TR/soap12-part1/#soapenv - anything more excluded? and >>comments are allowed just not inside message but in document ...) >> >>so think it can be simply done by having DTD related properties >>empty/default/null (such as those in >>http://www.w3.org/TR/xml-infoset/#infoitem.document) and AXIOM impl to >>throw exception if it sees DTD (configurable to do so as required for >>SOAP 1.2 ...) [Chinthaka] can u all remember the basic concepts we agreed on the summit. One is YAGNI and one other is KISS. So if we just create some support for DTD and PI and just throw an exception, isn't it YAGNI or violating KISS ??????? Thankx, Eran Chinthaka >> >>this is very quick analysis - let me know if i missed something. >> >>thanks, >> >>alek >> >>-- >>The best way to predict the future is to invent it - Alan Kay