10.1.3.1 Worklist - Using Prototype with auto-gen JSP forms

Question

There is an interesting conflict when using the javascript package Prototype with the auto-generated jsp for worklist forms.
Inside the main JSP is this javascript function, which iterates through the keyNames array associatively:
function isNameExist(keyNames, name)
var exist = "false";
     for (keyName in keyNames)
     if(trim(keyNames[keyName]) == trim(name))
     exist = "true";
return exist;
However because of Prototype's modifications to the Array object, this function fails. To make it work, change the function to this:
function isNameExist(keyNames, name)
var exist = "false";
if (keyNames && keyNames.length > 0) {
          for (var j = 0; j < keyNames.length; j++)
          //for (keyName in keyNames)
          if(trim(keyNames[j]) == trim(name))
          //if(trim(keyNames[keyName]) == trim(name))
          exist = "true";
return exist;
FYI: I first discovered the problem when the Save button became disabled (after adding Prototype), and Firefox kept reporting the js error "globalUpdateForm has no properties".
My thanks to Ryan Gahl for this one!
PS: If anyone else has tried using Prototype and knows of other conflicts, please post!

Answer 1

My code is in a java Exec, in a bpel process. I am not using any JSP pages. What do you mean by child of the orabpel process? How do I check if my bpel process is a child of the orabpel process?
Thanks!
Moe