Return-Path: Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: (qmail 99633 invoked from network); 30 Apr 2010 12:41:30 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Apr 2010 12:41:30 -0000 Received: (qmail 7658 invoked by uid 500); 30 Apr 2010 12:41:30 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 7602 invoked by uid 500); 30 Apr 2010 12:41:29 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 7594 invoked by uid 99); 30 Apr 2010 12:41:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Apr 2010 12:41:29 +0000 X-ASF-Spam-Status: No, hits=4.4 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of hiranya911@gmail.com designates 209.85.212.42 as permitted sender) Received: from [209.85.212.42] (HELO mail-vw0-f42.google.com) (209.85.212.42) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Apr 2010 12:41:23 +0000 Received: by vws8 with SMTP id 8so99766vws.15 for ; Fri, 30 Apr 2010 05:41:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=/HBDnPkTRiNMXLiFlCJygf1+dqYelk86qV7kCDpFgqw=; b=kqjRM/YWjc5Ov6sX0YrAk+CWc6MqGnBKcQGYAj8rctU42eUYvHDBzAT7ZmJEqXWCZR 8UdGV4MrhVnKCXu2wVGh0g1NMDXamxdWnKjooOW4lhdveFSG+Y0c+Ae+y5TZ963bsu7v P5BW57yHxmTZb6kOwIE3iWPiMHxXIkfDmFKgw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=YcCss7+xrdFgXOX9zLoZrq5tGlOHdvoanJmfrOEMDI9mYBiXxAl/1v0lsIbSgHJ0R7 R1rcxSQCqVh/jsRSULUdzHkjwh1cRZbqHXVefDOtBkgsb4l5uH+lAQKVJimdpXG9mQu8 7fXVWGmTEIycbZJf66AXwgVYfarSmpYmrz+1c= MIME-Version: 1.0 Received: by 10.220.62.12 with SMTP id v12mr4656471vch.187.1272631262075; Fri, 30 Apr 2010 05:41:02 -0700 (PDT) Received: by 10.220.99.134 with HTTP; Fri, 30 Apr 2010 05:41:02 -0700 (PDT) Date: Fri, 30 Apr 2010 18:11:02 +0530 Message-ID: Subject: Local Entires with CDATA Elements From: Hiranya Jayathilaka To: dev@synapse.apache.org Content-Type: multipart/alternative; boundary=e0cb4e887dd54e5c820485738ef4 X-Virus-Checked: Checked by ClamAV on apache.org --e0cb4e887dd54e5c820485738ef4 Content-Type: text/plain; charset=ISO-8859-1 Hi Folks, While doing some work on SYNAPSE-624, I have realized that Synapse does not handle local entry values with CDATA elements properly. Axiom seems to drop CDATA elements while parsing XML. For an example given the following local entry configuration: ]]> the serialized XML would be as follows: <SomeXML/> Note that the CDATA element is gone, and its value has been partially encoded. The way out of this issue is to disable coalescing in the parser. But that would be globally applied to all XML parsing logic in Synapse (unless we somehow use a separate OM builder for parsing local entries). So how do you think we should handle this scenario? Thanks -- Hiranya Jayathilaka Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com --e0cb4e887dd54e5c820485738ef4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Folks,

While doing some work on SYNAPSE-624, I have r= ealized that Synapse does not handle local entry values with CDATA elements= properly. Axiom seems to drop CDATA elements while parsing XML. For an exa= mple given the following local entry configuration:

<= br>

the serialized XML would be as follows:

Note tha= t the CDATA element is gone, and its value has been partially encoded. The = way out of this issue is to disable coalescing in the parser. But that woul= d be globally applied to all XML parsing logic in Synapse (unless we someho= w use a separate OM builder for parsing local entries). So how do you think= we should handle this scenario?

Thanks
--
Hiranya Jayathilaka
Software Engine= er;
WSO2 Inc.; =A0http://wso2.org
E-m= ail: hiranya@wso2.com; =A0Mobile: += 94 77 633 3491
Blog: http://techfeast-hi= ranya.blogspot.com

--e0cb4e887dd54e5c820485738ef4--