You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2016/12/01 08:24:58 UTC
[jira] [Reopened] (OFBIZ-4427) Possible runtime errors with
UtilValidate.isEmpty(Object) should be rather caught during compilation
[ https://issues.apache.org/jira/browse/OFBIZ-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Le Roux reopened OFBIZ-4427:
------------------------------------
I Paul, I agree so I reopen. BTW I forgot to mention in the title: the same is true for isNotEmpty(Object) which was introduced with OFBIZ-785. isEmpty(Object) was pre Apache era.
Will you handle the rest with a new patch?
> Possible runtime errors with UtilValidate.isEmpty(Object) should be rather caught during compilation
> ----------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-4427
> URL: https://issues.apache.org/jira/browse/OFBIZ-4427
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: Trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Priority: Minor
> Labels: UtilValidate.isEmpty
> Attachments: OFBIZ-4427.patch, OFBIZ-4427_isEmpty.patch
>
>
> Hence we need to remove the UtilValidate.isEmpty(Object) method and provide methods that accept explicit types.
> Adrian then (http://markmail.org/message/37rtrnulhmyzxfoo) suggested that
> bq. Scripting languages should use a facade class that provides methods for working with generic Objects or providing default behaviors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)