• 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: Pierre Bernard <email@hidden>
  • Date: Fri, 22 Jun 2007 00:24:56 +0200

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


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:
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:
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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Java Client refuses to use Client-Side classes once deployed
      • From: Paul Lynch <email@hidden>
    • Re: Java Client refuses to use Client-Side classes once deployed
      • From: Johan Henselmans <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>)

  • Prev by Date: Re: WOPopUpButton
  • Next by Date: Re: Java Client refuses to use Client-Side classes once deployed
  • 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