[
https://jira.jboss.org/jira/browse/JBSEAM-3033?page=com.atlassian.jira.pl...
]
Daniel Roth updated JBSEAM-3033:
--------------------------------
Attachment: cache.patch
This is one way of doing it which works well. The developer controls cacheKey for each
image (so that he/she may invalidate them when necessary) and may also set a flag for
removing a key.
The cache used is the one provided by the CacheProvider, which the developer may configure
as he/she likes.
Using this patch on pages with lots of images ("webshop") makes the app
significally faster.
Example
<s:graphicImage value="#{bean.file}" cache="true"
cacheKey="#{bean.file.id}-size0.5"
invalidate="#{bean.file.dirty}">
<s:transformImageSize factor="0.5" />
</s:graphicImage>
make s:graphicImage work with s:cache
--------------------------------------
Key: JBSEAM-3033
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3033
Project: Seam
Issue Type: Feature Request
Components: JSF Controls, Performance and Scalability
Affects Versions: 2.0.2.GA, 2.1.0.GA
Environment: All
Reporter: Daniel Roth
Priority: Minor
Fix For: The future
Attachments: cache.patch
s:graphicImage with its transformations is a great tag to use for user uploaded images.
However, having a couple of images on the same page makes the page a bit slow to load due
to transformations. One can quite easy make the transformations oneself and cache them,
however a nicer solution would be if s:graphicImage could be used inside s:cache tags.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira