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 2017/06/19 01:56:02 UTC

[jira] [Commented] (POLYGENE-265) Use method parameter names if present in Constraint Violation reporting.

    [ https://issues.apache.org/jira/browse/POLYGENE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053395#comment-16053395 ] 

Niclas Hedhman commented on POLYGENE-265:
-----------------------------------------

Also doing a general improvement in the ConstraintViolationException, especially to make it more readable to people.

It now looks like this by default; 

org.apache.polygene.api.constraint.ConstraintViolationException: 
	Constraint Violation(s) in service LegalService with id=[null].
		@Optional(not optional) on WillItem.description(). Parameter [description] does not allow value [null].

and variants on that.

> Use method parameter names if present in Constraint Violation reporting.
> ------------------------------------------------------------------------
>
>                 Key: POLYGENE-265
>                 URL: https://issues.apache.org/jira/browse/POLYGENE-265
>             Project: Polygene
>          Issue Type: Bug
>            Reporter: Niclas Hedhman
>            Assignee: Niclas Hedhman
>
> In Polygene we have the @Name annotation to put parameter names on method arguments, and we generate a synthetic name (paramN) if it is not present. But an intermediate step would be to use the name available via the "-parameters" compile option if used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)