Just reported :-)
On Jul 23, 2008, at 6:26 PM, Lachlan Deck wrote:
On 24/07/2008, at 1:12 AM, Rams wrote:
Okay, now I feel dumb :-)~
Generics wasn't broken! The problem was I was using WOContext's
directActionURLForActionNamed with generics and it only accepts a
NSDictionary and I was t
On Jul 23, 2008, at 17:14, Mike Schrag wrote:
Nope. String is final. means, well, any Object. Wildcards
are useless in this scenario.
F
try this:
http://java.sun.com/j2se/1.5/pdf/generics-tutorial.pdf
It's a bit dry but explains the whys and hows of generics and
wildcards.
Actually it
On 24/07/2008, at 1:12 AM, Rams wrote:
Okay, now I feel dumb :-)~
Generics wasn't broken! The problem was I was using WOContext's
directActionURLForActionNamed with generics and it only accepts a
NSDictionary and I was trying to pass it a
NSDictionary in almost every case. That worked i
I really like how explicit the the second one is ... You're going to
get a dictionary back where the keys are the same type as the
keypath you passed in and the values are the same type as the value
key path you passed in ... Even without the added docs explaining
what this does, you can al
Nope. String is final. means, well, any Object. Wildcards
are useless in this scenario.
F
try this:
http://java.sun.com/j2se/1.5/pdf/generics-tutorial.pdf
It's a bit dry but explains the whys and hows of generics and
wildcards.
Actually it should be NSDictionary or rather
just NSDiction
Nope. String is final. means, well, any Object. Wildcards
are useless in this scenario.
F
try this:
http://java.sun.com/j2se/1.5/pdf/generics-tutorial.pdf
It's a bit dry but explains the whys and hows of generics and wildcards.
On Jul 23, 2008, at 11:12, Rams wrote:
Okay, now I feel dumb
Okay, now I feel dumb :-)~
Generics wasn't broken! The problem was I was using WOContext's
directActionURLForActionNamed with generics and it only accepts a
NSDictionary and I was trying to pass it a
NSDictionary in almost every case. That worked in
5.3.3 since arguments weren't paramet
On 22.07.2008, at 22:05, Rams wrote:
There doesn't seem to be a way to move just the Wonder frameworks
there. Moving all the WebObjects frameworks to the top or the
bottom of the list has no effect.
The best is to checkout the source from SVN from the Wonder frameworks
you use and use th
Hi Guido,
There doesn't seem to be a way to move just the Wonder frameworks
there. Moving all the WebObjects frameworks to the top or the bottom
of the list has no effect. I still get errors in 5.4 that don't exist
if I switch back to 5.3. If I go to the Libraries tab and select
edit, I
On 22.07.2008, at 20:38, Rams wrote:
At risk of asking a stupid question, how exactly does one change the
load order?
There is an "Order and Export" tab in the build path settings for the
project in Eclipse.
cug
--
http://www.event-s.net
___
D
Hi all,
At risk of asking a stupid question, how exactly does one change the
load order?
rg
On Jun 4, 2008, at 1:42 AM, Guido Neitzer wrote:
On 03.06.2008, at 13:38, Qi Yang wrote:
In the project I'm working on I need to use 5.3 because of some
compatibility problems, and I added both Ja
On 03.06.2008, at 13:38, Qi Yang wrote:
In the project I'm working on I need to use 5.3 because of some
compatibility problems, and I added both JavaWOExtensions and
ERExtensions frameworks in the build path, but can't seem to get rid
of
the NSArray can't be parameterized error.
Is there any
Hi all,
I set up WO5.3.3 on OS X 10.4.11 with Eclipse and Wolips. I've read
about the trouble with NSArray cannot be parameterized error, seems that
WO5.3 doesn't support it and that I need to add ERExtension framework
from project wonder.
In the project I'm working on I need to use 5.3 because
13 matches
Mail list logo
