Re: Convention plugin confusion

2009-06-03 Thread Roger
On Wednesday 03 June 2009 16:16:03 Dave Newton wrote: > Wes Wannemacher wrote: > > I think you have action and result confused... Instead of using > > @Action, try to add a @Result that configures a result for the string > > returned by the getDetails() call. > > I think he's saying that he was sur

Re: Convention plugin confusion

2009-06-03 Thread Musachy Barroso
That's why it is called "convention". If you want to modified the "conventional" behavior, use the annotations (@Result, @Action etc etc) musachy On Wed, Jun 3, 2009 at 6:16 AM, Dave Newton wrote: > Wes Wannemacher wrote: >> >> I think you have action and result confused... Instead of using >> @

Re: Convention plugin confusion

2009-06-03 Thread Dave Newton
Wes Wannemacher wrote: I think you have action and result confused... Instead of using @Action, try to add a @Result that configures a result for the string returned by the getDetails() call. I think he's saying that he was surprised that using the @Action annotation also meant the expected vi

Re: Convention plugin confusion

2009-06-03 Thread Wes Wannemacher
hing now works as > expected. > > Is this as it should be and, if so, why does Struts issue the misleading > message? Alternatively, how do I set things up so that the result is found > on the containing class IndexAction as Struts wants? > > Regards > -- > View this mess

Convention plugin confusion

2009-06-03 Thread RogerV
d. Is this as it should be and, if so, why does Struts issue the misleading message? Alternatively, how do I set things up so that the result is found on the containing class IndexAction as Struts wants? Regards -- View this message in context: http://www.nabble.com/Convention-plugin-confusion-tp238471