Hi,
  It seems for now the function attribute in <map:call> must be a function in the global object. I think it might be better if this function could be within a scope object because our project groups all _javascript_ objects like java packages (or just like what dojo does). There are more _javascript_ codes than java codes in our project, so goruping them in different naming spaces is needed. Cocoon itself is a good environment for easily _javascript_ coding at the server side with its flowscript and continuation. However, it seems not that care about naming space at _javascript_ code itself. Maybe some ideas from dojo can be borrowed here. Like dojo has dojo naming space, cocoon has cocoon naming space, and within cocoon, there are cocoon.flow, cocoon.flow.continuation,...

Rice

Reply via email to