I´m 100% agree with Florrijan. I´m using JC a lot, and sometimes it is much better solution for intranet, than Flex/Hibernate or other intranet platforms that I worked with (I´m not trying to open a discussion of what solution is better, what I´m trying to point out is that JC is very good).
If you use the Florrrijan binding framework with JFormDesigner tool, or develop your own binding framework (as I did). You can develop screens very fast. More to JC in my case for simple screen I´m still using the D2JC controllers classes programatically with WO 5.4.1
Another happy developer using JC.
Ricardo.
Message: 4
Date: Wed, 20 Feb 2008 19:11:47 -0400
From: Florijan Stamenkovic <email@hidden>
Subject: Re: Rant: Why I hate Java Client
To: "Pierce T. Wetter III" <email@hidden>
Cc: Development WebObjects <email@hidden>
Message-ID: <email@hidden">email@hidden>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
So this is some sort of config problem, brought on somehow by the
fact that I've moved all the .jar cruft we had hanging out in /
Library/Java/Extensions into a framework. It looks like the server
is forwarding some sort of EOGeneralAdaptorException to the client
which might have had useful information in it but client has no
idea how to unarchive it because for some reason it can't access
eocasses, so it then throws a completely different exception on the
client side.
Interesting situation. The eoaccess package is not provided because
it contains stuff that is irrelevant to the client. Mostly the
"connect to database" stuff. So it makes sense it is not there.
Like Lachlan says, log the exception on the server.
Plus none of this stuff works for me from Eclipse, because no one
ever got around to porting it fully to Eclipse when they moved the
rest of the projects over.
Meanwhile, the Support folks are whining, because I lowered the
boom and told them Java Client was going away,
Very much not true. Let the light of the JC sun shine on you and
realize: Apple is not dropping it! YAY! :)
so they have to adjust to an app that isn't just a thin coat of
paint over Direct2JavaClient and actually come up with a
specification for what all they use this piece of shit for.
I've spent 40 hours over the last 2 weeks fighting with this stupid
thing. It takes me about an hour to build a screen in the new app
that will replace this crap.
The new app being based on which technology? Might I suggest
switching to WO Java Client "the third way"? No D2JC, no Interface
Builder to Swing translation... It will still be possible to get
exception stack traces that are somewhat obscure (until you get used
to it at least, and apparently especially so if the root of the
problem is a thrown EOGeneralAdapterExeption), but they will be
shorter :)
Best regards,
Flor
of
The Perpetually Happy WOJC Lobby :)
or simply TPHWOJCL
p.s. - before you ditch JC as a lost cause, well, I've invested a
_lot_ of time looking for a good rich GUI client - server tech that
we could use in my company. Still sticking to WO, regardless of some,
minor, annoyances.
|