We've heard that there is a fix for this available in Wicket 1.5.

However, we are stuck with Wicket 1.4.7 and cannot upgrade, for various
reasons. (We're also already using the AnnotationConfigWebApplicationContext
referred to in the previous post.)

Are there any other workarounds for this problem? Is it OK to make the
problem classes "implement Serializable" just to move past this issue (even
if they are injected with the @SpringBean, and are service classes), or
should we try other workarounds?

View this message in context: 
Sent from the Users forum mailing list archive at Nabble.com.

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to