Home >> All >> com >> RuntimeCollective >> [ questionnaire Javadoc ]

•	com.RuntimeCollective.questionnaire.action.* (6)	•	com.RuntimeCollective.questionnaire.bean.* (13)
•	com.RuntimeCollective.questionnaire.form.* (8)	•	com.RuntimeCollective.questionnaire.test.* (3)

• com.RuntimeCollective.questionnaire: Javadoc index of package com.RuntimeCollective.questionnaire.


Package Samples:

• com.RuntimeCollective.questionnaire.bean: The Questionnaire modules allows for the creation of complex Questionnaires, and the processing of data submitted by Users.  
• com.RuntimeCollective.questionnaire.action
• com.RuntimeCollective.questionnaire.form
• com.RuntimeCollective.questionnaire.test

Classes:

• QuestionnaireLink: The QuestionnaireLink class implements the abstract Link class, by linking to a Questionnaire. NB: Saving a QuestionnaireLink doesn't save its Questionnaire, as that could provoke some infinite loop. So take care of saving the destination first. If you want to be spared the hassle of writing JSPs for the creation of your QuestionnaireLink objects, do have a look at the pages written for the Sussex Enterprise project. You can find them by checking out the relevent project: "cvs co rsework", then look in rsework/web/admin. The pages are called addQuestionnaireLinkXXX.jsp. They should be pretty self-explanatory. ...
• Questionnaire: The Questionnaire class, which is basically a Publishable container of Questions and UserAnswers. With a Name and Description thrown in. It reuses SimplePublishable. If you want to be spared the hassle of writing JSPs to edit your Questionnaires, do have a look at the pages written for the Sussex Enterprise project. You can find them by checking out the relevent project: "cvs co rsework", then look in rsework/web/admin. The pages only deal with simple Polls (ie one question). The pages are called add/edit/deletePollXXX.jsp. The rsework/struts-config.xml file is also worth checking, for the action ...
• SimpleQuestion: Basic and incomplete implementation of the Question interface, which you can subclass at will to create new types of Questions. In your sub classes, you should define some Fields to store the possible answers (*not* Answers), and override isAnswerValid and makeNewAnswer , and (most probably) save , delete and the 2 usual constructors.
• SimpleAnswer: Basic and incomplete implementation of the Answer interface, which you can subclass at will to create new types of Answers. In your sub classes, you should define some Fields to store the actual answer content, and override setAnswerGiven and getAnswerGiven , and (most probably) save , delete and the 2 usual constructors.
• DefaultQuestionnaireTest: This is the default QuestionnaireTest class that new projects should use. It adapts the QuestionnaireTestReal to the new standard way to organise our JUnit test scripts. Do not use the QuestionnaireTest.java anymore. This class can be subclassed to specify eg a different default EBS.
• ManyInManyStringsQuestion: Question implementation which offers the choice of many Strings between many. Useful for multi-choice questionnaires, where more than one answer of many can be chosen.
• OneInManyStringsQuestion: Question implementation which offers the choice of one String between many. Useful for single-option questionnaires, where only one answer of many can be chosen.
• EditQuestionnaireAction: Implementation of Action to modify a questionnaire (proposed replacement for EditQuestionnaireAction but not fully checked for compatibility).
• QuestionnaireRealTest: This class does various tests of the questionnaire functionality. Do not use it directly, use its DefaultQuestionnaireTest subclass instead.
• EditQuestionnaireForm2: A form for creating/editing a Questionnaire (proposed replacement for EditQuestionnaireForm but not fully checked for compatibility).
• QuestionnaireException: The subclass of RuntimeException which should be thrown by classes in the Questionnaire module when they meet some kind of problem.
• QuestionnaireTest: This configures the QuestionnaireRealTest class, but old-style. Do not use this class, use DefaultQuestionnaireTest instead.
• AddQuestionnaireLinkAction: Implementation of Action that adds a QuestionnaireLink to the current CSL. It is passed the id of the Link.
• XInManyStringsQuestion: Common superclass for OneInManyStringsQuestion and ManyInManyStringsQuestion - contains methods useful for both.
• DeleteLinkedPollAction: subclass of EditPollAction that will also delete any links that the poll may have in the EntityLinkTable
• ClusterSafeQuestionnaire: An extension of Questionnaire that is (I really hope) cluster-safe (i.e. works with the SynchronizedEBS).
• EditQuestionnairePermissionRuleAction: Implementation of Action to edit the group permissions of a poll or questionnaire.
• UserAnswers: The UserAnswers class, which is basically a set of Answers given by a User to a Questionnaire.
• Question: Interface to implement if you want to create a new kind of Question for Questionnaires.
• Answer: Interface to implement if you want to create a new kind of Answer for Questionnaires.
• QuestionnaireForm: The parent QuestionnaireForm, which should be subclassed by actual questionnaires.
• PollForm: A custom QuestionnaireForm for Polls, only one String answer is required.
• EditPollAction: Implementation of Action that create/edit/delete a Poll.
• ProcessQuestionnaireAction: Implementation of Action to process a QuestionnaireForm.
• QuestionnaireLinkForm: A form for editing the very basic details of a new QuestionnaireLink

Home | Contact Us | Privacy Policy | Terms of Service