[appengine-java] [SOLVED] Re: Strange exception with my app
Solved. Looks like appengine sandbox banned sun.dc.* classes too. Changed the namespace and now it's up and running. On 14 Ott, 18:07, nicanor.babula nicanor.bab...@gmail.com wrote: Hi google appengine team, Since today, I have been getting continuously the exception reported below. Yesterday I am not sure, but the day before yesterday it worked for sure. I have more apps that use the same library and all of them keep throwing the same exception. You can reproduce it uploading this xsl file:http://www.4shared.com/file/uefUC7KX/simple.html on this servlet:http://almaoffice0.appspot.com/testPDF.jsp app id: almaoffice0 and domodentweb. In the development server, everything works fine (just like before). I need information about the issue pretty fast because the second app is a production one and I need to know what decision to take. Thanks in advance. Uncaught exception from servlet java.lang.NoClassDefFoundError: sun/dc/path/PathException at org.apache.xmlgraphics.java2d.GraphicContext.init(GraphicContext.java: 93) at org.apache.fop.render.intermediate.IFGraphicContext.init(IFGraphicContext .java: 42) at org.apache.fop.render.intermediate.IFRenderer.init(IFRenderer.java: 127) at org.apache.fop.render.RendererFactory.createRendererForDocumentHandler(Rend ererFactory.java: 313) at org.apache.fop.render.RendererFactory.tryIFDocumentHandlerMaker(RendererFac tory.java: 290) at org.apache.fop.render.RendererFactory.createRenderer(RendererFactory.java: 270) at org.apache.fop.area.RenderPagesModel.init(RenderPagesModel.java: 69) at org.apache.fop.area.AreaTreeHandler.setupModel(AreaTreeHandler.java: 130) at org.apache.fop.area.AreaTreeHandler.init(AreaTreeHandler.java: 102) at org.apache.fop.render.RendererFactory.createFOEventHandler(RendererFactory. java: 359) at org.apache.fop.fo.FOTreeBuilder.init(FOTreeBuilder.java:105) at org.apache.fop.apps.Fop.createDefaultHandler(Fop.java:100) at org.apache.fop.apps.Fop.init(Fop.java:78) at org.apache.fop.apps.FopFactory.newFop(FopFactory.java:254) at org.apache.fop.apps.FopFactory.newFop(FopFactory.java:231) at cri.domodentweb.server.servlets.GenUserCalendarMemoPDF.doGet(GenUserCalenda rMemoPDF.java: 166) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 511) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1166) at com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlo bUploadFilter.java: 97) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionF ilter.java: 35) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1157) at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(Trans actionCleanupFilter.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(AppVersionH andlerMap.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(RpcRequ estParser.java: 76) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceReques t(JettyServletEngineAdapter.java: 135) at com.google.apphosting.runtime.JavaRuntime.handleRequest(JavaRuntime.java: 261) at com.google.apphosting.base.RuntimePb$EvaluationRuntime $6.handleBlockingRequest(RuntimePb.java:8483) at com.google.apphosting.base.RuntimePb$EvaluationRuntime $6.handleBlockingRequest(RuntimePb.java:8481) at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest(BlockingAp
[appengine-java] Re: JPA query + missing the obvious?
Experimenting a bit more, I'm now even more confused ... SetSubscription set = new HashSetSubscription(); Query query = getEM().createQuery(select s from Subscription s where s.clientId = ?1); Long cid = client.getId(); query.setParameter(1, cid); List list = query.getResultList(); // -- not empty set.addAll(list); query = getEM().createQuery(select s from Subscription s where s.topicId = ?1); Long tid = topic.getId(); query.setParameter(1, tid); list = query.getResultList(); // -- same results as before -- as we have proper intersection data set.addAll(list); query = getEM().createQuery(select s from Subscription s where s.clientId = ?1 and s.topicId = ?2); query.setParameter(1, cid); query.setParameter(2, tid); list = query.getResultList(); // - no results?!? set.addAll(list); return getSingleResult(set); -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Any changes to access levels in com.google.appengine.api.datastore recently?
Just had the same thing. On Oct 14, 9:14 pm, Darren Clarke dar...@redaranj.com wrote: Has anything changed with class access levels (public vs. private) in the production datastore code in the last day or so? I've had a Clojure app running for several weeks and starting last night, whenever I try to access the datastore, I get the error below. It could be a bug in the library I'm using (appengine-clj) or even in Clojure's dispatch code, but I just want to understand if anything has changed server-side that might have triggered it. The application still works on the dev appserver v1.3.7. java.lang.IllegalArgumentException: Can't call public method of non-public class: public com.google.appengine.api.datastore.Transaction com.google.appengine.api.datastore.BaseDatastoreService.getCurrentTransaction(com.google.appengine.api.datastore.Transaction) at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:85) at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28) at appengine.datastore.service$current_transaction.invoke(service.clj:72) at appengine.datastore.service$put_entity.invoke(service.clj:131) at appengine.datastore.service$fn__176.invoke(service.clj:149) at appengine.datastore.service$fn__136$G__116__141.invoke(service.clj:10) at com.redaranj.ledes.service.servlet$fn__1902$fn__1903.invoke(servlet.clj:17) at compojure.core$routes$fn__1706$fn__1707.invoke(core.clj:72) at clojure.core$some.invokeStatic(core.clj:2297) at compojure.core$routes$fn__1706.invoke(core.clj:71) at ring.middleware.params$wrap_params$fn__1468.invoke(params.clj:77) at ring.middleware.cookies$wrap_cookies$fn__1559.invoke(cookies.clj:123) at ring.util.servlet$make_service_method$fn__1881.invoke(servlet.clj:117) at com.redaranj.ledes.service.servlet$_service.invoke(servlet.clj:19) at com.redaranj.ledes.service.servlet.service(Unknown Source) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) 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:8483) at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8481) at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest(BlockingApplicationHandler.java:24) at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java:418) 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) -- You received this message because you are
[appengine-java] Re: SDK 1.3.8 released!
good news - btw, when can the cookie bug get fixed? http://code.google.com/p/googleappengine/issues/detail?id=1704 not an easy task i guess. well done, after all. On Oct 15, 11:44 am, Takashi Matsuo tmat...@google.com wrote: Hello App Engine Developers! We're very happy to announce that SDK 1.3.8 is released today. There are many new cool features, so please download the new SDK and enjoy it! You can download the new SDK from:http://code.google.com/appengine/downloads.html Our blog post includes some screenshots of new features in admin console:http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-in... Here are release notes: Java --- Version 1.3.8 = - You can run task queue tasks immediately from the admin console. - Added an OutputSettings class to the Images API to specify the JPEG encoding quality when running in production. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.xml, the maximum allowed bucket size is now 100. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - The whitelist has been updated to include java.net.InetAddress and some interfaces and abstract classes in javax.xml.soap, including javax.xml.soap.SOAPMessage. - Fixed an issue reserving App Ids by owners of emails containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue where TaskOptions had no public getters, making testing impossible. http://code.google.com/p/googleappengine/issues/detail?id=3243 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 Python - Version 1.3.8 == - Builtin app.yaml handlers are available for common application functions, such as appstats. http://code.google.com/appengine/docs/python/config/appconfig.html#Bu... - The Admin Console now provides an experimental tool to delete all entities in the datastore or all entities of a given type. This is available only if enabled using the datastore_admin builtin. Deleting entities will count against application quota. http://code.google.com/appengine/docs/python/datastore/creatinggettin... - You can run task queue tasks immediately from the Admin Console. - You can now specify the quality of JPEG images via the Image API's execute_transforms function. Available in production only. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.yaml, the maximum allowed bucket size is now 100. - Precompilation is now enabled by default. To disable, use the --no_precompilation flag when updating your app. - BlobInfo now has an open() method that returns a BlobReader. - BlobReader now accepts a BlobInfo. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - Fixed an issue with task queue tasks not running on the dev_appserver when using Python 2.6. - Fixed an issue on the dev_appserver where auto task running wasn't working for BulkAdd. - Fixed an issue reserving App Ids by owners of similarly-named mails accounts containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 -- Takashi Matsuo Developer Relations Developer Advocate for Google App Engine/iGoogle Google Japan, Inc. -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: HtmlUnit support on GAE for GWT crawlability
On Oct 14, 11:16 am, Gal Dolber gal.dol...@gmail.com wrote: This is not 100% mature, but it is a beginninghttp://code.google.com/p/guit-ajax-crawler/ I haven't tried it yet, but this sounds like a fantastic project. Thanks! I look forward to trying it when I get to that point! -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] SDK 1.3.8 released!
Excellent, thank you! The instances view is really nice and interesting! I just wanted to also mention that while upgrading one of my apps, one controller wasn't compiling against the new SDK, as there had been a little rename refactoring of a method: FetchOptions.Builder#withDefault is now: FetchOptions.Builder#withDefaults Notice the final 's'! Perhaps you could publish a list of API differences between releases? I know some OSS projects publish such documents for helping people upgrade to newer versions, or for showing users what the new APIs are. Anyhow, well done for this release! Guillaume On Fri, Oct 15, 2010 at 05:44, Takashi Matsuo tmat...@google.com wrote: Hello App Engine Developers! We're very happy to announce that SDK 1.3.8 is released today. There are many new cool features, so please download the new SDK and enjoy it! You can download the new SDK from: http://code.google.com/appengine/downloads.html Our blog post includes some screenshots of new features in admin console: http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-includes-new.html Here are release notes: Java --- Version 1.3.8 = - You can run task queue tasks immediately from the admin console. - Added an OutputSettings class to the Images API to specify the JPEG encoding quality when running in production. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.xml, the maximum allowed bucket size is now 100. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - The whitelist has been updated to include java.net.InetAddress and some interfaces and abstract classes in javax.xml.soap, including javax.xml.soap.SOAPMessage. - Fixed an issue reserving App Ids by owners of emails containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue where TaskOptions had no public getters, making testing impossible. http://code.google.com/p/googleappengine/issues/detail?id=3243 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 Python - Version 1.3.8 == - Builtin app.yaml handlers are available for common application functions, such as appstats. http://code.google.com/appengine/docs/python/config/appconfig.html#Builtin_Handlers - The Admin Console now provides an experimental tool to delete all entities in the datastore or all entities of a given type. This is available only if enabled using the datastore_admin builtin. Deleting entities will count against application quota. http://code.google.com/appengine/docs/python/datastore/creatinggettinganddeletingdata.html#Deleting_Entities_in_Bulk - You can run task queue tasks immediately from the Admin Console. - You can now specify the quality of JPEG images via the Image API's execute_transforms function. Available in production only. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.yaml, the maximum allowed bucket size is now 100. - Precompilation is now enabled by default. To disable, use the --no_precompilation flag when updating your app. - BlobInfo now has an open() method that returns a BlobReader. - BlobReader now accepts a BlobInfo. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - Fixed an issue with task queue tasks not running on the dev_appserver when using Python 2.6. - Fixed an issue on the dev_appserver where auto task running wasn't working for BulkAdd. - Fixed an issue reserving App Ids by owners of similarly-named mails accounts containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 -- Takashi Matsuo Developer Relations Developer Advocate for Google App Engine/iGoogle Google Japan, Inc. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send
Re: [appengine-java] SDK 1.3.8 released!
Am I the only one who cannot download the eclipse 1.3.8 update ? On 15/10/10 14:51, Guillaume Laforge glafo...@gmail.com wrote: Excellent, thank you! The instances view is really nice and interesting! I just wanted to also mention that while upgrading one of my apps, one controller wasn't compiling against the new SDK, as there had been a little rename refactoring of a method: FetchOptions.Builder#withDefault is now: FetchOptions.Builder#withDefaults Notice the final 's'! Perhaps you could publish a list of API differences between releases? I know some OSS projects publish such documents for helping people upgrade to newer versions, or for showing users what the new APIs are. Anyhow, well done for this release! Guillaume On Fri, Oct 15, 2010 at 05:44, Takashi Matsuo tmat...@google.com wrote: Hello App Engine Developers! We're very happy to announce that SDK 1.3.8 is released today. There are many new cool features, so please download the new SDK and enjoy it! You can download the new SDK from: http://code.google.com/appengine/downloads.html Our blog post includes some screenshots of new features in admin console: http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-includ es-new.html Here are release notes: Java --- Version 1.3.8 = - You can run task queue tasks immediately from the admin console. - Added an OutputSettings class to the Images API to specify the JPEG encoding quality when running in production. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.xml, the maximum allowed bucket size is now 100. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - The whitelist has been updated to include java.net.InetAddress and some interfaces and abstract classes in javax.xml.soap, including javax.xml.soap.SOAPMessage. - Fixed an issue reserving App Ids by owners of emails containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue where TaskOptions had no public getters, making testing impossible. http://code.google.com/p/googleappengine/issues/detail?id=3243 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 Python - Version 1.3.8 == - Builtin app.yaml handlers are available for common application functions, such as appstats. http://code.google.com/appengine/docs/python/config/appconfig.html#Builti n_Handlers - The Admin Console now provides an experimental tool to delete all entities in the datastore or all entities of a given type. This is available only if enabled using the datastore_admin builtin. Deleting entities will count against application quota. http://code.google.com/appengine/docs/python/datastore/creatinggettingand deletingdata.html#Deleting_Entities_in_Bulk - You can run task queue tasks immediately from the Admin Console. - You can now specify the quality of JPEG images via the Image API's execute_transforms function. Available in production only. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.yaml, the maximum allowed bucket size is now 100. - Precompilation is now enabled by default. To disable, use the --no_precompilation flag when updating your app. - BlobInfo now has an open() method that returns a BlobReader. - BlobReader now accepts a BlobInfo. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - Fixed an issue with task queue tasks not running on the dev_appserver when using Python 2.6. - Fixed an issue on the dev_appserver where auto task running wasn't working for BulkAdd. - Fixed an issue reserving App Ids by owners of similarly-named mails accounts containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 -- Takashi Matsuo Developer Relations Developer Advocate for Google App Engine/iGoogle Google Japan, Inc. -- You received this
Re: [appengine-java] help with redirecting user after authentication
already fixed, sorry fd 2010/10/14 fd fdmu...@gmail.com hello people; i have a question about user authentication, i want to redirect the http request, to a custom url, after the user performs login, actually the framework redirects to the same url that host the app. thanks a lot fd -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Can't get the google application code
Hi I work in a research group in Argentine, I tried to load an application using google app engine but I cant get the application code. I sent my cellphone number and everything seems ok but never get the message with the code. I tried with others cellphone here and nothing!!! I do really want to try App Engine!!! Any Help??? Thanks in advance!!! -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: protobuf storage with JDO
Hello, I think it's not so common. In my project I use protobufs for objects I want to store as serialized fields or in bynary form. That is, I encapsulate protocol buffer building in a wrapper, then store such wrapper in an annotated field of JDO. @Persistent(Serialized = true) private MyProtobufWrapper wrapper; MyProtobufWrapper uses protocol buffer Builder in its writeObject / readObject methods and is of course Serializable. OR @Persistent Blob serializedObject; and use a class MyProtobufAdapter which has two methods byte[] convertToSerialized(MyObjet o) and MyObject deserialize(byte[] bytes). I think this is useful if you want to convert data you share with your client code, or if you hit limitations in datastore modeling that you can't work around. And obviously if you don't need to index such data for queries. Otherwise I'll go with regular datastore fields. Regards Lorenzo On Oct 15, 12:29 am, Guillaume B. guillaume.brus...@gmail.com wrote: Hello, I make a basic application that store simple java object using objectify I also make a spring service that create and return protobuf object as the protobuf object is nearly the same that the object that I store in big table I wonder if there was a standard way to store protobuf object in the datastore as objectify and JDO use annotation and that I will not anoted generated protobuf object perhaps someone as a sample / tutorial of the AddressBook protobuf in appengine that store object in the datastore -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] SDK 1.3.8 released!
Guillaume, Which FetchOptions class are you looking at? The last update I see to either of them was back in April and they were backwards compatible changes. Thanks, Max On Fri, Oct 15, 2010 at 5:51 AM, Guillaume Laforge glafo...@gmail.comwrote: Excellent, thank you! The instances view is really nice and interesting! I just wanted to also mention that while upgrading one of my apps, one controller wasn't compiling against the new SDK, as there had been a little rename refactoring of a method: FetchOptions.Builder#withDefault is now: FetchOptions.Builder#withDefaults Notice the final 's'! Perhaps you could publish a list of API differences between releases? I know some OSS projects publish such documents for helping people upgrade to newer versions, or for showing users what the new APIs are. Anyhow, well done for this release! Guillaume On Fri, Oct 15, 2010 at 05:44, Takashi Matsuo tmat...@google.com wrote: Hello App Engine Developers! We're very happy to announce that SDK 1.3.8 is released today. There are many new cool features, so please download the new SDK and enjoy it! You can download the new SDK from: http://code.google.com/appengine/downloads.html Our blog post includes some screenshots of new features in admin console: http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-includes-new.html Here are release notes: Java --- Version 1.3.8 = - You can run task queue tasks immediately from the admin console. - Added an OutputSettings class to the Images API to specify the JPEG encoding quality when running in production. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.xml, the maximum allowed bucket size is now 100. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - The whitelist has been updated to include java.net.InetAddress and some interfaces and abstract classes in javax.xml.soap, including javax.xml.soap.SOAPMessage. - Fixed an issue reserving App Ids by owners of emails containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue where TaskOptions had no public getters, making testing impossible. http://code.google.com/p/googleappengine/issues/detail?id=3243 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 Python - Version 1.3.8 == - Builtin app.yaml handlers are available for common application functions, such as appstats. http://code.google.com/appengine/docs/python/config/appconfig.html#Builtin_Handlers - The Admin Console now provides an experimental tool to delete all entities in the datastore or all entities of a given type. This is available only if enabled using the datastore_admin builtin. Deleting entities will count against application quota. http://code.google.com/appengine/docs/python/datastore/creatinggettinganddeletingdata.html#Deleting_Entities_in_Bulk - You can run task queue tasks immediately from the Admin Console. - You can now specify the quality of JPEG images via the Image API's execute_transforms function. Available in production only. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.yaml, the maximum allowed bucket size is now 100. - Precompilation is now enabled by default. To disable, use the --no_precompilation flag when updating your app. - BlobInfo now has an open() method that returns a BlobReader. - BlobReader now accepts a BlobInfo. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - Fixed an issue with task queue tasks not running on the dev_appserver when using Python 2.6. - Fixed an issue on the dev_appserver where auto task running wasn't working for BulkAdd. - Fixed an issue reserving App Ids by owners of similarly-named mails accounts containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue on the development server where PNGs were being
Re: [appengine-java] SDK 1.3.8 released!
I can't either, when I try an update in eclipse by using help - install new software - Google App Engine - http://dl.google.com/eclipse/plugin/3.6 I can only see 1.3.7 under the SDKs section. On Fri, Oct 15, 2010 at 6:14 AM, Cyrille Vincey crll...@gmail.com wrote: Am I the only one who cannot download the eclipse 1.3.8 update ? On 15/10/10 14:51, Guillaume Laforge glafo...@gmail.com wrote: Excellent, thank you! The instances view is really nice and interesting! I just wanted to also mention that while upgrading one of my apps, one controller wasn't compiling against the new SDK, as there had been a little rename refactoring of a method: FetchOptions.Builder#withDefault is now: FetchOptions.Builder#withDefaults Notice the final 's'! Perhaps you could publish a list of API differences between releases? I know some OSS projects publish such documents for helping people upgrade to newer versions, or for showing users what the new APIs are. Anyhow, well done for this release! Guillaume On Fri, Oct 15, 2010 at 05:44, Takashi Matsuo tmat...@google.com wrote: Hello App Engine Developers! We're very happy to announce that SDK 1.3.8 is released today. There are many new cool features, so please download the new SDK and enjoy it! You can download the new SDK from: http://code.google.com/appengine/downloads.html Our blog post includes some screenshots of new features in admin console: http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-includ es-new.html Here are release notes: Java --- Version 1.3.8 = - You can run task queue tasks immediately from the admin console. - Added an OutputSettings class to the Images API to specify the JPEG encoding quality when running in production. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.xml, the maximum allowed bucket size is now 100. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - The whitelist has been updated to include java.net.InetAddress and some interfaces and abstract classes in javax.xml.soap, including javax.xml.soap.SOAPMessage. - Fixed an issue reserving App Ids by owners of emails containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue where TaskOptions had no public getters, making testing impossible. http://code.google.com/p/googleappengine/issues/detail?id=3243 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 Python - Version 1.3.8 == - Builtin app.yaml handlers are available for common application functions, such as appstats. http://code.google.com/appengine/docs/python/config/appconfig.html#Builti n_Handlers - The Admin Console now provides an experimental tool to delete all entities in the datastore or all entities of a given type. This is available only if enabled using the datastore_admin builtin. Deleting entities will count against application quota. http://code.google.com/appengine/docs/python/datastore/creatinggettingand deletingdata.html#Deleting_Entities_in_Bulk - You can run task queue tasks immediately from the Admin Console. - You can now specify the quality of JPEG images via the Image API's execute_transforms function. Available in production only. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.yaml, the maximum allowed bucket size is now 100. - Precompilation is now enabled by default. To disable, use the --no_precompilation flag when updating your app. - BlobInfo now has an open() method that returns a BlobReader. - BlobReader now accepts a BlobInfo. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - Fixed an issue with task queue tasks not running on the dev_appserver when using Python 2.6. - Fixed an issue on the dev_appserver where auto task running wasn't working for BulkAdd. - Fixed an issue reserving App Ids by owners of similarly-named mails accounts containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue on the
Re: [appengine-java] Any changes to access levels in com.google.appengine.api.datastore recently?
We refactored the internals of the DatastoreService implementation pretty heavily in the release we just pushed out but there shouldn't have been any backwards incompatible changes to the public API. I'm not familiar with appengine-clj. Does it use reflection to access non-public classes/methods/fields? If so that's not safe, since we only guarantee backwards compatibility for the public API. If not then I'll need more info. Thanks, Max On Thu, Oct 14, 2010 at 12:14 PM, Darren Clarke dar...@redaranj.com wrote: Has anything changed with class access levels (public vs. private) in the production datastore code in the last day or so? I've had a Clojure app running for several weeks and starting last night, whenever I try to access the datastore, I get the error below. It could be a bug in the library I'm using (appengine-clj) or even in Clojure's dispatch code, but I just want to understand if anything has changed server-side that might have triggered it. The application still works on the dev appserver v1.3.7. java.lang.IllegalArgumentException: Can't call public method of non-public class: public com.google.appengine.api.datastore.Transaction com.google.appengine.api.datastore.BaseDatastoreService.getCurrentTransaction(com.google.appengine.api.datastore.Transaction) at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:85) at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28) at appengine.datastore.service$current_transaction.invoke(service.clj:72) at appengine.datastore.service$put_entity.invoke(service.clj:131) at appengine.datastore.service$fn__176.invoke(service.clj:149) at appengine.datastore.service$fn__136$G__116__141.invoke(service.clj:10) at com.redaranj.ledes.service.servlet$fn__1902$fn__1903.invoke(servlet.clj:17) at compojure.core$routes$fn__1706$fn__1707.invoke(core.clj:72) at clojure.core$some.invokeStatic(core.clj:2297) at compojure.core$routes$fn__1706.invoke(core.clj:71) at ring.middleware.params$wrap_params$fn__1468.invoke(params.clj:77) at ring.middleware.cookies$wrap_cookies$fn__1559.invoke(cookies.clj:123) at ring.util.servlet$make_service_method$fn__1881.invoke(servlet.clj:117) at com.redaranj.ledes.service.servlet$_service.invoke(servlet.clj:19) at com.redaranj.ledes.service.servlet.service(Unknown Source) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) 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:8483) at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8481) at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest(BlockingApplicationHandler.java:24) at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java:418) at com.google.net.rpc.impl.Server$RpcTask.runInContext(Server.java:572)
[appengine-java] Re: SDK 1.3.8 released!
Apparently the newer version of SDK is not available yet. On Oct 15, 3:14 pm, Cyrille Vincey crll...@gmail.com wrote: Am I the only one who cannot download the eclipse 1.3.8 update ? On 15/10/10 14:51, Guillaume Laforge glafo...@gmail.com wrote: Excellent, thank you! The instances view is really nice and interesting! I just wanted to also mention that while upgrading one of my apps, one controller wasn't compiling against the new SDK, as there had been a little rename refactoring of a method: FetchOptions.Builder#withDefault is now: FetchOptions.Builder#withDefaults Notice the final 's'! Perhaps you could publish a list of API differences between releases? I know some OSS projects publish such documents for helping people upgrade to newer versions, or for showing users what the new APIs are. Anyhow, well done for this release! Guillaume On Fri, Oct 15, 2010 at 05:44, Takashi Matsuo tmat...@google.com wrote: Hello App Engine Developers! We're very happy to announce that SDK 1.3.8 is released today. There are many new cool features, so please download the new SDK and enjoy it! You can download the new SDK from: http://code.google.com/appengine/downloads.html Our blog post includes some screenshots of new features in admin console: http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-in... es-new.html Here are release notes: Java --- Version 1.3.8 = - You can run task queue tasks immediately from the admin console. - Added an OutputSettings class to the Images API to specify the JPEG encoding quality when running in production. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.xml, the maximum allowed bucket size is now 100. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - The whitelist has been updated to include java.net.InetAddress and some interfaces and abstract classes in javax.xml.soap, including javax.xml.soap.SOAPMessage. - Fixed an issue reserving App Ids by owners of emails containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue where TaskOptions had no public getters, making testing impossible. http://code.google.com/p/googleappengine/issues/detail?id=3243 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 Python - Version 1.3.8 == - Builtin app.yaml handlers are available for common application functions, such as appstats. http://code.google.com/appengine/docs/python/config/appconfig.html#Bu... n_Handlers - The Admin Console now provides an experimental tool to delete all entities in the datastore or all entities of a given type. This is available only if enabled using the datastore_admin builtin. Deleting entities will count against application quota. http://code.google.com/appengine/docs/python/datastore/creatinggettin... deletingdata.html#Deleting_Entities_in_Bulk - You can run task queue tasks immediately from the Admin Console. - You can now specify the quality of JPEG images via the Image API's execute_transforms function. Available in production only. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.yaml, the maximum allowed bucket size is now 100. - Precompilation is now enabled by default. To disable, use the --no_precompilation flag when updating your app. - BlobInfo now has an open() method that returns a BlobReader. - BlobReader now accepts a BlobInfo. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - Fixed an issue with task queue tasks not running on the dev_appserver when using Python 2.6. - Fixed an issue on the dev_appserver where auto task running wasn't working for BulkAdd. - Fixed an issue reserving App Ids by owners of similarly-named mails accounts containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue on the development server where PNGs were being
Re: [appengine-java] Can't get the google application code
Hi! Look, I'm from Uruguay and I had the same problems with carriers from here. Apply in this form: https://appengine.google.com/waitlist/sms_issues and explain that you're not getting the activation sms... after a few hours you should get an email from google and your account activated. Hope it helps! Seba 2010/10/15 QFractal s4sali...@gmail.com Hi I work in a research group in Argentine, I tried to load an application using google app engine but I cant get the application code. I sent my cellphone number and everything seems ok but never get the message with the code. I tried with others cellphone here and nothing!!! I do really want to try App Engine!!! Any Help??? Thanks in advance!!! -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] SDK 1.3.8 released!
Hi Max, I upgraded one app from a much older version, so that must have been a change I had not noticed before, sorry for the false alarm then. Guillaume On Fri, Oct 15, 2010 at 18:38, Max Ross (Google) maxr+appeng...@google.commaxr%2bappeng...@google.com wrote: Guillaume, Which FetchOptions class are you looking at? The last update I see to either of them was back in April and they were backwards compatible changes. Thanks, Max On Fri, Oct 15, 2010 at 5:51 AM, Guillaume Laforge glafo...@gmail.comwrote: Excellent, thank you! The instances view is really nice and interesting! I just wanted to also mention that while upgrading one of my apps, one controller wasn't compiling against the new SDK, as there had been a little rename refactoring of a method: FetchOptions.Builder#withDefault is now: FetchOptions.Builder#withDefaults Notice the final 's'! Perhaps you could publish a list of API differences between releases? I know some OSS projects publish such documents for helping people upgrade to newer versions, or for showing users what the new APIs are. Anyhow, well done for this release! Guillaume On Fri, Oct 15, 2010 at 05:44, Takashi Matsuo tmat...@google.com wrote: Hello App Engine Developers! We're very happy to announce that SDK 1.3.8 is released today. There are many new cool features, so please download the new SDK and enjoy it! You can download the new SDK from: http://code.google.com/appengine/downloads.html Our blog post includes some screenshots of new features in admin console: http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-includes-new.html Here are release notes: Java --- Version 1.3.8 = - You can run task queue tasks immediately from the admin console. - Added an OutputSettings class to the Images API to specify the JPEG encoding quality when running in production. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.xml, the maximum allowed bucket size is now 100. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - The whitelist has been updated to include java.net.InetAddress and some interfaces and abstract classes in javax.xml.soap, including javax.xml.soap.SOAPMessage. - Fixed an issue reserving App Ids by owners of emails containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue where TaskOptions had no public getters, making testing impossible. http://code.google.com/p/googleappengine/issues/detail?id=3243 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 Python - Version 1.3.8 == - Builtin app.yaml handlers are available for common application functions, such as appstats. http://code.google.com/appengine/docs/python/config/appconfig.html#Builtin_Handlers - The Admin Console now provides an experimental tool to delete all entities in the datastore or all entities of a given type. This is available only if enabled using the datastore_admin builtin. Deleting entities will count against application quota. http://code.google.com/appengine/docs/python/datastore/creatinggettinganddeletingdata.html#Deleting_Entities_in_Bulk - You can run task queue tasks immediately from the Admin Console. - You can now specify the quality of JPEG images via the Image API's execute_transforms function. Available in production only. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.yaml, the maximum allowed bucket size is now 100. - Precompilation is now enabled by default. To disable, use the --no_precompilation flag when updating your app. - BlobInfo now has an open() method that returns a BlobReader. - BlobReader now accepts a BlobInfo. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - Fixed an issue with task queue tasks not running on the dev_appserver when using Python 2.6. - Fixed an issue on the dev_appserver where auto task running wasn't working for BulkAdd. - Fixed
Re: [appengine-java] Can't get the google application code
hey buddys! i'm tried too, but sms messages seems don't work. I filled this form and my account was opened without sms validation. https://appengine.google.com/waitlist/sms_issues i'm also in Argentina and i never received a sms message. greetings! Franco. 2010/10/15 SebaGra seba...@gmail.com Hi! Look, I'm from Uruguay and I had the same problems with carriers from here. Apply in this form: https://appengine.google.com/waitlist/sms_issues and explain that you're not getting the activation sms... after a few hours you should get an email from google and your account activated. Hope it helps! Seba 2010/10/15 QFractal s4sali...@gmail.com Hi I work in a research group in Argentine, I tried to load an application using google app engine but I cant get the application code. I sent my cellphone number and everything seems ok but never get the message with the code. I tried with others cellphone here and nothing!!! I do really want to try App Engine!!! Any Help??? Thanks in advance!!! -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] properties missing from datastore viewer
Hi, I'm developing a new app using twig, just getting started with GAE. I often delete all entities using the data store browser to cleanup (using 1.3.7) It's also pretty often that some properties missing from datastore viewer (i.e. columns). I don't get empty data, but the whole column isn't displayed. The data is there though, as it's properly loaded from my app. Is this a known issue? Is there more info I could provide for debug? Thanks -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] a basic tutorial on using the new 1.3.8 datastore delete with a Java app
It wasn't immediately obvious on how to get the 1.3.8 datastore delete
functionality working with a Java app so I played around with it, got
it working and thought I'd share how I did it for those java devs that
cringe at the sight of python :)
lets assume you have an existing java app with an app id my_java_app
1. install the appengine python sdk
(http://code.google.com/appengine/downloads.html)
2. create a new folder anywhere outside your existing java project and
call it (for example) my_java_app_tmp
3. create a file called app.yaml with these contents (make sure the
application id is the same as your java one, and it has a non existing
version number (I used 99)
application: my_java_app
version: 99
runtime: python
api_version: 1
handlers:
- url: .*
script: main.py
builtins:
- datastore_admin: on
3. create a index.yaml with this content (not sure if this is required
but I did it)
indexes:
4. create a main.py with this content
#!/usr/bin/env python
#
# Copyright 2007 Google Inc.
#
# Licensed under the Apache License, Version 2.0 (the License);
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an AS IS BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
from google.appengine.ext import webapp
from google.appengine.ext.webapp import util
class MainHandler(webapp.RequestHandler):
def get(self):
self.response.out.write('Hello world!')
def main():
application = webapp.WSGIApplication([('/', MainHandler)],
debug=True)
util.run_wsgi_app(application)
if __name__ == '__main__':
main()
5. upload the app using the python script (its installed when you
install the appengine python sdk)
appcfg.py update my_java_app_tmp
6. once uploaded go to the app console (https://appengine.google.com)
and on the top left of the console select your java app and then in
the option box next to it select 99
7. now underneath the blob viewer on the left side you should have the
option 'datastore admin'
all done.
enjoy.
--
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 google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] bean.XMLEncoder AccessControlException
Hey Guys,
I'm use some very simple beans and have run into an java security exception
when I deployed into production servers.
{
ByteArrayOutputStream baos = new ByteArrayOutputStream( );
XMLEncoder encoder = new XMLEncoder(baos);
encoder.writeObject( myBean );
encoder.close();
return baos.toString();
}
XMLEncoder is on the JRE
whitelisthttp://code.google.com/appengine/docs/java/jrewhitelist.html
This does not happen in Development Mode, only in production.
java.security.AccessControlException: access denied
(java.util.PropertyPermission java.version read)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:355)
at
java.security.AccessController.checkPermission(AccessController.java:567)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at
com.google.apphosting.runtime.security.CustomSecurityManager.checkPermission(CustomSecurityManager.java:45)
at
java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1302)
at java.lang.System.getProperty(System.java:669)
at java.beans.XMLEncoder.flush(XMLEncoder.java:406)
at java.beans.XMLEncoder.close(XMLEncoder.java:446)
Does anyone have an idea of what could cause this?
--Stevko
--
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 google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: bean.XMLEncoder AccessControlException
Found an issue #3866 being worked on presently... Java policy changed (throwing AccessControlException for read of basic things like java.version) http://code.google.com/p/googleappengine/issues/detail?id=3866 -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] javax.mail.Transport.send() API throws ApiDeadlineExceededException but emails are sent
We're aware of this issue and looking into it. There's another thread in the google-appengine group that follows this issue. Can you make sure you keep up with that? -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Thu, Oct 14, 2010 at 1:14 AM, Lior Harsat lior.har...@gmail.com wrote: Hi, I am using the javax.mail.Transport.send(). this API may throw ApiDeadlineExceededException . When it does I catch it a retry. I am currently retrying 5 times. 3 days ago I started noticing in my logs that ApiDeadlineExceededException are thrown at a higher rate than normal. To my surprise I found out that even though the exception is thrown, The emails are sent (including the ones in the retry). This causes the same email to be sent 6 times !!! My customers noticed this as well :-( My appId is farmigo-csa. Please assist. Thanx, Lior -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Newly deployed app doesn’t seem a lways reflected on the server.
I deployed an app, in which an URL was originally serving simply a “hello”. Later I changed the content served from that URL to something else and deployed it again. However the new content did not show up and the page still showed the original “hello”. Another (possibly related) issue I'm experiencing is that an URL that was removed from my code remained accessible for about a day or so after the new code was deployed. (The issue could be either from the delayed deployment or some sort of cache?) p.s. everything is working as expected on devel environment. p.s. admin console shows successful deployment. Anyone encountered similar issues? Any suggestions? Thanks -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Transforming Images from the Blobstore
I got this example from the site: http://code.google.com/intl/en/appengine/docs/java/images/overview.html I'm using the API in this way: BlobKey blobKey = blobs.get(image); ImagesService imagesService = ImagesServiceFactory.getImagesService(); Image oldImage = ImagesServiceFactory.makeImageFromBlob(blobKey); Transform resize = ImagesServiceFactory.makeResize(200, 300); Image newImage = imagesService.applyTransform(resize, oldImage); String urlimg = images.getServingUrl(newImage.getBlobKey()); my .jsp img src =urlimg / when I invoke the method: images.getServingUrl(newImage.getBlobKey()); newImage.getBlobKey() is always null. I'm looking to manipulate the image and then return the image url. How could I be doing? -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: SDK 1.3.8 released!
Eclipse is not picking up this new release! Also, why second class treatment to Java developers? Most of the advanced tricks for appengine involves python. On Oct 15, 8:44 am, Takashi Matsuo tmat...@google.com wrote: Hello App Engine Developers! We're very happy to announce that SDK 1.3.8 is released today. There are many new cool features, so please download the new SDK and enjoy it! You can download the new SDK from:http://code.google.com/appengine/downloads.html Our blog post includes some screenshots of new features in admin console:http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-in... Here are release notes: Java --- Version 1.3.8 = - You can run task queue tasks immediately from the admin console. - Added an OutputSettings class to the Images API to specify the JPEG encoding quality when running in production. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.xml, the maximum allowed bucket size is now 100. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - The whitelist has been updated to include java.net.InetAddress and some interfaces and abstract classes in javax.xml.soap, including javax.xml.soap.SOAPMessage. - Fixed an issue reserving App Ids by owners of emails containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue where TaskOptions had no public getters, making testing impossible. http://code.google.com/p/googleappengine/issues/detail?id=3243 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 Python - Version 1.3.8 == - Builtin app.yaml handlers are available for common application functions, such as appstats. http://code.google.com/appengine/docs/python/config/appconfig.html#Bu... - The Admin Console now provides an experimental tool to delete all entities in the datastore or all entities of a given type. This is available only if enabled using the datastore_admin builtin. Deleting entities will count against application quota. http://code.google.com/appengine/docs/python/datastore/creatinggettin... - You can run task queue tasks immediately from the Admin Console. - You can now specify the quality of JPEG images via the Image API's execute_transforms function. Available in production only. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.yaml, the maximum allowed bucket size is now 100. - Precompilation is now enabled by default. To disable, use the --no_precompilation flag when updating your app. - BlobInfo now has an open() method that returns a BlobReader. - BlobReader now accepts a BlobInfo. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - Fixed an issue with task queue tasks not running on the dev_appserver when using Python 2.6. - Fixed an issue on the dev_appserver where auto task running wasn't working for BulkAdd. - Fixed an issue reserving App Ids by owners of similarly-named mails accounts containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 -- Takashi Matsuo Developer Relations Developer Advocate for Google App Engine/iGoogle Google Japan, Inc. -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] How to get rid of a hanging mapreduce job?
Here's the scoop... One of my first mapreduce jobs didn't want to complete by itself. It did not want to abort either. To get rid of the sucker I deployed a new application version and deleted the one the job was running against. I also manually deleted all the residual state mapreduce created in the datastore. That seemed to kill most of it. However now, 5 days later, there are still two artifacts - mapperCallback and controllerCallback - that disturb my serenity (and keep sucking the juice) by popping up every hour or so. Obviously they are looking for a job that exists no more and fail miserably with a stack trace similar to below. Is there a way to make them go away? java.lang.RuntimeException: Couldn't find MR with job ID: job_1286643750234_0001 at com.google.appengine.tools.mapreduce.AppEngineJobContext.getConfigurationFromRequest(AppEngineJobContext.java: 157) at com.google.appengine.tools.mapreduce.AppEngineJobContext.init(AppEngineJobContext.java: 110) at com.google.appengine.tools.mapreduce.MapReduceServlet.handleController(MapReduceServlet.java: 507) at com.google.appengine.tools.mapreduce.MapReduceServlet.doPost(MapReduceServlet.java: 222) at javax.servlet.http.HttpServlet.service(HttpServlet.java:713) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 511) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1166) 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:8483) at com.google.apphosting.base.RuntimePb$EvaluationRuntime $6.handleBlockingRequest(RuntimePb.java:8481) at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest(BlockingApplicationHandler.java: 24) at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java: 418) 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) Uncaught exception from servlet java.lang.RuntimeException: Couldn't find MR with job ID: job_1286643750234_0001 at com.google.appengine.tools.mapreduce.AppEngineJobContext.getConfigurationFromRequest(AppEngineJobContext.java: 157) at
Re: [appengine-java] How to get rid of a hanging mapreduce job?
Which map reduce library are you using? Saludos, Guillermo Schwarz. El 15-10-2010, a las 18:44, burnayev burna...@gmail.com escribió: Here's the scoop... One of my first mapreduce jobs didn't want to complete by itself. It did not want to abort either. To get rid of the sucker I deployed a new application version and deleted the one the job was running against. I also manually deleted all the residual state mapreduce created in the datastore. That seemed to kill most of it. However now, 5 days later, there are still two artifacts - mapperCallback and controllerCallback - that disturb my serenity (and keep sucking the juice) by popping up every hour or so. Obviously they are looking for a job that exists no more and fail miserably with a stack trace similar to below. Is there a way to make them go away? java.lang.RuntimeException: Couldn't find MR with job ID: job_1286643750234_0001 at com.google.appengine.tools.mapreduce.AppEngineJobContext.getConfigurationFromRequest( AppEngineJobContext.java: 157) at com.google.appengine.tools.mapreduce.AppEngineJobContext.init (AppEngineJobContext.java: 110) at com.google.appengine.tools.mapreduce.MapReduceServlet.handleController( MapReduceServlet.java: 507) at com.google.appengine.tools.mapreduce.MapReduceServlet.doPost (MapReduceServlet.java: 222) at javax.servlet.http.HttpServlet.service(HttpServlet.java:713) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle (ServletHolder.java: 511) at org.mortbay.jetty.servlet.ServletHandler $CachedChain.doFilter(ServletHandler.java:1166) 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:8483) at com.google.apphosting.base.RuntimePb$EvaluationRuntime $6.handleBlockingRequest(RuntimePb.java:8481) at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest (BlockingApplicationHandler.java: 24) at com.google.net.rpc.impl.RpcUtil.runRpcInApplication (RpcUtil.java: 418) 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) Uncaught exception from servlet java.lang.RuntimeException: Couldn't find MR with job ID: job_1286643750234_0001 at com.google.appengine.tools.mapreduce.AppEngineJobContext.getConfigurationFromRequest( AppEngineJobContext.java: 157) at com.google.appengine.tools.mapreduce.AppEngineJobContext.init (AppEngineJobContext.java: 110)
Re: [appengine-java] Re: SDK 1.3.8 released!
same here, I tried an eclipse helios update, and it doesn't see this release. On Fri, Oct 15, 2010 at 10:26 AM, Ganesh Krishnan ganesh...@gmail.comwrote: Eclipse is not picking up this new release! Also, why second class treatment to Java developers? Most of the advanced tricks for appengine involves python. On Oct 15, 8:44 am, Takashi Matsuo tmat...@google.com wrote: Hello App Engine Developers! We're very happy to announce that SDK 1.3.8 is released today. There are many new cool features, so please download the new SDK and enjoy it! You can download the new SDK from: http://code.google.com/appengine/downloads.html Our blog post includes some screenshots of new features in admin console: http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-in... Here are release notes: Java --- Version 1.3.8 = - You can run task queue tasks immediately from the admin console. - Added an OutputSettings class to the Images API to specify the JPEG encoding quality when running in production. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.xml, the maximum allowed bucket size is now 100. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - The whitelist has been updated to include java.net.InetAddress and some interfaces and abstract classes in javax.xml.soap, including javax.xml.soap.SOAPMessage. - Fixed an issue reserving App Ids by owners of emails containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue where TaskOptions had no public getters, making testing impossible. http://code.google.com/p/googleappengine/issues/detail?id=3243 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 Python - Version 1.3.8 == - Builtin app.yaml handlers are available for common application functions, such as appstats. http://code.google.com/appengine/docs/python/config/appconfig.html#Bu... - The Admin Console now provides an experimental tool to delete all entities in the datastore or all entities of a given type. This is available only if enabled using the datastore_admin builtin. Deleting entities will count against application quota. http://code.google.com/appengine/docs/python/datastore/creatinggettin... - You can run task queue tasks immediately from the Admin Console. - You can now specify the quality of JPEG images via the Image API's execute_transforms function. Available in production only. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.yaml, the maximum allowed bucket size is now 100. - Precompilation is now enabled by default. To disable, use the --no_precompilation flag when updating your app. - BlobInfo now has an open() method that returns a BlobReader. - BlobReader now accepts a BlobInfo. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - Fixed an issue with task queue tasks not running on the dev_appserver when using Python 2.6. - Fixed an issue on the dev_appserver where auto task running wasn't working for BulkAdd. - Fixed an issue reserving App Ids by owners of similarly-named mails accounts containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 -- Takashi Matsuo Developer Relations Developer Advocate for Google App Engine/iGoogle Google Japan, Inc. -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . For more options, visit this group at
Re: [appengine-java] Re: SDK 1.3.8 released!
Sorry folks, the Eclipse plugin pipeline is a bit backed up and the 1.3.8 release will not be automatically updated until Monday. In the mean time you can download the SDK manually and point Eclipse to it if you need to upgrade early. This has nothing to do with Java being treated as a second class language, it's just unfortunate timing. As evidence, 1.3.8 is already out in Maven Central: http://repo2.maven.org/maven2/com/google/appengine/appengine-tools-sdk/1.3.8/ On Fri, Oct 15, 2010 at 4:58 PM, Jeroen Lapre' jeroen.la...@gmail.com wrote: same here, I tried an eclipse helios update, and it doesn't see this release. On Fri, Oct 15, 2010 at 10:26 AM, Ganesh Krishnan ganesh...@gmail.com wrote: Eclipse is not picking up this new release! Also, why second class treatment to Java developers? Most of the advanced tricks for appengine involves python. On Oct 15, 8:44 am, Takashi Matsuo tmat...@google.com wrote: Hello App Engine Developers! We're very happy to announce that SDK 1.3.8 is released today. There are many new cool features, so please download the new SDK and enjoy it! You can download the new SDK from:http://code.google.com/appengine/downloads.html Our blog post includes some screenshots of new features in admin console:http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-in... Here are release notes: Java --- Version 1.3.8 = - You can run task queue tasks immediately from the admin console. - Added an OutputSettings class to the Images API to specify the JPEG encoding quality when running in production. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.xml, the maximum allowed bucket size is now 100. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - The whitelist has been updated to include java.net.InetAddress and some interfaces and abstract classes in javax.xml.soap, including javax.xml.soap.SOAPMessage. - Fixed an issue reserving App Ids by owners of emails containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue where TaskOptions had no public getters, making testing impossible. http://code.google.com/p/googleappengine/issues/detail?id=3243 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 Python - Version 1.3.8 == - Builtin app.yaml handlers are available for common application functions, such as appstats. http://code.google.com/appengine/docs/python/config/appconfig.html#Bu... - The Admin Console now provides an experimental tool to delete all entities in the datastore or all entities of a given type. This is available only if enabled using the datastore_admin builtin. Deleting entities will count against application quota. http://code.google.com/appengine/docs/python/datastore/creatinggettin... - You can run task queue tasks immediately from the Admin Console. - You can now specify the quality of JPEG images via the Image API's execute_transforms function. Available in production only. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.yaml, the maximum allowed bucket size is now 100. - Precompilation is now enabled by default. To disable, use the --no_precompilation flag when updating your app. - BlobInfo now has an open() method that returns a BlobReader. - BlobReader now accepts a BlobInfo. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - Fixed an issue with task queue tasks not running on the dev_appserver when using Python 2.6. - Fixed an issue on the dev_appserver where auto task running wasn't working for BulkAdd. - Fixed an issue reserving App Ids by owners of similarly-named mails accounts containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue on the development server where PNGs were being returned as JPEGs.
Re: [appengine-java] Re: SDK 1.3.8 released!
Adding to Don's comments, we are sorry about this on the Google Plugin for Eclipse team. In the meantime, you can install the SDK manually by downloading it and following these instructions: http://code.google.com/eclipse/docs/using_sdks.html On Fri, Oct 15, 2010 at 6:17 PM, Don Schwarz schwa...@google.com wrote: Sorry folks, the Eclipse plugin pipeline is a bit backed up and the 1.3.8 release will not be automatically updated until Monday. In the mean time you can download the SDK manually and point Eclipse to it if you need to upgrade early. This has nothing to do with Java being treated as a second class language, it's just unfortunate timing. As evidence, 1.3.8 is already out in Maven Central: http://repo2.maven.org/maven2/com/google/appengine/appengine-tools-sdk/1.3.8/ On Fri, Oct 15, 2010 at 4:58 PM, Jeroen Lapre' jeroen.la...@gmail.com wrote: same here, I tried an eclipse helios update, and it doesn't see this release. On Fri, Oct 15, 2010 at 10:26 AM, Ganesh Krishnan ganesh...@gmail.com wrote: Eclipse is not picking up this new release! Also, why second class treatment to Java developers? Most of the advanced tricks for appengine involves python. On Oct 15, 8:44 am, Takashi Matsuo tmat...@google.com wrote: Hello App Engine Developers! We're very happy to announce that SDK 1.3.8 is released today. There are many new cool features, so please download the new SDK and enjoy it! You can download the new SDK from:http://code.google.com/appengine/downloads.html Our blog post includes some screenshots of new features in admin console: http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-in... Here are release notes: Java --- Version 1.3.8 = - You can run task queue tasks immediately from the admin console. - Added an OutputSettings class to the Images API to specify the JPEG encoding quality when running in production. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.xml, the maximum allowed bucket size is now 100. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - The whitelist has been updated to include java.net.InetAddress and some interfaces and abstract classes in javax.xml.soap, including javax.xml.soap.SOAPMessage. - Fixed an issue reserving App Ids by owners of emails containing periods, multiple cases, and googlemail.com address. http://code.google.com/p/googleappengine/issues/detail?id=1196 - Fixed an issue where TaskOptions had no public getters, making testing impossible. http://code.google.com/p/googleappengine/issues/detail?id=3243 - Fixed an issue on the development server where PNGs were being returned as JPEGs. http://code.google.com/p/googleappengine/issues/detail?id=3661 Python - Version 1.3.8 == - Builtin app.yaml handlers are available for common application functions, such as appstats. http://code.google.com/appengine/docs/python/config/appconfig.html#Bu... - The Admin Console now provides an experimental tool to delete all entities in the datastore or all entities of a given type. This is available only if enabled using the datastore_admin builtin. Deleting entities will count against application quota. http://code.google.com/appengine/docs/python/datastore/creatinggettin... - You can run task queue tasks immediately from the Admin Console. - You can now specify the quality of JPEG images via the Image API's execute_transforms function. Available in production only. - Support for login of multiple Google accounts within an app, and longer login sessions. For more information see: http://www.google.com/support/accounts/bin/answer.py?answer=181599 - In queue.yaml, the maximum allowed bucket size is now 100. - Precompilation is now enabled by default. To disable, use the --no_precompilation flag when updating your app. - BlobInfo now has an open() method that returns a BlobReader. - BlobReader now accepts a BlobInfo. - Removed limits on zigzag merge-join queries. Therefore the error The built-in indices are not efficient enough for this query and your data. Please add a composite index for this query. will no longer be thrown in most cases, enabling more types of queries without indexes. - Fixed an issue with task queue tasks not running on the dev_appserver when using
[appengine-java] help JDO meta declaration [ Meta-Data/annotations for the class are not found]
Hello I create a gae project by template
As I work with eclipse plugin the jdoconfig.xml has been generated and
the datanucleus.jar files (3) are in the WEB-INF lib path
add a java basic UserApp class (pojo without any annotation) (this
class must not be modifed else I would have add annotation nut this is
not possible)
add a PMF.java to retrieve Persistant Manager (code from google
appengine JDP tutorial page)
create a package.jdo declaration file that I place in the same package
I moify defaut gae servlet to make a jdo test
public static UserApp insertNewApp(UserApp userBuilder) {
PersistenceManager pm = PMF.get().getPersistenceManager();
pm.makePersistent(userBuilder);
System.out.println(
The ID of the new entry is: + userBuilder.getId());
return userBuilder;
}
I did not modify jdoconfig.xml and perhaps I miss something here but I
don't know how to declare my package.jdo in the jdoconfig.xml
Off course When I start the project as Gae project in eclipse, I have
an error
The class The class test.gae.UserApp is not persistable ...
Meta-Data/annotations for the class are not found
If someone can eplain me the step I miss to make all of this works,
this would be great
ps the file package.jdo has been renamed to fit this forum restriction
--
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 google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
?xml version=1.0?
!DOCTYPE jdo SYSTEM file:/javax/jdo/jdo.dtd
jdo
package name=test.gae
class name=UserApp table=UserData
field name=id primary-key=true/
field name=name/
field name=email/
field name=externalId/
/class
/package
/jdopackage test.gae;
import javax.jdo.JDOHelper;
import javax.jdo.PersistenceManagerFactory;
public final class PMF {
private static final PersistenceManagerFactory pmfInstance =
JDOHelper.getPersistenceManagerFactory(transactions-optional);
private PMF() {}
public static PersistenceManagerFactory get() {
return pmfInstance;
}
}package test.gae;
import java.io.IOException;
import javax.jdo.PersistenceManager;
import javax.servlet.http.*;
@SuppressWarnings(serial)
public class Test_gae_servletServlet extends HttpServlet {
public void doGet(HttpServletRequest req, HttpServletResponse resp)
throws IOException {
UserApp userBuilder = new UserApp();
userBuilder.setId(10L);
userBuilder.setName(name1);
userBuilder.setEmail(mail1);
userBuilder.setExternalId(external1);
insertNewApp(userBuilder);
resp.setContentType(text/plain);
resp.getWriter().println(Hello, world);
}
public static UserApp insertNewApp(UserApp userBuilder) {
PersistenceManager pm = PMF.get().getPersistenceManager();
pm.makePersistent(userBuilder);
System.out.println(
The ID of the new entry is: + userBuilder.getId());
return userBuilder;
}
}
package test.gae;
import java.io.Serializable;
public class UserApp {
private Long id;
/** The corresponding id of this user for facebook / opensocial / openId*/
private String externalId = null;
private String name = null;
private String language = null;
private String email = null;
private Long preferedChannelListId = null;
public void setId(Long id) {
this.id = id;
}
public Long getId() {
return id;
}
public void setName(String name) {
this.name = name;
}
public String getName() {
return name;
}
public void setLanguage(String language) {
this.language = language;
}
public String getLanguage() {
return language;
}
public void setEmail(String mail) {
this.email = mail;
}
public String getMail() {
return email;
}
public void setExternalId(String externalId) {
this.externalId = externalId;
}
public String getExternalId() {
return externalId;
}
public void setPreferedChannelListId(Long preferedChannelListId) {
this.preferedChannelListId = preferedChannelListId;
}
public Long getPreferedChannelListId() {
return preferedChannelListId;
}
}
[appengine-java] Re: API CRUD interface for application ?
now I'm playing with this http://www.restlet.org/ looks promising, activate only the necessary jar (Jackson supported) one rest application data-service in the clouds and the ability to create multiple implementations of client applications (webapp, android, etc) 'sorry for my Google translated english' =) On Oct 11, 3:28 am, Maxim Veksler ma...@vekslers.org wrote: Hello, The application we run is a backend online service and has no GUI. We some how need to be able to upload new content / update existing datastore entity records. The database model is relatively simple: 1 to many relationships on all of the kinds. I would be happy to use learn about a library / some API configuration option to expose an interface so that external code can do the CRUD logic. Is there any support for this in GAE / other library that runs on GAE? If this plays any role in your suggestions: We're super focused on response times so: We currently use low level data store API. I actually tried Objectify but found even it to be an over kill for our needs. I also deleted all the jars the were added by GAE eclipse plugin but are not used by the code. Actually the list of jars used by the application consists of: ls war/WEB-INF/lib/ appengine-api-1.0-sdk-1.3.7.jar appengine-jsr107cache-1.3.7.jar jackson-core-asl-1.6.0.jar jsr107cache-1.1.jar appengine-api-labs-1.3.7.jar EyeViewUtils-1.0.1-SNAPSHOT.jar jackson-mapper-asl-1.6.0.jar log4j-1.2.16.jar Any recommendations / personal experience with this issue / pointers about correct design of the interface / what technology to use and co. are highly welcome and appreciated. Thank you, Maxim. -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Using multiple PersistenceManagerFactorys for multiple concurrent Transactions.
Hello, Can someone from the GAE team please confirm whether this would be possible? My specific use-case is that I have meta data in one entity group and instance data in another. Services, using nested transactions and different PersistenceManagerFactorys, could hopefully access both (as they would be different 'Transactions' and never refer to the same entity groups). I've run various tests that seem to indicate that this should be possible, but I'm now getting IllegalStateExceptions as it seems I have: Attempted to deregister a transaction that is not currently registered. The only way I could really see that this would be possible is if there was some type of thread-local stack that explicitly prohibits this from happening (as the nested tx would close the parent). It's no big deal if it can't happen, but would certainly be great if it could. Your thoughts would be appreciated. - Andrew. -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] API CRUD interface for application ?
Why bother with Java? This sounds like a simple system that could be done with about 10 lines of Python and the remote_api. Jeff On Sun, Oct 10, 2010 at 2:28 PM, Maxim Veksler ma...@vekslers.org wrote: Hello, The application we run is a backend online service and has no GUI. We some how need to be able to upload new content / update existing datastore entity records. The database model is relatively simple: 1 to many relationships on all of the kinds. I would be happy to use learn about a library / some API configuration option to expose an interface so that external code can do the CRUD logic. Is there any support for this in GAE / other library that runs on GAE? If this plays any role in your suggestions: We're super focused on response times so: We currently use low level data store API. I actually tried Objectify but found even it to be an over kill for our needs. I also deleted all the jars the were added by GAE eclipse plugin but are not used by the code. Actually the list of jars used by the application consists of: ls war/WEB-INF/lib/ appengine-api-1.0-sdk-1.3.7.jar appengine-jsr107cache-1.3.7.jar jackson-core-asl-1.6.0.jar jsr107cache-1.1.jar appengine-api-labs-1.3.7.jar EyeViewUtils-1.0.1-SNAPSHOT.jar jackson-mapper-asl-1.6.0.jar log4j-1.2.16.jar Any recommendations / personal experience with this issue / pointers about correct design of the interface / what technology to use and co. are highly welcome and appreciated. Thank you, Maxim. -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] protobuf storage with JDO
I'm not entirely certain what you are asking, but while Objectify
doesn't have a special annotation that will turn a field into a
protobuf, you can pretty easily do this yourself with @PostLoad and
@PrePersist lifecycle callbacks:
class MyEntity {
@Transient ComplexThing thing;
byte[] thingBuf;
@PrePersist void onSave() { thingBuf = pbfSerialize(thing); }
@PostLoad void onLoad() { thing = pbfDeserialize(thingBuf); }
}
Jeff
On Thu, Oct 14, 2010 at 3:29 PM, Guillaume B.
guillaume.brus...@gmail.com wrote:
Hello,
I make a basic application that store simple java object using objectify
I also make a spring service that create and return protobuf object
as the protobuf object is nearly the same that the object that I store in
big table
I wonder if there was a standard way to store protobuf object in the
datastore
as objectify and JDO use annotation and that I will not anoted generated
protobuf object
perhaps someone as a sample / tutorial of the AddressBook protobuf in
appengine that store object in the datastore
--
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 google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
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 google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] alishascardwall.com Forbidden 403 Error
I purchased a domain alishascardwall.com for my appid: alishascardwall and removed Sites and enabled www mapping for my appid. While alishascardwall.appspot.com works fine alishascardwall.com gives a Forbidden 403 error. I've created 2 other domains for my other apps and I have followed the same steps exactly. The system doesn't allow me to remove the www mapping or remove the GAE service from my account. So I think something got corrupted in the process. Need some help getting this working. -- 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 google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
