[ https://issues.jboss.org/browse/GTNPORTAL-2514?page=com.atlassian.jira.pl... ] Gary Hu commented on GTNPORTAL-2514: ------------------------------------ Is it possible that this issue was introduced in EPP 5.2 due to a different implementation on rendering the error/warning messages on the UI possibly to prevent the cross script attack? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/GTNPORTAL-2514?page=com.atlassian.jira.pl... ] Gary Hu commented on GTNPORTAL-2514: ------------------------------------ This issue could be reproduced against the EPP-SP 5.2.1-GA out of box installation: 1) change the PreNodeSaveInterceptor.groovy via the ecmdemo admin ui. Group->Content Manager's Page -> Administration -> Advanced Configurations > Manage Scripts > select interceptor in dropdown list -> click the "Edit' icon for PreNodeSaveInterceptor.groovy Add the following to the groovy template: import org.exoplatform.web.application.ApplicationMessage; import org.exoplatform.webui.exception.MessageException; public void execute(Object context) throws Exception{ ... throw new MessageException(new ApplicationMessage("Exception1<br/>Exception2",null, ApplicationMessage.WARNING)); } 2) create new content from Content Explorer click "New Content" button under Content Explorer and create a new content, for example "eXo:Article". After finishing the content and click "Save" button. It will show the NoSuchMethodError as reported in REDHAT-10. I had to recompile the exo-ecms-core-webui-2.3.6-CP01.jar using the workaround mentioned in REDHAT-10 to get this around. I'm attaching the recompiled jar file for your reference. To apply it just replace the original one under gatein-wcm-extension-5.2.1-exo-2.3.6-CP01.ear/lib with the attached one. After applying the "patch", and if you go through the same steps mentioned above, you will see the exception messages show on the pop up box. In EPP5.1 The message would have been -------------------------- Exception1 Exception2 --------------------------- i.e <br/> acts like a line break. In EPP5.2.1 I am getting Exception1<br/>Exception2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/GTNPORTAL-2514?page=com.atlassian.jira.pl... ] Gary Hu updated GTNPORTAL-2514: ------------------------------- Attachment: exo-ecms-core-webui-2.3.6-CP01.jar -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/GTNPORTAL-2514?page=com.atlassian.jira.pl... ] Boleslaw Dawidowicz closed GTNPORTAL-2514. ------------------------------------------ Resolution: Won't Fix This change was related to XSS issue and part of security fix -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira