You rock. I'll give it a try. Thanks!
On Sep 24, 3:25 pm, "Alejandro D. Garin" wrote:
> Hi objectuser,
>
> yes, currently I have a project to share this kind of code and an online
> demo with source code.
>
> Advice class (RetryAdvice.java): (I have an advice for cache too - see
> CacheAdvice
On Sep 23, 11:40 am, dflorey wrote:
> I've just refactored my app to use Low-Level API instead of JDO and
> it's much cleaner, works more reliable etc.
> If you are not really forced to use JDO/JPA I'd strongly recommend to
> use the very simple, elegant and clean Low-Level API.
> BigTable simp
Hi objectuser,
yes, currently I have a project to share this kind of code and an online
demo with source code.
Advice class (RetryAdvice.java): (I have an advice for cache too - see
CacheAdvice.java)
http://code.google.com/p/puntosoft/source/browse/trunk/#trunk/src/ar/com/puntosoft/shared/server
Alejandro, is this code you can share? I'd much appreciate it if so!
On Sep 24, 12:08 pm, "Alejandro D. Garin" wrote:
> I'm using Spring with AOP, I have created an AOP advice to retry some
> datastore operations. With this approach I don't have any retry related code
> in my DAO or Service.
--
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 stopper
> - When using JDO it has not been obvious when stuff gets save to the
> datastore. When do I have to call makePersistent(...), when is it done
> explicitly
If an object is detached then you call makePersistent. If an object is
not persistent (i.e transient) then you call makePersistent. If an
ob
Hi, my experience inline ...
On Thu, Sep 24, 2009 at 11:10 AM, dflorey wrote:
>
> - Each time I save a persistent class the enhancer runs
>
In my case I'm not using the google plugin, just working with ant. I ran the
enhance when I considere apropiate.
> - Sometimes the app gets deployed with
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
-1
I have used JDO in my application (ok... not a big one, 9 domain classes, 6
DAO classes and 3 services) and I'm happy using JDO.
On Wed, Sep 23, 2009 at 6:40 AM, dflorey wrote:
>
> I've just refactored my app to use Low-Level API instead of JDO and
> it's much cleaner, works more reliable etc
The best example I could find was:
// Get a handle on the datastore itself
DatastoreService datastore =
DatastoreServiceFactory.getDatastoreService();
// Lookup data by known key name
Entity userEntity = datastore.get(KeyFactory.createKey("UserInfo",
email));
// Or perform a query
Query q
+1, I agree with this approach.
I like the great flexibility and control that the low-level API gives
me.
I would like documentation about low-level API programming.The API is
very simple but I have some doubts.
For example, It is not necessary to close the DatastoreService after
using? It's ve
imho, the low level api is quite simple and straightforward. The relevant
docs for Python is useful to me.
there is nothing wrong with JPA/JDO. DAO + Low Level API implementation
without an additional JDO layer works for me.
On Thu, Sep 24, 2009 at 5:23 AM, Marcel Overdijk
wrote:
>
> I think th
@Diana
Currently there is only "real" docs for JDO.
I think same documentation should be available for JPA and low-level
API.
Concentrating on practical exmaples.
On Sep 24, 7:09 am, Diana Cruise wrote:
> Could you supply some briefs on your findings? This is exactly the
> type of feedback we
Could you supply some briefs on your findings? This is exactly the
type of feedback we need in this forum to help us who are starting new
projects to best decide on what APIs and designs to use.
For example, if you could summarize your handling of this simple
relation that is in ALL apps: Entit
I think the docs about low level api is rather limited. Some examples
would be nice.
On Sep 23, 4:33 pm, Clay Lenhart wrote:
> +1
>
> We're having a similar discussion here:
>
> http://groups.google.com/group/google-appengine-java/browse_thread/th...
>
> Andy,
> My view is that there is no produ
+1
We're having a similar discussion here:
http://groups.google.com/group/google-appengine-java/browse_thread/thread/e406e4f77548f803?hl=en
Andy,
My view is that there is no productivity difference between the two.
It might be good to show us what is difficult to do in the datastore
but easy i
> BigTable simply is not a relational db, so it is highly misleading to
> fake a relational wrapper and to me it caused lots of pain.
Apart from the fact that JDO is not a "relational wrapper". The API
and metadata are object-based; only a subset of metadata is specific
to "mapped" datastores and
+1 Definitely.
On Wed, Sep 23, 2009 at 10:53 AM, Mingfai wrote:
>
>
> On Wed, Sep 23, 2009 at 5:40 PM, dflorey wrote:
>
>>
>> I've just refactored my app to use Low-Level API instead of JDO and
>> it's much cleaner, works more reliable etc.
>> If you are not really forced to use JDO/JPA I'd str
On Wed, Sep 23, 2009 at 5:40 PM, dflorey wrote:
>
> I've just refactored my app to use Low-Level API instead of JDO and
> it's much cleaner, works more reliable etc.
> If you are not really forced to use JDO/JPA I'd strongly recommend to
> use the very simple, elegant and clean Low-Level API.
> B
19 matches
Mail list logo
