Yasudo:

I used the solution Muller has suggested and it works fine.

This problem you have is due to permissions you need to specify.
Add this line to the .java.policy file by hand or using the policytool.exe.

permission java.security.AllPermission;

You can do this just for testing objetives. You need to find the exact
permission you have to specify in order to gaing acces to library loading
when you begin to deploy your applet or you'll be leaving clues to a
security hole. If you find it let me know

If anybody knows wich permission have to be specified please let us know

thanks in advance

Marchena

----- Original Message -----
From: "H.Yasudo" <[EMAIL PROTECTED]>
To: "Christophe Muller" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, December 20, 2000 10:42 PM
Subject: Re: [OCF] Applet using javax.comm


> Thank you very much !
>
> I tried to add the code in the reference to my applet but the result is as
> follows:
>
> -- Error message --
>
> Security Exception win32com: java.security.AccessControlException: access
> denied (java.lang.RuntimePermission loadLibrary.win32com)
>
> driver initialized
>
> Security Exception win32com: java.security.AccessControlException: access
> denied (java.lang.RuntimePermission loadLibrary.win32com)
>
> Thank you
>
> ----- Original Message -----
> From: "Christophe Muller" <[EMAIL PROTECTED]>
> To: "H.Yasudo" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Wednesday, December 20, 2000 6:02 PM
> Subject: Re: [OCF] Applet using javax.comm
>
>
> > Hello,
> >
> > H.Yasudo wrote:
> > >
> > > I am testing applet using javax.comm for smartcard terminal connected
> > > serial port. While application that has same function is no problem,
> > > applet causes the error message:
> > >
> > > "Caught java.lang.NullPointerException: name can't be null while
> > > loading driver com.sun.comm.Win32Driver"
> > >
> >
> > This is due to a Comm API bug when used into a Java2 (1.2 or 1.3)
> > plugin. There is a workaround, see one of my previous post on this
> > issue: http://www.opencard.org/archive/opencard/1374.html
> >
> > There is also some good news, it's that if you can use Solaris or
> > Linux, this bug has been fixed in the latest version of Comm API (see
> > an other post: http://www.opencard.org/archive/opencard/1462.html ).
> > If you are stuck with Win$$, there is still the workaround.
> >
> > Hope it'll help.
> >
> > Cheers,
> > Christophe.
> >
> >  = "If there is a better solution... find it." -- Thomas Edison =
> > --
> > -------------------------------------------------------------
> > [EMAIL PROTECTED] - Gemplus Research Lab
> > Phone: +33 4-42-36-57-83 | Disclaimer: I don't speak for Gemplus
> > Gemplus doesn't speak for me... it is better that way!
> > -------------------------------------------------------------
> >
> >
> > ---
> > > Visit the OpenCard web site at http://www.opencard.org/ for more
> > > information on OpenCard---binaries, source code, documents.
> > > This list is being archived at
http://www.opencard.org/archive/opencard/
> >
> > ! To unsubscribe from the [EMAIL PROTECTED] mailing list send an
email
> > ! to
> > !                           [EMAIL PROTECTED]
> > ! containing the word
> > !                           unsubscribe
> > ! in the body.
> >
> >
>
>
>
> ---
> > Visit the OpenCard web site at http://www.opencard.org/ for more
> > information on OpenCard---binaries, source code, documents.
> > This list is being archived at http://www.opencard.org/archive/opencard/
>
> ! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
> ! to
> !                           [EMAIL PROTECTED]
> ! containing the word
> !                           unsubscribe
> ! in the body.
>
>


---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/

! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
!                           [EMAIL PROTECTED]
! containing the word
!                           unsubscribe 
! in the body.

Reply via email to