thank you Justin. The reason why we want to disable the MWS JS files is because they interfere with our Portlet owned JS. For instance, there are some global arrays defined in our Portlet page. If the Portlet is deployed in Pluto, the data in these arrays is correct. However, if deployed in MWS, in addition to the original data, the arrays contain some other strange values like eventlistener. Do you kow if it’s possible that the MWS JS code that adds extra data into these arrays?
Thank you very much,
Wen
#webMethods#webMethods-BPMS#MWS-CAF-Task-Engine