Seth,
Yep, that looked like the problem.
> Is there a guru on the list that can comment on this pattern?
I'm not one of those but I think I can help...
It's not clear from your code why you feel you need to do any initialization
at all, the following will work just fine:
<?xml version="1.0"?>
<?cocoon-process type="xsp"?>
<xsp:page language="java"
xmlns:xsp="http://apache.org/xsp";
xmlns:xsp-request="http://apache.org/xsp/request/2.0";>
<store>
<store-name>
<xsp-request:get-parameter name="store-name"/>
</store-name>
</store>
</xsp:page>
As for your second example,
<xsp:page ...>
<xsp:logic>
String s_name;
public void init() {
s_name = <xsp-request.../>
}
</xsp:logic>
<xsp:logic>
init();
</xsp:logic>
<store>
<name><xsp:expr>getStoreName()</xsp:expr></name>
</store>
<xsp:page>
Both of the first two <xsp:logic> blocks will appear in the static section
of the page's class and therefor init() perhaps wouldn't have been called.
If you feel like you need to do other initialization or protect access to
the value (your getStoreName() kind of came out of the blue), then I'd think
a better way would be to call init from within that function.
But you shouldn't need to, you can pass default values to
<xsp-request:get-parameter> instead.
Per
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
