search

dkuspawono / google-plugin-for-eclipse

Automatically exported from code.google.com/p/google-plugin-for-eclipse
Eclipse Public License 1.0
0 stars 0 forks source link

Clound Enpoints generation is down #117

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
There have been some changes with the generation of could endpoints that will 
cause a connection android project to have errors.  The package name in the 
generated file is incorrect which an extra "com.google.api.services" being 
prefixed to the package name.

The current workout for this is to modify the package path of the generated 
libraries to match up with how they are referenced in the android project.

The GPE team is aware of this issue and is working on updating to account for 
this change in the generator.  A fix is expected next week.

Original issue reported on code.google.com by a...@google.com on 12 Apr 2013 at 7:46

GoogleCodeExporter commented 8 years ago 
A workaround has been pushed server-side for this, so the problem should be 
fixed (for now). 

However, if you're using App Engine 1.7.7, there's a bug that we'll need to fix 
with a new version of GPE (will go out early next week). In the Android GCM 
code that is generated when creating an App Engine backend or generating a new 
Android Connected App Engine proejct, there are errors that appear. 

To work around them, the best approach is to use App Engine 1.7.5 or App Engine 
1.7.6 for now. With the new version of GPE next week, we'll put out a version 
that works with App Engine 1.7.7 (and breaks compatibility with previous 
versions of App Engine for Endpoints).

Another way to work around the problem is to take the problematic call and fix 
it like so:

Old code:

 // Works on 1.7.5, 1.7.6, broken on 1.7.7
 messageEndpoint.listMessages().setLimit(5).execute();
 endpoint.getDeviceInfo(registration)  

New code:

 // works on 1.7.7
 messageEndpoint.messgageEndpoint().listMessages().setLimit(5).execute();  
 endpoint.deviceInfoEndpoint().getDeviceInfo(registration)

Sorry about the breakage...

Original comment by rdayal@google.com on 12 Apr 2013 at 11:41

GoogleCodeExporter commented 8 years ago 
It works! :-) Thank you so much - As a student I benefit most of the 
cloudendpoint service

Original comment by shirsche...@gmail.com on 13 Apr 2013 at 6:10

GoogleCodeExporter commented 8 years ago

Original comment by rdayal@google.com on 15 Apr 2013 at 3:37

GoogleCodeExporter commented 8 years ago 
This issue has not been fixed. I am still experiencing mismatch due to the 
prepended "com.google.api.services". I have experiencing the issue with both 
new projects (blank projects) and old projects.

Original comment by leslyel...@gmail.com on 24 Apr 2013 at 10:12

GoogleCodeExporter commented 8 years ago 
I have just encountered this problem for the first time.  I'm using Eclipse 
4.2.2 on Windows.  Since encountering the problem I've upgraded from SDK 1.7.7 
to 1.7.7.1 (and regenerated and re-built everything) but the problem remains 
the same.

To be clear, my problem is not in the referencing of the package, but an error 
on the package declaration.  It is confusing because the declared package looks 
like it is correct (matches the actual package):

package com.google.api.services.<my endpoint path>.<endpoint name>;

Eclipse reports that the declared package does not match the expected package 
"".

Note the empty quotes at the end - Eclipse appears to be confused about the 
expected package name.

Original comment by t...@malcolmson.ca on 25 Apr 2013 at 6:33

GoogleCodeExporter commented 8 years ago 
Any heads up on when the Release-3.2.3 will available on the eclipse update 
site?

The version that I see from the Eclipse > Help > Install New Software > Google 
Update Site for Eclipse 4.2 > Google Plugin for Eclipse 4.2, still says 
3.2.2.v201303261859-rel-r42.

Original comment by dostihar...@gmail.com on 26 Apr 2013 at 10:16

GoogleCodeExporter commented 8 years ago

Original comment by rdayal@google.com on 26 Apr 2013 at 8:15

GoogleCodeExporter commented 8 years ago 
GPE 3.2.3 was not visible on Eclipse update when I looked a few hours ago, but 
you can download it and install it from here:

https://developers.google.com/eclipse/docs/install-from-zip

I have GPE 3.2.3, plus GAE/J SDK 1.7.7.1, and all is working. You will have to 
make changes to your code regarding the new package names for the endpoint 
classes, and there's a new function in the endpoint service to get the endpoint 
itself (instead of having endpoint calls directly in the service).

Original comment by einnoc...@gmail.com on 27 Apr 2013 at 3:52

