• 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: ERXEntityClassDescription - Invalid class name for entity [SOLVED]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ERXEntityClassDescription - Invalid class name for entity [SOLVED]


  • Subject: Re: ERXEntityClassDescription - Invalid class name for entity [SOLVED]
  • From: Kieran Kelleher <email@hidden>
  • Date: Tue, 14 Oct 2008 06:24:36 -0400

Wonder prevents you getting burned by not letting you play with fire ;-)


On Oct 13, 2008, at 9:14 PM, Chuck Hill wrote:


On Oct 13, 2008, at 5:43 PM, Ash Mishra wrote:


I'm trying to switch a WOApp that has a framework with my model and entity classes to use Project Wonder. I've followed the Quickstart guide, but the following error occurs when the application launches:


[main] WARN er.extensions.ERXEntityClassDescription - Invalid class name for entity: Account exception: java.lang.ClassNotFoundException: Account using com.webobjects.eocontrol.EOGenericRecord instead



For the record on a google search. The problem above is if you put the classes for your entities in packages. e.g. framework/sources/ com/myproject/entities/Account.java.

If your EOModel lists Account as the entity name and Account as the class name, in a standard WOLips / Eclipse project that uses a framerok - this will work. WO at runtime is able to find Account without any difficulty.

Switching to Project Wonder (use of ERXApplication... etc), this breaks, because whatever classloading mechanism Wonder is using - it is unable to find the class for the entity unless the full package name is specified. ie. The EOModel needs to list Account as the entity name, and com.myproject.entities.Account as the class name. This solves the issue.


I'd say that regardless of what you are using, the class name in the model should match the fully qualified class name. Anything else is playing with fire.


Chuck


-- Chuck Hill Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects







_______________________________________________ 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

_______________________________________________ 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: 
 >ERXEntityClassDescription - Invalid class name for entity (From: Ash Mishra <email@hidden>)
 >Re: ERXEntityClassDescription - Invalid class name for entity (From: Chuck Hill <email@hidden>)
 >Re: ERXEntityClassDescription - Invalid class name for entity [SOLVED] (From: Ash Mishra <email@hidden>)
 >Re: ERXEntityClassDescription - Invalid class name for entity [SOLVED] (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: [Wonder-disc] Locking problem
  • Next by Date: Re: Eclipse 3.4.1
  • Previous by thread: Re: ERXEntityClassDescription - Invalid class name for entity [SOLVED]
  • Next by thread: Eclipse 3.4.1
  • Index(es):
    • Date
    • Thread