Details
-
Bug
-
Resolution: Answered
-
Low
-
None
-
None
-
None
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Description:
Our plugin extends / overrides the CreateWorklog action and - in addition - exchanges the view (original view was: /secure/views/issue/logwork.jsp from actions.xml)
Extract from atlassian-plugin.xml:
<webwork1 key="ictime-extended-worklog" class="java.lang.Object"> <actions> <action name="de.iconcept.ictime.actions.timeentry.ExtendedCreateTimeEntry" alias="CreateWorklog"> <view name="input">/templates/ictime-webwork-module/extendedCreateEntry.vm</view> <view name="error">/templates/ictime-webwork-module/extendedCreateEntry.vm</view> <view name="invalidlicense">/templates/ictime-webwork-module/invalidLicense.vm</view> <view name="invalidJiraVersion">/templates/ictime-webwork-module/invalidJiraVersion.vm</view> <view name="securitybreach">/secure/views/securitybreach.jsp</view> </action> </actions> </webwork1>
If you click on the "Log Work" action within an issue, it happens - on customer installations - that an IllegalArgumentException is thrown:
java.lang.IllegalArgumentException: name
at sun.misc.URLClassPath$Loader.findResource(URLClassPath.java:494)
at sun.misc.URLClassPath.findResource(URLClassPath.java:176)
at java.net.URLClassLoader$2.run(URLClassLoader.java:551)
at java.net.URLClassLoader$2.run(URLClassLoader.java:549)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findResource(URLClassLoader.java:548)
at org.apache.catalina.loader.WebappClassLoader.findResource(WebappClassLoader.java:1267)
at org.apache.catalina.loader.WebappClassLoader.getResource(WebappClassLoader.java:1408)
at com.atlassian.core.util.ClassLoaderUtils.getResource(ClassLoaderUtils.java:113)
at com.atlassian.velocity.DefaultVelocityManager.exceptionHandling(DefaultVelocityManager.java:137)
at com.atlassian.velocity.DefaultVelocityManager.writeEncodedBodyImpl(DefaultVelocityManager.java:123)
at com.atlassian.velocity.DefaultVelocityManager.writeEncodedBody(DefaultVelocityManager.java:97)
at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest.toWriterImpl(DefaultVelocityTemplatingEngine.java:146)
at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest.asHtml(DefaultVelocityTemplatingEngine.java:134)
at com.atlassian.jira.web.dispatcher.JiraVelocityViewDispatcher.dispatch(JiraVelocityViewDispatcher.java:50)
at com.atlassian.jira.web.dispatcher.JiraWebworkViewDispatcher.dispatchViaVelocityView(JiraWebworkViewDispatcher.java:110)
at com.atlassian.jira.web.dispatcher.JiraWebworkViewDispatcher.dispatchView(JiraWebworkViewDispatcher.java:69)
at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:204)
From atlassian-jira.log:
2014-06-10 12:03:05,806 http-bio-8443-exec-61 ERROR earagones 723x176214x1 9cj4er 127.0.0.1 /secure/CreateWorklog!default.jspa [velocity] ResourceManager : unable to find resource 'de.iconcept.ictime.jira-ictime:ictime-extended-worklog//secure/views/issue/logwork.jsp' in any resource loader.
This means, that the webwork plugin from jira tried to find the original logwork.jsp in our plugin code instead of using the original jsp provided by jira OR taking the overriden velocity view defined in the atlassian-plugin.xml.
Enabling / disabling the plugin does not solves the problem. We are not able to reproduce the problem, but it happens frequently on customer sites installing our plugin.
Attachments
Issue Links
- relates to
-
-
- Closed
-
