On Fri, 10 Aug 2012 15:43:48 -0300, Howard Lewis Ship
wrote:
That looks like another bug to me; for anything that goes into a URL
(as path or query parameter) the code should be using a ValueEncoder.
By the way, sometimes I miss having separate encoders for fields and URLs.
What is good f
I created a new TypeCoercer and it works fine.
Thanks,
Greg
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/ActivationRequestParameter-question-tp5715201p5715233.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
On Fri, Aug 10, 2012 at 7:58 AM, Thiago H de Paula Figueiredo
wrote:
> On Fri, 10 Aug 2012 10:36:21 -0300, gricker wrote:
>
>> I tried creating my own ValueEncoder but it seems like the error is
>> occurring before my code is called.
>
>
> I guess because the annotation handler uses TypeCoercer,
On Fri, 10 Aug 2012 10:36:21 -0300, gricker wrote:
I tried creating my own ValueEncoder but it seems like the error is
occurring before my code is called.
I guess because the annotation handler uses TypeCoercer, not ValueEncoder
for that.
--
Thiago H. de Paula Figueiredo
I tried creating my own ValueEncoder but it seems like the error is
occurring before my code is called.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/ActivationRequestParameter-question-tp5715201p5715222.html
Sent from the Tapestry - User mailing list archive at Nabbl
Seems like a missing feature; Tapestry should have a built-in
ValueEncoder for the Date type, to encode a Date into a more
reasonable string, and decode it back when converting the parameter
back into a field value.
On Thu, Aug 9, 2012 at 11:46 AM, gricker wrote:
>
>
> In the java code I have :
