Watter wrote:
>
>
> Jean-Baptiste Quenot-3 wrote:
>>
>> * Watter:
>>
>>> 1) I realized that "ContextLoader" which is the reported as the
>>> classloader when I do a Session.class.getClassloader() right
>>> before the error occurs is actually a Spring class. For some
>>> reason I was thinking that it was a standard Java class
>>> loader. I am using Spring in my application, but from the
>>> web tier, I only access my Spring beans using the approved
>>> @SpringBean annotation. Does that fact that this is a Spring
>>> class tell me anything useful?
>>
>> Do you obtain your WebApplication or your WebSession from Spring's
>> WebApplicationContext? If this is the case, that's not compatible
>> with the reloading mechanism.
>>
>> Otherwise, about the annotations, I haven't tried to work with
>> them yet. I'll test this combination during the next weeks.
>>
> I think I was incorrect in assuming this had anything to do with Spring. I
> removed Spring from the picture completely and I was still able to
> recreate the same ClassCastExceptions.
>
> Here's some additional information that may or may not be useful. The
> reason why the cast isn't working is because the stored custom WebSession
> class is from the RelaodingClassLoader but the class requesting the
> session (a page class) is using the Jetty's normal classloader. The
> question is, then, why is that page class being loaded using the normal
> classloader? Normally it isn't. In most normal situations, that page class
> is being loaded by the ReloadingClasLoader. It only seems to be loaded by
> the normal classloader after I've used my browser back button and then
> clicked the link which load it.
>
> I've also found that after making a change to page and recompiling, the
> changed page class is occasionally loaded by the normal classloader as
> well. I havent' figured out how to recreate this behavior reliably,
> though.
>
I created a small demo application that demonstrates the problem? Is there
somewhere I can upload the zip file (it uses maven so it's only 7kb) with
some instructions on the steps necessary to recreate the problem? I hate to
open a bug in JIRA for this seeing as how it's most likely a
misconfiguration error on my part and not really a bug in Wicket.
Matt
--
View this message in context:
http://www.nabble.com/Has-something-changed-in-markup-inheritance--tf3963374.html#a11552954
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
