Sure would be nice if appengine would decide to support awt - it would solve this problem and many others. (Vote for it here http://code.google.com/p/googleappengine/issues/detail?id=1423). However, my impression is that they have no intention to do so any time soon - it must cause some significant problems for their infrastructure.
Someone apparently got iText to run in app-engine http://groups.google.com/group/google-appengine-java/msg/419faf63fff47ef7 and there was an issue posted to itext on sourceforge, but I can't seem to access the itext project there anymore - perhaps they moved? https://sourceforge.net/tracker/?func=detail&aid=2810312&group_id=152 On Sep 4, 1:33 am, Grzegorz Borkowski <grzegorz...@gmail.com> wrote: > Do you know if JasperReports developers are aware of this problem? Is > there any bug reported to them? I haven't found any on myself. > Logically, JasperReports (nor iText) shouldn't depend on AWT classes, > so this dependency is a bit strange, and perhaps can be fixed by them. > > On Sep 4, 12:16 am, bgood <ben.mcgee.g...@gmail.com> wrote: > > > > > We had the same problem but ended up hosting the report generator on a > > separate server. If you figure it out, please post here about how to > > do it! Its really the only critical piece of our code that we can't > > move into this particular cloud. Its the only reason we are > > considering alternative hosting services right now. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---