Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: 21 Feb 2004 13:24:40 -0000
Message-ID: <20040221132440.10565.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@cocoon.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 27133] New:  -
    JxTemplateGenerator eats backslash-characters

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=27133>.
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=27133

JxTemplateGenerator eats backslash-characters

           Summary: JxTemplateGenerator eats backslash-characters
           Product: Cocoon 2
           Version: 2.1.4
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: core
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: mike.bach@prisma-net.de


When working with a combination of JxForms and JxTemplate (JxForm as the 
generator and JxTemplate as a transformer in the processing pipeline) I found 
out that values with backslash characters appears WITHOUT the backslash 
characters in the resulting XML Document. e.G: the original value 
d:\static\webs appears as d:staticwebs. 

I discoverd a problem in the code of parsing values in JxTemplateGenerator 
(Source from the latest 2.1.4 release):
Line 1270
Line 1502

My quick solution was to comment out the fragment which tests on backslash 
characters in the input stream. Now it works, but I'm not sure about side 
effects so far. Perhaps my hint is useful.