To check for errors, go to XCode and find the "Executables" group and
open it. This should show the resulting executable file. Double click
on this (not the one on the right hand side). In there, you can add a
few command line arguments. Put the following in:
-NSDebugGroups -1
-NSDebugLevel 1
This will get WO to display a number of things that are happening in
the background (such as SQL calls). Any errors that occur should now
get listed in the run log. This may give you "some" idea of where
things are going wrong.
Personally, I have found it very hard to debug Direct to Java (D2J) as
the Java client is running in its own JVM space, so you can't control
it from Xcode (which can only debug the server side).
Let me know how you go. More help is available.
Ray.
On 30/11/2003, at 6:43, Franco Solerio wrote:
Hello, I am evaluating WO 5.2.2 on my Panther-ized PB 12''.
I tried to create a simple DB with EOmodeler and make a Direct to web
app with that EOmodel: everything works fine.
Then I tried Direct To Java on the same EOmodel, the project builds
with no errors and a java icon appears in the dock with no window
associated with it and menu caption is:
"com.webobjects.eoapplication.client.EOClientApplicationSupport". I
can wait for ages but no app window appears.
Tried one of webobjects java examples (JCDiscussionBoard) and the
result is exactly the same: project builds and starts with no errors,
but no window appears.
What am I doing wrong?
--__--__--
