[jira] Commented: (WICKET-385) Move HTTP caching features out of wicket.Resource

["Peter Ertl (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924631#action_12924631 ] 

Peter Ertl commented on WICKET-385:
-----------------------------------

@martin: yeah, there were quite a few changes :-)

It's recommended to extend AbstractResource for custom resources.

When implementing abstract method    

   protected ResourceResponse newResourceResponse(Attributes attributes)

you can configure a custom ResourceResponse and utilize wicket's caching goodness.

E.g.

    ResourceResponse response = new ResourceResponse();
    response.setLastModified(.... date ....);

For details look at

  https://cwiki.apache.org/WICKET/caching-in-wicket-15.html

which describes how caching works / changed in 1.5.

I think you can close that ticket ..

> Move HTTP caching features out of wicket.Resource
> -------------------------------------------------
>
>                 Key: WICKET-385
>                 URL: https://issues.apache.org/jira/browse/WICKET-385
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: Jean-Baptiste Quenot
>            Assignee: Peter Ertl
>             Fix For: 1.5-M3
>
>
> * Add IResourceStream.isCacheable() (default to false in AbstractResourceStream)
> * Add lastModifiedTime handling in ResourceStreamRequestTarget

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.