• 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 - FIXED!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • Subject: Re: Java Client refuses to use Client-Side classes once deployed - FIXED!
  • From: David Avendasora <email@hidden>
  • Date: Fri, 22 Jun 2007 08:42:16 -0500

Fixed it, or should I say it spontaneously, in a very reverse- Schrödinger's cat-way, fixed itself.

After going in and JUST LOOKING at the stuff in the Java cache and re- building the project for the 10th time, it is working. Rebuilding didn't help until after I went in a looked at the cache.

I have a feeling that for some reason Java WebStart must have been somehow using an old version of the cached app that had no custom client-side classes (I have no idea where it was getting it, the one in the cache had the classes).

I have since deleted the ~/Library/Caches/Java directory, rebuilt the application again and run it and everything is working correctly.

Thanks for the heads up on the Cache directory, it was the key, even though not the key anyone expected!

Dave


On Jun 22, 2007, at 6:04 AM, David Avendasora wrote:


On Jun 21, 2007, at 6:03 PM, Johan Henselmans wrote:


On 22-jun-2007, at 0:24, Pierre Bernard wrote:

That's one of the bad things of JavaClient. The little bits that make it hard to debug. In this instance, JavaClient silently falls back to EOGenericRecord when it doesn't find the appropriate class.

You should check the JAR downloaded to the client. Probably your classes aren't in there. I don't exactly know how XCode works for this, but there must be some copying that did not take place during the Deployment build. In XCode this may be a matter of adding classes to the right target or of adding a file copy build phase. I use Eclipse - so should you ;-)

Pierre


If you are using WebStart (like any Java app should use), then you can take a look in your java cace. On a Mac that is in ~/Library/ Caches/Java/cache/javaws/http/ (or any other folders over there).


You might find that not all the jars are downloaded, or not the right ones.

Okay, my application JAR is there (in the Cache directory), and it has all the classes in it. I'm guessing the way the WOA file and all the JARs are named (prefixed with DM, RM, etc) is just part of Java WebStart's caching strategy and is normal, yes?


If so, maybe it is a class-path thing?

Dave



On Jun 21, 2007, at 9:52 PM, David Avendasora wrote:

A little clarification. The difference isn't Development vs Deployment builds, it is the difference between the application running using the build-and-go functionality of Xcode, and the app running inside of Tomcat.

It doesn't call the client-side classes when run inside of Tomcat on either Mac or Windows2000.

Does anyone have any idea why the WebObjects would run differently in Tomcat than through build-and-go?

Dave

On Jun 21, 2007, at 2:35 PM, David Avendasora wrote:

Hi all,

I have a java client application (I know, I know) that refuses to use my client-side classes when built for deployment. When building for development in Xcode (I know, I know) it uses the client-side classes flawlessly. When deployed, it simply uses EOGenericRecord instead of the classes defined in the EOModel.

Oh, and it is deployed as a SSDD to Tomcat.

Does anyone have any idea why WebObjects would work differently in deployment than in development?

Thanks!

Dave

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@avendasora.com


This email sent to email@hidden



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


This email sent to email@hidden

- - - Houdah Software s. à r. l. http://www.houdah.com

HoudahGeo: One-stop photo geocoding
HoudahSpot: Powerful Spotlight frontend



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40netsense.nl


This email sent to email@hidden

Regards,

Johan Henselmans
http://www.netsense.nl
Tel: +31-20-6267538
Fax: +31-20-6273852





_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40avendasora.com


This email sent to email@hidden



_______________________________________________ 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
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>)

  • 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