On Fri, Oct 17, 2008 at 2:56 AM, Moritz Gmelin <[EMAIL PROTECTED]> wrote:
> Hi,
>
> In our application we override the default editing component for Date types
> to be the DateTimeEditor from t5-components (why is that one not the
> default. It is so much nicer?).
Licensing. An Apache project has certain limitations in this regard;
fortunately, Tapestry is so good at late binding that you can bypass
those kinds of issues.
>
>
> AppModule.java
> public static void contributeBeanBlockSource(
> Configuration<BeanBlockContribution>
> configuration)
> {
>
> configuration.add(new BeanBlockContribution("date",
> "AppPropertyEditBlocks", "date", true));
>
> }
>
> Now it sometimes happens that dates are still rendered with the T5_Default
> DateField editor. Re-starting the application most often solves this so that
> my contributed renderer is used again.
> Is this some kind of timing issue in T5.0.15 with the contributions?
None that I can think of. If you look at the code, there's not any
room for variations as you describibe; a Map is created when the
BeanBlockSource is realized and then the Map is just used. Something
else must be going on.
>
> Thanks
>
> Moritz
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
