[
https://issues.apache.org/jira/browse/POLYGENE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman closed POLYGENE-122.
-----------------------------------
Resolution: Fixed
I am closing this issue, as I can't think of any other cases where this should
be reported. If there is, please open a new issue.
> 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)
