if the jetty classloader is able to load that class
then you have a wrong configuration.
Jetty shouldn't be able to load the classes at all, those classes shouldn't
be in the webapp classpath
johan
On 7/12/07, Watter <[EMAIL PROTECTED]> wrote:
Jean-Baptiste Quenot-3 wrote:
>
> * Watter:
>
Jean-Baptiste Quenot-3 wrote:
>
> * Watter:
>
>> 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
* Watter:
> 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
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 w
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
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
* 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 usi
Watter wrote:
>
>
> Jean-Baptiste Quenot-3 wrote:
>>
>> That's very interesting. It may be caused by some page
>> deserialization not using the right classloader, when Wicket pulls
>> pages out of the second-level cache. May be worth trying with
>> org.apache.wicket.util.lang.Objects.setObje
Jean-Baptiste Quenot-3 wrote:
>
> * Watter:
>>
>> Most of the time the following holds true when I reach that statement:
>>
>> Session.get().getClass().getClassLoader() =
>> org.apache.wicket.application.ReloadingClassLoader
>> FusionAuthenticatedWebSession.class.getClassLoader() =
>> org.
* Watter:
>
> Most of the time the following holds true when I reach that statement:
>
> Session.get().getClass().getClassLoader() =
> org.apache.wicket.application.ReloadingClassLoader
> FusionAuthenticatedWebSession.class.getClassLoader() =
> org.apache.wicket.application.ReloadingClassLoad
Jean-Baptiste Quenot-3 wrote:
>
> It means com.ptc.fusion.web.FusionAuthenticatedWebSession is
> already loaded in other classes that did not match the inclusion
> patterns.
>
> To debug your usecase, set a conditional breakpoint in
> ReloadingClassLoader.loadClass() when class name is
> com.pt
ptrthomas wrote:
>
> On 6/28/07, Watter <[EMAIL PROTECTED]> wrote:
> A couple of observations. Looks like you are using Acegi as well. I have
> the same problem when I don't exclude my Session and Application classes.
>
Actually, we aren't using Acegi. That class you're looking it is named
si
* Watter:
>
>
>
> Jean-Baptiste Quenot-3 wrote:
> >
> > * Watter:
> >
> >> With that, I can get past the error I reported
> >> earlier. Unfortunately, I'm seeing something else now. If I go
> >> to a page, then use my browser back button to go back a page,
> >> and then
On 6/28/07, Watter <[EMAIL PROTECTED]> wrote:
Jean-Baptiste Quenot-3 wrote:
>
> * Watter:
>
>> With that, I can get past the error I reported
>> earlier. Unfortunately, I'm seeing something else now. If I go
>> to a page, then use my browser back button to go back a page,
Jean-Baptiste Quenot-3 wrote:
>
> * Watter:
>
>> With that, I can get past the error I reported
>> earlier. Unfortunately, I'm seeing something else now. If I go
>> to a page, then use my browser back button to go back a page,
>> and then click on any other link, I get a
* Watter:
> With that, I can get past the error I reported
> earlier. Unfortunately, I'm seeing something else now. If I go
> to a page, then use my browser back button to go back a page,
> and then click on any other link, I get a ClassCastException for
> FusionAuthenticate
On 6/28/07, Watter <[EMAIL PROTECTED]> wrote:
Watter wrote:
>
> I now have a new issue. Jean-Baptiste mentions in the JIRA issue that
one
> *must* include the XxxApplication and XxxSession classes. Well, when I
> tried to do so I was unable to access my application. When I included
the
> my ve
Watter wrote:
>
> I now have a new issue. Jean-Baptiste mentions in the JIRA issue that one
> *must* include the XxxApplication and XxxSession classes. Well, when I
> tried to do so I was unable to access my application. When I included the
> my versions of those classes, I received the followin
Jean-Baptiste Quenot-3 wrote:
>
> * Watter:
>
>> Is it necessary to explicitly specify the inclusion of
>> sub-packages when the parent package is already included? I only
>> aske because our package hierarchy is pretty deep when it comes
>> to pages, and I'd loke to avoid having t
* Watter:
> Is it necessary to explicitly specify the inclusion of
> sub-packages when the parent package is already included? I only
> aske because our package hierarchy is pretty deep when it comes
> to pages, and I'd loke to avoid having to explicitly call each
> one of them out
Jean-Baptiste Quenot-3 wrote:
>
> I commented on the issue, and finally marked it as invalid. Here
> is the comment, in case you wish to discuss it on the mailing-list
> or just for the record if other users came across this:
>
> It's a bit tricky to make the reloading work with Spring. You
* Peter Thomas:
> Sure Eelco, JIRA logged: WICKET-685
>
> On 6/22/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>
> >Could you describe the problems in a JIRA issue? Thanks.
Please avoid to reply on top!
I commented on the issue, and finally marked it as invalid. Here
is the comment, in case
22 matches
Mail list logo
