Joose
JXTemplates are pretty simple to use - maybe too
simple for your app?? They can access variables
from the request, the session and the context,
eg. ${cocoon.request.contentType} or
${cocoon.session.myVariable} - so any variables
placed into the session from flow can be accessed.
Certainly beans can be used from flow, and therefore
the data made available to the JXTemplates; remember
the SOC means that JXTemplates should *not* be
accessing beans directly (I think this is a "downside" of
using XSP to access the data layer directly...)
HTH
Derek
>>> [EMAIL PROTECTED] 2004/08/30 09:03:45 AM >>>
Hi Derek,
thanks, I have to check that out, but how can I pass variables to forms
to be read from jxtemplategenerator? I have not yet looked much into
jxtemplate-stuff, but I'm using beans with XSP (not esql), so can
jxtemplate be used with beans also? There is alos that jpath stuff for
XSP so I could use that in XSP. JXTemplates have been a thing for me to
check out.
> Why not use a JXTemplateGenerator to build the
> selection list; variables created in flow can certainly
> be accessed from such pages, using the
> ${variable_name} notation. I have used this to build
> selection lists from forms, whose members vary according
> to selections from previous forms.
--
"Always remember that you are unique, just like everyone else!"
* http://iki.fi/joose/ * [EMAIL PROTECTED] * +358 44 561 0270 *
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
