Start from their basic SOAP tutorial and add your project jars one by one, that's what I did... In my case just the presence of a jaxb jar was enough to screw things up. But my case was just one possibility, there could be other classes triggering this problem. GAE's security manager is very strict (probably a good thing)
On Thursday, 20 September 2012 00:03:37 UTC+12, Phil wrote: > > Thanks for your quick answer. However, I haven't any jaxb on my classpath. > I use the one of app engine. > Any other advices? > > Many thanks for your help, I really need to fix this issue. > > Le mercredi 19 septembre 2012 13:55:46 UTC+2, Emanuele Ziglioli a écrit : >> >> Have you got a jaxb jar in your classpath? >> If that's the case, you have to remove it and rely on the JRE >> implementation of jaxb. >> The GAE runtime wants you to use their jaxb and jaxws implementations. >> You can use a jaxb jar without jaxws but not toghether (the reason >> escapes me). >> I had to adapt my code (and the restlet jaxb adaptor) to do so. >> >> On Wednesday, 19 September 2012 22:11:15 UTC+12, Phil wrote: >>> >>> Any advices for fixing this issue because I got the same problem when I >>> deploy my application on google server. It works fine in local developement. >>> >>> Thanks for your feedback >>> >>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/bTBpDSIqB1gJ. 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?hl=en.
