----- Original Message -----
From: "Schmitt, Christian" <Christian.Schmitt@Dresdner-Bank.com>
To: <cocoon-dev@xml.apache.org>
Sent: Thursday, December 21, 2000 3:59 AM
Subject: AW: esql logicsheet errors (C2)
Berin,
I find that behaviour strange as well.
May be take a look at a thread called "[C2] xsp-attribute behaviour" from
about three weeks ago.
The result of that thread was a modification to the xsp.xsl file in
CVS. With pure xsp, it works. The problem is that now we are in
another logicsheet, and it is broken again. I haven't seen a
template that responds to that in the esql logicsheet....
Cheers,
Christian Schmitt
> -----Ursprüngliche Nachricht-----
> Von: Berin Loritsch [mailto:bloritsch@infoplanning.com]
> Gesendet am: Mittwoch, 20. Dezember 2000 22:54
> An: cocoon-dev@xml.apache.org
> Betreff: esql logicsheet errors (C2)
>
> Perhaps someone can help.
>
> The problem I am experiencing has to do with using the
> <xsp:attribute> tag inside the <esql:results> tag.
>
> When I do something like this:
>
> <esql:results>
> <option>
> <xsp:attribute><esql:get-int column="id"/></xsp:attribute>
> <esql:get-string column="name"/>
> </option>
> </esql:results>
>
> The generated code has this snippet:
>
> --------------------------------------------------------
>
> this.contentHandler.startElement("", "option", "option",
> xspAttr);
>
> xspAttr.clear();
>
> xspAttr.addAttribute("", "value", "value", "CDATA",
> String.valueOf(
> _esql_session.resultset.getInt("id")) + "");
>
> --------------------------------------------------------
>
> Which means that the attribute is set _AFTER_ the startElement()
> call. This is clearly wrong. This may be something that we have
> to fix in every logicsheet.
>
> Because this is effectively in a loop, the value is set for the
> following value, and this is a serious logic bomb!
>
>
> ---------------------------------------
> If you lust for Ham and Eggs, you have
> committed breakfast in your heart
> already. -- C. S. Lewis
>
|