On 6/23/02 2:09 PM, "Sylvain Wallez" <[EMAIL PROTECTED]> wrote:
> Christian Haul wrote: >> Ovidiu, Sylvain, >> >> I spend some time to look into both treeprocessor and flow. In order >> to achieve the above and input modules in sitemap I would need two >> things: >> >> a) reference to the sitemap's component manager in flow. I have found >> two possibilities, either extending some routines' signatures (many >> modifications) or placing it into the Environment. But I seem not to >> find the place where it is created. It seems related to >> CocoonComponentManager.getCurrentEnvironment() but I didn't quite >> understand the mechanics. > > > Look at o.a.c.components.flow.JavaScript.JSCocoon, which makes some > Cocoon objects available to the flow : it already has a ComponentManager > attribute, but doesn't publish it to the script. This should be a simple > matter of adding a jsGet_manager method (Ovidiu, am I right ?). Yes, adding such a method should work. For an introduction on how to make objects and classes available to JavaScript, check out this tutorial: http://www.mozilla.org/rhino/tutorial.html Regards, Ovidiu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
