Re: Packaging webobjects apps and frameworks
Re: Packaging webobjects apps and frameworks
- Subject: Re: Packaging webobjects apps and frameworks
- From: Florijan Stamenkovic <email@hidden>
- Date: Mon, 23 May 2005 17:57:58 +0200
On the other hand, as I am just exploring on the subject, I see some
pretty unpleasant behavior of XCode + friends on this. It is if
WOBuilder has a preference to look into the EOModel when determining
attributes of an eo, over looking into a packed class. And does NOT do
it when one uses only the default package.
To overcome this one has to declare all the keys of the component with
full package path, if one wants to see his custom methods or variables
or whatever in WO Builder.
In contrast to this, all the methods are accessible even when the key
is declared just with the class name. Just not displayed to be
available.
I think it is not handy at all. Not to mention all the bah bah stuff
that comes with packing Application and Session classes...
But then again I am a complete novice to it, so maybe after a while it
will not seem like such a pain.
Cheers
F
On May 23, 2005, at 15:18, Anjo Krank wrote:
This is pretty bad practice and will almost certainly break in JDK 1.5.
Cheers, Anjo
_______________________________________________
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