You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Bruno Cesar Borges <br...@cetip.com.br> on 2008/11/17 20:03:59 UTC

Drop wicket:link

This might sound crazy, but what about dropping the support for the tag <wicket:link> ? :-)

People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that.

Example: 

   # Java
   AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer("menus");

   # HTML
   <ul wicket:id="menus">
     <li><a href="Users.html">Users</a></li>
     <li><a href="Departments.html">Departments</a></li>
   </ul>

What do you guys think?

Cheers,
Bruno
***************************************************************************************************
"Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s),
podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por 
lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema.
Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem 
expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, 
o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas."


"Warning: This message was sent for exclusive use of the addressees above identified, possibly 
containing information and or privileged/confidential documents whose content is protected by law. 
In case you have mistakenly received it, please notify the sender and delete it from your system. 
Be noticed that the law forbids the retention, dissemination, distribution, copy or use without 
express authorization from the sender. Personal opinions of the sender do not necessarily reflect 
CETIP's point of view, which is only divulged by authorized personnel."
***************************************************************************************************


Re: Drop wicket:link

Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
With the risk of hijacking the thread. It's really easy registering new 
stuff with the parser, I recently had a look at something in the 
formcomponent hieracy, and you just call a method or 2 to register new 
tags.. :)

James Carman wrote:
> That's my opinion, also.  I voted -1 to removing wicket:link.  I was
> more just curious about the inner workings of the parser at this point
> :)
>
> On Tue, Nov 18, 2008 at 4:59 PM, Peter Ertl <pe...@gmx.net> wrote:
>   
>> What's the problem with just leaving it where it is?
>>
>> If you don't like it ignore it - or am I missing something important here?
>>
>> Am 18.11.2008 um 22:12 schrieb James Carman:
>>
>>     
>>> Would the user have to register the plugin manually or would it be
>>> picked up merely by the jar being on the classpath?
>>>
>>> On Tue, Nov 18, 2008 at 4:01 PM, Igor Vaynberg <ig...@gmail.com>
>>> wrote:
>>>       
>>>> it is already all pluggable and wicketlink handler is just a plugin
>>>> into the parser :)
>>>>
>>>> -igor
>>>>
>>>> On Tue, Nov 18, 2008 at 12:29 PM, James Carman
>>>> <ja...@carmanconsulting.com> wrote:
>>>>         
>>>>> The markup parser has to know how to deal with it I would think.  That
>>>>> would be quite an undertaking to split that functionality out and make
>>>>> it able to be plugged back in.
>>>>>
>>>>> On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <rh...@kindleit.net>
>>>>> wrote:
>>>>>           
>>>>>> +1, what about moving it to an optional package? wicket-tags ?
>>>>>>
>>>>>> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <pe...@gmx.net> wrote:
>>>>>>
>>>>>>             
>>>>>>> -1, too:
>>>>>>>
>>>>>>> I use it just the way Igor describes. I usually set up a mock html
>>>>>>> page,
>>>>>>> then <wicket:link> the css and javascript. So I can easily test the
>>>>>>> page in
>>>>>>> preview mode and in wicket, too.
>>>>>>>
>>>>>>> Once the application evolves I tend to remove <wicket:link> again and
>>>>>>> replace it with ResourceReference inside the pages and base pages.
>>>>>>>
>>>>>>> Let it there, it's really useful. If people tend to be stupid no
>>>>>>> framework
>>>>>>> on earth will stop them from doing so.
>>>>>>>
>>>>>>> Cheers
>>>>>>> Peter
>>>>>>>
>>>>>>>
>>>>>>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>>>>>>
>>>>>>> -1.
>>>>>>>               
>>>>>>>> this stuff is very useful for linking to css/js/image files. if
>>>>>>>> people
>>>>>>>> want to abuse it, it is their problem. people will find a way to
>>>>>>>> abuse
>>>>>>>> anything though.
>>>>>>>>
>>>>>>>> -igor
>>>>>>>>
>>>>>>>> 2008/11/17 Bruno Cesar Borges <br...@cetip.com.br>:
>>>>>>>>
>>>>>>>>                 
>>>>>>>>> This might sound crazy, but what about dropping the support for the
>>>>>>>>> tag
>>>>>>>>> <wicket:link> ? :-)
>>>>>>>>>
>>>>>>>>> People are starting to use it frequently, and because of that,
>>>>>>>>> features
>>>>>>>>> will be requested. And then we might end with a tag library. But, to
>>>>>>>>> not
>>>>>>>>> freak everybody out, I suggest develop a markup container to do
>>>>>>>>> that.
>>>>>>>>>
>>>>>>>>> Example:
>>>>>>>>>
>>>>>>>>> # Java
>>>>>>>>> AutoLinkMarkupContainer autolinks = new
>>>>>>>>> AutoLinkMarkupContainer("menus");
>>>>>>>>>
>>>>>>>>> # HTML
>>>>>>>>> <ul wicket:id="menus">
>>>>>>>>> <li><a href="Users.html">Users</a></li>
>>>>>>>>> <li><a href="Departments.html">Departments</a></li>
>>>>>>>>> </ul>
>>>>>>>>>
>>>>>>>>> What do you guys think?
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Bruno
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ***************************************************************************************************
>>>>>>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>>>>>>> destinatários(s) acima identificado(s),
>>>>>>>>> podendo conter informações e/ou documentos
>>>>>>>>> confidencias/privilegiados e
>>>>>>>>> seu sigilo é protegido por
>>>>>>>>> lei. Caso você tenha recebido por engano, por favor, informe o
>>>>>>>>> remetente
>>>>>>>>> e apague-a de seu sistema.
>>>>>>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>>>>>>> distribuição, cópia ou uso sem
>>>>>>>>> expressa autorização do remetente. Opiniões pessoais do remetente
>>>>>>>>> não
>>>>>>>>> refletem, necessariamente,
>>>>>>>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>>>>>>>> autorizadas."
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> "Warning: This message was sent for exclusive use of the addressees
>>>>>>>>> above
>>>>>>>>> identified, possibly
>>>>>>>>> containing information and or privileged/confidential documents
>>>>>>>>> whose
>>>>>>>>> content is protected by law.
>>>>>>>>> In case you have mistakenly received it, please notify the sender
>>>>>>>>> and
>>>>>>>>> delete it from your system.
>>>>>>>>> Be noticed that the law forbids the retention, dissemination,
>>>>>>>>> distribution, copy or use without
>>>>>>>>> express authorization from the sender. Personal opinions of the
>>>>>>>>> sender do
>>>>>>>>> not necessarily reflect
>>>>>>>>> CETIP's point of view, which is only divulged by authorized
>>>>>>>>> personnel."
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ***************************************************************************************************
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                   
>>     

