[JIRA] Created: (MAGNOLIA-2909) POST requests to Magnolia fail if Struts filter chain is used before the Magnolia chain
|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
 |
[JIRA] Created: (MAGNOLIA-2909) POST requests to Magnolia fail if Struts filter chain is used before the Magnolia chain
by JIRA (on behalf of Jan Haderka)
::
Rate this Message:
POST requests to Magnolia fail if Struts filter chain is used before the Magnolia chain --------------------------------------------------------------------------------------- Key: MAGNOLIA-2909 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2909 Project: Magnolia Issue Type: Bug Affects Versions: 4.1.1 Environment: struts 2.1.6, tomcat 6 Reporter: Andreas Antener Assignee: Boris Kraft Attachments: stacktrace.txt, web.xml First, what are we trying to do: We have already existing applications that are using Struts and we would like to integrate them in Magnolia. The idea is to use these existing applications as paragraphs, which can be placed anywhere on the site. JSP templates came in handy to include pages that are using struts tags. We added the struts filter-dispacher and mapped him BEFORE magnolia (see attachement). From now on, struts tags get executed and they work as expected. However, the thing that does not work anymore are POST requests that are directed to Magnolia itself (meaning every Magnolia dialog / input etc.). Magnolia terminates parsing those request with the following exception: java.io.IOException: Corrupt form data: premature ending com.oreilly.servlet.multipart.MultipartParser.<init>(MultipartParser.java:205) com.oreilly.servlet.MultipartRequest.<init>(MultipartRequest.java:222) info.magnolia.cms.filters.CosMultipartRequestFilter.parseParameters(CosMultipartRequestFilter .... (see attachement for full stacktrace) I read that this could be an MultipartParser-library related incompatibility with Struts: http://stackoverflow.com/questions/240163/corrupt-form-data-premature-ending-resolved Any suggestions? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
[JIRA] Commented: (MAGNOLIA-2909) POST requests to Magnolia fail if Struts filter chain is used before the Magnolia chain
by JIRA (on behalf of Jan Haderka)
::
Rate this Message:
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24729#action_24729 ] Danilo Ghirardelli commented on MAGNOLIA-2909: ---------------------------------------------- In a similar project we used the opposite approach, having struts actions mapped as Magnolia paragraphs, and it worked out well (except that you should disable Magnolia cache for pages with struts content). If you are interested you can take a look at the code here: http://lab.openmindonline.it/lab/products/mgnlstruts.html > POST requests to Magnolia fail if Struts filter chain is used before the Magnolia chain > --------------------------------------------------------------------------------------- > > Key: MAGNOLIA-2909 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2909 > Project: Magnolia > Issue Type: Bug > Affects Versions: 4.1.1 > Environment: struts 2.1.6, tomcat 6 > Reporter: Andreas Antener > Assignee: Boris Kraft > Attachments: stacktrace.txt, web.xml > > > First, what are we trying to do: > We have already existing applications that are using Struts and we would like to integrate them in Magnolia. The idea is to use these existing applications as paragraphs, which can be placed anywhere on the site. > JSP templates came in handy to include pages that are using struts tags. We added the struts filter-dispacher and mapped him BEFORE magnolia (see attachement). > From now on, struts tags get executed and they work as expected. However, the thing that does not work anymore are POST requests that are directed to Magnolia itself (meaning every Magnolia dialog / input etc.). Magnolia terminates parsing those request with the following exception: > java.io.IOException: Corrupt form data: premature ending > com.oreilly.servlet.multipart.MultipartParser.<init>(MultipartParser.java:205) > com.oreilly.servlet.MultipartRequest.<init>(MultipartRequest.java:222) > info.magnolia.cms.filters.CosMultipartRequestFilter.parseParameters(CosMultipartRequestFilter > .... (see attachement for full stacktrace) > I read that this could be an MultipartParser-library related incompatibility with Struts: > http://stackoverflow.com/questions/240163/corrupt-form-data-premature-ending-resolved > Any suggestions? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
[JIRA] Commented: (MAGNOLIA-2909) POST requests to Magnolia fail if Struts filter chain is used before the Magnolia chain
by JIRA (on behalf of Jan Haderka)
::
Rate this Message:
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24740#action_24740 ] Andreas Antener commented on MAGNOLIA-2909: ------------------------------------------- Thank you for the hint. I had a short look into the code. Basically what you are doing is delegating the action to struts for processing in a renderer, right? In the meanwhile I tried to do something similar with a filter in the Magnolia filter chain. My filter just delegates the request to the struts dispacher. It works with post-requests if the filter is positioned after "multipartRequest". Also it was necessary to check on loops because struts calls Magnolia sites as result pages, which is why I'm not quite sure if this is the correct approach to solve it.. > POST requests to Magnolia fail if Struts filter chain is used before the Magnolia chain > --------------------------------------------------------------------------------------- > > Key: MAGNOLIA-2909 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2909 > Project: Magnolia > Issue Type: Bug > Affects Versions: 4.1.1 > Environment: struts 2.1.6, tomcat 6 > Reporter: Andreas Antener > Assignee: Boris Kraft > Attachments: stacktrace.txt, web.xml > > > First, what are we trying to do: > We have already existing applications that are using Struts and we would like to integrate them in Magnolia. The idea is to use these existing applications as paragraphs, which can be placed anywhere on the site. > JSP templates came in handy to include pages that are using struts tags. We added the struts filter-dispacher and mapped him BEFORE magnolia (see attachement). > From now on, struts tags get executed and they work as expected. However, the thing that does not work anymore are POST requests that are directed to Magnolia itself (meaning every Magnolia dialog / input etc.). Magnolia terminates parsing those request with the following exception: > java.io.IOException: Corrupt form data: premature ending > com.oreilly.servlet.multipart.MultipartParser.<init>(MultipartParser.java:205) > com.oreilly.servlet.MultipartRequest.<init>(MultipartRequest.java:222) > info.magnolia.cms.filters.CosMultipartRequestFilter.parseParameters(CosMultipartRequestFilter > .... (see attachement for full stacktrace) > I read that this could be an MultipartParser-library related incompatibility with Struts: > http://stackoverflow.com/questions/240163/corrupt-form-data-premature-ending-resolved > Any suggestions? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscribe@...> ---------------------------------------------------------------- |
| Free embeddable forum powered by Nabble | Forum Help |
