Re: Java Client refuses to use Client-Side classes once deployed
Re: Java Client refuses to use Client-Side classes once deployed
- Subject: Re: Java Client refuses to use Client-Side classes once deployed
- From: Robert Walker <email@hidden>
- Date: Fri, 22 Jun 2007 10:42:53 -0400
David you're probably right. Java web start uses a time stamp in a file to determine if it need to download a new version of the files from the server. I had this problem once when I tried to revert back to a previous version of the client app by replacing a backup of the deployed file and forgot to "touch" the file to update it's modification date on the server. Took me a minute to figure out that the clients were not getting the "older bug-free and stable" version of the client files from the server.On Jun 22, 2007, at 10:27 AM, David Avendasora wrote: LOL. Not the issue, but I do appreciate the "take nothing for granted" suggestion. :)
Dave On Jun 22, 2007, at 8:07 AM, Robert Walker wrote: 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