Re: [VOTE] Require Java 1.6 for Cocoon3
Am 19.09.2011 23:03, schrieb Nathaniel, Alfred: +1 = Yes, Cocoon3 shall require Java 1.6 -1 = No, Cocoon3 must remain usable with Java 1.5 (with justification for the veto) +1
Re: [VOTE] Require Java 1.6 for Cocoon3
On 19/09/2011 23:03, Nathaniel, Alfred wrote: Hi all, A few weeks ago we had a discussion [1] whether to increase for Cocoon3 the minimum Java version from 1.5 to 1.6. There were a number of advantages identified to be gained by using Java6, which I don't want to repeat here, The only downside is the exclusion of potential C3 users locked in to Java5. A survey on the user list [2] asking users to step forward if that really applied to anybody did not yield any response. Therefore I' call the vote on Code Modification [3]: +1 = Yes, Cocoon3 shall require Java 1.6 -1 = No, Cocoon3 must remain usable with Java 1.5 (with justification for the veto) +1 This change is targeted only at Cocoon3. Cocoon2.1 and Cocoon2.2 are not affected. Please cast your votes before Mon 3 Oct 06:00 UTC. Here is mine: +1 Cheers, Alfred. [1] http://www.mail-archive.com/dev@cocoon.apache.org/msg59791.html [2] http://www.mail-archive.com/users@cocoon.apache.org/msg46231.html [3] http://www.apache.org/foundation/voting.html The content of this e-mail is intended only for the confidential use of the person addressed. If you are not the intended recipient, please notify the sender and delete this e-mail immediately. Thank you. -- Francesco Chicchiriccò Apache Cocoon Committer and PMC Member http://people.apache.org/~ilgrosso/
Re: [VOTE] Require Java 1.6 for Cocoon3
On Mon, 2011-09-19 at 23:03 +0200, Nathaniel, Alfred wrote: ... +1 = Yes, Cocoon3 shall require Java 1.6 -1 = No, Cocoon3 must remain usable with Java 1.5 (with justification for the veto) + 1 salu2 -- Thorsten Scherler thorsten.at.apache.org codeBusters S.L. - web based systems consulting, training and solutions http://www.codebusters.es/
[jira] [Created] (COCOON-2315) Generator and CInclude transformer do not include the request headers of the caller.
Generator and CInclude transformer do not include the request headers of the
caller.
Key: COCOON-2315
URL: https://issues.apache.org/jira/browse/COCOON-2315
Project: Cocoon
Issue Type: Bug
Components: * Cocoon Core
Affects Versions: 2.1.9, 2.1.12-dev (Current SVN)
Reporter: Alec Bickerton
When using the file generator or any sub class. The request headers are not
propagated to the source.
e.g.
{code}
map:match pattern=deviceInfo
map:generate src=http://deviceMetaService.example.com/lookup.jsp/
map:serialize/
/map:match
{code}
The request received by the http://deviceMetaService.example.com/lookup.jsp
will not contain the user-agent header of the original request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (COCOON-2315) Generator and CInclude transformer do not include the request headers of the caller.
[
https://issues.apache.org/jira/browse/COCOON-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alfred Nathaniel closed COCOON-2315.
Resolution: Not A Problem
This is not a bug but a misconception what the file generator does. As the
name implies the file generator is most often used to read files, parse them as
XML documents and send the SAX events down the pipeline. The src attribute
also allows to use other source protocols as drop-in replacement for files.
In the case of http: the file generator creates a GET request to the given
webserver. Parameters or headers from the original request invoking the
current pipeline are not forwarded.
If you need to formulate customized HTTP requests you should look at
http://cocoon.apache.org/2.1/userdocs/wsproxy-generator.html.
Generator and CInclude transformer do not include the request headers of the
caller.
Key: COCOON-2315
URL: https://issues.apache.org/jira/browse/COCOON-2315
Project: Cocoon
Issue Type: Bug
Components: * Cocoon Core
Affects Versions: 2.1.9, 2.1.12-dev (Current SVN)
Reporter: Alec Bickerton
When using the file generator or any sub class. The request headers are not
propagated to the source.
e.g.
{code}
map:match pattern=deviceInfo
map:generate src=http://deviceMetaService.example.com/lookup.jsp/
map:serialize/
/map:match
{code}
The request received by the http://deviceMetaService.example.com/lookup.jsp
will not contain the user-agent header of the original request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Require Java 1.6 for Cocoon3
On Mon, 2011-09-19 at 23:03 +0200, Nathaniel, Alfred wrote: +1 = Yes, Cocoon3 shall require Java 1.6 -1 = No, Cocoon3 must remain usable with Java 1.5 (with justification for the veto) +1 Regards, David Legg
Re: [VOTE] Require Java 1.6 for Cocoon3
Nathaniel, Alfred wrote: Please cast your votes before Mon 3 Oct 06:00 UTC. +1 -David
Re: [VOTE] Require Java 1.6 for Cocoon3
On 09/19/2011 11:03 PM, Nathaniel, Alfred wrote: Hi all, A few weeks ago we had a discussion [1] whether to increase for Cocoon3 the minimum Java version from 1.5 to 1.6. There were a number of advantages identified to be gained by using Java6, which I don’t want to repeat here, The only downside is the exclusion of potential C3 users locked in to Java5. A survey on the user list [2] asking users to step forward if that really applied to anybody did not yield any response. Therefore I’ call the vote on Code Modification [3]: +1 = Yes, Cocoon3 shall require Java 1.6 -1 = No, Cocoon3 must remain usable with Java 1.5 (with justification for the veto) This change is targeted only at Cocoon3. Cocoon2.1 and Cocoon2.2 are not affected. Please cast your votes before Mon 3 Oct 06:00 UTC. +1 -- Reinhard Pötz Founder Managing Director, Indoqa and Deepsearch http://www.indoqa.com/people/reinhard-poetz.html Member of the Apache Software Foundation Apache Cocoon Committer, PMC member reinh...@apache.org Furthermore, I think Oracle has to honor the JSPA agreement. http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap
