FormService.SubmitFormData should accept null

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2011 02:26 PM
It would be good if FormService.SubmitFormData and SubmitTaskData can accept null as a parameter to the Map<String, String>.
Reason:
If I have a cdi scoped bean filled up from a jsf form. I just need a trigger to put the waiting task to move forward.
under these circumstances one has to really create an Instance of Map and send it empty thereby consuming unnecessary memory.
But if the Submit methods of FormService can check for the existence of null it can just ignore and trigger the task to move forward.
I may be wrong but I have to do this time and again.
Reason:
If I have a cdi scoped bean filled up from a jsf form. I just need a trigger to put the waiting task to move forward.
under these circumstances one has to really create an Instance of Map and send it empty thereby consuming unnecessary memory.
But if the Submit methods of FormService can check for the existence of null it can just ignore and trigger the task to move forward.
I may be wrong but I have to do this time and again.
Labels:
- Labels:
-
Archive
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2011 03:49 PM
I agree it could be a convenience, but are you seriously concerned about this map using memory?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-05-2011 02:29 AM
Seriously?
Use Collections.EMPTY_MAP -> this is already consuming memory… Or create your own map-implementing singleton that consumes even LESS memory
Use Collections.EMPTY_MAP -> this is already consuming memory… Or create your own map-implementing singleton that consumes even LESS memory


Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-28-2011 03:26 PM
But it does not harm checking for an existence of a null value , since many a time we may not be interested in sending those
string data types in the Map, when we already have facilities from activiti like spring beans and cdi beans.
string data types in the Map, when we already have facilities from activiti like spring beans and cdi beans.
