as i see it there are two cases
a) when raw markup has this attribute
b) when a component has this attribute (markup with wicket:id)
for case (a) we dont need the full search stack do we? it makes sense to only try the limited stack right?
case (b) is where the issue is right now. i think a better hook for that is to have a pluggable componenttag handler rather then some weird render-time/markup time hooks.
something like IComponentTagHandler{ void onComponentTag(Component c, ComponentTag t); }
ISomeSettings.add(IComponentTagHandler handler);
this is much easier to understand because it builds on a concept that you have to know anyways.
-Igor
On 9/22/06,
Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 9/22/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> what do you mean inspect? the attribute modifier itself can perform the
> attribute replacement/i18n, why should this be any different then regular
> ams - excpet that this one is stateless/singleton. statelesness is a
> property of the behavior.
>
> the reason requiredvalidator.instance() is gone is that required validator
> itself is gone, there is nothing stopping you from sharing behaviors that
> are meant to be stateless across component instances.
Huh? We are talking about different things here. If you read back a
couple of posts you'll see Juergen say:
> What if the Message markup filter (which is only executed when the
> markup is loaded) were able to add a stateless attributemodifier to
> the component tag and that AM gets automatically attached to the
> component at render time.
I was talking about how a behavior would automatically get attached to
components. In order to achieve that, I think the render process
should somewhere inspect the tags and recognize there are behaviors to
be attached. Note the 'I *think*' part, as I was asking Juergen
whether that was what he had in mind.
Eelco
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
