The util logicsheet is the place to look for:
<xsp:page ... xmlns:util="http://apache.org/xsp/util/2.0";>
<Cell>
<util:include-expr expr="displayField.getDisplayType()"/>
</Cell>
There are also similar functions for including XML documents from
files or URIs.
XSP is not going away. It has only lost its place as Cocoon core
technology. The majority of Cocoon developers thinks that flowscript
and templates are a better way. That is not just about using a
different language than Java (although flowscript happens to be Javascript)
but a different programming paradigm for web applications.
In my day job we are using Cocoon to run our corporate websites and
depend heavily on XSP. So I'll try my best to make sure that XSP will
also be usable in the future.
HTH, Alfred.
-----Original Message-----
From: Edward Elhauge [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 15. Dezember 2005 02:39
To: [email protected]
Subject: Cocoon JSP to Cocoon XSP porting question
Hi,
I've been porting an application I wrote last year from
and older version of Cocoon to a newer version of Cocoon.
While doing the transition I decided to use XSP instead of
the JSP generator that I had been using. Now I've got most
things working correctly except for one.
I'm using XSP code that looks like this:
<xsp:logic>
for ( int idx = 0 ; idx < numCols ; idx++ ) {
DisplayField displayField = columnsInfo[idx] ;
<xsp:content>
<Cell>
<xsp:attribute
name="type"><xsp:expr>displayField.getDisplayType()</xsp:expr></xsp:attribute>
<xsp:expr>displayField.getDisplayValue()</xsp:expr>
</Cell>
</xsp:content>
}
</xsp:logic>
which works great when "displayField.getDisplayValue()" is a simple string.
But I sometimes getDisplayValue() generates some XML that is intended to be
rendered by an XSL transform further down the pipeline. Unfortunately
for my application, the output of xsp:expr seems to be XML quoted
to use entities (such as < > etc), which of course stops the
templates from matching. This worked fine when I was using
JSP, because the JSP controlled the whole output stream.
So my question is if there is a way to turn of the entity quoting?
If not, what would be the way to go? Do I need to create a taglib
to get the effect that I want? There are so many ways to do things
in Cocoon that it gets a bit overwhelming.
Also is XSP "going away"? If so why? What would be replacing it?
I know that I wouldn't mind dropping down into Python or Perl
to do the logic, but I don't look forward to using Javascript.
--
Edward Elhauge <[EMAIL PROTECTED]>
"One allows himself to be fooled once, to be fooled twice; but he
who permits himself always to be fooled remains a fool." -- Rudolf Rocker
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please notify the sender urgently and then immediately delete the message and
any copies of it from your system. Please also immediately destroy any
hardcopies of the message. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the intended
recipient. The sender's company reserves the right to monitor all e-mail
communications through their networks. Any views expressed in this message are
those of the individual sender, except where the message states otherwise and
the sender is authorised to state them to be the views of the sender's company.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
