• 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: Java Client refuses to use Client-Side classes once deployed
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Java Client refuses to use Client-Side classes once deployed


  • Subject: Re: Java Client refuses to use Client-Side classes once deployed
  • From: David Avendasora <email@hidden>
  • Date: Fri, 22 Jun 2007 09:49:06 -0500

Okay, just a little perspective on this problem. While it wasn't Robert's suggested simple thing, it was another insanely simple thing. Just delete the Java WebStart Cache at ~/Library/Caches/Java.

This has been a problem for me for OVER A YEAR! Waste a bunch of time, indeed!  

My first post on the issue was back in May of last year, and as of August 2006, with the help of lots of people on the list, I had gotten close to figuring it out, but ended up giving up and shelving Java Client.

I stopped using doing JavaClient development just because I couldn't get this to work correctly, even with help from the list. After 9 months of trying to get a good Web UI to function as smoothly (for my purposes) as the Java Client, I went back to the Java Client version to see if I could figure it out again.

Having a year more of WO experience certainly helped me more quickly narrow down where the problem was and post much more informative requests for help, but without the continued help of the list, I'm sure I would have never figured it out, and all it was, was deleting a directory. Ahhhhhhgg!

Oh, and thanks to everyone that didn't go off on how Java Client is dead. I know it was hard for you (Chuck). :D

Thanks again!!!!!

Dave

On Jun 22, 2007, at 8:07 AM, Robert Walker wrote:

David,

Just to be sure, you do have the "Client-side class" set properly in your EOModel right?  If you happen to be using EOModeler you may have to add the column from the popup menu (since it's hidden by default).

I realize this is a basic thing, but I'd hate for you to waist a bunch of time due to something silly like this.



 _______________________________________________
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: Java Client refuses to use Client-Side classes once deployed
      • From: Robert Walker <email@hidden>
References: 
 >Java Client refuses to use Client-Side classes once deployed (From: David Avendasora <email@hidden>)
 >Re: Java Client refuses to use Client-Side classes once deployed (From: David Avendasora <email@hidden>)
 >Re: Java Client refuses to use Client-Side classes once deployed (From: Pierre Bernard <email@hidden>)
 >Re: Java Client refuses to use Client-Side classes once deployed (From: Johan Henselmans <email@hidden>)
 >Re: Java Client refuses to use Client-Side classes once deployed (From: David Avendasora <email@hidden>)
 >Re: Java Client refuses to use Client-Side classes once deployed (From: Robert Walker <email@hidden>)

  • Prev by Date: Re: WOPopUpButton
  • Next by Date: Re: WOPopUpButton
  • Previous by thread: Re: Java Client refuses to use Client-Side classes once deployed
  • Next by thread: Re: Java Client refuses to use Client-Side classes once deployed
  • Index(es):
    • Date
    • Thread