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 (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects%
40avendasora.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
