On Thu, 01 Dec 2005 11:28:41 -0500, Ron Piterman <[EMAIL PROTECTED]> wrote:
without regard to the topic of this thread, could you elaborate on what you mean here, and maye be give a usecase as example?
Sure thing. The meat of my original issue can be found at http://www.opensubscriber.com/message/tapestry-user@jakarta.apache.org/2056611.html. My concern now was raised in a later message, which I forwarded from the user list to the dev list on Nov. 22, but it mustn't have gone through (maybe tagged as spam? It's not in gmane, anyway). I've included the text of the original message below:
~~~ 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]
