Nice. Why don't you post the code on a new page here? ...
http://wiki.apache.org/tapestry/Tapestry5HowTos
Cheers,
Nick.
Ognen Ivanovski wrote:
>
>
> On 2007-08-16, at 05:10, Nick Westgate wrote:
>
>> Indeed. Hence the JIRA.
>>
>> Howard has mentioned the possibility of merging the two type
On 2007-08-16, at 05:10, Nick Westgate wrote:
Indeed. Hence the JIRA.
Howard has mentioned the possibility of merging the two type
coercion systems.
That Would be great!
What I currently do to seamlessly use Entities across the framework
(activation / deactivation, parameters, RadioGrou
Indeed. Hence the JIRA.
Howard has mentioned the possibility of merging the two type coercion systems.
Cheers,
Nick.
Todd Orr wrote:
Thanks for the info. I'll add that to my component. However, it seems
odd that a simple conversion from Long to String isn't built in. It
seems to me that such
Thanks for the info. I'll add that to my component. However, it seems
odd that a simple conversion from Long to String isn't built in. It
seems to me that such standard conversions should be part of the
framework.
On 8/14/07, Christian Koeberl <[EMAIL PROTECTED]> wrote:
> Tapestry just supports a
Tapestry just supports a ValueEncoder for String and Enum. If you want
additional
encoders you have to implement them yourself:
class LongValueEncoder implements ValueEncoder
{
public String toClient(Long value)
{
return value == null ? "" : value.toString();
This error looks familiar. Can you post some source?
(I can't get to it myself for a couple of days though.)
Cheers,
Nick.
redijedi wrote:
>
> I've suddenly run into what seems to be a bug that appears when I pass
> an integer to a custom component that itself contains a radiogroup
> that use
