You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@wink.apache.org by David Calavera <da...@gmail.com> on 2010/05/06 12:46:24 UTC
Nested resources with @Parent
Hi,
I was taking a look to you documentation and I bumbed into the annotation
@Parent. I was wondering if with it I can build a route path like this:
/service/{serviceId}/resource/{resourceId}
is that possible??
thank you
Re: Nested resources with @Parent
Posted by David Calavera <da...@gmail.com>.
Cool, thanks for the reply, that simplify my choose a lot
On Thu, May 6, 2010 at 1:04 PM, Michael Elman <el...@apache.org> wrote:
> Short answer: yes.
>
> Long answer:
> The annotation @Parent means that you can set a "parent" bean.
> Actually this means that the path of "parent" will be inserted before the
> path of "child".
> So if you have "parent" with path " /service/{serviceId}" and child with
> path "resource/{resourceId}"
> the actual child path will be "/service/{serviceId}/resource/{resourceId}"
>
>
> On Thu, May 6, 2010 at 1:46 PM, David Calavera <da...@gmail.com>wrote:
>
>> Hi,
>>
>> I was taking a look to you documentation and I bumbed into the annotation
>> @Parent. I was wondering if with it I can build a route path like this:
>>
>> /service/{serviceId}/resource/{resourceId}
>>
>> is that possible??
>>
>> thank you
>>
>>
>
Re: Nested resources with @Parent
Posted by Michael Elman <el...@apache.org>.
Short answer: yes.
Long answer:
The annotation @Parent means that you can set a "parent" bean.
Actually this means that the path of "parent" will be inserted before the
path of "child".
So if you have "parent" with path " /service/{serviceId}" and child with
path "resource/{resourceId}"
the actual child path will be "/service/{serviceId}/resource/{resourceId}"
On Thu, May 6, 2010 at 1:46 PM, David Calavera <da...@gmail.com>wrote:
> Hi,
>
> I was taking a look to you documentation and I bumbed into the annotation
> @Parent. I was wondering if with it I can build a route path like this:
>
> /service/{serviceId}/resource/{resourceId}
>
> is that possible??
>
> thank you
>
>