I'm still waiting for the classloader problem to be fixed. There is no point putting this into a quickstart project since this won't reproduce the same classloader issues.
We don't yet know if it's a problem with wicket or pax wicket. Since there were no issues with 1.2, it's strange that 1.3 is suddenly broken. I can think of only two possibilities: wicket 1.2 didn't use classloaders correctly, and pax wicket compensated for this. So, when the classloader issues were fixed in 1.3, pax wicket no longer works. Or, Classloaders in 1.2 were working just fine, but were broken in the 1.3 branch. I have too many other things to do right now, and the pax wicket developer is always being put on other projects, so hasn't had time to look into this, either. Once we get the classloader problem fixed, I'll get back to this. I still have a strong suspicion that the two are related. If it's not, then I guess it would be worthwhile to create a quickstart. Thanks for checking in! On Thu, 2007-09-13 at 10:14 -0700, Eelco Hillenius wrote: > > Is there a possibility that this issue could be related to a > > classloading issue that I'm having? > > You could try to write a test case or quickstart project that shows this. > > Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
