I'm trying to convert an existing AppEngine app that uses org.restlet as transport to use cloud endpoints. I was planning on moving to endpoints to gain better access to authenticated users specifically from Android devices. But I'm finding that the endpoint tooling doesn't play very nicely with Maven and could use some pointers on making it less tedious.
In particular with org.restlet I defined my server interfaces in projectA, app engine implementation in projectB and Android client impl in projectC. All cleanly separate. But with the endpoint tooling: 1) It assumes that the engine app is in a folder called 'war' 2) It requires all classes declared in the method signatures to have their source in the app engine project (they can't be contained in a dependent jar). 3) Creates a client ?project? library embedded in the war/web-inf folder of the engine server app which contains source, dependencies, proguard config and needs to be cut out of the server app and added to the client app. 4) Maybe I missed this but I couldn't see a way to force params into the request body instead of being part of the URL.. Does someone have a good example project that uses Maven to build using endpoints? What Maven plugins are people using. I have been using net.kindleit:maven-gae-plugin to date, but it looks close to abandoned now and doesn't support endpoints. appengine-maven-plugin looks newish and pretty clean (doesn't support the endpoint tooling) maven-endpoint-plugin generates the server api descriptor but not any of the client classes. William -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