-- 
-Wicket for love

Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684


Re: Drop wicket:link

Posted by James Carman <ja...@carmanconsulting.com>.
That's my opinion, also.  I voted -1 to removing wicket:link.  I was
more just curious about the inner workings of the parser at this point
:)

On Tue, Nov 18, 2008 at 4:59 PM, Peter Ertl <pe...@gmx.net> wrote:
> What's the problem with just leaving it where it is?
>
> If you don't like it ignore it - or am I missing something important here?
>
> Am 18.11.2008 um 22:12 schrieb James Carman:
>
>> Would the user have to register the plugin manually or would it be
>> picked up merely by the jar being on the classpath?
>>
>> On Tue, Nov 18, 2008 at 4:01 PM, Igor Vaynberg <ig...@gmail.com>
>> wrote:
>>>
>>> it is already all pluggable and wicketlink handler is just a plugin
>>> into the parser :)
>>>
>>> -igor
>>>
>>> On Tue, Nov 18, 2008 at 12:29 PM, James Carman
>>> <ja...@carmanconsulting.com> wrote:
>>>>
>>>> The markup parser has to know how to deal with it I would think.  That
>>>> would be quite an undertaking to split that functionality out and make
>>>> it able to be plugged back in.
>>>>
>>>> On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <rh...@kindleit.net>
>>>> wrote:
>>>>>
>>>>> +1, what about moving it to an optional package? wicket-tags ?
>>>>>
>>>>> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <pe...@gmx.net> wrote:
>>>>>
>>>>>> -1, too:
>>>>>>
>>>>>> I use it just the way Igor describes. I usually set up a mock html
>>>>>> page,
>>>>>> then <wicket:link> the css and javascript. So I can easily test the
>>>>>> page in
>>>>>> preview mode and in wicket, too.
>>>>>>
>>>>>> Once the application evolves I tend to remove <wicket:link> again and
>>>>>> replace it with ResourceReference inside the pages and base pages.
>>>>>>
>>>>>> Let it there, it's really useful. If people tend to be stupid no
>>>>>> framework
>>>>>> on earth will stop them from doing so.
>>>>>>
>>>>>> Cheers
>>>>>> Peter
>>>>>>
>>>>>>
>>>>>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>>>>>
>>>>>> -1.
>>>>>>>
>>>>>>> this stuff is very useful for linking to css/js/image files. if
>>>>>>> people
>>>>>>> want to abuse it, it is their problem. people will find a way to
>>>>>>> abuse
>>>>>>> anything though.
>>>>>>>
>>>>>>> -igor
>>>>>>>
>>>>>>> 2008/11/17 Bruno Cesar Borges <br...@cetip.com.br>:
>>>>>>>
>>>>>>>> This might sound crazy, but what about dropping the support for the
>>>>>>>> tag
>>>>>>>> <wicket:link> ? :-)
>>>>>>>>
>>>>>>>> People are starting to use it frequently, and because of that,
>>>>>>>> features
>>>>>>>> will be requested. And then we might end with a tag library. But, to
>>>>>>>> not
>>>>>>>> freak everybody out, I suggest develop a markup container to do
>>>>>>>> that.
>>>>>>>>
>>>>>>>> Example:
>>>>>>>>
>>>>>>>> # Java
>>>>>>>> AutoLinkMarkupContainer autolinks = new
>>>>>>>> AutoLinkMarkupContainer("menus");
>>>>>>>>
>>>>>>>> # HTML
>>>>>>>> <ul wicket:id="menus">
>>>>>>>> <li><a href="Users.html">Users</a></li>
>>>>>>>> <li><a href="Departments.html">Departments</a></li>
>>>>>>>> </ul>
>>>>>>>>
>>>>>>>> What do you guys think?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Bruno
>>>>>>>>
>>>>>>>>
>>>>>>>> ***************************************************************************************************
>>>>>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>>>>>> destinatários(s) acima identificado(s),
>>>>>>>> podendo conter informações e/ou documentos
>>>>>>>> confidencias/privilegiados e
>>>>>>>> seu sigilo é protegido por
>>>>>>>> lei. Caso você tenha recebido por engano, por favor, informe o
>>>>>>>> remetente
>>>>>>>> e apague-a de seu sistema.
>>>>>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>>>>>> distribuição, cópia ou uso sem
>>>>>>>> expressa autorização do remetente. Opiniões pessoais do remetente
>>>>>>>> não
>>>>>>>> refletem, necessariamente,
>>>>>>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>>>>>>> autorizadas."
>>>>>>>>
>>>>>>>>
>>>>>>>> "Warning: This message was sent for exclusive use of the addressees
>>>>>>>> above
>>>>>>>> identified, possibly
>>>>>>>> containing information and or privileged/confidential documents
>>>>>>>> whose
>>>>>>>> content is protected by law.
>>>>>>>> In case you have mistakenly received it, please notify the sender
>>>>>>>> and
>>>>>>>> delete it from your system.
>>>>>>>> Be noticed that the law forbids the retention, dissemination,
>>>>>>>> distribution, copy or use without
>>>>>>>> express authorization from the sender. Personal opinions of the
>>>>>>>> sender do
>>>>>>>> not necessarily reflect
>>>>>>>> CETIP's point of view, which is only divulged by authorized
>>>>>>>> personnel."
>>>>>>>>
>>>>>>>>
>>>>>>>> ***************************************************************************************************
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>
>

