I use Play framework with GAE module, it works quite nice and performance is
ok.
Personally I don't have good experience with Spring roo
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Hi all,
I am also not very old in both Java and AppEngine. I got the same error when
testing some basic app, and it seems the error was coming from an exception
whose source Eclipse could not locate (hence suggesting for source attachment).
When I uploaded the application to Appengine, it run
Hey
I'm using JDO and need to update two entities both of which reside in
their own entity group. As I cannot use a transaction, I'd like to
determine how others achieve this. It is imperative that both entities
are updated or none at all.
Thanks
--
You received this message because you are
vraptor is fast, easy and RESTful ready
better startup time with guice or pico instead of spring
be sure to disable annotation scanning and setup your annotated components
manually
http://vraptor.caelum.com.br/en
On Sun, Jul 10, 2011 at 3:38 AM, Max thebb...@gmail.com wrote:
I use Play
Hi,
Have a look at this to understand the issues:
http://blog.notdot.net/2009/9/Distributed-Transactions-on-App-Engine
regards
didier
On Jul 10, 11:09 pm, mscwd01 mscw...@gmail.com wrote:
Hey
I'm using JDO and need to update two entities both of which reside in
their own entity group. As I
You can use STRONG consistency on HR and if you get by key then that should
work with what you describe. There was just a discussion on this and you can
see a related post by Ikai which may also help you from a reply of his to
this other discussion:
I get the follwing compile error -- com.google.appengine.api.datastore.Key
can not be found in source packages. Check the inheritance chain from your
module; it may not be inheriting a required module or a module may not be
adding its source path entries properly -- with the below code snippet.
This answer to this -- in the Eclispe IDE -- is to uncheck build
automatically and then hit build all, and then it can see it. Strange,
but true.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
Hi all,
Sorry for what I consider a very simple question.
I want to check something I have done.
I wanted to do some test driven development for a specific part of my
project.
In order to run the tests I need to import the google libs (I am
running on MacOS)
I have put this at the top of my
The example you describe will be strongly consistant in the high
replication datastore. Take a look at the consistency section of the
table on this page comparing master/slave with high replication:
http://code.google.com/appengine/docs/python/datastore/hr/
You'll see there that gets, puts, and
Hi Kyle,
You should read the link I provided with Ikai's discussion. Gets by key with
EVENTUAL consistency on HR can go to a replica datastore that may not have
the latest info. Also, see the discussion we just had where this was
discussed. Subject was ReadPolicy.Consistency.EVENTUAL under HR The
Hi Joops,
You might want to have a look a the docs on Local Unit Testing for Python
[1] and especially on setting up a testing framework [2].
Cheers,
Tobias
[1] http://code.google.com/appengine/docs/python/tools/localunittesting.html
[2]
On Sun, Jul 10, 2011 at 5:17 PM, bejayoharen wrote:
A great project would be one that worked from a
third party site (non-cloud hosting would suffice), checked your site
periodically, and contacted you (eg sent you a text message using
twillio) if there was any trouble.
There are only
Ok, so, gets can use eventual consistency, but that's not the default.
Is that correct?
If so, I agree with you that that sentence should be changed.
Remember, if you do a get(), put(), or a transaction, you will always
see the most recently written data.
Thank you, this is helpful, especially the links.
I am using JPA and it's not clear to me what constitutes a get --
does calling EntityManager.find() always constitute a get or only
when the @Id of my class is the same as the underlying datastore key?
Furthermore, the docs cited by Kyle indicate
On Sun, Jul 10, 2011 at 4:26 PM, Barry Hunter barrybhun...@gmail.com wrote:
On Sun, Jul 10, 2011 at 5:17 PM, bejayoharen wrote:
A great project would be one that worked from a
third party site (non-cloud hosting would suffice), checked your site
periodically, and contacted you (eg sent
That's correct. The default is strong consistency.
On Sun, Jul 10, 2011 at 5:18 PM, Kyle Mulka kyle.mu...@gmail.com wrote:
Ok, so, gets can use eventual consistency, but that's not the default.
Is that correct?
If so, I agree with you that that sentence should be changed.
Remember, if you
I don't use JPA, but the way I understand it is that a get is by key which
can also be a batch get by key. Whereas a query, queries for the entity keys
using an index and then gets the entities by key. So, the way I understand
it is below, but this is just my understanding so I could be wrong:
There is a difference between a query (getting entities by indexed
properties) and get()/get_by_id() which get a specified object. So if
client A sends the key/id to client B, you'll be fine - client B will
get the latest version of the entity.
Also one other small point - as long as you are
As I understand it, you can't run a non-ancestor query in a
transaction. Transactions are only supported within a single entity
group.
--
Kyle Mulka
Co-Founder, DealSavant
http://www.dealsavant.com
On Jul 10, 8:36 pm, bejayoharen beayoha...@gmail.com wrote:
Thank you, this is helpful,
Hi Mark,
That's not the case - you can map multiple domains to the same app, either
by setting them up as separate Google Apps domains, or by adding them as
aliases for an existing domain. Your app can then use the Host header to
distingush between domains and serve different content to them.
Hey Stephen,
Yeah that last sentence looks like an incorrect, or at least
seriously misleading, statement to me; there is a chance that an
eventually consistent get will not see the most recent data (it also
will not initiate a catch-up cycle if it finds stale data). Hopefully
Ikai will get a
On Fri, Jul 8, 2011 at 15:30, Tom Phillips tphill0...@gmail.com wrote:
That aliasing via tools sounds pretty good to me. I was worried about
the timing of aliasing my old app to my new one if it had to be done
via raising a billing issue. Having the ability to time it ourselves
is much better.
Hi Bejayoharen,
Great thanks for the feedback.
As I said this is just several hours work so sorry for the UI. I agree it's
not quite comprehensive.
You can login with your Google Account by clicking top-right link Log in
with your Google Account to manage your warmers
You will be able to
hi Jeff,
AFAIK, lots of GAE developers are using cron job to *warm up*, including me.
You can search in this group, many ppl are doing this.
Also, if we want something more than a periodic ping, like those use cases
you mentioned, then we probably don't want all these logic stay with in our
25 matches
Mail list logo
