• 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: WOToManyRelationship issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOToManyRelationship issue


  • Subject: Re: WOToManyRelationship issue
  • From: Don Lindsay <email@hidden>
  • Date: Tue, 22 Mar 2005 14:44:59 -0500

Hello;

Thanks for the quick response. I turns out that I was using the control correctly but I found that the associative table that is created by EOModeler, the columns and table name are not defined in the module. Once you assign the names to the columns and the associative table then you can use the WOToManyRelationship control. :) He,he.

Thanks

Don Lindsay

On Mar 22, 2005, at 2:01 PM, David Holt wrote:

Hi Don,

Documentation is located here:

http://developer.apple.com/documentation/WebObjects/Reference/ WOJExtensions/index.html

I bind my control in the following manner:
<ScreenSnapz.jpg>

In my form, I am inputting a process image and wanting to display the evidence associated with it. Your EO is going to have the toMany relationship (in this case evidences) and you have to select the key you want to display (in this case I am displaying the numeric ID). Your source is the instance of the object you are inputting using the form and the Entity is your object.

From looking at your code, I assume you are entering the Area Codes in an Audit form. If that is the case, you probably want the following bindings:

Datasource: null
DestinationDisplayKey: "description" (pick an identifying characteristic of the AreaCode EO)
isMandatory: null
relationshipKey: "issueAreaCodes" (the to many relationship in your Audit EO)
sourceEntityName: "AreaCode" (the name of the EO)
sourceObject: anAreaCode (or whatever you have called your instance of the object)


I hope that helps,

David


Audits >> issueAreaCodes < issueAreaCode

When I attempt to use a WOToManyRel in my form I get a null pointer exception. I have been trying for a week to get this to work. I have the to-one relationships working with no problems. Just the WOToManyRel is not working.

I have the following in the properties:

Datasource: null
DestinationDisplayKey: "description"
isMandatory: null
relationshipKey: "issueAreaCodes"
sourceEntityName: "Audits"
sourceObject: projectData

Thanks,

Don Lindsay

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


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:
email@hidden


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
References: 
 >EOModelGroup.defaultGroup().models() is empty !!! Why ? (From: Dumitru Husleag <email@hidden>)
 >JavaMonitor Null Pointer exception (From: "Robert Snyder" <email@hidden>)
 >WOToManyRel issue (From: Don Lindsay <email@hidden>)
 >Re: WOToManyRel issue (From: Don Lindsay <email@hidden>)

  • Prev by Date: Re: ANY DB2 Experts Here????
  • Next by Date: Re: Linking Array elements to WOComponents
  • Previous by thread: Re: WOToManyRel issue
  • Next by thread: Design Best Practice Question
  • Index(es):
    • Date
    • Thread