[appengine-java] Re: 1.3.8 Console Logging Issue

2010-12-05 Thread MarkH 
I'm still having Eclipse console logging issues with 1.4.0. (OSX10.6.5/
Helios).

I tried the following:
1. Used the Eclipse plugin to generate a new GWT/AppEngine app.
2. Added a java.util.logging.Logger to the GreetingServiceImpl
3. Added logger.fine("test"); to the greetServer call
4. set logging.properites level to .level = FINE

As per 1.3.8 there are still no logger.fine log message in the Eclipse
console.

As per 1.3.8 logger.info adds messages to the console in the same
format as the Jetty startup phase - message text only (no date, or
logger info).

As per 1.3.8 setting the Run Configuration -> Arguments -> Program
Arguments to, -logLevel DEBUG does causes logger.fine messages
(message text only) to appear on the console, along with the
associated GWT noise.

Is it possible to restore 1.3.7 like 'SimpleFormatter' style logging:
date, logger, message in the Eclipse console?

On Nov 22, 4:23 pm, timzon  wrote:
> Thank you. Looking forward to get 1.4.0.
>
> On Nov 4, 9:33 am, Rajeev Dayal  wrote:
>
>
>
>
>
>
>
> > We're going to fix this for the App Engine 1.4.0 release. What we'll do is
> > have messages at Log.INFO level be outputted when you've got your Launch
> > Configuration's log level set to INFO.
>
> > In the Google Plugin for Eclipse, we'll make a change such that any new
> > launch configurations created have a default log level of WARN.
>
> > On Thu, Nov 4, 2010 at 4:23 AM, Stefano Ciccarelli <
>
> > stef...@indacosoftware.it> wrote:
> > > I changed the GWT log level to TRACE solving partially the problem, infact
> > > now I have very verbose logs.
>
> > > On Wed, Nov 3, 2010 at 15:33, Rajeev Dayal  wrote:
>
> > >> No, I did not mean dropping it there - I meant changing it in the Web App
> > >> Launch Configuration UI - edit your launch configuration (in Eclipse), 
> > >> and
> > >> set the log level to TRACE. Does that help?
>
> > >> On Tue, Nov 2, 2010 at 10:38 PM, timzon  wrote:
>
> > >>> Dropping default log level (.level) to TRACE, INFO or FINEST doesn't
> > >>> fix the problem.
>
> > >>> log.info (with default INFO level) used to work before 1.3.8 upgrade
> > >>> and doesn't work after the upgrade.
>
> > >>> On Oct 29, 2:49 pm, Rajeev Dayal  wrote:
> > >>> > Drop you launch configuration's log level down to TRACE. Do you see 
> > >>> > the
> > >>> > messages now?
>
> > >>> > On Fri, Oct 29, 2010 at 1:23 PM, John Bito  > >>> >wrote:
>
> > >>> > > Starred the issue:
> > >>> > >http://code.google.com/p/googleappengine/issues/detail?id=3969
>
> > >>> > >  --
> > >>> > > 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 > >>> > >  unsubscr...@googlegroups.com> > >>> 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 > >>>  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 > >>  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 > >  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

2010-12-05 Thread Mike 
Yeah, I had the same problem and fixed it by making sure that App
Engine SDK 1.4 was First in the Java Build Path -> Order and Export.
And that GWT SDK 2.1.0 was second.

Mike

On Dec 5, 7:28 am, Sudhir  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  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  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 org.apache.jasper.compiler.Compiler.compile(Compiler.java:314)
> > >         at
> > > org.apache.jasper.JspCompilatio

[appengine-java] Tic Tac Toe live demo

2010-12-05 Thread abcdroid 
http://channel-remote.appspot.com/

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

[appengine-java] Re: 1.4 eclipse plugin

2010-12-05 Thread Stream18 
Hi Sudhir,

I finally managed to solve this (at least ir worked for me). Just edit
the ".classpath" file in your eclipse project and review the order of
this two entries:



I had GWT_CONTAINER before GAE_CONTAINER, after reordering it started
compiling JSPs again.
Hope this helps,

Eduardo.


