--- Hardy Ferentschik wrote: > Currently I get the following error: > No result defined for action SearchAction and result > input
If validation fails the framework will try to bring you back to the "input" result. You don't appear to have one; this will cause a problem. > validation on 'complex' datatypes as I am trying to > do with SearchParam? Or do I need keywords and locations > as simple String properties in the Action directly? You can do what you're doing. In this case I'm not sure what you're gaining by using the SearchParam object, but without knowing why you've chosen that way, it's hard to say. > I also tried to apply the ExpressionValidator > annotation directly on setSearchParam method, > but then I got the following error message: > > >>> > caught OgnlException while setting property > 'methodName' [...] methodName? I'm not sure why that's happening; the actual annotation you used might be helpful. d. ____________________________________________________________________________________ Get your own web address. Have a HUGE year through Yahoo! Small Business. http://smallbusiness.yahoo.com/domains/?p=BESTDEAL --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
