• 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: Fake Entity Modeler validation errors preventing veogen running
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fake Entity Modeler validation errors preventing veogen running


  • Subject: Re: Fake Entity Modeler validation errors preventing veogen running
  • From: Mike Schrag <email@hidden>
  • Date: Tue, 22 Apr 2008 12:54:40 -0400

I've updated to WOLips 3.3.5047 but now can't veogenerate because of model validation errors relating to key paths in model based fetch specifications:

/Users/Eclipse2/ClickTravelSystem/Resources/TravelSystem.eogen:
Error: The fetch specification TrainLegSearch has a qualifier that refers to an invalid key 'segment.voucher.ticketQueue'.
Error: The fetch specification TrainLegSearch has a qualifier that refers to an invalid key 'flightNumber'.


However, the key paths refer to attributes contained within subclasses so are actually valid.

We had the same problem with Component Editor validation but can work around it by marking them with

//VALID

Is there something similar in Entity Modeler ?
It's a known bug in EM and there is no way to mark them valid ...

ms

_______________________________________________
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: Fake Entity Modeler validation errors preventing veogen running
      • From: Simon McLean <email@hidden>
References: 
 >Fake Entity Modeler validation errors preventing veogen running (From: Simon McLean <email@hidden>)

  • Prev by Date: Re: ERXMigrationTable.newColumn does not set default value
  • Next by Date: Re: ERXMigrationTable.newColumn does not set default value
  • Previous by thread: Fake Entity Modeler validation errors preventing veogen running
  • Next by thread: Re: Fake Entity Modeler validation errors preventing veogen running
  • Index(es):
    • Date
    • Thread