Actions you should take

Getting Started
FAQ
Migrating your GlassFish site

Hello,

Assume there is a root resource with <at> Path("/") with a resource method for <at> Path("{path:.*}") and a root resource for <at> Path("/foo") with no method matching the subpath "bar". Is it ok for an implementation to forward the request for /foo/bar to the method of the first root resource or is it necessary to answer with 404?

Cheers,
Reto

CreditSuisse
VP - Application Development
Tel: 212-538-5703 

Please follow the attached hyperlink to an important disclosure:  http://www.credit-suisse.com/legal/marketcommentary

==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================

Hello -

Can someone please give me an authoritative answer about the differences between UriBuilder.build() and UriBuilder.buildFromEncoded() and they way they have to deal with quieries containing percent-encoded data.

1. UriBuilder.fromUri("http://localhost:8080").queryParam("name", "%20").build();
2. UriBuilder.fromUri("http://localhost:8080").queryParam("name", "%20").buildFromEncoded();
3. UriBuilder.fromUri("http://localhost:8080").replaceQuery("name=%20").build();
4. UriBuilder.fromUri("http://localhost:8080").replaceQuery("name=%20").buildFromEncoded();

I'm seriously confused. Specifically, it seems totally wrong that the way '%' is dealt with depends on how a query is built (i.e, from individual parameters or from a ready string).

I'd appreciate if you can give the answers to 1-4 above.
Besides, what is the way in UriBuilder to have a literal '%' passed on ? Example, should it be :

UriBuilder.fromUri("http://localhost:8080").queryParam("name", "%2520").buildFromEncoded();

or

UriBuilder.fromUri("http://localhost:8080").replaceQuery("name=%2520").build();

How about

UriBuilder.fromUri("http://localhost:8080").replaceQuery("name=%2520").buildFromEncoded();

versus

UriBuilder.fromUri("http://localhost:8080").replaceQuery("name=%2520").build();

Thanks !

Sergey

Hi All

I have to fix a couple of disabled UriBuilder tests which are going to block the next CXF release unless fixed and I'm looking at these tests and feeling confused given that it's been awhile since I was looking into the relevant code.

The question is about dealing with ' ' and '+' in the query component of URI.
I can see two UriBuilder tests adapted from the similar JAXRS TCK 1.1 tests, one using the replaceQuery method and the other one - queryParam.

One test does uriBuilder.queryParam(name, "x y").build() and expects : name=x+y.
The other one does uriBuilder.replaceQuery("name=x y").build() and expects :  name=x%20y

I think something is wrong there. Irrespectively of which method is used to create a query component, the end result, as far as UriBuilder is concerned, should be the same.

Now, I can see another test requirement where we do

uriBuilder.replaceQuery("name=x+y&name=%20").build()

and expect

name=x+y&name=%20

Given the build() leads to encoding % to %25, we need to decode "name=x+y&name=%20" first, otherwise we'd get %2520 for the 2nd value of name.

Clearly we can not decode '+' to ' ' here otherwise we'd not be able to reproduce the original query. Which makes me think that the test which expects "x y" be encoded as "x+y" is wrong.

So I'm thinking :

- test that does uriBuilder.queryParam(name, "x y").build() and expects : 'name=x+y' is wrong
- decoding 'x+y' to 'x y' is not required

Is it correct ?

Any clarifications will be appreciated
cheers, Sergey

Hello,

Is there a standard way (i.e. one that doesn't just work on servlet based implementations) to get client certificates (X509Certificate) in a jax-rs root resource?


Cheers,
reto

Hi,
I was reading the JAX-RS spec and I had a quick question.

I couldn’t find the meaning of X in JAX-RS ==> Java API for RESTful Web Services. Seriously, what does the X stand for?

My only guess is – it got carried over from JAX-WS ==>Java API for XML Web Services. Am I right?


Thanks,
Stephen

It seams that the specification has talked  about that. But Could you give me a concrete  example?


--
Thank you.