Juergen,
I think your example is breaking the concept of Wicket because you are embedding business rules within the HTML page. In your case you are making the HTML aware of roles, which are a business concept. The HTML should only contain links to components and nothing else. Within the code for your component you should check the user's role and make a component visible or not. I think you have again got into the mindset of subclassing when it is not appropriate. The problem you are trying to solve is behavoural and therefore should be done as Java logic inside a component and not by subclassing a component. I am therefre -1 for your suggested change.
Regards,
Chris
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: 06 December 2004 23:48
> To: [EMAIL PROTECTED]
> Subject: Re: [Wicket-develop] handleUnknownComponents
>
>
> ??? Sorry, it is probably my english, but I don't understand
> your comment. I already have a component which disable menu
> item by means of <li id="wcn-[role:amin] and which proves
> that you can do it.
>
> regards
> Juergen
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from
> real users. Discover which products truly live up to the
> hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Wicket-develop mailing list [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
>
