Re: [jaxrs-dev] Spec clarification: UriBuilder

["Markus KARG" <markus@xxxxxxxxxxxxxxx>]

Jan,

I understand your point, but actually I doubt that any implementing product actually would support file:// URLs anywhere outside of UriBuilder. JAX-RS cleary and explicitly is solely http-centric:

1.2 Goals
The following are the goals of the API:
...
HTTP-centric The specification will assume HTTP[4] is the underlying network protocol and will provide a clear mapping between HTTP and URI[5] elements and the corresponding API classes and annotations. The API will provide high level support for common HTTP usage patterns and will be sufficiently flexible to support a variety of HTTP applications including WebDAV[6] and the Atom
Publishing Protocol[7].
...

So it wouldn't make much sense to force all implementations to support file:// URLs in UriBuilder if that is the sole place where file:// would work then.

Just My 2C
-Markus

-----Ursprüngliche Nachricht-----
Von: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] Im Auftrag von Jan Supol
Gesendet: Montag, 27. Januar 2020 11:21
An: jaxrs-dev@xxxxxxxxxxx
Betreff: Re: [jaxrs-dev] Spec clarification: UriBuilder

Markus,

UriBuilder refers to RFC 3986. I was always under the impression that 
not only the HTTP scheme should be handled by UriBuilder, but other 
described by the RFC, too. Am I wrong?

Thanks,

Jan

On 24.01.2020 17:52, Markus KARG wrote:
>
> Well, UriBuilder is defined by JAX-RS, and JAX-RS is an API for 
> REST-/over-http/ only, so I doubt there will be a cross-product 
> solution be defined by us as long as you want to use any other scheme 
> than "http". ;-)
>
> -Markus
>
> *Von:*jaxrs-dev-bounces@xxxxxxxxxxx 
> [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] *Im Auftrag von *Jonathan Gallimore
> *Gesendet:* Freitag, 24. Januar 2020 11:53
> *An:* jaxrs-dev@xxxxxxxxxxx
> *Betreff:* [jaxrs-dev] Spec clarification: UriBuilder
>
> Hi
>
> Hopefully this isn't daft question, but I'd appreciate some help. I 
> have a scenario where UriBuilder is being used to construct a file 
> URI, and append a path to it:
>
> UriBuilder.fromUri("file:///~/calendar").path("extra").build().toString()
>
> I've tried this with a couple of implementations, specifically Jersey 
> and CXF, with differing results - Jersey returns 
> file:///~/calendar/extra, which is what I personally would expect. CXF 
> on the other hand picks up "///~/calendar" as a "schemeSpecificPart" 
> of the URI, and used that, and does not append the path.
>
> I'm looking at 
> https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/jaxrs/api/rs/core/uribuilder/JAXRSClient.java - 
> its possible I've missed something, but I can't see a case that 
> specifically covers file://, or a case that specifically covers 
> UriBuilder.fromUri().path() (there are others that test cases such as 
> fromUri().port(), fromUri().host() and fromUri().scheme() etc).
>
> Could you clarify what behaviour you'd expect in this scenario, and / 
> or point me at the relevant part of the spec document (I'm struggling 
> to find a reference there too).
>
> I'd be very happy to contribute any appropriate updates to either 
> documentation or TCK tests if necessary.
>
> Many thanks
>
> Jon
>
> -- 
>
> Jonathan Gallimore
>
> http://www.tomitribe.com <http://www.tomitribe.com/>
>
>
> _______________________________________________
> jaxrs-dev mailing list
> jaxrs-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev