[appengine-java] Re: big table parent-child
Hi, Answers to your questions are in http://code.google.com/appengine/docs/java/datastore/transactions.html#Using_Transactions To do what you want, you only have to delete the book to remove it from entity group A and recreate it in entity group B (assuming the root entity - cat B - has been created already else you need to create it before) Deleting then recreating allow the datastore to move your entity from the ds server for cat A to the ds server for cat B in order to provide the apppropriate scalability NB: you won't be able to do both ops in 1 transaction as 1 transaction can only touch entities from a single entity group. You need to do that via 2 transactions. The best (only ?) way to continue guaranteeing integrity of your data in to do it via a task for the second action (recreate) that you make transactional with the 1st (delete). regards didier On Dec 6, 7:57 am, asianCoolz second.co...@gmail.com wrote: if have i have pojo like categoryA - subcategoryA-- book relationship. subcategoryA is child of parent categoryA. book is child of subcategoryA in this case, everything is inside same entitygroup if i need to move 'book' to another subcategory-B. i need to delete subcategoryA and categoryA, and recreate categoryA - subcategoryA-- without book ? and recreate categoryb - subcategoryb-- book ,other-book, other-book3 ? -- 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: Local datastore empty after updating to SDK 1.4.0
Hi Fabrizio, Yes, I do delete the local datastore and create it again. I delete the local datastore by following the instructions given in: http://code.google.com/intl/en/appengine/docs/java/tools/devserver.html#Using_the_Datastore I then create it again by launching the development application server and then populating my local datastore using my web application. Cheers, Ian On Dec 6, 7:07 am, Fabrizio Accatino fht...@gmail.com wrote: Sorry Ian, I don't understand. Do you delete the local datastore and create it again? If yes, how? Fabrizio On Sun, Dec 5, 2010 at 5:16 PM, Ian Marshall ianmarshall...@gmail.comwrote: I have a test local datastore. I also have a procedure now to delete this whenever I install a new GAE/J SDK. This solved my problem of disappearing test data. -- 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: Is warm up requests enabled or disabled by default? (Documentation disagrees)
Hi Maxim, good point, I was asking myself, too. I do not have a app.yaml and I am not sure if I do have to add one and what to put in. Will it override appengine-web.xml and web.xml? Would be good to get some clarification. Maybe it can also be configured in appengine-web.xml? Cheers, Toby On Dec 5, 9:48 pm, Maxim Veksler ma...@vekslers.org wrote: Hello Guys, This pagehttp://code.google.com/appengine/docs/java/config/appconfig.html#Warm... says *Warming requests are also enabled by default if you configured your Java application with app.yaml. For details, please refer to Java Application Configuration Using app.yamlhttp://code.google.com/appengine/docs/java/configyaml/appconfig_yaml .* This pagehttp://code.google.com/appengine/docs/java/configyaml/appconfig_yaml says *In Java applications configured with app.yaml, warming requests are disabled by default. To enable them, add the warmup argument to the inbound_servicesdirective:* So which of the two is it? I'm configuration my application with app.yaml and warm ups are one of our definitely wanted features. Logic says it's enabled by default, but lets be sure. Please don't do the mistake of allowsing different default behaviour based on configuration method for the same functionality. This will confuse the hell out of people jumping between appengine-web.xml app.yaml. Thanks, 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] Query and fetch more than 15000 objects in single query,best way to do it.
I have gone through many articles declaring 1000 limit for single query has been removed but still i don't want to stuck into query fetch and deadline exceptions so can you please suggest me the best way to query and search through around 15000 objects and sometimes fetching all objects at a go.Right now am looking into Cursors,are Cursors helpful in such cases? Thank you. Sagar Misal. -- 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: Query and fetch more than 15000 objects in single query,best way to do it.
Hi, If i had to that, I would: a) test the classical all-at-once fetch for the 15000 entities b) Then, if too long, I would try to break up the task and make it faster via Task. Tasks will provide you with parallel execution so you may get much faster. I would organize each subquery (as run asby a task) per entity-group (supposing that your entities are grouped as GAE permits it) so that 1 subquery goes to a single datastore server to avoid concurrency race in data fetching. This separation will also leverage the scalability / performances offered by App Engine. Of course, you will need to re-synchronize the subqueries at the end of all tasks to put all results back together. So, all of this would represent quite some coding. As I didn't try yet personally (it's only my thoughts), it's interesting to see if other members of this forum have something simpler to propose. regards didier On Dec 6, 11:36 am, sagar misal sagar1982mi...@gmail.com wrote: I have gone through many articles declaring 1000 limit for single query has been removed but still i don't want to stuck into query fetch and deadline exceptions so can you please suggest me the best way to query and search through around 15000 objects and sometimes fetching all objects at a go.Right now am looking into Cursors,are Cursors helpful in such cases? Thank you. Sagar Misal. -- 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: Query and fetch more than 15000 objects in single query,best way to do it.
Checkout http://code.google.com/p/appengine-mapreduce/ On Mon, Dec 6, 2010 at 6:46 AM, Didier Durand durand.did...@gmail.comwrote: Hi, If i had to that, I would: a) test the classical all-at-once fetch for the 15000 entities b) Then, if too long, I would try to break up the task and make it faster via Task. Tasks will provide you with parallel execution so you may get much faster. I would organize each subquery (as run asby a task) per entity-group (supposing that your entities are grouped as GAE permits it) so that 1 subquery goes to a single datastore server to avoid concurrency race in data fetching. This separation will also leverage the scalability / performances offered by App Engine. Of course, you will need to re-synchronize the subqueries at the end of all tasks to put all results back together. So, all of this would represent quite some coding. As I didn't try yet personally (it's only my thoughts), it's interesting to see if other members of this forum have something simpler to propose. regards didier On Dec 6, 11:36 am, sagar misal sagar1982mi...@gmail.com wrote: I have gone through many articles declaring 1000 limit for single query has been removed but still i don't want to stuck into query fetch and deadline exceptions so can you please suggest me the best way to query and search through around 15000 objects and sometimes fetching all objects at a go.Right now am looking into Cursors,are Cursors helpful in such cases? Thank you. Sagar Misal. -- 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. -- Guit: Elegant, beautiful, modular and *production ready* gwt applications. http://code.google.com/p/guit/ -- 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: 1.4 eclipse plugin
Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type An error occurred at line: 24 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 31 in the generated java file _el_expressionfactory cannot be resolved An error occurred at line: 31 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 31 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file _jsp_annotationprocessor cannot be resolved An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 32 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 38 in the generated java file HttpServletRequest cannot be resolved to a type An error occurred at line: 38 in the generated java file HttpServletResponse cannot be resolved to a type An error occurred at line: 39 in the generated java file ServletException cannot be resolved to a type An error occurred at line: 41 in the generated java file PageContext cannot be resolved to a type An error occurred at line: 42 in the generated java file HttpSession cannot be resolved to a type An error occurred at line: 43 in the generated java file ServletContext cannot be resolved to a type An error occurred at line: 44 in the generated java file ServletConfig cannot be resolved to a type An error occurred at line: 45 in the generated java file JspWriter cannot be resolved to a type An error occurred at line: 47 in the generated java file JspWriter cannot be resolved to a type An error occurred at line: 48 in the generated java file PageContext cannot be resolved to a type An error occurred at line: 53 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 1,315 in the generated java file SkipPageException cannot be resolved to a type An error occurred at line: 1,322 in the generated java file _jspxFactory cannot be resolved Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl er.java: 92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: 330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: 439) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) at
[appengine-java] Re: big table parent-child
how about, if i denormalized everything . Mean book as id of subcategory. One entitygroup will only has one entity. any impact on that if i have too many separate entitygroups...? is this good practice in bigtable? if i do aware if i do this way, not be able to use transactional. can you elaborate The best (only ?) way to continue guaranteeing integrity of your data in to do it via a task for the second action (recreate) that you make transactional with the 1st (delete). -- do you mean i should re-created book in subcategoryB first before do delete book from subcategoryA ? what do you mean task, using background job ? any example? -- 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: Local datastore empty after updating to SDK 1.4.0
I have just found that my local datastore test data seems to be unaffected so far by my upgrading my GAE/J SDK this morning from 1.3.8 to 1.4.0. Of course, even if my test data should prove unaffected by the latest change in SDK, there is no guarantee of such an outcome for any future release. That being said, I produce my test data when conducting test scripts for my web app, so generating a fresh set of test datastore data by going through these tests for a new SDK is no bad thing anyway! On Dec 6, 9:21 am, Ian Marshall ianmarshall...@gmail.com wrote: Hi Fabrizio, Yes, I do delete the local datastore and create it again. I delete the local datastore by following the instructions given in: http://code.google.com/intl/en/appengine/docs/java/tools/devserver.ht... I then create it again by launching the development application server and then populating my local datastore using my web application. Cheers, Ian On Dec 6, 7:07 am, Fabrizio Accatino fht...@gmail.com wrote: Sorry Ian, I don't understand. Do you delete the local datastore and create it again? If yes, how? Fabrizio On Sun, Dec 5, 2010 at 5:16 PM, Ian Marshall ianmarshall...@gmail.comwrote: I have a test local datastore. I also have a procedure now to delete this whenever I install a new GAE/J SDK. This solved my problem of disappearing test data. -- 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: big table parent-child
Hi, By task, I mean http://code.google.com/appengine/docs/java/taskqueue/overview.html About transactionnality of your changes: you have to make sure that when you delete, it's gauranteed to be recreated. The only way to do so is to start a task bound to the transaction where you delete. See http://code.google.com/appengine/docs/java/taskqueue/overview.html#Tasks_within_Transactions You can go the way 1 entity only per entity group (i.e then no entity group per se) but then it means that you lose the transactionnality service of GAE: i.e no way to guarantee that your changes are done all at once or not at all. It's very important to keep transactionnality if you want to guarantee integrity of your data on the long run. For transactions, read http://code.google.com/appengine/docs/java/datastore/transactions.html regards didier On Dec 6, 2:34 pm, asianCoolz second.co...@gmail.com wrote: how about, if i denormalized everything . Mean book as id of subcategory. One entitygroup will only has one entity. any impact on that if i have too many separate entitygroups...? is this good practice in bigtable? if i do aware if i do this way, not be able to use transactional. can you elaborate The best (only ?) way to continue guaranteeing integrity of your data in to do it via a task for the second action (recreate) that you make transactional with the 1st (delete). -- do you mean i should re-created book in subcategoryB first before do delete book from subcategoryA ? what do you mean task, using background job ? any example? -- 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] Setting up Warmup Requests
Hey I'm not sure if it's just me but I really cannot make sense of the documentation explaining how to set up warm up requests. http://code.google.com/appengine/docs/java/config/appconfig.html#Warming_Requests It states Warming requests are enabled by default for all Java applications. and then precedes to explain how to set them up. Do I have to do anything or don't I? My app is configured with the web.xml file and having read the documentation it says I can implement warm up requests via an optional warming-requests-enabled element in appengine-web.xml If warm up requests are enabled by default, do I need to do this? Apologies if I am being dumb but the more times I read it the more confused I get. 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.
Re: [appengine-java] Setting up Warmup Requests
If you have a Java application that you have configured with an appengine-web.xml file[1], you just need to redeploy with the 1.4.0 SDK to enable warming requests. However, to get the most benefit from this feature you may want to cause more of your initialization code to run during the warmup request. As the documentation states, there are a few ways to do this. If you have any servlets that do a non-trivial amount of setup in their init() method (e.g. initializing an IoC container like Spring or Guice) you will want to mark them as load-on-startup. You could also implement your own servlet to do custom initialization or to execute common code-paths in your application code to trigger class loading and hotspot compilation early. Does that clear things up? -- Don [1] Some Java applications (e.g. JRuby apps) are configured with an app.yaml file instead. On Mon, Dec 6, 2010 at 9:22 AM, mscwd01 mscw...@gmail.com wrote: Hey I'm not sure if it's just me but I really cannot make sense of the documentation explaining how to set up warm up requests. http://code.google.com/appengine/docs/java/config/appconfig.html#Warming_Requests It states Warming requests are enabled by default for all Java applications. and then precedes to explain how to set them up. Do I have to do anything or don't I? My app is configured with the web.xml file and having read the documentation it says I can implement warm up requests via an optional warming-requests-enabled element in appengine-web.xml If warm up requests are enabled by default, do I need to do this? Apologies if I am being dumb but the more times I read it the more confused I get. 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.
[appengine-java] Re: Setting up Warmup Requests
That clears things up nicely. I'll just add warming-requests-enabled to my appengine-web.xml and redeploy. Many thanks On Dec 6, 3:52 pm, Don Schwarz schwa...@google.com wrote: If you have a Java application that you have configured with an appengine-web.xml file[1], you just need to redeploy with the 1.4.0 SDK to enable warming requests. However, to get the most benefit from this feature you may want to cause more of your initialization code to run during the warmup request. As the documentation states, there are a few ways to do this. If you have any servlets that do a non-trivial amount of setup in their init() method (e.g. initializing an IoC container like Spring or Guice) you will want to mark them as load-on-startup. You could also implement your own servlet to do custom initialization or to execute common code-paths in your application code to trigger class loading and hotspot compilation early. Does that clear things up? -- Don [1] Some Java applications (e.g. JRuby apps) are configured with an app.yaml file instead. On Mon, Dec 6, 2010 at 9:22 AM, mscwd01 mscw...@gmail.com wrote: Hey I'm not sure if it's just me but I really cannot make sense of the documentation explaining how to set up warm up requests. http://code.google.com/appengine/docs/java/config/appconfig.html#Warm... It states Warming requests are enabled by default for all Java applications. and then precedes to explain how to set them up. Do I have to do anything or don't I? My app is configured with the web.xml file and having read the documentation it says I can implement warm up requests via an optional warming-requests-enabled element in appengine-web.xml If warm up requests are enabled by default, do I need to do this? Apologies if I am being dumb but the more times I read it the more confused I get. 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%2B 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: Setting up Warmup Requests
Oh I just realised, the docs are wrong it's not: warming-requests-enabledtrue/warming-requests-enabled but in fact: warmup-requests-enabledtrue/warmup-requests-enabled Just in case that catches others out. On Dec 6, 4:01 pm, mscwd01 mscw...@gmail.com wrote: That clears things up nicely. I'll just add warming-requests-enabled to my appengine-web.xml and redeploy. Many thanks On Dec 6, 3:52 pm, Don Schwarz schwa...@google.com wrote: If you have a Java application that you have configured with an appengine-web.xml file[1], you just need to redeploy with the 1.4.0 SDK to enable warming requests. However, to get the most benefit from this feature you may want to cause more of your initialization code to run during the warmup request. As the documentation states, there are a few ways to do this. If you have any servlets that do a non-trivial amount of setup in their init() method (e.g. initializing an IoC container like Spring or Guice) you will want to mark them as load-on-startup. You could also implement your own servlet to do custom initialization or to execute common code-paths in your application code to trigger class loading and hotspot compilation early. Does that clear things up? -- Don [1] Some Java applications (e.g. JRuby apps) are configured with an app.yaml file instead. On Mon, Dec 6, 2010 at 9:22 AM, mscwd01 mscw...@gmail.com wrote: Hey I'm not sure if it's just me but I really cannot make sense of the documentation explaining how to set up warm up requests. http://code.google.com/appengine/docs/java/config/appconfig.html#Warm... It states Warming requests are enabled by default for all Java applications. and then precedes to explain how to set them up. Do I have to do anything or don't I? My app is configured with the web.xml file and having read the documentation it says I can implement warm up requests via an optional warming-requests-enabled element in appengine-web.xml If warm up requests are enabled by default, do I need to do this? Apologies if I am being dumb but the more times I read it the more confused I get. 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%2B 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: Setting up Warmup Requests
Ah, thanks. We'll get that fixed. However, true is the default so you can just leave this out entirely. On Mon, Dec 6, 2010 at 10:11 AM, mscwd01 mscw...@gmail.com wrote: Oh I just realised, the docs are wrong it's not: warming-requests-enabledtrue/warming-requests-enabled but in fact: warmup-requests-enabledtrue/warmup-requests-enabled Just in case that catches others out. On Dec 6, 4:01 pm, mscwd01 mscw...@gmail.com wrote: That clears things up nicely. I'll just add warming-requests-enabled to my appengine-web.xml and redeploy. Many thanks On Dec 6, 3:52 pm, Don Schwarz schwa...@google.com wrote: If you have a Java application that you have configured with an appengine-web.xml file[1], you just need to redeploy with the 1.4.0 SDK to enable warming requests. However, to get the most benefit from this feature you may want to cause more of your initialization code to run during the warmup request. As the documentation states, there are a few ways to do this. If you have any servlets that do a non-trivial amount of setup in their init() method (e.g. initializing an IoC container like Spring or Guice) you will want to mark them as load-on-startup. You could also implement your own servlet to do custom initialization or to execute common code-paths in your application code to trigger class loading and hotspot compilation early. Does that clear things up? -- Don [1] Some Java applications (e.g. JRuby apps) are configured with an app.yaml file instead. On Mon, Dec 6, 2010 at 9:22 AM, mscwd01 mscw...@gmail.com wrote: Hey I'm not sure if it's just me but I really cannot make sense of the documentation explaining how to set up warm up requests. http://code.google.com/appengine/docs/java/config/appconfig.html#Warm... It states Warming requests are enabled by default for all Java applications. and then precedes to explain how to set them up. Do I have to do anything or don't I? My app is configured with the web.xml file and having read the documentation it says I can implement warm up requests via an optional warming-requests-enabled element in appengine-web.xml If warm up requests are enabled by default, do I need to do this? Apologies if I am being dumb but the more times I read it the more confused I get. 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.comgoogle-appengine-java%2B 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.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] Re: Setting up Warmup Requests
Even better, thanks On Dec 6, 4:12 pm, Don Schwarz schwa...@google.com wrote: Ah, thanks. We'll get that fixed. However, true is the default so you can just leave this out entirely. On Mon, Dec 6, 2010 at 10:11 AM, mscwd01 mscw...@gmail.com wrote: Oh I just realised, the docs are wrong it's not: warming-requests-enabledtrue/warming-requests-enabled but in fact: warmup-requests-enabledtrue/warmup-requests-enabled Just in case that catches others out. On Dec 6, 4:01 pm, mscwd01 mscw...@gmail.com wrote: That clears things up nicely. I'll just add warming-requests-enabled to my appengine-web.xml and redeploy. Many thanks On Dec 6, 3:52 pm, Don Schwarz schwa...@google.com wrote: If you have a Java application that you have configured with an appengine-web.xml file[1], you just need to redeploy with the 1.4.0 SDK to enable warming requests. However, to get the most benefit from this feature you may want to cause more of your initialization code to run during the warmup request. As the documentation states, there are a few ways to do this. If you have any servlets that do a non-trivial amount of setup in their init() method (e.g. initializing an IoC container like Spring or Guice) you will want to mark them as load-on-startup. You could also implement your own servlet to do custom initialization or to execute common code-paths in your application code to trigger class loading and hotspot compilation early. Does that clear things up? -- Don [1] Some Java applications (e.g. JRuby apps) are configured with an app.yaml file instead. On Mon, Dec 6, 2010 at 9:22 AM, mscwd01 mscw...@gmail.com wrote: Hey I'm not sure if it's just me but I really cannot make sense of the documentation explaining how to set up warm up requests. http://code.google.com/appengine/docs/java/config/appconfig.html#Warm... It states Warming requests are enabled by default for all Java applications. and then precedes to explain how to set them up. Do I have to do anything or don't I? My app is configured with the web.xml file and having read the documentation it says I can implement warm up requests via an optional warming-requests-enabled element in appengine-web.xml If warm up requests are enabled by default, do I need to do this? Apologies if I am being dumb but the more times I read it the more confused I get. 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%2B unsubscr...@googlegroups.comgoogle-appengine-java%2B 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.comgoogle-appengine-java%2B 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: 1.4 eclipse plugin
This still doesn't solve the issue for me, mapping a servlet url pattern to a jsp file always fails... On Dec 6, 1:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type An error occurred at line: 24 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 31 in the generated java file _el_expressionfactory cannot be resolved An error occurred at line: 31 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 31 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file _jsp_annotationprocessor cannot be resolved An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 32 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 38 in the generated java file HttpServletRequest cannot be resolved to a type An error occurred at line: 38 in the generated java file HttpServletResponse cannot be resolved to a type An error occurred at line: 39 in the generated java file ServletException cannot be resolved to a type An error occurred at line: 41 in the generated java file PageContext cannot be resolved to a type An error occurred at line: 42 in the generated java file HttpSession cannot be resolved to a type An error occurred at line: 43 in the generated java file ServletContext cannot be resolved to a type An error occurred at line: 44 in the generated java file ServletConfig cannot be resolved to a type An error occurred at line: 45 in the generated java file JspWriter cannot be resolved to a type An error occurred at line: 47 in the generated java file JspWriter cannot be resolved to a type An error occurred at line: 48 in the generated java file PageContext cannot be resolved to a type An error occurred at line: 53 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 1,315 in the generated java file SkipPageException cannot be resolved to a type An error occurred at line: 1,322 in the generated java file _jspxFactory cannot be resolved Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl er.java: 92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: 330) at
Re: [appengine-java] Re: 1.4 eclipse plugin
What does the error message say? No hints in the Problems window? On Mon, Dec 6, 2010 at 5:42 PM, mscwd01 mscw...@gmail.com wrote: This still doesn't solve the issue for me, mapping a servlet url pattern to a jsp file always fails... On Dec 6, 1:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type An error occurred at line: 24 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 31 in the generated java file _el_expressionfactory cannot be resolved An error occurred at line: 31 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 31 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file _jsp_annotationprocessor cannot be resolved An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 32 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 38 in the generated java file HttpServletRequest cannot be resolved to a type An error occurred at line: 38 in the generated java file HttpServletResponse cannot be resolved to a type An error occurred at line: 39 in the generated java file ServletException cannot be resolved to a type An error occurred at line: 41 in the generated java file PageContext cannot be resolved to a type An error occurred at line: 42 in the generated java file HttpSession cannot be resolved to a type An error occurred at line: 43 in the generated java file ServletContext cannot be resolved to a type An error occurred at line: 44 in the generated java file ServletConfig cannot be resolved to a type An error occurred at line: 45 in the generated java file JspWriter cannot be resolved to a type An error occurred at line: 47 in the generated java file JspWriter cannot be resolved to a type An error occurred at line: 48 in the generated java file PageContext cannot be resolved to a type An error occurred at line: 53 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 1,315 in the generated java file SkipPageException cannot be resolved to a type An error occurred at line: 1,322 in the generated java file _jspxFactory cannot be resolved Stacktrace: at
Re: [appengine-java] Re: 1.4 eclipse plugin
seems like repackaged-appengine-jasper-6.0.29.jar is not where it is supposed to be...? On Mon, Dec 6, 2010 at 5:58 PM, mscwd01 mscw...@gmail.com wrote: No hints in the problems window that are of any help. The error I get is: WARNING: /features org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 11 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type And the first part of the stacktrace is: Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java: 92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: 330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: 439) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: 592) Thanks On Dec 6, 4:52 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: What does the error message say? No hints in the Problems window? On Mon, Dec 6, 2010 at 5:42 PM, mscwd01 mscw...@gmail.com wrote: This still doesn't solve the issue for me, mapping a servlet url pattern to a jsp file always fails... On Dec 6, 1:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type An error occurred at line: 24 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 31 in the generated java file _el_expressionfactory cannot be resolved An error occurred at line: 31 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 31 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file _jsp_annotationprocessor cannot be resolved An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 32 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 38 in the generated java file HttpServletRequest cannot be resolved to a type An error occurred at line: 38
[appengine-java] Re: 1.4 eclipse plugin
Where should it be? I cannot see it listed in my libraries. On Dec 6, 5:03 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: seems like repackaged-appengine-jasper-6.0.29.jar is not where it is supposed to be...? On Mon, Dec 6, 2010 at 5:58 PM, mscwd01 mscw...@gmail.com wrote: No hints in the problems window that are of any help. The error I get is: WARNING: /features org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 11 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type And the first part of the stacktrace is: Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl er.java: 92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: 330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: 439) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: 592) Thanks On Dec 6, 4:52 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: What does the error message say? No hints in the Problems window? On Mon, Dec 6, 2010 at 5:42 PM, mscwd01 mscw...@gmail.com wrote: This still doesn't solve the issue for me, mapping a servlet url pattern to a jsp file always fails... On Dec 6, 1:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type An error occurred at line: 24 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 31 in the generated java file _el_expressionfactory cannot be resolved An error occurred at line: 31 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 31 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file _jsp_annotationprocessor cannot be resolved An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 32 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file
Re: [appengine-java] Re: 1.4 eclipse plugin
This JAR is where Eclipse reads the HttpJspBase type from. It is included in the AppEngine SDK Library. Project - Properties - Java Build Path - Libraries On Mon, Dec 6, 2010 at 6:28 PM, mscwd01 mscw...@gmail.com wrote: Where should it be? I cannot see it listed in my libraries. On Dec 6, 5:03 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: seems like repackaged-appengine-jasper-6.0.29.jar is not where it is supposed to be...? On Mon, Dec 6, 2010 at 5:58 PM, mscwd01 mscw...@gmail.com wrote: No hints in the problems window that are of any help. The error I get is: WARNING: /features org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 11 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type And the first part of the stacktrace is: Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl er.java: 92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: 330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: 439) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: 592) Thanks On Dec 6, 4:52 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: What does the error message say? No hints in the Problems window? On Mon, Dec 6, 2010 at 5:42 PM, mscwd01 mscw...@gmail.com wrote: This still doesn't solve the issue for me, mapping a servlet url pattern to a jsp file always fails... On Dec 6, 1:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type An error occurred at line: 24 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 31 in the generated java file _el_expressionfactory cannot be resolved An error occurred at line: 31 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 31 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file _jsp_annotationprocessor
[appengine-java] Re: 1.4 eclipse plugin
Ah yes found it in the App Engine SDK, repackaged-appengine- jasper-6.0.29.jar is there. The question now, is why isn't it working? On Dec 6, 5:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: This JAR is where Eclipse reads the HttpJspBase type from. It is included in the AppEngine SDK Library. Project - Properties - Java Build Path - Libraries On Mon, Dec 6, 2010 at 6:28 PM, mscwd01 mscw...@gmail.com wrote: Where should it be? I cannot see it listed in my libraries. On Dec 6, 5:03 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: seems like repackaged-appengine-jasper-6.0.29.jar is not where it is supposed to be...? On Mon, Dec 6, 2010 at 5:58 PM, mscwd01 mscw...@gmail.com wrote: No hints in the problems window that are of any help. The error I get is: WARNING: /features org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 11 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type And the first part of the stacktrace is: Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl er.java: 92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: 330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: 439) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: 592) Thanks On Dec 6, 4:52 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: What does the error message say? No hints in the Problems window? On Mon, Dec 6, 2010 at 5:42 PM, mscwd01 mscw...@gmail.com wrote: This still doesn't solve the issue for me, mapping a servlet url pattern to a jsp file always fails... On Dec 6, 1:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type An error occurred at line: 24 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 31 in the generated java file _el_expressionfactory cannot be resolved An error occurred at line: 31 in the generated java file
Re: [appengine-java] Re: 1.4 eclipse plugin
Could it be it is only a missing import declaration in the *.java result of your *.JSP? On Mon, Dec 6, 2010 at 6:46 PM, mscwd01 mscw...@gmail.com wrote: Ah yes found it in the App Engine SDK, repackaged-appengine- jasper-6.0.29.jar is there. The question now, is why isn't it working? On Dec 6, 5:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: This JAR is where Eclipse reads the HttpJspBase type from. It is included in the AppEngine SDK Library. Project - Properties - Java Build Path - Libraries On Mon, Dec 6, 2010 at 6:28 PM, mscwd01 mscw...@gmail.com wrote: Where should it be? I cannot see it listed in my libraries. On Dec 6, 5:03 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: seems like repackaged-appengine-jasper-6.0.29.jar is not where it is supposed to be...? On Mon, Dec 6, 2010 at 5:58 PM, mscwd01 mscw...@gmail.com wrote: No hints in the problems window that are of any help. The error I get is: WARNING: /features org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 11 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type And the first part of the stacktrace is: Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl er.java: 92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: 330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: 439) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: 592) Thanks On Dec 6, 4:52 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: What does the error message say? No hints in the Problems window? On Mon, Dec 6, 2010 at 5:42 PM, mscwd01 mscw...@gmail.com wrote: This still doesn't solve the issue for me, mapping a servlet url pattern to a jsp file always fails... On Dec 6, 1:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type
[appengine-java] Re: 1.4 eclipse plugin
I'm not sure I understand. It worked fine before I downloaded the new 1.4 SDK. On Dec 6, 5:54 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Could it be it is only a missing import declaration in the *.java result of your *.JSP? On Mon, Dec 6, 2010 at 6:46 PM, mscwd01 mscw...@gmail.com wrote: Ah yes found it in the App Engine SDK, repackaged-appengine- jasper-6.0.29.jar is there. The question now, is why isn't it working? On Dec 6, 5:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: This JAR is where Eclipse reads the HttpJspBase type from. It is included in the AppEngine SDK Library. Project - Properties - Java Build Path - Libraries On Mon, Dec 6, 2010 at 6:28 PM, mscwd01 mscw...@gmail.com wrote: Where should it be? I cannot see it listed in my libraries. On Dec 6, 5:03 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: seems like repackaged-appengine-jasper-6.0.29.jar is not where it is supposed to be...? On Mon, Dec 6, 2010 at 5:58 PM, mscwd01 mscw...@gmail.com wrote: No hints in the problems window that are of any help. The error I get is: WARNING: /features org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 11 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type And the first part of the stacktrace is: Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl er.java: 92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: 330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: 439) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: 592) Thanks On Dec 6, 4:52 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: What does the error message say? No hints in the Problems window? On Mon, Dec 6, 2010 at 5:42 PM, mscwd01 mscw...@gmail.com wrote: This still doesn't solve the issue for me, mapping a servlet url pattern to a jsp file always fails... On Dec 6, 1:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at
Re: [appengine-java] Re: 1.4 eclipse plugin
Forget it, I don't think it is actually possible to get JSP transformed into *.java without the imports, it'd probably yell at you upon saving the JSP. Have you tried re-syncing the JARs? I believe it can be done either by unchecking the is GAE option in the GAE settings of your project, and checking it back again... or by deleting some of those JARs in your /WEB-INF/lib - Eclipse (the plugin) should offer you the re-syncing in the Problems window as a Quick Fix. On Mon, Dec 6, 2010 at 7:07 PM, mscwd01 mscw...@gmail.com wrote: I'm not sure I understand. It worked fine before I downloaded the new 1.4 SDK. On Dec 6, 5:54 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Could it be it is only a missing import declaration in the *.java result of your *.JSP? On Mon, Dec 6, 2010 at 6:46 PM, mscwd01 mscw...@gmail.com wrote: Ah yes found it in the App Engine SDK, repackaged-appengine- jasper-6.0.29.jar is there. The question now, is why isn't it working? On Dec 6, 5:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: This JAR is where Eclipse reads the HttpJspBase type from. It is included in the AppEngine SDK Library. Project - Properties - Java Build Path - Libraries On Mon, Dec 6, 2010 at 6:28 PM, mscwd01 mscw...@gmail.com wrote: Where should it be? I cannot see it listed in my libraries. On Dec 6, 5:03 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: seems like repackaged-appengine-jasper-6.0.29.jar is not where it is supposed to be...? On Mon, Dec 6, 2010 at 5:58 PM, mscwd01 mscw...@gmail.com wrote: No hints in the problems window that are of any help. The error I get is: WARNING: /features org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 11 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type And the first part of the stacktrace is: Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl er.java: 92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: 330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: 439) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: 592) Thanks On Dec 6, 4:52 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: What does the error message say? No hints in the Problems window? On Mon, Dec 6, 2010 at 5:42 PM, mscwd01 mscw...@gmail.com wrote: This still doesn't solve the issue for me, mapping a servlet url pattern to a jsp file always fails... On Dec 6, 1:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome
[appengine-java] Re: com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: Set failed to set 1 keys: [...@1669ea1
Same here. Google Appengine SDK 1.4.0 has been just released so I wonder if it is a bug... On 2 dic, 10:51, sagar misal sagar1982mi...@gmail.com wrote: Till yesterday my application was performing well with more number of users than today but today suddenly it started raising this exception com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: Set failed to set 1 keys: [...@1669ea1 Can you please guide me what i need to do to avoid this exception.Besides i have not used memcache services exhaustively . 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: 1.4 eclipse plugin
I can confirm that JSPs are broken in 1.4 - tested it with eclipse 3.5 3.6 fresh install. The actual app engine renders them just fine so it should be something in the sdk or the plugin (or both) Solution for now would be - revert back to 1.3.8 ... On Dec 6, 1:26 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Forget it, I don't think it is actually possible to get JSP transformed into *.java without the imports, it'd probably yell at you upon saving the JSP. Have you tried re-syncing the JARs? I believe it can be done either by unchecking the is GAE option in the GAE settings of your project, and checking it back again... or by deleting some of those JARs in your /WEB-INF/lib - Eclipse (the plugin) should offer you the re-syncing in the Problems window as a Quick Fix. On Mon, Dec 6, 2010 at 7:07 PM, mscwd01 mscw...@gmail.com wrote: I'm not sure I understand. It worked fine before I downloaded the new 1.4 SDK. On Dec 6, 5:54 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Could it be it is only a missing import declaration in the *.java result of your *.JSP? On Mon, Dec 6, 2010 at 6:46 PM, mscwd01 mscw...@gmail.com wrote: Ah yes found it in the App Engine SDK, repackaged-appengine- jasper-6.0.29.jar is there. The question now, is why isn't it working? On Dec 6, 5:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: This JAR is where Eclipse reads the HttpJspBase type from. It is included in the AppEngine SDK Library. Project - Properties - Java Build Path - Libraries On Mon, Dec 6, 2010 at 6:28 PM, mscwd01 mscw...@gmail.com wrote: Where should it be? I cannot see it listed in my libraries. On Dec 6, 5:03 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: seems like repackaged-appengine-jasper-6.0.29.jar is not where it is supposed to be...? On Mon, Dec 6, 2010 at 5:58 PM, mscwd01 mscw...@gmail.com wrote: No hints in the problems window that are of any help. The error I get is: WARNING: /features org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 11 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type And the first part of the stacktrace is: Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl er.java: 92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: 330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: 439) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: 592) Thanks On Dec 6, 4:52 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: What does the error message say? No hints in the Problems window? On Mon, Dec 6, 2010 at 5:42 PM, mscwd01 mscw...@gmail.com wrote: This still doesn't solve the issue for me, mapping a servlet url pattern to a jsp file always fails... On Dec 6, 1:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in
[appengine-java] Re: 1.4 eclipse plugin
JSPs still broken with 1.4 Tested with eclipse 3.5 3.6 JDK version 1.6.0_22; OS Linux x86_64; Google Plugin for 1.4.0.v201010280047 com.google.gdt.eclipse.suite.e35.feature.feature.group Google App Engine Java SDK 1.4.0 1.4.0.v201012021500 com.google.appengine.eclipse.sdkbundle.e35.feature.1.4.0.feature.group To reproduce: 1. download fresh eclipse 3.5 or 3.6; 2. install sdk plugin as described in http://code.google.com/appengine/docs/java/tools/eclipse.html 3. create Web Application Project disable GWT support (testing JSPs only) 4. add JSP definition to web.xml 5. create hello world jsp as defined in web.xml 6. run the project and hit the jsp : INFO: The server is running at http://localhost:/ Dec 6, 2010 12:35:57 PM com.google.apphosting.utils.jetty.JettyLogger warn WARNING: /test.htm org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 7 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 8 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type On Dec 6, 8:33 am, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type An error occurred at line: 24 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 31 in the generated java file _el_expressionfactory cannot be resolved An error occurred at line: 31 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 31 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file _jsp_annotationprocessor cannot be resolved An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 32 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 38 in the generated java file HttpServletRequest cannot be resolved to a type An error occurred at line: 38 in the generated java file HttpServletResponse cannot be resolved to a type An error occurred at line: 39 in the generated java file ServletException cannot be resolved to a type An error occurred at line: 41 in the generated java file PageContext cannot be resolved to a type An error occurred at line: 42 in the generated java file HttpSession cannot be resolved to a type An error occurred at line: 43 in the generated java file ServletContext cannot be resolved to a type An error occurred
[appengine-java] Re: 1.4 eclipse plugin
http://code.google.com/p/googleappengine/issues/detail?id=4216 On Dec 6, 1:26 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Forget it, I don't think it is actually possible to get JSP transformed into *.java without the imports, it'd probably yell at you upon saving the JSP. Have you tried re-syncing the JARs? I believe it can be done either by unchecking the is GAE option in the GAE settings of your project, and checking it back again... or by deleting some of those JARs in your /WEB-INF/lib - Eclipse (the plugin) should offer you the re-syncing in the Problems window as a Quick Fix. On Mon, Dec 6, 2010 at 7:07 PM, mscwd01 mscw...@gmail.com wrote: I'm not sure I understand. It worked fine before I downloaded the new 1.4 SDK. On Dec 6, 5:54 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Could it be it is only a missing import declaration in the *.java result of your *.JSP? On Mon, Dec 6, 2010 at 6:46 PM, mscwd01 mscw...@gmail.com wrote: Ah yes found it in the App Engine SDK, repackaged-appengine- jasper-6.0.29.jar is there. The question now, is why isn't it working? On Dec 6, 5:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: This JAR is where Eclipse reads the HttpJspBase type from. It is included in the AppEngine SDK Library. Project - Properties - Java Build Path - Libraries On Mon, Dec 6, 2010 at 6:28 PM, mscwd01 mscw...@gmail.com wrote: Where should it be? I cannot see it listed in my libraries. On Dec 6, 5:03 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: seems like repackaged-appengine-jasper-6.0.29.jar is not where it is supposed to be...? On Mon, Dec 6, 2010 at 5:58 PM, mscwd01 mscw...@gmail.com wrote: No hints in the problems window that are of any help. The error I get is: WARNING: /features org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 11 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type And the first part of the stacktrace is: Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandl er.java: 92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java: 330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java: 439) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:314) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java: 592) Thanks On Dec 6, 4:52 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: What does the error message say? No hints in the Problems window? On Mon, Dec 6, 2010 at 5:42 PM, mscwd01 mscw...@gmail.com wrote: This still doesn't solve the issue for me, mapping a servlet url pattern to a jsp file always fails... On Dec 6, 1:33 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set
[appengine-java] Java App CSV file generator
I was using the python bulk loader for java deployed app , the problem i am facing is that am unable to upload the data due to csv format issues , and also when i download the existing datastore into a csv file i get junk data like config name , app id and other things , although I am able to retrieve the data It is very confusing to look my data in that generated file , I want the exact format of csv file , so that I can use the same to upload data . I have around 30 mb of xls data which i can convert into csv and upload . Please 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] Facebook, Cache Control and Money
Hi. As implied by the subject i would like to ask: 1. Facebook: My GAE application is working with the FB API. this API is very slow, and I receive timeouts. These timeouts cause erroneousness publish action to my users' Facebook. 10 seconds of timeout are just not enough. Can I make this threshold higher? 2. Cache: I'm trying to set the HTML header for my app in GAE to enable client side caching. Unfourtunatly, I have no idea how to do this. Can someone please drop me a hint? thanks. 3. Money: Actually this was to get some attention to my discussion, as FB+Cache issues seemed so boring to me! :-) A big 'Thank You' and a 'Happy Christmas' will be sent (with no Shipping fees) to the answering user. -- 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: 1.4 eclipse plugin
I'm running JSPs w/o issues now. Eclipse Java EE IDE for Web Developers. Version: Helios Service Release 1 Build id: 20100917-0705 GAE 1.4, GWT 2.1 On Mon, Dec 6, 2010 at 6:46 PM, xenoneo kozhuharov.i...@gmail.com wrote: JSPs still broken with 1.4 Tested with eclipse 3.5 3.6 JDK version 1.6.0_22; OS Linux x86_64; Google Plugin for 1.4.0.v201010280047 com.google.gdt.eclipse.suite.e35.feature.feature.group Google App Engine Java SDK 1.4.0 1.4.0.v201012021500 com.google.appengine.eclipse.sdkbundle.e35.feature.1.4.0.feature.group To reproduce: 1. download fresh eclipse 3.5 or 3.6; 2. install sdk plugin as described in http://code.google.com/appengine/docs/java/tools/eclipse.html 3. create Web Application Project disable GWT support (testing JSPs only) 4. add JSP definition to web.xml 5. create hello world jsp as defined in web.xml 6. run the project and hit the jsp : INFO: The server is running at http://localhost:/ Dec 6, 2010 12:35:57 PM com.google.apphosting.utils.jetty.JettyLogger warn WARNING: /test.htm org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 7 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 8 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type On Dec 6, 8:33 am, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type An error occurred at line: 24 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 31 in the generated java file _el_expressionfactory cannot be resolved An error occurred at line: 31 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 31 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file _jsp_annotationprocessor cannot be resolved An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 32 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 38 in the generated java file HttpServletRequest cannot be resolved to a type An error occurred at line: 38 in the generated java file HttpServletResponse cannot be resolved to a type An error occurred at line: 39 in the generated java file ServletException cannot be resolved to a
[appengine-java] Re: 1.4 eclipse plugin
No luck with: Eclipse IDE for Java EE Developers 1.3.1.20100916-1202 epp.package.jee Google App Engine Java SDK 1.4.0 1.4.0.v201012021502 com.google.appengine.eclipse.sdkbundle.e36.feature.1.4.0.feature.group Google Plugin for Eclipse 3.6 1.4.0.v201010280102 com.google.gdt.eclipse.suite.e36.feature.feature.group no GWT will test Web version of eclipse in a a few On Dec 6, 2:14 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: I'm running JSPs w/o issues now. Eclipse Java EE IDE for Web Developers. Version: Helios Service Release 1 Build id: 20100917-0705 GAE 1.4, GWT 2.1 On Mon, Dec 6, 2010 at 6:46 PM, xenoneo kozhuharov.i...@gmail.com wrote: JSPs still broken with 1.4 Tested with eclipse 3.5 3.6 JDK version 1.6.0_22; OS Linux x86_64; Google Plugin for 1.4.0.v201010280047 com.google.gdt.eclipse.suite.e35.feature.feature.group Google App Engine Java SDK 1.4.0 1.4.0.v201012021500 com.google.appengine.eclipse.sdkbundle.e35.feature.1.4.0.feature.group To reproduce: 1. download fresh eclipse 3.5 or 3.6; 2. install sdk plugin as described in http://code.google.com/appengine/docs/java/tools/eclipse.html 3. create Web Application Project disable GWT support (testing JSPs only) 4. add JSP definition to web.xml 5. create hello world jsp as defined in web.xml 6. run the project and hit the jsp : INFO: The server is running athttp://localhost:/ Dec 6, 2010 12:35:57 PM com.google.apphosting.utils.jetty.JettyLogger warn WARNING: /test.htm org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 7 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 8 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type On Dec 6, 8:33 am, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type An error occurred at line: 24 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 31 in the generated java file _el_expressionfactory cannot be resolved An error occurred at line: 31 in the generated java file _jspxFactory cannot be resolved An error occurred at line: 31 in the generated java file The method getServletConfig() is undefined for the type plans_jsp An error occurred at line: 32 in the generated java file _jsp_annotationprocessor cannot be resolved An error occurred at line: 32 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An error occurred at line: 32 in the generated java file The method getServletConfig() is
[appengine-java] Re: 1.4 eclipse plugin
I'm running: Eclipse Java EE IDE for Web Developers. Build id: 20100218-1602 With V1.4 of the App Engine SDK and cannot get servlets mapping to jsp files, i.e. servlet servlet-nameabout/servlet-name jsp-file/about.jsp/jsp-file /servlet servlet-mapping servlet-nameabout/servlet-name url-pattern/about/url-pattern /servlet-mapping However, other servlets work fine for example I have servlets which issue a redirect to a jsp file in my WEB-INF folder and they work fine. It's baffling me now. On Dec 6, 7:25 pm, xenoneo kozhuharov.i...@gmail.com wrote: No luck with: Eclipse IDE for Java EE Developers 1.3.1.20100916-1202 epp.package.jee Google App Engine Java SDK 1.4.0 1.4.0.v201012021502 com.google.appengine.eclipse.sdkbundle.e36.feature.1.4.0.feature.group Google Plugin for Eclipse 3.6 1.4.0.v201010280102 com.google.gdt.eclipse.suite.e36.feature.feature.group no GWT will test Web version of eclipse in a a few On Dec 6, 2:14 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: I'm running JSPs w/o issues now. Eclipse Java EE IDE for Web Developers. Version: Helios Service Release 1 Build id: 20100917-0705 GAE 1.4, GWT 2.1 On Mon, Dec 6, 2010 at 6:46 PM, xenoneo kozhuharov.i...@gmail.com wrote: JSPs still broken with 1.4 Tested with eclipse 3.5 3.6 JDK version 1.6.0_22; OS Linux x86_64; Google Plugin for 1.4.0.v201010280047 com.google.gdt.eclipse.suite.e35.feature.feature.group Google App Engine Java SDK 1.4.0 1.4.0.v201012021500 com.google.appengine.eclipse.sdkbundle.e35.feature.1.4.0.feature.group To reproduce: 1. download fresh eclipse 3.5 or 3.6; 2. install sdk plugin as described in http://code.google.com/appengine/docs/java/tools/eclipse.html 3. create Web Application Project disable GWT support (testing JSPs only) 4. add JSP definition to web.xml 5. create hello world jsp as defined in web.xml 6. run the project and hit the jsp : INFO: The server is running athttp://localhost:/ Dec 6, 2010 12:35:57 PM com.google.apphosting.utils.jetty.JettyLogger warn WARNING: /test.htm org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 7 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 8 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type On Dec 6, 8:33 am, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: Thanks guys, moving AppEngine (and GWT) to the top in Order and Export really solved this. Thanks a lot :) On Sun, Dec 5, 2010 at 4:40 PM, Mike Friesen mfrie...@gmail.com wrote: I had the same problem and fixed it by: 1) Selecting project Root - Goto File-Properties 2) Select Java Build Path 3) Select Order and Export 4) Move App Engine SDK 1.4.0 to the #1 position and GWT SDK 2.1.0 to the #2 position On Sun, Dec 5, 2010 at 7:28 AM, Sudhir sudhi...@gmail.com wrote: Same issue here... does anyone have a fix that doesn't involve re- installing eclipse and recreating the entire project step by step? Sudhir On Dec 4, 4:37 pm, GoSharp Lite gosharpl...@gmail.com wrote: I solve my jsp compilation issue by using below steps. 1) Download and install eclipse-java-helios-SR1-win32.zip. 2) Install plugins from http://dl.google.com/eclipse/plugin/3.6;. 3) Download and install java_ee_sdk-6u1-jdk-windows.exe. 4) Create a new and empty app using same project name and package as my old app. 5) Carefully copy all files in src and war from my old app into the new app. 6) Import all external libs from my old app into the new app. 7) Set Properties-Google-App Engine-ORM to server files which need enhancement. 8) Debug and no more Unable to compile class for JSP. On Dec 4, 11:47 am, Jerome jerome.mou...@gmail.com wrote: Sorry, no solution but a very similar issue with Eclipse Helios SR 1: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 9 in the generated java file org.apache.jasper.runtime.HttpJspBase cannot be resolved to a type An error occurred at line: 10 in the generated java file org.apache.jasper.runtime.JspSourceDependent cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved to a type An error occurred at line: 12 in the generated java file JspFactory cannot be resolved An error occurred at line: 23 in the generated java file javax.el.ExpressionFactory cannot be resolved to a type An error occurred at line: 24 in the generated java file org.apache.AnnotationProcessor cannot be resolved to a type An
[appengine-java] Primefaces works on Development but after Deployment seems like all css are not recognized? (In FireFox only)
Hi I'm developing using PrimeFaces(JSF) library... and all works just fine on development (in IE 8 and FireFox 3.6) But after the deployment to the GAE platform it stops to work in FireFox, it looks like no css are recognized... and the website looks poor... Any ideas how can i solve this issue? Regards Daniel. -- 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: no async queries on AsyncDatastoreService for 1.4.0?
Luke, thanks for the follow up! You're right that sometimes RPC overhead can add up especially with something as fast as Memcache, so batching things is definitely your friend. With the datastore, the RPC overhead should be a much smaller percentage overall of operations, so you see real benefit when you do, well, exactly what you did switching to async operations and batching when possible. This is probably my favorite post of the morning. Here's hoping more developers see this and are inspired by your optimizations =). -- 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 Sat, Dec 4, 2010 at 10:55 PM, Luke lvale...@gmail.com wrote: i finished updating my server to use the AsyncDatastoreService. i also cleaned up my memcache code to batch cache requests. both of these changes allowed me to improve the request time by up to 4x for some requests. from ~80ms to ~20ms. now i can prefetch content for the user with little to no penalty to request latency. in fact, much content will have no latency thanks to prefetching :) the server used to get and set cached objects in memcache for each command in a batch. if i have 4 commands in a batch, that could be up to 8 memcache RPCs as well as the actual work for those commands. that was pretty wasteful. so i updated my server to batch all gets into a getAll, and all puts into a putAll. that made a big difference. the length of each get and put are the same, but now i have no more than two memcache calls no matter how many commands are in a batch. if everything hits the cache, then i don't even need to do a put...the entire request will finish in about 6ms. the server also used the synchronous datastore service. so all i/o was blocking. now it's been updated to use AsyncDatastoreService. the server can kick off all i/o for each command at the beginning of the request and gather up the results when they finish. my queries are still blocking...but that doesn't seem to be much of an impact for now. thanks to the app engine team for delivering this interface :) On Dec 3, 11:52 am, Jeff Schnitzer j...@infohazard.org wrote: Does it take so much time to process your results that it really matters they be done in the optimal order? All that polling code is complicated... unless you're shaving off a lot of real-world time, seems like it's better to just launch all batches and block on the first one. Jeff On Wed, Dec 1, 2010 at 8:44 PM, Luke lvale...@gmail.com wrote: great, thanks for the insight max. i have a client that will batch together multiple requests into one RPC call to my app on GAE. each of these individual requests may have one or more datastore accesses. this may include some prefetch requests. so i want to build a mechanism that will interleave these requests taking advantage of theAsyncDatastoreServicefor minimum request latency. i've gone through my server-side stack and made it asynchronous by wrapping RPC returns in Future objects. then i've created a FutureChain object that takes one or more Future objects as input, and will return one Future object. i then have some code that will poll the ultimate Future objects until all of them have finished. it ends up being a simple multi-threaded emulation where each individual request in a batch gets a thread and each thread gives up control when it makes an Async request. now for the PreparedQuery, because my app knows how many items i want, i should be able to wrap it in a special Future object that will try to pull in that many items when it is polled...but the problem is, i don't know when the batch has come back, so every time i call next(), i risk blocking on I/O when i could be initiating another I/O asynchronously or processing the results of an async I/O. so until there is explicit knowledge of when the I/O for a batch has finished, i may be able to get away with reducing the poll-rate of queries i suppose i could just query for the keys, then i could use an explicit Async method to fetch the entities themselves. if i query for keys, will they be split up in batches? any way to know how many keys will be in one batch? On Nov 29, 11:08 am, Max Ross (Google) maxr+appeng...@google.com wrote: Hi Luke, First the awesome news: As of 1.4.0, many queries are implicitly asynchronous. When you call PreparedQuery.asIterable() or PreparedQuery.asIterator(), we initiate the query in the background and then immediately return. This lets you do work while the first batch of results is being fetched. And, when the first batch has been consumed we immediately request the next batch. If you're performing a significant amount of work with each Entity as you iterate you will probably see a latency win as a result of this. Now the
Re: [appengine-java] Re: Local datastore empty after updating to SDK 1.4.0
Hey guys. There are issues going between versions with local data. From what I remember, there was an issue with the local SDK going between 1.3.7 and 1.3.8. Long term solutions we are considering include better support for using SQLite as a backend (similar to what Nick did with the Python SDK). In the meantime, it is probably a best practice to create fixtures from which you can create test data. If you're running any kind of automated testing (say Selenium), this is a practice you're already familiar with. Would it be helpful if the SDK provided an easier mechanism for loading data? If I get some time, maybe I'll blog about how to do this ... -- 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 Mon, Dec 6, 2010 at 5:45 AM, Ian Marshall ianmarshall...@gmail.com wrote: I have just found that my local datastore test data seems to be unaffected so far by my upgrading my GAE/J SDK this morning from 1.3.8 to 1.4.0. Of course, even if my test data should prove unaffected by the latest change in SDK, there is no guarantee of such an outcome for any future release. That being said, I produce my test data when conducting test scripts for my web app, so generating a fresh set of test datastore data by going through these tests for a new SDK is no bad thing anyway! On Dec 6, 9:21 am, Ian Marshall ianmarshall...@gmail.com wrote: Hi Fabrizio, Yes, I do delete the local datastore and create it again. I delete the local datastore by following the instructions given in: http://code.google.com/intl/en/appengine/docs/java/tools/devserver.ht... I then create it again by launching the development application server and then populating my local datastore using my web application. Cheers, Ian On Dec 6, 7:07 am, Fabrizio Accatino fht...@gmail.com wrote: Sorry Ian, I don't understand. Do you delete the local datastore and create it again? If yes, how? Fabrizio On Sun, Dec 5, 2010 at 5:16 PM, Ian Marshall ianmarshall...@gmail.comwrote: I have a test local datastore. I also have a procedure now to delete this whenever I install a new GAE/J SDK. This solved my problem of disappearing test data. -- 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: Professional Google App Engine Programming with Java book
Interesting. I guess one of the drawbacks of such fast-moving tech is that books from 2009 are already outdated! On Nov 30, 9:56 am, Didier Durand durand.did...@gmail.com wrote: Read it: full of very interesting stuff that you don't find elsewhere on the web! On Nov 30, 4:48 pm, Tommy Fannon tfan...@gmail.com wrote: I will take a look. I saw that the date was from 2009, so was hoping for more latest and greatest direct from a google engineer! Thanks, tf -- 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: Real-Time Log Delivery Via XMPP
nice writeup! On Dec 1, 12:59 pm, Stephen Johnson onepagewo...@gmail.com wrote: I'm not sure if anyone is interested in this type of capability but I had a use for it for my own debugging and monitoring purposes so I thought I'd share what I came up with especially since people seem to be losing their logs or at least they aren't showing up for a while. You can read my post atwww.professionalintellectualdevelopment.com. Stephen -- 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: Real-Time Log Delivery Via XMPP
PS for whatever reason that link isn't working for me. On Dec 6, 5:17 pm, Dan Billings debil...@gmail.com wrote: nice writeup! On Dec 1, 12:59 pm, Stephen Johnson onepagewo...@gmail.com wrote: I'm not sure if anyone is interested in this type of capability but I had a use for it for my own debugging and monitoring purposes so I thought I'd share what I came up with especially since people seem to be losing their logs or at least they aren't showing up for a while. You can read my post atwww.professionalintellectualdevelopment.com. Stephen -- 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: datanucleus-appengine
On Fri, Dec 3, 2010 at 12:50 PM, George Moschovitis george.moschovi...@gmail.com wrote: - Objectify seems to have more momentum, but is not standard, dunno if this will be supported in a year or two Just to give you a little perspective, it's worth pointing out how thin projects like Objectify really are: http://www.ohloh.net/p/objectify-appengine/analyses/latest At less than 10k lines of code, compare this to Datanucleus ( 500k): http://www.ohloh.net/p/datanucleus/analyses/latest As the lead developer, I'm genuinely flattered that people hold Objectify in such high regard, but I really have to give the credit to the folks at Google working on the backend and the Low-Level API. Objectify is a very simple project and we're trying to keep it that way. If I were to be hit by a bus tomorrow, there are plenty of other people who can step up... or anyone using the code could branch/fork it. It's just not that complicated. Jeff -- 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] appcfg.sh --append duplicates logs
Repeatedly running the following command: path to app engine SDK/bin/appcfg.sh --append request_logs path to app my_logs.txt duplicates the logs rather than appending new logs since the last fetch as indicated by the documentation. Furthermore, the logs appear in reverse-chronological order, so it seems like periodic appends would be somewhat nonsensical. Anyone have experience downloading the App Engine request/message logs using the Java SDK? Am I using the command properly? Please help, 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] Re: Professional Google App Engine Programming with Java book
Hi Dan, Not really: the info on datatstore, queues, etc is still very much up to date and impossible to find elsewhere as it was contributed by Googlers. regards didier On Dec 6, 11:55 pm, Dan Billings debil...@gmail.com wrote: Interesting. I guess one of the drawbacks of such fast-moving tech is that books from 2009 are already outdated! On Nov 30, 9:56 am, Didier Durand durand.did...@gmail.com wrote: Read it: full of very interesting stuff that you don't find elsewhere on the web! On Nov 30, 4:48 pm, Tommy Fannon tfan...@gmail.com wrote: I will take a look. I saw that the date was from 2009, so was hoping for more latest and greatest direct from a google engineer! Thanks, tf -- 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: Facebook, Cache Control and Money
I use 20 seconds timeout when issuing http requests:
URL urlObj = new URL(url);
URLConnection urlCon = urlObj.openConnection();
urlCon.setConnectTimeout(2);
urlCon.setReadTimeout(2);
BufferedReader reader = new BufferedReader(new
InputStreamReader(urlCon.getInputStream()));
while ((line = reader.readLine()) != null) {
// do something with the line of content
}
reader.close();
Does it help?
Michael Weinberg
On Dec 6, 10:12 am, takealike shaharkarny.h...@gmail.com wrote:
Hi.
As implied by the subject i would like to ask:
1. Facebook: My GAE application is working with the FB API. this API
is very slow, and I receive timeouts. These timeouts cause
erroneousness publish action to my users' Facebook. 10 seconds of
timeout are just not enough. Can I make this threshold higher?
2. Cache: I'm trying to set the HTML header for my app in GAE to
enable client side caching. Unfourtunatly, I have no idea how to do
this. Can someone please drop me a hint? thanks.
3. Money: Actually this was to get some attention to my discussion, as
FB+Cache issues seemed so boring to me! :-)
A big 'Thank You' and a 'Happy Christmas' will be sent (with no
Shipping fees) to the answering user.
--
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: datanucleus-appengine
I don't know the back story on ROO-1797, but the issue report is, I think, not entirely accurate. The Expenses sample app that shipped with Roo 1.1 and GWT 2.1.0 runs on App Engine with DataNucleus. Given that Spring Roo seems oriented towards RDBMSs, it would not surprise me if there were a lot of one-off code in Roo to support App Engine's non-relational aspects. However, the Spring team demoed the standard travel booking app running on App Engine with hosted SQL (http://code.google.com/appengine/business/#features) at SpringOne in October, so I don't think cloud portability is exactly a lost cause. Even if it is, I'll take the simplicity and scalability of the Datastore vs. the portability of an API for which required me to consult a 408-page (and later, 841-page) reference manual every time I started a new app. For me, Objectify made Java persistence coding fun again, and words like persistence manager lifecycle and detached instance are blissfully draining out of my vocabulary :-) /dmc http://turbomanage.wordpress.com On Dec 5, 3:41 am, George Moschovitis george.moschovi...@gmail.com wrote: On Dec 4, 6:56 am, John Howe jhowe...@gmail.com wrote: Is that another wave I see on the horizon ... the news on the cloud-portability front are disappointing too: https://jira.springsource.org/browse/ROO-1797 Remove support for DataNucleus 1.x and Google App Engine Since none of Roo's sample apps can deploy to the app engine and given there are a lot of hacks in the Roo code to allow even the simplest of apps to run in the app engine, this task is to remove all the code that supports the app engine until full SQL support is available. This also has the added benefit of being able to drop support for JPA 1.0 with the removal of DataNuclueus 1.x maybe another reason to update datanuclues-appengine to datanucleus 2.x ? -g. -- 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] error msg= javax.management.MBeanServerPermission is a restricted class
Hi all, I'm getting the errror while running the web application in google app engine(web application). Error: Warning: WDK application could not be started, error msg= javax.management.MBeanServerPermission is a restricted class. Please see the Google App Engine developer's guide for more details., error type=java.lang.NoClassDefFoundError. This message can be ignored during the installation. java.lang.NoClassDefFoundError: javax.management.MBeanServerPermission is a restricted class. Please see the Google App Engine developer's guide for more details. help me to resolve this error. 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. Dec 7, 2010 6:37:40 AM com.google.apphosting.utils.jetty.JettyLogger info INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger Dec 7, 2010 6:37:44 AM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml INFO: Successfully processed E:\SVN_LOCAL\GoogleAppForWebTop\war\WEB-INF/appengine-web.xml Dec 7, 2010 6:37:44 AM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml INFO: Successfully processed E:\SVN_LOCAL\GoogleAppForWebTop\war\WEB-INF/web.xml Warning: WDK application could not be started, error msg= javax.management.MBeanServerPermission is a restricted class. Please see the Google App Engine developer's guide for more details., error type=java.lang.NoClassDefFoundError. This message can be ignored during the installation. java.lang.NoClassDefFoundError: javax.management.MBeanServerPermission is a restricted class. Please see the Google App Engine developer's guide for more details. at com.google.appengine.tools.development.agent.runtime.Runtime.reject(Runtime.java:51) at com.documentum.fc.client.security.impl.policy.PolicyConfigurator.configureDfc(PolicyConfigurator.java:85) at com.documentum.fc.client.security.impl.policy.PolicyConfigurator.access$000(PolicyConfigurator.java:24) at com.documentum.fc.client.security.impl.policy.PolicyConfigurator$1.run(PolicyConfigurator.java:45) at com.documentum.fc.client.security.impl.policy.PolicyConfigurator$1.run(PolicyConfigurator.java:41) at java.security.AccessController.doPrivileged(Native Method) at com.documentum.fc.client.security.impl.policy.PolicyConfigurator.configure(PolicyConfigurator.java:38) at com.documentum.fc.impl.RuntimeContext.clinit(RuntimeContext.java:171) at com.documentum.fc.client.DfClient.clinit(DfClient.java:700) at com.documentum.com.DfClientX.getLocalClient(DfClientX.java:43) at com.documentum.web.env.NotificationManager.contextInitialized(NotificationManager.java:101) at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548) at org.mortbay.jetty.servlet.Context.startContext(Context.java:136) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.Server.doStart(Server.java:224) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at com.google.appengine.tools.development.JettyContainerService.startContainer(JettyContainerService.java:185) at com.google.appengine.tools.development.AbstractContainerService.startup(AbstractContainerService.java:149) at com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java:219) at com.google.appengine.tools.development.DevAppServerMain$StartAction.apply(DevAppServerMain.java:164) at com.google.appengine.tools.util.Parser$ParseResult.applyArgs(Parser.java:48) at com.google.appengine.tools.development.DevAppServerMain.init(DevAppServerMain.java:113) at com.google.appengine.tools.development.DevAppServerMain.main(DevAppServerMain.java:89) Exception in thread Thread-4 java.lang.NoClassDefFoundError: java.io.FileOutputStream is a restricted class. Please see the Google App Engine developer's guide for more details. at com.google.appengine.tools.development.agent.runtime.Runtime.reject(Runtime.java:51) at
[appengine-java] Re: error msg= javax.management.MBeanServerPermission is a restricted class
Hi, GAE does not provide full support for java runtime. You have to limit your code to the supported classes as defined by the JRE white list (1400+ classes as of now). See http://code.google.com/appengine/docs/java/jrewhitelist.html MBeans classes are currently not part of this list regards didier On Dec 7, 8:04 am, ramesh rajapandian r.rameshrajapand...@gmail.com wrote: Hi all, I'm getting the errror while running the web application in google app engine(web application). Error: Warning: WDK application could not be started, error msg= javax.management.MBeanServerPermission is a restricted class. Please see the Google App Engine developer's guide for more details., error type=java.lang.NoClassDefFoundError. This message can be ignored during the installation. java.lang.NoClassDefFoundError: javax.management.MBeanServerPermission is a restricted class. Please see the Google App Engine developer's guide for more details. help me to resolve this error. thanks. Error file.txt 4KViewDownload -- 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: Spring Security login problem with IE8 for app within frame (on GAE)
Hi, Thanks for the reply. I didn't do that because honestly I couldn't make head or tail of it. :-) I'll have another look I guess, but I find the documentation around this whole area to be pretty much abominable. Regards, Neil Brennan On Dec 7, 9:20 am, Ikai Lan (Google) ikai.l+gro...@google.com wrote: Is there a reason you didn't just register a Google Apps domain and used that instead? http://stackoverflow.com/questions/817809/how-to-use-google-app-engin... -- 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 Sat, Dec 4, 2010 at 4:54 PM, Nello nelloban...@gmail.com wrote: Hi, I've built a Spring 3.0.2 app on GAE using Spring Security for authentication that works just fine for all browsers tested, EXCEPT... I'm using Google App Engine and so ended up with one of those horrible xxx.appspot.com addresses for the project. So, I'm using domain forwarding from GoDaddy, which essentially means my original app is housed inside a frame. It's a bit ugly, but it works for Firefox, Chrome and Safari, just not IE. I don't need to support any IE except IE8. I'm using a login.page with a LoginController, and can see that the authentication request is going through the controller but even if I just mark the user as authenticated at that point (which I do for a 'casual browser' role) they are still locked out of the app and re- presented with the login page. Facts that may be relevant: I'm using 'remember-me' and the 'disable- url-rewriting' attributes, and have made sure that my error and 404 pages are available to unsecured users. I'm kind of at a loss here. Right now my only option appears to be to add some frame-breaking javascript for IE, but that pretty much stinks. Thoughts? Please! -- 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 athttp://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.
