[
https://issues.apache.org/jira/browse/TAP5-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033526#comment-14033526
]
Lance edited comment on TAP5-1611 at 6/17/14 7:44 AM:
------------------------------------------------------
{quote}I thought a class would be loaded and initialized when the first line of
code with any kind of reference to it was run{quote}
Me too.... I guess it's back to java school for both of us!
{quote}I'll leave the contribution as class instances, as I couldn't find any
downside yet{quote}
Ok, it still feels a bit wrong to me with all the dynamic classloading but I
won't object. I wonder if [~hlship] has anything to add?
Thanks again for the fix.... Long live #MonthOfTapestry
was (Author: uklance):
{quote}I thought a class would be loaded and initialized when the first line of
code with any kind of reference to it was run{quote}
Me too.... I guess it's back to java school for both of us!
{quote}I'll leave the contribution as class instances, as I couldn't find any
downside yet{qoute}
Ok, it still feels a bit wrong to me with all the dynamic classloading but I
won't object. I wonder if [~hlship] has anything to add?
Thanks again for the fix.... Long live #MonthOfTapestry
> out-of-the-box way in Tapestry for replacing components
> -------------------------------------------------------
>
> Key: TAP5-1611
> URL: https://issues.apache.org/jira/browse/TAP5-1611
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Jens Breitenstein
> Assignee: Thiago H. de Paula Figueiredo
> Priority: Minor
> Labels: component, month-of-tapestry
> Fix For: 5.4
>
>
> It would be nice to allow global component replacement by a different
> component class (or derived version from the original) compared to the field
> type provided. So @InjectComponent would behave more or less like @Inject for
> services without the need of Interfaces.
> NOTE:
> current workaround is decorating ComponentInstantiatorSource
> As Thiago outlines my workaround is sub-optimal as it bases on internal
> classes which might subject to change without notice. He suggests to have an
> Service we can contribute our "overrides" to. Replaceing components would
> introduce a new level of flexibility to change implementations without
> touching tml's at all. Naturally ServiceBinder was not my suggested place for
> this new kind of "binding", seems to be a misunderstanding. From a functional
> point of view I was just thinking about something like...
> public static void bind(final ComponentBinder binder)
> {
> binder.bind(ComponentA,class, ComponentBderivedFromA.class);
> }
> ...this, as an example.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
