Tuesday, October 30, 2012

Re: GWT 2.5 Java 5 runtime(!) compatibility

Yes, for build-time this makes absolute sense - however applying the same constraint on the server runtime (where gwt-servlet is needed as a dependency to host GWT-RPC services and such) appears unnecessary and artificial.

Effectively this is shutting out alot(!) of enterprise adopters from GWT 2.5 (and possibly later) - since they are usually not as quick to upgrade their servers.
For instance we are still stuck with Websphere 6.1 (running on a IBM Java 5 VM), with no current upgrade path.

Am Dienstag, 30. Oktober 2012 14:56:57 UTC+1 schrieb Samyem Tuladhar:
This was part of the plan and set as a requirement for GWT 2.5: https://developers.google.com/web-toolkit/gettingstarted

On Tuesday, October 30, 2012 9:40:12 AM UTC-4, Lars Ködderitzsch wrote:
Hi all,

while trying to upgrade to GWT 2.5 I noticed that all jars (incl. gwt-servlet.jar) are now build with target 1.6 (class file version 50.0).

This removes ability to host a GWT application on older application servers (e.g. Websphere 6.1).
While I understand that at least at build time during GWT-compile Java 6 is a requirement, I don't understand this restriction on the runtime environment.

Can somebody from the team please shed some light if this is intentional (if so why?) or just an oversight, which would be fixed in subsequent releases?


You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/wmDY9ARYoNMJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

No comments:

Post a Comment