On 1/6/2016 4:53 PM, Mandy Chung wrote:
On Jan 6, 2016, at 4:11 PM, huizhe wang wrote:
What if “paths” is non-empty but all entries are invalid and no catalog file is
read - will it read the system property?
It will not read the system property. The assumption is that the paths
specified
> On Jan 6, 2016, at 4:11 PM, huizhe wang wrote:
>
>
>>
>> What if “paths” is non-empty but all entries are invalid and no catalog file
>> is read - will it read the system property?
>
> It will not read the system property. The assumption is that the paths
> specified are meant to be used.
Thanks Mandy. Please see inline.
On 1/4/2016 6:50 PM, Mandy Chung wrote:
On Dec 23, 2015, at 2:55 PM, huizhe wang wrote:
Hi,
This is an improvement to the new Catalog API on null handling. At the package
level, a null argument shall result in NPE. However, an exception was made to
the metho
> On Dec 23, 2015, at 2:55 PM, huizhe wang wrote:
>
> Hi,
>
> This is an improvement to the new Catalog API on null handling. At the
> package level, a null argument shall result in NPE. However, an exception was
> made to the methods in CatalogManager so that they can used conveniently.
> W
Hi,
This is an improvement to the new Catalog API on null handling. At the
package level, a null argument shall result in NPE. However, an
exception was made to the methods in CatalogManager so that they can
used conveniently. With this request, we're in favor of consistency over
the minor co