[Trustedjava-support] Unhanded "RemoteException" causing null pointers.

[Michael S. <ms...@nt...>]

In "iaik.tc.tss.impl.java.tsp.tcsbinding.soapservice.TcTcsBindingSoap" 
and possibly other places you use an idiom of

     } catch (RemoteException e) {
       ConvertRemoteExceptions.convertTcTcsException(e);
       ConvertRemoteExceptions.convertTcTddlException(e);
       ConvertRemoteExceptions.convertTcTpmException(e);
       return null;
     }

to catch remote errors and turn them into local errors of an appropriate 
type.  For some reason, I keep finding cases that as far as I can tell 
are causing RemoteExceptions where the underlying cause is not 
TcTcsException, TcTddlException or TcTpmException and which result in 
the call returning a null object.  That then causes an NPE the next 
layer up when it trys to extract the error code value.   I'd suggest 
replacing "return null" with something that returns


My most recent one was a simple attempt to try and retrieve TPM status bits.

"tpm.getStatus (TSS_TPMSTATUS_DISABLED)"

I'm running this on a Lenovo Thinkpad T500 with an Atmel chip.   I'm 
using SOAP because I can't seem to get the direct thing to work.  Going 
to try that again.

JDK is 1.6.0_17 for various reasons.  I've tried others without much 
success.  I'm using the pre-compiled v0.7 of jTSS.

Mike