On Dec 5, 2:28 pm, Sudhir  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  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  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)

[appengine-java] Re: Local datastore empty after updating to SDK 1.4.0

2010-12-05 Thread Nello 
I've seen this in the past.  As far as I can see it's par for the
course.  The GAE developers have very little respect for our test
data.  I'm still worried about taking any of this to production
because it is so obviously in permanent beta.


On Dec 5, 1:40 am, Fabrizio  wrote:
> I have a project with a local datastore. There was many entities in
> it.
>
> I have update the sdk from 1.3.7 to 1.4.0. Now the local datastore is
> empty. My app does not show data and local management tell datastore
> is empty (http://localhost:/_ah/admin/datastore).
>
> I've also tried to "revert" the local_db.bin file to my previous
> version from my local subversion. But it does not work.   :(
>
> Any idea?
>
> Fabrizio

-- 
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

2010-12-05 Thread Mike Friesen 
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  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  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  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.compil

[appengine-java] Spring Security login problem with IE8 for app within frame (on GAE)

2010-12-05 Thread Nello 
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 at 
http://groups.google.com/group/google-appengine-java?hl=en.

[appengine-java] Re: Tic Tac Toe not there

2010-12-05 Thread abcdroid 
Thanks.

live demo here: http://goo.gl/Y1mbz

-- 
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] War fails to deploy locally due to FactoryConfigurationError

2010-12-05 Thread ankur 
Hello,

I am trying to deploy the sample app on local machine but getting the
error below.
The server starts but the application fails to deploy .
This is confusing to me as only the appengine and  standard java
libraries are on the build path.

Environment:
  Google App Engine Java SDK 1.4.0
  Google Plugin for Eclipse 3.5
JDK1.6

Error Log:
WARNING: failed jettycontainerservice$apiproxyhand...@73a34b:
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.SAXParserFactoryImpl could not be instantiated:
java.lang.NullPointerException
Dec 5, 2010 10:59:28 PM com.google.apphosting.utils.jetty.JettyLogger
warn
WARNING: Error starting handlers
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.SAXParserFactoryImpl could not be instantiated:
java.lang.NullPointerException
at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
at org.mortbay.xml.XmlParser.(XmlParser.java:69)
at
org.mortbay.jetty.webapp.WebXmlConfiguration.webXmlParser(WebXmlConfiguration.java:
83)
at
org.mortbay.jetty.webapp.WebXmlConfiguration.(WebXmlConfiguration.java:
78)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at
org.mortbay.jetty.webapp.WebAppContext.loadConfigurations(WebAppContext.java:
858)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
430)
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.(DevAppServerMain.java:
113)
at
com.google.appengine.tools.development.DevAppServerMain.main(DevAppServerMain.java:
89)
Dec 5, 2010 10:59:28 PM com.google.apphosting.utils.jetty.JettyLogger
warn
WARNING: Nested in javax.xml.parsers.FactoryConfigurationError:
Provider org.apache.xerces.jaxp.SAXParserFactoryImpl could not be
instantiated: java.lang.NullPointerException:
java.lang.NullPointerException
at javax.xml.parsers.FactoryFinder.newInstance(Unknown Source)
at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown
Source)
at javax.xml.parsers.FactoryFinder.find(Unknown Source)
at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
at org.mortbay.xml.XmlParser.(XmlParser.java:69)
at
org.mortbay.jetty.webapp.WebXmlConfiguration.webXmlParser(WebXmlConfiguration.java:
83)
at
org.mortbay.jetty.webapp.WebXmlConfiguration.(WebXmlConfiguration.java:
78)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at
org.mortbay.jetty.webapp.WebAppContext.loadConfigurations(WebAppContext.java:
858)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
430)
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

[appengine-java] Re: 1.4 eclipse plugin

2010-12-05 Thread Mike 
I fixed this problem by making sure that App Engine SDK 1.4.0 is first
in my Java Build Path in the Order and Export and changing my GWT SDK
to 2.1.0

-- 
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] InvalidValueException: Non-incrementable value for key ...

2010-12-05 Thread Lior Harsat 
Hi,


