Well, the value stack lets you do things like (excuse me if my attribute names are wrong):
<ww:iterator value=”myListOfDomainObjects”> <ww:push value=”mySubObject”> <ww:property value=”myActionProperty”> - this property is on my Action <ww:property value=”myDomainObjectProperty”> - this property is on my Domain Object <ww:property value=”mySubDomainObjectProperty”> - this property is on my Sub object of my Domain Object </ww:push> </ww:iterator>
OGNL is also a more powerful _expression_ language.. see some of the posts Pat sent that will build a Map for you to display in the ww:select tag….
Jason
-----Original Message-----
I've been playing around with ww2 for a month or so and I love it! However there is something I'm missing and that is the value in the OgnlValueStack. As a stack itself it is great! I can get parameters out of the request (thanks ParameterizedInterceptor). And I guess I could use it to transfer variables from Action to Action in a chained action result, but ActionContext is eaiser for that purpose. Ognl allows you to do expresson language stuff in the JSP's... but so can JSTL, therefore why would I choose OGNL expresson over JSTL? Kris Thompson |
Title: The value in the OgnlValueStack?
- [OS-webwork] The value in the OgnlValueStack? Thompson, Christopher
- [OS-webwork] TokenInterceptor Fred Lamuette
- RE: [OS-webwork] The value in the OgnlValueStac... Patrick Lightbody
- [OS-webwork] The value in the OgnlValueStack? Thompson, Christopher
- Jason Carreira