Re: [OpenMap Users] jdk 1.1 - conversion of current release

HI Lior,

On Apr 19, 2004, at 8:36 AM, Lior Graf wrote:

> Hi,
>
>  
>
> I asked about using openamp with JDK 1.1, and was told that I can use
> earlier versions of openmap (the last one supported is openmap 3.7).
>
>  
>
> My question is, whether it is a consuming task to convert the current
> release of openmap to work with JDK 1.1? can u estimate how much
> effort I should put in that in order for that to run under JDK 1.1?

The rendering of the OMGraphics depends on the Java 2D API, so that
would have to be modified. All the OMGraphic stuff that deals with
java.awt.Shape objects would have to be removed and reverted back to
jdk 1.1. The BeanContext package isn't a part of jdk 1.1, so the
MapHandler won't compile, which breaks all the application component
connections and the basic framework. You might be able to create a jdk
1.1 version of the jdk 1.2 beans (with additional classes over 1.1.8)
and beancontext packages to make that work.

Then there's all the stuff added to java.util that is used throughout
OpenMap since 3.7, like Lists, Iterators, etc. All that would have to
be re-implemented in a jdk 1.1 fashion where it appears. That's
probably the hardest part of the retro-fit.

You'll need Swing, too.

> The reason I am asking is that I would still like to enjoy future
> releases/enhancements of openmap, and I don't want to limit myself to
> version 3.7

We don't take jdk 1.1 compatibility into design and coding
considerations for future releases, so this process would have to be
repeated for every release if you wanted to pursue this.

The easiest thing to do might be to implement jdk 1.2 classes for your
jdk 1.1 implementation for some things. Either way, I think this is a
really big job, retro-fitting 3-4 years of code changes into a more
limited runtime environment.

- Don

--
[To unsubscribe to this list send an email to "majdart@bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]