RE: [OS-webwork] Need help with WW2 form processing...

2003-10-11 Thread Peter White
PM > To: [EMAIL PROTECTED] > Subject: RE: [OS-webwork] Need help with WW2 form processing... > > Matt, > > Thanks for the tip, it works like a charm! Now I have to > figure out the best way to adapt it to our situation but I'm > quite pleased to know that WW is able to persis

RE: [OS-webwork] Need help with WW2 form processing...

2003-10-11 Thread Peter White
[EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Matt Ho > Sent: Friday, October 10, 2003 5:52 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Need help with WW2 form processing... > > I'm clearer now on what you're looking to do. If > > that[0

Re: [OS-webwork] Need help with WW2 form processing...

2003-10-10 Thread Matt Ho
Francisco Hernandez wrote: why do you use that OgnlList instead of just ArrayList? Ognl doesn't (currently) instantiate new objects when users submit info. OgnlList fills in this blank by instantiating objects of the specified instance. So, without OgnlList, that[0] would always resolve to null

Re: [OS-webwork] Need help with WW2 form processing...

2003-10-10 Thread Francisco Hernandez
why do you use that OgnlList instead of just ArrayList? Matt Ho wrote: I'm clearer now on what you're looking to do. If that[0].Cheetah.name that[1].Monkey.name works, then ModelDriven should work just fine. Having said that, the following code snippet should work for you (haven't tested it th

RE: [OS-webwork] Need help with WW2 form processing...

2003-10-10 Thread Peter White
Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Matt Ho > Sent: Friday, October 10, 2003 5:51 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Need help with WW2 form processing... > > I'm clearer now on what you're lo

Re: [OS-webwork] Need help with WW2 form processing...

2003-10-10 Thread Matt Ho
I'm clearer now on what you're looking to do. If that[0].Cheetah.name that[1].Monkey.name works, then ModelDriven should work just fine. Having said that, the following code snippet should work for you (haven't tested it though). This is slightly different than what you asked for in that what

Re: [OS-webwork] Need help with WW2 form processing...

2003-10-10 Thread Matt Ho
I'm clearer now on what you're looking to do. If that[0].Cheetah.name that[1].Monkey.name works, then ModelDriven should work just fine. Having said that, the following code snippet should work for you (haven't tested it though). This is slightly different than what you asked for in that what

RE: [OS-webwork] Need help with WW2 form processing...

2003-10-10 Thread Peter White
MAIL PROTECTED] On > Behalf Of Matt Ho > Sent: Friday, October 10, 2003 11:23 AM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Need help with WW2 form processing... > > I'm not sure exactly of the problem you're having. However, > there's a write up on mo

Re: [OS-webwork] Need help with WW2 form processing...

2003-10-10 Thread Matt Ho
I'm not sure exactly of the problem you're having. However, there's a write up on model driven on http://wiki.opensymphony.com/space/Xwork+Interceptors To summarize, declaring something as ModelDriven just puts it on the top of the value stack so when your parameters get resolved, the model g