Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 380
  • Last Modified:

Using javax.comm in Java 1.2 applets

I am trying to get access to a PC's serial ports from a signed Java applet, using the Java 1.2.2 plug-in for IE5 and the Java Comms API v2.0. I have copied the win32com.dll, comm.jar and properties file to the appropriate places for the right runtime environment on the client PC, and granted all permissions to applets signed by me. In the applet, I use getCommPortIdentifiers to get an enumerator, then use this to obtain all available serial ports. However, when the applet is loaded, the following error is reported when I execute the hasMoreElements() method of the enumerator:
"Caught java.lang.NullPointerException: name can't be null while loading driver com.sun.comm.Win32Driver"

The same code works fine when run as an application. The security setup is definitely having an effect, since I also try to read from a local file - this fails as expected when the applet is unsigned (and the comm port stuff raises a different seurity-related error, too) but succeeds when the applet is signed. Perhaps I have missed something else though.

If anyone has any ideas on how to proceed, I would be glad to hear them.

Many thanks,
Chris
0
chrisgresty
Asked:
chrisgresty
  • 2
  • 2
1 Solution
 
heyhey_Commented:
it seems that JavaComm can't configure itself.

the only thing I can suggest is to decompile the JavaComm classes and add some additional logging.

you can find the code that prints the error message inside javax.comm.CommPortIdentifier.java

try
{
    CommDriver commdriver = (CommDriver)Class.forName(s1).newInstance();
    commdriver.initialize();
}
catch(Throwable throwable)
{
    System.err.println("Caught " + throwable + " while loading driver " + s1);
}

the real problem is somewhere inside com.sun.comm.Win32Driver
0
 
chrisgrestyAuthor Commented:
Thanks heyhey_, you pointed me in the right direction. There is a problem during the static initialisation of CommPortIdentifier. During this, the following lines are executed:

loadDriver(s1);
propfilename = new String(s1);

(s1 is the javax.comm.properties file)

As part of the driver initialisation started by loadDriver, the addPortName() method is called. If there is a security manager being used, it checks the delete permission on propfilename. Which hasn't been initialised yet. Whoops.

So initialisation fails whenever you use javax.comm with a security manager.

Switching the two lines around solves this problem. I can't see any negative implications of this yet...
0
 
chrisgrestyAuthor Commented:
Heyhey_'s comments gave me a handle on the problem, and led me to find the right answer - thanks!
0
 
heyhey_Commented:
thank you :)
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now