Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Mime-Version: 1.0 (Apple Message framework v609)
In-Reply-To: 
 <1E0CC447E59C974CA5C7160D2A2854EC02FECBEB@SJMEMXMB04.stjude.sjcrh.local>
References: 
 <1E0CC447E59C974CA5C7160D2A2854EC02FECBEB@SJMEMXMB04.stjude.sjcrh.local>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D73FB24C-3DAA-11D8-B3DF-000393B61B56@pace2020.com>
Content-Transfer-Encoding: 7bit
From: peter royal <proyal@pace2020.com>
Subject: Re: Accessing flow context attributes
Date: Sat, 3 Jan 2004 00:08:17 -0500
To: dev@cocoon.apache.org

On Jan 2, 2004, at 6:08 PM, Hunsberger, Peter wrote:
> show and makes perfect sense in the flow script.  So I coded a flow
> script with statements like:
>
>     cocoon.sendPage( "run/_page/" + collection, {
> "layout_type_preference" : "list" } );

> It seems to me that this really needs to be refactored into some helper
> class, though I'm not sure where?

If you follow the rabbit hole a bit more, you'll find the real secret 
which is in

org.apache.cocoon.components.flow.javascript.ScriptablePropertyHandler 
(initialized in JavaScriptInterpreter)

and the essence of which can be boiled down to:

         final Object o = unwrap( FlowHelper.getContextObject( 
objectModel ) );

         if( o instanceof Scriptable )
         {
             final Scriptable jsobject = (Scriptable)o;
             final Object[] ids = jsobject.getIds();

             for( int i = 0; i < ids.length; i++ )
             {
                 final String key = ScriptRuntime.toString( ids[i] );
                 final Object value = jsobject.get( key, jsobject );

                 //do something with the key and value now.
             }
         }

So the 'utility' could be a FlowHelper.getContextObjectAsMap or such..
-pete