#2 I'm not too sure about - doesn't calling getClientInfo() cause a
redirect to
a temporary page to collect that information?
No, this info will be extracted from the User-Agent header. The extended
info like browser dimensions are extracted with the special page.
So, I call
@wicket.apache.org
Subject: Re: Wicket/Spring Boilerplate
Hi,
Thanks for sharing it!
Here are some ideas:
https://github.com/limone/wicket-spring-boilerplate/blob/master/src/main/resources/archetype-resources/src/main/java/HomePage.java#L25
Better override #renderHead(IHeaderResponse response) and use
On 03/01/2012 02:07 AM, Michael Laccetti wrote:
Just a quick note to folks that may be interested that I've created a Maven
archetype that ties together Wicket 1.5 and Spring 3.1, along with Hibernate
4.1/JPA 2 and logback. It is purely annotation driven, and has no XML
configuration files.
Michael, I have an app on wicket 1.4.x, spring 2.5.x and *non-JPA* hibernate
3.5.x. Without taking wicket or other API changes into account, can you
suggest whether or even how this archetype could be helpful in migrating to
1.5/3.1/4.1 and perhaps JPA later on? I wouldn't want to migrate to
to the servlet 3 annotation, it worked. I'd love to back
this one out, as it forces a servlet 3 container.
Mike
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: March-01-12 2:51 AM
To: users@wicket.apache.org
Subject: Re: Wicket/Spring Boilerplate
Hi
Hi,
Thanks for sharing it!
Here are some ideas:
https://github.com/limone/wicket-spring-boilerplate/blob/master/src/main/resources/archetype-resources/src/main/java/HomePage.java#L25
Better override #renderHead(IHeaderResponse response) and use
'response.renderXYZ()'
