From: Peter C. <Pet...@me...> - 2006-06-13 10:56:25
|
> From: Jon Maber > I cant create a questionnaire tool - a null pointer exception=20 > is thrown=20 > in the code that checks to see if the parameters are right. =20 Chuck us the stack trace? - Peter |
From: Peter C. <Pet...@me...> - 2006-06-13 11:04:26
|
> From: Jon Maber > I cant create a questionnaire tool - a null pointer exception=20 > is thrown=20 > in the code that checks to see if the parameters are right. =20 > My guess is=20 > that the template in the CVS doesnt match the=20 > QuestionnaireFacility.java=20 > that was checked in. Wtf? SF appears to have lost at least one commit from me... - Peter |
From: Peter C. <Pet...@me...> - 2006-06-13 11:18:02
|
> From: Jon Maber > Stack trace below as requested. The issue appears to be that Oxford's questionnaire mods and my date mods crossed (although I don't know how I missed that file). I'll fix and commit. - Peter |
From: Peter C. <Pet...@me...> - 2006-06-13 11:30:16
|
> From: Peter Crowther > I'll fix and commit. ... But it'll have to be another day, as the new code from Oxford handles date parsing and error reporting in a manner utterly unlike the rest of Bodington and therefore my utility functions require severe refactoring. With other deadlines, I don't have time to do this today. Any other volunteers, if this is required sooner? - Peter |
From: Matthew B. <mat...@ou...> - 2006-06-13 11:49:07
|
Peter Crowther wrote: >> From: Peter Crowther >> I'll fix and commit. > > ... But it'll have to be another day, as the new code from Oxford > handles date parsing and error reporting in a manner utterly unlike the > rest of Bodington and therefore my utility functions require severe > refactoring. With other deadlines, I don't have time to do this today. Sorry? The date/time refactoring from Oxford was just a tidyup so that rather than having 3 ways of parsing a date there was just one (which was already in DateParser). Why is the date parsing unlike the rest of Bodington? -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |
From: Peter C. <Pet...@me...> - 2006-06-13 11:58:25
|
> From: Matthew Buckett > Why is the date parsing unlike the rest of Bodington? It's not, the parameter parsing is. In most of the rest of the system, parameter parsing is done in a function that has the request and the output writer to hand, so the present central functions for date-input-field parsing take those as parameters to minimise the call sequence. By contrast, checkParameters() in QuestionnaireFacility takes a Map of parameters and fills a Vector of error messages. I quite like the way checkParameters() does its job, but it means I need a version of the date-input-parser that can cope with parameter maps and appropriate outputs. - Peter |
From: Jon M. <jo...@te...> - 2006-06-13 11:15:15
|
Stack trace below as requested. Peter Crowther wrote: >> From: Jon Maber >> I cant create a questionnaire tool - a null pointer exception >> is thrown >> in the code that checks to see if the parameters are right. >> > > Chuck us the stack trace? > > java.lang.NullPointerException at org.bodington.assessment.QuestionnaireFacility.checkParameters(QuestionnaireFacility.java:1279) at org.bodington.assessment.QuestionnaireFacility.createCheck(QuestionnaireFacility.java:443) at org.bodington.servlet.facilities.Facility.createconfirm(Facility.java:7235) at org.bodington.servlet.facilities.Facility.createconfirm(Facility.java:7117) at org.bodington.servlet.facilities.Facility.insert(Facility.java:3694) at org.bodington.servlet.facilities.SuiteFacility.insert(SuiteFacility.java:108) at working.style_default_default.template_confirmcreatequestionnaire_en.process(template_confirmcreatequestionnaire_en.java:81) at org.bodington.servlet.BuildingServlet.doProcessing(BuildingServlet.java:516) at org.bodington.servlet.BuildingServlet.doGet(BuildingServlet.java:362) at org.bodington.servlet.BuildingServlet.doPost(BuildingServlet.java:292) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) |