I didn't get a response on the user list, and given that it's probably
more appropriate for the dev list, I'm forwarding it here. Apologies to
those that have seen it before.
--
Kevin
------- Forwarded message -------
From: "Kevin Menard" <[EMAIL PROTECTED]>
To: "Tapestry users" <tapestry-user@jakarta.apache.org>
Cc:
Subject: Re: Meta data and HiveMind?
Date: Mon, 31 Oct 2005 15:26:30 -0500
Given that HiveMind 1.1 has been released without a fix for HIVEMIND-151
(the report for the below bug), is there going to be a straightforward way
of converting meta values into other types in the T4 release?
Thanks,
Kevin
On Thu, 01 Sep 2005 14:09:44 -0400, Howard Lewis Ship <[EMAIL PROTECTED]>
wrote:
In HiveMind, the <set> element (of <construct>, with BuilderFactory)
will do simple string->primitive conversions.
Alas, the <set-object> element does no conversion at all.
This is really a HiveMind bug ... it should see if the object result
is java.lang.String and to a simple conversion for it.
Tapestry has a much more involved data-type-conversion system in
place, used to convert properties of any type to any desired type (or
explain why it can't). It's simple, but works. I've heard of systems
that can forward- and back-chain conversions until it finds a way to
convert ... that's probably overkill for Tapestry.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