I've been getting an "InvalidValueException: Non-incrementable value
for key..." In my logs from time to time.
This exception is thrown by a call to MemcacheService.increment(Object
key, long delta, Long initialValue).
The value I am incrementing is an integer.
The documentation states that this exceptiob is "Thrown when a cache
entry has content, but it cannot be read. For example:
- An attempt to MemcacheService.increment(java.lang.Object, long) a
non-integral value
- Version skew between your application and the data in the cache,
causing a serialization error."
I dont think my scenario fits the above examples.
Can anyone shed some light on this exception and its causes/meaning?


Thanx, Lior

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Re: [appengine-java] Re: Local datastore empty after updating to SDK 1.4.0

2010-12-05 Thread Fabrizio Accatino 
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 wrote:

> 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] big table parent-child

2010-12-05 Thread asianCoolz 
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: 1.4 eclipse plugin

2010-12-05 Thread Nick 
Same error...JSPs are not working with 1.4.0

On Dec 5, 6:58 pm, Jaroslav Záruba  wrote:
> Same error, syncing the JARs has not helped. :(
> It appears to me there's still hiding one incompatible (Jasper?)
> library somewhere.
>
> I guess I just have bad luck. Every time I upgrade GAE/GWT Eclipse
> plugin or SDK I end up doing clean install of Eclipse. :(
>
> On Dec 5, 7:36 pm, Rajeev Dayal  wrote:
>
>
>
>
>
>
>
> > Hi,
>
> > If you navigate to Project Properties -> Google -> Web Application, do you
> > have the option "Launch and deploy from this directory" checked? If so, when
> > you switched SDKs on your project, the Google Plugin for Eclipse should have
> > copied over the new libraries from the SDK over to your war/WEB-INF/lib
> > directory.
>
> > Have you manually copied/modified/removed any of the App Engine-related
> > libraries in the war/WEB-INF/lib folder? If so, then the Google Plugin for
> > Eclipse will not overwrite those changes on an SDK switch. What will happen
> > is that when switching SDKs, a warning will appear in the problems view,
> > indicating that there is a mismatch between the SDK jars and those in your
> > war/WEB-INF/lib folder. By selecting the warning and hitting CTRL-1, you'll
> > be given the option to synchronize the jars in the new SDK with the jars in
> > war/WEB-INF/lib.
>
> > Rajeev
>
> > On Fri, Dec 3, 2010 at 9:30 PM, GoSharp Lite  wrote:
> > > I have just upgraded Eclipse Galileo with AppEngine version 1.4.0.
> > > There seems to be a mismatch of Tomcat versions between pre-
> > > compilation and execution.
>
> > > Does anyone have a solution with jsp compilation issue?
>
> > > Local server shows below logs with SDK 1.4.0 -
> > > HTTP ERROR 500
>
> > > Problem accessing /. Reason:
> > > Unable to compile class for JSP:
>
> > > An error occurred at line: -1 in the generated java file
> > >    [javac] D:\Profiles\LOCALS~1\Temp\Jetty_0_0_0_0__warmasbuh
> > > \jsp\org\apache\jsp\GoChildWeb_jsp.java:8:
> > > org.apache.jsp.GoChildWeb_jsp is not abstract and does not override
> > > abstract method getDependants() in
> > > org.apache.jasper.runtime.JspSourceDependent
> > >    [javac] public final class GoChildWeb_jsp extends
> > > org.apache.jasper.runtime.HttpJspBase
> > >    [javac]              ^
>
> > > An error occurred at line: -1 in the generated java file
> > >    [javac] D:\Profiles\LOCALS~1\Temp\Jetty_0_0_0_0__warmasbuh
> > > \jsp\org\apache\jsp\GoChildWeb_jsp.java:18: getDependants() in
> > > org.apache.jsp.GoChildWeb_jsp cannot implement getDependants() in
> > > org.apache.jasper.runtime.JspSourceDependent; attempting to use
> > > incompatible return type
> > >    [javac] found   : java.lang.Object
> > >    [javac] required: java.util.List
> > >    [javac]   public Object getDependants() {
> > >    [javac]                 ^
>
> > > An error occurred at line: -1 in the generated java file
> > >    [javac] D:\Profiles\LOCALS~1\Temp\Jetty_0_0_0_0__warmasbuh
> > > \jsp\org\apache\jsp\GoChildWeb_jsp.java:23: cannot find symbol
> > >    [javac] symbol  : method
> > > getJspApplicationContext(javax.servlet.ServletContext)
> > >    [javac] location: class javax.servlet.jsp.JspFactory
> > >    [javac]     _el_expressionfactory =
>
> > > _jspxFactory.getJspApplicationContext(getServletConfig().getServletContext(
> > >  )).getExpressionFactory();
> > >    [javac]                                         ^
> > >    [javac] 3 errors
>
> > > On Dec 4, 6:30 am, Alex Humesky  wrote:
> > > > GPE's AppEngine SDK bundle version 1.4.0 is now up. Sorry for the
> > > > delay.
>
> > > > On Dec 3, 11:02 am, Don Schwarz  wrote:
>
> > > > > My apologies.  We plan to have it up before the end of the day today.
>
> > > > > On Fri, Dec 3, 2010 at 9:26 AM, Royce Fullerton 
> > > wrote:
> > > > > > When will the Eclipse plugin update site be updated?
>
> > > > > > The plugin is now version 1.4, but the SDK is still version 1.3.8.
>
> > > > > > On Dec 3, 2:59 am, "Ikai Lan (Google)" 
> > > > > > 
>
> > > > > > wrote:
> > > > > >> Dance dance robot is a bit older and the API may have changed
> > > slightly (not
> > > > > >> sure, I have not done a visual check), but it's a good example of
> > > how to use
> > > > > >> JSNI with the Channel API:
>
> > > > > >>http://code.google.com/p/dance-dance-robot/
>
> > > > > >> --
> > > > > >> Ikai Lan
> > > > > >> Developer Programs Engineer, Google App Engine
> > > > > >> Blogger:http://googleappengine.blogspot.com
> > > > > >> Reddit:http://www.reddit.com/r/appengine
> > > > > >> Twitter:http://twitter.com/app_engine
>
> > > > > >> On Thu, Dec 2, 2010 at 3:50 PM, emerix  wrote:
> > > > > >> > Great release! Are there some libraries/docs for GWT and the
> > > Channel
> > > > > >> > API ?
>
> > > > > >> > On Dec 2, 10:17 pm, "Ikai Lan (Google)" 
> > > > > >> > 
> > > >
>
> > > > > >> > wrote:
> > > > > >> > > They're still rolling out:
>
> > > > > >> > >http://code.google.com/appengine/docs/java/channel/
>
> > > > > >> > > If yo

[appengine-java] Re: 1.4 eclipse plugin

2010-12-05 Thread Jaroslav Záruba 
Same error, syncing the JARs has not helped. :(
It appears to me there's still hiding one incompatible (Jasper?)
library somewhere.

I guess I just have bad luck. Every time I upgrade GAE/GWT Eclipse
plugin or SDK I end up doing clean install of Eclipse. :(

On Dec 5, 7:36 pm, Rajeev Dayal  wrote:
> Hi,
>
> If you navigate to Project Properties -> Google -> Web Application, do you
> have the option "Launch and deploy from this directory" checked? If so, when
> you switched SDKs on your project, the Google Plugin for Eclipse should have
> copied over the new libraries from the SDK over to your war/WEB-INF/lib
> directory.
>
> Have you manually copied/modified/removed any of the App Engine-related
> libraries in the war/WEB-INF/lib folder? If so, then the Google Plugin for
> Eclipse will not overwrite those changes on an SDK switch. What will happen
> is that when switching SDKs, a warning will appear in the problems view,
> indicating that there is a mismatch between the SDK jars and those in your
> war/WEB-INF/lib folder. By selecting the warning and hitting CTRL-1, you'll
> be given the option to synchronize the jars in the new SDK with the jars in
> war/WEB-INF/lib.
>
> Rajeev
>
>
>
>
>
>
>
> On Fri, Dec 3, 2010 at 9:30 PM, GoSharp Lite  wrote:
> > I have just upgraded Eclipse Galileo with AppEngine version 1.4.0.
> > There seems to be a mismatch of Tomcat versions between pre-
> > compilation and execution.
>
> > Does anyone have a solution with jsp compilation issue?
>
> > Local server shows below logs with SDK 1.4.0 -
> > HTTP ERROR 500
>
> > Problem accessing /. Reason:
> > Unable to compile class for JSP:
>
> > An error occurred at line: -1 in the generated java file
> >    [javac] D:\Profiles\LOCALS~1\Temp\Jetty_0_0_0_0__warmasbuh
> > \jsp\org\apache\jsp\GoChildWeb_jsp.java:8:
> > org.apache.jsp.GoChildWeb_jsp is not abstract and does not override
> > abstract method getDependants() in
> > org.apache.jasper.runtime.JspSourceDependent
> >    [javac] public final class GoChildWeb_jsp extends
> > org.apache.jasper.runtime.HttpJspBase
> >    [javac]              ^
>
> > An error occurred at line: -1 in the generated java file
> >    [javac] D:\Profiles\LOCALS~1\Temp\Jetty_0_0_0_0__warmasbuh
> > \jsp\org\apache\jsp\GoChildWeb_jsp.java:18: getDependants() in
> > org.apache.jsp.GoChildWeb_jsp cannot implement getDependants() in
> > org.apache.jasper.runtime.JspSourceDependent; attempting to use
> > incompatible return type
> >    [javac] found   : java.lang.Object
> >    [javac] required: java.util.List
> >    [javac]   public Object getDependants() {
> >    [javac]                 ^
>
> > An error occurred at line: -1 in the generated java file
> >    [javac] D:\Profiles\LOCALS~1\Temp\Jetty_0_0_0_0__warmasbuh
> > \jsp\org\apache\jsp\GoChildWeb_jsp.java:23: cannot find symbol
> >    [javac] symbol  : method
> > getJspApplicationContext(javax.servlet.ServletContext)
> >    [javac] location: class javax.servlet.jsp.JspFactory
> >    [javac]     _el_expressionfactory =
>
> > _jspxFactory.getJspApplicationContext(getServletConfig().getServletContext( 
> > )).getExpressionFactory();
> >    [javac]                                         ^
> >    [javac] 3 errors
>
> > On Dec 4, 6:30 am, Alex Humesky  wrote:
> > > GPE's AppEngine SDK bundle version 1.4.0 is now up. Sorry for the
> > > delay.
>
> > > On Dec 3, 11:02 am, Don Schwarz  wrote:
>
> > > > My apologies.  We plan to have it up before the end of the day today.
>
> > > > On Fri, Dec 3, 2010 at 9:26 AM, Royce Fullerton 
> > wrote:
> > > > > When will the Eclipse plugin update site be updated?
>
> > > > > The plugin is now version 1.4, but the SDK is still version 1.3.8.
>
> > > > > On Dec 3, 2:59 am, "Ikai Lan (Google)" 
> > > > > 
>
> > > > > wrote:
> > > > >> Dance dance robot is a bit older and the API may have changed
> > slightly (not
> > > > >> sure, I have not done a visual check), but it's a good example of
> > how to use
> > > > >> JSNI with the Channel API:
>
> > > > >>http://code.google.com/p/dance-dance-robot/
>
> > > > >> --
> > > > >> Ikai Lan
> > > > >> Developer Programs Engineer, Google App Engine
> > > > >> Blogger:http://googleappengine.blogspot.com
> > > > >> Reddit:http://www.reddit.com/r/appengine
> > > > >> Twitter:http://twitter.com/app_engine
>
> > > > >> On Thu, Dec 2, 2010 at 3:50 PM, emerix  wrote:
> > > > >> > Great release! Are there some libraries/docs for GWT and the
> > Channel
> > > > >> > API ?
>
> > > > >> > On Dec 2, 10:17 pm, "Ikai Lan (Google)" 
> > > > >> > 
> > >
>
> > > > >> > wrote:
> > > > >> > > They're still rolling out:
>
> > > > >> > >http://code.google.com/appengine/docs/java/channel/
>
> > > > >> > > If you see an error, wait a bit and refresh.
>
> > > > >> > > --
> > > > >> > > Ikai Lan
> > > > >> > > Developer Programs Engineer, Google App Engine
> > > > >> > > Blogger:http://googleappengine.blogspot.com
> > > > >> > > Reddit:http://www.reddit.com/r/appengine
> > > > >> > > Twitter

Re: [appengine-java] HttpServletRequest.getLocalPort() returns 0

2010-12-05 Thread Gabriele Kahlout 
http://code.google.com/p/googleappengine/issues/detail?id=4210

-- 
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] Is warm up requests enabled or disabled by default? (Documentation disagrees)

2010-12-05 Thread Maxim Veksler 
Hello Guys,

This page
http://code.google.com/appengine/docs/java/config/appconfig.html#Warming_Requests
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.yaml
."*

This page
http://code.google.com/appengine/docs/java/configyaml/appconfig_yaml.html#Warming_Requests
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.

Re: [appengine-java] Re: 1.4 eclipse plugin

2010-12-05 Thread Rajeev Dayal 
Hi,

If you navigate to Project Properties -> Google -> Web Application, do you
have the option "Launch and deploy from this directory" checked? If so, when
you switched SDKs on your project, the Google Plugin for Eclipse should have
copied over the new libraries from the SDK over to your war/WEB-INF/lib
directory.

Have you manually copied/modified/removed any of the App Engine-related
libraries in the war/WEB-INF/lib folder? If so, then the Google Plugin for
Eclipse will not overwrite those changes on an SDK switch. What will happen
is that when switching SDKs, a warning will appear in the problems view,
indicating that there is a mismatch between the SDK jars and those in your
war/WEB-INF/lib folder. By selecting the warning and hitting CTRL-1, you'll
be given the option to synchronize the jars in the new SDK with the jars in
war/WEB-INF/lib.


Rajeev

On Fri, Dec 3, 2010 at 9:30 PM, GoSharp Lite  wrote:

> I have just upgraded Eclipse Galileo with AppEngine version 1.4.0.
> There seems to be a mismatch of Tomcat versions between pre-
> compilation and execution.
>
> Does anyone have a solution with jsp compilation issue?
>
> Local server shows below logs with SDK 1.4.0 -
> HTTP ERROR 500
>
> Problem accessing /. Reason:
> Unable to compile class for JSP:
>
> An error occurred at line: -1 in the generated java file
>[javac] D:\Profiles\LOCALS~1\Temp\Jetty_0_0_0_0__warmasbuh
> \jsp\org\apache\jsp\GoChildWeb_jsp.java:8:
> org.apache.jsp.GoChildWeb_jsp is not abstract and does not override
> abstract method getDependants() in
> org.apache.jasper.runtime.JspSourceDependent
>[javac] public final class GoChildWeb_jsp extends
> org.apache.jasper.runtime.HttpJspBase
>[javac]  ^
>
>
> An error occurred at line: -1 in the generated java file
>[javac] D:\Profiles\LOCALS~1\Temp\Jetty_0_0_0_0__warmasbuh
> \jsp\org\apache\jsp\GoChildWeb_jsp.java:18: getDependants() in
> org.apache.jsp.GoChildWeb_jsp cannot implement getDependants() in
> org.apache.jasper.runtime.JspSourceDependent; attempting to use
> incompatible return type
>[javac] found   : java.lang.Object
>[javac] required: java.util.List
>[javac]   public Object getDependants() {
>[javac] ^
>
>
> An error occurred at line: -1 in the generated java file
>[javac] D:\Profiles\LOCALS~1\Temp\Jetty_0_0_0_0__warmasbuh
> \jsp\org\apache\jsp\GoChildWeb_jsp.java:23: cannot find symbol
>[javac] symbol  : method
> getJspApplicationContext(javax.servlet.ServletContext)
>[javac] location: class javax.servlet.jsp.JspFactory
>[javac] _el_expressionfactory =
>
> _jspxFactory.getJspApplicationContext(getServletConfig().getServletContext()).getExpressionFactory();
>[javac] ^
>[javac] 3 errors
>
>
>
> On Dec 4, 6:30 am, Alex Humesky  wrote:
> > GPE's AppEngine SDK bundle version 1.4.0 is now up. Sorry for the
> > delay.
> >
> > On Dec 3, 11:02 am, Don Schwarz  wrote:
> >
> > > My apologies.  We plan to have it up before the end of the day today.
> >
> > > On Fri, Dec 3, 2010 at 9:26 AM, Royce Fullerton 
> wrote:
> > > > When will the Eclipse plugin update site be updated?
> >
> > > > The plugin is now version 1.4, but the SDK is still version 1.3.8.
> >
> > > > On Dec 3, 2:59 am, "Ikai Lan (Google)" 
> > > > 
> >
> > > > wrote:
> > > >> Dance dance robot is a bit older and the API may have changed
> slightly (not
> > > >> sure, I have not done a visual check), but it's a good example of
> how to use
> > > >> JSNI with the Channel API:
> >
> > > >>http://code.google.com/p/dance-dance-robot/
> >
> > > >> --
> > > >> Ikai Lan
> > > >> Developer Programs Engineer, Google App Engine
> > > >> Blogger:http://googleappengine.blogspot.com
> > > >> Reddit:http://www.reddit.com/r/appengine
> > > >> Twitter:http://twitter.com/app_engine
> >
> > > >> On Thu, Dec 2, 2010 at 3:50 PM, emerix  wrote:
> > > >> > Great release! Are there some libraries/docs for GWT and the
> Channel
> > > >> > API ?
> >
> > > >> > On Dec 2, 10:17 pm, "Ikai Lan (Google)" 
> > > >> > 
> >
> >
> > > >> > wrote:
> > > >> > > They're still rolling out:
> >
> > > >> > >http://code.google.com/appengine/docs/java/channel/
> >
> > > >> > > If you see an error, wait a bit and refresh.
> >
> > > >> > > --
> > > >> > > Ikai Lan
> > > >> > > Developer Programs Engineer, Google App Engine
> > > >> > > Blogger:http://googleappengine.blogspot.com
> > > >> > > Reddit:http://www.reddit.com/r/appengine
> > > >> > > Twitter:http://twitter.com/app_engine
> >
> > > >> > > On Thu, Dec 2, 2010 at 1:10 PM, Ikai Lan (Google)
> > > >> > >  <
> ikai.l%2bgro...@google.com ><
> > > >> > ikai.l%2bgro...@google.com  <
> ikai.l%252bgro...@google.com >>
> >
> > > >> > > > wrote:
> > > >> > > > The docs aren't live yet. They'll be live later in the day.
> >
> > > >> > > > --
> > > >> > > > Ikai Lan
> > > >> > > > Developer Programs Engineer, Google App Engine
> > > >> > > > Blogger:http://googleappen

[appengine-java] Re: Local datastore empty after updating to SDK 1.4.0

2010-12-05 Thread Ian Marshall 
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.

On Dec 5, 1:00 pm, Fabrizio Accatino  wrote:
> Ian,
>
> I had read your previous post (2010-04-15). As you wrote, I'd also like to
> find a more "authoritatively" response. But  I haven't found it. :(
>
>   fabrizio
>
> On Sun, Dec 5, 2010 at 11:47 AM, Ian Marshall wrote:
>
> > Does this post help?
>
> >http://www.google.com/url?url=http://groups.google.com/g/f907f736/t/2...
>
> > On Dec 4, 2:40 pm, Fabrizio  wrote:
> > > I have a project with a local datastore. There was many entities in
> > > it.
>
> > > I have update the sdk from 1.3.7 to 1.4.0. Now the local datastore is
> > > empty. My app does not show data and local management tell datastore
> > > is empty (http://localhost:/_ah/admin/datastore).
>
> > > I've also tried to "revert" the local_db.bin file to my previous
> > > version from my local subversion. But it does not work.   :(
>
> > > Any idea?
>
> > > Fabrizio
>
> > --
> > 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: Checking admin priviledges using UserService in a cron/task-queue task execution

2010-12-05 Thread andrew 
Thanks Didier.

I will look into it while waiting to see if Google can respond on what
the UserService returns in this case and if it can be used.

My first thought was that it would be pretty easy for someone to
construct a request with those headers present and valid values
(especially for the "default" queue), especially to pass the "generic"
security filter I'd like to write.

regards

-- 
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

2010-12-05 Thread Sudhir 
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  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  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 org.apache.jasper.compiler.Compiler.compile(Compiler.java:314)
> >         at
> > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:
> > 592)
> >         at
> > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:
> > 317)
> >         at
> > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:
> > 313)
> >         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
> >         at 
> > com.google.appengine.to

Re: [appengine-java] Re: Local datastore empty after updating to SDK 1.4.0

2010-12-05 Thread Fabrizio Accatino 
Ian,

I had read your previous post (2010-04-15). As you wrote, I'd also like to
find a more "authoritatively" response. But  I haven't found it. :(

  fabrizio

On Sun, Dec 5, 2010 at 11:47 AM, Ian Marshall wrote:

> Does this post help?
>
>
> http://www.google.com/url?url=http://groups.google.com/g/f907f736/t/27097b9831aff32a/d/c16b898dcaad10ef%3Fq%3D%23c16b898dcaad10ef&ei=aG37TNXvFoHA_Abn1qTaAg&sa=t&ct=res&cd=10&source=groups&usg=AFQjCNGa_5Wk3KqMn7czeKwR0zocC07gOw
>
> On Dec 4, 2:40 pm, Fabrizio  wrote:
> > I have a project with a local datastore. There was many entities in
> > it.
> >
> > I have update the sdk from 1.3.7 to 1.4.0. Now the local datastore is
> > empty. My app does not show data and local management tell datastore
> > is empty (http://localhost:/_ah/admin/datastore).
> >
> > I've also tried to "revert" the local_db.bin file to my previous
> > version from my local subversion. But it does not work.   :(
> >
> > Any idea?
> >
> > Fabrizio
>
> --
> 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] jsessionid not present anymore

2010-12-05 Thread Ioan 
Thanks for the update. In the meantime I've enabled the cookies in
appengine-web.xml and now are working as expected.
cheers
Ioan

-- 
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

2010-12-05 Thread Ian Marshall 
I am encouraged by the contributions from Ikai and Max.

I forgot to mention in my earlier post one reason I elected to use JDO
as my interface to the datastore: to maintain the capability to port
my application to another hosting service without too much work.

That being said, I have no intention currently of porting away from
GAE/J. Despite various problems, I think that this is an excellent
offering which improves continuously. A big thank you to everyone who
is responsible!


On Dec 5, 8:41 am, George  Moschovitis 
wrote:
> On Dec 4, 6:56 am, John Howe  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] Re: Local datastore empty after updating to SDK 1.4.0

2010-12-05 Thread Ian Marshall 
Does this post help?

http://www.google.com/url?url=http://groups.google.com/g/f907f736/t/27097b9831aff32a/d/c16b898dcaad10ef%3Fq%3D%23c16b898dcaad10ef&ei=aG37TNXvFoHA_Abn1qTaAg&sa=t&ct=res&cd=10&source=groups&usg=AFQjCNGa_5Wk3KqMn7czeKwR0zocC07gOw

On Dec 4, 2:40 pm, Fabrizio  wrote:
> I have a project with a local datastore. There was many entities in
> it.
>
> I have update the sdk from 1.3.7 to 1.4.0. Now the local datastore is
> empty. My app does not show data and local management tell datastore
> is empty (http://localhost:/_ah/admin/datastore).
>
> I've also tried to "revert" the local_db.bin file to my previous
> version from my local subversion. But it does not work.   :(
>
> Any idea?
>
> Fabrizio

-- 
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

2010-12-05 Thread George Moschovitis 

On Dec 4, 6:56 am, John Howe  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.