Hello,
I'm using 1.0.3 and I'm bumping up against this issue
(
https://jersey.dev.java.net/issues/show_bug.cgi?id=238), but I
probably don't have time to wait for the update release since I need
to release my webapp pretty soon. Could you recommend the best course
of action for me to fix this in the near term? ie. which do you think
would be the most "stable" solution:
- get the head of the repo or some tagged version and work with that
- patch 1.0.3 with some minimal set of changes (and if so which patches?)
- use jersey-1.1.0-ea instead
- something else
Thanks!
Keith