Create a new component as a subclass of the component in question
(Label). In the constructor you call setEscape...(false). From then on,
only use the new subclass.
But before you do so, read the other responses :)
Regards,
Erik.
Marco Aurélio Silva schreef:
Hi all
Is there a way to set
What you are saying makes little sense. Wicket escapes and unescapes
the field value transparently, so your model object will never contain
the gt;
-Matej
On Wed, Mar 19, 2008 at 6:57 PM, Marco Aurélio Silva [EMAIL PROTECTED] wrote:
Hi all
Is there a way to set EscapeModelStrings to false
What do you mean? If wicket escapes and unescapes it on database should be
saved instead gt; ?
On Wed, Mar 19, 2008 at 3:20 PM, Matej Knopp [EMAIL PROTECTED] wrote:
What you are saying makes little sense. Wicket escapes and unescapes
the field value transparently, so your model object will
Yes. lt; should never make it into your model object.
-Matej
On Wed, Mar 19, 2008 at 7:26 PM, Marco Aurélio Silva [EMAIL PROTECTED] wrote:
What do you mean? If wicket escapes and unescapes it on database should be
saved instead gt; ?
On Wed, Mar 19, 2008 at 3:20 PM, Matej Knopp [EMAIL
Hi Marco,
do you have the ability to change the textfield creation to a factory?
You could use a creator for EscapeIgnoringTextField, wich is a call to
public static TextField createEscapeIgnoringTextField(String id, IModel model)
{
return new TextField(id,
I think the point here is not to call setEscapeModelString at all.
Unless I'm missing something the call is completely redundant in this
case and only results in invalid markup generated when user enters a
xml entity.
-Matej
On Wed, Mar 19, 2008 at 9:48 PM, Per Newgro [EMAIL PROTECTED] wrote:
