Re: ERXEntityClassDescription - Invalid class name for entity [SOLVED]
Re: ERXEntityClassDescription - Invalid class name for entity [SOLVED]
- Subject: Re: ERXEntityClassDescription - Invalid class name for entity [SOLVED]
- From: Ash Mishra <email@hidden>
- Date: Mon, 13 Oct 2008 17:43:15 -0700
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.
Regards,
Ash
_______________________________________________
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