You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Vikramjit Singh (JIRA)" <ji...@apache.org> on 2012/10/07 20:54:02 UTC

[jira] [Updated] (OFBIZ-5048) Multi Part Input Parameters not Available in Groovy Event

     [ https://issues.apache.org/jira/browse/OFBIZ-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vikramjit Singh updated OFBIZ-5048:
-----------------------------------

    Attachment: GroovyEventMultipartParametes.patch

Patch for making Multi Part Parameters available in the Groovy Event Too.
                
> Multi Part Input Parameters not Available in Groovy Event
> ---------------------------------------------------------
>
>                 Key: OFBIZ-5048
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5048
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: ALL COMPONENTS
>    Affects Versions: Release Branch 11.04
>            Reporter: Vikramjit Singh
>             Fix For: Release Branch 11.04
>
>         Attachments: GroovyEventMultipartParametes.patch
>
>
> If form is of type enctype="multipart/form-data" and we are handling it's submission through Groovy Event then in the parameters Map Ofbiz does not set the multipart input parameters from request parameters.
> The same are available when multipart form submission is handled through service.
> The reason being the code that sets the multipart parameters in request attribute is only available in ServiceEventHandler.java and in GroovyEventHandler the multipart are never set. 
> So I have created a method getMultiPartParameterMap in the class UtilHttp.java and put the common logic in that method so that when getCombinedMap method is called from the GroovEventHandler the method also call getMultiPartParameterMap and in the ServiceEventHandler I have written a call for getMultiPartParameterMap method.
> I am attaching the Patch Kindly Verify the same.

--
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