• 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: WO Direct to Java Client Application questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO Direct to Java Client Application questions

  • Subject: Re: WO Direct to Java Client Application questions
  • From: Benjamin J Doherty <email@hidden>
  • Date: Mon, 19 Apr 2004 11:57:05 -0500
Ismael Nass-Duce wrote:

Created an emodel and used it to generate a Direct to Java Client Application.
When I ran the app, I noticed that for some entities, the form window, which allows
me to add a new record, contains a section that allows me to link the new record to
another entity, based on the relationship defined in the model. But for other similarly
defined entities, no linking section is displayed. What am I doing wrong? All I did is
create a Direct to Java Client Application based on the model and run the app.

Sometimes I think that the D2JC developers need our own list! We need to stick together.

It sounds like you've got to pay closer attention to the client class property attribute for your EOModel's relationships. If you want the relationship to be viewable or editable from "both sides" in the client application, you have some special problems to worry about.

D2JC builds the interface based on how you've set up the model. For relationships, the delete rule and "owns destination" attributes may determine how D2JC defines the entity containing that relationship. Apple's book about Java desktop applications explains the precise conditions an entity needs to meet in order to become a certain kind of entity. For example, an enumeration entity cannot be the destination of any relationships with a cascade delete rule. So you need to investigate all the relationships very carefully to be sure that the delete rules are appropraite for the kinds of entity you want each entity in your EOModel to be.

For your operations and services, I think that your operations may be enumerative entities, so you need to make sure that the service entity has relationships that enable that to happen automatically. It helps to define both sides of a relationship, even though it might not appear to be necessary with enumerative entities. Once you define both sides, make sure that the enumerative entity's relationship does not have any delete rules which would cause it to be promoted to a main or other entity. I use a DENY delete rule in the relationships of most of my enumerative entities and a DO NOTHING delete rule when the enumeration entity is the destination of the relationship.
_______________________________________________
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.

References: 
 >java.io.IOException: No serializer found for class... (From: Ismael Nass-Duce <email@hidden>)
 >Re: java.io.IOException: No serializer found for class... (From: Tony Becker <email@hidden>)
 >Re: java.io.IOException: No serializer found for class... (From: Ismael Nass-Duce <email@hidden>)
 >Creating serializer and deserializer classes... (From: Ismael Nass-Duce <email@hidden>)
 >WO Direct to Java Client Application questions (From: Ismael Nass-Duce <email@hidden>)

  • Prev by Date: Re: making associations between eomodeler files
  • Next by Date: Re: WOFileUpload - No form data left for WOFileUpload!
  • Previous by thread: WO Direct to Java Client Application questions
  • Next by thread: Re: java.io.IOException: No serializer found for class...
  • Index(es):
    • Date
    • Thread