Re: [OT] moving to Eclipse... still some issue
Re: [OT] moving to Eclipse... still some issue
- Subject: Re: [OT] moving to Eclipse... still some issue
- From: WO Dev <email@hidden>
- Date: Sun, 1 Jul 2007 22:29:23 +0200
OK,
I'm still trying to figure out why it wouldn't work on the dev
machine and not the deployment server...
I can launch the application and access the main start page (no
request to the database) but when I try to log with a user I got:
----
2007-07-01 12:33:19 CEST] <WorkerThread1> java.lang.NullPointerException
at
com.webobjects.eoaccess.EOAttribute.adaptorValueByConvertingAttributeVal
ue(EOAttribute.java:2020)
at com.webobjects.jdbcadaptor.JDBCColumn.takeInputValue
(JDBCColumn.java:562)
at
com.webobjects.jdbcadaptor.JDBCChannel._bindInputVariablesWithBindingsAn
dExecute(JDBCChannel.java:226)
at com.webobjects.jdbcadaptor.JDBCChannel._evaluateExpression
(JDBCChannel.java:303)
at com.webobjects.jdbcadaptor.JDBCChannel.evaluateExpression
(JDBCChannel.java:261)
at com.webobjects.jdbcadaptor.JDBCChannel.selectAttributes
(JDBCChannel.java:185)
at
com.webobjects.eoaccess.EODatabaseChannel._selectWithFetchSpecificationE
ditingContext(EODatabaseChannel.java:878)
at
com.webobjects.eoaccess.EODatabaseChannel.selectObjectsWithFetchSpecific
ation(EODatabaseChannel.java:215)
at
com.webobjects.eoaccess.EODatabaseContext._objectsWithFetchSpecification
EditingContext(EODatabaseContext.java:3205)
at
com.webobjects.eoaccess.EODatabaseContext.objectsWithFetchSpecification(
EODatabaseContext.java:3346)
at
com.webobjects.eocontrol.EOObjectStoreCoordinator.objectsWithFetchSpecif
ication(EOObjectStoreCoordinator.java:539)
at
com.webobjects.eocontrol.EOEditingContext.objectsWithFetchSpecification(
EOEditingContext.java:4114)
at er.extensions.ERXEC.objectsWithFetchSpecification
(ERXEC.java:944)
at
com.webobjects.eocontrol.EOEditingContext.objectsWithFetchSpecification(
EOEditingContext.java:4500)
at Session.validateEmployee(Session.java:132)
at Main.checkLogin(Main.java:48)
----
The method validateEmployee is correct I printed the stacktrace, and
it crash just after the "evaluateExpression" but I can't find
something with a null value:(
But only on the deploy machine...
I remember something about framework without the "current" folder or
something like this.
Could it be the reason?
Xavier
Hello Chuck:)
But it seems there's 2 different problems, the first one for me
is Monitor isn't able to start the instance for the updated apps.
Which is a serious issue because all schedule instances won't be
able to restart!
Anyone has an idea why it only happens with applications build
with WOLips?
There is (or is this fixed now?) a problem with the executable not
being marked as an executable file. You need to chmod 755 App.woa/
App
I do this in my Ant file that builds the deployment package.
It's not fixed because it was the issue regarding Monitor couldn't
launch it:)
Who was complaining about Apple not fixing some bugs in
WebObjects?:) It would be nice to fix it, it's really something
that would make a new comer go back to xCode:(
I'm not used to ant files and things like this, could you tell me
which file to edit and what to add?
The exact same application build with Xcode works.
Starting with the command line work only if I remove the --
NSProjectSearchPath ()...
That might be a different issue then.
Monitor can launch it with the correct rights so this seems ok.
I still have issues with the application, I'll try to investigate
now Monitor is working to see if I can fix them.
Thanks:)
Xavier
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40anazys.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