Implement RFC6570 (URI Template) Level 2

[glassfishrobot]

Are there plans to implement the Level 2 of the URI template specification? That would be greatly useful for framework developers who want to base their implementations on the JSR-356.

[glassfishrobot]

@glassfishrobot Commented
Reported by ccidraljr

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA WEBSOCKET_SPEC-222

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/websocket-spec/issues/222
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @pavelbucek

[markt-asf]

This change would need to wait until Jakarta EE 10.
Level 2 introduces reserved string expansion and fragment expansion. We can ignore fragment expansion as clients (should) never send the fragments to the server. That leaves reserved string expansion.
This would need careful specification as a template such as /{+a}/{+b} does not have an unambiguous mapping to /zzz/yyy/xxx. We need to find a wording that disallows the ambiguous mappings without blocking needed functionality. Some examples of what users would like to be able to do would be helpful here.

[joakime]

We would need to be careful about lookup order as well.