Closed GoogleCodeExporter closed 9 years ago
And just fyi I have not made any changes to the Java code base. Everything is
fresh install via the document:
http://code.google.com/p/youtube-direct/wiki/GettingStarted
Original comment by steven.s...@gmail.com
on 6 Dec 2010 at 8:25
I'm seeing the same thing with the recently released App Engine 1.4.0 runtime.
I don't think that Eclipse's plugin importer makes it easy for you to download
the older runtime, 1.3.8, but if you could get your hands on that, it would
probably be the easiest solution.
I'm following up with the App Engine team to see what might have changed in the
1.4.0 release that's causing this.
Original comment by api.je...@gmail.com
on 7 Dec 2010 at 9:01
Looks like this is affecting more than just YouTube Direct:
http://code.google.com/p/googleappengine/issues/detail?id=4216
Original comment by api.je...@gmail.com
on 7 Dec 2010 at 9:09
Workaround for local progress is to copy all the jars which references App
Ending SDK library to web\WEB-INF\lib. No need to add them to class path, just
copy them to lib. It looks like the (internal?) javac compiler does not take
into account the current classpath, but only libs in WEB-INF\lib. Compared to
simple appengine aplication created in same eclipse in same workspace and
working with jsp pages, I could not find the reason, why ytd projects has this
problem. I hope this will help a little, at least the workaround seems to work.
(I have 1.4.0 runtime, I have removed the old runtime and put there the actual
one by re-inserting the app engine sdk library to build-path.
Original comment by vital.ge...@gmail.com
on 8 Dec 2010 at 12:43
Thank you will give that a try tomorrow morning!
Original comment by steven.s...@gmail.com
on 8 Dec 2010 at 3:05
[deleted comment]
Ok, I'll be honest I am not a java programmer. Can you explain copying the
jars that reference "App Ending SDK library" to me a bit more?
However, what I did get to work was updating again from svn, and deploying. Now
the admin at least loads on app engine.
I now receive "Request failed: SyntaxError: JSON.parse" errors however these
are because the following is getting returned instead of an obvious json object.
Uncaught exception from servlet
java.lang.Error: Unresolved compilation problem:
The method getSubmissions(String, String, String) of type VideoSubmissionDaoImpl must override a superclass method
at com.google.ytd.dao.VideoSubmissionDaoImpl.getSubmissions(VideoSubmissionDaoImpl.java:40)
at com.google.ytd.command.GetVideoSubmissions.execute(GetVideoSubmissions.java:56)
at com.google.ytd.jsonrpc.JsonRpcProcessor.doPost(JsonRpcProcessor.java:60)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:216)
at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:141)
at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:93)
at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:63)
at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:122)
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:110)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:97)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:35)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:238)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcRequestParser.java:76)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:135)
at com.google.apphosting.runtime.JavaRuntime.handleRequest(JavaRuntime.java:261)
at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8495)
at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8493)
at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest(BlockingApplicationHandler.java:24)
at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java:435)
at com.google.net.rpc.impl.Server$RpcTask.runInContext(Server.java:572)
at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:448)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:688)
at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:326)
at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:318)
at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:446)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
<br>Unexpected exception from servlet: java.lang.Error: Unresolved compilation
problem:
The method getSubmissions(String, String, String) of type VideoSubmissionDaoImpl must override a superclass method
Original comment by steven.s...@gmail.com
on 9 Dec 2010 at 5:31
As per the updates in
http://code.google.com/p/googleappengine/issues/detail?id=4216 this issue has
been acknowledged as a bug in the App Engine 1.4.0 SDK, and will hopefully be
resolved soon in a future patched release.
Original comment by api.je...@gmail.com
on 10 Dec 2010 at 3:58
Thank you so much for your patience and help jeffy. I will be looking forward
to the release of the new SDK, however this unfortunately looks like it spoils
our usage which needs to be live over the next several weeks. C'est la vie.
Original comment by steven.s...@gmail.com
on 10 Dec 2010 at 4:12
For what it's worth, you can still manually download the App Engine 1.3.8 SDK
from one of the links here
http://code.google.com/p/googleappengine/downloads/list?can=4&q=1.3.8&colspec=Filename+Summary+Uploaded+Size+DownloadCount
Use whichever link is appropriate for your operating system. You'll need to
manually copy the SDK's library files to the correct location inside your
Eclipse file hierarchy in order to get Eclipse to pick up on them, making it
more difficult to use than the current Eclipse plugin, but if you're really
stuck and the workarounds that were posted earlier in this bug don't help, it's
another option.
Original comment by api.je...@gmail.com
on 10 Dec 2010 at 4:25
I just reported the same problem, didn't see this post. Jeffy, PLEASE make a
tutorial video on this fix or pull it till you debug it or let it be known
before you spend hours working on this for it not to work. I have big plans for
this app, it is going to change the internet in many ways. My hat is off to
you!!!!
Original comment by aaat...@gmail.com
on 10 Jan 2011 at 5:34
I've confirmed internally that this issue will be resolved in the App Engine
SDK 1.4.2 release, but I can't provide a timeline for when that will be
available (that's up to the App Engine team).
I do apologize that this is affecting YouTube Direct local development, but
we're dependent on the tools that the App Engine team makes available. Do
understand that if you deploy your application to production, things should
work properly there—this only affects the local App Engine development server.
Original comment by api.je...@gmail.com
on 10 Jan 2011 at 4:34
Issue 59 has been merged into this issue.
Original comment by api.je...@gmail.com
on 10 Jan 2011 at 4:35
The App Engine SDK 1.4.2 is out and resolves this issue. Unfortunately,
Eclipse's built-in mechanism for auto-updating plug-ins is not detecting the
1.4.2 release at this time. So you need to manually go to "Help -> Install New
Software..." and enter the URL fo the Google Plugin site
(http://dl.google.com/eclipse/plugin/3.5 for Eclipse 3.5) in the "Work with:"
field, and then select and install the App Engine 1.4.2 plugin from the list
that comes up.
Original comment by api.je...@gmail.com
on 23 Feb 2011 at 3:26
Original issue reported on code.google.com by
steven.s...@gmail.com
on 6 Dec 2010 at 7:40Attachments: