[appengine-java] DatastoreNeedIndexException
I now have problem with com.google.appengine.api.datastore.DatastoreNeedIndexException: no matching index found... And, the admin Dashboard shown === Number of Indexes 100% 100%199 of 200 === the application is a relatively simple, yet got such problem. i wonder how many datastore indexes u guys have. pls share it here. p/s: google appengine team, can increase the quota for index ...? -- 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: Disappointment about JPA relationships :(
Hi Matthieu, You are right, you need some conditioning and then you need to work around the limitations of working with relationships around JPA. Then finally you tend to realize more and more that may be you are better off with unowned relationships Here are the issues that we faced and tried to resolve http://wp.me/pNh6u-6b Regards | Vikas www.inphina.com On Oct 23, 9:01 pm, Matthieu Bertin wrote: > Hello, > > I'm just here because i feel i need to rant a little. I came here > expecting way too much. I'm of course blaming me for being way too > optimistic but i also believe ranting against google is somehow > justifiable, and i'll explain why. > > I've started porting an application on Google App engine and i'm now > sick of discovering exceptions like : > > - Detected attempt to establish PictureThread(28) as the parent of > Picture(27) but the entity identified by Picture(27) has already been > persisted without a parent. A parent cannot be established or changed > once an object has been persisted > - cannot operate on two differents types of entities in the same > request/transaction'. Your documentation has headed me in the wrong > direction; all you mention is 'unowned relationships' and 'many-to-many > relationships' are not supported. > Please fix that. Give us the real limitations on the documentation! > There is no mention of "one to one" limitations or 'handling multiple > entities in same transaction' limitations anywhere. > > It would totally be understandable not to mention theses limitations > when JDBC APIs were created, but nowadays, when you mention 'JPA', this > kind of limitations HAVE to be mentionned. -- 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] 1.3.8 Console Logging Issue
Hello, I upgraded my project from 1.3.4 to 1.3.8. After the upgrade, the console fails to log. If I switch back to 1.3.4, the console logs properly. I am on a 64-bit Windows Vista environment, running Eclipse 3.4.2 w/ (MyEclipse and Instantiations GWT tools) 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] Recurring tasks
Hie Guys Our application manages a list of blood donors. Time to time these blood donors are unreachable so the administrators can mark such blood donors as inactive. However, these blood donors should be active again after 1 day automatically. How should we achieve this? ?In regular J2EE apis we can write scheduler classes to do the same. What is the option in GAE? Are there any limitations? I went through a bit and feel like task queues are the way. But I am not sure? If yes then for above scenario how should it be done? Thankx and Regards Vik Founder www.sakshum.com www.sakshum.blogspot.com -- 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] Mapreduce gives error when I execute job on appengine cloud?
Have you created a descending index on the key of the entity group you try to map ? (required for mapreduce jobs) From: suersh babu Reply-To: Date: Fri, 22 Oct 2010 14:52:17 +0530 To: , Subject: [appengine-java] Mapreduce gives error when I execute job on appengine cloud? Hi, I am using mapreduce to run the job but when I try to run the job in mapreduce by clicking run button I am getting error like this : Error -- java.lang.RuntimeException: Full stack trace is available in the server logs. Message: Got an IOException while trying to make splits In my local machine mapreduce works fine, It executed the job without any error. I am using app engine sdk 1.3.8 Following is the server log generated by my application for the mapreduce error. 1. 10-22 02:02AM 49.783 2. com.google.appengine.tools.mapreduce.DatastoreInputFormat getSplits: Getting input splits for: Payment 3. 4. E 10-22 02:02AM 49.810 5. com.google.appengine.tools.mapreduce.MapReduceServlet handleCommand: Got exception while running command 6. java.lang.RuntimeException: Got an IOException while trying to make splits 7. at com.google.appengine.tools.mapreduce.MapReduceServlet.handleStart(MapReduceS ervlet.java:747) 8. at com.google.appengine.tools.mapreduce.MapReduceServlet.handleStartJob(MapRedu ceServlet.java:364) 9. at com.google.appengine.tools.mapreduce.MapReduceServlet.handleCommand(MapReduc eServlet.java:247) 10. at com.google.appengine.tools.mapreduce.MapReduceServlet.doPost(MapReduceServle t.java:184) 11. at javax.servlet.http.HttpServlet.service(HttpServlet.java:713) 12. at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) 13. at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) 14. at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler .java:1166) 15. at com.veersoft.filter.ResetUserMessagesAndErrorsFilter.doFilter(ResetUserMessa gesAndErrorsFilter.java:28) 16. at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler .java:1157) 17. at com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlob UploadFilter.java:97) 18. at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler .java:1157) 19. at com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFi lter.java:35) 20. at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler .java:1157) 21. at com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(Transa ctionCleanupFilter.java:43) 22. at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler .java:1157) 23. at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) 24. at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) 25. at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) 26. at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) 27. at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) 28. at com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHa ndlerMap.java:238) 29. at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) 30. at org.mortbay.jetty.Server.handle(Server.java:326) 31. at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) 32. at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnectio n.java:923) 33. at com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcReque stParser.java:76) 34. at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) 35. at com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest (JettyServletEngineAdapter.java:135) 36. at com.google.apphosting.runtime.JavaRuntime.handleRequest(JavaRuntime.java:261 ) 37. at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingReque st(RuntimePb.java:8486) 38. at com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingReque st(RuntimePb.java:8484) 39. at com.google.net.rpc.impl.BlockingApplicationHandler.handleRequest(BlockingApp licationHandler.java:24) 40. at com.google.net.rpc.impl.RpcUtil.runRpcInApplication(RpcUtil.java:418) 41. at com.google.net.rpc.impl.Server$RpcTask.runInContext(Server.java:572) 42. at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java :448) 43. at com.google.tracing.TraceContext.runInContext(TraceContext.java:688) 44. at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedC ontextNoUnref(TraceContext.java:326) 45. at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedC ontext(TraceContext.java:318) 46. at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:4 46) 47. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:11 10) 48. at java.util.concurrent.ThreadPoolEx
Re: [appengine-java] Mapreduce gives error when I execute job on appengine cloud?
*Sir,Thanks for your guide lines. Thankyou. * On Mon, Oct 25, 2010 at 1:18 AM, Cyrille Vincey wrote: > Have you created a descending index on the key of the entity group you try > to map ? > (required for mapreduce jobs) > > From: suersh babu > Reply-To: > Date: Fri, 22 Oct 2010 14:52:17 +0530 > To: , < > google-appeng...@googlegroups.com> > Subject: [appengine-java] Mapreduce gives error when I execute job on > appengine cloud? > > Hi, > > I am using mapreduce to run the job but when I try to run the job in > mapreduce by clicking run button I am getting error like this : > Error -- java.lang.RuntimeException: Full stack trace is available in the > server logs. Message: Got an IOException while trying to make splits > > In my local machine mapreduce works fine, It executed the job without any > error. > > I am using app engine sdk 1.3.8 > > Following is the server log generated by my application for the mapreduce > error. > >1. 10-22 02:02AM 49.783 > >com.google.appengine.tools.mapreduce.DatastoreInputFormat getSplits: > Getting input splits for: Payment > >2. E 10-22 02:02AM 49.810 > >com.google.appengine.tools.mapreduce.MapReduceServlet handleCommand: Got > exception while running command >java.lang.RuntimeException: Got an IOException while trying to make splits > at > com.google.appengine.tools.mapreduce.MapReduceServlet.handleStart(MapReduceServlet.java:747) > at > com.google.appengine.tools.mapreduce.MapReduceServlet.handleStartJob(MapReduceServlet.java:364) > at > com.google.appengine.tools.mapreduce.MapReduceServlet.handleCommand(MapReduceServlet.java:247) > at > com.google.appengine.tools.mapreduce.MapReduceServlet.doPost(MapReduceServlet.java:184) > 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.veersoft.filter.ResetUserMessagesAndErrorsFilter.doFilter(ResetUserMessagesAndErrorsFilter.java:28) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) > at > com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:97) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) > at > com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:35) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) > at > com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43) > at > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) > at > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > at > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) > at > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) > at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) > at > com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:238) > at > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) > at org.mortbay.jetty.Server.handle(Server.java:326) > at > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) > at > org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923) > at > com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcRequestParser.java:76) > at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) > at > com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:135) > at > com.google.apphosting.runtime.JavaRuntime.handleRequest(JavaRuntime.java:261) > at > com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8486) > at > com.google.apphosting.base.RuntimePb$EvaluationRuntime$6.handleBlockingRequest(RuntimePb.java:8484) > 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(Tra
Re: [appengine-java] Recurring tasks
*Sir, Thanks for your guide lines. Thank you. * On Sun, Oct 24, 2010 at 10:41 PM, Vik wrote: > Hie Guys > > Our application manages a list of blood donors. Time to time these blood > donors are unreachable so the administrators can mark such blood donors as > inactive. > > However, these blood donors should be active again after 1 day > automatically. How should we achieve this? ?In regular J2EE apis we can > write scheduler classes to do the same. > What is the option in GAE? Are there any limitations? > > I went through a bit and feel like task queues are the way. But I am not > sure? If yes then for above scenario how should it be done? > > > Thankx and Regards > > Vik > Founder > www.sakshum.com > www.sakshum.blogspot.com > > -- > 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] Re: Disappointment about JPA relationships :(
*Sir, Thanks for your guidelines. Thankyou. * On Sun, Oct 24, 2010 at 5:14 PM, Vikas Hazrati wrote: > Hi Matthieu, > > You are right, you need some conditioning and then you need to work > around the limitations of working with relationships around JPA. Then > finally you tend to realize more and more that may be you are better > off with unowned relationships > > Here are the issues that we faced and tried to resolve > http://wp.me/pNh6u-6b > > Regards | Vikas > www.inphina.com > > On Oct 23, 9:01 pm, Matthieu Bertin wrote: > > Hello, > > > > I'm just here because i feel i need to rant a little. I came here > > expecting way too much. I'm of course blaming me for being way too > > optimistic but i also believe ranting against google is somehow > > justifiable, and i'll explain why. > > > > I've started porting an application on Google App engine and i'm now > > sick of discovering exceptions like : > > > > - Detected attempt to establish PictureThread(28) as the parent of > > Picture(27) but the entity identified by Picture(27) has already been > > persisted without a parent. A parent cannot be established or changed > > once an object has been persisted > > - cannot operate on two differents types of entities in the same > > request/transaction'. Your documentation has headed me in the wrong > > direction; all you mention is 'unowned relationships' and 'many-to-many > > relationships' are not supported. > > Please fix that. Give us the real limitations on the documentation! > > There is no mention of "one to one" limitations or 'handling multiple > > entities in same transaction' limitations anywhere. > > > > It would totally be understandable not to mention theses limitations > > when JDBC APIs were created, but nowadays, when you mention 'JPA', this > > kind of limitations HAVE to be mentionned. > > -- > 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] Disappointment about JPA relationships :(
> I'm just here because i feel i need to rant a little. I came here expecting > way too much. Been there with JDO -- the docs are not adequate. I don't know your exact requirements but I suspect you'll find many on this list who found objectify to be the "simplest convenient interface to the Google App Engine datastore". http://code.google.com/p/objectify-appengine/ Shawn -- 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] appengine and domain
can i have this. app1.abc.com --> point to --> app1.appspot.com app2.abc.com --> point to --> app2.appspot.com any help or guide? -- 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: appengine and domain
Hi, see http://code.google.com/appengine/docs/domain.html: it is what you need. Did it myself and it was fine. didier On Oct 25, 5:06 am, pman wrote: > can i have this. > > app1.abc.com --> point to --> app1.appspot.com > > app2.abc.com --> point to --> app2.appspot.com > > any help or guide? -- 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: Recurring tasks
Hi Vik, Tasks scheduled via cron.xml is the way I would go: http://code.google.com/appengine/docs/java/config/cron.html I would schedule a task every minute, make a query on the deadline for donors and then do what has to be done. didier On Oct 24, 7:11 pm, Vik wrote: > Hie Guys > > Our application manages a list of blood donors. Time to time these blood > donors are unreachable so the administrators can mark such blood donors as > inactive. > > However, these blood donors should be active again after 1 day > automatically. How should we achieve this? ?In regular J2EE apis we can > write scheduler classes to do the same. > What is the option in GAE? Are there any limitations? > > I went through a bit and feel like task queues are the way. But I am not > sure? If yes then for above scenario how should it be done? > > Thankx and Regards > > Vik > Founderwww.sakshum.comwww.sakshum.blogspot.com -- 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] Re: Recurring tasks
Hie Thanks for the response. I am confused a bit. If cron job does the scheduling then what Task Queue does? Thankx and Regards Vik Founder www.sakshum.com www.sakshum.blogspot.com On Mon, Oct 25, 2010 at 8:51 AM, Didier Durand wrote: > Hi Vik, > > Tasks scheduled via cron.xml is the way I would go: > http://code.google.com/appengine/docs/java/config/cron.html > > I would schedule a task every minute, make a query on the deadline for > donors and then do what has to be done. > > didier > > On Oct 24, 7:11 pm, Vik wrote: > > Hie Guys > > > > Our application manages a list of blood donors. Time to time these blood > > donors are unreachable so the administrators can mark such blood donors > as > > inactive. > > > > However, these blood donors should be active again after 1 day > > automatically. How should we achieve this? ?In regular J2EE apis we can > > write scheduler classes to do the same. > > What is the option in GAE? Are there any limitations? > > > > I went through a bit and feel like task queues are the way. But I am not > > sure? If yes then for above scenario how should it be done? > > > > Thankx and Regards > > > > Vik > > Founderwww.sakshum.comwww.sakshum.blogspot.com > > -- > 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] Re: Recurring tasks
Hi, I see different purposes for the 2: - cron tasks are the tasks I always want to do for sure - tasks via API are tasks that I schedule programmatically when needed and triggered by event that I can't predict in advance. I see personally 2 other purposes for API tasks: a) when I run a task and it comes close to the 30s limit, I pause it, serialize its context and schedule a task with this context. When the task starts, it's in fact a restart with another 30s credit for running b) I also tasks in context of transactions if I want to be sure that the action of the task is done (i.e datastore writes) even if the transactions fails -> for example, store errors in datastore for later analysis for a failing transaction / program, etc. regards didier On Oct 25, 6:23 am, Vik wrote: > Hie Thanks for the response. > > I am confused a bit. If cron job does the scheduling then what Task Queue > does? > > Thankx and Regards > > Vik > Founderwww.sakshum.comwww.sakshum.blogspot.com > > On Mon, Oct 25, 2010 at 8:51 AM, Didier Durand wrote: > > > Hi Vik, > > > Tasks scheduled via cron.xml is the way I would go: > >http://code.google.com/appengine/docs/java/config/cron.html > > > I would schedule a task every minute, make a query on the deadline for > > donors and then do what has to be done. > > > didier > > > On Oct 24, 7:11 pm, Vik wrote: > > > Hie Guys > > > > Our application manages a list of blood donors. Time to time these blood > > > donors are unreachable so the administrators can mark such blood donors > > as > > > inactive. > > > > However, these blood donors should be active again after 1 day > > > automatically. How should we achieve this? ?In regular J2EE apis we can > > > write scheduler classes to do the same. > > > What is the option in GAE? Are there any limitations? > > > > I went through a bit and feel like task queues are the way. But I am not > > > sure? If yes then for above scenario how should it be done? > > > > Thankx and Regards > > > > Vik > > > Founderwww.sakshum.comwww.sakshum.blogspot.com > > > -- > > 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] Feature Request: Restore prepared query from a cursor
Hi App Engine team, the Cursor stores the full state of a prepared query to check if it matches the query when applied and raise an exception if this is not the case. Now the usual use case is that during a paging operation the cursor is transferred between client (e.g HTML page, JSP, ...) and server. The server restores the cursor from the string encoding and applies it to the PreparedQuery. As the server is stateless the server side needs to restore the prepared query somehow either by caching it somewhere or by reconstructing it from the application context (I take the reconstruction approach) Now I wonder if you could avoid caching/reconstructing the query if you have the cursor, because apparently the cursor contains the full state of the query. Wouldn't it be a trivial change in the API of the SDK to introduce a method on the Cursor class like: PreparedQuery getQuery() Then you could have on the server have code like this: Cursor decodedCursor = Cursor.fromWebSafeString(encodedCursor); PreparedQuery preparedQuery = decodedCursor.getPreparedQuery(); List nextBatch = preparedQuery.asQueryResultList(withLimit(20).cursor(decoded)); Not sure if I missed something but this seems to be trivial and it would give so much convenience... Comments? -- 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: 1.3.8 Console Logging Issue
Similar here. Now only logs WARNING and ERROR. Logging properties set to INFO and prior to 1.3.8 upgrade INFO logged fine. Have configuration procedures been changed or something? Window 7 32bit Eclipse 3.5 and 3.6 -- 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.