This is a good suggestion. However, I have been working with Jini for
awhile where classes: inner and otherwise are being shipped, deserialized
and loaded cross the world, but didn't run into this one. Although
MarshalledObject wrapper
protects classes from being misinterpreted in my case.
We'll keep digging.
----- Original Message -----
From: "Robert Schweng" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 15, 2001 4:42 PM
Subject: Re: IllegalAccessError when run from Tomcat
> hi,
> could it be, it is in reason that classes over the web are interpreted
> as URIs.
> many systems could cause trouble when
> interpreting a dir path like com.class.class$innerclass
> to com/class/class?innerclass in Linux
> or on NT to com\class\class?innerclass
>
>
> cheers
> Robert
>
>
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 15, 2001 10:19 PM
> Subject: Re: IllegalAccessError when run from Tomcat
>
>
> > Good idea, I didn't realize System.getSecurityManager existed. It is
> > returning null, so there is no SecurityManager established and that
isn't
> > my problem. Anyone have other ideas? I'm pretty sure this is legal, it
> > works when not run under Tomcat, and it is 3'rd party code I'm running
so
> I
> > don't want to pull out the inner class. This is happening in JTidy.
> JTidy
> > isn't used anywhere else in Tomcat is it (in one of the standard jars)?
> Do
> > I have some wierd conflict between different versions of classes with
the
> > same name? I searched, but didn't find anything like that. Thanks for
> the
> > ideas so far - I would love some other suggestions on what to try?
> >
> > >Put:
> > >System.out.println(System.getSecurityManager()) into your program.
> > >Let us know what it says.
> > >
> > >----- Original Message -----
> > >From: <[EMAIL PROTECTED]>
> > >To: <[EMAIL PROTECTED]>
> > >Sent: Friday, June 15, 2001 11:20 AM
> > >Subject: IllegalAccessError when run from Tomcat
> > >
> > >
> > >> When running a servlet from within Tomcat I get the following
> exception:
> > >>
> > >> java.lang.IllegalAccessError: try to access field
> > >org.w3c.tidy.ParserImpl._parseHead from class
> > >org.w3c.tidy.ParserImpl$ParseHTML
> > >> at org.w3c.tidy.ParserImpl$ParseHTML.parse(ParserImpl.java)
> > >> at org.w3c.tidy.ParserImpl.parseDocument(ParserImpl.java)
> > >> at org.w3c.tidy.Tidy.parse(Tidy.java)
> > >> at org.w3c.tidy.Tidy.parseDOM(Tidy.java)
> > >> ...
> > >>
> > >> A method in the inner class $ParseHTML is trying to access a private
> field
> > >> _parseHead in the containing class, but that is legal as far as I
know.
> > >> When I move the body of this servlet to a stand alone application it
> runs
> > >> fine - no exceptions. Is there some strange JVM security manager
here
> that
> > >> is different from running as a real application? Anyone have an idea
> what
> > >> is going on?
> > >>
> >
> >
>
