[infinispan-issues] [JBoss JIRA] (ISPN-8530) Default value of "merge-policy" xsd attribute has an unstable name like org.infinispan.conflict.MergePolicies$$Lambda$72/520956294

[Dan Berindei (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489528#comment-13489528 ] 

Dan Berindei commented on ISPN-8530:
------------------------------------

The default value from XSD is only for the editor's information, the parser doesn't use it. 

Since the parser uses {{Parser.MergePolicy.toString()}} first, and only tries to parse the attribute value as a class name if it's not one of the enum values, we should make {{MergePolicies}} constants reference {{Parser.MergePolicy}} values in their {{toString()}} implementation. Or maybe merge the two...

> Default value of "merge-policy" xsd attribute has an unstable name like org.infinispan.conflict.MergePolicies$$Lambda$72/520956294
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-8530
>                 URL: https://issues.jboss.org/browse/ISPN-8530
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 9.1.0.Final
>            Reporter: Adrian Nistor
>            Assignee: Ryan Emerson
>             Fix For: 9.2.0.Final
>
>
> A different lambda name gets generated during each build.
> So an xsd created and deployed to http://docs.jboss.org/infinispan/schemas/ becomes out of sync after next build. We can fix that by redeploying the schema but we cannot assume users will always re-fetch it.
> Using static inner classes (non-anonymous) would be preferable in this case even though the lambda code looks nicer. This solution maintains backward compat with 9.1 too.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)