+1
On Mar 12, 2012, at 8:57 AM, David Canteros wrote:
> +1
> I have several problems with the integration of my Tapestry tools and other
> non-tapestry tools, all of this caused by tapestry URLEncoder. I solved
> this by overriding URLEncoder, but your proposal would be a more elegant
> solution
>
+1
I have several problems with the integration of my Tapestry tools and other
non-tapestry tools, all of this caused by tapestry URLEncoder. I solved
this by overriding URLEncoder, but your proposal would be a more elegant
solution
+1
possibly with 3 options? :
a) tomcat compatible default encoding
b) jetty compatible default encoding
c) tapestry encoding
On 21/06/2010 6:34 AM, Joel Halbert wrote:
Agreed, it would be good to have this as a configuration option.
On 20/06/10 19:20, Kai Weber wrote:
* Nicolas Bouillon:
T
Agreed, it would be good to have this as a configuration option.
On 20/06/10 19:20, Kai Weber wrote:
* Nicolas Bouillon:
The Tapestry URL encoding is not a problem for me in general, just for one
use case when i wanted to migrate a site to tapestry and keeping the same
URL (with accents, s
* Nicolas Bouillon :
> The Tapestry URL encoding is not a problem for me in general, just for one
> use case when i wanted to migrate a site to tapestry and keeping the same
> URL (with accents, spaces, dashes, underscores and so on).
It is a problem if you get called by other webapps. If they ca
Makes sense. I must admit I was curious as to why T5 uses custom
encoding, so thanks for the explanation.
I'll use Nicolas's solution to override this behaviour.
On 19/06/10 01:20, Howard Lewis Ship wrote:
Tapestry does its own encoding because Jetty and Tomcat differ on
whether you get the de
The Tapestry URL encoding is not a problem for me in general, just for one
use case when i wanted to migrate a site to tapestry and keeping the same
URL (with accents, spaces, dashes, underscores and so on).
On Fri, 18 Jun 2010 17:20:36 -0700, Howard Lewis Ship
wrote:
> Tapestry does its own enco
Tapestry does its own encoding because Jetty and Tomcat differ on
whether you get the decoded or raw strings. Creating another option,
that would work the same across servlet containers, seemed to make
sense at the time.
On Fri, Jun 18, 2010 at 8:50 AM, Nicolas Bouillon wrote:
> Hi,
>
> Here is
Hi,
Here is how i've overrided this behavior, to allow URL with "%20" or other
chars as incomming request. It quite a copy/paste tweaking of the original
UrlEncoderImpl from Tapestry 5.1.0.5.
public class AppModule {
.
public static void contributeServiceOverride(
MappedCo
You can override every service of Tapestry, you have three ways to achieve
this :
1. Decoration
http://tapestry.apache.org/tapestry5.1/tapestry-ioc/decorator.html
2. Advice
http://tapestry.apache.org/tapestry5.1/tapestry-ioc/advice.html
3. Complete override
http://tapestry.apache.org/tapestry
10 matches
Mail list logo
