On Feb 26, 2008, at 12:02 PM, David Peter Shaykewich wrote:

Hi All.

Now that we've lost our WO developer, I'll be supporting our existing apps and have no experience with WO. So, apologies for the newb question, but I'm just not able to figure out what's going wrong.

My Machine:
        OSX Leopard
        Xcode 3.0
        Eclipse 3.3.1.1
        Wolips 3.3.4788

Our Server:
        OSX Tiger
(don't know much else about it but can find out from our sysadmins if required)

I've successfully installed the wolips development environment (thanks in large part to the great tutorials at wiki.objectstyle.org) and built a 'hello world' application that runs on my machine.

When we try to deploy the application to the server however, the Java Monitor will not start it (and increments the number of deaths). The sysadmin has looked for logs that would help diagnose what the problem might be, but hasn't found anything. Applications built with the old Apple development tools (on Tiger) are deploying successfully.

Any ideas what the problem might be?

There are a few things I thought might be a problem, but don't know how to diagnose without some indication of what is happening when the start button is pressed.

Java mismatch?
Xcode mismatch?
Wolips build params mis-configured?

Is there a way to turn on logging of the Java Monitor so that we can see what and how events are failing?


Here is an alternative:
http://www.gvcsitemaker.com/gvc.webobjects/ faq&mode=single&recordID=19193


--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects





_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list      (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to