Hi Chuck (and others who might see what this problem is),
On 27/03/2007, at 3:09 AM, Chuck Hill wrote:
Hi Ian,
On Mar 25, 2007, at 9:43 PM, Ian Joyner wrote:
I'm getting a crash in the following code:
public boolean is_unassigned () {
// editingContext ().refaultObject
On 26.03.2007, at 11:16, Chuck Hill wrote:
to avoid null pointer exceptions all over the place (and/or to
avoid having to write lots of code to check that the relationships
were non-null). I took the following steps:
You should never need to worry about that. If the to-many
relationshi
to avoid null pointer exceptions all over the place (and/or to
avoid having to write lots of code to check that the relationships
were non-null). I took the following steps:
You should never need to worry about that. If the to-many
relationships are null, you have overridden awakeFromIns
Steven,
If you were getting null pointers on your to-many relationships, you
are most likely overriding awakeFromInsertion without calling super
on that entity.
Ken
On Mar 26, 2007, at 1:09 PM, Steven Mark McCraw wrote:
Hi Chuck,
As it turns out, I was abusing EOF (although not in a way
On Mar 26, 2007, at 10:09 AM, Steven Mark McCraw wrote:
Hi Chuck,
As it turns out, I was abusing EOF
Ah ha! You will grow hair your palms if you keep doing that! :-P
(although not in a way that has ever been documented by Apple, to
my knowledge). In my EOModeler generation template, I
Hi Chuck,
As it turns out, I was abusing EOF (although not in a way that has
ever been documented by Apple, to my knowledge). In my EOModeler
generation template, I was initializing all of the the to-many
relationships to empty (but non-null) arrays in the generated
constructor to avoid
Hi Ian,
On Mar 25, 2007, at 9:43 PM, Ian Joyner wrote:
I'm getting a crash in the following code:
public boolean is_unassigned () {
// editingContext ().refaultObject (this);
log.info ("is_unassigned " + this.groups ());
boolean result = tr
There is no need for a workaround. Somehow, somewhere, you are
abusing EOF. Even if you work around this, EOF will just lie in
wait and take its revenge elsewhere. I used nested editing
contexts. I know lots of others do too. They work just fine if
you play nice with EOF.
Get the probl
On Mar 24, 2007, at 9:37 PM, Steven Mark McCraw wrote:
Hi Chuck,
That's was a good thought, and actually I was not locking the child
EC. It still strikes me as bizarre that the responsibility of
locking and unlocking the editing context is left up to the
programmer, but that's just me g
On Mar 23, 2007, at 12:53 PM, Ted Archibald wrote:
Hi, I'm developing a series of internal applications that focus on
bookkeeping and accounting.
Using webobjects how would one one design a simple app for batch
entries similar to what one would do in Excel? These entries could
be anywhe
10 matches
Mail list logo
