if it helps you can manually call rendered() on the component link and that should quiet the use check.
-Igor
On 3/14/06, David Leangen <[EMAIL PROTECTED]> wrote:
> Hi David, thanks for your contribution. You mention that 'wicket does
> not allow us to pass parameters to our components'. However, Wicket
> components /can/ access their attributes. Currently, if you override
> onComponentTag(ComponentTag tag), you can find all the attribute
> information in the tag. You can even edit it, which is done by e.g.
> AttributeModifiers. Alternatively, you may call getMarkupAttributes()
> to get them, though this currently has the limitation that you
> component has to be added to it's parent. This latter restriction will
> be eliminated in Wicket 1.3 when we do our constructor change.
That's cool.
But it still doesn't solve the problem that for some localisations, the
link may not exist. In such cases, since the link is not rendered, an
exception will be thrown.
Cheers,
Dave
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
