Issue Type: Bug Bug
Assignee: Marvin Kerkhoff
Attachments: Screen Shot 2014-11-05 at 12.19.39.png, Screen Shot 2014-11-05 at 12.24.03.png, Screen Shot 2014-11-05 at 12.35.48.png
Created: 05/Nov/14 12:36 PM
Description:

In our project the Form2dbProcessor fails to work. The issue seems to be that not all of the form parameters can be transformed into Magnolia properties using PropertyUtil.setProperty. This results in a IllegalArgumentException which is run time exception and is not caught or logged anywhere so is completely lost.

When I look at the list of form parameters there a couple of 'internal / system' parameters not set by our code but I guess by the Magnolia Form Module itself which cannot be converted into properties. The first one of these is a parameter called '_FreeMarkerServlet.Request_'. I have no idea why these parameters are set but I guess this is an internal Magnolia Form Module thing. See screenshots attached.

I guess the solution would be to either first check if a parameter value is of a supported type and if not skip it, or catch the IllegalArgumentException specifically for the call to PropertyUtil.setProperty but that seems a bit dirty to me.

Our form in this case is a (somewhat) custom form that extends from the default /modules/form/templates/components/form. Nothing special there. See screenshot of the form component model configuration. We use Magnolia 5.3.4.

I can hardly imagine that the processor does work for plain Magnolia 5.3.4 forms? I will check.

Project: Form2DB
Priority: Neutral Neutral
Reporter: Edgar Vonk
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to