Stephan Koops wrote:
> Hi,
>>>> *_at_PathParam(...) PathSegment*
>>>> while thinking how to implement @PathParam for a PathSegment: an uri
>>>> template variable could be represent a part of a path segment (e.g.
>>>> @Path("ab{CD}ef{GH}") ), but also multiple path segments: (e.g.
>>>> @Path(value="ab{CDEF}gh", limited=false) ).
>>>> For the first case it seems useful to me to return for
>>>>> @PathParam("CD") PathSegment ps
>>>> and for
>>>>> @PathParam("GH") PathSegment ps
>>>> the same (or two equal) objects implementing PathSegment.
>>>> But what happens, if CDEF in @Path(value="ab{CDEF}gh",
>>>> limited=false) matches "12/34" or "12/34/56"? What is the value of
>>> IMO, limited=false has no affect for @Path(value="ab{CDEF}gh",
>>> limited=false.
>> Right, the template var has to be at the end of the URI for
>> limited=false to have any effect.
> Ok, then we have
>> @Path(value="ab{CDEF}", limited=false)
> and
>> @PathParam("{CDEF}") PathSegment ps
> with "ab12/34/56" to match. What it the path in the PathSegment? "12"?
> "56"? "12/34/56"? The first and second is IMO not useful and the last is
> not realy one path segment.
IMO, if we're not going to support my idea of PathSegment<List>, this
should be an error. Having a path Segment value of "12/34/56" sort of
defeats the purpose of PathSegment and is really not within the
definitin of PathSegment.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com