Content Scoping

Thought I would throw out a quick idea and see what other JP users think. I
was thinking it might be nice to introduce a little scoping when it comes to
content actions.

Currently in JP:
Page actions run first
Template actions run when merge is called
Content actions run for each included content

If content1 sets some values in the JP context they are currently available
to content1 and everything which follows.
If content1 overrode some value defined in a page action, it is no longer
available.

I am proposing content actions be limited in scope to just the included
content.

page action:
context.put("foo", bar");

include content1
content1 action:
context.put("foo", "nobar");
foo = nobar for content1

include content2
no action for content2
foo = bar for content2

I'd like to hear thoughts on this..

-Andy




-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps