>
>On Monday 18 October 2004 18:29, Andrew Evers wrote:
>> The use of these types comes from our desire (and our users desire)
>> to work with Java 1.1, often in Applets in a web browser. This
>> unfortunately means that the more abstract collections framework
>> introduced in 1.2 is not availabl
On Monday 18 October 2004 18:29, Andrew Evers wrote:
> The use of these types comes from our desire (and our users desire)
> to work with Java 1.1, often in Applets in a web browser. This
> unfortunately means that the more abstract collections framework
> introduced in 1.2 is not available.
IMHO
Oded,
I needed more flexibility too.
I just created my own XmlWriter implementation and modified XmlRpc to use a class
specified at runtime.
Modify XmlRpc.java - Add the following 3 methods and a static member (xmlWriterClass)
//++ START CODE SNIPPET +
/** ***
Hello,
>we do want to keep the current API, and the majority of
work is being done in other areas (use of Apache commons
components for example)
Aha, does this include the integration of HttpClient?
Best Regards,
Sven
Hi Oded,
The use of these types comes from our desire (and our users desire) to work with Java
1.1, often in Applets in a web browser. This unfortunately means that the more
abstract collections framework introduced in 1.2 is not available.
While Collection has a toArray() method, Vector (or ma
