> From: Torsten Curdt [mailto:[EMAIL PROTECTED]]
>
> On Thu, 10 Jan 2002, Vadim Gritsenko wrote:
> > > ...
> > IIRC, this works.
>
> Well, it should... but seems not to...
No, it works.
<snip/>
> <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?!;)
Please, give me a break! I did not write lots of XSP those days, but I
do remember that it was not this way. Check this out:
http://cvs.apache.org/viewcvs.cgi/xml-cocoon/samples/xsp/page.xml?rev=1.
5&content-type=text/vnd.viewcvs-markup:
<xsp:logic>
Enumeration e = request.getHeaderNames();
if ((e != null) && (e.hasMoreElements())) {
<p>Here are the request headers...
There is no escaping here! XSP automagically switches from Java to
content once any tag or <xsp:content> is found.
</p>
<list title="Request Headers">
And that's exactly the reason why xsp:logic is required again to switch
from content to Java:
<xsp:logic>
while (e.hasMoreElements()) { ... }
</xsp:logic>
</list>
}
</xsp:logic>
That's how it was 2 years ago ;P
(Revision 1.5 , Sat Jan 8 07:19:41 2000 UTC (24 months ago) by Ricardo)
> > > 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
Yep. Do you want to patch Cocoon 1 also? ;)
Vadim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
