Hi,
I am still trying to understand why you think you need a seperate
interface for getting the unique id. Component.getPath() gets you the
unique id within the page already.
Yes, it gets you *a* unique id within the page, but nothing
guarantees you that this is the document id in the markup. But you're
right, the interface is not neccessary. What I tried to do is
separate "component id / path" from "document id" because these two
things have nothing to do with each other. It's just that the
component path makes a good candidate for the document id, because
it's unique.
What we can do - and what we actually talked about doing in a distant
past - is attaching an AttributeModifier (yes, I do like them) that
appends an id attribute with that path value when some application
wide setting is set. Because that is your only actual problem, right?
That you don't want to attach AttributeModifiers all of the time, but
instead want something that works out-of-the-box?
well, the actual problem (taken apart from any ideas) is: a component
which is rendering its markup a wants to have another component
rending a id="" attribute as part of is markup and want to know that
id. So I also don't need them application wide, I just need a way to
tell a component to do this. As mentioned, an AttributeModifier can
do this easily, but as noted in the original rfe (sorry that I filed
it as bug) I felt this rather complicated for such a standard thing.
AttributeModifier => sorry I was a bit angry about them :) I just
like to work in a more direct way with markup attributes, f.e.
expressing things like "add it only if its not there" in java code
instead of a flags like addAttributeIfNotPresent. But thats a matter
of taste :)
Regards,
Ralf
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
