
|
If you were logged in you would be able to see more operations.
|
Google issue summary
|
|
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
5.1 M3
|
|
|
Issue Links:
|
Dependency
|
|
|
|
This issue is required by:
|
|
|
NXP-982 Finish to implement the action fragment
|
|
|
|
|
|
|
|
The facelets cache management needs to be improved:
what is needed is:
- the possibility to clear the cache (e.g. when a theme is modified)
- the possibility to not cache a given facelet (e.g. when rendering non-static fragments)
currently the methods used in nxthemes are to:
- set a facelet modification date in the past - works only in dev mode, this is used for reloading JSF templates without restarting the server.
- add a ?timestamp=..... at the end of the url (this leads to memory leaks since every modification forces the facelet factory to create a new facelet, and the "old" facelets are not removed)
the main problem is that there is currently no good solution for rendering non-static fragments that should never be cached (e.g. the action fragment)
with the current facelets code the only solution is to create a new FaceletViewHandler, by extending SeamFaceletViewHandler and to create a custom FaceletFactory with better cache management functionality.
this means that references to SeamFaceletViewHandler would need to be updated in the configuration files.
|
|
Description
|
The facelets cache management needs to be improved:
what is needed is:
- the possibility to clear the cache (e.g. when a theme is modified)
- the possibility to not cache a given facelet (e.g. when rendering non-static fragments)
currently the methods used in nxthemes are to:
- set a facelet modification date in the past - works only in dev mode, this is used for reloading JSF templates without restarting the server.
- add a ?timestamp=..... at the end of the url (this leads to memory leaks since every modification forces the facelet factory to create a new facelet, and the "old" facelets are not removed)
the main problem is that there is currently no good solution for rendering non-static fragments that should never be cached (e.g. the action fragment)
with the current facelets code the only solution is to create a new FaceletViewHandler, by extending SeamFaceletViewHandler and to create a custom FaceletFactory with better cache management functionality.
this means that references to SeamFaceletViewHandler would need to be updated in the configuration files.
|
Show » |
|
http://svn.nuxeo.org/trac/nuxeo/changeset/18624
...
http://svn.nuxeo.org/trac/nuxeo/changeset/18523
http://svn.nuxeo.org/trac/nuxeo/changeset/18522
...