On Apr 5, 2007, at 4:13 PM, Fred Shurtleff wrote:
Also I know what you are saying about the use of the primary key
use and EOF discouraging its explicit usage; but this does not
appear to be such a bad transgression in that it is not ever
displayed nor used as a user manipulated attribute.
How is it a form value then? Is it written to a hidden text field?
The topicID value has to come from somewhere. Maybe it's a foreign
key in an object that your Java code already knows about. In any
event, it seems likely that you can refer to the Topic object that
topicID represents as a relationship value from a "parent" object or
in some way that avoids using the primary key explicitly.
Re:EOSharedEditingContext it is 'crossed out' in the Eclipse IDE
and shows a context message indicating this is a deprecated method.
But then the code you see was written in 2002 for a demo app in
"WebObjects Developer's Guide"(SAMS Publisher).
Shared objects can be tricky to use correctly. Failure to do so can
result in deadlocks and other problems. The best description I have
found is at <http://developer.apple.com/documentation/
LegacyTechnologies/WebObjects/WebObjects_4.5/System/Documentation/
Developer/WebObjects/DeltaDoc/EOF.html#CBGCHAIA>. It's a pretty
quick read that can save much grief later.
Aloha,
Art
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
