no one has any ideas on this?
I'd really like to know if this is just a bug that will be resolved
(in which case I'll continue to use this data model) or if there is a
flaw in my data model/JDO usage.
thanks!
-bryce
On Nov 30, 1:21 am, bcottam wrote:
> I'm trying to save some data in my app,
Max, have you had a chance to try this out? I'm not trying to push or
anything, just wanted to make sure my last message didn't get
overlooked. I've noticed this error sort of... randomly popping up in
places where it preivously hasn't as of late. If i'm missing
something in my configuration, I'
Hi Bryce,
Thanks for posting your model objects. I'm not able to reproduce the
exception you're reporting, but then again I'm just guessing at how you're
populating your objects and persisting them. Here's what I did:
Bundle b = new Bundle();
RatePlan rp = new RatePlan();
rp.setPric
thanks so much for checking into this Max.
The data that I'm saving is user generated, so there's not a set
script for it. Conceptually what I'm doing is this:
Bundle bundle = new Bundle();
bundle.setName("My Bundle");
bundle.setDe
I don't see a call to tx.begin() in the code below. Is that a typo or is it
actually missing?
On Tue, Dec 1, 2009 at 12:29 PM, bryce cottam wrote:
> thanks so much for checking into this Max.
>
> The data that I'm saving is user generated, so there's not a set
> script for it. Conceptually wha
that is both a type-o and it was missing :) It was missing from my
test code, but it was present in my "real" code. So, after putting
the tx.begin() in the test code, I get the exact same behavior as the
"real" code (i.e. nothing gets written to the datastore and I get the
exception. Sorry abou
Now I'm starting to suspect something funny going on with your config. I
received a TransactionNotActiveException when I tried to run your code
without starting the txn, and the fact that you didn't receive that
exception doesn't make any sense to me. I can't explain why you see the
exception and
yeah, I didn't see a TransactionNotActiveException.
here is my jdoconfig.xml:
I think the only thing I changed was putting in this line:
which may explain why I don't get the TransactionNotActiveException.
So, for this unit test/serv
Okay, sorry for the delay, I haven't been able to focus on this for a few days.
here is the full (including the jar libararies in
case there is an issue with them).
http://www.resmarksystems.com/code/JdoTest.zip
It's a very simple Servlet, by hitting the url hostname/jdotest you
should execute t
Hi Bryce,
I started digging into you issue and quickly bumped into the "Multiple
relationships of the same type" bug for which I posted the workaround. Then
I got bogged down with unrelated stuff. I have definite plans to get back
to your example today. Thanks for being patient, and sorry this
No worries Max, I'm using 1.2.6 right now, so the "multiple instance" bug
isn't an issue right now. Whenever you get to it is fine. As always I
appreciate your input.
Thanks
-bryce
On Dec 8, 2009 10:14 AM, "Max Ross (Google)"
>
wrote:
Hi Bryce,
I started digging into you issue and quickly bumpe
Ok I think I know what's going on. First here's a stripped down version of
your object model with the bare minimum needed to reproduce the exception:
@PersistenceCapable(identityType = IdentityType.APPLICATION)
public class RatePlan {
@PrimaryKey
@Persistent(valueStrategy = IdGenerato
Filed http://code.google.com/p/datanucleus-appengine/issues/detail?id=170
On Tue, Dec 8, 2009 at 6:18 PM, Max Ross (Google)
> wrote:
> Ok I think I know what's going on. First here's a stripped down version of
> your object model with the bare minimum needed to reproduce the exception:
>
> @P
Thanks for filing that Max.
I'm kind of interested in your findings because there is another place
where I'm doing about the same thing (i.e. making a RatePlan instance
a direct child of an Entity other than Activity) and it works fine in
that case most of the time. Sometimes it gives me the "oid
I don't see a class that is owned by more than one entity in your latest
example. What exactly should I be looking at?
Your understanding of the BigTable layout is correct, but you're bumping
into a limitation of how we've mapped JDO on to that layout. The low-level
api knows nothing about your
On the ActivityReservation model object, there is an instance of
RatePlan (which is also a child object of Activity).
So, here's a thought, I will try it out later, but I thought I'd ask
right now about it:
how about having subclasses of RatePlan that live on different parent
objects? since RateP
16 matches
Mail list logo