Re: Drop wicket:link

Posted by Peter Ertl <pe...@gmx.net>.
What's the problem with just leaving it where it is?

If you don't like it ignore it - or am I missing something important  
here?

Am 18.11.2008 um 22:12 schrieb James Carman:

> Would the user have to register the plugin manually or would it be
> picked up merely by the jar being on the classpath?
>
> On Tue, Nov 18, 2008 at 4:01 PM, Igor Vaynberg <igor.vaynberg@gmail.com 
> > wrote:
>> it is already all pluggable and wicketlink handler is just a plugin
>> into the parser :)
>>
>> -igor
>>
>> On Tue, Nov 18, 2008 at 12:29 PM, James Carman
>> <ja...@carmanconsulting.com> wrote:
>>> The markup parser has to know how to deal with it I would think.   
>>> That
>>> would be quite an undertaking to split that functionality out and  
>>> make
>>> it able to be plugged back in.
>>>
>>> On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <rhansen@kindleit.net 
>>> > wrote:
>>>> +1, what about moving it to an optional package? wicket-tags ?
>>>>
>>>> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <pe...@gmx.net>  
>>>> wrote:
>>>>
>>>>> -1, too:
>>>>>
>>>>> I use it just the way Igor describes. I usually set up a mock  
>>>>> html page,
>>>>> then <wicket:link> the css and javascript. So I can easily test  
>>>>> the page in
>>>>> preview mode and in wicket, too.
>>>>>
>>>>> Once the application evolves I tend to remove <wicket:link>  
>>>>> again and
>>>>> replace it with ResourceReference inside the pages and base pages.
>>>>>
>>>>> Let it there, it's really useful. If people tend to be stupid no  
>>>>> framework
>>>>> on earth will stop them from doing so.
>>>>>
>>>>> Cheers
>>>>> Peter
>>>>>
>>>>>
>>>>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>>>>
>>>>> -1.
>>>>>>
>>>>>> this stuff is very useful for linking to css/js/image files. if  
>>>>>> people
>>>>>> want to abuse it, it is their problem. people will find a way  
>>>>>> to abuse
>>>>>> anything though.
>>>>>>
>>>>>> -igor
>>>>>>
>>>>>> 2008/11/17 Bruno Cesar Borges <br...@cetip.com.br>:
>>>>>>
>>>>>>> This might sound crazy, but what about dropping the support  
>>>>>>> for the tag
>>>>>>> <wicket:link> ? :-)
>>>>>>>
>>>>>>> People are starting to use it frequently, and because of that,  
>>>>>>> features
>>>>>>> will be requested. And then we might end with a tag library.  
>>>>>>> But, to not
>>>>>>> freak everybody out, I suggest develop a markup container to  
>>>>>>> do that.
>>>>>>>
>>>>>>> Example:
>>>>>>>
>>>>>>> # Java
>>>>>>> AutoLinkMarkupContainer autolinks = new
>>>>>>> AutoLinkMarkupContainer("menus");
>>>>>>>
>>>>>>> # HTML
>>>>>>> <ul wicket:id="menus">
>>>>>>> <li><a href="Users.html">Users</a></li>
>>>>>>> <li><a href="Departments.html">Departments</a></li>
>>>>>>> </ul>
>>>>>>>
>>>>>>> What do you guys think?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Bruno
>>>>>>>
>>>>>>> ***************************************************************************************************
>>>>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>>>>> destinatários(s) acima identificado(s),
>>>>>>> podendo conter informações e/ou documentos confidencias/ 
>>>>>>> privilegiados e
>>>>>>> seu sigilo é protegido por
>>>>>>> lei. Caso você tenha recebido por engano, por favor, informe o  
>>>>>>> remetente
>>>>>>> e apague-a de seu sistema.
>>>>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>>>>> distribuição, cópia ou uso sem
>>>>>>> expressa autorização do remetente. Opiniões pessoais do  
>>>>>>> remetente não
>>>>>>> refletem, necessariamente,
>>>>>>> o ponto de vista da CETIP, o qual é divulgado somente por  
>>>>>>> pessoas
>>>>>>> autorizadas."
>>>>>>>
>>>>>>>
>>>>>>> "Warning: This message was sent for exclusive use of the  
>>>>>>> addressees above
>>>>>>> identified, possibly
>>>>>>> containing information and or privileged/confidential  
>>>>>>> documents whose
>>>>>>> content is protected by law.
>>>>>>> In case you have mistakenly received it, please notify the  
>>>>>>> sender and
>>>>>>> delete it from your system.
>>>>>>> Be noticed that the law forbids the retention, dissemination,
>>>>>>> distribution, copy or use without
>>>>>>> express authorization from the sender. Personal opinions of  
>>>>>>> the sender do
>>>>>>> not necessarily reflect
>>>>>>> CETIP's point of view, which is only divulged by authorized  
>>>>>>> personnel."
>>>>>>>
>>>>>>> ***************************************************************************************************
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>
>>


