Hi,
This is very probably a question related to Objectfify that is a
package independent, i.e 3rd party, of App Engine. You should ask it
there http://groups.google.com/group/objectify-appengine.
Question though: do you have a no-arg constructor in your class source
code ? It's required.
Hi,
The cause of your issue is defined by the line Caused by:
javax.jdo.JDOException: Error creating the MetaDataManager for API
JDO
When you start googling this, you find quite a lot of issues related
to JDO implementation itself: maybe you face one of those bugs.
JDO in GAE is based on
Hi,
My understaning of Datastore based on Google BigTables is that you
can't share objects in 2 different apps (i.e using different id)
because the app id is part of the key of the entity. BigTable,
Datastore and GAD enforce a strong sandboxing based on this id.
The app id in the key is
Hi,
Is you Summary.html properly defined as a static file ? See how-to in
http://code.google.com/appengine/docs/java/config/appconfig.html#Static_Files_and_Resource_Files.
If not defined directly (or via a containing directory), GAE won't be
able to serve it to your application. Hence the 404.
Hello Didier
thank you for your reply, I will ask the question in your mentioned group.
I do have a non-arg constructor, yes.
Greetz Ueli
--
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
Let's suppose I need to check by a key if the specified entity exists
in the datastore. What is the most proper way to achieve that?I have
the next ways:
1) datastoreservice.get(key).
2) execute keys-only query with the __key__ property: new
Query(Kind).addFilter(Entity.KEY_RESERVED_PROPERTY,
Hi,
You're right about 2): more efficient because only key is accessed: i/
o limited to index rather than index + table when you fetch the entire
entity. So more disk i/o and more bytes to transfer between the
datastore server and the server of your jvm.
About 3): 2 important points come to
You're right about 2): more efficient because only key is accessed: i/
o limited to index rather than index + table when you fetch the entire
entity. So more disk i/o and more bytes to transfer between the
datastore server and the server of your jvm.
OK
About 3): 2 important points come to
I am now stepping my first steps in Google App Engine world I have
Arabic language RTL support as a MUST requirements? Is there a
sample code that covers this? Pls help.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to
Hi!
I'm new to GAE and had quite a lot of issues that I solved, but stuck with
this one.
The app deploys/runs fine locally, but fails to run on the server.
ERROR org.springframework.web.context.ContextLoader - Context initialization
failed
Hi,
The difference is: in 3) you give the key of the ancestor and the ds
will return you the keys of the entities having this ancestor
(potentially more than 1 one) and in 2) you give the key of the entity
that you want to check itself.
in 2) you can get the key from somewhere without having to
Hi,
Some interesting how-to post in App Engine for Python forum:
http://groups.google.com/group/google-appengine/browse_thread/thread/4dd9e2d2b7213311.
You can probably easily adapt that to the Java context.
With its UTF encoding, Java can support all alphabets. Isn't your
question more a
You can use the Datastore Admin tool available to Python apps that came with
App Engine 1.3.8 to delete data more easily:
http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-includes-new.html
(under Delete all (or a part) of your application’s data)
As it says in the blog post you
I've got your idea.
The '2)' way is more flexible, because using '3)' we should guarantee
that the key is complete and the key is not an ancestor for other
entities(extra constraints for the app).
So now I'm agreed with you that '2)' way is a choice.
Thanks, very much!
--
You received this
Hello everyone.
I've an issue : I can't update a pojo object.
I have two classes : A user and a location.
A user HAS A location.
My servlet do this :
1) create a user without a location, make it persist
2) retrieve a user, set the location (for the first time), make it persist
3) retrieve a
Upon further investigation, it seems that none of the sandbox restrictions
are applied in local development mode. I can even create threads in my
servlets when running them locally. Is that normal?
I tried it on two separate machines, one running Windows, the other one
running Linux, using the
Hi, I'm trying to write a sample app with spring and JDO.
From what I've read, I've written the following config
bean id=springpmf
class=org.springframework.orm.jdo.LocalPersistenceManagerFactoryBean
property name=persistenceManagerFactoryName value=keepeye /
/bean
I have to correct myself on the HelloWorld-Project. It does throw an
exception as expected, I think I had some mistake in my test case the first
time I tried. However, I think i located the problem now:
The sandbox restrictions don't seem to apply while Guice initializes itself
and any
Upon deeper consideration, whether or not Monotonic currently could
produce dups depends on the exact behavior of:
MemcacheService.increment(java.lang.Object key, long delta,
java.lang.Long initialValue)
Unfortunately the documentation is ambiguous about what the return
value will be when
Ok, upon further further reflection, MG is right there is an
opportunity for failure, even if MemcacheService.increment() behaves
as expected. Another description of the problem, with indentation to
distinguish the two threads:
Initial state, last value in db (and memcache) is 100
STARTING SAVE
http://www.youtube.com/watch?v=S_u7CkU_NnI
--
Guit: Elegant, beautiful, modular and *production ready* gwt applications.
http://code.google.com/p/guit/
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send
I've got http://www.stripesframework.org/
cold starting in under 2 secs
with http sessions enabled
On Dec 29, 9:08 am, Sree sreeju...@gmail.com wrote:
Hello,
I am new to Java and App Engine, and coming from ASP.NET C# and
Windows Azure world. I am looking for a lightweight best performing
Useful for tests when developing XSLT:
http://xslttest.appspot.com/
Developed with Java, GWT and Google Plugin for Eclipse. Hosted in GAE.
Cheers
--
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
For the Groovy inclined, I've been having a lot of fun learning Gaelyk:
http://gaelyk.appspot.com/
--
biz: http://www.linkedin.com/in/vincentstoessel/
personal: http://www.xaymaca-studios.com/
On Thu, Dec 30, 2010 at 5:56 AM, Davi Nogueira davis...@gmail.com wrote:
I like, VRaptor,
Your question, although not the answer that worked, got me to thinking
about whether the html file itself was properly defined, because
before I used OpenOffice to create the html document and this time I
used Google Docs to create the html document, and that was the
problem. For whatever very
looks cool
On Jan 2, 10:23 pm, XSLT Master xslt@gmail.com wrote:
Useful for tests when developing XSLT:
http://xslttest.appspot.com/
Developed with Java, GWT and Google Plugin for Eclipse. Hosted in GAE.
Cheers
--
You received this message because you are subscribed to the Google
+1 on Stripes. Extremely easy to setup and use - very powerfull and
performs quite well on GAE as its basically just a somewhat simple
filter/servlet and JSP with a stripes taglib though still, as I said,
powerfull.
I had to make a few adjustments to get it to serve @UrlBinding(/)
for example and
Stripes; easy, powerful, and flexible.
On 2010-12-29 11:02, Ikai Lan (Google) wrote:
Um ... those are like the opposite of lightweight.
Here are some I like:
Play Framework: probably the most underrated Java framework I've ever see
http://www.playframework.org/
Slim3: built for App Engine.
Hi all,
I want to ask about error message diplayed on my application :
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.
this error message
29 matches
Mail list logo
