On Apr 25, 2006, at 1:16 PM, Andrew R. Kinnie wrote:
When I build and run the app on the development build configuration the app runs, though I get a weird error on the development machine in the one component - an NSTimestamp appears as a number in scientific notation, and the insert fails because a column is missing in the SQL near the "E" e.g.:
SQL ERROR - [position 116, near 'E' in ', 1.709028E+8, 1158, 112)'] insert error: comma expected but not found in data
Note: earlier in the same error message, it appears that the NSTimestamp is properly an NSTimestamp:
withBindings: . . . ., 3:2006-06-01 21:00:00(eventDate) . . . .
I have no idea what this means or why this is happening now.
This error is consistent with the use of Java 1.5:
"• A BigDecimal number compatibility issue exists due to a change in the
JDK's toString() returning scientific notation when exponents are needed.
This affects EO fetching. A workaround for this issue is to not lock on
BigDecimal EOAttributes. Another is to modify the scale and precision on
EOAttributes in your application."
You may have now seen Cliff Tuel's message about this problem and solutions that was posted a few minutes prior to your posting.
Another issue is when I take the development version's .woa to the deployment machine, I can't get the .woa to start in Monitor.
When I switch the development configuration to deployment I get "No Launchable Executable At Path"
The path is /Users/me/projects/myapp/build/deployment/myapp.woa
at that location there is an alias that I assume points to the .woa in /Library/WebObjects/Applications
"Get Info" on that alias and you'll probably see that it points elsewhere; by default, /tmp/myapp.dst//Library/WebObjects/Applications/myapp.woa which may no longer exist.