Try it again using a String property, to be sure it is not a problem with the type conversion.
On 11/27/06, Tarek Nabil <[EMAIL PROTECTED]> wrote:
To clear my doubts, I re-built this application using WW 2.2.4. I expected that it will work perfectly and that would prove it's some sort of a bug. To my surprise, it exhibited the exact same behavior!!!!! Now, since it's quite remote that such a drastic bug exists in WW 2.2.4, I'm starting to think that maybe the behavior I expect is not the correct one. Now, could someone please clarify whether the following is true? 1- When parameters are available in the "query string", those parameters are made available to the action through " ActionContext.getContext().getParameters()". Is this true? 2- If a property on the action has the same name as one of those parameters then the framework will attempt to set the property with the parameter's name. This is not what is currently happening. Since WW 2.2.4 is supposed to be production quality then I'm guessing that there must be something wrong with the configuration. It can not be that some configuration I've provided is wrong, simply because I have not provided any. It could be, though, that some configuration is missing. The changes I've made to the application to get it to work with WW 2.2.4 is minimal, so I won't go ahead and copy all the files here.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
