Re: jEuclid-problem

Andreas L Delmelle a écrit :
> On Mar 8, 2007, at 22:02, Thomas Zastrow wrote:
> 
> Hi Tom,
> 
>> Andreas L Delmelle schrieb:
> <snip />
>> Andreas, thank you for your help 
> 
> You're welcome, of course.
> 
>> I'm not sure if I can help something, I have some Java-experience but
>> don't want to mess up other's work.
> 
> If you really want to help, all that needs to be changed/updated is the
> class org.apache.fop.mathml.MathMLElement (located in
> examples/mathml/src, to restore compatibility with the latest JEuclid.
> 
> It only seems that JEuclid, in one of the last releases, has begun
> targeting Java 1.5 as a minimum. I can't say for sure whether no other
> problems will arise. FOP and Batik both still have a minimal target JVM
> of 1.3 (release FOP 0.93 / Batik 1.6). For FOP this should be 1.4 by the
> next release. This means we can't use Java 1.5 features like generics or
> typesafe enums internally in FOP, and I'm not sure whether the MathBase
> constructor will accept a standard Map, which would resolve to:
> Map<Object, Object>

That should be ok. You would have to use Java 1.5 to run FOP with
Jeuclid. You can use a non-generic map in the FOP code, you will only
get warnings from the compiler about non-typesafe checking. But the code
would still run.

> If this latter issue is only minor, and the updated MathBase constructor
> also accepts non-generic Maps, then updating the extension should prove
> to be a cake-walk. If the issue cannot be overcome, then I'm afraid this
> means that either:
> a) for the time being, FOP will remain incompatible with the latest
> JEuclid versions
> b) the need may arise for a separate MathML extension that is written in
> Java 5

Good luck!
Vincent