Re: Drop wicket:link

Posted by James Carman <ja...@carmanconsulting.com>.
Would the user have to register the plugin manually or would it be
picked up merely by the jar being on the classpath?

On Tue, Nov 18, 2008 at 4:01 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> it is already all pluggable and wicketlink handler is just a plugin
> into the parser :)
>
> -igor
>
> On Tue, Nov 18, 2008 at 12:29 PM, James Carman
> <ja...@carmanconsulting.com> wrote:
>> The markup parser has to know how to deal with it I would think.  That
>> would be quite an undertaking to split that functionality out and make
>> it able to be plugged back in.
>>
>> On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <rh...@kindleit.net> wrote:
>>> +1, what about moving it to an optional package? wicket-tags ?
>>>
>>> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <pe...@gmx.net> wrote:
>>>
>>>> -1, too:
>>>>
>>>> I use it just the way Igor describes. I usually set up a mock html page,
>>>> then <wicket:link> the css and javascript. So I can easily test the page in
>>>> preview mode and in wicket, too.
>>>>
>>>> Once the application evolves I tend to remove <wicket:link> again and
>>>> replace it with ResourceReference inside the pages and base pages.
>>>>
>>>> Let it there, it's really useful. If people tend to be stupid no framework
>>>> on earth will stop them from doing so.
>>>>
>>>> Cheers
>>>> Peter
>>>>
>>>>
>>>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>>>
>>>>  -1.
>>>>>
>>>>> this stuff is very useful for linking to css/js/image files. if people
>>>>> want to abuse it, it is their problem. people will find a way to abuse
>>>>> anything though.
>>>>>
>>>>> -igor
>>>>>
>>>>> 2008/11/17 Bruno Cesar Borges <br...@cetip.com.br>:
>>>>>
>>>>>> This might sound crazy, but what about dropping the support for the tag
>>>>>> <wicket:link> ? :-)
>>>>>>
>>>>>> People are starting to use it frequently, and because of that, features
>>>>>> will be requested. And then we might end with a tag library. But, to not
>>>>>> freak everybody out, I suggest develop a markup container to do that.
>>>>>>
>>>>>> Example:
>>>>>>
>>>>>>  # Java
>>>>>>  AutoLinkMarkupContainer autolinks = new
>>>>>> AutoLinkMarkupContainer("menus");
>>>>>>
>>>>>>  # HTML
>>>>>>  <ul wicket:id="menus">
>>>>>>   <li><a href="Users.html">Users</a></li>
>>>>>>   <li><a href="Departments.html">Departments</a></li>
>>>>>>  </ul>
>>>>>>
>>>>>> What do you guys think?
>>>>>>
>>>>>> Cheers,
>>>>>> Bruno
>>>>>>
>>>>>> ***************************************************************************************************
>>>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>>>> destinatários(s) acima identificado(s),
>>>>>> podendo conter informações e/ou documentos confidencias/privilegiados e
>>>>>> seu sigilo é protegido por
>>>>>> lei. Caso você tenha recebido por engano, por favor, informe o remetente
>>>>>> e apague-a de seu sistema.
>>>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>>>> distribuição, cópia ou uso sem
>>>>>> expressa autorização do remetente. Opiniões pessoais do remetente não
>>>>>> refletem, necessariamente,
>>>>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>>>>> autorizadas."
>>>>>>
>>>>>>
>>>>>> "Warning: This message was sent for exclusive use of the addressees above
>>>>>> identified, possibly
>>>>>> containing information and or privileged/confidential documents whose
>>>>>> content is protected by law.
>>>>>> In case you have mistakenly received it, please notify the sender and
>>>>>> delete it from your system.
>>>>>> Be noticed that the law forbids the retention, dissemination,
>>>>>> distribution, copy or use without
>>>>>> express authorization from the sender. Personal opinions of the sender do
>>>>>> not necessarily reflect
>>>>>> CETIP's point of view, which is only divulged by authorized personnel."
>>>>>>
>>>>>> ***************************************************************************************************
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>
>

Re: Drop wicket:link

Posted by Igor Vaynberg <ig...@gmail.com>.
it is already all pluggable and wicketlink handler is just a plugin
into the parser :)

-igor

