Almost, but not quite. :)

RULES OF THE STACK:

1) The stack is just a stack of objects.

2) Initially the stack contains the Action executed (this is why as you say
value="foo" calls action.getFoo())

3) New objects are placed onto the stack during the body of various tags
(like <ww:iterator> or <ww:property> for example)

4) Using the expression language you can navigate UP the stack (ie ../ to
move up the stack, / to root an expression from the top of the stack)

5) Using the expression language you can navigate DOWN the object graph from
any point on the stack (ie / to move down the object's methods)


How is that for a brief primer? Should we put this on the Wiki? Anyone have
any other rules to add?

-mike

On 4/2/03 10:15 AM, "Andre Mermegas" ([EMAIL PROTECTED]) penned the
words:

> Yeah, I've been looking at the wiki and saw that document, it is very
> helpful for the syntax, thanks.
> 
> As far as the value stack goes, I've been thinking about it a bit, and
> this is what I've come up with, The stack begins with whatever
> properties comes from the Action directly, so "errors" is a base
> property because it has a getter/setter in ActionSupport and through
> inheritance my Action.
> As witnessed by:
> 
> <ww:iterator value="errors">
>  key=<ww:property value="key"/>, value=<ww:property
> value="value"/><br>
> </ww:iterator>
> 
> Anything attached to the Action say for instance a bean that has a
> getter/setter; its properties are not visible from the base of the stack
> because the getters and setters for the beans properties are not in the
> action but are in the bean, so to access them you must prefix the
> property value with objectName/propertyname.
> 
> As witenessed by:
> name=<ww:property value="testBean/name"/>
> 
> I think I get it now.
> 
> Regards,
> -Andre Mermegas
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of
> boxed
> Sent: Monday, February 03, 2003 5:36 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [OS-webwork] where might info on this be?
> 
>> 3.)     A list of all possible views.properties entries like
>> action.* what is available and what does it do. I'm aware of the basic
> ones:
>> foo.action, foo.success, foo.error, foo.none, foo.input, foo.login for
>> having looked at the Action interface but are there any other
> possible? I
>> don't know.
> 
> The suffixes are just strings. An action returns a String, and that
> return
> value is what you map in the views.properties file. Nothing more,
> nothing
> less.
> 
>> 2.)     A good explanation of how exactly the value stack works,
> 
> The wiki has a reference:
> http://www.opensymphony.com:8668/space/WebWork+Expression+Language+Synta
> x
> 
> Anders Hovmöller
> [EMAIL PROTECTED] http://boxed.killingar.net
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Opensymphony-webwork mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Opensymphony-webwork mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to