"John Wilson" <[EMAIL PROTECTED]> writes:
> ----- Original Message -----
> From: "Jim Redman" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, June 08, 2002 2:39 PM
> Subject: Re: Dictionary vs. Hashtable in XmlRpc.java
>
>
>> System.getProperty
>>
>> also always throws and prints in IE so that causes more problems in
>> applets.
>
> Jim,
>
> Would explicitly catching the exception help?
That's what's been done in at least some of the client code. A
default value is used instead of the System property. Adding a method
like the following to the XmlRpc class would encapsulate this behavior
nicely:
protected String getProperty(String name, String defaultValue)
{
try
{
return System.getProperty(name);
}
catch (SecurityException useDefault)
{
return defaultValue;
}
}
> It's possible that using java.util.Map, etc. screws JDK 1.x applets anyway.
> I seem to remember that applet jar/zip files could not contain java.*
> classes because of security issues. In which case packaging a subset of the
> Java 2 Collections classes with the applet would not work.
That's correct. However, the separate Collections package is in the
com.sun domain. Don't know if it suffers from the same issues or
not. This discussion is good stuff.
- Dan
