David, We keep on eye on what seems to be blocking developers the most. We've got a few open issues for AWT:
http://code.google.com/p/googleappengine/issues/list?can=2&q=awt You'll want to star the issues as needed or create a new one with your use case in the description. On Fri, Nov 20, 2009 at 6:28 AM, David Hedley <[email protected]> wrote: > > We are currently evaluating whether to develop a series of > applications for deployment on the App Engine. However, our apps will > require Apache POI and iText (and dependent libraries) to work which > they don't currently do due to their dependence on AWT classes. > > I was wondering what Google current official policy on whitelisting > java.awt.* classes is? > i.e. one of: > a) We haven't looked at them yet. > b) We've looked at the classes and will never be whitelisting them. > c) We've looked at the classes and will be whitelisting some/all of > the classes in the near/distant future (please delete as applicable). > > Thanks > > -- > > 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 > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=. > > > -- Ikai Lan Developer Programs Engineer, Google App Engine -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=.
