Hi Jens,
the reason for the failures are clear: The sandbox strikes back.
Different browsers impose different restrictions on the execution of
unsave operations. But again, there is not enough info to tell exactely
what's happening. To give concrete advice, I need to know more: Which in
the the successful case broser? How are the additional classes (mysql.*)
loadded (locally or via the network)?
There are only two hints I can give you blindly:
1) with appletviewer, it is possible to change the security
restrictions. Try to make them more restrictive untill you get a simular
error as in the browsers. Expecially try to forbid to open network
connections to hosts other than the one the applet was loaded from.
2) With Netscape Navigator, open the Java console
(Communicator/Tools/Java Console) before executing the applet. The stack
dump from the Exception will show in it. This way, you can find out
about the line number where the error occurs.
Matthias
"Neumann, Jens" wrote:
>
> Hi Matthias
>
> thanks for your quick response. I tried some things in between and the
> problem moved. My Applet is connecting to a database using port 1114 and
> using mslqjava 1.2.8.
> I found the right place to locate the classes and comilation works fine. I
> copied the Applet1.class file and another Applet1$SymAction.class on my web
> server and made a test2.html.
>
> I checked the rights (755) and it's nop problem to run the applet on some
> machiones. Other computers with the same Browser fail with an security error
> (IE says:" com.ms.security.SecurityExceptionEx(Apllet1.init)" and Mozilla
> says:"Applet Applet1 can't start: class Applet1 got a security violation:
> method verification error"
>
> I don't see the reason for the different result with different machines? Do
> you or somebody else know this problem?
>
> Thanks for your help.
>
> Jens
>
> Jens Neumann
> Senior Support Engineer
>
> Digi International AG
> (formerly ITK AG)
> Joseph-von-Fraunhofer-Str. 23
> 44227 Dortmund
> Germany
>
> Tel.: +49-231-9747-250
> Fax: +49-231-9747-777
> Email: [EMAIL PROTECTED]
>
> > -----Original Message-----
> > From: Matthias Pfisterer
> > [SMTP:[EMAIL PROTECTED]]
> > Sent: Tuesday, June 22, 1999 4:15 PM
> > To: Neumann, Jens
> > Cc: '[EMAIL PROTECTED]'
> > Subject: Re: msqljava implementation
> >
> > Hi Jens,
> >
> > let me say that you made the typical beginner's error. I don't mean your
> > problem with java or linux - all of us have such problems from time to
> > time, even experts. The real error is to not give us enough information
> > to help you. Perhaps you just made a typo when setting the CLASSPATH: we
> > cannot find out if we do not know exactely what you did.
> >
> > So please give the exact commands that you used: the working ones and
> > the not-working ones. Tell us what shell you are using. Give us the
> > exact error messages. And, check on your system that the user-id the
> > java VM is running under has the permissions to read the archive you
> > want to add. Check the jar file if it really contains the classes you
> > think it does.
> >
> > Matthias
> >
> >
> > "Neumann, Jens" wrote:
> > >
> > > Hi all
> > >
> > > I'm going to develop a jdbc cleint applet for a msql database in my
> > company.
> > > The lib of msqljava wants me to add it to the classpath (so I created
> > one).
> > > When I try to compile written code the "import msql.*;" is not accepted,
> > > because it's not found. I tried the classpath extension of the javac but
> > now
> > > I'm able to import msql.* only. How to add foreign classes to the
> > system.
> > > Even if I know that I'm asking beginner questions I hope one of you'll
> > send
> > > me an answer. I tried 1.2pre and 1.1.7 v1a, but it's the same with both
> > > packages.
> > >
> > > Thanks for your help.
> > >
> > > Jens
> > >
> > > ----------------------------------------------------------------------
> > > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > > with a subject of "unsubscribe". Trouble? Contact
> > [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
