You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@polygene.apache.org by "Niclas Hedhman (JIRA)" <ji...@apache.org> on 2018/04/19 03:40:00 UTC

[jira] [Assigned] (POLYGENE-122) Use parameter names to build better error messages on null barrier faults

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

Niclas Hedhman reassigned POLYGENE-122:
---------------------------------------

    Assignee: Niclas Hedhman

> 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
>            Assignee: Niclas Hedhman
>            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)