I added one of the inverse relationships back in, and using ERXEC to
create the new editing context I do NOT get the error.
Just to make sure everything else was the same, I changed back to
using "new EOEditingContext" to create the editing context, and the
error returns. So, whatever is c
Yep, that's what I did, as well as removing the offending "inverse"
relationships. I changed to the ERXEC.newEditingContext originally
to get rid of the "you don't have a delegate" error. What I didn't
try was adding the "inverse" relationships back in while using ERXEC
to create the new
Yep, that's what I did, as well as removing the offending "inverse"
relationships. I changed to the ERXEC.newEditingContext originally to get rid
of the "you don't have a delegate" error. What I didn't try was adding the
"inverse" relationships back in while using ERXEC to create the new editi
Actually, I was using:
EOObjectStoreCoordinator parentObjectStore = new
EOObjectStoreCoordinator();
EOEditingContext threadEditingContext = new
EOEditingContext(parentObjectStore);
You're using Wonder, right? I just setup a test case of this and it
worked fine, except that you
On 06.08.2008, at 03:19, Jeff Schmitz wrote:
and with that, I still was getting the error until I removed a
couple of the inverse relationships. Note that I didn't have to
remove them all of them, just a couple of them. Not sure what made
those cause trouble.
Is it possible that EOF is
Actually, I was using:
EOObjectStoreCoordinator parentObjectStore = new
EOObjectStoreCoordinator();
EOEditingContext threadEditingContext = new
EOEditingContext(parentObjectStore);
and with that, I still was getting the error until I removed a
couple of the inverse relat
On Aug 5, 2008, at 9:05 PM, Jeff Schmitz wrote:
I fixed the problem by removing a couple of inverse relationships,
and I also needed to use ERXEC.newEditingContext(parentObjectStore)
to create my new editing context (instead of just new
EOEditingContext), and now it works. Since I wasn't
I fixed the problem by removing a couple of inverse relationships, and
I also needed to use ERXEC.newEditingContext(parentObjectStore) to
create my new editing context (instead of just new EOEditingContext),
and now it works. Since I wasn't using these inverse relationships
anyway it's no
OK, I took the thread completely out of the equation and call
updateResults directly from the main processing thread, but still the
first fetch I try using the new EC and Object Store Coordinator I get
the error:
java.lang.IllegalStateException: Attempt to access an EO that has
either n
Normally, the pattern I use is to create a separate class that
implements Runnable or Callable. Not sure if your use of an inline
anonymous class inside the WOComponent has anything to do with your
problem I just don't know since I don't use that pattern for
threads. Might be worth refa
As I look closer at the exception trace, the problem seems to have
something to do with the fetch traversing inverse relationships that
are setup within the model. Notice the following part of the stack
trace:
at com.netbracketsfw.model._Pricing.pools(_Pricing.java:86)
the prici
Sure, here's how the thread is kicked off. updateResultsThread and
updateResults are both functions in the Component class.
public void updateResultsThread(final int winCmd) {
t = new Thread("updateResults") {
public void run() {
This may be just a trivial coding sequence problem Jeff.
Why not post your whole Runnable (or Callable) class so we can see
what you are doing ?
On Aug 4, 2008, at 12:01 AM, Jeff Schmitz wrote:
Hello,
Continuing on with trying to access EOs in a background thread, I'm
trying to give
Hello,
Continuing on with trying to access EOs in a background thread, I'm
trying to give the background thread its own
EOObjectStoreCoordinator. To create a new EOObjectStoreCoordinator,
I'm using the following code:
EOObjectStoreCoordinator parentObjectStore = new
EOObjectSto
14 matches
Mail list logo
