Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Java Client refuses to use Client-Side classes once deployed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Java Client refuses to use Client-Side classes once deployed

Subject: Java Client refuses to use Client-Side classes once deployed
From: David Avendasora <email@hidden>
Date: Thu, 21 Jun 2007 14:35:26 -0500

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


Follow-Ups:

Re: Java Client refuses to use Client-Side classes once deployed
From: David Avendasora <email@hidden>


Prev by Date:
WOPopUpButton

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

Previous by thread:
Re: WOPopUpButton

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

Index(es):

Date
Thread