Re: Setting a Default toOne Relationship
Re: Setting a Default toOne Relationship
- Subject: Re: Setting a Default toOne Relationship
- From: Paul Lynch <email@hidden>
- Date: Tue, 29 Aug 2006 19:28:05 +0100
Could it be as simple as the eo classes not being included in the JC
target?
Paul
On 29 Aug 2006, at 19:22, David Avendasora wrote:
Paul,
I've just been getting back to this issue, and you seem to be spot-
on. I've left the client class setting pointing to:
com.bestmaid.erp.client.Routing in the .eomodel file, but deleted
the generated classes from the project. When I compile and run, it
never complains about the classes missing.
I get no feedback in the console at all - no errors, no warnings,
nothing. This leads me to believe that it isn't looking for them in
the first place.
I've tried scouring the documentation, but I can't see why it
wouldn't call the client class only when deployed.
I wonder if it has something to do with the application settings or
command-line arguments such as WODirectConnectEnabled? Any ideas?
Thanks,
Dave
On May 19, 2006, at 3:01 PM, Paul Lynch wrote:
I have to wonder if your D2JC app is ignoring your eo classes, and
acting directly on the database, by way of EOGenericRecord? I
believe that, in some circumstances, if WO can't find your class
from the eomodel, it will fall back on EOGenericRecord.
IIRC, JC uses some form of 2 stage commit - first is within the JC
app, then a further commit back to the server. If you follow this
idea through the documentation, something useful might pop up (I
hope).
_______________________________________________
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