Re: Switching from XCode to WOLips: ressources headaches
Re: Switching from XCode to WOLips: ressources headaches
- Subject: Re: Switching from XCode to WOLips: ressources headaches
- From: Mike Schrag <email@hidden>
- Date: Wed, 16 Aug 2006 11:42:05 -0400
What exactly is the procedure you're using to run the app from
Eclipse or the commandline? If you're running from commandline, you
can ONLY do this after doing an ant build and running the app that is
created in the dist folder. If you're trying to run the one inside
of the build folder, you're going to get really weird behavior
(because it's not a REAL woa). To run from inside of Eclipse, you
should select your Application class in the Package Explorer, right-
click=>Debug As=>WOApplication, or setup a WOApplication-based run/
debug profile manually.
I /guess/ maybe this should move over to the wolips list if you
continue to have problems?
ms
On Aug 16, 2006, at 11:31 AM, François Reboursier wrote:
On Aug 16, 2006, at 14:55, Timo Hoepfner wrote:
- Only the 'index.plist' file of my EOModel is copied to the
build ressources. I could manually add the others .plist
and .fspec files, but I don't want to do this manually every time
I add an entity. Is there a way to automate this ?
Probaby a problem with the patternsets above. my
"resources.include.patternset" includes the entry
**/*.eomodeld/
If that's missing (I guess the trailing slash is important), that
will likely cause the problem you are describing.
I had this, and an extra ' **/*.eomodeld ' line (without the
trailing slash)... :@
- When the project is built, no executable is created within
the .woa bundle, but the project can be run nevertheless (this
one is really weird... )
That's ok. the "build" folder is only for use by eclipse. If you
want to deploy, you'll have to use ANT:
-configure the filter (like above) to show the "build.xml" file
-Add the ANT view: Menu->Window->Show View->Other, Select Ant/Ant
from there
-drag the build.xml form the Package Explorer to the Ant View
-To build a deployable App, double-click the "build" task. It'll
create a deployable WOA in the dist folder (probably also hidden
by the default filter settings).
This works, thanks a lot Timo!
Now on to my other problem (and the last one I hope ! ): when I
run the app (in Eclipse or from the command-line) I get the following:
<WorkerThread0> <DirectAction>: Exception in performActionNamed()
on the action "default" with the message:
java.lang.NullPointerException
<WorkerThread0> java.lang.NullPointerException
at com.webobjects.appserver._private.WOComponentDefinition.<init>
(WOComponentDefinition.java:84)
at
com.webobjects.appserver.WOApplication._componentDefinitionFromClassNa
med(WOApplication.java:2353)
at com.webobjects.appserver.WOApplication._componentDefinition
(WOApplication.java:2448)
at com.webobjects.appserver.WOApplication.pageWithName
(WOApplication.java:1943)
at com.webobjects.appserver.WOAction.pageWithName(WOAction.java:98)
at DirectAction.defaultAction(DirectAction.java:29)
[snip]
The faulty line is DirectAction.java is:
return pageWithName(Main.class.getName());
The .woa appears to be well formed, the Main.wo is present (I
reduced its content to a simple 'hello world' to make sure),
the .jar contains the code for the Main class...
Any pointers on how to debug this?
Thanks,
François _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mdimension.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:
This email sent to email@hidden