What do you think of renaming the Rhino packages in the cocoondev.org version of Rhino used by Cocoon? It appears both Weblogic and Websphere ship their own versions of Rhino that are exposed to the class loader used by Cocoon. This prevents using flowscript "out-of-the-box" or at all with these containers. Although this is a brute force approach it seems straightforward and foolproof to implement. In contrast, attempting to implement some form of class loader isolation seems difficult and error prone given the lack of a proper architecture to support it in Rhino, Cocoon, and in Weblogic and Websphere.

Your thoughts?

Chris

Reply via email to