Re: Wicket security and JavaMelody

2013-08-20 Thread Tommy Sadiq Hinrichsen
I ended having to write a custom JDBC Realm since i have used a salt for users passwords. import org.apache.catalina.realm.JDBCRealm; import org.apache.juli.logging.Log; import org.apache.juli.logging.LogFactory; import org.springframework.security.authentication.encoding.ShaPasswordEncoder;

problem header contribution with ajax

2013-08-20 Thread haiko
Dear wicket-users, I notice that a header contribution by a panel is not rendered in the following case. An inline CSS in the head section is first rendered by switching tabs header-contribution encoding=wicket1 ![CDATA[head xmlns:wicket=http://wicket.apache.org;script

Re: problem header contribution with ajax

2013-08-20 Thread Martin Grigorov
Hi, You cannot replace header contributions with the same HTML id attribute. Wicket checks whether the contribution is already in the page and ignores it. You can use normal Label component to be able to replace it in Ajax responses. On Tue, Aug 20, 2013 at 5:23 PM, ha...@dds.nl wrote: Dear

Re: problem header contribution with ajax

2013-08-20 Thread haiko
Martin Grigorov mgrigo...@apache.org schreef: Hi Martin, Thanks for your quick answer. You cannot replace header contributions with the same HTML id attribute. Wicket checks whether the contribution is already in the page and ignores it. Ok, that explains a lot. You can use normal

Wicket serialization concerns

2013-08-20 Thread Michael Chandler
I could use some input from some of the more experienced Wicket users out there. I'm having a hard time fully understanding when to worry about Wicket attempting to serialize domain model objects, resulting in serialization warnings/errors in the logs. I had been under the impression that if

Re: Wicket serialization concerns

2013-08-20 Thread Carl-Eric Menzel
On Tue, 20 Aug 2013 23:01:29 + Michael Chandler michael.chand...@onassignment.com wrote: I'm led to believe that creating a reference to any of my domain classes within a Wicket component (as a field or in a method implementation) will expose me to a serialization error unless I put it in