Johannes Textor wrote:

OK, I thought it would work the same way in flow like it does in XSP,
but apparently I was wrong ... so I'll put up a bugzilla entry about the
docs.

The docs are correct, but a little misleading. I have therefore changed the page to say:


       <map:flow language="javascript">
          <map:script src="myApplication.js"/>
       </map:flow>
       <map:pipelines>
          <map:pipeline>
             <map:match pattern="index.html">
                <map:call function="showIndexPage">
                  <map:parameter name="paramName" value="Value"/>
                </map:call>
             </map:match>
          </map:pipeline>
       </map:pipelines>

and:
function showIndexPage() {
var param = cocoon.parameters.paramName;
sendPage("private/index.html", {param: param});
}
This'll go onto the site next time someone updates it. Speak up if anything above is incorrect.


Regards, Upayavira


beyaNet Consultancy wrote:


Johannes,
I have it. The correct syntax is: cocoon.parameters.svgWidth;

Peter
On 25 Apr 2004, at 13:53, beyaNet Consultancy wrote:

    Johannes,
    I do not have a bugzilla account, so feel free to log it. Also, I
    am now getting an error which says:

    org.apache.avalon.framework.CascadingRuntimeException:
    getParameter is not a function.

Any reason why this is?? I am using version 2.1.4 of cocoon.

Peter


On 25 Apr 2004, at 13:39, Johannes Textor wrote:


        true, the docs seem incorrect (or misleading at least).
        does it work out when using the parameter object ? if so,
        can you report the bug in bugzilla ? I can also do it if you
        don't have a bugzilla account.

beyaNet Consultancy wrote:

            Thanks guys,
            but the source of my initial information was from the
            actual cocoon site on flow!, which is obviously incorrect:

http://cocoon.apache.org/2.1/userdocs/flow/sitemap.html

Read code specified in the *function* section...


---------------------------------------------------------------------


        To unsubscribe, e-mail: [EMAIL PROTECTED]
        For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to