Author Topic: Why the need for Java 6 for the Java API? (Read 7825 times)

gwieser · « **on:** May 22, 2007, 05:33:48 am »

hi,

tried the java api today and found that class version problem when using java 5.

is there any good reason why the java api needs to run under java 6? java 6 is brand new, and most of the big projects run java 5, some even 1.4. would be cool to get a version that runs under at least java 5....

btw: the html report generation is so quick when using the java api, we thought that it didn't work because it took less than a second to generate what usualy takes a minute within the GUI.

br,
günther

mikewhit · « **Reply #1 on:** May 22, 2007, 08:07:01 am »

Yes, unless it's essential you should usually 'write down' to a low common denominator such as Java 1.3 rather than 'writing up' to the latest and greatest version.

Especially for a 'run anywhere' app ...

gwieser · « **Reply #2 on:** May 22, 2007, 08:11:16 am »

hi mike,

just in case i got something wrong: do you refer to programming java in general, or do you respond to what i explained in my posting, that the java api provided by EA since 6.5 is in java 6 and creates problems when using with lower versions in java?

br,
günther

Eve · « **Reply #3 on:** May 22, 2007, 01:38:53 pm »

The Java API requires Java 1.5 because it uses generics and enumerations. It's an unfortunate error that it was compiled for Java 1.6 instead of 1.5.

gwieser · « **Reply #4 on:** May 22, 2007, 10:43:06 pm »

Quote

The Java API requires Java 1.5 because it uses generics and enumerations. It's an unfortunate error that it was compiled for Java 1.6 instead of 1.5.

that's good news! I guess with the next release, the Java API will run using 1.5, right?

Is there a chance to get a version for the current EA release that run's under 1.5? We would really appreciate that as we want to automate several tasks (e.g. report generation).

br,
guenther

gwieser · « **Reply #5 on:** June 19, 2007, 10:58:35 pm »

Tried the EA 7.0 beta today, and still the Java API is limited to a Java 6 runtime env.

May I ask someone from Sparx Support to confirm that in final 7.0 the API will be usable with Java 5? This is important information for us, as we can use Java 5 in our project but NOT Java 6. So if it would stay in Java 6 we won't use the Java API.

«Midnight» · « **Reply #6 on:** June 20, 2007, 02:22:19 am »

Guenther,

I strongly suggest you submit a beta bug report - use the link on the beta download page - regarding this. Such reports go directly into the Sparx hopper, and you need action quickly before Java 6 gets embedded into the product, assuming there is still time...

David

gwieser · « **Reply #7 on:** June 20, 2007, 04:01:01 am »

a real newbie question:

unfortunately there is no beta bug report for the 7.0 beta. should i post this beta bug using the 6.5 beta bug form?

«Midnight» · « **Reply #8 on:** June 20, 2007, 04:11:45 am »

No.

The link to the beta bug report page in on the download page for beta (or perhaps on the announcement page in the Latest News section of the forum.)

gwieser · « **Reply #9 on:** June 20, 2007, 05:08:04 am »

found out that there is already a beta 2 of version 7.0 out, which SHOULD habe java 1.5 for the java api.

i'll check that and post the results.

gwieser · « **Reply #10 on:** June 20, 2007, 05:15:35 am »

tested beta 2, works fine now with java 5.

thanx, guys!

«Midnight» · « **Reply #11 on:** June 20, 2007, 07:58:24 am »

We have a winner!

For all those who wonder why we choose EA versus <insert competing product of the week>, this is the sort of responsiveness that we can get.

Of course, we need to work more with Sparx to propagate this troughout the product...

David

Eve · « **Reply #12 on:** June 20, 2007, 01:03:17 pm »

Beta 1 of version 7 was released two days before this thread. So unfortunately it missed getting the Java API compiled for 1.5.

Sparx Systems Forum

News: