Marc,
> A use case you might not have considered is generating URI templates
> from JAX-RS classes. Keeping the JAX-RS templates a strict subset of
> the URI templates draft makes this relatively straightforward.
> Assuming URI templates catch on (which I think they will) this seems
> useful.
This is an interesting use case.
It does not require all @Path values be a subset of a URI template syntax --
just those the author wants to be automatically converted to templates.
JAX-RS could define @Path varnames as [^}]*,
and any future @Path-to-template component could restrict itself to @Path
values that are a subset of all the possibilities.
I also think URI templates will catch on --
though I hope it is with a cleaner syntax than the current draft-03
[
http://lists.w3.org/Archives/Public/uri/2008Apr/0006.html]
> It would be possible to support an empty value for class fields and bean
> properties, definitely something to consider and I've added issue 44
> to track this.
> https://jsr311.dev.java.net/issues/show_bug.cgi?id=44
Thanks.
James Manger