I believe the answer is highly dependent on whether you're using the NS
collections from WebObjects JavaFoundation or the ones from WOnder. If I
remember correctly, Anjo did a lot of work optimizing performance on the
ones in wonder, making those much faster than the ones found in
JavaFoundatio
Thanks (to all who responded)!
I do use WOnder (is there nowadays any WO programmer who does not? Really?),
but still, self-evidently it makes sense to use Java collections primarily, and
go to NS-ones only when needed.
All the best,
OC
> On 2. 2. 2025, at 23:46, Ramsey Gurley wrote:
>
> I b
This I don’t see:
If you put it in src/main/resources, but did not include the fake maven nature
in your .project, it won't be found. If you are using fluffy bunny layout where
it is in Resource/ and you DO have the fake maven nature in .project, it also
won't be found.
MY user.d2wmodel lives a
Hi all,
Even if I still use EOF (due to inheritance limitations of Cayenne), I followed
Hugi’s precepts :
- « use 100% java native whenever possible »
One other advantage when working in a team… is that 100% java is widely
documented and exampled... and it's more attractive to newbees.
Sorry
Iirc the NS collections were there due to simplifying porting of apps from objc to Java. I don’t think there is any big difference in performance Sent from my iPhoneOn 2 Feb 2025, at 12:18, Jérémy DE ROYER via Webobjects-dev wrote:
Hi all,
Even if I still use EOF (due to inheritance limitat
When I made the switch to Java collections I did do some benchmarking. Haven’t
got the code anymore (this was a decade ago) but at that time, the Java
collection classes were faster, but the operations were really so fast in both
cases that the differences were negligible — at that time.
Since