On Tue, Nov 18, 2008 at 12:29 PM, James Carman
<ja...@carmanconsulting.com> wrote:
> The markup parser has to know how to deal with it I would think.  That
> would be quite an undertaking to split that functionality out and make
> it able to be plugged back in.
>
> On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <rh...@kindleit.net> wrote:
>> +1, what about moving it to an optional package? wicket-tags ?
>>
>> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <pe...@gmx.net> wrote:
>>
>>> -1, too:
>>>
>>> I use it just the way Igor describes. I usually set up a mock html page,
>>> then <wicket:link> the css and javascript. So I can easily test the page in
>>> preview mode and in wicket, too.
>>>
>>> Once the application evolves I tend to remove <wicket:link> again and
>>> replace it with ResourceReference inside the pages and base pages.
>>>
>>> Let it there, it's really useful. If people tend to be stupid no framework
>>> on earth will stop them from doing so.
>>>
>>> Cheers
>>> Peter
>>>
>>>
>>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>>
>>>  -1.
>>>>
>>>> this stuff is very useful for linking to css/js/image files. if people
>>>> want to abuse it, it is their problem. people will find a way to abuse
>>>> anything though.
>>>>
>>>> -igor
>>>>
>>>> 2008/11/17 Bruno Cesar Borges <br...@cetip.com.br>:
>>>>
>>>>> This might sound crazy, but what about dropping the support for the tag
>>>>> <wicket:link> ? :-)
>>>>>
>>>>> People are starting to use it frequently, and because of that, features
>>>>> will be requested. And then we might end with a tag library. But, to not
>>>>> freak everybody out, I suggest develop a markup container to do that.
>>>>>
>>>>> Example:
>>>>>
>>>>>  # Java
>>>>>  AutoLinkMarkupContainer autolinks = new
>>>>> AutoLinkMarkupContainer("menus");
>>>>>
>>>>>  # HTML
>>>>>  <ul wicket:id="menus">
>>>>>   <li><a href="Users.html">Users</a></li>
>>>>>   <li><a href="Departments.html">Departments</a></li>
>>>>>  </ul>
>>>>>
>>>>> What do you guys think?
>>>>>
>>>>> Cheers,
>>>>> Bruno
>>>>>
>>>>> ***************************************************************************************************
>>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>>> destinatários(s) acima identificado(s),
>>>>> podendo conter informações e/ou documentos confidencias/privilegiados e
>>>>> seu sigilo é protegido por
>>>>> lei. Caso você tenha recebido por engano, por favor, informe o remetente
>>>>> e apague-a de seu sistema.
>>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>>> distribuição, cópia ou uso sem
>>>>> expressa autorização do remetente. Opiniões pessoais do remetente não
>>>>> refletem, necessariamente,
>>>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>>>> autorizadas."
>>>>>
>>>>>
>>>>> "Warning: This message was sent for exclusive use of the addressees above
>>>>> identified, possibly
>>>>> containing information and or privileged/confidential documents whose
>>>>> content is protected by law.
>>>>> In case you have mistakenly received it, please notify the sender and
>>>>> delete it from your system.
>>>>> Be noticed that the law forbids the retention, dissemination,
>>>>> distribution, copy or use without
>>>>> express authorization from the sender. Personal opinions of the sender do
>>>>> not necessarily reflect
>>>>> CETIP's point of view, which is only divulged by authorized personnel."
>>>>>
>>>>> ***************************************************************************************************
>>>>>
>>>>>
>>>>>
>>>
>>
>

Re: Drop wicket:link

Posted by James Carman <ja...@carmanconsulting.com>.
The markup parser has to know how to deal with it I would think.  That
would be quite an undertaking to split that functionality out and make
it able to be plugged back in.

On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen <rh...@kindleit.net> wrote:
> +1, what about moving it to an optional package? wicket-tags ?
>
> On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <pe...@gmx.net> wrote:
>
>> -1, too:
>>
>> I use it just the way Igor describes. I usually set up a mock html page,
>> then <wicket:link> the css and javascript. So I can easily test the page in
>> preview mode and in wicket, too.
>>
>> Once the application evolves I tend to remove <wicket:link> again and
>> replace it with ResourceReference inside the pages and base pages.
>>
>> Let it there, it's really useful. If people tend to be stupid no framework
>> on earth will stop them from doing so.
>>
>> Cheers
>> Peter
>>
>>
>> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>>
>>  -1.
>>>
>>> this stuff is very useful for linking to css/js/image files. if people
>>> want to abuse it, it is their problem. people will find a way to abuse
>>> anything though.
>>>
>>> -igor
>>>
>>> 2008/11/17 Bruno Cesar Borges <br...@cetip.com.br>:
>>>
>>>> This might sound crazy, but what about dropping the support for the tag
>>>> <wicket:link> ? :-)
>>>>
>>>> People are starting to use it frequently, and because of that, features
>>>> will be requested. And then we might end with a tag library. But, to not
>>>> freak everybody out, I suggest develop a markup container to do that.
>>>>
>>>> Example:
>>>>
>>>>  # Java
>>>>  AutoLinkMarkupContainer autolinks = new
>>>> AutoLinkMarkupContainer("menus");
>>>>
>>>>  # HTML
>>>>  <ul wicket:id="menus">
>>>>   <li><a href="Users.html">Users</a></li>
>>>>   <li><a href="Departments.html">Departments</a></li>
>>>>  </ul>
>>>>
>>>> What do you guys think?
>>>>
>>>> Cheers,
>>>> Bruno
>>>>
>>>> ***************************************************************************************************
>>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>>> destinatários(s) acima identificado(s),
>>>> podendo conter informações e/ou documentos confidencias/privilegiados e
>>>> seu sigilo é protegido por
>>>> lei. Caso você tenha recebido por engano, por favor, informe o remetente
>>>> e apague-a de seu sistema.
>>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>>> distribuição, cópia ou uso sem
>>>> expressa autorização do remetente. Opiniões pessoais do remetente não
>>>> refletem, necessariamente,
>>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>>> autorizadas."
>>>>
>>>>
>>>> "Warning: This message was sent for exclusive use of the addressees above
>>>> identified, possibly
>>>> containing information and or privileged/confidential documents whose
>>>> content is protected by law.
>>>> In case you have mistakenly received it, please notify the sender and
>>>> delete it from your system.
>>>> Be noticed that the law forbids the retention, dissemination,
>>>> distribution, copy or use without
>>>> express authorization from the sender. Personal opinions of the sender do
>>>> not necessarily reflect
>>>> CETIP's point of view, which is only divulged by authorized personnel."
>>>>
>>>> ***************************************************************************************************
>>>>
>>>>
>>>>
>>
>

