Hello, I have made some investigations and found that the cookie injection into the top of the html page was causing the browser display issue. Setting webSEAL parameter to inject cookie at end the html page is fixing this issue.
But another problem is there: When the form is submitted with POST, the json reponse returns html of the form, and at the end, the scripts linked to component used in the form. Url of the scripts are partial. Then when page is updated, scripts url are rebuild and then inserted in the page. Rebuild url function adds the prefix (protocol + hostname given by windon.href.l.host), as webSEAL was not configured to filter application/json response, some javascript link are added twice with different url, this is causing an issue. This issue happens when tml of form contains link or when form contains mixing with @Import. Is there any solution without configuring webSEAL ? Thanks for you help -----Original Message----- From: Bosch, Christian [mailto:cbo...@cincom.com] Sent: lundi 23 novembre 2015 18:13 To: Tapestry users <users@tapestry.apache.org> Subject: Tapestry 5.3.7 and webSEAL Hello, I 'm totally stucked with a problem happening with a tapestry web application (5.3.7) accessed through a webSEAL junction (With Websphere ND 8.5.5). I have page with a complex form with a lot of components, when it is accessed without webSEAL, the page is correctly rendered. But when it is accessed through webSEAL junction, the rendering of the page is different. I have debugged the styles, the css stack is the same, but some attributes are not correctly rendered. There is no error in Tapestry log and browser log, beginning of HREF for css and js are not the same. Thanks your help. C. BOSCH. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
