Details
-
Bug
-
Resolution: Fixed
-
High
-
4.0
-
4
-
Description
WebSphere (in particular) defaults to using 1.3 syntax when compiling JSPs. Any Java5 syntax support (such as generified collections or return types) fails to compile, giving errors such as:
/home/was/IBM/WebSphere/AppServer/profiles/AppSrv04/temp/centos5wasNode04/server1/atlassian-jira-4_0_1-SNAPSHOT_war/atlassian-jira-4.0.1-SNAPSHOT.war/decorators/_admin.java : 368 : Type mismatch: cannot convert from Object to ReindexMessageManager
To fully assess the damage we need to install JIRA with Precompile JSPs switched on (an install option only).
The workaround is to set the JDK version to 15 in the JSP Compiler settings while installing (for example see this link) or to add something like:
<jspAttributes xmi:id="JSPAttribute_1257295496424" name="jdkSourceLevel" value="15"/>
In the WEB-INF/ibm-web-ext.xmi. Note you need to be careful with the xmi:id to make sure it is unique.
Attachments
Issue Links
- blocks
-
JRASERVER-19421 JIRA 4.0 does not work under WebSphere 6.1
- Closed
- details
-
JRASERVER-20239 Update WebSphere documentation to ask customers to make their WebSphere compile jsps in java 1.5
- Closed
- incorporates
-
JRASERVER-19241 JSP compliation error in Jboss 4.2.1
- Closed