[jira] [Closed] (COCOON-2359) [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8
[ https://issues.apache.org/jira/browse/COCOON-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli closed COCOON-2359. -- Resolution: Fixed so be it :) > [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8 > > > Key: COCOON-2359 > URL: https://issues.apache.org/jira/browse/COCOON-2359 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Captcha >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Priority: Major > Fix For: 2.3.0 > > > Goal is to remove the direct usage of > - JPEGImageEncoder > - JPEGEncodeParam > inside CaptchaReader.java > And replace them with the newer 1.6 API of ImageIO > https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2359) [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8
[ https://issues.apache.org/jira/browse/COCOON-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli updated COCOON-2359: --- Fix Version/s: 2.3.0 (was: 2.3.1) > [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8 > > > Key: COCOON-2359 > URL: https://issues.apache.org/jira/browse/COCOON-2359 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Captcha >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Priority: Major > Fix For: 2.3.0 > > > Goal is to remove the direct usage of > - JPEGImageEncoder > - JPEGEncodeParam > inside CaptchaReader.java > And replace them with the newer 1.6 API of ImageIO > https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (COCOON-2359) [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8
[ https://issues.apache.org/jira/browse/COCOON-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791653#comment-17791653 ] Christofer Dutz commented on COCOON-2359: - Yeah ... I actually replaced all usages of JPEG types with ImageIO types ;-) > [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8 > > > Key: COCOON-2359 > URL: https://issues.apache.org/jira/browse/COCOON-2359 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Captcha >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Priority: Major > Fix For: 2.3.1 > > > Goal is to remove the direct usage of > - JPEGImageEncoder > - JPEGEncodeParam > inside CaptchaReader.java > And replace them with the newer 1.6 API of ImageIO > https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2227) Creation of child settings object is broken
[ https://issues.apache.org/jira/browse/COCOON-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli updated COCOON-2227: --- Fix Version/s: 2.3.1 (was: 2.3.0) > Creation of child settings object is broken > --- > > Key: COCOON-2227 > URL: https://issues.apache.org/jira/browse/COCOON-2227 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core >Affects Versions: 2.3.0 >Reporter: Grzegorz Kossakowski >Priority: Major > Fix For: 2.3.1 > > > It seems that there is a problem with creation of child settings object. To > reproduce this problem just go to: > core/cocoon-webapp > and then run Cocoon using following command: > mvn jetty:run -Dorg.apache.cocoon.formencoding=UTF-8 > Then access: > http://localhost:/ > and you will get following exception: > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'org.apache.cocoon.configuration.Settings': Invocation of init > method failed; nested exception is java.lang.IllegalStateException: This > value can only be changed for the root settings object. > [...] > Caused by: java.lang.IllegalStateException: This value can only be changed > for the root settings object. > at > org.apache.cocoon.configuration.MutableSettings.checkSubSetting(MutableSettings.java:423) > at > org.apache.cocoon.configuration.MutableSettings.setFormEncoding(MutableSettings.java:364) > at > org.apache.cocoon.configuration.MutableSettings.configure(MutableSettings.java:151) > at > org.apache.cocoon.spring.configurator.impl.AbstractSettingsBeanFactoryPostProcessor.createSettings(AbstractSettingsBeanFactoryPostProcessor.java:258) > at > org.apache.cocoon.spring.configurator.impl.AbstractSettingsBeanFactoryPostProcessor.init(AbstractSettingsBeanFactoryPostProcessor.java:130) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2212) jx:attribute does not check name is correct before proceeding
[ https://issues.apache.org/jira/browse/COCOON-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli updated COCOON-2212: --- Fix Version/s: 2.3.1 (was: 2.3.0) > jx:attribute does not check name is correct before proceeding > - > > Key: COCOON-2212 > URL: https://issues.apache.org/jira/browse/COCOON-2212 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: Templating >Affects Versions: 2.1.12, 2.2, 2.3.0 >Reporter: Kamal Bhatt >Priority: Major > Fix For: 2.3.1 > > Attachments: JXtemplateAttributePatch > > > Currently, jx:attribute does not validate that the name is correct before > generating attribute. This patch fixes this. > Also, refactored the JXTemplateGeneratorTestCase -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2276) New Maven Repository Upload Request
[ https://issues.apache.org/jira/browse/COCOON-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli updated COCOON-2276: --- Fix Version/s: 2.3.1 (was: 2.3.0) > New Maven Repository Upload Request > --- > > Key: COCOON-2276 > URL: https://issues.apache.org/jira/browse/COCOON-2276 > Project: Cocoon > Issue Type: Wish > Components: * Cocoon Core >Affects Versions: 2.3.0 >Reporter: Don Corley >Priority: Trivial > Fix For: 2.3.1 > > > It would be nice to have a new release to the central maven repository of > version 2.x. > Some of the code in the repository is rather old and contains some bugs > (which have been fixed) in the current development tree. > Cocoon is a great product which saves me a ton of time... Thanks! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2108) xmodule:flow-attr Does not accept document objects
[ https://issues.apache.org/jira/browse/COCOON-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli updated COCOON-2108: --- Fix Version/s: 2.3.1 (was: 2.3.0) > xmodule:flow-attr Does not accept document objects > -- > > Key: COCOON-2108 > URL: https://issues.apache.org/jira/browse/COCOON-2108 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core >Affects Versions: 2.1.11, 2.2 >Reporter: Hugh Sparks >Priority: Minor > Fix For: 2.3.1 > > Attachments: Cocoon-2.2-truck-JXPathHelper.java.patch, > Cocoon-BRANCH-2.1.X-JXPathHelper.java.patch, xmodulePuzzle.txt > > > Sending document objects from flowscript back to the pipeline using > xmodule:flow-attr produces unexpected results. Also, the examples from > the documentation do not work as described: > http://cocoon.apache.org/2.1/861.daisy.html > The most common error reported is: > 'The object type: class java.lang.String could not be serialized to XML" > This issue was discussed recently on the cocoon-users mailing list. > The thread was introduced by Kazo Csaba with the subject "Sending DOM from > flowscript to pipeline." > (July 17, 2007) > He has attempted to trace this behavior in the source code and believes that a > possibly-inappropriate conversion to string occurs in some cases. > Jason Johnston suggested moving the issue to JIRA. > I've created a demonstration of this apparent bug and some related problems > in this very brief example: > http://www.csparks.com/xmodulePuzzle.txt > I hope someone can fix or explain the correct usage of xmodule:flow-attr. > Thanks to all, > -Hugh Sparks, h...@csparks.com -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2197) Making the cocoon-auth-block acegi-security-sample work
[ https://issues.apache.org/jira/browse/COCOON-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli updated COCOON-2197: --- Fix Version/s: 2.3.1 (was: 2.3.0) > Making the cocoon-auth-block acegi-security-sample work > --- > > Key: COCOON-2197 > URL: https://issues.apache.org/jira/browse/COCOON-2197 > Project: Cocoon > Issue Type: Wish > Components: - Samples >Affects Versions: 2.2 >Reporter: Patrick Heiden >Assignee: Grzegorz Kossakowski >Priority: Minor > Fix For: 2.3.1 > > Attachments: cocoon-acegi-sample-svn-diff.patch > > > The current acegi-security-sample doesn't work with acegi version used! > So an update to spring-security (2.0.0-SNAPSHOT) fixed that problem. > Following steps need to be performed: > 1) get the latest trunk from spring-security (acegi) (see [1] for details) > 2) compile and install that trunk (mvn install, maybe skip the more than 1000 > tests ;) > 3) change the pom.xml of cocoon-acegisecurity-sample block: >replace the acegi dependency with: > > org.springframework.security > spring-security-core > 2.0.0-SNAPSHOT > > > avalon-framework > avalon-framework > > > > 4) replacements in META-INF/cocoon/xpatch/acegi-filter-patch.xweb: >every org.acegi. ... should be replaced by org.springframework.security > 5) the same needs to be done for all bean's class attribute inside > META-INF/cocoon/spring/cocoon-acegisecurity.xml > 6) mvn install; mvn jetty:run > I would guess, that by making acegi a spring portfolio project, the rework on > that project > contains better adoption of spring bean-lifecycles. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2359) [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8
[ https://issues.apache.org/jira/browse/COCOON-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli updated COCOON-2359: --- Fix Version/s: 2.3.1 (was: 2.3.0) > [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8 > > > Key: COCOON-2359 > URL: https://issues.apache.org/jira/browse/COCOON-2359 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Captcha >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Priority: Major > Fix For: 2.3.1 > > > Goal is to remove the direct usage of > - JPEGImageEncoder > - JPEGEncodeParam > inside CaptchaReader.java > And replace them with the newer 1.6 API of ImageIO > https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2304) ThreadLocal in Rhino context is not always cleared
[
https://issues.apache.org/jira/browse/COCOON-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cédric Damioli updated COCOON-2304:
---
Fix Version/s: 2.3.1
(was: 2.3.0)
> ThreadLocal in Rhino context is not always cleared
> --
>
> Key: COCOON-2304
> URL: https://issues.apache.org/jira/browse/COCOON-2304
> Project: Cocoon
> Issue Type: Bug
> Components: - Flowscript
>Reporter: Graham Triggs
>Priority: Major
> Fix For: 2.3.1
>
> Attachments: flowscript.diff
>
>
> The Mozilla Rhino Context isn't exited in all cases in
> FOM_JavascriptInterpreter. This can lead to a leak on application
> undeployment, with the ThreadLocal references inside.
> Patch restructures the code slightly to use try { } finally { } blocks to
> ensure the Context.exit() is called where appropriate (this makes the patch
> look bigger than it really is, due to indenting).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (COCOON-2372) Release Cocoon 2.3.0
[ https://issues.apache.org/jira/browse/COCOON-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli closed COCOON-2372. -- Resolution: Fixed > Release Cocoon 2.3.0 > > > Key: COCOON-2372 > URL: https://issues.apache.org/jira/browse/COCOON-2372 > Project: Cocoon > Issue Type: Task > Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, > Blocks: ImageOp, Blocks: XSP >Affects Versions: 2.2 >Reporter: Javier Puerto >Priority: Major > Fix For: 2.3.0 > > > Maintenance release for Java 8 compatibility improvements. > * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java > image API. > * Update DataSource implementations (only wrappers) to implement the method > [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()] > introduced in Java 1.7. > * Update XSP block with newer Eclipe JDK compiler to support Java 8. > Furthermore, the following issues will be addressed: > * Fix test cases for JCR block by excluding a SLF4J dependency that was not > working with our current Spring version. > * Other bugfixes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2372) Release Cocoon 2.3.0
[ https://issues.apache.org/jira/browse/COCOON-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli updated COCOON-2372: --- Summary: Release Cocoon 2.3.0 (was: Release Cocoon 2.2.1) > Release Cocoon 2.3.0 > > > Key: COCOON-2372 > URL: https://issues.apache.org/jira/browse/COCOON-2372 > Project: Cocoon > Issue Type: Task > Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, > Blocks: ImageOp, Blocks: XSP >Affects Versions: 2.2 >Reporter: Javier Puerto >Priority: Major > Fix For: 2.3.0 > > > Maintenance release for Java 8 compatibility improvements. > * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java > image API. > * Update DataSource implementations (only wrappers) to implement the method > [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()] > introduced in Java 1.7. > * Update XSP block with newer Eclipe JDK compiler to support Java 8. > Furthermore, the following issues will be addressed: > * Fix test cases for JCR block by excluding a SLF4J dependency that was not > working with our current Spring version. > * Other bugfixes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2372) Release Cocoon 2.2.1
[ https://issues.apache.org/jira/browse/COCOON-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Javier Puerto updated COCOON-2372: -- Status: Continued (was: Blocked) > Release Cocoon 2.2.1 > > > Key: COCOON-2372 > URL: https://issues.apache.org/jira/browse/COCOON-2372 > Project: Cocoon > Issue Type: Task > Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, > Blocks: ImageOp, Blocks: XSP >Affects Versions: 2.2 >Reporter: Javier Puerto >Priority: Major > Fix For: 2.2.1 > > > Maintenance release for Java 8 compatibility improvements. > * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java > image API. > * Update DataSource implementations (only wrappers) to implement the method > [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()] > introduced in Java 1.7. > * Update XSP block with newer Eclipe JDK compiler to support Java 8. > Furthermore, the following issues will be addressed: > * Fix test cases for JCR block by excluding a SLF4J dependency that was not > working with our current Spring version. > * Other bugfixes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2372) Release Cocoon 2.2.1
[ https://issues.apache.org/jira/browse/COCOON-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Javier Puerto updated COCOON-2372: -- Status: Blocked (was: Open) > Release Cocoon 2.2.1 > > > Key: COCOON-2372 > URL: https://issues.apache.org/jira/browse/COCOON-2372 > Project: Cocoon > Issue Type: Task > Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, > Blocks: ImageOp, Blocks: XSP >Affects Versions: 2.2 >Reporter: Javier Puerto >Priority: Major > Fix For: 2.2.1 > > > Maintenance release for Java 8 compatibility improvements. > * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java > image API. > * Update DataSource implementations (only wrappers) to implement the method > [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()] > introduced in Java 1.7. > * Update XSP block with newer Eclipe JDK compiler to support Java 8. > Furthermore, the following issues will be addressed: > * Fix test cases for JCR block by excluding a SLF4J dependency that was not > working with our current Spring version. > * Other bugfixes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2372) Release Cocoon 2.2.1
[ https://issues.apache.org/jira/browse/COCOON-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Javier Puerto updated COCOON-2372: -- Description: Maintenance release for Java 8 compatibility improvements. * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java image API. * Update DataSource implementations (only wrappers) to implement the method [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()] introduced in Java 1.7. * Update XSP block with newer Eclipe JDK compiler to support Java 8. Furthermore, the following issues will be addressed: * Fix test cases for JCR block by excluding a SLF4J dependency that was not working with our current Spring version. * Other bugfixes. was: Maintenance release for Java 8 compatibility improvements. * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java image API. * Update DataSource implementations (only wrappers) to implement the method [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()] introduced in Java 1.7. * Update XSP block with newer Eclipe JDK compiler to support Java 8. Furthermore, the following issues will be addressed: * Fix test cases for JCR block by excluding a SLF4J dependency that was not working with our current Spring version. * Other bugfixes. * Exclude conflicting dependency from JCR block incompatible with o > Release Cocoon 2.2.1 > > > Key: COCOON-2372 > URL: https://issues.apache.org/jira/browse/COCOON-2372 > Project: Cocoon > Issue Type: Task > Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, > Blocks: ImageOp, Blocks: XSP >Affects Versions: 2.2 >Reporter: Javier Puerto >Priority: Major > Fix For: 2.2.1 > > > Maintenance release for Java 8 compatibility improvements. > * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java > image API. > * Update DataSource implementations (only wrappers) to implement the method > [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()] > introduced in Java 1.7. > * Update XSP block with newer Eclipe JDK compiler to support Java 8. > Furthermore, the following issues will be addressed: > * Fix test cases for JCR block by excluding a SLF4J dependency that was not > working with our current Spring version. > * Other bugfixes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2372) Release Cocoon 2.2.1
[ https://issues.apache.org/jira/browse/COCOON-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Javier Puerto updated COCOON-2372: -- Description: Maintenance release for Java 8 compatibility improvements. * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java image API. * Update DataSource implementations (only wrappers) to implement the method [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()] introduced in Java 1.7. * Update XSP block with newer Eclipe JDK compiler to support Java 8. Furthermore, the following issues will be addressed: * Fix test cases for JCR block by excluding a SLF4J dependency that was not working with our current Spring version. * Other bugfixes. * Exclude conflicting dependency from JCR block incompatible with o was: Maintenance release for Java 8 compatibility improvements. * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java image API. * Update DataSource implementations (only wrappers) to implement the method [getParentLogger()|https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()] introduced in Java 1.7. * Update XSP block with newer Eclipe JDK compiler to support Java 8. Furthermore, the following issues will be addressed: * Fix test cases for JCR block by excluding a SLF4J dependency that was not working with our current Spring version. * Other bugfixes. * Exclude conflicting dependency from JCR block incompatible with o > Release Cocoon 2.2.1 > > > Key: COCOON-2372 > URL: https://issues.apache.org/jira/browse/COCOON-2372 > Project: Cocoon > Issue Type: Task > Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, > Blocks: ImageOp, Blocks: XSP >Affects Versions: 2.2 >Reporter: Javier Puerto >Priority: Major > Fix For: 2.2.1 > > > Maintenance release for Java 8 compatibility improvements. > * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java > image API. > * Update DataSource implementations (only wrappers) to implement the method > [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()] > introduced in Java 1.7. > * Update XSP block with newer Eclipe JDK compiler to support Java 8. > Furthermore, the following issues will be addressed: > * Fix test cases for JCR block by excluding a SLF4J dependency that was not > working with our current Spring version. > * Other bugfixes. > * Exclude conflicting dependency from JCR block incompatible with o -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (COCOON-2372) Release Cocoon 2.2.1
Javier Puerto created COCOON-2372: - Summary: Release Cocoon 2.2.1 Key: COCOON-2372 URL: https://issues.apache.org/jira/browse/COCOON-2372 Project: Cocoon Issue Type: Task Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, Blocks: ImageOp, Blocks: XSP Affects Versions: 2.2 Reporter: Javier Puerto Fix For: 2.2.1 Maintenance release for Java 8 compatibility improvements. * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java image API. * Update DataSource implementations (only wrappers) to implement the method [getParentLogger()|https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()] introduced in Java 1.7. * Update XSP block with newer Eclipe JDK compiler to support Java 8. Furthermore, the following issues will be addressed: * Fix test cases for JCR block by excluding a SLF4J dependency that was not working with our current Spring version. * Other bugfixes. * Exclude conflicting dependency from JCR block incompatible with o -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (COCOON-2371) Allow stack traces in default error pages to be disabled
[ https://issues.apache.org/jira/browse/COCOON-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Schultz updated COCOON-2371: Other Info: Patch available > Allow stack traces in default error pages to be disabled > > > Key: COCOON-2371 > URL: https://issues.apache.org/jira/browse/COCOON-2371 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core >Affects Versions: 2.1.13 >Reporter: Christopher Schultz >Priority: Minor > Attachments: COCOON-2371.diff > > > If you want to disable stack traces in Cocoon, you have to completely replace > the default error pages. It should be configurable to disable stack traces on > the default error pages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (COCOON-2371) Allow stack traces in default error pages to be disabled
[ https://issues.apache.org/jira/browse/COCOON-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17514144#comment-17514144 ] Christopher Schultz commented on COCOON-2371: - This patch adds two optional parameters to exception2html.xslt: stack-traces and java-stack-traces. They are expected to be strings representing boolean flags and both default to 'true'. Setting java-stack-traces to anything other than 'true' will cause the Java stack trace to be suppressed from the default error page. Setting stack-traces to anything other than 'true' will cause both the Cocoon "stack trace" (the config-file traces and XSLTs) and the Java stack traces to be suppressed. > Allow stack traces in default error pages to be disabled > > > Key: COCOON-2371 > URL: https://issues.apache.org/jira/browse/COCOON-2371 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core >Affects Versions: 2.1.13 >Reporter: Christopher Schultz >Priority: Minor > Attachments: COCOON-2371.diff > > > If you want to disable stack traces in Cocoon, you have to completely replace > the default error pages. It should be configurable to disable stack traces on > the default error pages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (COCOON-2371) Allow stack traces in default error pages to be disabled
[ https://issues.apache.org/jira/browse/COCOON-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Schultz updated COCOON-2371: Attachment: COCOON-2371.diff > Allow stack traces in default error pages to be disabled > > > Key: COCOON-2371 > URL: https://issues.apache.org/jira/browse/COCOON-2371 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core >Affects Versions: 2.1.13 >Reporter: Christopher Schultz >Priority: Minor > Attachments: COCOON-2371.diff > > > If you want to disable stack traces in Cocoon, you have to completely replace > the default error pages. It should be configurable to disable stack traces on > the default error pages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (COCOON-2371) Allow stack traces in default error pages to be disabled
Christopher Schultz created COCOON-2371: --- Summary: Allow stack traces in default error pages to be disabled Key: COCOON-2371 URL: https://issues.apache.org/jira/browse/COCOON-2371 Project: Cocoon Issue Type: Improvement Components: * Cocoon Core Affects Versions: 2.1.13 Reporter: Christopher Schultz If you want to disable stack traces in Cocoon, you have to completely replace the default error pages. It should be configurable to disable stack traces on the default error pages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (COCOON-2298) IncludeTransformer does not handle multi-valued parameters
[ https://issues.apache.org/jira/browse/COCOON-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nico Verwer updated COCOON-2298: Affects Version/s: 2.1.13 > IncludeTransformer does not handle multi-valued parameters > -- > > Key: COCOON-2298 > URL: https://issues.apache.org/jira/browse/COCOON-2298 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core >Affects Versions: 2.1.11, 2.1.13 >Reporter: Nico Verwer >Priority: Major > Attachments: IncludeTransformer.patch > > > When you pass multivalued parameters to > org.apache.cocoon.transformation.IncludeTransformer, like: > > > only the last gets passed in the request made by IncludeTransformer. This is > because parameters are stored in a Map. > HTTP specifies that multi-valued parameters are possible, or rather it does > not forbid them. So the query-string "?foo=bar=baz" is perfectly legal. > The patch changes the way IncludeTransformer handles this case, so that > multi-valued parameters are handled correctly. The NetUtils.parameterize() > method, used by IncludeTransformer, was already prepared for this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (COCOON-2297) Character encoding does not follow JTidy properties
[ https://issues.apache.org/jira/browse/COCOON-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nico Verwer updated COCOON-2297: Affects Version/s: 2.1.13 > Character encoding does not follow JTidy properties > --- > > Key: COCOON-2297 > URL: https://issues.apache.org/jira/browse/COCOON-2297 > Project: Cocoon > Issue Type: Bug > Components: Blocks: HTML >Affects Versions: 2.1.11, 2.1.13 >Reporter: Nico Verwer >Priority: Major > Attachments: HTMLTransformer.patch > > > The text that HTMLTransformer sends to JTidy is always encoded according tot > the platform default encoding, by calling text.getBytes() without an encoding > parameter. JTidy does not follow the platform default encoding, but has its > own default. It is possible to change JTidy's input encoding in the > properties file. > The patch uses the encoding specified by JTidy's configuration. > The result is that HTMLTransformer handles UTF-8 or other encodings > correctly, so you don't get Chinese characters where you expected a > diacritical mark. > While I was changing the code, I also changed the logging settings. They now > take the settings in the JTidy configuration into account. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (COCOON-2370) Download page gpg example needs second parameter
Sebb created COCOON-2370: Summary: Download page gpg example needs second parameter Key: COCOON-2370 URL: https://issues.apache.org/jira/browse/COCOON-2370 Project: Cocoon Issue Type: Bug Components: * Cocoon Core Reporter: Sebb It is important that the file being checked is also specified [1] on the gpg command line [2] If the second paramater is omitted, gpg can report success without actually checking the main artifact. This should not happen on correctly constructed ASF downloads, as we only provide detached sigs, but we should not be documenting bad practise. [1] https://www.apache.org/info/verification.html#specify_both [2] http://cocoon.apache.org/mirror.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COCOON-2369) Flowscript should work with latest rhino
[ https://issues.apache.org/jira/browse/COCOON-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17160468#comment-17160468 ] Gabriel Gruber commented on COCOON-2369: Changed the necessary bits in cocoon-flowscript-impl to be compatible with rhino 1.7R5 https://github.com/ggruber4711/cocoon/tree/COCOON-2369_UpgradeRhino > Flowscript should work with latest rhino > > > Key: COCOON-2369 > URL: https://issues.apache.org/jira/browse/COCOON-2369 > Project: Cocoon > Issue Type: Bug > Components: - Flowscript >Reporter: Gabriel Gruber >Priority: Major > > Cocoon flowscript depends on a special version of rhino, which includes > support for continuations. > The last compatible version of rhino which works with flowscript interpreter > is 1.7R1. After that some breaking changes were done in the rhino project: > - rename Continutation to NativeContinuation > - move NativeContinuation to root package. > Goal of this ticket is to make cocoon-flow-impl work with the newest rhino > version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (COCOON-2291) StoreJanitor cannot work with more than ~2 gb memory
[ https://issues.apache.org/jira/browse/COCOON-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Gruber updated COCOON-2291: --- Comment: was deleted (was: Added a branch on my fork which does the work: https://github.com/ggruber4711/cocoon/tree/COCOON-2369_UpgradeRhino) > StoreJanitor cannot work with more than ~2 gb memory > > > Key: COCOON-2291 > URL: https://issues.apache.org/jira/browse/COCOON-2291 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core >Reporter: Krzysztof Kowalczyk >Priority: Blocker > > StoreJanitor uses int for values of freememory, heapsize etc. So StoreJanitor > cannot be used in environment with jvm heap bigger than 2,147,483,647 bytes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COCOON-2291) StoreJanitor cannot work with more than ~2 gb memory
[ https://issues.apache.org/jira/browse/COCOON-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17160467#comment-17160467 ] Gabriel Gruber commented on COCOON-2291: Added a branch on my fork which does the work: https://github.com/ggruber4711/cocoon/tree/COCOON-2369_UpgradeRhino > StoreJanitor cannot work with more than ~2 gb memory > > > Key: COCOON-2291 > URL: https://issues.apache.org/jira/browse/COCOON-2291 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core >Reporter: Krzysztof Kowalczyk >Priority: Blocker > > StoreJanitor uses int for values of freememory, heapsize etc. So StoreJanitor > cannot be used in environment with jvm heap bigger than 2,147,483,647 bytes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (COCOON-2333) C-2.1: upgrade some supporting product dependencies
[ https://issues.apache.org/jira/browse/COCOON-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli closed COCOON-2333. -- Resolution: Fixed Closing for now, for preparing 2.1.13 If other upgrades have to be done, open a new ticket. > C-2.1: upgrade some supporting product dependencies > --- > > Key: COCOON-2333 > URL: https://issues.apache.org/jira/browse/COCOON-2333 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core >Affects Versions: 2.1.12 >Reporter: David Crossley >Priority: Major > Fix For: 2.1.13 > > > It would be a good opportunity to upgrade some of the supporting product > dependencies. > This ticket can note which ones are necessary or worthwhile to be updated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (COCOON-2369) Flowscript should work with latest rhino
Gabriel Gruber created COCOON-2369: -- Summary: Flowscript should work with latest rhino Key: COCOON-2369 URL: https://issues.apache.org/jira/browse/COCOON-2369 Project: Cocoon Issue Type: Bug Components: - Flowscript Reporter: Gabriel Gruber Cocoon flowscript depends on a special version of rhino, which includes support for continuations. The last compatible version of rhino which works with flowscript interpreter is 1.7R1. After that some breaking changes were done in the rhino project: - rename Continutation to NativeContinuation - move NativeContinuation to root package. Goal of this ticket is to make cocoon-flow-impl work with the newest rhino version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COCOON-2368) Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12
[ https://issues.apache.org/jira/browse/COCOON-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970448#comment-16970448 ] Torsten Curdt commented on COCOON-2368: --- You are thinking way too high level. mitmproxy, fiddler, charles proxy or even wireshark/tcpdump/tcpflow allow you to record http request response flows. You want to see the http headers of all communications - and then compare the two scenarios. > Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12 > -- > > Key: COCOON-2368 > URL: https://issues.apache.org/jira/browse/COCOON-2368 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core, Blocks: (Undefined) >Affects Versions: 2.1.12 >Reporter: Modou Dia >Priority: Major > > Hello, > I try to load a MP4 File with a Cocoon Reader. It works well in all major > browsers except Safari (desktop and IOS). > Referring to this thread : > https://stackoverflow.com/questions/30199261/why-wont-safari-play-file-without-extension-in-video/51901198#51901198, > I overloaded the default Reader' by forcing cocoon to add a Byte Range > header (and 206 status code) ... It still does not work. > For being sure to avoid encode problems, I have tried the same mp4 file > directly and only with an Apache Server. It is loaded well in Safari and all > other browsers. > Last point, if the reader pipeline is cached or not (or if the browser cache > is empty or not) the behaviour is completely different following browser > used. In all cases, with Safari it never works. > Thank you for you helps . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COCOON-2368) Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12
[ https://issues.apache.org/jira/browse/COCOON-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970424#comment-16970424 ] Modou Dia commented on COCOON-2368: --- Sorry, but by "request response flow", I suppose you mean the process followed by a request ? If it's true, I schematized below flows. - Case 1: work in Safari ( http://test-v4.pleade.com/test.mp4 ) Web Browser ==> Apache Server (2.4) ==> test.mp4 ==> Apache Server ==> Web Browser - Case 2: not work in Safari ( http://test-v4.pleade.com/functions/ead/detached/docs/test.mp4 ) Web Browser ==> Apache Server (2.4) ==> AJP Connector ==> Tomcat ==> Cocoon ==> Reader Pipeline ==> test.mp4 ==> Reader Pipeline ==> Cocoon ==> Tomcat ==> AJP Connector ==> Apache Server ==> Web Browser - Case 3: (same as case 2 but without Apache and AJP) : not work in Safari ( http://test-v4.pleade.com:8205/pleade/functions/ead/detached/docs/test.mp4 ) Web Browser ==> Tomcat ==> Cocoon ==> Reader Pipeline ==> test.mp4 ==> Reader Pipeline ==> Cocoon ==> Tomcat ==> Web Browser In our sitemap, we call the reader pipeline like this: Thanks ! > Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12 > -- > > Key: COCOON-2368 > URL: https://issues.apache.org/jira/browse/COCOON-2368 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core, Blocks: (Undefined) >Affects Versions: 2.1.12 >Reporter: Modou Dia >Priority: Major > > Hello, > I try to load a MP4 File with a Cocoon Reader. It works well in all major > browsers except Safari (desktop and IOS). > Referring to this thread : > https://stackoverflow.com/questions/30199261/why-wont-safari-play-file-without-extension-in-video/51901198#51901198, > I overloaded the default Reader' by forcing cocoon to add a Byte Range > header (and 206 status code) ... It still does not work. > For being sure to avoid encode problems, I have tried the same mp4 file > directly and only with an Apache Server. It is loaded well in Safari and all > other browsers. > Last point, if the reader pipeline is cached or not (or if the browser cache > is empty or not) the behaviour is completely different following browser > used. In all cases, with Safari it never works. > Thank you for you helps . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COCOON-2368) Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12
[ https://issues.apache.org/jira/browse/COCOON-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970162#comment-16970162 ] Torsten Curdt commented on COCOON-2368: --- You should provide the full request response flow (without the body) for both cases. Working and not working. > Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12 > -- > > Key: COCOON-2368 > URL: https://issues.apache.org/jira/browse/COCOON-2368 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core, Blocks: (Undefined) >Affects Versions: 2.1.12 >Reporter: Modou Dia >Priority: Major > > Hello, > I try to load a MP4 File with a Cocoon Reader. It works well in all major > browsers except Safari (desktop and IOS). > Referring to this thread : > https://stackoverflow.com/questions/30199261/why-wont-safari-play-file-without-extension-in-video/51901198#51901198, > I overloaded the default Reader' by forcing cocoon to add a Byte Range > header (and 206 status code) ... It still does not work. > For being sure to avoid encode problems, I have tried the same mp4 file > directly and only with an Apache Server. It is loaded well in Safari and all > other browsers. > Last point, if the reader pipeline is cached or not (or if the browser cache > is empty or not) the behaviour is completely different following browser > used. In all cases, with Safari it never works. > Thank you for you helps . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COCOON-2368) Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12
[ https://issues.apache.org/jira/browse/COCOON-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970151#comment-16970151 ] Modou Dia commented on COCOON-2368: --- We have added the Etag header just for a test. It have no incidence on the result. Please can you give more details on the sort of informations you need. Thanks ! > Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12 > -- > > Key: COCOON-2368 > URL: https://issues.apache.org/jira/browse/COCOON-2368 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core, Blocks: (Undefined) >Affects Versions: 2.1.12 >Reporter: Modou Dia >Priority: Major > > Hello, > I try to load a MP4 File with a Cocoon Reader. It works well in all major > browsers except Safari (desktop and IOS). > Referring to this thread : > https://stackoverflow.com/questions/30199261/why-wont-safari-play-file-without-extension-in-video/51901198#51901198, > I overloaded the default Reader' by forcing cocoon to add a Byte Range > header (and 206 status code) ... It still does not work. > For being sure to avoid encode problems, I have tried the same mp4 file > directly and only with an Apache Server. It is loaded well in Safari and all > other browsers. > Last point, if the reader pipeline is cached or not (or if the browser cache > is empty or not) the behaviour is completely different following browser > used. In all cases, with Safari it never works. > Thank you for you helps . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COCOON-2368) Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12
[ https://issues.apache.org/jira/browse/COCOON-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970091#comment-16970091 ] Torsten Curdt commented on COCOON-2368: --- For the record $ curl -I http://test-v4.pleade.com/functions/ead/detached/docs/test.mp4 HTTP/1.1 200 OK Date: Fri, 08 Nov 2019 11:17:23 GMT Server: Apache X-Cocoon-Version: 2.1.10 Set-Cookie: JSESSIONID=43554C2D80E2A947FA8015821E611385; Path=/; HttpOnly Accept-Ranges: bytes Last-Modified: Fri, 08 Nov 2019 10:18:43 GMT access-control-allow-origin: * ETag: 1 cache-control: max-age=31536000 Content-Type: video/mp4 Content-Length: 589052 $ curl -I http://test-v4.pleade.com/test.mp4 HTTP/1.1 200 OK Date: Fri, 08 Nov 2019 11:17:39 GMT Server: Apache Last-Modified: Tue, 29 Oct 2019 14:54:19 GMT ETag: "8fcfc-5960dca7db96d" Accept-Ranges: bytes Content-Length: 589052 Content-Type: video/mp4 But this is not enough information for debugging this. You need at the full request response flow. And the ETag header with "1" looks fishy as is. While we will try to help as good as we can you need to provide more information or hire someone to do the debugging for you. > Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12 > -- > > Key: COCOON-2368 > URL: https://issues.apache.org/jira/browse/COCOON-2368 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core, Blocks: (Undefined) >Affects Versions: 2.1.12 >Reporter: Modou Dia >Priority: Major > > Hello, > I try to load a MP4 File with a Cocoon Reader. It works well in all major > browsers except Safari (desktop and IOS). > Referring to this thread : > https://stackoverflow.com/questions/30199261/why-wont-safari-play-file-without-extension-in-video/51901198#51901198, > I overloaded the default Reader' by forcing cocoon to add a Byte Range > header (and 206 status code) ... It still does not work. > For being sure to avoid encode problems, I have tried the same mp4 file > directly and only with an Apache Server. It is loaded well in Safari and all > other browsers. > Last point, if the reader pipeline is cached or not (or if the browser cache > is empty or not) the behaviour is completely different following browser > used. In all cases, with Safari it never works. > Thank you for you helps . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COCOON-2368) Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12
[ https://issues.apache.org/jira/browse/COCOON-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970068#comment-16970068 ] Modou Dia commented on COCOON-2368: --- Hello [~tcurdt], Thank you for you reply. The problem impacts all IOS users including Iphone and Ipad. We have yet done parallels tests scenario. Here you have URLs used : - 1st URL (Served with Cocoon) : http://test-v4.pleade.com/functions/ead/detached/docs/test.mp4 (not work in Safari) - 2nd URL (Served with Apache): http://test-v4.pleade.com/test.mp4 (work with Safari) As you can notice, we have adapted the Cocoon Reader for serving the same headers as well as Apache ... Thanks ! > Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12 > -- > > Key: COCOON-2368 > URL: https://issues.apache.org/jira/browse/COCOON-2368 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core, Blocks: (Undefined) >Affects Versions: 2.1.12 >Reporter: Modou Dia >Priority: Major > > Hello, > I try to load a MP4 File with a Cocoon Reader. It works well in all major > browsers except Safari (desktop and IOS). > Referring to this thread : > https://stackoverflow.com/questions/30199261/why-wont-safari-play-file-without-extension-in-video/51901198#51901198, > I overloaded the default Reader' by forcing cocoon to add a Byte Range > header (and 206 status code) ... It still does not work. > For being sure to avoid encode problems, I have tried the same mp4 file > directly and only with an Apache Server. It is loaded well in Safari and all > other browsers. > Last point, if the reader pipeline is cached or not (or if the browser cache > is empty or not) the behaviour is completely different following browser > used. In all cases, with Safari it never works. > Thank you for you helps . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (COCOON-2368) Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12
[ https://issues.apache.org/jira/browse/COCOON-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Curdt updated COCOON-2368: -- Priority: Major (was: Blocker) > Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12 > -- > > Key: COCOON-2368 > URL: https://issues.apache.org/jira/browse/COCOON-2368 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core, Blocks: (Undefined) >Affects Versions: 2.1.12 >Reporter: Modou Dia >Priority: Major > > Hello, > I try to load a MP4 File with a Cocoon Reader. It works well in all major > browsers except Safari (desktop and IOS). > Referring to this thread : > https://stackoverflow.com/questions/30199261/why-wont-safari-play-file-without-extension-in-video/51901198#51901198, > I overloaded the default Reader' by forcing cocoon to add a Byte Range > header (and 206 status code) ... It still does not work. > For being sure to avoid encode problems, I have tried the same mp4 file > directly and only with an Apache Server. It is loaded well in Safari and all > other browsers. > Last point, if the reader pipeline is cached or not (or if the browser cache > is empty or not) the behaviour is completely different following browser > used. In all cases, with Safari it never works. > Thank you for you helps . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COCOON-2368) Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12
[ https://issues.apache.org/jira/browse/COCOON-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970022#comment-16970022 ] Torsten Curdt commented on COCOON-2368: --- What I would suggest is to record the HTTP flow between a working and a non-working scenario. Then you can deduce what feature is missing for supporting Safari. Everything else is a bit like stabbing in the dark. Given it works on all major browsers but Safari this certainly is not a blocker in Cocoon. I will hence reduce the severity. > Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12 > -- > > Key: COCOON-2368 > URL: https://issues.apache.org/jira/browse/COCOON-2368 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core, Blocks: (Undefined) >Affects Versions: 2.1.12 >Reporter: Modou Dia >Priority: Blocker > > Hello, > I try to load a MP4 File with a Cocoon Reader. It works well in all major > browsers except Safari (desktop and IOS). > Referring to this thread : > https://stackoverflow.com/questions/30199261/why-wont-safari-play-file-without-extension-in-video/51901198#51901198, > I overloaded the default Reader' by forcing cocoon to add a Byte Range > header (and 206 status code) ... It still does not work. > For being sure to avoid encode problems, I have tried the same mp4 file > directly and only with an Apache Server. It is loaded well in Safari and all > other browsers. > Last point, if the reader pipeline is cached or not (or if the browser cache > is empty or not) the behaviour is completely different following browser > used. In all cases, with Safari it never works. > Thank you for you helps . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (COCOON-2368) Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12
Modou Dia created COCOON-2368: - Summary: Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12 Key: COCOON-2368 URL: https://issues.apache.org/jira/browse/COCOON-2368 Project: Cocoon Issue Type: Bug Components: * Cocoon Core, Blocks: (Undefined) Affects Versions: 2.1.12 Reporter: Modou Dia Hello, I try to load a MP4 File with a Cocoon Reader. It works well in all major browsers except Safari (desktop and IOS). Referring to this thread : https://stackoverflow.com/questions/30199261/why-wont-safari-play-file-without-extension-in-video/51901198#51901198, I overloaded the default Reader' by forcing cocoon to add a Byte Range header (and 206 status code) ... It still does not work. For being sure to avoid encode problems, I have tried the same mp4 file directly and only with an Apache Server. It is loaded well in Safari and all other browsers. Last point, if the reader pipeline is cached or not (or if the browser cache is empty or not) the behaviour is completely different following browser used. In all cases, with Safari it never works. Thank you for you helps . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (COCOON-2360) [2,2] Inconsistent method names
[
https://issues.apache.org/jira/browse/COCOON-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò closed COCOON-2360.
--
Resolution: Not A Problem
It's not inconsistent, the select() method is on a class named DateSelector,
extending AbstractSwitchSelector.
This method's name is also given according to sitemap's standards,
> [2,2] Inconsistent method names
> ---
>
> Key: COCOON-2360
> URL: https://issues.apache.org/jira/browse/COCOON-2360
> Project: Cocoon
> Issue Type: Improvement
> Components: Blocks: (Undefined)
>Affects Versions: 2.2
>Reporter: KuiLIU
>Assignee: Francesco Chicchiriccò
>Priority: Minor
>
> The following method is named as "select".
> "select" is prone to mean that something will be selected.
> But this method actually checks whether the expression is contained or not.
> So, rename it as "contains" should be more clearly and intuitively.
> public boolean select( String expression ) {
> return this.set.contains( expression );
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (COCOON-2360) [2,2] Inconsistent method names
[
https://issues.apache.org/jira/browse/COCOON-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated COCOON-2360:
---
Fix Version/s: (was: 2.2.1)
> [2,2] Inconsistent method names
> ---
>
> Key: COCOON-2360
> URL: https://issues.apache.org/jira/browse/COCOON-2360
> Project: Cocoon
> Issue Type: Improvement
> Components: Blocks: (Undefined)
>Affects Versions: 2.2
>Reporter: KuiLIU
>Assignee: Francesco Chicchiriccò
>Priority: Minor
>
> The following method is named as "select".
> "select" is prone to mean that something will be selected.
> But this method actually checks whether the expression is contained or not.
> So, rename it as "contains" should be more clearly and intuitively.
> public boolean select( String expression ) {
> return this.set.contains( expression );
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (COCOON-2360) [2,2] Inconsistent method names
[
https://issues.apache.org/jira/browse/COCOON-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò reassigned COCOON-2360:
--
Assignee: Francesco Chicchiriccò
> [2,2] Inconsistent method names
> ---
>
> Key: COCOON-2360
> URL: https://issues.apache.org/jira/browse/COCOON-2360
> Project: Cocoon
> Issue Type: Improvement
> Components: Blocks: (Undefined)
>Affects Versions: 2.2
>Reporter: KuiLIU
>Assignee: Francesco Chicchiriccò
>Priority: Major
>
> The following method is named as "select".
> "select" is prone to mean that something will be selected.
> But this method actually checks whether the expression is contained or not.
> So, rename it as "contains" should be more clearly and intuitively.
> public boolean select( String expression ) {
> return this.set.contains( expression );
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (COCOON-2360) [2,2] Inconsistent method names
[
https://issues.apache.org/jira/browse/COCOON-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated COCOON-2360:
---
Fix Version/s: 2.2.1
> [2,2] Inconsistent method names
> ---
>
> Key: COCOON-2360
> URL: https://issues.apache.org/jira/browse/COCOON-2360
> Project: Cocoon
> Issue Type: Improvement
> Components: Blocks: (Undefined)
>Affects Versions: 2.2
>Reporter: KuiLIU
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 2.2.1
>
>
> The following method is named as "select".
> "select" is prone to mean that something will be selected.
> But this method actually checks whether the expression is contained or not.
> So, rename it as "contains" should be more clearly and intuitively.
> public boolean select( String expression ) {
> return this.set.contains( expression );
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (COCOON-2360) [2,2] Inconsistent method names
[
https://issues.apache.org/jira/browse/COCOON-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated COCOON-2360:
---
Priority: Minor (was: Major)
> [2,2] Inconsistent method names
> ---
>
> Key: COCOON-2360
> URL: https://issues.apache.org/jira/browse/COCOON-2360
> Project: Cocoon
> Issue Type: Improvement
> Components: Blocks: (Undefined)
>Affects Versions: 2.2
>Reporter: KuiLIU
>Assignee: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 2.2.1
>
>
> The following method is named as "select".
> "select" is prone to mean that something will be selected.
> But this method actually checks whether the expression is contained or not.
> So, rename it as "contains" should be more clearly and intuitively.
> public boolean select( String expression ) {
> return this.set.contains( expression );
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (COCOON-2361) Cannot upload a file with name containing a '=' or a ';'
[
https://issues.apache.org/jira/browse/COCOON-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cédric Damioli closed COCOON-2361.
--
Resolution: Fixed
> Cannot upload a file with name containing a '=' or a ';'
>
>
> Key: COCOON-2361
> URL: https://issues.apache.org/jira/browse/COCOON-2361
> Project: Cocoon
> Issue Type: Bug
> Components: * Cocoon Core
>Affects Versions: 2.1.12
>Reporter: Cédric Damioli
>Priority: Major
> Fix For: 2.1.13
>
>
> The RFC allows eg.
> {code}Content-Disposition: form-data; name="file";
> filename="6008160736474408812-account_id=1.jpg"{code}
> but the MultiPartParser tokenizes on the '=' Inside the filename, leading to
> incorrect file name after upload
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (COCOON-2361) Cannot upload a file with name containing a '=' or a ';'
[
https://issues.apache.org/jira/browse/COCOON-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781832#comment-16781832
]
Hudson commented on COCOON-2361:
SUCCESS: Integrated in Jenkins build Cocoon 2.1.X #138 (See
[https://builds.apache.org/job/Cocoon%202.1.X/138/])
COCOON-2361 Cannot upload a file with name containing a '=' or a ';' (cdamioli:
[http://svn.apache.org/viewvc/?view=rev=1854601])
* (edit)
BRANCH_2_1_X/src/java/org/apache/cocoon/servlet/multipart/MultipartParser.java
> Cannot upload a file with name containing a '=' or a ';'
>
>
> Key: COCOON-2361
> URL: https://issues.apache.org/jira/browse/COCOON-2361
> Project: Cocoon
> Issue Type: Bug
> Components: * Cocoon Core
>Affects Versions: 2.1.12
>Reporter: Cédric Damioli
>Priority: Major
> Fix For: 2.1.13
>
>
> The RFC allows eg.
> {code}Content-Disposition: form-data; name="file";
> filename="6008160736474408812-account_id=1.jpg"{code}
> but the MultiPartParser tokenizes on the '=' Inside the filename, leading to
> incorrect file name after upload
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (COCOON-2359) [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8
[ https://issues.apache.org/jira/browse/COCOON-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel updated COCOON-2359: - Summary: [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8 (was: Fix incompatibility of cocoon-captcha with JDK 1.7/1.8) > [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8 > > > Key: COCOON-2359 > URL: https://issues.apache.org/jira/browse/COCOON-2359 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Captcha >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Priority: Major > Fix For: 2.2.1 > > > Goal is to remove the direct usage of > - JPEGImageEncoder > - JPEGEncodeParam > inside CaptchaReader.java > And replace them with the newer 1.6 API of ImageIO > https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COCOON-2360) [2,2] Inconsistent method names
[
https://issues.apache.org/jira/browse/COCOON-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alfred Nathaniel updated COCOON-2360:
-
Affects Version/s: 2.2
Summary: [2,2] Inconsistent method names (was: Inconsistent
method names)
> [2,2] Inconsistent method names
> ---
>
> Key: COCOON-2360
> URL: https://issues.apache.org/jira/browse/COCOON-2360
> Project: Cocoon
> Issue Type: Improvement
> Components: Blocks: (Undefined)
>Affects Versions: 2.2
>Reporter: KuiLIU
>Priority: Major
>
> The following method is named as "select".
> "select" is prone to mean that something will be selected.
> But this method actually checks whether the expression is contained or not.
> So, rename it as "contains" should be more clearly and intuitively.
> public boolean select( String expression ) {
> return this.set.contains( expression );
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (COCOON-2364) Update to fop-1.1
[ https://issues.apache.org/jira/browse/COCOON-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel closed COCOON-2364. Resolution: Fixed Assignee: Alfred Nathaniel > Update to fop-1.1 > - > > Key: COCOON-2364 > URL: https://issues.apache.org/jira/browse/COCOON-2364 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: FOP >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Assignee: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 includes fop-1.0. fop-1.1 contains an impressive list of > improvements: https://xmlgraphics.apache.org/fop/1.1/changes_1.1.html > Update is straightforward except that the ExtendableRendererFactory must be > removed. The old Renderer implementations it is based are no longer > available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (COCOON-2362) Unsynchronized HashMap.put leads to infinite loop
[
https://issues.apache.org/jira/browse/COCOON-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alfred Nathaniel closed COCOON-2362.
Resolution: Fixed
Assignee: Alfred Nathaniel
> Unsynchronized HashMap.put leads to infinite loop
> -
>
> Key: COCOON-2362
> URL: https://issues.apache.org/jira/browse/COCOON-2362
> Project: Cocoon
> Issue Type: Bug
> Components: * Cocoon Core
>Affects Versions: 2.1.12
>Reporter: Alfred Nathaniel
>Assignee: Alfred Nathaniel
>Priority: Major
> Fix For: 2.1.13
>
>
> Under load a Cocoon thread occasionally starts spinning at 100% in an
> infinite loop. The reason is concurrent writing to a HashMap without proper
> synchronization. The two stack traces are:
> {noformat}
> java.util.HashMap.put (HashMap.java:420)
> org.apache.cocoon.components.language.generator.GeneratorSelector.select
> (GeneratorSelector.java:125)
> {noformat}
> {noformat}
> java.util.HashMap.getEntry(HashMap.java:465)
> java.util.HashMap.get(HashMap.java:417)
> org.apache.cocoon.reading.ResourceReader.getLastModified(ResourceReader.java:242)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (COCOON-2363) Update to poi-3.14
[ https://issues.apache.org/jira/browse/COCOON-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel closed COCOON-2363. Resolution: Fixed Assignee: Alfred Nathaniel > Update to poi-3.14 > -- > > Key: COCOON-2363 > URL: https://issues.apache.org/jira/browse/COCOON-2363 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: POI >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Assignee: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > The Cocoon 2.1.12 POI block uses poi-3.10-final which contains a few security > issues. > Updating to 3.14 is low-hanging fruit, except that minimum Java is 1.6. > (3.15 drops deprecated methods. 4.0 raises Java to 1.8). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (COCOON-2365) Update to httpclient-3.1
[ https://issues.apache.org/jira/browse/COCOON-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel closed COCOON-2365. Resolution: Fixed > Update to httpclient-3.1 > > > Key: COCOON-2365 > URL: https://issues.apache.org/jira/browse/COCOON-2365 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: XSP >Reporter: Alfred Nathaniel >Assignee: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 uses httpclient-2.0.2 in various blocks (XSP, Proxy, WebDAV). > The Commons HttpClient project is now end of life and has been replaced by > the Apache HttpComponents project. > An update to the latest available version httpclient-3.1 is low-hanging fruit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (COCOON-2367) Update to xalan-2.7.2 and add serializer-2.7.2
[ https://issues.apache.org/jira/browse/COCOON-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel closed COCOON-2367. Resolution: Fixed > Update to xalan-2.7.2 and add serializer-2.7.2 > -- > > Key: COCOON-2367 > URL: https://issues.apache.org/jira/browse/COCOON-2367 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Assignee: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 uses xalan-2.7.1 which contains a security issue. Upgrade to > xalan-2.7.2 is straightforward. Only the spawned-off serializer-2.7.2 jar > must be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (COCOON-2366) XSP block doesn't compile with Java 8
[ https://issues.apache.org/jira/browse/COCOON-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel closed COCOON-2366. Resolution: Fixed > XSP block doesn't compile with Java 8 > - > > Key: COCOON-2366 > URL: https://issues.apache.org/jira/browse/COCOON-2366 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: XSP >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Assignee: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 provides as option to use the JDK compiler for XSPs. The Javac > class calls internal APIs no longer available in recent Java versions. Since > Java 6 the standard API javax.tool.JavaCompiler is provided. > Source code to compile with Java 5 and Java 6 would need to do indirect class > loading calls. Better to drop Java 5 support in Cocoon and declare 1.6 to be > the minimum version, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (COCOON-2366) XSP block doesn't compile with Java 8
[ https://issues.apache.org/jira/browse/COCOON-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel reassigned COCOON-2366: Assignee: Alfred Nathaniel > XSP block doesn't compile with Java 8 > - > > Key: COCOON-2366 > URL: https://issues.apache.org/jira/browse/COCOON-2366 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: XSP >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Assignee: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 provides as option to use the JDK compiler for XSPs. The Javac > class calls internal APIs no longer available in recent Java versions. Since > Java 6 the standard API javax.tool.JavaCompiler is provided. > Source code to compile with Java 5 and Java 6 would need to do indirect class > loading calls. Better to drop Java 5 support in Cocoon and declare 1.6 to be > the minimum version, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (COCOON-2365) Update to httpclient-3.1
[ https://issues.apache.org/jira/browse/COCOON-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel reassigned COCOON-2365: Assignee: Alfred Nathaniel > Update to httpclient-3.1 > > > Key: COCOON-2365 > URL: https://issues.apache.org/jira/browse/COCOON-2365 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: XSP >Reporter: Alfred Nathaniel >Assignee: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 uses httpclient-2.0.2 in various blocks (XSP, Proxy, WebDAV). > The Commons HttpClient project is now end of life and has been replaced by > the Apache HttpComponents project. > An update to the latest available version httpclient-3.1 is low-hanging fruit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (COCOON-2367) Update to xalan-2.7.2 and add serializer-2.7.2
[ https://issues.apache.org/jira/browse/COCOON-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel reassigned COCOON-2367: Assignee: Alfred Nathaniel > Update to xalan-2.7.2 and add serializer-2.7.2 > -- > > Key: COCOON-2367 > URL: https://issues.apache.org/jira/browse/COCOON-2367 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Assignee: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 uses xalan-2.7.1 which contains a security issue. Upgrade to > xalan-2.7.2 is straightforward. Only the spawned-off serializer-2.7.2 jar > must be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2367) Update to xalan-2.7.2 and add serializer-2.7.2
[ https://issues.apache.org/jira/browse/COCOON-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774266#comment-16774266 ] Alfred Nathaniel commented on COCOON-2367: -- Committed fix to 2.1.13-dev. http://svn.apache.org/viewvc?view=revision=1853788 > Update to xalan-2.7.2 and add serializer-2.7.2 > -- > > Key: COCOON-2367 > URL: https://issues.apache.org/jira/browse/COCOON-2367 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 uses xalan-2.7.1 which contains a security issue. Upgrade to > xalan-2.7.2 is straightforward. Only the spawned-off serializer-2.7.2 jar > must be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (COCOON-2367) Update to xalan-2.7.2 and add serializer-2.7.2
Alfred Nathaniel created COCOON-2367: Summary: Update to xalan-2.7.2 and add serializer-2.7.2 Key: COCOON-2367 URL: https://issues.apache.org/jira/browse/COCOON-2367 Project: Cocoon Issue Type: Improvement Components: * Cocoon Core Affects Versions: 2.1.12 Reporter: Alfred Nathaniel Fix For: 2.1.13 Cocoon 2.1.12 uses xalan-2.7.1 which contains a security issue. Upgrade to xalan-2.7.2 is straightforward. Only the spawned-off serializer-2.7.2 jar must be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (COCOON-2366) XSP block doesn't compile with Java 8
Alfred Nathaniel created COCOON-2366: Summary: XSP block doesn't compile with Java 8 Key: COCOON-2366 URL: https://issues.apache.org/jira/browse/COCOON-2366 Project: Cocoon Issue Type: Improvement Components: Blocks: XSP Affects Versions: 2.1.12 Reporter: Alfred Nathaniel Fix For: 2.1.13 Cocoon 2.1.12 provides as option to use the JDK compiler for XSPs. The Javac class calls internal APIs no longer available in recent Java versions. Since Java 6 the standard API javax.tool.JavaCompiler is provided. Source code to compile with Java 5 and Java 6 would need to do indirect class loading calls. Better to drop Java 5 support in Cocoon and declare 1.6 to be the minimum version, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2366) XSP block doesn't compile with Java 8
[ https://issues.apache.org/jira/browse/COCOON-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774256#comment-16774256 ] Alfred Nathaniel commented on COCOON-2366: -- Retaining Javac, Jikes, and Pizza compilers as options is rather nostalgic. The Eclipse JDT compiler included in the standard Cocoon distribution is quite sufficient. > XSP block doesn't compile with Java 8 > - > > Key: COCOON-2366 > URL: https://issues.apache.org/jira/browse/COCOON-2366 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: XSP >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 provides as option to use the JDK compiler for XSPs. The Javac > class calls internal APIs no longer available in recent Java versions. Since > Java 6 the standard API javax.tool.JavaCompiler is provided. > Source code to compile with Java 5 and Java 6 would need to do indirect class > loading calls. Better to drop Java 5 support in Cocoon and declare 1.6 to be > the minimum version, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COCOON-2365) Update to httpclient-3.1
[ https://issues.apache.org/jira/browse/COCOON-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated COCOON-2365: --- Fix Version/s: 2.1.13 > Update to httpclient-3.1 > > > Key: COCOON-2365 > URL: https://issues.apache.org/jira/browse/COCOON-2365 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: XSP >Reporter: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 uses httpclient-2.0.2 in various blocks (XSP, Proxy, WebDAV). > The Commons HttpClient project is now end of life and has been replaced by > the Apache HttpComponents project. > An update to the latest available version httpclient-3.1 is low-hanging fruit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2366) XSP block doesn't compile with Java 8
[ https://issues.apache.org/jira/browse/COCOON-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774251#comment-16774251 ] Alfred Nathaniel commented on COCOON-2366: -- Committed fix to 2.1.13-dev. http://svn.apache.org/viewvc?view=revision=1853873 > XSP block doesn't compile with Java 8 > - > > Key: COCOON-2366 > URL: https://issues.apache.org/jira/browse/COCOON-2366 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: XSP >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 provides as option to use the JDK compiler for XSPs. The Javac > class calls internal APIs no longer available in recent Java versions. Since > Java 6 the standard API javax.tool.JavaCompiler is provided. > Source code to compile with Java 5 and Java 6 would need to do indirect class > loading calls. Better to drop Java 5 support in Cocoon and declare 1.6 to be > the minimum version, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2365) Update to httpclient-3.1
[ https://issues.apache.org/jira/browse/COCOON-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774243#comment-16774243 ] Alfred Nathaniel commented on COCOON-2365: -- Committed fix to 2.1.13-dev. http://svn.apache.org/viewvc?view=revision=1853818 > Update to httpclient-3.1 > > > Key: COCOON-2365 > URL: https://issues.apache.org/jira/browse/COCOON-2365 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: XSP >Reporter: Alfred Nathaniel >Priority: Major > > Cocoon 2.1.12 uses httpclient-2.0.2 in various blocks (XSP, Proxy, WebDAV). > The Commons HttpClient project is now end of life and has been replaced by > the Apache HttpComponents project. > An update to the latest available version httpclient-3.1 is low-hanging fruit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (COCOON-2365) Update to httpclient-3.1
Alfred Nathaniel created COCOON-2365: Summary: Update to httpclient-3.1 Key: COCOON-2365 URL: https://issues.apache.org/jira/browse/COCOON-2365 Project: Cocoon Issue Type: Improvement Components: Blocks: XSP Reporter: Alfred Nathaniel Cocoon 2.1.12 uses httpclient-3.0 in varies blocks (XSP, Proxy, WebDAV). The Commons HttpClient project is now end of life and has been replaced by the Apache HttpComponents project. An update to the latest available version httpclient-3.1 is low-hanging fruit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COCOON-2365) Update to httpclient-3.1
[ https://issues.apache.org/jira/browse/COCOON-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel updated COCOON-2365: - Description: Cocoon 2.1.12 uses httpclient-2.0.2 in various blocks (XSP, Proxy, WebDAV). The Commons HttpClient project is now end of life and has been replaced by the Apache HttpComponents project. An update to the latest available version httpclient-3.1 is low-hanging fruit. was: Cocoon 2.1.12 uses httpclient-3.0 in varies blocks (XSP, Proxy, WebDAV). The Commons HttpClient project is now end of life and has been replaced by the Apache HttpComponents project. An update to the latest available version httpclient-3.1 is low-hanging fruit. > Update to httpclient-3.1 > > > Key: COCOON-2365 > URL: https://issues.apache.org/jira/browse/COCOON-2365 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: XSP >Reporter: Alfred Nathaniel >Priority: Major > > Cocoon 2.1.12 uses httpclient-2.0.2 in various blocks (XSP, Proxy, WebDAV). > The Commons HttpClient project is now end of life and has been replaced by > the Apache HttpComponents project. > An update to the latest available version httpclient-3.1 is low-hanging fruit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2364) Update to fop-1.1
[ https://issues.apache.org/jira/browse/COCOON-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774202#comment-16774202 ] Alfred Nathaniel commented on COCOON-2364: -- Committed fix to 2.1.13-dev. http://svn.apache.org/viewvc?view=revision=1853820 > Update to fop-1.1 > - > > Key: COCOON-2364 > URL: https://issues.apache.org/jira/browse/COCOON-2364 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: FOP >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > Cocoon 2.1.12 includes fop-1.0. fop-1.1 contains an impressive list of > improvements: https://xmlgraphics.apache.org/fop/1.1/changes_1.1.html > Update is straightforward except that the ExtendableRendererFactory must be > removed. The old Renderer implementations it is based are no longer > available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (COCOON-2364) Update to fop-1.1
Alfred Nathaniel created COCOON-2364: Summary: Update to fop-1.1 Key: COCOON-2364 URL: https://issues.apache.org/jira/browse/COCOON-2364 Project: Cocoon Issue Type: Improvement Components: Blocks: FOP Affects Versions: 2.1.12 Reporter: Alfred Nathaniel Fix For: 2.1.13 Cocoon 2.1.12 includes fop-1.0. fop-1.1 contains an impressive list of improvements: https://xmlgraphics.apache.org/fop/1.1/changes_1.1.html Update is straightforward except that the ExtendableRendererFactory must be removed. The old Renderer implementations it is based are no longer available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COCOON-2363) Update to poi-3.14
[ https://issues.apache.org/jira/browse/COCOON-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel updated COCOON-2363: - Description: The Cocoon 2.1.12 POI block uses poi-3.10-final which contains a few security issues. Updating to 3.14 is low-hanging fruit, except that minimum Java is 1.6. (3.15 drops deprecated methods. 4.0 raises Java to 1.8). was: The Cocoon 2.1.12 POI block uses poi-3.10-final which contains a few security issues. Updating to 3.14 is low-hanging fruit, except that minimum Java is 1.6 since 3.11. (3.15 drops deprecated methods. 4.0 raises Java to 1.8). > Update to poi-3.14 > -- > > Key: COCOON-2363 > URL: https://issues.apache.org/jira/browse/COCOON-2363 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: POI >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > The Cocoon 2.1.12 POI block uses poi-3.10-final which contains a few security > issues. > Updating to 3.14 is low-hanging fruit, except that minimum Java is 1.6. > (3.15 drops deprecated methods. 4.0 raises Java to 1.8). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2363) Update to poi-3.14
[ https://issues.apache.org/jira/browse/COCOON-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774179#comment-16774179 ] Alfred Nathaniel commented on COCOON-2363: -- Commited fix to 2.1.13-dev, including updates to * commons-logging-1.2 * log4j-1.2.17 * commons-codec-1.10.jar * curvesapi-1.06.jar * poi-3.14.jar * poi-ooxml-3.14.jar * poi-ooxml-schemas-3.14.jar * xmlbeans-3.0.2.jar * slf4j-log4j12-1.6.4.jar http://svn.apache.org/viewvc?view=revision=1853823 http://svn.apache.org/viewvc?view=revision=1853975 > Update to poi-3.14 > -- > > Key: COCOON-2363 > URL: https://issues.apache.org/jira/browse/COCOON-2363 > Project: Cocoon > Issue Type: Improvement > Components: Blocks: POI >Affects Versions: 2.1.12 >Reporter: Alfred Nathaniel >Priority: Major > Fix For: 2.1.13 > > > The Cocoon 2.1.12 POI block uses poi-3.10-final which contains a few security > issues. > Updating to 3.14 is low-hanging fruit, except that minimum Java is 1.6. > (3.15 drops deprecated methods. 4.0 raises Java to 1.8). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (COCOON-2363) Update to poi-3.14
Alfred Nathaniel created COCOON-2363: Summary: Update to poi-3.14 Key: COCOON-2363 URL: https://issues.apache.org/jira/browse/COCOON-2363 Project: Cocoon Issue Type: Improvement Components: Blocks: POI Affects Versions: 2.1.12 Reporter: Alfred Nathaniel Fix For: 2.1.13 The Cocoon 2.1.12 POI block uses poi-3.10-final which contains a few security issues. Updating to 3.14 is low-hanging fruit, except that minimum Java is 1.6 since 3.11. (3.15 drops deprecated methods. 4.0 raises Java to 1.8). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2362) Unsynchronized HashMap.put leads to infinite loop
[
https://issues.apache.org/jira/browse/COCOON-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774123#comment-16774123
]
Alfred Nathaniel commented on COCOON-2362:
--
Fix committed to 2.1.13-dev.
http://svn.apache.org/viewvc?view=revision=1853824
> Unsynchronized HashMap.put leads to infinite loop
> -
>
> Key: COCOON-2362
> URL: https://issues.apache.org/jira/browse/COCOON-2362
> Project: Cocoon
> Issue Type: Bug
> Components: * Cocoon Core
>Affects Versions: 2.1.12
>Reporter: Alfred Nathaniel
>Priority: Major
> Fix For: 2.1.13
>
>
> Under load a Cocoon thread occasionally starts spinning at 100% in an
> infinite loop. The reason is concurrent writing to a HashMap without proper
> synchronization. The two stack traces are:
> {noformat}
> java.util.HashMap.put (HashMap.java:420)
> org.apache.cocoon.components.language.generator.GeneratorSelector.select
> (GeneratorSelector.java:125)
> {noformat}
> {noformat}
> java.util.HashMap.getEntry(HashMap.java:465)
> java.util.HashMap.get(HashMap.java:417)
> org.apache.cocoon.reading.ResourceReader.getLastModified(ResourceReader.java:242)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (COCOON-2362) Unsynchronized HashMap.put leads to infinite loop
Alfred Nathaniel created COCOON-2362:
Summary: Unsynchronized HashMap.put leads to infinite loop
Key: COCOON-2362
URL: https://issues.apache.org/jira/browse/COCOON-2362
Project: Cocoon
Issue Type: Bug
Components: * Cocoon Core
Affects Versions: 2.1.12
Reporter: Alfred Nathaniel
Fix For: 2.1.13
Under load a Cocoon thread occasionally starts spinning at 100% in an infinite
loop. The reason is concurrent writing to a HashMap without proper
synchronization. The two stack traces are:
{noformat}
java.util.HashMap.put (HashMap.java:420)
org.apache.cocoon.components.language.generator.GeneratorSelector.select
(GeneratorSelector.java:125)
{noformat}
{noformat}
java.util.HashMap.getEntry(HashMap.java:465)
java.util.HashMap.get(HashMap.java:417)
org.apache.cocoon.reading.ResourceReader.getLastModified(ResourceReader.java:242)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (COCOON-2361) Cannot upload a file with name containing a '=' or a ';'
Cédric Damioli created COCOON-2361:
--
Summary: Cannot upload a file with name containing a '=' or a ';'
Key: COCOON-2361
URL: https://issues.apache.org/jira/browse/COCOON-2361
Project: Cocoon
Issue Type: Bug
Components: * Cocoon Core
Affects Versions: 2.1.12
Reporter: Cédric Damioli
Fix For: 2.1.13
The RFC allows eg.
{code}Content-Disposition: form-data; name="file";
filename="6008160736474408812-account_id=1.jpg"{code}
but the MultiPartParser tokenizes on the '=' Inside the filename, leading to
incorrect file name after upload
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (COCOON3-139) DELETE - tkkk
[ https://issues.apache.org/jira/browse/COCOON3-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pacawat k updated COCOON3-139: -- Summary: DELETE - tkkk (was: tkkk) > DELETE - tkkk > - > > Key: COCOON3-139 > URL: https://issues.apache.org/jira/browse/COCOON3-139 > Project: Cocoon 3 > Issue Type: Bug > Components: cocoon-cli, cocoon-controller, cocoon-rest >Reporter: pacawat k >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (COCOON3-139) tkkk
[ https://issues.apache.org/jira/browse/COCOON3-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pacawat k closed COCOON3-139. - Resolution: Invalid > tkkk > > > Key: COCOON3-139 > URL: https://issues.apache.org/jira/browse/COCOON3-139 > Project: Cocoon 3 > Issue Type: Bug > Components: cocoon-cli, cocoon-controller, cocoon-rest >Reporter: pacawat k >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (COCOON3-139) tkkk
pacawat k created COCOON3-139: - Summary: tkkk Key: COCOON3-139 URL: https://issues.apache.org/jira/browse/COCOON3-139 Project: Cocoon 3 Issue Type: Bug Components: cocoon-cli, cocoon-controller, cocoon-rest Reporter: pacawat k -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2360) Inconsistent method names
[
https://issues.apache.org/jira/browse/COCOON-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16447145#comment-16447145
]
ASF GitHub Bot commented on COCOON-2360:
GitHub user BruceKuiLiu opened a pull request:
https://github.com/apache/cocoon/pull/5
COCOON-2360: Change the inconsistent method name.
The method is named as "select".
"select" is prone to mean that something will be selected.
But this method actually checks whether the expression is contained or not.
So, rename it as "contains" should be more clearly and intuitively.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BruceKuiLiu/cocoon trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cocoon/pull/5.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5
commit c6889d0c6298076a315fc6dab4700ebb79248662
Author: Kui LIU <brucekuiliu@...>
Date: 2018-04-22T08:27:39Z
COCOON-2360: Change the inconsistent method name.
The method is named as "select".
"select" is prone to mean that something will be selected.
But this method actually checks whether the expression is contained or not.
So, rename it as "contains" should be more clearly and intuitively.
> Inconsistent method names
> -
>
> Key: COCOON-2360
> URL: https://issues.apache.org/jira/browse/COCOON-2360
> Project: Cocoon
> Issue Type: Improvement
> Components: Blocks: (Undefined)
>Reporter: KuiLIU
>Priority: Major
>
> The following method is named as "select".
> "select" is prone to mean that something will be selected.
> But this method actually checks whether the expression is contained or not.
> So, rename it as "contains" should be more clearly and intuitively.
> public boolean select( String expression ) {
> return this.set.contains( expression );
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (COCOON-2360) Inconsistent method names
KuiLIU created COCOON-2360:
--
Summary: Inconsistent method names
Key: COCOON-2360
URL: https://issues.apache.org/jira/browse/COCOON-2360
Project: Cocoon
Issue Type: Improvement
Components: Blocks: (Undefined)
Reporter: KuiLIU
The following method is named as "select".
"select" is prone to mean that something will be selected.
But this method actually checks whether the expression is contained or not.
So, rename it as "contains" should be more clearly and intuitively.
public boolean select( String expression ) {
return this.set.contains( expression );
}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[ https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò closed COCOON-2347. -- Resolution: Fixed This issue is now fixed, temporary branch BRANCH_2_2_COCOON-2347 was merged back to trunk. > Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version > - > > Key: COCOON-2347 > URL: https://issues.apache.org/jira/browse/COCOON-2347 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Components: Sitemap, - Expression > language, - Servlet service framework >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Assignee: Javier Puerto >Priority: Major > Fix For: 2.2.1 > > Attachments: AbstractElementParser.java.patch, > AbstractTestCase.java.patch, AbstractTestCase.java.patch, > BeanMapElementParser.java.patch, BridgeElementParser.java.patch, > BridgeElementParser.java.patch, CallScope.java.patch, > MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, > ObjectModel.java.patch, ObjectModelImpl.java.patch, > PipelineComponentInfoInitializerDecorator.java.patch, > PipelineComponentScope.java.patch, ServletDecorator.java.patch, > ServletScope.java.patch, SitemapElementParser.java.patch, > SourceResource.java.patch, UnmodifiableMultiMap.java.patch, > WildcardBeanMap.java.patch, formatDate-output.xml.patch, > jxAttribute-output.xml.patch, jxElement-output.xml.patch > > > The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible > with latest Spring Framework version. > According to research and feedback in mailinglist following projects (maven > modules) are affected: > - cocoon-spring-configurator > - cocoon-servlet-service-impl > - cocoon-sitemap-impl > - cocoon-pipeline-impl > - cocoon-expression-api > - cocoon-expression-language-impl > .. > Let's discuss problems, and append patches here and someone of the committers > can then apply them to SVN. > Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6 > SVN branches: > * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347 > Jenkins job: https://builds.apache.org/job/Cocoon 2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[ https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425679#comment-16425679 ] Hudson commented on COCOON-2347: SUCCESS: Integrated in Jenkins build Cocoon 2.2 #2435 (See [https://builds.apache.org/job/Cocoon%202.2/2435/]) [COCOON-2347] Fixes made by Gabriel Gruber @ggruber4711 - This fixes #4 (ilgrosso: [http://svn.apache.org/viewvc/?view=rev=1828352]) * (edit) BRANCH_2_2_COCOON-2347/blocks/cocoon-portal/cocoon-portal-impl/src/main/java/org/apache/cocoon/portal/spring/AspectsBeanDefinitionParser.java * (edit) BRANCH_2_2_COCOON-2347/blocks/cocoon-template/cocoon-template-impl/src/test/resources/org/apache/cocoon/template/jxtg/formatDate-output.xml * (edit) BRANCH_2_2_COCOON-2347/blocks/cocoon-template/cocoon-template-impl/src/test/resources/org/apache/cocoon/template/jxtg/formatDate.xml * (edit) BRANCH_2_2_COCOON-2347/blocks/cocoon-template/cocoon-template-impl/src/test/resources/org/apache/cocoon/template/jxtg/jxAttribute-output.xml * (edit) BRANCH_2_2_COCOON-2347/blocks/cocoon-template/cocoon-template-impl/src/test/resources/org/apache/cocoon/template/jxtg/jxAttribute.xml * (edit) BRANCH_2_2_COCOON-2347/blocks/cocoon-template/cocoon-template-impl/src/test/resources/org/apache/cocoon/template/jxtg/jxElement-output.xml * (edit) BRANCH_2_2_COCOON-2347/blocks/cocoon-template/cocoon-template-impl/src/test/resources/org/apache/cocoon/template/jxtg/jxElement.xml * (edit) BRANCH_2_2_COCOON-2347/core/cocoon-expression-language/cocoon-expression-language-api/src/main/java/org/apache/cocoon/el/objectmodel/ObjectModel.java * (add) BRANCH_2_2_COCOON-2347/core/cocoon-expression-language/cocoon-expression-language-api/src/main/java/org/apache/cocoon/el/util * (add) BRANCH_2_2_COCOON-2347/core/cocoon-expression-language/cocoon-expression-language-api/src/main/java/org/apache/cocoon/el/util/MultiMap.java * (add) BRANCH_2_2_COCOON-2347/core/cocoon-expression-language/cocoon-expression-language-api/src/main/java/org/apache/cocoon/el/util/MultiValueMap.java * (edit) BRANCH_2_2_COCOON-2347/core/cocoon-expression-language/cocoon-expression-language-impl/src/main/java/org/apache/cocoon/el/impl/objectmodel/ObjectModelImpl.java * (edit) BRANCH_2_2_COCOON-2347/core/cocoon-expression-language/cocoon-expression-language-impl/src/main/java/org/apache/cocoon/el/impl/objectmodel/UnmodifiableMultiMap.java * (edit) BRANCH_2_2_COCOON-2347/core/cocoon-sitemap/cocoon-sitemap-impl/src/main/java/org/apache/cocoon/core/container/spring/avalon/AvalonBeanPostProcessor.java * (edit) BRANCH_2_2_COCOON-2347/core/cocoon-sitemap/cocoon-sitemap-impl/src/main/java/org/apache/cocoon/core/container/spring/avalon/BridgeElementParser.java * (edit) BRANCH_2_2_COCOON-2347/core/cocoon-sitemap/cocoon-sitemap-impl/src/test/java/org/apache/cocoon/AbstractTestCase.java * (edit) BRANCH_2_2_COCOON-2347/parent/pom.xml > Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version > - > > Key: COCOON-2347 > URL: https://issues.apache.org/jira/browse/COCOON-2347 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Components: Sitemap, - Expression > language, - Servlet service framework >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Assignee: Javier Puerto >Priority: Major > Fix For: 2.2.1 > > Attachments: AbstractElementParser.java.patch, > AbstractTestCase.java.patch, AbstractTestCase.java.patch, > BeanMapElementParser.java.patch, BridgeElementParser.java.patch, > BridgeElementParser.java.patch, CallScope.java.patch, > MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, > ObjectModel.java.patch, ObjectModelImpl.java.patch, > PipelineComponentInfoInitializerDecorator.java.patch, > PipelineComponentScope.java.patch, ServletDecorator.java.patch, > ServletScope.java.patch, SitemapElementParser.java.patch, > SourceResource.java.patch, UnmodifiableMultiMap.java.patch, > WildcardBeanMap.java.patch, formatDate-output.xml.patch, > jxAttribute-output.xml.patch, jxElement-output.xml.patch > > > The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible > with latest Spring Framework version. > According to research and feedback in mailinglist following projects (maven > modules) are affected: > - cocoon-spring-configurator > - cocoon-servlet-service-impl > - cocoon-sitemap-impl > - cocoon-pipeline-impl > - cocoon-expression-api > - cocoon-expression-language-impl > .. > Let's discuss problems, and append patches here and someone of the committers > can then apply them to SVN. > Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6
[jira] [Commented] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[ https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425668#comment-16425668 ] Gabriel Gruber commented on COCOON-2347: Thanks ilgrosso for taking care of the patches and guiding me through the process. I think the work is done related with this ticket. Created a follower-bug for cocoon-captcha: COCOON-2359 > Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version > - > > Key: COCOON-2347 > URL: https://issues.apache.org/jira/browse/COCOON-2347 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Components: Sitemap, - Expression > language, - Servlet service framework >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Assignee: Javier Puerto >Priority: Major > Fix For: 2.2.1 > > Attachments: AbstractElementParser.java.patch, > AbstractTestCase.java.patch, AbstractTestCase.java.patch, > BeanMapElementParser.java.patch, BridgeElementParser.java.patch, > BridgeElementParser.java.patch, CallScope.java.patch, > MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, > ObjectModel.java.patch, ObjectModelImpl.java.patch, > PipelineComponentInfoInitializerDecorator.java.patch, > PipelineComponentScope.java.patch, ServletDecorator.java.patch, > ServletScope.java.patch, SitemapElementParser.java.patch, > SourceResource.java.patch, UnmodifiableMultiMap.java.patch, > WildcardBeanMap.java.patch, formatDate-output.xml.patch, > jxAttribute-output.xml.patch, jxElement-output.xml.patch > > > The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible > with latest Spring Framework version. > According to research and feedback in mailinglist following projects (maven > modules) are affected: > - cocoon-spring-configurator > - cocoon-servlet-service-impl > - cocoon-sitemap-impl > - cocoon-pipeline-impl > - cocoon-expression-api > - cocoon-expression-language-impl > .. > Let's discuss problems, and append patches here and someone of the committers > can then apply them to SVN. > Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6 > SVN branches: > * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347 > Jenkins job: https://builds.apache.org/job/Cocoon 2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[ https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425638#comment-16425638 ] ASF GitHub Bot commented on COCOON-2347: Github user ggruber4711 closed the pull request at: https://github.com/apache/cocoon/pull/4 > Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version > - > > Key: COCOON-2347 > URL: https://issues.apache.org/jira/browse/COCOON-2347 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Components: Sitemap, - Expression > language, - Servlet service framework >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Assignee: Javier Puerto >Priority: Major > Fix For: 2.2.1 > > Attachments: AbstractElementParser.java.patch, > AbstractTestCase.java.patch, AbstractTestCase.java.patch, > BeanMapElementParser.java.patch, BridgeElementParser.java.patch, > BridgeElementParser.java.patch, CallScope.java.patch, > MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, > ObjectModel.java.patch, ObjectModelImpl.java.patch, > PipelineComponentInfoInitializerDecorator.java.patch, > PipelineComponentScope.java.patch, ServletDecorator.java.patch, > ServletScope.java.patch, SitemapElementParser.java.patch, > SourceResource.java.patch, UnmodifiableMultiMap.java.patch, > WildcardBeanMap.java.patch, formatDate-output.xml.patch, > jxAttribute-output.xml.patch, jxElement-output.xml.patch > > > The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible > with latest Spring Framework version. > According to research and feedback in mailinglist following projects (maven > modules) are affected: > - cocoon-spring-configurator > - cocoon-servlet-service-impl > - cocoon-sitemap-impl > - cocoon-pipeline-impl > - cocoon-expression-api > - cocoon-expression-language-impl > .. > Let's discuss problems, and append patches here and someone of the committers > can then apply them to SVN. > Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6 > SVN branches: > * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347 > Jenkins job: https://builds.apache.org/job/Cocoon 2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[
https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425634#comment-16425634
]
Francesco Chicchiriccò commented on COCOON-2347:
Thanks [~gabriel.gru...@workflow.at] I have committed your changes with
https://svn.apache.org/viewvc?view=revision=1828352
Question: is the work related to this issue to be considered complete? Shall we
close this issue and merge the branch {{BRANCH_2_2_COCOON-2347}} back to
{{trunk}}?
> Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
> -
>
> Key: COCOON-2347
> URL: https://issues.apache.org/jira/browse/COCOON-2347
> Project: Cocoon
> Issue Type: Improvement
> Components: * Cocoon Core, - Components: Sitemap, - Expression
> language, - Servlet service framework
>Affects Versions: 2.2
>Reporter: Gabriel Gruber
>Assignee: Javier Puerto
>Priority: Major
> Fix For: 2.2.1
>
> Attachments: AbstractElementParser.java.patch,
> AbstractTestCase.java.patch, AbstractTestCase.java.patch,
> BeanMapElementParser.java.patch, BridgeElementParser.java.patch,
> BridgeElementParser.java.patch, CallScope.java.patch,
> MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java,
> ObjectModel.java.patch, ObjectModelImpl.java.patch,
> PipelineComponentInfoInitializerDecorator.java.patch,
> PipelineComponentScope.java.patch, ServletDecorator.java.patch,
> ServletScope.java.patch, SitemapElementParser.java.patch,
> SourceResource.java.patch, UnmodifiableMultiMap.java.patch,
> WildcardBeanMap.java.patch, formatDate-output.xml.patch,
> jxAttribute-output.xml.patch, jxElement-output.xml.patch
>
>
> The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible
> with latest Spring Framework version.
> According to research and feedback in mailinglist following projects (maven
> modules) are affected:
> - cocoon-spring-configurator
> - cocoon-servlet-service-impl
> - cocoon-sitemap-impl
> - cocoon-pipeline-impl
> - cocoon-expression-api
> - cocoon-expression-language-impl
> ..
> Let's discuss problems, and append patches here and someone of the committers
> can then apply them to SVN.
> Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6
> SVN branches:
> * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347
> *
> https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347
> *
> https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347
> Jenkins job: https://builds.apache.org/job/Cocoon 2.2
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[ https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated COCOON-2347: --- Fix Version/s: 2.2.1 > Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version > - > > Key: COCOON-2347 > URL: https://issues.apache.org/jira/browse/COCOON-2347 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Components: Sitemap, - Expression > language, - Servlet service framework >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Assignee: Javier Puerto >Priority: Major > Fix For: 2.2.1 > > Attachments: AbstractElementParser.java.patch, > AbstractTestCase.java.patch, AbstractTestCase.java.patch, > BeanMapElementParser.java.patch, BridgeElementParser.java.patch, > BridgeElementParser.java.patch, CallScope.java.patch, > MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, > ObjectModel.java.patch, ObjectModelImpl.java.patch, > PipelineComponentInfoInitializerDecorator.java.patch, > PipelineComponentScope.java.patch, ServletDecorator.java.patch, > ServletScope.java.patch, SitemapElementParser.java.patch, > SourceResource.java.patch, UnmodifiableMultiMap.java.patch, > WildcardBeanMap.java.patch, formatDate-output.xml.patch, > jxAttribute-output.xml.patch, jxElement-output.xml.patch > > > The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible > with latest Spring Framework version. > According to research and feedback in mailinglist following projects (maven > modules) are affected: > - cocoon-spring-configurator > - cocoon-servlet-service-impl > - cocoon-sitemap-impl > - cocoon-pipeline-impl > - cocoon-expression-api > - cocoon-expression-language-impl > .. > Let's discuss problems, and append patches here and someone of the committers > can then apply them to SVN. > Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6 > SVN branches: > * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347 > Jenkins job: https://builds.apache.org/job/Cocoon 2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COCOON-2359) Fix incompatibility of cocoon-captcha with JDK 1.7/1.8
[ https://issues.apache.org/jira/browse/COCOON-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated COCOON-2359: --- Affects Version/s: 2.2 > Fix incompatibility of cocoon-captcha with JDK 1.7/1.8 > -- > > Key: COCOON-2359 > URL: https://issues.apache.org/jira/browse/COCOON-2359 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Captcha >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Priority: Major > Fix For: 2.2.1 > > > Goal is to remove the direct usage of > - JPEGImageEncoder > - JPEGEncodeParam > inside CaptchaReader.java > And replace them with the newer 1.6 API of ImageIO > https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COCOON-2359) Fix incompatibility of cocoon-captcha with JDK 1.7/1.8
[ https://issues.apache.org/jira/browse/COCOON-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated COCOON-2359: --- Fix Version/s: 2.2.1 > Fix incompatibility of cocoon-captcha with JDK 1.7/1.8 > -- > > Key: COCOON-2359 > URL: https://issues.apache.org/jira/browse/COCOON-2359 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Captcha >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Priority: Major > Fix For: 2.2.1 > > > Goal is to remove the direct usage of > - JPEGImageEncoder > - JPEGEncodeParam > inside CaptchaReader.java > And replace them with the newer 1.6 API of ImageIO > https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COCOON-2359) Fix incompatibility of cocoon-captcha with JDK 1.7/1.8
[ https://issues.apache.org/jira/browse/COCOON-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Gruber updated COCOON-2359: --- Description: Goal is to remove the direct usage of - JPEGImageEncoder - JPEGEncodeParam inside CaptchaReader.java And replace them with the newer 1.6 API of ImageIO https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ was: Goal is to remove the direct usage of - JPEGImageEncoder - JPEGEncodeParam And replace them with the newer 1.6 API of ImageIO https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ > Fix incompatibility of cocoon-captcha with JDK 1.7/1.8 > -- > > Key: COCOON-2359 > URL: https://issues.apache.org/jira/browse/COCOON-2359 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Captcha >Reporter: Gabriel Gruber >Priority: Major > > Goal is to remove the direct usage of > - JPEGImageEncoder > - JPEGEncodeParam > inside CaptchaReader.java > And replace them with the newer 1.6 API of ImageIO > https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (COCOON-2359) Fix incompatibility of cocoon-captcha with JDK 1.7/1.8
Gabriel Gruber created COCOON-2359: -- Summary: Fix incompatibility of cocoon-captcha with JDK 1.7/1.8 Key: COCOON-2359 URL: https://issues.apache.org/jira/browse/COCOON-2359 Project: Cocoon Issue Type: Bug Components: Blocks: Captcha Reporter: Gabriel Gruber Goal is to remove th direct usage of - JPEGImageEncoder - JPEGEncodeParam And replace them with the newer 1.6 API of ImageIO https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COCOON-2359) Fix incompatibility of cocoon-captcha with JDK 1.7/1.8
[ https://issues.apache.org/jira/browse/COCOON-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Gruber updated COCOON-2359: --- Description: Goal is to remove the direct usage of - JPEGImageEncoder - JPEGEncodeParam And replace them with the newer 1.6 API of ImageIO https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ was: Goal is to remove th direct usage of - JPEGImageEncoder - JPEGEncodeParam And replace them with the newer 1.6 API of ImageIO https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ > Fix incompatibility of cocoon-captcha with JDK 1.7/1.8 > -- > > Key: COCOON-2359 > URL: https://issues.apache.org/jira/browse/COCOON-2359 > Project: Cocoon > Issue Type: Bug > Components: Blocks: Captcha >Reporter: Gabriel Gruber >Priority: Major > > Goal is to remove the direct usage of > - JPEGImageEncoder > - JPEGEncodeParam > And replace them with the newer 1.6 API of ImageIO > https://blog.idrsolutions.com/2012/05/replacing-the-deprecated-java-jpeg-classes-for-java-7/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[ https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425293#comment-16425293 ] ASF GitHub Bot commented on COCOON-2347: GitHub user ggruber4711 opened a pull request: https://github.com/apache/cocoon/pull/4 COCOON-2347 Needed changes to build against spring 4.x JDK 1.8 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ggruber4711/cocoon BRANCH_2_2_COCOON-2347 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cocoon/pull/4.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4 commit e7dcaa5987ceb7739aee6737a8468909f79429a4 Author: Gabriel Gruber <gabriel.gruber@...> Date: 2018-04-04T10:13:23Z COCOON-2347 Needed changes to build against spring 4.x JDK 1.8 > Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version > - > > Key: COCOON-2347 > URL: https://issues.apache.org/jira/browse/COCOON-2347 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Components: Sitemap, - Expression > language, - Servlet service framework >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Assignee: Javier Puerto >Priority: Major > Attachments: AbstractElementParser.java.patch, > AbstractTestCase.java.patch, AbstractTestCase.java.patch, > BeanMapElementParser.java.patch, BridgeElementParser.java.patch, > BridgeElementParser.java.patch, CallScope.java.patch, > MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, > ObjectModel.java.patch, ObjectModelImpl.java.patch, > PipelineComponentInfoInitializerDecorator.java.patch, > PipelineComponentScope.java.patch, ServletDecorator.java.patch, > ServletScope.java.patch, SitemapElementParser.java.patch, > SourceResource.java.patch, UnmodifiableMultiMap.java.patch, > WildcardBeanMap.java.patch, formatDate-output.xml.patch, > jxAttribute-output.xml.patch, jxElement-output.xml.patch > > > The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible > with latest Spring Framework version. > According to research and feedback in mailinglist following projects (maven > modules) are affected: > - cocoon-spring-configurator > - cocoon-servlet-service-impl > - cocoon-sitemap-impl > - cocoon-pipeline-impl > - cocoon-expression-api > - cocoon-expression-language-impl > .. > Let's discuss problems, and append patches here and someone of the committers > can then apply them to SVN. > Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6 > SVN branches: > * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347 > Jenkins job: https://builds.apache.org/job/Cocoon 2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[ https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Gruber updated COCOON-2347: --- Attachment: jxAttribute-output.xml.patch jxElement-output.xml.patch formatDate-output.xml.patch > Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version > - > > Key: COCOON-2347 > URL: https://issues.apache.org/jira/browse/COCOON-2347 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Components: Sitemap, - Expression > language, - Servlet service framework >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Assignee: Javier Puerto >Priority: Major > Attachments: AbstractElementParser.java.patch, > AbstractTestCase.java.patch, AbstractTestCase.java.patch, > BeanMapElementParser.java.patch, BridgeElementParser.java.patch, > BridgeElementParser.java.patch, CallScope.java.patch, > MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, > ObjectModel.java.patch, ObjectModelImpl.java.patch, > PipelineComponentInfoInitializerDecorator.java.patch, > PipelineComponentScope.java.patch, ServletDecorator.java.patch, > ServletScope.java.patch, SitemapElementParser.java.patch, > SourceResource.java.patch, UnmodifiableMultiMap.java.patch, > WildcardBeanMap.java.patch, formatDate-output.xml.patch, > jxAttribute-output.xml.patch, jxElement-output.xml.patch > > > The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible > with latest Spring Framework version. > According to research and feedback in mailinglist following projects (maven > modules) are affected: > - cocoon-spring-configurator > - cocoon-servlet-service-impl > - cocoon-sitemap-impl > - cocoon-pipeline-impl > - cocoon-expression-api > - cocoon-expression-language-impl > .. > Let's discuss problems, and append patches here and someone of the committers > can then apply them to SVN. > Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6 > SVN branches: > * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347 > Jenkins job: https://builds.apache.org/job/Cocoon 2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[ https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425216#comment-16425216 ] Gabriel Gruber commented on COCOON-2347: There is a last fail in JXTemplateGeneratorTestCase which is related to a change of the translation of the 'january' in polish within the JDK. With JDK 7 this testcase succeeds, as JDK 1.7 returns 'styczeń' in contrast to JDK 1.8 which returns 'stycznia' In order to make those testcases run again, you would need to apply these patches to the XMLs containing the expected results inside cocoon-template-impl (src/test/resources): - formatDate-output.xml - jxAttribute-output.xml - jxElement-output.xml > Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version > - > > Key: COCOON-2347 > URL: https://issues.apache.org/jira/browse/COCOON-2347 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Components: Sitemap, - Expression > language, - Servlet service framework >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Assignee: Javier Puerto >Priority: Major > Attachments: AbstractElementParser.java.patch, > AbstractTestCase.java.patch, AbstractTestCase.java.patch, > BeanMapElementParser.java.patch, BridgeElementParser.java.patch, > BridgeElementParser.java.patch, CallScope.java.patch, > MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, > ObjectModel.java.patch, ObjectModelImpl.java.patch, > PipelineComponentInfoInitializerDecorator.java.patch, > PipelineComponentScope.java.patch, ServletDecorator.java.patch, > ServletScope.java.patch, SitemapElementParser.java.patch, > SourceResource.java.patch, UnmodifiableMultiMap.java.patch, > WildcardBeanMap.java.patch > > > The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible > with latest Spring Framework version. > According to research and feedback in mailinglist following projects (maven > modules) are affected: > - cocoon-spring-configurator > - cocoon-servlet-service-impl > - cocoon-sitemap-impl > - cocoon-pipeline-impl > - cocoon-expression-api > - cocoon-expression-language-impl > .. > Let's discuss problems, and append patches here and someone of the committers > can then apply them to SVN. > Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6 > SVN branches: > * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347 > Jenkins job: https://builds.apache.org/job/Cocoon 2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[ https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425213#comment-16425213 ] Francesco Chicchiriccò commented on COCOON-2347: Thanks for your enduring interest, [~gabriel.gru...@workflow.at]! For the sake of manageability, would it be possible to grab all the patches attached here as a single PR on github, made against https://github.com/apache/cocoon/tree/BRANCH_2_2_COCOON-2347 ? > Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version > - > > Key: COCOON-2347 > URL: https://issues.apache.org/jira/browse/COCOON-2347 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Components: Sitemap, - Expression > language, - Servlet service framework >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Assignee: Javier Puerto >Priority: Major > Attachments: AbstractElementParser.java.patch, > AbstractTestCase.java.patch, AbstractTestCase.java.patch, > BeanMapElementParser.java.patch, BridgeElementParser.java.patch, > BridgeElementParser.java.patch, CallScope.java.patch, > MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, > ObjectModel.java.patch, ObjectModelImpl.java.patch, > PipelineComponentInfoInitializerDecorator.java.patch, > PipelineComponentScope.java.patch, ServletDecorator.java.patch, > ServletScope.java.patch, SitemapElementParser.java.patch, > SourceResource.java.patch, UnmodifiableMultiMap.java.patch, > WildcardBeanMap.java.patch > > > The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible > with latest Spring Framework version. > According to research and feedback in mailinglist following projects (maven > modules) are affected: > - cocoon-spring-configurator > - cocoon-servlet-service-impl > - cocoon-sitemap-impl > - cocoon-pipeline-impl > - cocoon-expression-api > - cocoon-expression-language-impl > .. > Let's discuss problems, and append patches here and someone of the committers > can then apply them to SVN. > Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6 > SVN branches: > * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347 > Jenkins job: https://builds.apache.org/job/Cocoon 2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[ https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425204#comment-16425204 ] Gabriel Gruber commented on COCOON-2347: I have added a path for AbstractTestCase which fixes the test-case fails in cocoon-core. The problem was that Spring4 needed the applicationContext to be refreshed. If that was not done, the loading of the XML resource bundles would fail with this exception: java.lang.IllegalStateException: org.apache.cocoon.MockWebApplicationContext@7d898981 has not been refreshed yet > Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version > - > > Key: COCOON-2347 > URL: https://issues.apache.org/jira/browse/COCOON-2347 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Components: Sitemap, - Expression > language, - Servlet service framework >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Assignee: Javier Puerto >Priority: Major > Attachments: AbstractElementParser.java.patch, > AbstractTestCase.java.patch, AbstractTestCase.java.patch, > BeanMapElementParser.java.patch, BridgeElementParser.java.patch, > BridgeElementParser.java.patch, CallScope.java.patch, > MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, > ObjectModel.java.patch, ObjectModelImpl.java.patch, > PipelineComponentInfoInitializerDecorator.java.patch, > PipelineComponentScope.java.patch, ServletDecorator.java.patch, > ServletScope.java.patch, SitemapElementParser.java.patch, > SourceResource.java.patch, UnmodifiableMultiMap.java.patch, > WildcardBeanMap.java.patch > > > The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible > with latest Spring Framework version. > According to research and feedback in mailinglist following projects (maven > modules) are affected: > - cocoon-spring-configurator > - cocoon-servlet-service-impl > - cocoon-sitemap-impl > - cocoon-pipeline-impl > - cocoon-expression-api > - cocoon-expression-language-impl > .. > Let's discuss problems, and append patches here and someone of the committers > can then apply them to SVN. > Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6 > SVN branches: > * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347 > Jenkins job: https://builds.apache.org/job/Cocoon 2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
[ https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Gruber updated COCOON-2347: --- Attachment: AbstractTestCase.java.patch > Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version > - > > Key: COCOON-2347 > URL: https://issues.apache.org/jira/browse/COCOON-2347 > Project: Cocoon > Issue Type: Improvement > Components: * Cocoon Core, - Components: Sitemap, - Expression > language, - Servlet service framework >Affects Versions: 2.2 >Reporter: Gabriel Gruber >Assignee: Javier Puerto >Priority: Major > Attachments: AbstractElementParser.java.patch, > AbstractTestCase.java.patch, AbstractTestCase.java.patch, > BeanMapElementParser.java.patch, BridgeElementParser.java.patch, > BridgeElementParser.java.patch, CallScope.java.patch, > MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, > ObjectModel.java.patch, ObjectModelImpl.java.patch, > PipelineComponentInfoInitializerDecorator.java.patch, > PipelineComponentScope.java.patch, ServletDecorator.java.patch, > ServletScope.java.patch, SitemapElementParser.java.patch, > SourceResource.java.patch, UnmodifiableMultiMap.java.patch, > WildcardBeanMap.java.patch > > > The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible > with latest Spring Framework version. > According to research and feedback in mailinglist following projects (maven > modules) are affected: > - cocoon-spring-configurator > - cocoon-servlet-service-impl > - cocoon-sitemap-impl > - cocoon-pipeline-impl > - cocoon-expression-api > - cocoon-expression-language-impl > .. > Let's discuss problems, and append patches here and someone of the committers > can then apply them to SVN. > Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6 > SVN branches: > * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347 > * > https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347 > Jenkins job: https://builds.apache.org/job/Cocoon 2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (COCOON-2358) Inconsistent Content-Length header for HEAD requests
[ https://issues.apache.org/jira/browse/COCOON-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175304#comment-16175304 ] Hudson commented on COCOON-2358: SUCCESS: Integrated in Jenkins build Cocoon 2.1.X #120 (See [https://builds.apache.org/job/Cocoon%202.1.X/120/]) COCOON-2358 Inconsistent Content-Length header for HEAD requests (cdamioli: [http://svn.apache.org/viewvc/?view=rev=1809196]) * (edit) BRANCH_2_1_X/src/java/org/apache/cocoon/environment/http/HttpEnvironment.java > Inconsistent Content-Length header for HEAD requests > > > Key: COCOON-2358 > URL: https://issues.apache.org/jira/browse/COCOON-2358 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core >Reporter: Cédric Damioli >Assignee: Cédric Damioli > Fix For: 2.1.13 > > > After any request processing, Environment.commitResponse() is called which > has the side effect to compute the actual response body size and then set the > response content length. > While this is perfectly fine for GET requests, it's obviously useless for > eg.OPTIONS and even wrong for HEAD requests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (COCOON-2358) Inconsistent Content-Length header for HEAD requests
[ https://issues.apache.org/jira/browse/COCOON-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli closed COCOON-2358. -- Resolution: Fixed > Inconsistent Content-Length header for HEAD requests > > > Key: COCOON-2358 > URL: https://issues.apache.org/jira/browse/COCOON-2358 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core >Reporter: Cédric Damioli >Assignee: Cédric Damioli > > After any request processing, Environment.commitResponse() is called which > has the side effect to compute the actual response body size and then set the > response content length. > While this is perfectly fine for GET requests, it's obviously useless for > eg.OPTIONS and even wrong for HEAD requests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (COCOON-2358) Inconsistent Content-Length header for HEAD requests
[ https://issues.apache.org/jira/browse/COCOON-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cédric Damioli updated COCOON-2358: --- Fix Version/s: 2.1.13 > Inconsistent Content-Length header for HEAD requests > > > Key: COCOON-2358 > URL: https://issues.apache.org/jira/browse/COCOON-2358 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core >Reporter: Cédric Damioli >Assignee: Cédric Damioli > Fix For: 2.1.13 > > > After any request processing, Environment.commitResponse() is called which > has the side effect to compute the actual response body size and then set the > response content length. > While this is perfectly fine for GET requests, it's obviously useless for > eg.OPTIONS and even wrong for HEAD requests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (COCOON-2358) Inconsistent Content-Length header for HEAD requests
Cédric Damioli created COCOON-2358: -- Summary: Inconsistent Content-Length header for HEAD requests Key: COCOON-2358 URL: https://issues.apache.org/jira/browse/COCOON-2358 Project: Cocoon Issue Type: Bug Components: * Cocoon Core Reporter: Cédric Damioli Assignee: Cédric Damioli After any request processing, Environment.commitResponse() is called which has the side effect to compute the actual response body size and then set the response content length. While this is perfectly fine for GET requests, it's obviously useless for eg.OPTIONS and even wrong for HEAD requests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (COCOON-2357) Content-Range and Range headers
[ https://issues.apache.org/jira/browse/COCOON-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173610#comment-16173610 ] Hudson commented on COCOON-2357: SUCCESS: Integrated in Jenkins build Cocoon 2.1.X #119 (See [https://builds.apache.org/job/Cocoon%202.1.X/119/]) COCOON-2357 Content-Range and Range headers (cdamioli: [http://svn.apache.org/viewvc/?view=rev=1809062]) * (edit) BRANCH_2_1_X/src/java/org/apache/cocoon/reading/ResourceReader.java * (edit) BRANCH_2_1_X/src/java/org/apache/cocoon/util/ByteRange.java > Content-Range and Range headers > --- > > Key: COCOON-2357 > URL: https://issues.apache.org/jira/browse/COCOON-2357 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core >Reporter: Cédric Damioli >Assignee: Cédric Damioli > Fix For: 2.1.13 > > > I tried to use the ResourceReader in combination with Range/Content-Range > headers for video streaming. > It seems to me that the implementation does not respect the HTTP spec. > According to the spec, asking for a 100 bytes resource with header > Range "bytes=0-" > should respond > Content-Range "bytes 0-99/100" > where Cocoon currently responds > Content-Range "0-100/100" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
