Hi all,
I'm new to wicket and just recently started to use it for a new web
app for one of our projects. Today I came across a similar issue like
described in [1], a ClassNotFoundException during deserialization of a
page. The interesting part about this in my mind is, that the
mentioned missing class was missing for a good reason: I simply
refactored a bit and renamed the class, redeployed and restarted my
Tomcat. This looks like a normal use case to me, but is something I
didn't thought of when I've read through the docs because.
My deployment is very simple: I check out a SVN working copy with a
pre-configured tag containing the whole application once and
afterwards just need to merge/update and stop/start the web
server/app.
How is deployment supposed to work in Wicket after I have refactored
or otherwise changed my classes regarding cached and serialized pages?
Is there anything I need to tell wicket to clear its caches on each
deployment or ignore those or whatever? Am I forced to not delete once
deployed classes for a fair period of time? That would be a litte
nightmare... Or is there any other issue I ran into I should have
avoided?
Obviously others do deploy their Wicket apps as well, so I hope you
have some input on how to avoid the problem I've ran into. Thanks!
The important parts of the stacktrace:
java.lang.ClassNotFoundException:
de.am_soft.util.frontend.wicket.markup.link.LogoutLink
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1720)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at
org.apache.wicket.application.AbstractClassResolver.resolveClass(AbstractClassResolver.java:108)
at
org.apache.wicket.serialize.java.JavaSerializer$ClassResolverObjectInputStream.resolveClass(JavaSerializer.java:218)
at java.io.ObjectInputStream.[...]
[...]
at
org.apache.wicket.serialize.java.JavaSerializer.deserialize(JavaSerializer.java:122)
at
org.apache.wicket.pageStore.DefaultPageStore.deserializePage(DefaultPageStore.java:396)
at
org.apache.wicket.pageStore.DefaultPageStore.getPage(DefaultPageStore.java:135)
at
org.apache.wicket.page.PageStoreManager$SessionEntry.getPage(PageStoreManager.java:203)
at
org.apache.wicket.page.PageStoreManager$PersistentRequestAdapter.getPage(PageStoreManager.java:360)
at
org.apache.wicket.page.AbstractPageManager.getPage(AbstractPageManager.java:107)
[1]: https://issues.apache.org/jira/browse/WICKET-4785
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
