Subject: Re: How to Debug JIRA source - msg#00167

Previous Message by Date: (click to view message preview)

Re: Custom service - init() method is called twice!

The validation is only performed each time the init() method is called. Unfortunately it's called twice. Calling the class/method is handled by JIRA (each time the "Update" button is clicked the init() is called). The values I *want* to validate are the entered values in the form, but as I can't control (at least I don't know how) which properties is sent to the method, it gets a little frustrating. Snippet of source code: ///---- Start snippet ----/// public class DueDateCheckerService extends AbstractService { public void init(PropertySet props) throws ObjectConfigurationException { super.init(props); myLog.info(props); for (int i=0;i<PARAM_KEYS.length;i++) { if (hasProperty(PARAM_KEYS[i])) { params[i] = getProperty(PARAM_KEYS[i]); switch (i) { case 3: int temp = Integer.valueOf(params[i]); if (!(temp >= 0 && temp < 12)) { myLog.error("Incorrect input parameter (must be between 0-11): " + params[i]); throw new ObjectConfigurationException("The value must be between 0-11"); } hourOfDay = temp; break; case 4: if (params[i].toUpperCase().equals("AM")) { amPm=Calendar.AM; } else if (params[i].toUpperCase().equals("PM")) { amPm=Calendar.PM; } else { myLog.error("Incorrect input parameter (AM or PM): " + params[i]); myLog.error("Incorrect input parameter (AM or PM). Setting value to AM"); amPm=Calendar.AM; throw new ObjectConfigurationException("The value must be AM or PM"); } break; } myLog.debug(PARAM_KEYS[i] + ": " + params[i]); } else { myLog.error("Error in getting essential parameters, check " + XMLFILE); } } } } ///--- End snippet ----/// -- Post by thomasdahlin - online at: http://forums.atlassian.com/thread.jspa?forumID=100&threadID=24240

Next Message by Date: click to view message preview

Re: Custom service - init() method is called twice!

I usually include a value on the form that lets me know these are form submissions. Like <INPUT TYPE="HIDDEN" NAME="beenthere" value="donethat" /> But my validator restores the original values to the form on failure instead of the new invalid parameters. In your first example it wouldn't help on the second submission when beenthere=donethat and value=12. -- Post by DocKaos - online at: http://forums.atlassian.com/thread.jspa?forumID=100&threadID=24240

Previous Message by Thread: click to view message preview

Re: How to Debug JIRA source

What do you mean by debug? -- Post by me0wster - online at: http://forums.atlassian.com/thread.jspa?forumID=100&threadID=24244

Next Message by Thread: click to view message preview

Error when build a JIRA source in Eclipse IDE

This is a multipart message in MIME format. Hi All,    I tried to build JIRA source in Eclipse IDE , i am getting an error :   The project was not built due to "A resource exists with a different case: /JIRA/bin/com/atlassian/jira/bc/project/projectOperation.". Fix the problem, then try refreshing this project and building it since it may be inconsistent        JIRA          I had my JIRA source in the folder : D:/guru/JIRA/atlassian-jira-enterprise-3.12.1-source Below are the steps i did. 1. created new project (java project)         2. selected "create project from existing source and given location as D:/guru/JIRA/atlassian-jira-enterprise-3.12.1-source click next 3. selected the output folder JIRA/bin click finish Do i need to add any external jars to compile project successfully? Please help me out. Thanks & Regards, Gurunath Vankadara Tata Consultancy Services Discoverer Bldg, 4th Floor International Technology Park Ltd, Whitefield Road Bangalore - 560066,Karnataka India Mailto: gurunath.vankadara-/cgKlWMm3F8@xxxxxxxxxxxxxxxx Website: http://www.tcs.com ____________________________________________ Experience certainty.        IT Services                        Business Solutions                        Outsourcing ____________________________________________=====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you