Ron,
Thanks again.
I was hoping, some one could throw some light from a holistic point of view on this particular behavior with JAX-RS, Jersey2.4, JDK1.7, and the URI mismatch scenario posed.
Right from,
1. How is HTTP supposed to work?
2. How a Java based HTTP container(eg.
Tomcat) expected to behave under the circumstances?
3. What does the JAX-RS spec say about it, and
4. Is there some anomaly (specified or unspecified) by the Jersey reference implementation?
I would be grateful for the information/answers to the questions posed above or even a re-direction to any literature/blog/online learning tutorial etc.
Again, thanks in advance.
Regards,
Anirudh.