Troubleshooting Form Problems (Oracle Waveset 8.1.1 System Administrator's Guide)

Oracle Waveset 8.1.1 System Administrator's Guide

Troubleshooting Form Problems

This section describes some common form problems and how to fix these problems.

You added a <script> tag to your user form, but see the following exception when trying to access the user form:
```
java.lang.NoClassDefFoundError: org/mozilla/javascript/NativeScript
```
You must put the WEB-INF/lib/javascript.jar file into the application server’s classpath. For example:
- If you installed Tomcat as a service (Windows only), edit the following registry key:
  
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tomcat\Parameters\JVM Option Number 0
  
  Append the path to your jar file to the end of the JVM Option Number 0 key string value, wherever it is located. For example:
  
  ;C:\tomcat\lib\javascript.jar
- If you just started Tomcat from the command line, move the jar file into the tomcat/lib directory.
You customized a Tabbed User Form, but when you try accessing the form through User Creation, you see the following exception:

com.waveset.util.WavesetException: Maximum form stack depth exceeded

You are limited to pushing 1000 hard-coded elements on the stack and you exceeded this limit.

If you added a check to detect Field containers that include a FieldRef or Field that matches the name of the Field container, you might have inadvertently created a circular reference on the form. To fix this problem, change the FieldRef or Field name.
You used a MultiSelect field in a form for LDAP users, assigned groups to a user in this field, edited the user again, and then see the same group on both sides of the MultiSelect. For example:
- Left side value. cn=Group1,dc=test,dc=Com
- Right side value. cn=Group1,dc=test,dc=com
  
  In this example, the LDAP baseContext resource field is set to dc=test,dc=com and the LDAP groups are listed as dc=test,dc=Com, which causes a problem because LDAP is not case sensitive, but the MultiSelect widget is case-sensitive.
  
  To alleviate this problem, change the baseContext on the LDAP resource to match the case in your LDAP resource dc=test,dc=Com or use the <upcase> XPRESS function to uppercase both the left and right side displays.