You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Francois Armand (JIRA)" <de...@tapestry.apache.org> on 2008/07/24 14:37:32 UTC
[jira] Created: (TAPESTRY-2537) Utf8Filter should be contributed by
default in tapestry core
Utf8Filter should be contributed by default in tapestry core
------------------------------------------------------------
Key: TAPESTRY-2537
URL: https://issues.apache.org/jira/browse/TAPESTRY-2537
Project: Tapestry
Issue Type: Improvement
Reporter: Francois Armand
Fix For: 5.0
I think that today, UTF-8 is the default encoding for a worldwide used framework as Tapestry is, and so the default behaviour of Tapestry should be that it "just works" with this encoding (just look at the number of UTF-8 related question on the mailing list).
So, I think that the UTF-8 filter at http://wiki.apache.org/tapestry/Tapestry5Utf8Encoding should be contributed by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Issue Comment Edited: (TAPESTRY-2537) Utf8Filter should be
contributed by default in tapestry core
Posted by "Christophe Cordenier (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616470#action_12616470 ]
ccordenier edited comment on TAPESTRY-2537 at 7/24/08 5:55 AM:
-------------------------------------------------------------------------
Actually, I have also worked on the UTF-8 issue, and I have found that the "RequestEncodingInitializerImpl" is bypassed by the "ClientPersistentFieldStorage" service wich call the a "request.getParameter" in its constructor.
So that the "initializeRequestEncoding" of the "RequestEncodingInitializerImpl " has no effect because the request has already been parsed.
Is it not more suitable to call the "request.getParameter" on page load for the client persistent strategy.
was (Author: ccordenier):
Actually, I have also worked on the UTF-8 issue, and I have found that the "RequestEncodingInitializerImpl" is bypassed by the "ClientPersistentFieldStorage" service wich call the a "request.getParameter" in its constructor.
So that the "initializeRequestEncoding" of the "RequestEncodingInitializerImpl " has no effect because the request has already been parsed.
> Utf8Filter should be contributed by default in tapestry core
> ------------------------------------------------------------
>
> Key: TAPESTRY-2537
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2537
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Francois Armand
> Fix For: 5.0
>
>
> I think that today, UTF-8 is the default encoding for a worldwide used framework as Tapestry is, and so the default behaviour of Tapestry should be that it "just works" with this encoding (just look at the number of UTF-8 related question on the mailing list).
> So, I think that the UTF-8 filter at http://wiki.apache.org/tapestry/Tapestry5Utf8Encoding should be contributed by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-2537) Utf8Filter should be contributed by
default in tapestry core
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2537.
------------------------------------------
Resolution: Invalid
Assignee: Howard M. Lewis Ship
TAPESTRY-2543 effectively does this.
> Utf8Filter should be contributed by default in tapestry core
> ------------------------------------------------------------
>
> Key: TAPESTRY-2537
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2537
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Francois Armand
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0
>
>
> I think that today, UTF-8 is the default encoding for a worldwide used framework as Tapestry is, and so the default behaviour of Tapestry should be that it "just works" with this encoding (just look at the number of UTF-8 related question on the mailing list).
> So, I think that the UTF-8 filter at http://wiki.apache.org/tapestry/Tapestry5Utf8Encoding should be contributed by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-2537) Utf8Filter should be contributed
by default in tapestry core
Posted by "Christophe Cordenier (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616470#action_12616470 ]
Christophe Cordenier commented on TAPESTRY-2537:
------------------------------------------------
Actually, I have also worked on the UTF-8 issue, and I have found that the "RequestEncodingInitializerImpl" is bypassed by the "ClientPersistentFieldStorage" service wich call the a "request.getParameter" in its constructor.
So that the "initializeRequestEncoding" of the "RequestEncodingInitializerImpl " has no effect because the request has already been parsed.
> Utf8Filter should be contributed by default in tapestry core
> ------------------------------------------------------------
>
> Key: TAPESTRY-2537
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2537
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Francois Armand
> Fix For: 5.0
>
>
> I think that today, UTF-8 is the default encoding for a worldwide used framework as Tapestry is, and so the default behaviour of Tapestry should be that it "just works" with this encoding (just look at the number of UTF-8 related question on the mailing list).
> So, I think that the UTF-8 filter at http://wiki.apache.org/tapestry/Tapestry5Utf8Encoding should be contributed by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Issue Comment Edited: (TAPESTRY-2537) Utf8Filter should be
contributed by default in tapestry core
Posted by "Christophe Cordenier (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616470#action_12616470 ]
ccordenier edited comment on TAPESTRY-2537 at 7/24/08 5:58 AM:
-------------------------------------------------------------------------
Actually, I have also worked on the UTF-8 issue, and I have found that the "RequestEncodingInitializerImpl" is bypassed by the "ClientPersistentFieldStorage" service wich call the a "request.getParameter" in its constructor.
So that the "initializeRequestEncoding" of the "RequestEncodingInitializerImpl " has no effect because the request has already been parsed.
Is it not more suitable to call the "request.getParameter" on page load for the client persistent strategy ? In fact the page loading comes after the request analysis...
was (Author: ccordenier):
Actually, I have also worked on the UTF-8 issue, and I have found that the "RequestEncodingInitializerImpl" is bypassed by the "ClientPersistentFieldStorage" service wich call the a "request.getParameter" in its constructor.
So that the "initializeRequestEncoding" of the "RequestEncodingInitializerImpl " has no effect because the request has already been parsed.
Is it not more suitable to call the "request.getParameter" on page load for the client persistent strategy ?
> Utf8Filter should be contributed by default in tapestry core
> ------------------------------------------------------------
>
> Key: TAPESTRY-2537
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2537
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Francois Armand
> Fix For: 5.0
>
>
> I think that today, UTF-8 is the default encoding for a worldwide used framework as Tapestry is, and so the default behaviour of Tapestry should be that it "just works" with this encoding (just look at the number of UTF-8 related question on the mailing list).
> So, I think that the UTF-8 filter at http://wiki.apache.org/tapestry/Tapestry5Utf8Encoding should be contributed by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-2537) Utf8Filter should be contributed by
default in tapestry core
Posted by "Francois Armand (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francois Armand updated TAPESTRY-2537:
--------------------------------------
Component/s: tapestry-core
Affects Version/s: 5.0
bad component / revision
> Utf8Filter should be contributed by default in tapestry core
> ------------------------------------------------------------
>
> Key: TAPESTRY-2537
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2537
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Francois Armand
> Fix For: 5.0
>
>
> I think that today, UTF-8 is the default encoding for a worldwide used framework as Tapestry is, and so the default behaviour of Tapestry should be that it "just works" with this encoding (just look at the number of UTF-8 related question on the mailing list).
> So, I think that the UTF-8 filter at http://wiki.apache.org/tapestry/Tapestry5Utf8Encoding should be contributed by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Issue Comment Edited: (TAPESTRY-2537) Utf8Filter should be
contributed by default in tapestry core
Posted by "Christophe Cordenier (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616470#action_12616470 ]
ccordenier edited comment on TAPESTRY-2537 at 7/24/08 5:55 AM:
-------------------------------------------------------------------------
Actually, I have also worked on the UTF-8 issue, and I have found that the "RequestEncodingInitializerImpl" is bypassed by the "ClientPersistentFieldStorage" service wich call the a "request.getParameter" in its constructor.
So that the "initializeRequestEncoding" of the "RequestEncodingInitializerImpl " has no effect because the request has already been parsed.
Is it not more suitable to call the "request.getParameter" on page load for the client persistent strategy ?
was (Author: ccordenier):
Actually, I have also worked on the UTF-8 issue, and I have found that the "RequestEncodingInitializerImpl" is bypassed by the "ClientPersistentFieldStorage" service wich call the a "request.getParameter" in its constructor.
So that the "initializeRequestEncoding" of the "RequestEncodingInitializerImpl " has no effect because the request has already been parsed.
Is it not more suitable to call the "request.getParameter" on page load for the client persistent strategy.
> Utf8Filter should be contributed by default in tapestry core
> ------------------------------------------------------------
>
> Key: TAPESTRY-2537
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2537
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Francois Armand
> Fix For: 5.0
>
>
> I think that today, UTF-8 is the default encoding for a worldwide used framework as Tapestry is, and so the default behaviour of Tapestry should be that it "just works" with this encoding (just look at the number of UTF-8 related question on the mailing list).
> So, I think that the UTF-8 filter at http://wiki.apache.org/tapestry/Tapestry5Utf8Encoding should be contributed by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org