On May 8, 2009, at 3:30 PM, Kieran Kelleher wrote:
Ricardo, to start with Wonder, you only need ERExtensions and
ERJars ..... and by default they don't really change any of the
default WebObjects behaviour ..... but it will fix a lot of
WebObjects bugs for you by default AFAIK.
Yep thanks. We have plans to transition to Wonder. It's just that
it's not that easy because we have our own ajax frameworks and so we
have collisions with Wonder. When we transition to Wonder we'll be
dropping our ajax stuff and replacing it with Wonder because I don't
want to reinvent the wheel and want to take advantage of all the good
stuff in Wonder. :-) This is a large code base though. Many years
of development from the Objective-C WO days. :-) We have
transitioned to WO 5.4.3. Wonder is next on my list.
On May 8, 2009, at 3:01 PM, Chuck Hill wrote:
On May 8, 2009, at 11:46 AM, Ricardo J. Parada wrote:
.... [snip]...
I noticed something interesting. I inserted this line of code
right before the line of code where the problem occurs:
EOModelGroup.defaultGroup();
That forces all models to get loaded. I have seen several cases
where this caused EOF to start working. But it has to be done at
just the right time...
Yep... exactly what I'm seeing... I moved that line of code one line
down in the constructor right after calling another method that does
some other initialization and that fixes the problem. It seems as if
this problem is time dependent, because by moving it down one line I'm
just allowing for more time to pass by. The other method I call is
not really doing anything, it just checks a System property flag and
the prints something to the console and that's it. Very weird if you
aske me!!
Thanks all!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