Re: Drop wicket:link

Posted by Rodolfo Hansen <rh...@kindleit.net>.
+1, what about moving it to an optional package? wicket-tags ?

On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl <pe...@gmx.net> wrote:

> -1, too:
>
> I use it just the way Igor describes. I usually set up a mock html page,
> then <wicket:link> the css and javascript. So I can easily test the page in
> preview mode and in wicket, too.
>
> Once the application evolves I tend to remove <wicket:link> again and
> replace it with ResourceReference inside the pages and base pages.
>
> Let it there, it's really useful. If people tend to be stupid no framework
> on earth will stop them from doing so.
>
> Cheers
> Peter
>
>
> Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:
>
>  -1.
>>
>> this stuff is very useful for linking to css/js/image files. if people
>> want to abuse it, it is their problem. people will find a way to abuse
>> anything though.
>>
>> -igor
>>
>> 2008/11/17 Bruno Cesar Borges <br...@cetip.com.br>:
>>
>>> This might sound crazy, but what about dropping the support for the tag
>>> <wicket:link> ? :-)
>>>
>>> People are starting to use it frequently, and because of that, features
>>> will be requested. And then we might end with a tag library. But, to not
>>> freak everybody out, I suggest develop a markup container to do that.
>>>
>>> Example:
>>>
>>>  # Java
>>>  AutoLinkMarkupContainer autolinks = new
>>> AutoLinkMarkupContainer("menus");
>>>
>>>  # HTML
>>>  <ul wicket:id="menus">
>>>   <li><a href="Users.html">Users</a></li>
>>>   <li><a href="Departments.html">Departments</a></li>
>>>  </ul>
>>>
>>> What do you guys think?
>>>
>>> Cheers,
>>> Bruno
>>>
>>> ***************************************************************************************************
>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>> destinatários(s) acima identificado(s),
>>> podendo conter informações e/ou documentos confidencias/privilegiados e
>>> seu sigilo é protegido por
>>> lei. Caso você tenha recebido por engano, por favor, informe o remetente
>>> e apague-a de seu sistema.
>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>> distribuição, cópia ou uso sem
>>> expressa autorização do remetente. Opiniões pessoais do remetente não
>>> refletem, necessariamente,
>>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas
>>> autorizadas."
>>>
>>>
>>> "Warning: This message was sent for exclusive use of the addressees above
>>> identified, possibly
>>> containing information and or privileged/confidential documents whose
>>> content is protected by law.
>>> In case you have mistakenly received it, please notify the sender and
>>> delete it from your system.
>>> Be noticed that the law forbids the retention, dissemination,
>>> distribution, copy or use without
>>> express authorization from the sender. Personal opinions of the sender do
>>> not necessarily reflect
>>> CETIP's point of view, which is only divulged by authorized personnel."
>>>
>>> ***************************************************************************************************
>>>
>>>
>>>
>

Re: Drop wicket:link

Posted by Peter Ertl <pe...@gmx.net>.
-1, too:

I use it just the way Igor describes. I usually set up a mock html  
page, then <wicket:link> the css and javascript. So I can easily test  
the page in preview mode and in wicket, too.

Once the application evolves I tend to remove <wicket:link> again and  
replace it with ResourceReference inside the pages and base pages.

Let it there, it's really useful. If people tend to be stupid no  
framework on earth will stop them from doing so.

Cheers
Peter


Am 17.11.2008 um 21:06 schrieb Igor Vaynberg:

> -1.
>
> this stuff is very useful for linking to css/js/image files. if people
> want to abuse it, it is their problem. people will find a way to abuse
> anything though.
>
> -igor
>
> 2008/11/17 Bruno Cesar Borges <br...@cetip.com.br>:
>> This might sound crazy, but what about dropping the support for the  
>> tag <wicket:link> ? :-)
>>
>> People are starting to use it frequently, and because of that,  
>> features will be requested. And then we might end with a tag  
>> library. But, to not freak everybody out, I suggest develop a  
>> markup container to do that.
>>
>> Example:
>>
>>  # Java
>>  AutoLinkMarkupContainer autolinks = new  
>> AutoLinkMarkupContainer("menus");
>>
>>  # HTML
>>  <ul wicket:id="menus">
>>    <li><a href="Users.html">Users</a></li>
>>    <li><a href="Departments.html">Departments</a></li>
>>  </ul>
>>
>> What do you guys think?
>>
>> Cheers,
>> Bruno
>> ***************************************************************************************************
>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)  
>> destinatários(s) acima identificado(s),
>> podendo conter informações e/ou documentos confidencias/ 
>> privilegiados e seu sigilo é protegido por
>> lei. Caso você tenha recebido por engano, por favor, informe o  
>> remetente e apague-a de seu sistema.
>> Notificamos que é proibido por lei a sua retenção, disseminação,  
>> distribuição, cópia ou uso sem
>> expressa autorização do remetente. Opiniões pessoais do remetente  
>> não refletem, necessariamente,
>> o ponto de vista da CETIP, o qual é divulgado somente por pessoas  
>> autorizadas."
>>
>>
>> "Warning: This message was sent for exclusive use of the addressees  
>> above identified, possibly
>> containing information and or privileged/confidential documents  
>> whose content is protected by law.
>> In case you have mistakenly received it, please notify the sender  
>> and delete it from your system.
>> Be noticed that the law forbids the retention, dissemination,  
>> distribution, copy or use without
>> express authorization from the sender. Personal opinions of the  
>> sender do not necessarily reflect
>> CETIP's point of view, which is only divulged by authorized  
>> personnel."
>> ***************************************************************************************************
>>
>>


