Wednesday, April 30, 2014

Re: Supersourcing own clode and maintenance

On Tuesday, April 29, 2014 11:09:14 PM UTC+2, wrote:
Well, surely there are some situations where there is a workaround possible to avoid or minimize code duplication. However there are things where I can not find an option.
* What if I have a basic exception class that will use the new constructor introduced in Java 1.7 with the two booleans but I also want to use the exception classes in shared code?
* What if I want to overwrite a method like printStackTrace(PrintStream) or the like but leave it alone in GWT emul?
* What if I have a class that has has its own Java serialization based on readObject/writeObject?

Wouldn't @GwtIncompatible work for the last two?

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment