Great, thanks Filip and Howard! :-) I hadn't ever thought of contributing a
DataTypeAnalyzer before the default one.
On Thu, Apr 10, 2008 at 8:42 PM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> Or contribute your own DataTypeAnalyzer ahead of the
> DefaultDataTypeAnalyzer that specifically rec
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 Pet
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/apid
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
