The ERExtensions framework needs to come in front of the WebObjects
frameworks. That is because the newer versions of those NS foundation
classes are in Wonder.
I achieve this in development by having the Wonder projects in my
workspace and I adjust the Build Order in the Build Path. Not sure
how you can manipulate this when just referencing installed
frameworks .... maybe by editing the .classpath file entry that reads
something like this:
<classpathentry kind="con"
path="org.objectstyle.wolips.ContainerInitializer/10/1/Ajax/1/nil/1/
nil/1/0/1/false/10/1/ERExtensions/1/nil/1/nil/1/0/1/false/10/1/ERJars/
1/nil/1/nil/1/0/1/false/10/1/ERJavaMail/1/nil/1/nil/1/0/1/false/10/1/
ExcelGenerator/1/nil/1/nil/1/0/1/false/10/1/JavaWOExtensions/1/nil/1/
nil/1/0/1/false/10/1/WKDemography/1/nil/1/nil/1/0/1/false/10/1/
WKEmailData/1/nil/1/nil/1/0/1/false/10/1/WKEOFExtensions/1/nil/1/nil/
1/0/1/false/10/1/WKFoundation/1/nil/1/nil/1/0/1/false/10/1/
WKPrototypes/1/nil/1/nil/1/0/1/false/10/1/WKRemoteMailingServices/1/
nil/1/nil/1/0/1/false/10/1/WKWebObjects/1/nil/1/nil/1/0/1/false/10/1/
WOOgnl/1/nil/1/nil/1/0/1/false/10/1/JavaEOAccess/1/nil/1/nil/1/0/1/
false/10/1/JavaEOControl/1/nil/1/nil/1/0/1/false/10/1/JavaFoundation/
1/nil/1/nil/1/0/1/false/10/1/JavaJDBCAdaptor/1/nil/1/nil/1/0/1/false/
10/1/JavaWebObjects/1/nil/1/nil/1/0/1/false/10/1/JavaXML/1/nil/1/nil/
1/0/1/false"/>
... anyone else got a suggestion?....
Not sure though how you do this without Wonder source in workspace.
(Wow, is this yet another advantage to having Wonder source in the
workspace?!) http://wiki.objectstyle.org/confluence/display/WONDER/
Working+with+Wonder+source+in+Eclipse
In deployment this is taken care of by the build.xml file, and the
resulting classpath order is seen in the MacOSClassPath.txt file
inside the deployment bundle.
On Dec 14, 2007, at 5:23 AM, Paul Armitage wrote:
Hi,
I've switched to Eclipse 3.3.1.1 with WOLips 3.3.4743.
I'm on Leopard but with Wonder compiled for 53 and with the WO53
frameworks installed as per current thinking. (Many thanks Mike,
what _would_ we do without you? See, it _is_ appreciated!)
Now any source which refers to an NSMutableArray or an
NSMutableDictionary is throwing an error like this:
NSMutableDictionary bindings = new NSMutableDictionary();
"The type Dictionary is not generic; it cannot be parameterized
with arguments <? extends K, ? extends V>"
For the projects I'm referring to ERExtensions, ERJars and they are
not included as projects in my workspace. In the Compiler/Errors/
Warnings/Generic types section I have all set to "Ignore", which I
thought (mistakenly it seems) would address this problem.
Could someone more familiar with Eclipse please point out what
simple and obvious setting I'm missing to switch these errors off?
Thanks,
Paul
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists%
40mac.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
