I've a patched version working for the last two years on my demo app http://ph-jdo.appspot.com/
The multiple patches (that worked for me) hanging off of http://jira.codehaus.org/browse/XSTR-566 are not good enough for the XStream team. They'll get round to fixing the issue soon I hear. It may mean a change in constructors for XStream. Meanwhile, one of you that's able to, could fork XStream to Github (git-svn checkout) and play with permutations there until it works for you. The trick while debugging it is to wrap everything with try/catch and stream to sys-out or a logger, if not the page itself as you go through trial and error. It was a journey of discovery a couple of years ago, and has to be done on the production GAE stack, as the SDK does not (did not?) have the same permissions. - Paul On Thu, Feb 3, 2011 at 12:14 PM, Jonny <[email protected]> wrote: > Thanks, > > If I use the DomDriver in the XStream constructor I still get the > error about using restricted classes (Reflection) when in the GAE > context. When I run my unit tests with the same patched .jar - > everything is OK. > > Am I missing something? > > On Jan 26, 4:58 pm, Charms Styler <[email protected]> wrote: > > yes we do... try this outhttp:// > guice-maven.googlecode.com/svn/trunk/com/thoughtworks/xstream/... > > -- > 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=en. > > -- 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=en.
