OSP fails if compiled on Java 1.6
Description
Environment
Test Plan
is related to
Activity

Sam Ottenhoff October 27, 2011 at 9:00 AM
Other Sakai tools have marked this as Won't Fix and will continue to require the JAVA_OPTS.... Marking this JIRA the same to close the parent 1.6 issue.

Christopher Maurer January 10, 2011 at 9:54 AM
OSP team discussed and we are downgrading to Major.

Beth Kirschner June 22, 2010 at 10:56 AM
Note goals from June Project Planning Meeting in Denver (http://confluence.sakaiproject.org//x/CBUhB)
Ensure all tools are Java 1.6 compatible (eliminate need to specify the workaround system property -Dsun.lang.ClassLoader.allowArraySyntax=true)
Enforce strict quote escaping in *.jsp files (eliminate need to specify the workaround system property -Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false required since Tomcat 5.5.27).

Anthony Whyte March 2, 2010 at 1:13 AM
Lowering the status to critical.

Anthony Whyte March 2, 2010 at 1:09 AM
Addressing this issue will be deferred to either 2.8 or a later 2.7 maintenance version. The current workaround is to add the following environment parameter to JAVA_OPTS.
-Dsun.lang.ClassLoader.allowArraySyntax=true
Details
Details
Assignee

Reporter

A number of tools are broken in a similar way to: http://jira.sakaiproject.org/browse/SAK-16745
2009-07-23 14:48:57,191 INFO main org.apache.catalina.startup.HostConfig - Deploying web application archive sakai-chat-tool.war
java.lang.ClassNotFoundException: [Ljava.lang.String;
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1359)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1205)
This happens due to compiling with Java 1.6. The short term work around is to add the following option in the tomcat startup script.
-Dsun.lang.ClassLoader.allowArraySyntax=true
Code needs to be updated to avoid this.
Effected
Samigo-app,
sakai-chat
sakai-blogger
osp-wizaard-tool
osp-matrix-tool