GoogleCodeExporter commented 8 years ago 
Thanks Number 8. Seems like, some more hacking is required to bring Order to 
Chaos. :-)

Original comment by dostihar...@gmail.com on 27 Apr 2013 at 7:20

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I've upgraded to 3.2.3 and 1.7.7.1, modified my import paths, and rebuilt 
everything, and have one rather peculiar problem remaining: the generated code 
for one of my endpoints looks like this.

Class Endpointname {

  // 1st endpoint method - as expected
  public void sendData( ... );
  class SendData { ...

  public static class Builder { ... }

  // 2nd endpoint method is inside this inner class??
  class Endpointname {
    public void sendData2( ... );
    class SendData2 { ... }
  }
}

There is one thing different about my declaration of sendData2: the first 
parameter is HttpServletRequest.  This is fine and has worked for me before - I 
mention it because this problem has only occurred with this one endpoint method.

Original comment by t...@malcolmson.ca on 28 Apr 2013 at 1:02

GoogleCodeExporter commented 8 years ago 
@einnocent: If you generate a new backend for an existing Android app, you will 
not have to tweak any package names/etc. If you'd like to fix up an existing 
App Engine backend, you will have to do some tweaking. For the latter case, I'd 
recommend the following:

1) Create a new Android Project with a root package that matches that of your 
existing Android project. 

2) Select that project, right-click on it, and generate an App Engine backend 
for it with App Engine 1.7.7.

3) Copy the DeviceInfoEndpoint.java and the MessageEndpoint.java classes from 
the new App Engine project over to your existing project (replacing the 
existing classes, unless you had some custom code in there).

4) Right-click your existing App Engine project and select "Generate Cloud 
Endpoint Library".

5) Now, in the new Android project, select the GCMIntentService.java and the 
RegisterActivity.java classes and copy them into your existing App Engine 
project (replacing the the existing classes, unless you had some custom code).

Notice the new annotations at the top of the DeviceInfoEndpoint.java and 
MessageEndpoint.java classes. They were first introduced in App Engine 1.7.7, 
and give a degree of predictability to the resulting package structure in the 
generate client libraries.

Original comment by rdayal@google.com on 30 Apr 2013 at 3:09

GoogleCodeExporter commented 8 years ago 
When Google is coming up with the stable GAE SDK and GPE? So that everything 
would be fine with the Hello World App of App engine Connected Android project.

Original comment by adeshato...@gmail.com on 28 May 2013 at 1:10

GoogleCodeExporter commented 8 years ago 
I am sorry for all of the jitter; things are finally stabilizing as both GPE's 
Endpoints integration and GAE's endpoints functionality are becoming more 
concrete. Are you still running into problems?

Original comment by rdayal@google.com on 28 May 2013 at 8:01

GoogleCodeExporter commented 8 years ago 
Hi rdayal,
Still i'm facing problem while creating Google Cloud EndPoints Library and i'm 
using GAE 1.8.4.

Original comment by shaikanj...@a-cti.com on 8 Nov 2013 at 7:13

GoogleCodeExporter commented 8 years ago 
What error are you seeing?

Can you go to Window -> Show View -> Error Log and let me know what you're 
running into?

Original comment by rdayal@google.com on 8 Nov 2013 at 7:15

GoogleCodeExporter commented 8 years ago 
Hi randyal,
Thanks for quick response it's showing like "could not check whether the launch 
configuration 'EndPoints' needs the -XstartOnFirstThread argument, assuming it 
does" plugin : com.google.gdt.eclipse.appengine.swarm, 
com.google.gwt.eclipse.core in these two plugin's it is showing errors.

Original comment by shaikanj...@a-cti.com on 9 Nov 2013 at 9:50

GoogleCodeExporter commented 8 years ago 
I have also created Appengine Android Connected Project and having the same 
issues. I have installed Eclipse 4.3  (Kepler) and installed the latest SDKs 
and plugins and still having the issues with generating endpoint client 
libraries.

I have included logs and the problem in the pic below:
http://joxi.ru/uploads/prod/2013/11/13/5ee/a10/51aa6c7b8002c20ac88734cd959324f10
9074fc3.jpg?v=2.3.8

Original comment by ssymbol....@gmail.com on 12 Nov 2013 at 8:04

GoogleCodeExporter commented 8 years ago 
Thanks. Could you show me the bottom part of the stack, or attach a file to 
this issue with the full stack trace copied in?

Original comment by rdayal@google.com on 13 Nov 2013 at 1:29