On 2002.06.08 07:50 John Wilson wrote:
>
> > System.getProperty
> >
> > also always throws and prints in IE so that causes more problems in
> > applets.
>
> Jim,
>
> Would explicitly catching the exception help?
I'm working from memory, but my recollection is that it prints an
exception in the IE Java console (== tech support call) regardless of
whether you catch it or not.
>
> 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.
There are a couple of places where the change seems to make little
sense except for consistency, for example, Vector->ArrayList in
WebServer.
Looking through the patch, the following occurs to me. You've already
created the AggregateFactory class, would it be possible to create:
interface MapInterface {
put
get
}
interface ListInterface {
add
get
}
(OR whatever). Then return a concrete implementation from
AggregateFactory. In 1.1 the implementation is a trivial subclass of a
Hashtable and Vector. In Java2, Map and List. Then the
AggregateFactory could be switched to change implementations.
I don't, however, have a good suggestion for Iterators and Enumerations.
Jim
--
Jim Redman
(505) 662 5156
http://www.ergotech.com
