Hi,
Is it possible to save my password, so I don't have to type it
everytime I click deploy on GAE Eclipse plugin?
Many thanks
Don
--
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
Hello.
I'm trying to make changes to my model class. I have a class called
Product that has a field category, which is a String.
public class Product {
...
private String category;
...
}
Now, I've decided that a Product can have different categories. I made
the field a List instead
Any updates on my previous question ?
Thank you!!
VSS
On Dec 4, 4:44 pm, VSS shyamsunder...@gmail.com wrote:
We are creating an Active Directory Kind of an application on App
Engine. What I want to know is there a way to store data securely so
that I can sell this application as a service to
I always get this exception when my app does its first datastore query. I
think it's causing me other problems. Is there anything I can do to fix this?
com.google.appengine.repackaged.com.google.common.base.FinalizableReferenceQueue
init: Failed to start reference finalizer thread. Reference
On Sat, Dec 5, 2009 at 9:29 AM, Toby tobias.ro...@sunnymail.mobi wrote:
I know that they are updated at least once a day. In my case the data
volume has not changed for quite some time. And the discrepancy is
really huge. I mean 50MB to 500MB. So maybe my datastore contains
stuff that does not
The exception is harmless. Add this to your logging.properties file to hide
it:
com.google.appengine.repackaged.com.google.common.base.FinalizableReferenceQueue.level=WARNING
There was previous discussion of this (search
for FinalizableReferenceQueue).
Vince
On Sat, Dec 5, 2009 at 1:00 PM,
Ah, ok; thanks Vince.
Vince Bonfanti wrote:
The exception is harmless. Add this to your logging.properties file to
hide it:
com.google.appengine.repackaged.com.google.common.base.FinalizableReferenceQueue.level=WARNING
There was previous discussion of this (search
for
On Sat, Dec 5, 2009 at 10:05 AM, Eric Rannaud eric.rann...@gmail.com wrote:
They also talked about an article they will publish soon that gives
enough details on how indexes are built that you can at least predict
the size of your indexes.
There it is:
Is it possible to use the GAE Eclipse plugin if you're using Maven? Maven uses
a different directory structure so I'm guessing that's why the GAE plugin
doesn't recognize the project as a GAE web app.
--
You received this message because you are subscribed to the Google Groups
Google App
What do you mean by no log? I often need to change the console web page's
filter level to debug to see some error messages.
Wong wrote:
Points to add
I'm using Spring 3.0.0 RC1
!-- Resolves logical view names returned by Controllers to Tiles; a
view
name to resolve is
Hi Max,
To be able cover my code with unit tests, I created a mock class for
the App Engine environment (http://github.com/DomDerrien/two-tiers-
utils/blob/master/src/Java/com/google/apphosting/api/
MockAppEngineEnvironment.java). As reported in my recent blog post
Max,
I've an issue probably related to my tests that recreate an
environement at each step (as unit tests usually does ;). The issue is
related to the re-creation of a Queue with the same name (the default
one).
Here is the exception with part of the stack trace:
2009/12/06 14:12 Dom Derrien dominique.derr...@gmail.com:
Max,
I've an issue probably related to my tests that recreate an
environement at each step (as unit tests usually does ;). The issue is
related to the re-creation of a Queue with the same name (the default
one).
Here is the exception
I'm sorry for you.
I have sent a strange mail because I did a wrong operation.
--
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
FYI, here is access to the mock queue I inject into the code during
the unit tests. In addition to working around the limitation with the
QueueFactory (because my Queue provider in test mode returns new
MockQueue(); instead of QueueFactory.getDefaultQueue();, the mock
provides accessors that
15 matches
Mail list logo
