RE: [OS-webwork] where might info on this be?
Hey all, Is there a new value stack created for every view coming from an Action? Or is it possible to back reference previous Actions executed, basically what I'm getting at is the value stack session like? If so how? From my tests it doesnt seem to be, but I could be doing it wrong =) Regards, -Andre Mermegas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Cannon-Brookes Sent: Monday, February 03, 2003 7:28 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] where might info on this be? 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 =omething 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
RE: [OS-webwork] where might info on this be?
If you want to save things in the Session, you need to do it explicitly. The ValueStack is only valid during one request / response cycle. -Original Message- From: Andre Mermegas [mailto:[EMAIL PROTECTED]] Sent: Friday, February 07, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] where might info on this be? Hey all, Is there a new value stack created for every view coming from an Action? Or is it possible to back reference previous Actions executed, basically what I'm getting at is the value stack session like? If so how? From my tests it doesn't seem to be, but I could be doing it wrong =) Regards, -Andre Mermegas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Cannon-Brookes Sent: Monday, February 03, 2003 7:28 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] where might info on this be? 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+Lang uage+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 =omething 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
RE: [OS-webwork] where might info on this be?
Ah k thats what I thought. Thanks =) Regards, -Andre Mermegas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jason Carreira Sent: Friday, February 07, 2003 5:40 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] where might info on this be? If you want to save things in the Session, you need to do it explicitly. The ValueStack is only valid during one request / response cycle. -Original Message- From: Andre Mermegas [mailto:[EMAIL PROTECTED]] Sent: Friday, February 07, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: RE: [OS-webwork] where might info on this be? Hey all, Is there a new value stack created for every view coming from an Action? Or is it possible to back reference previous Actions executed, basically what I'm getting at is the value stack session like? If so how? From my tests it doesn't seem to be, but I could be doing it wrong =) Regards, -Andre Mermegas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Cannon-Brookes Sent: Monday, February 03, 2003 7:28 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] where might info on this be? 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+Lang uage+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 =omething 2 See! http://www.vasoftware.com
Re: [OS-webwork] where might info on this be?
Andre, I'll let others tackle the other parts, but for 1) there are no implicit properties for a view. They ALL come from the action that has been run. The reason you probably can't find getErrorMessages() or getErrors() in your action, is that they are in ActionSupport. But they are still just getter methods and not 'hidden' at all ;) Cheers, Mike On 4/2/03 8:00 AM, Andre Mermegas ([EMAIL PROTECTED]) penned the words: Hi all, I was looking for some info today, but couldn't find it. 1.) All implicit properties available to a view, like today I was playing around with the doValidation() in an action using addError method, and I was trying to access this property but it wasn't clear what the value might be, I was trying errorMap which was wrong, then I google'd nad came across a blog entry that had referenced errors as the value name. So I was curious if there was a convenient repository of available properties in a view, from the framework, perhaps if needed with a when/why they are populated or created. 2.) A good explanation of how exactly the value stack works, Its kind of mysterious to me at this point and I'd really like to have a firm grasp on how to make use of it. How do I know where I am on it, how do I know what is available to me, How did I get where I am on it, etc... 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. I'm sorry if these questions have been answered multiple times before, but I'm generally a good google'r and reader, I just haven't been able to find these answers documented as such. Regards, -Andre Mermegas --- 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
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+Syntax 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
RE: [OS-webwork] where might info on this be?
Ah. That makes sense. Regards, -Andre Mermegas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Cannon-Brookes Sent: Monday, February 03, 2003 5:08 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] where might info on this be? Andre, I'll let others tackle the other parts, but for 1) there are no implicit properties for a view. They ALL come from the action that has been run. The reason you probably can't find getErrorMessages() or getErrors() in your action, is that they are in ActionSupport. But they are still just getter methods and not 'hidden' at all ;) Cheers, Mike On 4/2/03 8:00 AM, Andre Mermegas ([EMAIL PROTECTED]) penned the words: Hi all, I was looking for some info today, but couldn't find it. 1.) All implicit properties available to a view, like today I was playing around with the doValidation() in an action using addError method, and I was trying to access this property but it wasn't clear what the value might be, I was trying errorMap which was wrong, then I google'd nad came across a blog entry that had referenced errors as the value name. So I was curious if there was a convenient repository of available properties in a view, from the framework, perhaps if needed with a when/why they are populated or created. 2.) A good explanation of how exactly the value stack works, Its kind of mysterious to me at this point and I'd really like to have a firm grasp on how to make use of it. How do I know where I am on it, how do I know what is available to me, How did I get where I am on it, etc... 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. I'm sorry if these questions have been answered multiple times before, but I'm generally a good google'r and reader, I just haven't been able to find these answers documented as such. Regards, -Andre Mermegas --- 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
RE: [OS-webwork] where might info on this be?
Ok, so that makes sense too. Thanks. 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
Re: [OS-webwork] where might info on this be?
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
RE: [OS-webwork] where might info on this be?
Yes, this should be on the wiki... Link it to the example page I just put up about getting the values from an action... -Original Message- From: Mike Cannon-Brookes [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 7:28 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] where might info on this be? 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+Syn ta 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 =omething 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
Re: [OS-webwork] where might info on this be?
Looks good - and even if it's wrong, it should go on the wiki so people can correct it. On Tue, 4 Feb 2003, Mike Cannon-Brookes wrote: 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 http://www.vasoftware.com ___ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork - Joseph B. Ottinger [EMAIL PROTECTED] http://enigmastation.comIT Consultant --- 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
