Contribute a new implementation of URLEncoder to the Alias service configuration and Tapestry will use the contributed one instead of the default URLEncoder service.
Alternately, you can decorate the URLEncoder service with an alternative implementation, or a filter depending on how much of the existing URLEncoder service implementation you want to keep. Could you provide some more context as to why URLEncoder is a problem? On Tue, Oct 28, 2008 at 11:39 AM, jthompson209 <[EMAIL PROTECTED]> wrote: > > Hello I am in need of either turning off this new service or overriding it > and having it do nothing, it is currently breaking some code that I have, > what would be the best way of doing that, also if overriding it is the > answer how would i go about doing it. > > thanks so much > -jeff > -- > View this message in context: > http://n2.nabble.com/new-URLEncoder-Service-tp1389907p1389907.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
