• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cannot register the database context for the model?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cannot register the database context for the model?


  • Subject: Re: Cannot register the database context for the model?
  • From: Mike Schrag <email@hidden>
  • Date: Tue, 24 Apr 2007 16:08:20 -0400

I think you chopped the rest of that exception off, but where that exception ends up in your code, you should have access to an editingContext() the one from the object you're talking to there. Print out editingContext.rootObjectStore() and see what type of object it is.

If it's an EODatabaseContext, cast it out and print out databaseContext.adaptor().name(), adaptor().canServiceModel (EOModelGroup.defaultModelGroup().modelNamed (themodelthatisfailing)). Then print out adaptor ().connectionDictionary() and thatModel.connectionDictionary() and make sure the keys "URL", "username", "password", "driver", "plugin" all match. These are basically the determining factors for that call to succeed. One of these things will be not true.

ms


On Apr 24, 2007, at 3:54 PM, Alan Zebchuk wrote:

Yes the error message was edited. The model it actually refers to does exist.

It's very odd that it only happens when I first try to access this relationship, and after that everything works fine.

All of the model paths are correct.

Alan


On 24-Apr-07, at 3:14 PM, Mike Schrag wrote:

All the entity names are unique. The model.adaptorName() is "JDBC" and the dabase context's adapter().name() is "JDBC". I've also removed the jdbc2Info dictionaries from all the models. However, the error still occurs.

Alan
Do you actually have a model named MyEOModel or was that error message edited? That sounds a little suspicious given that MyEOModel is the default name Entity Modeler makes for a new model. I would enumerate in code in your app the default mode group's models, print out all the names, and the locations of the model folder and make sure the models are what you think/expect them to be.

ms

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40protocolis.ca


This email sent to email@hidden

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mdimension.com


This email sent to email@hidden


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Cannot register the database context for the model?
      • From: Alan Zebchuk <email@hidden>
References: 
 >Cannot register the database context for the model? (From: Alan Zebchuk <email@hidden>)
 >Re: Cannot register the database context for the model? (From: Mike Schrag <email@hidden>)
 >Re: Cannot register the database context for the model? (From: Alan Zebchuk <email@hidden>)
 >Re: Cannot register the database context for the model? (From: Mike Schrag <email@hidden>)
 >Re: Cannot register the database context for the model? (From: Alan Zebchuk <email@hidden>)

  • Prev by Date: Re: Cannot register the database context for the model?
  • Next by Date: Re: Noticing changes to a WOTextField
  • Previous by thread: Re: Cannot register the database context for the model?
  • Next by thread: Re: Cannot register the database context for the model?
  • Index(es):
    • Date
    • Thread