[
https://issues.apache.org/jira/browse/POLYGENE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443515#comment-16443515
]
Niclas Hedhman edited comment on POLYGENE-122 at 4/19/18 3:37 AM:
------------------------------------------------------------------
Need to figure out how many cases there are, and whether it is all handled by
the same piece of code.
# Construction of a Composite - *{color:#14892c}PARAMETER REPORTED{color}*
# {color:#333333}Setting Property to null on Transient{color} -
*{color:#14892c}PROPERTY NAME REPORTED{color}*
# Passing null as method argument - *{color:#14892c}PARAMETER REPORTED{color}*
# ??
was (Author: niclas):
Need to figure out how many cases there are, and whether it is all handled by
the same piece of code.
# Construction of a Composite - *{color:#14892c}PARAMETER REPORTED{color}*
# {color:#333333}Setting Property to null on Transient{color} -
# Passing null as method argument - *{color:#14892c}PARAMETER REPORTED{color}*
# ??
> Use parameter names to build better error messages on null barrier faults
> -------------------------------------------------------------------------
>
> Key: POLYGENE-122
> URL: https://issues.apache.org/jira/browse/POLYGENE-122
> Project: Polygene
> Issue Type: Improvement
> Reporter: Paul Merlin
> Priority: Major
> Fix For: 3.1.0
>
>
> Parameters to composite's methods must be non-null by default. This can be
> relaxed using the @Optional annotation.
> This issue is about producing more meaningful error messages, ie. including
> the parameter name, when a null parameter is given to a composite's method.
> See
> https://docs.oracle.com/javase/tutorial/reflect/member/methodparameterreflection.html
> for details on parameter names reflection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
