I believe it is technically possible to do this, but not at all
intuitive right now. This is probably my number one improvement
request for the REST plugin.
You should be able change the wildcard mapper to one that recognizes
named wildcards then use them in your namespace annotation like this:
@Namespace("/book/{bookId}")
As I said, it really needs work as this is a huge deficiency in the
REST plugin right now, but the reason I haven't just made this easier
as I'm toying with the idea of borrowing the URI mapping behavior from
Jersey, which I find very intuitive, if a bit un-Struts/xwork-like.
Don
On Tue, Jun 17, 2008 at 9:10 AM, Mike Watson <[EMAIL PROTECTED]> wrote:
> Well that'd be nice but I'm really struggling to get it to behave the
> way I want. Any thoughts on how I might do this?
>
> 2008/6/17 Dave Newton <[EMAIL PROTECTED]>:
>> --- On Mon, 6/16/08, Mike Watson <[EMAIL PROTECTED]> wrote:
>>> Can anybody suggest where I would start in an attempt to
>>> implement this hierarchical model?
>>
>> The existing REST plugin?
>>
>> Just an idea.
>>
>> Dave
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
