Ticket #270 (closed defect: fixed)
need better error from returnmoles.jar
| Reported by: | lawrence | Owned by: | ko23 |
|---|---|---|---|
| Priority: | critical | Milestone: | PreAlpha |
| Component: | MOLES | Version: | |
| Keywords: | Cc: |
Description
java -jar ../returnmoles.jar badc.nerc.ac.uk dataent1 xmldb:exist://glue.badc.rl.ac.uk:8080/exist/xmlrpc Exception in thread "main" java.lang.NullPointerException?
at ndg.services.returnmoles.Main.main(Main.java:145)
What went wrong? (This command normally works, so assume there is something wrong at the glue end ... or the network ... so it would be nice if I got a sensible error back to throw to the user ...)
Thanks Bryan
Change History
comment:2 Changed 15 years ago by lawrence
- Status changed from closed to reopened
- Resolution fixed deleted
Oh it went wrong because the backend was broken (exist was down), but the user couldn't tell the difference between a broken database and a missing URI ... which is what is needed.
Can I assume the new version will also deal with the exist access control issue?
I've reopened the ticket as I would rather we closed tickets *after* the code goes into the repository --- that way I don't need to watch the timeline ...
comment:3 Changed 15 years ago by ko23
No, it went down because the record wasn't there. The error messages are *far* more spectacular, and happen earlier in the code, if there is a DB problem.
Not at the moment. Depends largely on the current email exchange and how easy "better" solutions prove.
Fair enough, will close after update. Look for a zip prefixed "BADC" if there are site-specific pws.
Watch Subversion for upload of fixed version. The problem appears to be that the data entity didn't exist, thus null output. Why it wasn't there, I don't know...