Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 43588 invoked from network); 20 Nov 2009 09:32:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Nov 2009 09:32:22 -0000 Received: (qmail 15506 invoked by uid 500); 20 Nov 2009 09:32:22 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 15413 invoked by uid 500); 20 Nov 2009 09:32:22 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 15405 invoked by uid 99); 20 Nov 2009 09:32:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Nov 2009 09:32:22 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Alexander.Lochschmied@vishay.com designates 57.68.16.124 as permitted sender) Received: from [57.68.16.124] (HELO mamv02.vishay.com) (57.68.16.124) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Nov 2009 09:32:07 +0000 Received: from VMMV12.VISHAY.COM (vmmv12.Vishay.com [57.68.16.12]) by mamv02.vishay.com with ESMTP id v2sOlSibBbT4xato for ; Fri, 20 Nov 2009 04:31:45 -0500 (EST) Received: from WSMV54.corp.vishayint.com (wsmv54.corp.vishayint.com [172.26.20.54]) by Mail1.Vishay.com (PMDF V6.3-x3 #31205) with ESMTP id <01NGAWOT5H308WX6DL@Mail1.Vishay.com> for dev@cocoon.apache.org; Fri, 20 Nov 2009 04:31:30 -0500 Received: from WSMV109.eu.vishayint.com ([172.26.20.209]) by WSMV54.corp.vishayint.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 20 Nov 2009 04:31:29 -0500 Received: from EVSSE01.eu.vishayint.com ([172.16.20.19]) by WSMV109.eu.vishayint.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 20 Nov 2009 04:31:30 -0500 Date: Fri, 20 Nov 2009 10:31:26 +0100 From: "Lochschmied, Alexander" Subject: RE: Unbalanced tags not triggering endTransformingElement in Transformer To: dev@cocoon.apache.org Message-id: <896EE9AD73266B45A3D9543759F6503A03A30B79@EVSSE01.eu.vishayint.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Content-type: multipart/alternative; boundary="----_=_NextPart_001_01CA69C4.3BA9C55A" Thread-Topic: Unbalanced tags not triggering endTransformingElement in Transformer Thread-Index: AcppFjwkIqXU4hwZRs+0SnNJKVSnVwABMeywACo6wJA= Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: References: <896EE9AD73266B45A3D9543759F6503A03A305C3@EVSSE01.eu.vishayint.com> X-OriginalArrivalTime: 20 Nov 2009 09:31:30.0045 (UTC) FILETIME=[3D8A22D0:01CA69C4] X-Virus-Scanned: by bsmtpd at vishay.com X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------_=_NextPart_001_01CA69C4.3BA9C55A Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello again! =20 I think I was wrong, unbalanced tags do not seem to cause it. Here is = sample input XML for my transformer: =20 abc def img
br
Enlarge =20 The elements inside T8400 (img, br, a) do not trigger = endTransformingElement() but they do trigger startTransformingElement(). = And again: This is only a problem if the input XML is coming from = another Cocoon processing step. It is not a problem if the input XML is = read from file system (with FileGenerator). This is actually the most = confusing part for me. If input comes from a file, they do generate the end events. =20 Any pointers for me? =20 Thanks, Alexander =20 From: Lochschmied, Alexander=20 Sent: Donnerstag, 19. November 2009 14:23 To: 'dev@cocoon.apache.org' Subject: RE: Unbalanced tags not triggering endTransformingElement in = Transformer=20 =20 To avoid confusion, please swap the pattern values of my example; "OK" = should be "NOT_OK" and vice versa. =20 Let me call
"unbalanced" element as opposed to

. I'm extending AbstractSAXTransformer and noticed that unbalanced = elements do not trigger endTransformingElement(...) if the source (or = generator) is cocoon:/something. =20 Example: =20 1. Unbalanced tags do NOT trigger endTransformingElement(...) =20 2. Unbalanced tags do trigger endTransformingElement(...) =20 Can somebody explain what I could possibly be missing or is that a bug = in Cocoon? =20 Thanks, Alexander =20 From: Lochschmied, Alexander=20 Sent: Donnerstag, 19. November 2009 13:46 To: dev@cocoon.apache.org Subject: Unbalanced tags not triggering endTransformingElement in = Transformer=20 =20 Hello! =20 Let me call
"unbalanced" element as opposed to

. I'm extending AbstractSAXTransformer and noticed that unbalanced = elements do not trigger endTransformingElement(...) if the source (or = generator) is cocoon:/something. =20 Example: =20 1. Unbalanced tags do NOT trigger endTransformingElement(...) =20 2. Unbalanced tags do trigger endTransformingElement(...) =20 Can somebody explain what I'm could possibly be missing or is that a bug = in Cocoon? =20 Thanks, Alexander =20 Alexander Lochschmied=20 Web Programmer - Internet and Commerce=20 IT Global Web Services=20 Information Technology Phone: +49 92 8771 2682 Fax +49 92 8771 2545 Website: www.vishay.com =20 =20 Vishay Electronic GmbH Geheimrat-Rosenthal-Str. 100=20 D-95100 Selb=20 Amtsgericht/County Court Hof HRB 2894,=20 Gesch=E4ftsf=FChrer/Managing Directors: Sieglinde Janker-Buecherl, = Arnold Rohr =20 ------_=_NextPart_001_01CA69C4.3BA9C55A Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello = again!

 

I think I was wrong, = unbalanced tags do not seem to cause it. Here is sample input XML for my = transformer:

 

      <rowset xmlns=3D"http://www.vishay.com/r= owspan/1.0">

           = <row>

           =        <P1000>abc</P1000>

           =        <P1001>def</P1001>

           =        <T8400>

        &nbs= p;            = ;   <img src=3D"small.jpg">img</img>

        &nbs= p;            = ;   <br>br</br>

           =              <a href=3D"javascript:void(0)" onClick=3D"foo(42)">Enlarge</a>

           =        </T8400>

 

The elements inside = T8400 (img, br, a) do not trigger endTransformingElement() but they do trigger startTransformingElement(). And again: This is only a problem if the = input XML is coming from another Cocoon processing step. It is not a problem if = the input XML is read from file system (with FileGenerator). This is actually the = most confusing part for me.

If input comes from a = file, they do generate the end events.

 

Any pointers for = me?

 

Thanks,
Alexander

 

From:= = Lochschmied, Alexander
Sent: Donnerstag, 19. November 2009 14:23
To: 'dev@cocoon.apache.org'
Subject: RE: Unbalanced tags not triggering = endTransformingElement in Transformer

 

To avoid confusion, = please swap the pattern values of my example; “OK” should be = “NOT_OK” and vice versa.

 

Let me call <br/> “unbalanced” = element as opposed to <br></br>.

I’m extending AbstractSAXTransformer and = noticed that unbalanced elements do not trigger endTransformingElement(…) if the source = (or generator) is cocoon:/something.

 

Example:

 

1. Unbalanced tags do NOT trigger = endTransformingElement(…)

        <map:match pattern=3D"NOT_OK">

           = <map:generate src=3D"cocoon:/something"/>

           = <map:transform type=3D"custom-transformer"/>

           = <map:serialize type=3D"xml"/>

    = ;    </map:match>

 

2. Unbalanced tags do trigger = endTransformingElement(…)

        <map:match pattern=3D"OK">

           = <map:generate src=3D"same_something_as_above_but_now_as_= a_file.xml"/>

           = <map:transform type=3D"custom-transformer"/>

           = <map:serialize type=3D"xml"/>

    = ;    </map:match>

 

Can somebody explain what I could possibly be = missing or is that a bug in Cocoon?

 

Thanks,
Alexander

 

From:= = Lochschmied, Alexander
Sent: Donnerstag, 19. November 2009 13:46
To: dev@cocoon.apache.org
Subject: Unbalanced tags not triggering endTransformingElement in Transformer

 

Hello!

 

Let me call <br/> “unbalanced” = element as opposed to <br></br>.

I’m extending AbstractSAXTransformer and = noticed that unbalanced elements do not trigger endTransformingElement(…) if = the source (or generator) is cocoon:/something.

 

Example:

 

1. Unbalanced tags do NOT trigger = endTransformingElement(…)

        <map:match pattern=3D"OK">

           = <map:generate src=3D"cocoon:/something"/>

           = <map:transform type=3D"custom-transformer"/>

           = <map:serialize type=3D"xml"/>

    = ;    </map:match>

 

2. Unbalanced tags do trigger = endTransformingElement(…)

        <map:match pattern=3D" NOT_OK">

           = <map:generate src=3D"same_something_as_above_but_now_as_= a_file.xml"/>

           = <map:transform type=3D"custom-transformer"/>

           = <map:serialize type=3D"xml"/>

    = ;    </map:match>

 

Can somebody explain what I’m could possibly = be missing or is that a bug in Cocoon?

 

Thanks,

Alexander

 

Alexander Lochschmied

Web Programmer - Internet and Commerce

IT Global Web Services

Information Technology

Phone:    +49 92 8771 2682

Fax       +49 92 8771 2545

Website:  www.vishay.com

 

Vishay Electronic GmbH

Geheimrat-Rosenthal-Str. 100

D-95100 Selb

Amtsgericht/County Court Hof HRB 2894,

Gesch=E4ftsf=FChrer/Managing Directors: Sieglinde Janker-Buecherl, Arnold Rohr

 

------_=_NextPart_001_01CA69C4.3BA9C55A--