Re: Drop wicket:link

Posted by Igor Vaynberg <ig...@gmail.com>.
-1.

this stuff is very useful for linking to css/js/image files. if people
want to abuse it, it is their problem. people will find a way to abuse
anything though.

-igor

2008/11/17 Bruno Cesar Borges <br...@cetip.com.br>:
> This might sound crazy, but what about dropping the support for the tag <wicket:link> ? :-)
>
> People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that.
>
> Example:
>
>   # Java
>   AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer("menus");
>
>   # HTML
>   <ul wicket:id="menus">
>     <li><a href="Users.html">Users</a></li>
>     <li><a href="Departments.html">Departments</a></li>
>   </ul>
>
> What do you guys think?
>
> Cheers,
> Bruno
> ***************************************************************************************************
> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s),
> podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por
> lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema.
> Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem
> expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente,
> o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas."
>
>
> "Warning: This message was sent for exclusive use of the addressees above identified, possibly
> containing information and or privileged/confidential documents whose content is protected by law.
> In case you have mistakenly received it, please notify the sender and delete it from your system.
> Be noticed that the law forbids the retention, dissemination, distribution, copy or use without
> express authorization from the sender. Personal opinions of the sender do not necessarily reflect
> CETIP's point of view, which is only divulged by authorized personnel."
> ***************************************************************************************************
>
>

Re: Drop wicket:link

Posted by James Carman <ja...@carmanconsulting.com>.
There is support for this now.  It doesn't work for resources very
well, but for page links it works.

On Mon, Nov 17, 2008 at 2:24 PM, Nino Saturnino Martinez Vazquez Wael
<ni...@jayway.dk> wrote:
> And another thing it could make autolink parser able to look in other
> packages aswell for pages... Currently theres no support for autolinking to
> pages not in the same package..
>
> Nino Saturnino Martinez Vazquez Wael wrote:
>>
>> Hi Bruno
>>
>> +1 one from my side, the more of those horrible tag things we can get away
>> the better, they dont feel very wicket like anyway..
>>
>> And the worst thing I've even begun to use them. I just dont feel that
>> they fit into the split logic strategy..
>>
>> Bruno Cesar Borges wrote:
>>>
>>> This might sound crazy, but what about dropping the support for the tag
>>> <wicket:link> ? :-)
>>>
>>> People are starting to use it frequently, and because of that, features
>>> will be requested. And then we might end with a tag library. But, to not
>>> freak everybody out, I suggest develop a markup container to do that.
>>>
>>> Example:
>>>   # Java
>>>   AutoLinkMarkupContainer autolinks = new
>>> AutoLinkMarkupContainer("menus");
>>>
>>>   # HTML
>>>   <ul wicket:id="menus">
>>>     <li><a href="Users.html">Users</a></li>
>>>     <li><a href="Departments.html">Departments</a></li>
>>>   </ul>
>>>
>>> What do you guys think?
>>>
>>> Cheers,
>>> Bruno
>>>
>>> ***************************************************************************************************
>>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s)
>>> destinatários(s) acima identificado(s),
>>> podendo conter informações e/ou documentos confidencias/privilegiados e
>>> seu sigilo é protegido por lei. Caso você tenha recebido por engano, por
>>> favor, informe o remetente e apague-a de seu sistema.
>>> Notificamos que é proibido por lei a sua retenção, disseminação,
>>> distribuição, cópia ou uso sem expressa autorização do remetente. Opiniões
>>> pessoais do remetente não refletem, necessariamente, o ponto de vista da
>>> CETIP, o qual é divulgado somente por pessoas autorizadas."
>>>
>>>
>>> "Warning: This message was sent for exclusive use of the addressees above
>>> identified, possibly containing information and or privileged/confidential
>>> documents whose content is protected by law. In case you have mistakenly
>>> received it, please notify the sender and delete it from your system. Be
>>> noticed that the law forbids the retention, dissemination, distribution,
>>> copy or use without express authorization from the sender. Personal opinions
>>> of the sender do not necessarily reflect CETIP's point of view, which is
>>> only divulged by authorized personnel."
>>>
>>> ***************************************************************************************************
>>>
>>>
>>
>
> --
> -Wicket for love
>
> Nino Martinez Wael
> Java Specialist @ Jayway DK
> http://www.jayway.dk
> +45 2936 7684
>
>

Re: Drop wicket:link

Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
And another thing it could make autolink parser able to look in other 
packages aswell for pages... Currently theres no support for autolinking 
to pages not in the same package..

