Return-Path: 
 <cocoon-dev-return-20837-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 30574 invoked by uid 500); 10 Jan 2002 20:52:23 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 30562 invoked from network); 10 Jan 2002 20:52:21 -0000
Date: Thu, 10 Jan 2002 21:52:24 +0100 (CET)
From: Torsten Curdt <tcurdt@dff.st>
X-X-Sender: <tcurdt@mogh.dff.local>
To: <cocoon-dev@xml.apache.org>
Subject: RE: XSP bug?
In-Reply-To: <006401c19a15$51dfb290$90a4558b@vgritsenkopc>
Message-ID: <Pine.LNX.4.31.0201102133370.8699-100000@mogh.dff.local>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Thu, 10 Jan 2002, Vadim Gritsenko wrote:
> >  ...
> >  <tag>
> >     <xsp:logic>
> >        try {
> >
> >          <ns:list>
>              <xsp:logic>
> >            Collection list = ...
> >
> >            for (Iterator iterator = list.iterator();
> iterator.hasNext();) {
> >              MyObj o = (MyObj) iterator.next();
> >
> >              <ns:MyObj>
>                  <ns:name><xsp:expr>o.getName()</xsp:expr></ns:name>
> >              </ns:MyObj>
> >
> >            }
>              </xsp:logic>
> >          </ns:list>
> >
> >        }
> >        catch(Exception e) {
> >          <xsp:content>Error:
> > <xsp:expr>String.valueOf(e)</xsp:expr></xsp:content>
> >        }
> >     </xsp:logic>
> >  </tag>
> >  ...
>
> IIRC, this works.

Well, it should... but seems not to...

>
>
> > Unfortunately the current implementation will treat any java code
> > within a tag inside the xsp logic tag as text nodes - not as java.
>
> How you propose to rewrite this example:
>
> <xsp:logic>
>   try {
>     <para>
>       This is not a java code, but the document content.
>       <xsp:expr>new Date()</xsp:expr>
>     </para>
>   ...
> </xsp:logic>

 <xsp:logic>
   try {
     <para>
       <xsp:content>This is not a java code, but the document content.</xsp:content>
       <xsp:expr>new Date()</xsp:expr>
     </para>
   ...
 </xsp:logic>

IIRC that's how it was in the old days?!;)

> > If we can aggree that this behaviour is wrong I'd like to change
> > the xsp.xsl accordingly.
>
> I can't right now. May be I just do not get what you are proposing.

Hope it is clearer now
--
Torsten


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org