Tuesday, August 28, 2012

Re: GWT 2.5 and IBM JVM problems



On Tuesday, August 28, 2012 1:45:42 PM UTC-7, Thomas Broyer wrote:


On Tuesday, August 28, 2012 10:17:41 PM UTC+2, Daniel Kurka wrote:
I still don`t really get the issue since this is only an issue while developing GWT (am I right?)

As far as I know the jars we are packing (gwt-servlet,...) do not depend on a certain JVM. 
Can people who need an IBM JVM running for their servers not simply use the -noserver option with an Oracle JDK?

No, it's an issue when compiling with the GWT Compiler while processing the gwtar files packaged in the gwt-user.jar (see issue 7530).
And the Oracle JDK is apparently not an option on some OSes (see the thread in gwt-steering)
Moreover, the fix seems to be rather simple: follow java.io.Serializable contract and provide an explicit serialVersionUID (and make sure we change it whenever we modify the classes)

I talked to Ray a bit about this. We'd like to avoid setting serialVersionUID manually since it's another maintenance chore and we're sure to forget. We aren't doing long-term persistence, so the default way that serialVersionUID works should ensure that we rebuild gwttar whenever necessary. But perhaps this needs to be rebuilt when using IBM's JDK?

I also don't understand why removing the gwtar file doesn't solve the problem. Something else is going on.

- Brian

--
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/-/mL20gbO7f2AJ.
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