[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13713647#comment-13713647 ] Jos Snellings commented on COCOON3-126: --- True, so here is a solution that uses the injection in cocoon-sitemap. 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
[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: CachingXSLTTransformer.java The XLSTTransformer with internal LRU cache. 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: CachingXSLTTransformer.java, cocoon3-126.patch, cocoon-sax-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
[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: cocoon-sitemap-COCOON3-126-2.patch Changes to PrototypePipelineComponentFactory 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: CachingXSLTTransformer.java, cocoon3-126.patch, cocoon-sax-COCOON3-126.patch, cocoon-sitemap-COCOON3-126-1.patch, cocoon-sitemap-COCOON3-126-2.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
[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: cocoon-sitemap-COCOON3-126-1.patch 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: CachingXSLTTransformer.java, cocoon3-126.patch, cocoon-sax-COCOON3-126.patch, cocoon-sitemap-COCOON3-126-1.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
[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
[jira] [Closed] (COCOON3-103) Cannot pass map:parameter's to components inside of a map:select
[
https://issues.apache.org/jira/browse/COCOON3-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jos Snellings closed COCOON3-103.
-
Resolution: Not A Problem
Within nested blocks, sitemap parameters should be referred to by a relative
path
to the (ancestor) node in which they are declared.
It is just semantically not clear.
It is not a problem, but this should be documented. I had to look in the source
code to discover this.
Cannot pass map:parameter's to components inside of a map:select
-
Key: COCOON3-103
URL: https://issues.apache.org/jira/browse/COCOON3-103
Project: Cocoon 3
Issue Type: Bug
Components: cocoon-sitemap
Affects Versions: 3.0.0-beta-1
Reporter: Jos Snellings
Labels: clarification
Fix For: 3.0.0-beta-1
Following construct is in a sitemap match of:
map:match pattern=/staticstuff/{docid}/{nn}
map:select value={jexl:cocoon.request.method}
map:when equals=POST
map:transform type=tee
map:parameter name=nn value={map:nn}/
map:parameter name=Url value=repo:/{map:docid}/
/map:transform
map:transform type=edit
map:parameter name=nn value={map:nn}/
map:parameter name=element
value={jexl:cocoon.request.parameter.element}/
/map:transform
/map:when
map:otherwise/
/map:select
--
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] [Created] (COCOON3-106) Add cocoon site
Jos Snellings created COCOON3-106: - Summary: Add cocoon site Key: COCOON3-106 URL: https://issues.apache.org/jira/browse/COCOON3-106 Project: Cocoon 3 Issue Type: Wish Components: cocoon-sample-webapp Reporter: Jos Snellings Priority: Minor I'd like the site 'thesaurus on line Editor' for the European Heritage Network to the cocoon 3 production sites. -- 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-106) Add cocoon site
[ https://issues.apache.org/jira/browse/COCOON3-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jos Snellings updated COCOON3-106: -- Attachment: herein.patch just additional li Add cocoon site --- Key: COCOON3-106 URL: https://issues.apache.org/jira/browse/COCOON3-106 Project: Cocoon 3 Issue Type: Wish Components: cocoon-sample-webapp Reporter: Jos Snellings Priority: Minor Attachments: herein.patch I'd like the site 'thesaurus on line Editor' for the European Heritage Network to the cocoon 3 production sites. -- 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-106) Add cocoon site
[ https://issues.apache.org/jira/browse/COCOON3-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jos Snellings updated COCOON3-106: -- Attachment: herein.patch I am sorry, this must be a mistake ;-0 On Tue, Sep 25, 2012 at 4:36 PM, Francesco Chicchiriccò (JIRA) -- The doctrine of human equality reposes on this: that there is no man really clever who has not found that he is stupid. -- Gilbert K. Chesterson Add cocoon site --- Key: COCOON3-106 URL: https://issues.apache.org/jira/browse/COCOON3-106 Project: Cocoon 3 Issue Type: Wish Components: cocoon-sample-webapp Reporter: Jos Snellings Priority: Minor Attachments: herein.patch, herein.patch I'd like the site 'thesaurus on line Editor' for the European Heritage Network to the cocoon 3 production sites. -- 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] [Created] (COCOON3-103) Cannot pass map:parameter's to components inside of a map:select
Jos Snellings created COCOON3-103:
-
Summary: Cannot pass map:parameter's to components inside of a
map:select
Key: COCOON3-103
URL: https://issues.apache.org/jira/browse/COCOON3-103
Project: Cocoon 3
Issue Type: Bug
Components: cocoon-sitemap
Affects Versions: 3.0.0-beta-1
Reporter: Jos Snellings
Fix For: 3.0.0-beta-1
Following construct is in a sitemap match of:
map:match pattern=/staticstuff/{docid}/{nn}
map:select value={jexl:cocoon.request.method}
map:when equals=POST
map:transform type=tee
map:parameter name=nn value={map:nn}/
map:parameter name=Url value=repo:/{map:docid}/
/map:transform
map:transform type=edit
map:parameter name=nn value={map:nn}/
map:parameter name=element
value={jexl:cocoon.request.parameter.element}/
/map:transform
/map:when
map:otherwise/
/map:select
--
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] [Created] (COCOON3-99) Provide FopSerializer with an embedded user configuration present in the cocoon block
Jos Snellings created COCOON3-99: Summary: Provide FopSerializer with an embedded user configuration present in the cocoon block Key: COCOON3-99 URL: https://issues.apache.org/jira/browse/COCOON3-99 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-optional Affects Versions: 3.0.0-beta-1 Reporter: Jos Snellings Priority: Minor Fix For: 3.0.0-beta-1 The current FopSerializer creates an instance of FopFactory. Only the defaults are used. This is a problem if you want to generate PDFs from Unicode data. The Cyrillic and Greek characters have no glyphs in these fonts, causing those strings to be displayed as # sequences. This patch adds an override for the method setConfiguration to add a user configuration location via a sitemap parameter. In sitemap.xmap of the block, add the parameter userConfigurationPath indicating the location of the user configuration file. Example: map:match pattern=editor/publish/thesaurus.pdf map:generate type=publish/ map:transform src=presentation/xslt/thesaurusfo.xslt/ map:serialize type=flo2pdf map:parameter name=userConfigurationPath value=fopconf/fop.xconf/ /map:serialize /map:match -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COCOON3-99) Provide FopSerializer with an embedded user configuration present in the cocoon block
[ https://issues.apache.org/jira/browse/COCOON3-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jos Snellings updated COCOON3-99: - Attachment: patch-fopserializer.txt A patch for adding the user configuration to the fop serializer via a sitemap construct. Provide FopSerializer with an embedded user configuration present in the cocoon block - Key: COCOON3-99 URL: https://issues.apache.org/jira/browse/COCOON3-99 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-optional Affects Versions: 3.0.0-beta-1 Reporter: Jos Snellings Priority: Minor Fix For: 3.0.0-beta-1 Attachments: patch-fopserializer.txt The current FopSerializer creates an instance of FopFactory. Only the defaults are used. This is a problem if you want to generate PDFs from Unicode data. The Cyrillic and Greek characters have no glyphs in these fonts, causing those strings to be displayed as # sequences. This patch adds an override for the method setConfiguration to add a user configuration location via a sitemap parameter. In sitemap.xmap of the block, add the parameter userConfigurationPath indicating the location of the user configuration file. Example: map:match pattern=editor/publish/thesaurus.pdf map:generate type=publish/ map:transform src=presentation/xslt/thesaurusfo.xslt/ map:serialize type=flo2pdf map:parameter name=userConfigurationPath value=fopconf/fop.xconf/ /map:serialize /map:match -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (COCOON3-53) Cocoon 3: XMLSerializer caches all
[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842957#action_12842957 ] Jos Snellings commented on COCOON3-53: -- - No, I cannot say your test is wrong. The test clearly shows that the right response is returned from the cache - It must be somehow 'subtle' - Yesterday I looked into CachingPipeline and I found everything sound - Yet my test case on a browser stands. If you want I can describe it in detail == the next candidate to look at is simplecache. It is hard to imagine what can go wrong here, as it is based upon a map. The only thing I can imagine: - could it be that there is a situation where different cache keys map onto the same content? - my pipes have no jmxname. Can that be a problem? I think not. == the thing to do is probably: I try put a finger on the problem at my side and deliver a very specific test case, for I believe the problem is quite specific. I will keep this group posted. Cocoon 3: XMLSerializer caches all -- Key: COCOON3-53 URL: https://issues.apache.org/jira/browse/COCOON3-53 Project: Cocoon 3 Issue Type: Bug Components: cocoon-pipeline Reporter: Jos Snellings After startup, any pipeline/matcher ending in an xml-serializer will produce the output of the first request after server startup, regardless of the url, let alone parameters. So the first xml pipe that is activated produces the expected output. All subsequent calls will echo that output, whatever the url or parameters. It takes a server restart to make a pipeline ending in an xml serializer work again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-53) Cocoon 3: XMLSerializer caches all
[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842967#action_12842967 ] Jos Snellings commented on COCOON3-53: -- Cocoon 3, checked out from SVN on 5 march, and built with eclipse. Detail: three urls, activating a pipe ending with an xml serializer. (Note: all other pipes work correctly as far as I could verify) http://localhost:8080/thesaurus/hierarchies?language=el, result = the greek hierarchies in the thesaurus http://localhost:8080/thesaurus/showterm.xml?id=1004, visualize a term http://localhost:8080/thesaurus/editor/workspace.xml?random=23948783 Here is what happens: SETUP, manufacturing cacheKey: ~ adding SimpleCacheKey(hashCode=3116185) for component ToptermsGenerator(hashCode=21535750) ~ adding org.apache.cocoon.pipeline.caching.parametercache...@f91f7142 for component XMLSerializer(hashCode=10730286) Creating CompoundCacheKey(hashCode=22406408 key=[SimpleCacheKey(hashCode=3116185), org.apache.cocoon.pipeline.caching.parametercache...@f91f7142]) for pipeline CachingPipeline(hashCode=33258683 components=[ToptermsGenerator(hashCode=21535750), XMLSerializer(hashCode=10730286)]) SETTING CACHE: org.apache.cocoon.pipeline.caching.SimpleCache (CachingPipeline.setCache() called) SETUP, manufacturing cacheKey for 2nd: ~ adding SimpleCacheKey(hashCode=4540490) for component TermGenerator(hashCode=16199287) ~ adding org.apache.cocoon.pipeline.caching.parametercache...@f91f7142 for component XMLSerializer(hashCode=23533966) Creating CompoundCacheKey(hashCode=16471030 key=[SimpleCacheKey(hashCode=4540490), org.apache.cocoon.pipeline.caching.parametercache...@f91f7142]) for pipeline CachingPipeline(hashCode=772032 components=[TermGenerator(hashCode=16199287), XMLSerializer(hashCode=23533966)]) The value is FOUND in cache!!!, Here is the xml for: cacheValue.writeTo(System.out): JDB: CachingPipeline Write cache value to output stream: ?xml version=1.0 encoding=UTF-8?pagesearchform/classlistclass name=Ομάδα 1 - Οργανισμοί και Φορείςtop id=9001κυβέρνηση / διοίκηση/toptop id=9029οργανισμοί/toptop id=9056φορείς/top/classclass name=Ομάδα 2 - Κατηγορίες Πολιτιστικής Κληρονομιάςtop id=9085πολιτιστικό αγαθό/toptop id=9115περιοχές/toptop id=9149ενδιαφέρον πολιτιστικής κληρονομιάς/toptop id=9166κληρονομιά/top/classclass name=Ομάδα 3 - Συστήματα Αρχειοθέτησηςtop id=9194καταγραφή και τεκμηρίωση/toptop id=9215αρχεία καταγραφής/toptop id=9222κατάλογος προστατευόμενων αγαθών/top/classclass name=Ομάδα 4 - Νομικά συστήματαtop id=9225νομικά μέσα/toptop id=9250πολεοδομικό σύστημα/toptop id=9273διαχείριση κληρονομιάς/toptop id=9327ιδιοκτησία/toptop id=9355παράνομες ενέργειες/top/classclass name=Ομάδα 5 - Επεμβάσειςtop id=9362τύποι επεμβάσεων/toptop id=9413πολιτική επεμβάσεων/toptop id=9416προγράμματα επεμβάσεων/toptop id=9421εργαλεία επέμβασης/top/classclass name=Ομάδα 6 - Επαγγέλματα, δεξιότητες και αρμοδιότητεςtop id=9430επαγγέλματα/toptop id=9432δεξιότητες/toptop id=9437εκπαίδευση / επιμόρφωση/top/classclass name=Ομάδα 7 - Πρόσβαση και ερμηνείαtop id=9449πρόσβαση και ερμηνεία/top/classclass name=Ομάδα 8 - Χρηματο-οικονομικά συστήματαtop id=9491χρηματο-οικονομικά συστήματα/top/classclass name=Ομάδα 9 - Γενικές έννοιεςtop id=9521γενικές έννοιες/top/class/classlist/pageSETTING CACHE: org.apache.cocoon.pipeline.caching.SimpleCache Surprise! The Greek hierarchies! SETUP, now the call of workspace: ~ adding SimpleCacheKey(hashCode=30181678) for component WorkspaceProvider(hashCode=27011377) ~ adding org.apache.cocoon.pipeline.caching.parametercache...@f91f7142 for component XMLSerializer(hashCode=28014118) Creating CompoundCacheKey(hashCode=31048679 key=[SimpleCacheKey(hashCode=30181678), org.apache.cocoon.pipeline.caching.parametercache...@f91f7142]) for pipeline CachingPipeline(hashCode=22316052 components=[WorkspaceProvider(hashCode=27011377), XMLSerializer(hashCode=28014118)]) JDB: CachingPipeline Write cache value to output stream: ?xml version=1.0 encoding=UTF-8?pagesearchform/classlistclass name=Ομάδα 1 - Οργανισμοί και Φορείςtop id=9001κυβέρνηση / διοίκηση/toptop id=9029οργανισμοί/toptop id=9056φορείς/top/classclass name=Ομάδα 2 - Κατηγορίες Πολιτιστικής Κληρονομιάςtop id=9085πολιτιστικό αγαθό/toptop id=9115περιοχές/toptop id=9149ενδιαφέρον πολιτιστικής κληρονομιάς/toptop id=9166κληρονομιά/top/classclass name=Ομάδα 3 - Συστήματα Αρχειοθέτησηςtop id=9194καταγραφή και τεκμηρίωση/toptop id=9215αρχεία καταγραφής/toptop id=9222κατάλογος προστατευόμενων αγαθών/top/classclass name=Ομάδα 4 - Νομικά συστήματαtop id=9225νομικά μέσα/toptop id=9250πολεοδομικό σύστημα/toptop id=9273διαχείριση κληρονομιάς/toptop id=9327ιδιοκτησία/toptop id=9355παράνομες ενέργειες/top/classclass name=Ομάδα 5 - Επεμβάσειςtop id=9362τύποι επεμβάσεων/toptop id=9413πολιτική επεμβάσεων/toptop id=9416προγράμματα επεμβάσεων/toptop
[jira] Commented: (COCOON3-53) Cocoon 3: XMLSerializer caches all
[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843037#action_12843037 ] Jos Snellings commented on COCOON3-53: -- ParameterCacheKey, constructed with the request parameters effectively cures the problem. This issue is closed! Suggestion: Developers starting out with cocoon 3 are very much likely to leave the routine constructCacheKey() as they find it. It would be good to provide a lightly annotated example in the samples! I will post one. Cocoon 3: XMLSerializer caches all -- Key: COCOON3-53 URL: https://issues.apache.org/jira/browse/COCOON3-53 Project: Cocoon 3 Issue Type: Bug Components: cocoon-pipeline Reporter: Jos Snellings After startup, any pipeline/matcher ending in an xml-serializer will produce the output of the first request after server startup, regardless of the url, let alone parameters. So the first xml pipe that is activated produces the expected output. All subsequent calls will echo that output, whatever the url or parameters. It takes a server restart to make a pipeline ending in an xml serializer work again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-53) Cocoon 3: XMLSerializer caches all
[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jos Snellings closed COCOON3-53. Resolution: Fixed The observed problem was due to using a SimpleCacheKey. It remains a strange fact that this is only observed when the end point is an XMLSerializer. Cocoon 3: XMLSerializer caches all -- Key: COCOON3-53 URL: https://issues.apache.org/jira/browse/COCOON3-53 Project: Cocoon 3 Issue Type: Bug Components: cocoon-pipeline Reporter: Jos Snellings After startup, any pipeline/matcher ending in an xml-serializer will produce the output of the first request after server startup, regardless of the url, let alone parameters. So the first xml pipe that is activated produces the expected output. All subsequent calls will echo that output, whatever the url or parameters. It takes a server restart to make a pipeline ending in an xml serializer work again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-53) Cocoon 3: XMLSerializer caches all
[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842997#action_12842997 ] Jos Snellings commented on COCOON3-53: -- Yes, I thought about that, SimpleCacheKey is all too Simple. I kept it mainly because it was in the samples: it is not expected that a generator produces the same result. but why do pipelines with the same Starters (Termgenerator or WorkspaceProvider) are perfectly OK with the cache when they end in html serialization? Anyway, I will use a parameter cache and verify the cache behaviour is correct. If it does, I close this issue. Cocoon 3: XMLSerializer caches all -- Key: COCOON3-53 URL: https://issues.apache.org/jira/browse/COCOON3-53 Project: Cocoon 3 Issue Type: Bug Components: cocoon-pipeline Reporter: Jos Snellings After startup, any pipeline/matcher ending in an xml-serializer will produce the output of the first request after server startup, regardless of the url, let alone parameters. So the first xml pipe that is activated produces the expected output. All subsequent calls will echo that output, whatever the url or parameters. It takes a server restart to make a pipeline ending in an xml serializer work again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-53) Cocoon 3: XMLSerializer caches all
[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842613#action_12842613 ] Jos Snellings commented on COCOON3-53: -- This is only true for CachingPipeline! AsyncCachingPipeline is not affected. Cocoon 3: XMLSerializer caches all -- Key: COCOON3-53 URL: https://issues.apache.org/jira/browse/COCOON3-53 Project: Cocoon 3 Issue Type: Bug Components: cocoon-pipeline Reporter: Jos Snellings After startup, any pipeline/matcher ending in an xml-serializer will produce the output of the first request after server startup, regardless of the url, let alone parameters. So the first xml pipe that is activated produces the expected output. All subsequent calls will echo that output, whatever the url or parameters. It takes a server restart to make a pipeline ending in an xml serializer work again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COCOON-2287) Cocoon 3: XMLSerializer caches all
Cocoon 3: XMLSerializer caches all -- Key: COCOON-2287 URL: https://issues.apache.org/jira/browse/COCOON-2287 Project: Cocoon Issue Type: Bug Components: * Cocoon Core Reporter: Jos Snellings After startup, any pipeline/matcher ending in an xml-serializer will produce the output of the first request after server startup, regardless of the url, let alone parameters. So the first xml pipe that is activated produces the expected output. All subsequent calls will echo that output, whatever the url or parameters. It takes a server restart to make a pipeline ending in an xml serializer work again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-46) URLConnectionUtils.closeQuietly() complains loudly if servletConnection == null
[ https://issues.apache.org/jira/browse/COCOON3-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jos Snellings updated COCOON3-46: - Attachment: closeQuietly-fix.patch URLConnectionUtils.closeQuietly() complains loudly if servletConnection == null --- Key: COCOON3-46 URL: https://issues.apache.org/jira/browse/COCOON3-46 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-pipeline Affects Versions: 3.0.0-alpha-2 Reporter: Jos Snellings Assignee: Cocoon Developers Team Priority: Minor Fix For: 3.0.0-alpha-3 Attachments: closeQuietly-fix.patch finally clause in URLResponse method execute() contains call to URLConnectionUtils.closeQuietly. If servletConnection = this.url.openConnection(); fails, servletConnection is null. In that case closeQuietly causes a stacktrace to be output. Solution is if (servletConnection != null) URLConnectionUtils.closeQuietly(servletConnection);, guard the call with a test, or even better, take into account in closeQuietly that the input parameter may be null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COCOON3-46) URLConnectionUtils.closeQuietly() complains loudly if servletConnection == null
URLConnectionUtils.closeQuietly() complains loudly if servletConnection == null --- Key: COCOON3-46 URL: https://issues.apache.org/jira/browse/COCOON3-46 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-pipeline Affects Versions: 3.0.0-alpha-2 Reporter: Jos Snellings Assignee: Cocoon Developers Team Priority: Minor Fix For: 3.0.0-alpha-3 finally clause in URLResponse method execute() contains call to URLConnectionUtils.closeQuietly. If servletConnection = this.url.openConnection(); fails, servletConnection is null. In that case closeQuietly causes a stacktrace to be output. Solution is if (servletConnection != null) URLConnectionUtils.closeQuietly(servletConnection);, guard the call with a test, or even better, take into account in closeQuietly that the input parameter may be null. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
