You were absolutely right, Sven! Now, my unit tests pass and I can launch
my app. But amongst some minor problems, I have this exception in my
start-up logs:
java.lang.NoClassDefFoundError: org/apache/wicket/request/Request
at java.lang.Class.getDeclaredMethods0(Native Method)
at
You're missing the wicket-request jar.
Sven
On 03/20/2012 08:38 PM, Pierre Goupil wrote:
You were absolutely right, Sven! Now, my unit tests pass and I can launch
my app. But amongst some minor problems, I have this exception in my
start-up logs:
java.lang.NoClassDefFoundError:
No, I have it as a transitive dependency in my POM, so it is in my
classpath.
Thanks for the quick assistance!
Regards,
Pierre
On Tue, Mar 20, 2012 at 9:57 PM, Sven Meier s...@meiers.net wrote:
You're missing the wicket-request jar.
Sven
On 03/20/2012 08:38 PM, Pierre Goupil wrote:
Good evening,
I'm currently in the process of migrating my app from Wicket 1.4 to Wicket
1.5. I've read the migration guide and everything seems to go fine, except
for session management.
Here's my code:
public class MySession extends WebSession
{
public static MySession get()
{
On Sun, Mar 18, 2012 at 5:08 PM, Pierre Goupil goupilpie...@gmail.comwrote:
Good evening,
I'm currently in the process of migrating my app from Wicket 1.4 to Wicket
1.5. I've read the migration guide and everything seems to go fine, except
for session management.
Here's my code:
public
Yes, absolutely:
public Session newSession(final Request request, final Response
response)
{
return new MySession(request);
}
On Sun, Mar 18, 2012 at 10:32 PM, Jeremy Thomerson
jer...@wickettraining.com wrote:
On Sun, Mar 18, 2012 at 5:08 PM, Pierre Goupil
Put a breakpoint in the WebSession constructor and see where it's getting
called.
Or, perhaps you won't see anything there if this is happening because you
are in a serialized WebSession. You can test that by clearing all cookies,
etc, and starting a new session.
--
Jeremy Thomerson
Actually, this error occurs in my unit tests. I can't launch the app at
this very moment, because some more things need to be managed during the
migration. But this simple test should work as it all compiles.
As expected, the constructor from WebSession is called by
Perhaps a classloader issue? Check whether you have two Wicket versions
in your project.
Sven
On 03/18/2012 10:56 PM, Pierre Goupil wrote:
Actually, this error occurs in my unit tests. I can't launch the app at
this very moment, because some more things need to be managed during the
