I don’t see Person or EventBook in this model, but it’s mentioned in your code.
Seems like you’re leaving out something important.
On Feb 11, 2015, at 2:15 PM, Theodore Petrosky wrote:
> what I am trying to accomplish is assign to the entity Event all the Books
> that are assigned to the show.
On 2015-02-11, 1:15 PM, "Theodore Petrosky" wrote:
Ok so Chuck’s concern about using the willInsert method is that the EO is not
in an EC. what I am trying to accomplish is assign to the entity Event all the
Books that are assigned to the show.
soEvent toOne Show toMany Book
When I creat
Ok so Chuck’s concern about using the willInsert method is that the EO is not
in an EC. what I am trying to accomplish is assign to the entity Event all the
Books that are assigned to the show.
soEvent toOne Show toMany Book
When I create a new Event, I assign the Show and a Date.
would t
That is a different ExceptionInInitializerError. This one has a root cause of:
17:32:14,681 ERROR [stderr] (http-ecvomzsdd01.vzbi.com/146.1.200.130:8444-1)
Caused by: java.lang.NullPointerException
17:32:14,682 ERROR [stderr] (http-ecvomzsdd01.vzbi.com/146.1.200.130:8444-1)
at
com.webobject
lol, that’s Canadian for “Are you insane?!” :D
Srsly, ec.saveChanges() in init() means any time you create this EO, the whole
ec saves right then. If you create 20 EOs that’s 20 round trips to the DB.
EO: You were busy in the middle of changes that won’t validate? No problem, let
me call saveC
Sill confused.
I've gone through and identified and fixed cases of the static initializers as
described below. I've tried a number of different options to resolve this but
it seems that I am still getting the java.lang.ExceptionInInitializerError.
From what I can tell it is happening when I t
except maybe this is too early. this line is important:
EOQualifier booksAssignedToShowQualifier = Book.SHOW.eq(this.show()); //all the
books for this show
it looks like there is no Show assigned yet. so it looks like willInsert()
happens a little later (at least after the show is assigned).
Init() is correct though I am still not keen on calling saveChanges() in that
method.
On 2015-02-11, 9:21 AM, "Theodore Petrosky" wrote:
Actually, I was just thinking of that as I am setting a couple of values
(booleans) in the init method, and why not assign the relations there also.
I’ll try
Actually, I was just thinking of that as I am setting a couple of values
(booleans) in the init method, and why not assign the relations there also.
I’ll try to set it up there and see what happens.
what do you think Chuck, does this sound OK?
On Feb 11, 2015, at 11:46 AM, Timothy Worman wrot
Isn’t init() the Wonder Preferred Method ™? :-)
Tim Worman
UCLA GSE&IS
> On Feb 11, 2015, at 8:38 AM, Chuck Hill wrote:
>
> On 2015-02-11, 8:26 AM, "Theodore Petrosky" wrote:
>
> so are you suggesting that awakeFromInsertion is the correct place to assign
> these entities?
>
> That is a mor
On 2015-02-11, 8:26 AM, "Theodore Petrosky" wrote:
so are you suggesting that awakeFromInsertion is the correct place to assign
these entities?
That is a more correct place.
I actually assumed that there was an editingContext at this point. And you know
what they say about assuming.
My inter
so are you suggesting that awakeFromInsertion is the correct place to assign
these entities? I actually assumed that there was an editingContext at this
point. And you know what they say about assuming.
If I put my code in awake from insertion, I then call
“editingContext().saveChanges” at the
Doing anything to an EO when it is not in an EC (e.g. Before it is inserted)
seems like a Very Bad Idea. EOF is not expecting this.
Chuck
On 2015-02-11, 8:17 AM, "Theodore Petrosky" wrote:
but (and I will test this assumption) isn’t awakeFromInsertion called AFTER the
insertion? and willInse
but (and I will test this assumption) isn’t awakeFromInsertion called AFTER the
insertion? and willInsert Before?
I need to assign these relationships BEFORE the main EO is inserted. So in my
case, I want to relate all the BOOKS that belong to the Show, then assign the
PrimaryPlayer to the book
I see. But I think I will keep the solution renaming the Ship entity because if
I go with setting rules like this, there would be so many of it (since it's
happening in a lot of different EditPage).
Anthonin
On Tue, 2015-02-10 at 22:19 +, Mark Wardle wrote:
You can force the entit
15 matches
Mail list logo