New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HDIV and Spring: nesting <spring:url> tag in Spring's form tag breaks #4
Comments
Yes, there was a problem with nested tags and the system to manage nested states. This resolves the problem in my tests. Thank you for your interest in HDIV |
Wow, that was fast! Excellent work, it fixes our problem. When do you expect a version with this fix to be released to Maven Central? |
We plan to release it in a few days |
New version 2.1.2 is in Maven Central: Regards |
hai, I am using Spring3.1 MVC with HDIV2.1.2. I go the same problem.... The log in the console is........... INFO : org.hdiv.logs.Logger - HDIV_PARAMETER_NOT_EXISTS; .................please help me. |
Hi, Regards |
Hi, Thanks for ur reply, please find the attachments org.apache.jasper.JasperException: javax.servlet.ServletException: Please give the solution..................... On Mon, Sep 17, 2012 at 5:30 PM, Gotzon Illarramendi <
Thanks & Regards, |
Hi, Thanks |
When creating a form like this:
everything works as expected, and a hidden field is appended to the form containing the CSRF token. However, when I use a
<spring:url>
tag inside the form, the hidden CSRF token is suddenly not appended to the form anymore:It seems that something is going wrong in the
DataComposerMemory
class. Because in the first situation, in thegetExtraHiddenFields
method (see https://github.com/hdiv/hdiv/blob/master/hdiv-spring-mvc/src/main/java/org/hdiv/web/servlet/support/HdivRequestDataValueProcessor.java#L150) sees true when it callsDataComposer.isRequestStarted()
, but in the second situation with the nested<spring:url>
tag, it returns false!When the
<spring:url>
tag is moved outside of the form, everything works correctly again:Therefore the nesting causes the issue it seems.
The text was updated successfully, but these errors were encountered: