Or contribute your own DataTypeAnalyzer ahead of the DefaultDataTypeAnalyzer that specifically recognizes the String type and provides whatever datatype you want. But I suspect Filip's approach is what you want.
On Thu, Apr 10, 2008 at 2:43 PM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote: > Hi Peter, > > If you're doing this to provide another property editor for the "text" data > type for use in BeanEditor/BeanEditForm you should take a look at the > BeanBlockOverrideSource which will let you override the defaults specified > in BeanBlockSource. > > > http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry/services/BeanBlockOverrideSource.html > > If that's not what you're trying to do, well, then I don't know. :p > > -Filip > > > > On 2008-04-10 20:03, Peter Beshai wrote: > > > TapestryModule contributes to the DefaultDataTypeAnalyzer String.class as > > "text". Is it possible to override what String.class is mapped to? > > > > http://tapestry.apache.org/tapestry5/tapestry-ioc/configuration.html > states > > that: "The keys passed in must be unique. When conflicts occur, Tapestry > > will log warnings (identifying the source, in terms of invoked methods, of > > the conflict), and ignore the conflicting value." So I cannot simply do: > > configuration.add(String.class, "customText"); > > > > > > Peter Beshai > > > > > > --------------------------------------------------------------------- > 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]
