Your Gump Build(s)
Dear Community Apache Gump builds some of your projects and it is quite possible you don't know or have by now forgotten about it. More than half a year ago a technical problem has forced us to turn off emails on build failures as we would have been sending out lots of false alarms. Before we re-enable emails we'd like to know whether you are still interested in the service Gump provides, so please tell us. :-) Metadata for many projects have been neglected for a long time and it is quite possible they'd need some love for results to be meaningful. All Apache committers have write access to Gump's metadata. In case you don't know what this Gump stuff is about: Apache Gump builds the full stack of the latest commits of software in order to ensure integrity over releases. Build failures surface API discontinuities between projects before they impact releases, and Gump's e-mail notifications hope to promote the conversations between teams to resolve those discontinuities. When responding to this mail please shorten the CC list as appropriate. Cheers Stefan on behalf of the Gump PMC
[jira] [Created] (COCOON3-126) Make configurable whether xslt transformer component uses LRU cache or not
Jos Snellings created COCOON3-126: - Summary: Make configurable whether xslt transformer component uses LRU cache or not Key: COCOON3-126 URL: https://issues.apache.org/jira/browse/COCOON3-126 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Affects Versions: 3.0.0-beta-1 Reporter: Jos Snellings Priority: Minor Fix For: 3.0.0-beta-1 The XSLT pipeline component should be aware of the following setting in configurator:settings configurator:property name=org.apache.cocoon.sax.lrucache-enabled value=true|false|True|False/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COCOON3-126) Make configurable whether xslt transformer component uses LRU cache or not
[ https://issues.apache.org/jira/browse/COCOON3-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jos Snellings updated COCOON3-126: -- Attachment: cocoon3-126.patch Patch solving the issue from xslt transformer alone. Not too happy with it: Should it not be chosen in cocoon-sitemap if an lru cache is to be used? Leave it up to you. Make configurable whether xslt transformer component uses LRU cache or not -- Key: COCOON3-126 URL: https://issues.apache.org/jira/browse/COCOON3-126 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Affects Versions: 3.0.0-beta-1 Reporter: Jos Snellings Priority: Minor Fix For: 3.0.0-beta-1 Attachments: cocoon3-126.patch The XSLT pipeline component should be aware of the following setting in configurator:settings configurator:property name=org.apache.cocoon.sax.lrucache-enabled value=true|false|True|False/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Use LRU cache
Hi, Just reported the issue and proposed a patch, though I am not very happy with it. + : it intervenes only in cocoon-sax - : it introduces a new dependency (on spring). Question: would it be better to decide in cocoon-sitemap if an LRU cache is used? The constructor would have an extra parameter then. the template is loaded (or not) in the constructor, which is a bit early. What do you think? Cheers, Jos -- We should be careful to get out of an experience only the wisdom that is in it - and stay there, lest we be like the cat that sits down on a hot stove-lid. She will never sit down on a hot stove-lid again - and that is well; but also she will never sit down on a cold one any more. -- Mark Twain http://www.brainyquote.com/quotes/quotes/t/thomashobb118630.html
