private Logger log property in WebPage and Component

2011-10-14 Thread hok
Hello, the Component and WebPage classes have a private property /log/. Sometimes in Pages and Components there is a need for logging, but in this case the user have to instantiate separate logger, since the existing is not accessible. Do you think it's possible to make the logger protected, or

Re: private Logger log property in WebPage and Component

2011-10-14 Thread Bas Gooren
Out of curiosity: why would you want the component logger? If you create one locally (private static final Logger log = LoggerFactory.getLogger(YourClass.class);), you have the benefit of controlling log output since the logger is bound to the actual component and not the superclass. E.g. at

Re: NonCachingImage not showing image with GAE

2011-10-14 Thread Ian Marshall
I have solved my problem by using a class that descends from ByteArrayResource and which overrides getData(IResource.Attributes). I supply an instance of this class to my NonCachingImage instead of a model. I thank Martin Grigorov for his reply to a vaguely-related posting last month which solved

ListChoice and it's renderer

2011-10-14 Thread Hakan Steisjo
Hi All, I want to extend a simple listchoice component to also include a title attribute in the generated html code. So basically I want the option tag to be generated like this: option value=value title=titleUser display/option Can anyone give me some input on where I can add this feature to

Can not locate error messages from property messages

2011-10-14 Thread Erinc Arikan
Hi; I am using a really simple property file, to display some validation errors, it used to work fine, but it stopped working, now I can't even get the simplest example to work. and I am receiving an Could not locate error message for component: Here's the code that I am using(directly from

Re: UTF-8 not working

2011-10-14 Thread Mathias Nilsson
Sorry. Forgot to say wicket version 1.4.18 getMarkupSettings().setDefaultMarkupEncoding(UTF-8); getRequestCycleSettings().setResponseRequestEncoding(UTF-8); set in init -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/UTF-8-not-working-tp3906237p3906254.html Sent

Re: UTF-8 not working

2011-10-14 Thread Attila Király
You have to configure a filter (write one or reuse existing ones like http://static.springsource.org/spring/docs/3.1.0.RC1/javadoc-api/org/springframework/web/filter/CharacterEncodingFilter.html) to call request.setCharacterEncoding(UTF-8) before wicket gets the request. This is not needed with