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
> @PathParam("CDEF") PathSegment ps
? The first or the second (or last) of this path segments? Or should
this all be treated as one path segment?
If the last option, should this be treated as one path segment ever? If
I use
> @Path(value="{VAR}", limited=false)
and VAR matches "jkl/mno/pqr", than this are three path segments, e.g.
from UriInfo.getPathSegments(), in my understanding. I think it will
causes misunderstanding, if we define "jkl/mno/pqr" as one path segment,
if it is matched by one variable.
A possible solution is to forbid limited=false for parameters of type
PathSegment.
*_at_Encoded*
And another small point: The end of the javadoc of @Encoded could be
supplemented with something like ", including bean setters and also
annotated fields" (will result in "Using this annotation [@Encoded] on a
class will disable decoding for all parameters of all methods, including
bean setters and also annotated fields".
Is it right, that @Encoded is also allowed in providers (useful for bean
setters and annotated fields)?
best regards
Stephan