Nino Saturnino Martinez Vazquez Wael wrote:
> Hi Bruno
>
> +1 one from my side, the more of those horrible tag things we can get 
> away the better, they dont feel very wicket like anyway..
>
> And the worst thing I've even begun to use them. I just dont feel that 
> they fit into the split logic strategy..
>
> Bruno Cesar Borges wrote:
>> This might sound crazy, but what about dropping the support for the 
>> tag <wicket:link> ? :-)
>>
>> People are starting to use it frequently, and because of that, 
>> features will be requested. And then we might end with a tag library. 
>> But, to not freak everybody out, I suggest develop a markup container 
>> to do that.
>>
>> Example:
>>    # Java
>>    AutoLinkMarkupContainer autolinks = new 
>> AutoLinkMarkupContainer("menus");
>>
>>    # HTML
>>    <ul wicket:id="menus">
>>      <li><a href="Users.html">Users</a></li>
>>      <li><a href="Departments.html">Departments</a></li>
>>    </ul>
>>
>> What do you guys think?
>>
>> Cheers,
>> Bruno
>> *************************************************************************************************** 
>>
>> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) 
>> destinatários(s) acima identificado(s),
>> podendo conter informações e/ou documentos confidencias/privilegiados 
>> e seu sigilo é protegido por lei. Caso você tenha recebido por 
>> engano, por favor, informe o remetente e apague-a de seu sistema.
>> Notificamos que é proibido por lei a sua retenção, disseminação, 
>> distribuição, cópia ou uso sem expressa autorização do remetente. 
>> Opiniões pessoais do remetente não refletem, necessariamente, o ponto 
>> de vista da CETIP, o qual é divulgado somente por pessoas autorizadas."
>>
>>
>> "Warning: This message was sent for exclusive use of the addressees 
>> above identified, possibly containing information and or 
>> privileged/confidential documents whose content is protected by law. 
>> In case you have mistakenly received it, please notify the sender and 
>> delete it from your system. Be noticed that the law forbids the 
>> retention, dissemination, distribution, copy or use without express 
>> authorization from the sender. Personal opinions of the sender do not 
>> necessarily reflect CETIP's point of view, which is only divulged by 
>> authorized personnel."
>> *************************************************************************************************** 
>>
>>
>>   
>

-- 
-Wicket for love

Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684


Re: Drop wicket:link

Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
Hi Bruno

+1 one from my side, the more of those horrible tag things we can get 
away the better, they dont feel very wicket like anyway.. 


And the worst thing I've even begun to use them. I just dont feel that 
they fit into the split logic strategy..

Bruno Cesar Borges wrote:
> This might sound crazy, but what about dropping the support for the tag <wicket:link> ? :-)
>
> People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that.
>
> Example: 
>
>    # Java
>    AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer("menus");
>
>    # HTML
>    <ul wicket:id="menus">
>      <li><a href="Users.html">Users</a></li>
>      <li><a href="Departments.html">Departments</a></li>
>    </ul>
>
> What do you guys think?
>
> Cheers,
> Bruno
> ***************************************************************************************************
> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s),
> podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por 
> lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema.
> Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem 
> expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, 
> o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas."
>
>
> "Warning: This message was sent for exclusive use of the addressees above identified, possibly 
> containing information and or privileged/confidential documents whose content is protected by law. 
> In case you have mistakenly received it, please notify the sender and delete it from your system. 
> Be noticed that the law forbids the retention, dissemination, distribution, copy or use without 
> express authorization from the sender. Personal opinions of the sender do not necessarily reflect 
> CETIP's point of view, which is only divulged by authorized personnel."
> ***************************************************************************************************
>
>   

-- 
-Wicket for love

Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684


Re: Drop wicket:link

Posted by Ernesto Reinaldo Barreiro <re...@gmail.com>.
-1,

I do not use it myself but as  a user I would  hate to see something
removed just because it allows to use JSP like constructs. Anyway, a
willing user could extend markup processing to define his/her own JSP
like tags and make them work in Wicket...

Cheers,

Ernesto

Bruno Cesar Borges wrote:
> This might sound crazy, but what about dropping the support for the tag <wicket:link> ? :-)
>
> People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that.
>
> Example: 
>
>    # Java
>    AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer("menus");
>
>    # HTML
>    <ul wicket:id="menus">
>      <li><a href="Users.html">Users</a></li>
>      <li><a href="Departments.html">Departments</a></li>
>    </ul>
>
> What do you guys think?
>
> Cheers,
> Bruno
> ***************************************************************************************************
> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s),
> podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por 
> lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema.
> Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem 
> expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, 
> o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas."
>
>
> "Warning: This message was sent for exclusive use of the addressees above identified, possibly 
> containing information and or privileged/confidential documents whose content is protected by law. 
> In case you have mistakenly received it, please notify the sender and delete it from your system. 
> Be noticed that the law forbids the retention, dissemination, distribution, copy or use without 
> express authorization from the sender. Personal opinions of the sender do not necessarily reflect 
> CETIP's point of view, which is only divulged by authorized personnel."
> ***************************************************************************************************
>
>
>   


Re: Drop wicket:link

Posted by James Carman <ja...@carmanconsulting.com>.
I'd say -1.  This would be a nightmare on existing codebases.

2008/11/17 Bruno Cesar Borges <br...@cetip.com.br>:
> This might sound crazy, but what about dropping the support for the tag <wicket:link> ? :-)
>
> People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that.
>
> Example:
>
>   # Java
>   AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer("menus");
>
>   # HTML
>   <ul wicket:id="menus">
>     <li><a href="Users.html">Users</a></li>
>     <li><a href="Departments.html">Departments</a></li>
>   </ul>
>
> What do you guys think?
>
> Cheers,
> Bruno
> ***************************************************************************************************
> "Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s),
> podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por
> lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema.
> Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem
> expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente,
> o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas."
>
>
> "Warning: This message was sent for exclusive use of the addressees above identified, possibly
> containing information and or privileged/confidential documents whose content is protected by law.
> In case you have mistakenly received it, please notify the sender and delete it from your system.
> Be noticed that the law forbids the retention, dissemination, distribution, copy or use without
> express authorization from the sender. Personal opinions of the sender do not necessarily reflect
> CETIP's point of view, which is only divulged by authorized personnel."
> ***************************************************************************************************
>
>