Hi Guillaume, I am *not* speaking about GWT but of the App Engine on the server site. iText had the same issue with java.awt.Color and some other classes and finally they removed the dependency to run on GAE/J [1]. So clearly my answer was not about JavaScript and Swing because I would like to generate ODF on the GAE site.
Regards, Chrustian [1] http://sourceforge.net/tracker/?func=detail&aid=2810312&group_id=15255&atid=365255 On 16 Mai, 22:43, Guillaume Maillard <[email protected]> wrote: > Hi, > > I think you missunderstood the GAE compatibility tool goal, > it checked if jOpenDocument can be compiled to JavaScript by > the Java -> JavaScript compiler from google in order to be executed > by the browser localy. > > To remove swing related parts will not solve the issue, > running in the browser is a bad idea for a library which needs > access to files and which performs a lot of processing. > > Using jOpenDocument as-is at the server level is working fine, > as any Java library. > > Regards, > Guillaume > > 2010/5/16 Christian <[email protected]> > > > Title says it all :) > > >http://www.ltech.com/google-app-engine-java-compatibility-analyzer.html > > reveals that jOpenDocuments relies on quite a few forbidden Swing > > classes preventing to use it on GAE/J. I would like to see a split in > > a core.jar component for OpenDocument modification and another jar for > > the viewer. > > > Thanks for your great work > > > Chris
