• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Rant: Why I hate Java Client
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Rant: Why I hate Java Client


  • Subject: Re: Rant: Why I hate Java Client
  • From: Florijan Stamenkovic <email@hidden>
  • Date: Wed, 20 Feb 2008 19:11:47 -0400

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.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
  • Follow-Ups:
    • Re: Rant: Why I hate Java Client
      • From: "Pierce T. Wetter III" <email@hidden>
References: 
 >Rant: Why I hate Java Client (From: "Pierce T. Wetter III" <email@hidden>)

  • Prev by Date: Re: Rant: Why I hate Java Client
  • Next by Date: Re: slow app when having a lot of D2W rules ?
  • Previous by thread: Re: Rant: Why I hate Java Client
  • Next by thread: Re: Rant: Why I hate Java Client
  • Index(es):
    • Date
    • Thread