Re: Problem following example in Java Client ... (solved)
Re: Problem following example in Java Client ... (solved)
- Subject: Re: Problem following example in Java Client ... (solved)
- From: Ray Ackland <email@hidden>
- Date: Tue, 19 Aug 2003 11:13:44 +1200
Pierre,
Have made a few discoveries. The documentation says for WO 5.2. And it
is within the same chapter that it refers to the two different things
- but perhaps they updated their instructions but not the illustration.
I thought there was a problem with the length because when it was one
letter shorter it would accept the name, but not the full name.
However, when longer it will accept it too.
ie it will accept pretty much anything except the name I am trying to
change it to (com.webobjects.eogeneration.EOFormController). This
suggested to me that that class already existed. And indeed it did -
but as a subclass of another branch of the hierarchy
(EODocumentController > EOEditingController > ...)
I guess the problem was I am using the new version of IB than that
supplied with WO5.2 - and they have updated it to include the class in
question.
Hopefully this means that I can just skip that step in the example and
carry on to success.
Thanks,
Ray.
On Monday, Aug 18, 2003, at 20:04 Pacific/Auckland, Pierre Bernard
wrote:
Hi!
Java Client technologies were refactored between WO 5.1 & WO 5.2. I
guess some of the documentation may still refer to the old package
names. Make sure to use the documentation that matches your version of
WO.
The correct class name for WebObjects 5.2 is
com.webobjects.eogeneration.EOFormController.
I can't rememeber ever having had a problem with a class name being
too long. Did you make sure that you declare your class a being a Java
class rather than an Objective-C one?
Pierre.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.