[appengine-java] Re: Help needed with Error
If you are trying to put the reult of a query directly into memcache then you should read http://groups.google.com/group/google-appengine-java/msg/1d835ac8245d1d48. -- 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: Adding Task-Queue Tasks in Batch?
>From >http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/labs/taskqueue/Queue.html add(java.lang.Iterable taskOptions) Submits tasks to this queue. On Apr 6, 9:54 am, Seth Ladd wrote: > Aloha, > > The docs for the Java implementation of the Task Queue mentions this: > > maximum number of tasks that can be added in a batch - 100 > > However, I can't find any reference to adding tasks in a batch. What > does the above mean, and where can I find more information about it? > I'd like to be able to add "many" tasks in a batch, if that's > possible. > > I am aware of the "5 tasks per transaction" limit. > > Thanks! > Seth -- 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: Adding Task-Queue Tasks in Batch?
I think the five limit still applies. If you want to run more than five you could run five tasks and structure them to enqueue further tasks once they run. On Apr 8, 4:41 am, Seth Ladd wrote: > Thanks! > > If under a transaction, are tasks added via batch still constrained to > 5 per txn? > > On Apr 6, 11:53 am, Keith wrote: > > > > > Fromhttp://code.google.com/appengine/docs/java/javadoc/com/google/appengi... > > > add(java.lang.Iterable taskOptions) > > Submits tasks to this queue. > > > On Apr 6, 9:54 am, Seth Ladd wrote:> Aloha, > > > > The docs for the Java implementation of the Task Queue mentions this: > > > > maximum number of tasks that can be added in a batch - 100 > > > > However, I can't find any reference to adding tasks in a batch. What > > > does the above mean, and where can I find more information about it? > > > I'd like to be able to add "many" tasks in a batch, if that's > > > possible. > > > > I am aware of the "5 tasks per transaction" limit. > > > > Thanks! > > > Seth -- 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: Please help, I'm not able to obtain the oAuth redirect URL from twitter
I'm also seeing problems between app engine and twitter. There are a also a number of complaints from other people as well. I'm also using twitter4j and it has been working fine for some time and works fine when I use it locally. Anyone know what's going on? On Jul 23, 6:25 am, nischalshetty wrote: > @Benjamin > > I am using twitter4j. Its not an issue on my end since the apps been > running from 6 months now. And I just ran a check on many other > twitter apps hosted on the app engine, none seem to be working. > > Can you share the url of your app? > > -Nischal > > On Jul 23, 10:03 am, Benjamin wrote: > > > > > Sorry to hear of your trouble Nischal > > > I'm hitting twitter without any issue from my prod app engine - if it > > helps, i've had a lot of success using twitter4j libraries - maybe you > > can check them out. > > > The only strange thing about getting an auth token from twitter oauth > > from app engine is how you have to direct the user to the > > authorization url and hold the token in your session on the server > > side while they authorize the app - then continue with the process of > > getting an oauth token on the server. > > > On Jul 22, 10:33 pm, nischalshetty wrote: > > > > Was searching twitter, others seem to be facing the same problem. > > > Please treat this on priority, my entire sitehttp://www.justunfollow.com > > > is unusable right now due to the error. > > > > A lot of users are stuck due to the error. > > > > -Nischal > > > > On Jul 23, 7:24 am, nischalshetty wrote: > > > > > To obtain the redirect URL it's an https call to twitter. I'm just not > > > > able to obtain it in production. > > > > > However, it works in my development environment on my PC. Please help > > > > ASAP, my site gets a lot of users and this is causing problems for all > > > > of them :( > > > > > Here's the stack trace : > > > > > twitter4j.TwitterException: Could not fetch > > > > URL:https://twitter.com/oauth/request_token > > > > at > > > > twitter4j.internal.http.HttpClient.request(HttpClient.java:340) > > > > at > > > > twitter4j.internal.http.HttpClientWrapper.request(HttpClientWrapper.java: > > > > 68) > > > > at > > > > twitter4j.internal.http.HttpClientWrapper.post(HttpClientWrapper.java: > > > > 99) > > > > at > > > > twitter4j.http.OAuthAuthorization.getOAuthRequestToken(OAuthAuthorization.j > > > > ava: > > > > 121) > > > > at twitter4j.Twitter.getOAuthRequestToken(Twitter.java:1406) > > > > at > > > > justunfollow.manager.impl.JustUnfollowManagerImpl.redirectURL(JustUnfollowM > > > > anagerImpl.java: > > > > 60) > > > > at justunfollow.action.Login.authenticate(Login.java:56) > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown > > > > Source) > > > > at java.lang.reflect.Method.invoke(Unknown Source) > > > > at > > > > com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.M > > > > ethod_ > > > > $1.run(Method_.java:165) > > > > at java.security.AccessController.doPrivileged(Native Method) > > > > at > > > > com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.M > > > > ethod_.privilegedInvoke(Method_.java: > > > > 163) > > > > at > > > > com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.M > > > > ethod_.invoke_(Method_.java: > > > > 124) > > > > at > > > > com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.M > > > > ethod_.invoke(Method_.java: > > > > 43) > > > > at > > > > com.opensymphony.xwork2.DefaultActionInvocation.invokeAction(DefaultActionI > > > > nvocation.java: > > > > 404) > > > > at > > > > com.opensymphony.xwork2.DefaultActionInvocation.invokeActionOnly(DefaultAct > > > > ionInvocation.java: > > > > 267) > > > > at > > > > justunfollow.interceptor.ExceptionInterceptor.intercept(ExceptionIntercepto > > > > r.java: > > > > 23) > > > > at com.opensymphony.xwork2.DefaultActionInvocation > > > > $2.doProfiling(DefaultActionInvocation.java:224) > > > > at com.opensymphony.xwork2.DefaultActionInvocation > > > > $2.doProfiling(DefaultActionInvocation.java:223) > > > > at > > > > com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStac > > > > k.java: > > > > 455) > > > > at > > > > com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocat > > > > ion.java: > > > > 221) > > > > at > > > > com.opensymphony.xwork2.interceptor.DefaultWorkflowInterceptor.doIntercept( > > > > DefaultWorkflowInterceptor.java: > > > > 221) > > > > at > > > > com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(Metho > > > > dFilterInterceptor.java: > > > > 86) > > > > at com.opensymphony.x
[appengine-java] Re: Problem deploying application with jsps
Hi Abhinav, I suspect the problem may be exactly as the error message implies: access to javac is being denied because of its configured permissions. To test that theory, could you try running javac from a command prompt, using the path from the exception message? If you are able to run it, javac should display its usage options (since you didn't specify any arguments). However, if you also get an Access Denied error from the command line, then the problem is not with Eclipse or the plugin, but with the permissions on javac. One scenario that might produce this error would be if you installed the JDK as an Administrator and then run javac (either manually from the command line or indirectly via Eclipse) as a regular (non-admin) user. Let me know if you are able to reproduce the problem from the command line. Thanks, Keith On Wed, Aug 19, 2009 at 5:03 AM, Abhinav Lele wrote: > Hi, > > I am using Eclipse 3.5 ( Galilieo ) on Windows XP to deploy my application. > It runs fine on my local machine but when I try to deploy it to appengine it > is giving me the following error. > > > Creating staging directory > Scanning for jsp files. > Compiling jsp files. > Compiling java files. > java.io.IOException: Cannot run program "D:\usr\dev\jdk16_12\bin\javac": > CreateProcess error=5, Access is denied > > Debugging information may be found in C:\Documents and Settings\user\Local > Settings\Temp\appengine-deploy6738175632278023548.log > > appengine-deploy6738175632278023548.log > > Unable to upload: > java.io.IOException: Cannot run program "D:\usr\dev\jdk16_12\bin\javac": > CreateProcess error=5, Access is denied > at java.lang.ProcessBuilder.start(ProcessBuilder.java:459) > at > com.google.appengine.tools.admin.Application.startProcess(Application.java:434) > at > com.google.appengine.tools.admin.Application.compileJavaFiles(Application.java:393) > at > com.google.appengine.tools.admin.Application.compileJsps(Application.java:361) > at > com.google.appengine.tools.admin.Application.createStagingDirectory(Application.java:237) > at > com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:51) > at > com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngineBridgeImpl.java:271) > at > com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(DeployProjectJob.java:148) > at > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.io.IOException: CreateProcess error=5, Access is denied > at java.lang.ProcessImpl.create(Native Method) > at java.lang.ProcessImpl.(ProcessImpl.java:81) > at java.lang.ProcessImpl.start(ProcessImpl.java:30) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:452) > ... 9 more > > > > However if I remove the jsp file from the war folder the deployment works > fine. FYI, the jsp is an empty file. Can someone suggest what is going wrong > ??? > > > -- > Abhinav > > > --~--~-~--~~~---~--~~ 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-java@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: Problem deploying application with jsps
Hm, that is odd. Since you're able to use javac from the command line and via appcfg, I'm assuming the problem does lie with Eclipse and the permissions it was launched with. Would it be possible for you to write a small test Java app that uses ProcessBuilder<http://java.sun.com/j2se/1.5.0/docs/api/java/lang/ProcessBuilder.html>to invoke javac? If your test app fails with an Access Denied error, then at least we can rule out the plugin and App Engine as the source of the problem. If that is indeed the case, you could try installing another JDK and Eclipse instance using your user account, and see if that fixes things. Keith On Wed, Aug 19, 2009 at 2:35 PM, Abhinav Lele wrote: > Hi Keith, > > Well I was able to upload it using appcfg from the command line :) .. > Though I wonder why eclipse is getting a access denied error. > My user account has administrator privileges. > > -- > Abhinav > > > On Wed, Aug 19, 2009 at 8:49 PM, Keith Platfoot wrote: > >> Hi Abhinav, >> I suspect the problem may be exactly as the error message implies: access >> to javac is being denied because of its configured permissions. >> >> To test that theory, could you try running javac from a command prompt, >> using the path from the exception message? If you are able to run it, javac >> should display its usage options (since you didn't specify any arguments). >> However, if you also get an Access Denied error from the command line, then >> the problem is not with Eclipse or the plugin, but with the permissions on >> javac. One scenario that might produce this error would be if you installed >> the JDK as an Administrator and then run javac (either manually from the >> command line or indirectly via Eclipse) as a regular (non-admin) user. >> >> Let me know if you are able to reproduce the problem from the command >> line. Thanks, >> >> Keith >> >> On Wed, Aug 19, 2009 at 5:03 AM, Abhinav Lele wrote: >> >>> Hi, >>> >>> I am using Eclipse 3.5 ( Galilieo ) on Windows XP to deploy my >>> application. It runs fine on my local machine but when I try to deploy it to >>> appengine it is giving me the following error. >>> >>> >>> Creating staging directory >>> Scanning for jsp files. >>> Compiling jsp files. >>> Compiling java files. >>> java.io.IOException: Cannot run program "D:\usr\dev\jdk16_12\bin\javac": >>> CreateProcess error=5, Access is denied >>> >>> Debugging information may be found in C:\Documents and >>> Settings\user\Local Settings\Temp\appengine-deploy6738175632278023548.log >>> >>> appengine-deploy6738175632278023548.log >>> >>> Unable to upload: >>> java.io.IOException: Cannot run program "D:\usr\dev\jdk16_12\bin\javac": >>> CreateProcess error=5, Access is denied >>> at java.lang.ProcessBuilder.start(ProcessBuilder.java:459) >>> at >>> com.google.appengine.tools.admin.Application.startProcess(Application.java:434) >>> at >>> com.google.appengine.tools.admin.Application.compileJavaFiles(Application.java:393) >>> at >>> com.google.appengine.tools.admin.Application.compileJsps(Application.java:361) >>> at >>> com.google.appengine.tools.admin.Application.createStagingDirectory(Application.java:237) >>> at >>> com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:51) >>> at >>> com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngineBridgeImpl.java:271) >>> at >>> com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(DeployProjectJob.java:148) >>> at >>> org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) >>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) >>> Caused by: java.io.IOException: CreateProcess error=5, Access is denied >>> at java.lang.ProcessImpl.create(Native Method) >>> at java.lang.ProcessImpl.(ProcessImpl.java:81) >>> at java.lang.ProcessImpl.start(ProcessImpl.java:30) >>> at java.lang.ProcessBuilder.start(ProcessBuilder.java:452) >>> ... 9 more >>> >>> >>> >>> However if I remove the jsp file from the war folder the deployment works >>> fine. FYI, the jsp is an empty file. Can someone suggest what is going wrong >>> ??? >>> >>> >>> -- >>> Abhinav >>> >>> >> >> >> > > > --~--~-~--~~~---~--~~ 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-java@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: JSP errors in hosted mode
Hi Andy, At this point, no. For JSP errors generated by javac, the error will refer to locations inside the generated servlet class, instead of inside the JSP file it came from. Errors from the JSP compiler, on the other hand, *will*generally refer to the actual JSP file/line that caused the error. I see that you've already created an issue in the public tracker, which is exactly the right approach. Incidentally, you created an issue *just minutes* before I created essentially the same issue (issue 2131<http://code.google.com/p/googleappengine/issues/detail?id=2131>) on your behalf! That's ok, though; I'll go ahead and mark mine as a duplicate. Thanks for reporting this, Keith On Wed, Sep 16, 2009 at 11:23 AM, andy wrote: > > > I have been trying out Google App Engine for Java in Hosted mode > and ran into something I hope someone can shed some light on. I'm > using JSP pages and when a JSP page generates an error ( either > compilation or runtime ) the error message displayed contains > reference to the line number in the compiled servlet not the jsp > source. For example, the following error is displayed for a simple > invalid tag <% abc %>: > > Unable to compile class for JSP > > Generated servlet error: >[javac] C:\DOCUME~1\username\LOCALS~1\Temp > \Jetty_0_0_0_0_8080_warut4fm1\jsp\org\apache\jsp\index_jsp.java: > 53: ';' expected > > > Is there a way to get the GAE hosted mode server to display JSP > source line level error messages? > > Any help would be much appreciated. > > Andy > > > --~--~-~--~~~---~--~~ 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-java@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: JSP errors in hosted mode
Hi Andy, Actually, both the JSP compiler (Jasper) and javac process your JSPs. Jasper's compiler is really more of a pre-processor than an actual compiler: it just converts a JSP into source code for a Java servlet, which javac then compiles into Java bytecode. The problem comes when the Java servlet source that's generated by Jasper is malformed (due to errors in the JSP) and causes javac to generate errors. Those errors, as you noticed, refer to the locations within the generated servlet source code instead of in the original JSP. Internally, Jasper does maintain source mappings between the two, though, so it should be possible for the App Engine SDK to *always* report errors in terms of the original JSP. Keith On Wed, Sep 16, 2009 at 4:12 PM, andy wrote: > > > Thanks Keith. I somewhat understand your point. Since you say the > JSP compiler would give the desired information is there a way to > configure the hosted mode to use the JSP compiler instead of javac? > > From the IRC chat today it was suggested that I add an issue. The > issue I added was > http://code.google.com/p/googleappengine/issues/detail?id=2132. > > If anyone else feels this is an issue please feel free to star the > issue. > > Thanks again. > > On Sep 16, 11:49 am, Keith Platfoot wrote: > > Hi Andy, > > At this point, no. For JSP errors generated by javac, the error will > refer > > to locations inside the generated servlet class, instead of inside the > JSP > > file it came from. Errors from the JSP compiler, on the other hand, > > *will*generally refer to the actual JSP file/line that caused the > > error. > > > > I see that you've already created an issue in the public tracker, which > is > > exactly the right approach. Incidentally, you created an issue *just > > minutes* before I created essentially the same issue (issue > > 2131<http://code.google.com/p/googleappengine/issues/detail?id=2131>) > > on your behalf! That's ok, though; I'll go ahead and mark mine as a > > duplicate. > > > > Thanks for reporting this, > > > > Keith > > > > On Wed, Sep 16, 2009 at 11:23 AM, andy wrote: > > > > > I have been trying out Google App Engine for Java in Hosted mode > > > and ran into something I hope someone can shed some light on. I'm > > > using JSP pages and when a JSP page generates an error ( either > > > compilation or runtime ) the error message displayed contains > > > reference to the line number in the compiled servlet not the jsp > > > source. For example, the following error is displayed for a simple > > > invalid tag <% abc %>: > > > > > Unable to compile class for JSP > > > > > Generated servlet error: > > >[javac] C:\DOCUME~1\username\LOCALS~1\Temp > > > \Jetty_0_0_0_0_8080_warut4fm1\jsp\org\apache\jsp\index_jsp.java: > > > 53: ';' expected > > > > > Is there a way to get the GAE hosted mode server to display JSP > > > source line level error messages? > > > > > Any help would be much appreciated. > > > > > Andy > > > --~--~-~--~~~---~--~~ 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-java@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: My recommendation: Use Low-Level API instead of JDO/JPA
On Thu, Sep 24, 2009 at 10:10 AM, dflorey wrote: > > As this thread seems to be of some interest I'd like to summarize why > I'm happy with Low-Level API and why JDO caused a lot of pain to me. > Some of the points may be a matter of taste, some are just annoying - > others have been show stoppers to me: > > - Each time I save a persistent class the enhancer runs > - Sometimes the app gets deployed without enhanced classes (most > likely when saving files directly before deploy) Hi Daniel, I work on the Google Plugin for Eclipse, so I'd like to address the first two issues here, which appear to be Eclipse plugin-specific issues. - You're correct that the enhancer runs each time a persistent class is saved. However, as of the latest version of the plugin, this *should* be happening in a background job, and you should only notice it if there are errors. In this case, the plugin activates a Console window containing the enhancer errors. In contrast, the 1.0.x plugin activated the console even when there were no errors, which admittedly was pretty annoying. If you're using an older version of the plugin, I'd recommend upgrading to the latest release. If, on the other hand, you're seeing spurious errors every time you save a persistent class, then we'll need to investigate what's happening. - We're not currently enhancing all your project's persistent classes as part of the deploy process. However, we are planning on rethinking the way we handle enhancement, and it's possible that we'll need to perform an enhancement pass before launches and deploys, either in addition to, or as a replacement for, enhancements per persistent class save. Keith --~--~-~--~~~---~--~~ 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-java@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: Opening/closing projects in Eclipse
Hi Jay, I've never seen this particular error, but if you can send me your Eclipse log I can try to track it down. The log file should be at: */.metadata/.log* Thanks! On Thu, Sep 24, 2009 at 3:11 PM, Jay Damon wrote: > > I seems I may have found a bug with the GAE eclipse plugin. When I > select Open Project on a GAE project that was previously closed, e.g. > My First Web Application, it opens and may be run successfully. > However, it appears that if I shut down eclipse and restart it, the > data nucleus enhancer fails: > > java.lang.NoClassDefFoundError: com/google/appengine/tools/enhancer/ > Enhance > Exception in thread "main" > > If I select Close Project, then Open Project, it appears to solve the > problem. Has anyone else seen this? > > > > --~--~-~--~~~---~--~~ 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-java@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] Google Plugin for Eclipse 1.3 plans
Hey all, Many of you have reported incompatibilities between the Google Plugin for Eclipse and other build systems/project structures, most notably Maven and J2EE/Dynamic Web Projects. For example, issue 1515 (Eclipse plugin requires fixed location for war directory)<http://code.google.com/p/googleappengine/issues/detail?id=1515> has collected well over 100 stars, and a similar one in the GWT issue tracker has attracted a lot of attention as well. Based on this feedback, we've decided to try and address as many of the incompatibilities as possible with our upcoming 1.3 release of the plugin. To deliver on that goal, we want to share with your our current plans, and also let you know about a preview build that we'll make available so you can test the changes for yourself and give us feedback before final release. Our plans for the 1.3 release include 4 changes designed to make integration with Maven and J2EE projects easier: 1. The WAR directory can now be configured to be *any* project-relative path (e.g. src/main/webapp if you're using Maven). You'll also be able to specify whether that directory is source-only (typical Maven/J2EE scenario), or whether it should also function as the WAR output directory from which to run/debug or deploy to App Engine. If your WAR directory is input *and* output (which will remain the default for new Web App projects), the plugin will manage synchronizing the contents of WEB-INF/lib WEB-INF/classes with your project's build path and compiled output. Otherwise, we'll leave your WAR source directory alone and you'll need to specify your WAR output location when launching, deploying, etc (the plugin will remember the location once you set it the first time). 2. The Web App launch configuration UI is being redesigned to allow you to see, and if necessary change, *any* of the launch arguments. Previously, we were waiting until launch time to set many of these arguments based on heuristics that were invisible and inaccessible to you. Now you'll be in full control of how your projects get launched. Also, we're adding the capability to automatically migrate your launch configurations when necessary, for example, updating the -javaagent flag when changing App Engine SDKs. 3. GWT/App Engine projects will no longer require our SDK library on the classpath. This means Maven users will be able to pull in JAR files from their M2 repository as they're accustomed to and the plugin won't mind a bit. 4. The severity of any problem marker generated by the plugin will be fully customizable via an Errors/Warnings preference page (similar to the Java Errors/Warnings page), letting you specify either Error, Warning, or Ignore. We'll also be including a few smaller features and bug fixes as well. What does everyone think about the 4 changes outlined above? We've been testing the plugin against various Maven and J2EE configurations to try to ensure that we've eliminated the most critical roadblocks. However, we're very interested in also having you folks take it for a spin before the official release date (slated for next month). We're not quite ready yet, but stay tuned for a 1.3 preview build to be made available hopefully in a few weeks. We'll distribute it as a zip file for dropin installation<http://code.google.com/eclipse/docs/install-from-zip.html> so it will come with the standard warnings and caveats (use with a clean Eclipse install and workspace, use at your risk, etc.). However, it will hopefully give you a chance to give us any last-minute feedback about our changes before the final release. Thanks, Keith -- 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: Google Plugin for Eclipse 1.3 plans
Hi Marcel, The Eclipse plugin has a different release cycle than the App Engine SDK, so no, the current plugin version remains 1.2. Look the 1.3 version of the plugin to be released in March (with a preview build available near the end of this month). Keith On Thu, Feb 11, 2010 at 9:09 AM, Marcel Overdijk wrote: > SDK 1.3.1 was released today, so I was wondering if the 1.3 plugin is > also released, and more importantly if it contains better support for > maven as described in Keith's post. > > On Feb 9, 10:11 pm, Hannu Leinonen wrote: > > Allright, > > > > As I've stated before on the list, Maven + GAE Eclipse plugin > > integration is already possible! Exact instructions can be found in my > > blog post athttp:// > hamandeggs.wordpress.com/2010/01/26/how-to-gae-eclipse-maven/I > > also have made an archetype for such a project. I'm currently using > > pretty much the same configuration in one of my projects and it works > > quite well (only downside being that you're required to clean the > > project on every Eclipse startup). > > > > Just type: > > mvn org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate > \ > > -DarchetypeGroupId=org.beardedgeeks \ > > -DarchetypeArtifactId=gae-eclipse-maven-archetype \ > > -DarchetypeVersion=1.1.1 \ > > > > -DarchetypeRepository= > http://beardedgeeks.googlecode.com/svn/repository/releases > > > > -Hannu > > > > On 8.2.2010 20:35, Jake wrote: > > > > > > > > > I'm hoping for a good way to resolve workspace dependencies in > > > Eclipse. The m2eclipse plugin does this well, but that doesn't play > > > nicely with the maven-war-plugin, so it doesn't work for GAE. Running > > > a Maven Install on each workspace dependency before deploying, > > > however, is still nicer than having to manually generate/copy jar > > > files. I'm pretty new to Eclipse/Maven/GAE, so I don't know if it's > > > possible, but I'm hopeful! :) > > > > > Jake > > > > > On Feb 6, 12:40 pm, 杨浩 wrote: > > >> Where's the lastest plugin update sites for GAE Plugin? > > >> I will to test it! > > > > >> 2010/2/6 Philippe Marschall > > > > >>> Sounds like a good start. Ideally the maven eclipse plugin [1] could > > >>> be configured to automatically generate the configuration for the > > >>> Google Plugin and M2Eclipse [2] picking that up as well. Also an > > >>> archetype would help quick starting. I assume you're aware that you > > >>> get the most benefit out of that only when there are up to date Maven > > >>> artifacts wit good metadata in a publicly available repo, preferably > > >>> Maven central. > > > > >>> [1]http://maven.apache.org/eclipse-plugin.html > > >>> [2]http://m2eclipse.sonatype.org/ > > > > >>> Cheers > > >>> Philippe > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] I cann't enhance my class?
That's quite odd. Are there any other exceptions in your error log (/.metadata/.log) that occurred around the same time as the NPE you reported? Keith 2010/2/17 sunzf > hello: > > when i enhance my class i get the follow error! > if i have jsp file in my workspace it can't be work(may be)! > now i enhance my class in other worksace it's only my enhance class,it work > ok! > > > Message: An internal error occurred during: "DataNucleus Enhancer". > Exception Stack Trace: > java.lang.NullPointerException > > at > com.google.gdt.eclipse.core.ProcessUtilities.cleanupProcess(ProcessUtilities.java:367) > > at > com.google.gdt.eclipse.core.ProcessUtilities.launchProcessAndActivateOnError(ProcessUtilities.java:271) > > at > com.google.appengine.eclipse.core.orm.enhancement.EnhancerJob.runInWorkspace(EnhancerJob.java:82) > > at > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > > Session Data: > eclipse.buildId=M20090917-0800 > java.version=1.6.0_07 > java.vendor=Sun Microsystems Inc. > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=zh_CN > Framework arguments: -product org.eclipse.epp.package.jee.product > > Command-line arguments: -os win32 -ws win32 -arch x86 -product > org.eclipse.epp.package.jee.product > > > -- > 使用新一代 Windows Live Messenger 轻松交流和共享！ > 立刻下载！<http://www.windowslive.cn/Messenger/> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: Deployment with Eclipse plug-in
This is likely related to the unscheduled outage earlier today. See http://code.google.com/status/appengine Keith On Wed, Feb 24, 2010 at 11:28 AM, Sandeep wrote: > Same here, haven't been able to deploy my updated app too. > > java.io.IOException: Error posting to URL: > > http://appengine.google.com/api/appversion/create?app_id=mdvk-chn&version=1&; > 500 Internal Server Error > > > > 500 Server Error > > > Error: Server Error > The server encountered an error and could not complete your > request.If the problem persists, please report your problem and > mention this error message and the query that caused it. > > > > at > > com.google.appengine.tools.admin.ServerConnection.send(ServerConnection.java: > 143) >at > > com.google.appengine.tools.admin.ServerConnection.post(ServerConnection.java: > 81) >at > > com.google.appengine.tools.admin.AppVersionUpload.send(AppVersionUpload.java: > 522) >at > > com.google.appengine.tools.admin.AppVersionUpload.beginTransaction(AppVersionUpload.java: > 339) >at > > com.google.appengine.tools.admin.AppVersionUpload.doUpload(AppVersionUpload.java: > 111) >at > com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java: > 56) >at > > com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngineBridgeImpl.java: > 271) >at > > com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(DeployProjectJob.java: > 148) >at > > org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java: > 38) >at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > > Also note: http://appengine.google.com/ is throwing 500 Internal > Errors. I do not think this is your app problem. > > Regards, > Sandeep > > On Feb 24, 9:00 pm, dominity wrote: > > Hey, guys. > > > > Currently I've got this message during deployment. > > > > java.io.IOException: Error posting to URL: > http://appengine.google.com/api/appversion/create?app_id=caretransfer... > > 500 Internal Server Error > > > > > > > > 500 Server Error > > > > > > Error: Server Error > > The server encountered an error and could not complete your > > request.If the problem persists, please report your problem and > > mention this error message and the query that caused it. > > > > > > > > How does it be processed? > > > > Best regards, Alexander. > > -- > 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] Google Plugin for Eclipse 1.3 Preview is now available
Hi everyone, Last month, I announced some of the changes we had planned for the 1.3 version of the Google Plugin for Eclipse. To recap, this release is focused on making life easier for developers using GWT/App Engine alongside third-party tools, including Maven and Eclipse for Java EE. In my post, I promised we'd let you download a preview of 1.3 to get some hands-on testing of the new features and provide us with your feedback before the official release. I'm happy to announce that the time has come. An early preview of 1.3 is now available for download at the following URLs: http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.suite.e35.feature_1.2.101.v201003031407.zip http://dl.google.com/eclipse/plugin/3.4/zips/com.google.gdt.eclipse.suite.e34.feature_1.2.101.v201003031407.zip http://dl.google.com/eclipse/plugin/3.3/zips/com.google.gdt.eclipse.suite.e33.feature_1.2.101.v201003031407.zip Note: Ensure that your version of Eclipse has Eclipse's Web Standard Tools (WST) installed before installing the plugin. WST can be installed by navigating to the Software Installation section, and selecting the the appropriate WST feature from the update site for your version of Eclipse. The update sites and feature names are provided below: - 3.5 (Galileo): Galileo > Web, XML, and Java EE Development > Eclipse Web Developer Tools - 3.4 (Ganymede): Ganymede Update Site > Web and Java EE Development > Web Developer Tools - 3.3 (Europa): Europa Discovery Site > Web and JEE Development > Web Standard Tools Project This is a preview build, so the usual caveats and warnings apply: it is not officially supported, and we recommend using a clean installation of Eclipse and a new workspace. Also, we're distributing this preview as a zip file so be sure to follow the instructions on our Installing the Google Plugin for Eclipse from zip files page ( http://code.google.com/eclipse/docs/install-from-zip.html). *Known Issues* - If you change settings in the Server or GWT tab in the launch configuration dialog, you'll need to switch to the Arguments tab before clicking Apply or Run/Debug. This will be fixed in the final release. That being said, we are very interested in your experience with this new release, which we hope will allow the Google plugin to interoperate much better with alternative project structures and third-party tools. The tentative 1.3 release notes are as follows: Enhancements - Configurable WAR directory to allow better integration with Eclipse for Java EE <http://www.eclipse.org/downloads/moreinfo/jee.php> and projects built with Maven <http://maven.apache.org/> - Web Application launch configurations now display and allow editing of generated Program and VM arguments - Errors/Warnings preference page for customizing the severity of any generated problem marker - Projects can reference GWT/App Engine SDKs directly via JARs instead of through SDK library - GWT+App Engine projects automatically configured for optimal caching Fixes - GWT Issue 3583<http://code.google.com/p/google-web-toolkit/issues/detail?id=3583>: Google Eclipse Plugin configuration is too strict - GWT Issue 3592<http://code.google.com/p/google-web-toolkit/issues/detail?id=3592>: Eclipse plugin to add 'cache forever' configuration for new 'GWT + App Engine' projects - GWT Issue 3902<http://code.google.com/p/google-web-toolkit/issues/detail?id=3902>: Allow users to configure the severity of problems reported by the eclipse plugin - App Engine Issue 1515<http://code.google.com/p/googleappengine/issues/detail?id=1515>: Eclipse plugin requires fixed location for war directory - App Engine Issue 2115<http://code.google.com/p/googleappengine/issues/detail?id=2115>: Using the @PersistenceAware annotation puts the Eclipse Enhancer in an Infinite Loop - App Engine Issue 1941<http://code.google.com/p/googleappengine/issues/detail?id=1941>: Plugin fails to enhance dependent classes on source level changes For a complete list of fixed issues, see the GWT issue tracker<http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=label:GPE_1_3> and App Engine issue tracker<http://code.google.com/p/googleappengine/issues/list?can=1&q=label:GPE_1_3> . We encourage all interested developers to take the preview build for a spin, and let us know what you think. We'll do everything possible to incorporate your feedback before the final release, slated for later this month. Thanks! Keith, on behalf of the Google Plugin for Eclipse team -- 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: Google Plugin for Eclipse 1.3 plans
In case anyone on this thread missed announcement, the Google Plugin for Eclipse 1.3 preview is now available: http://groups.google.com/group/google-appengine-java/browse_thread/thread/460417b76e30c366/a7d8a913ef023878 Keith 2010/2/17 Miguel Méndez > It has not been released yet. We expect the preview to be available around > the end of the month. We'll send out an announcement when it is ready. > > > On Tue, Feb 16, 2010 at 11:47 PM, KasperDK wrote: > >> Hi all, >> >> Where exactly is the Google Plugin for Eclipse preview located ? Or is >> it not released yet ? Im dying to try it out :-) >> >> Cheers, >> >> :-) Kasper >> >> On Feb 4, 8:52 pm, Keith Platfoot wrote: >> > Hey all, >> > >> > Many of you have reported incompatibilities between the Google Plugin >> for >> > Eclipse and other build systems/project structures, most notably Maven >> and >> > J2EE/Dynamic Web Projects. For example, issue 1515 (Eclipse plugin >> requires >> > fixed location for war >> > directory)< >> http://code.google.com/p/googleappengine/issues/detail?id=1515> >> > has >> > collected well over 100 stars, and a similar one in the GWT issue >> tracker >> > has attracted a lot of attention as well. Based on this feedback, we've >> > decided to try and address as many of the incompatibilities as possible >> with >> > our upcoming 1.3 release of the plugin. To deliver on that goal, we >> want to >> > share with your our current plans, and also let you know about a preview >> > build that we'll make available so you can test the changes for yourself >> and >> > give us feedback before final release. >> > >> > Our plans for the 1.3 release include 4 changes designed to make >> integration >> > with Maven and J2EE projects easier: >> > >> >1. The WAR directory can now be configured to be *any* >> project-relative >> >path (e.g. src/main/webapp if you're using Maven). You'll also be >> able >> >to specify whether that directory is source-only (typical Maven/J2EE >> >scenario), or whether it should also function as the WAR output >> directory >> >from which to run/debug or deploy to App Engine. If your WAR >> directory is >> >input *and* output (which will remain the default for new Web App >> >projects), the plugin will manage synchronizing the contents of >> WEB-INF/lib >> >WEB-INF/classes with your project's build path and compiled output. >> > Otherwise, we'll leave your WAR source directory alone and you'll >> need to >> >specify your WAR output location when launching, deploying, etc (the >> plugin >> >will remember the location once you set it the first time). >> >2. The Web App launch configuration UI is being redesigned to allow >> you >> >to see, and if necessary change, *any* of the launch arguments. >> > Previously, we were waiting until launch time to set many of these >> >arguments based on heuristics that were invisible and inaccessible to >> you. >> > Now you'll be in full control of how your projects get launched. >> Also, >> >we're adding the capability to automatically migrate your launch >> >configurations when necessary, for example, updating the -javaagent >> flag >> >when changing App Engine SDKs. >> >3. GWT/App Engine projects will no longer require our SDK library on >> the >> >classpath. This means Maven users will be able to pull in JAR files >> from >> >their M2 repository as they're accustomed to and the plugin won't >> mind a >> >bit. >> >4. The severity of any problem marker generated by the plugin will be >> >fully customizable via an Errors/Warnings preference page (similar to >> the >> >Java Errors/Warnings page), letting you specify either Error, >> Warning, or >> >Ignore. >> > >> > We'll also be including a few smaller features and bug fixes as well. >> > >> > What does everyone think about the 4 changes outlined above? We've been >> > testing the plugin against various Maven and J2EE configurations to try >> to >> > ensure that we've eliminated the most critical roadblocks. However, >> we're >> > very interested in also having you folks take it for a spin before the >>
[appengine-java] Re: Google Plugin for Eclipse 1.3 Preview is now available
Hey again, Just wanted to mention that to actually customize your project's WAR directory (enhancement bullet 1 in the announcement email), you'll need to navigate to Google > Web Application in your project properties dialog. You can use any project-relative path as the WAR directory (e.g. src/main/webapp) and you can also use the checkbox below to toggle whether or not you want to launch and deploy from that directory, by default. If you uncheck that option, Eclipse will prompt you for a location the first time you launch your project, and will not mess with the JARs in /WEB-INF/lib or try to move your build output directory to /WEB-INF/classes. You can think of the checkbox as the *Keep your hands off my runtime WAR directory!* option. :-) If anyone runs into issues or has questions about any of the new features, don't hesitate to ask. Thanks! Keith On Wed, Mar 3, 2010 at 7:26 PM, Keith Platfoot wrote: > Hi everyone, > > Last month, I announced some of the changes we had planned for the 1.3 > version of the Google Plugin for Eclipse. To recap, this release is focused > on making life easier for developers using GWT/App Engine alongside > third-party tools, including Maven and Eclipse for Java EE. In my post, I > promised we'd let you download a preview of 1.3 to get some hands-on testing > of the new features and provide us with your feedback before the official > release. > > I'm happy to announce that the time has come. An early preview of 1.3 is > now available for download at the following URLs: > > > http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.suite.e35.feature_1.2.101.v201003031407.zip > > > http://dl.google.com/eclipse/plugin/3.4/zips/com.google.gdt.eclipse.suite.e34.feature_1.2.101.v201003031407.zip > > > http://dl.google.com/eclipse/plugin/3.3/zips/com.google.gdt.eclipse.suite.e33.feature_1.2.101.v201003031407.zip > > Note: Ensure that your version of Eclipse has Eclipse's Web Standard Tools > (WST) installed before installing the plugin. WST can be installed by > navigating to the Software Installation section, and selecting the the > appropriate WST feature from the update site for your version of Eclipse. > The update sites and feature names are provided below: > > >- 3.5 (Galileo): Galileo > Web, XML, and Java EE Development > Eclipse >Web Developer Tools >- 3.4 (Ganymede): Ganymede Update Site > Web and Java EE Development > >Web Developer Tools >- 3.3 (Europa): Europa Discovery Site > Web and JEE Development > Web >Standard Tools Project > > This is a preview build, so the usual caveats and warnings apply: it is > not officially supported, and we recommend using a clean installation of > Eclipse and a new workspace. Also, we're distributing this preview as a zip > file so be sure to follow the instructions on our Installing the Google > Plugin for Eclipse from zip files page ( > http://code.google.com/eclipse/docs/install-from-zip.html). > > *Known Issues* > > >- If you change settings in the Server or GWT tab in the launch >configuration dialog, you'll need to switch to the Arguments tab before >clicking Apply or Run/Debug. This will be fixed in the final release. > > That being said, we are very interested in your experience with this new > release, which we hope will allow the Google plugin to interoperate much > better with alternative project structures and third-party tools. The > tentative 1.3 release notes are as follows: > > Enhancements > > >- Configurable WAR directory to allow better integration with Eclipse >for Java EE <http://www.eclipse.org/downloads/moreinfo/jee.php> and >projects built with Maven <http://maven.apache.org/> >- Web Application launch configurations now display and allow editing >of generated Program and VM arguments >- Errors/Warnings preference page for customizing the severity of any >generated problem marker >- Projects can reference GWT/App Engine SDKs directly via JARs instead >of through SDK library >- GWT+App Engine projects automatically configured for optimal caching > > Fixes > > >- GWT Issue > 3583<http://code.google.com/p/google-web-toolkit/issues/detail?id=3583>: >Google Eclipse Plugin configuration is too strict >- GWT Issue > 3592<http://code.google.com/p/google-web-toolkit/issues/detail?id=3592>: >Eclipse plugin to add 'cache forever' configuration for new 'GWT + App >Engine' projects >- GWT Issue > 3902<http://code.google.com/p/google-web-toolkit/issues/detail?id=3902>: >Allow users to configure the severity of problems reported by the eclipse >
[appengine-java] Google Plugin for Eclipse 1.3 is now available
Hi everyone, I'm happy to announce the release of version 1.3 of the Google Plugin for Eclipse (http://code.google.com/eclipse). This release is designed to make life easier for developers using GWT and/or App Engine alongside third-party tools. For example, we've taken the pain out of using the plugin with projects built with the ever-popular Maven build system: no more ugly hacks or workarounds, or polluted WEB-INF/lib directories! We've even added a new FAQ dedicated to Maven usage: http://code.google.com/eclipse/docs/faq.html#gwt_with_maven. We've also worked hard to make sure the plugin works well with Dynamic Web projects in Eclipse for Java EE. See the following FAQ for details on this scenario: http://code.google.com/eclipse/docs/faq.html#gwt_in_eclipse_for_java_ee. In addition to improving third-party interoperability, we've also made the plugin more customizable and robust overall. Launch configurations now allow direct editing of generated command line arguments, and a new Errors/Warnings preference page lets you tweak the severity of any problem marker we create. We've also fixed a number of bugs related to App Engine ORM enhancement. To install the Google Plugin for Eclipse, you can find our update site URLs, along with detailed instructions, here: http://code.google.com/eclipse/docs/download.html If you're upgrading from a previous version of the plugin, you may want to consult our Upgrading the Plugin guide: http://code.google.com/eclipse/docs/updating_the_plugin.html *Note: If you installed the Google Plugin for Eclipse 1.3 Preview, be sure to remove the relevant subfolders from your /dropins folder before installing the official 1.3 release via the update site.* *Enhancements* - Configurable WAR directory to allow better integration with Eclipse for Java EE and projects built with Maven - Web Application launch configurations now display and allow editing of generated Program and VM arguments - Errors/Warnings preference page for customizing the severity of any generated problem marker - Projects can reference GWT/App Engine SDKs directly via JARs instead of through SDK library - GWT+App Engine projects automatically configured for optimal caching *Fixes* - GWT Issue 3583: Google Eclipse Plugin configuration is too strict - GWT Issue 3592: Eclipse plugin to add 'cache forever' configuration for new 'GWT + App Engine' projects - GWT Issue 3902: Allow users to configure the severity of problems reported by the eclipse plugin - App Engine Issue 1515: Eclipse plugin requires fixed location for war directory - App Engine Issue 2115: Using the @PersistenceAware annotation puts the Eclipse Enhancer in an Infinite Loop - App Engine Issue 1941: Plugin fails to enhance dependent classes on source level changes For a complete list of fixed issues, see the GWT issue tracker and App Engine issue tracker. We hope you enjoy using this new version of the Google Plugin for Eclipse for all your GWT/App Engine development needs! Let us know if you have questions or run into any issues. Thanks! Keith, on behalf of the Google Plugin for Eclipse team -- 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: Google Plugin for Eclipse 1.3 is now available
Hi Vlad, You should be able to develop and debug App Engine applications in Eclipse for Java EE in much the same way you would a GWT application, although there are a few key differences. I believe the main difference is that with App Engine, you will need to use its included Development Server ( http://code.google.com/appengine/docs/java/tools/devserver.html) rather than your own app server (Tomcat, Jetty, Glassfish, etc.). The Development Server simulates the runtime environment of Google App Engine, and is necessary for testing datastore, login, etc. Regarding multiple projects: we generally recommend using a single project if possible to keep things simpler. Also, the plugin may make it difficult to split across multiple projects, if you run/debug directly from your source WAR directory (project properties > Google > Web Application > Launch and deploy from this directory). In this scenario, the plugin automatically sets the project's build output path to /WEB-INF/classes, so you'll probably run into some issues with multiple projects, since they each need to contribute class files and/or jars into that same WAR directory. However, if you use Eclipse for Java EE and run GWT with -noserver, multiple projects *should* work, since WTP will take care of populating WEB-INF/classes and WEB-INF/lib automatically. Keith , although with Eclipse for Java EE, you may be able to get away On Wed, Mar 17, 2010 at 4:55 PM, Vlad Skarzhevskyy wrote: > Thanks Google for hard work! > > In your FAQ you made a big efforts to support Dynamic Web projects in > Eclipse for Java EE for GWT applications. Does the same apply for App > Engine projects? > > What is the recommended way to make complex GWT and App Engine > applications? > In template projects created by Plugin you see all in one project. > Client and server are all together with one classpath. What would be > the real world scenario with Client projects(modules) and server > project(modules) all in separate Eclipse projects? > > Regards, > Vlad > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: GPE 1.3 Tutorial?
Hi Jake, There's nothing in the Google Plugin for Eclipse that makes it incompatible with Maven+App Engine, per se. We just chose to add FAQs specifically for Maven+GWT since that case is probably a bit more complicated, because it requires using additional launch arguments, etc. On the flip side, it is also possible to serve GWT-only projects from other servlet containers like Tomcat or Jetty, which enables developers to use Eclipse for Java EE to create a runtime staging directory and automatically mirror changes into it, while the app is being debugged. App Engine applications, on the other hand, need to be run locally on the App Engine Development Server ( http://code.google.com/appengine/docs/java/tools/devserver.html), which simulates services like datastore, user login, etc. It is still possible to use the Google Plugin for Eclipse with an App Engine project, but it may require a few hacks or manual steps in order to keep the runtime WAR directory in sync with your changes. The process would actually be very close to the one described at the bottom of the GWT+Maven GPE FAQ ( http://code.google.com/eclipse/docs/faq.html#gwt_with_maven). Check out the instructions below the line: *If you're *not* able to use Eclipse for Java EE...* * * If developers of Maven-built App Engine projects would find it useful, we could probably add another FAQ entry specifically for that case. Keith On Tue, Mar 23, 2010 at 9:22 AM, Jake wrote: > Hey, > > I see now - the front page lists Maven support (and other things), but > under GWT. I was under the impression that they were closely linked > enough that it would work for me as well. I also don't really > understand what about GWT would suddenly allow me to use Maven to > resolve dependencies? But yes, I'm just using App Engine so I'll > return to my hacked Maven/Ant method that was working before. Some > day, I would love to use the Google Plugin for Eclipse! > > Jake > > On Mar 22, 11:52 am, Jason Parekh wrote: > > Hey Jake, > > > > GPE 1.3 introduces support for Maven when working with GWT projects, but > it > > doesn't look like you're using GWT (only App Engine, correct?). If this > is > > true, then those FAQ entries aren't relevant as they're only for GWT or > GWT > > + App Engine projects. > > > > Unfortunately, we don't have any instructions for your configuration, but > if > > you do gain any traction, please let us know and we can update our FAQ. > > > > Thanks, > > jason > > > > On Fri, Mar 19, 2010 at 2:05 PM, Jake wrote: > > > Hey all, > > > > > I've swapped to Google Plugin for Eclipse 1.3 in the hopes that I can > > > use it with Maven and resolving workspace dependencies. I have > > > created a copy of my previously working project, upgraded to the > > > latest GAE SDK and m2e plugin and have tried to follow the GPE FAQ > > > instructions with Eclipse 3.5 EE. They don't always match up and > > > depending on what I'm doing, I get the following issues: > > > > > 1. As instructed, I'm unchecking "Run built-in server" in the Web > > > Application run configuration. However, it shows the following error: > > > "App Engine projects need to run the built-in server." > > > > > 2. When running the Web Application Configuration, the console ONLY > > > displays: > > > Usage: [options] > > > ... > > > > > 3. I'm not entirely certain of how the process should go. Do I start > > > my Tomcat 1.6 instance first and THEN do Run As Google Web > > > Application? Who is responsible for initializing my servlet? I know > > > almost nothing Tomcat or running a server, so if this is the problem I > > > would appreciate some detail. > > > > > Thanks in advance for the help! > > > > > Jake > > > > > -- > > > 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. > > -- 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] app engine Eclipse plugin failed to install
Hi Tony, Eclipse WST (Web Standard Tools) is a dependency of the Google Plugin for Eclipse, but it looks like the Eclipse install process is having trouble finding it. Make sure the Eclipse update site is enabled, as per the instructions in this FAQ: http://code.google.com/eclipse/docs/faq.html#wstinstallerror Keith On Wed, Mar 24, 2010 at 12:52 AM, Tony Luo wrote: > Any ideas why? > > An error occurred while collecting items to be installed > No repository found containing: org.eclipse.wst.css.core/osgi.bundle/ > 1.1.201.v200808072008 > No repository found containing: org.eclipse.wst.css.ui/osgi.bundle/ > 1.0.301.v200807170605 > No repository found containing: org.eclipse.wst.html.core/ > osgi.bundle/1.1.204.v200901141603 > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: GPE 1.3 Tutorial?
Hi Jake, If we (as the Google Plugin for Eclipse team) do an FAQ on Maven + App Engine, it would be simply describe how to get such a setup working with Eclipse. I must admit that I have not worked through all the details yet, but in theory if you have an App Engine project working with Maven, using it with the Eclipse plugin should be similar to the bottom half of the GWT+Maven FAQ I referenced earlier in this thread. The broader issue of documenting best practices for actually building App Engine projects with Maven in the first place would be better handled by the App Engine team. There appears to already be an issue related to Maven + App Engine integration: http://code.google.com/p/googleappengine/issues/detail?id=1296 Keith On Wed, Mar 24, 2010 at 1:42 PM, Jake wrote: > Hello, > > I would very much appreciate an FAQ for GAE + Maven - there are > several blogs/plugins/etc that attempt to set it up in a haphazard > way, but I feel like there should be a stable, "Google-approved" > method. I personally have my own hacked together situation that works > about as well as anyone has described, but it's not perfect/clean/etc. > > The key difficulty for me seems to be that in non-GAE projects, > Eclipse/Maven can resolve dependencies in the Workspace cleanly, > without running 'mvn install' on each one. I haven't found a GAE > solution that does that and hoped the GPE would solve that. > > Thanks for the info! > > Jake > > On Mar 24, 12:34 am, jd wrote: > > On Mar 24, 3:53 am, Keith Platfoot wrote: > > > > > It is still possible to > > > use the Google Plugin for Eclipse with an App Engine project, but it > may > > > require a few hacks or manual steps in order to keep the runtime WAR > > > directory in sync with your changes. > > > > I found this Eclipse plugin, FileSync, really useful to keep /src/main/ > > webapp in sync with /target/myapp-deploy-dir/ > > > > http://andrei.gmxhome.de/filesync/usage.html > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: GAE Plugin not working.
Dennis, Are you running Eclipse with Administrator privileges? We've had other users report they had to do so in order to successfully install the Google Plugin for Eclipse. Keith On Tue, Mar 30, 2010 at 10:28 PM, dennisM wrote: > I can't get Appengine for Java 1.3.2 Eclipse plugin for Galileo to > install properly on Windows 7. I get a variety of error messages about > jars already being there, I'll post more specific info about the > errors shortly, but thought this might be familiar to others. > > Is there something special I need to do to get the plugin to work on > Windows 7? > > On Mar 5, 2:33 pm, Ahmad wrote: > > I am also unable to install gae plugin for eclipse 3.5 -- > > gelilio , on windows7 > > -- > 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] Getting a LOT of mysterious 500 responses
Hi, on our tiny little web service http://findbugs-cloud.appspot.com, we're getting a whole lot of 500 responses, with a mysterious message. It started a few months ago and has slowly but steadily gotten worse since. Since a 500 response makes our continuous build fail, it's getting irritating... Request was aborted after waiting too long to attempt to service your request. This may happen sporadically when the App Engine serving cluster is under unexpectedly high or uneven load. If you see this message frequently, please contact the App Engine team. Also irritating is that these only show up as "warnings" so sometimes I don't even notice they're happening. Any idea what's going on? Are we just on a bad cluster? Can we get moved somehow? -- 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] Dev App Server closing connection prematurely
Hi all,
I'm having an issue where the dev app server is sometimes truncating
HTTP responses, with the HTTP client seeing "Connection reset by
peer".
The server will write a certain number of bytes to the client
connection and then hangup mid-transfer.
For example I am expecting a response of length 153588 bytes and only
74256 bytes are read by the client before the connection is reset.
The 'cutoff point' (the point in the data where the connection drops)
varies, sometimes 74256 bytes are transferred, sometimes123280.
I am running the server from ant on the command line, on OSX 10.6,
though I have seen it fail using the Eclipse plugin too.
I get no error messages, core dumps or anything like that I can see.
My servlet is fairly simple. It is stateless, fetching an XML
document over HTTP, applying some transformations to it and serving
the result.
Here's a simplified version - I'm not doing anything fancy:
protected void doGet(HttpServletRequest request, HttpServletResponse
response)
throws ServletException, IOException
{
response.setContentType("text/xml");
String output =
translateDocument(request.getParameter("docURL"));
response.setContentLength(output.length());
response.getWriter().write(output);
}
Totally mystified!
Any ideas?
Thanks!
Keith
--
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.
