Re: ERRest example of non-model method with parameters
Re: ERRest example of non-model method with parameters
- Subject: Re: ERRest example of non-model method with parameters
- From: Mike Schrag <email@hidden>
- Date: Thu, 29 Nov 2012 11:39:03 -0500
The preferred way is whichever way you prefer :) If it feels too verbose, don't use it. They're doing (give or take) the same thing internally.
ms
On Nov 29, 2012, at 11:36 AM, Roger Perryman <email@hidden> wrote:
> Thanks Mike! That clears up some of the fog. I'm still not sure what the "preferred" way is for the community, though. Or is there a preferred way? The annotations are VERY verbose and remind me of Spring/Struts.
>
> On Nov 29, 2012, at 11:13 AM, Mike Schrag wrote:
>
>>>> I never used the annotations. The only time I would use them is if I have to register like 100 controllers, just to not have to do it in Application.
>>>
>>> If you are not using the @PathParam annotation, then how do you specify the parameters for the method? I assume you would use routeObjectForKey to access them. Does this mean there is no formal method signature? This would be similar to accessing parameters from a DirectAction call.
>> yes … route controller methods ARE direct actions (if you look at the inheritance hierarchy, you'll see that your controller is a DirectAction). so without the trickery of the annotations, you would lookup the parameters using the routeObjectForKey methods, or you can just fall back to standard DA tools and call request().stringFormValueForKey(..) etc.
>>
>> ms
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden