It is a generic caching API. If it does not fit well, we should create some JSR-107 JIRA issues :-)
On 16.06.2011, at 11:11, Markus KARG wrote:
> Well, this depends on the API designed in JSR-107. If that fits well, we can
> use it. But if not?
>
>> -----Original Message-----
>> From: Adam Bien [mailto:abien_at_adam-bien.com]
>> Sent: Donnerstag, 16. Juni 2011 10:07
>> To: jsr339-experts_at_jax-rs-spec.java.net
>> Subject: [jsr339-experts] Re: ...and JSR-107 JCache?
>>
>> If we decide to support a cache solution, we should use JCache and rely
>> on its semantics. We should not even think of doing it by us :-)
>> On 15.06.2011, at 21:27, Bill Burke wrote:
>>
>>> Those are just examples of using interceptors/filters, not part of
>> the spec. At least that's what Marek said.
>>>
>>> On 6/15/11 2:27 PM, Adam Bien wrote:
>>>> Hi RESTafaris,
>>>>
>>>> I just spotted the CacheEntry class in the
>> jaxrs.examples.client.cache package. Shouldn't we just reuse the JSR-
>> 107 JCache as internal implementation and delegate to it?
>>>> It will become a part of the Java EE 7 spec anyway. IMHO we should
>> avoid overlapping with other specs as much as possible.
>>>>
>>>> Just a spontaneous idea,
>>>>
>>>> cheers,
>>>>
>>>> adam
>>>>
>>>>
>>>>
>>>
>>> --
>>> Bill Burke
>>> JBoss, a division of Red Hat
>>> http://bill.burkecentral.com
>>
>
>