Thank you. I have updated the issue priority for you. We'll look into the issue and try to resolve it in the next dev iteration.
Marek
On 18 Jun 2014, at 07:36, Guy Rouillier <guy.rouillier_at_gmail.com> wrote:
> Marek, please see https://java.net/jira/browse/JERSEY-2553. I couldn't find anywhere to attach files, so I put the two zipped samples on my Google Drive and provided links in the issue. I also meant for this issue to be major instead of critical, but apparently I cannot edit the issue.
>
> Thanks.
>
> On 6/17/2014 11:58 AM, Marek Potociar wrote:
>> Hi Guy,
>>
>> At first sight, this looks like a potential bug in Jersey 2.x. Can you
>> please file a new Jira issue <https://java.net/jira/browse/JERSEY> and
>> attach a reproducible example to it to expedite the evaluation?
>>
>> Thank you,
>> Marek
>>
>> On 17 Jun 2014, at 08:49, Guy Rouillier <guy.rouillier_at_gmail.com
>> <mailto:guy.rouillier_at_gmail.com>> wrote:
>>
>>> This issue is a blocker for our upgrade to Jersey 2. Is the Jersey
>>> team aware of this problem? Would some sample code help?
>>>
>>> Thanks.
>>>
>>> On 6/10/2014 2:52 AM, Guy Rouillier wrote:
>>>> We use the proxy client for all our webservices; that proxy is an
>>>> excellent productivity enhancer. We originally wrote our Jersey
>>>> webservices using Jersey 1.8. Many of our resource methods take query
>>>> params of type java.util.Date. Here's one example (abbreviated):
>>>>
>>>> @GET
>>>> @Produces({ MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON })
>>>> @Path("summary/customer/{custId}")
>>>> public List<TicketData> getCustomerSummary (
>>>> @PathParam("custId") String custId,
>>>> @QueryParam("startDate") Date startDate,
>>>> @QueryParam("endDate") Date endDate, @QueryParam("startIndex")
>>>> int startIndex, @QueryParam("count") int count);
>>>>
>>>> This works fine with Jersey 1. However, when we upgraded the project to
>>>> use Jersey 2, we now get 404 Not Found if either of the supplied dates
>>>> is non-null; if they are both null, then the method still works.
>>>>
>>>> This seems to be a server-side issue. I ran both a 1.8 client and a 2.9
>>>> client against the 1.8 server version, and both worked. But neither
>>>> works against the 2.9 server version.
>>>>
>>>> I turned on the LoggingFilter to see what URL gets to the server; both
>>>> 1.8 and 2.9 produce the same thing:
>>>>
>>>> http://localhost:8081/api/rest/v1/ticket/summary/customer/MC000577?
>>>> status=Open&severity=1,3,5&startDate=Fri+May+10+00:00:00+EDT+2013&startIndex=0&count=100
>>>>
>>>>
>>>> I'd appreciate some pointers on how to get this working under 2.9. This
>>>> is one of our last hurdles for the upgrade.
>>>>
>>>> Thanks.
>>>>
>>>
>>>
>>> --
>>> Guy Rouillier
>>>
>>> ---
>>> This email is free from viruses and malware because avast! Antivirus
>>> protection is active.
>>> http://www.avast.com
>>>
>>
>
>
> --
> Guy Rouillier
>
> ---
> This email is free from viruses and malware because avast! Antivirus protection is active.
> http://www.avast.com