Re: Java Client refuses to use Client-Side classes once deployed
Re: Java Client refuses to use Client-Side classes once deployed
- Subject: Re: Java Client refuses to use Client-Side classes once deployed
- From: Paul Lynch <email@hidden>
- Date: Fri, 22 Jun 2007 10:16:55 +0100
On 21 Jun 2007, at 23:24, Pierre Bernard wrote:
That's one of the bad things of JavaClient. The little bits that
make it hard to debug. In this instance, JavaClient silently falls
back to EOGenericRecord when it doesn't find the appropriate class.
In this case it isn't just JavaClient, it is EOF. If the class
nominated in the eomodel isn't available, it uses EOGenericRecord.
This is actually convenient, as you can set up simple test projects
without having to rename all the classes in an eomodel.
Paul
_______________________________________________
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