• 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
[5.2.3] many to many with exposed attribute on join table
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[5.2.3] many to many with exposed attribute on join table


  • Subject: [5.2.3] many to many with exposed attribute on join table
  • From: Benjamin J Doherty <email@hidden>
  • Date: Sun, 28 Mar 2004 12:48:20 -0600

Friends,

With WO 5.2.2, this model worked fine in D2J:

Person -->> PersonOrganization <<-- Organization

I used the EOModeler command "Join in Many to Many" to create the PersonOrganization join table. I also filled out all of the database information for column names and the table name. In addition, I wanted to have an exposed attribute on the PersonOrganization table called businessTitle which is to-one relationship with another entity BusinessTitle. I deleted the flattened relationships from Person and Organization and made the relationship to the join table a class property on both server and client sides.

When the model was interpreted by D2J, I was allowed to select the Business Title from a drop down menu after adding the Organization to the Person's relationship. I could add an existing organization or I could add an organization which I created new instead of finding an existing one.

In 5.2.3, I get null pointer exceptions on the client side when I add a new relationship with an organization which does not yet exist. When I add a new Organization from within a Person instance, I have to add the relationship, create the organization, and save it. However, the new organization doesn't get added to the Person, so I have to Select it from within the Person instance's form. In 5.2.2, adding an organizational affiliation and creating a new organization worked flawlessly.

The null pointer exception doesn't cause the client to quit but if I try to use the client application after this null pointer exception, any instance of an entity I want to open up in the form mode is full of empty blanks.

Please let me know if I'm not being clear. This problem has pretty much put a stop to my work, because all of my applications so far use exposed attributes on many to many join tables in some way.

Cheers,

benjamin doherty
chicago illinois
bjd at pobox dot com
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


  • Prev by Date: Re: HELP: Problem using WebServices Assistant
  • Next by Date: Re: Binding WOString to method with parameters
  • Previous by thread: Re: Dynamic Template used for Generation of Page
  • Next by thread: Page creation and usage
  • Index(es):
    • Date
    • Thread