[jboss-jira] [JBoss JIRA] (WFLY-2471) jboss-as-infinispan_1_4.xsd differs between EAP and WildFly
Paul Ferraro (JIRA)
jira-events at lists.jboss.org
Fri Nov 8 08:20:02 EST 2013
[ https://issues.jboss.org/browse/WFLY-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921776#comment-12921776 ]
Paul Ferraro commented on WFLY-2471:
------------------------------------
As I recall (as the person who made the change), the change to the 1.4 schema was to fix a bug. As I recall, previously, the schema allowed an <invalidation-cache/> to contain a <state-transfer/> element. However, this is not allowed by either the parser or the model. So, really, assuming my recollection is correct, this fix should be backported to EAP 6.
> jboss-as-infinispan_1_4.xsd differs between EAP and WildFly
> -----------------------------------------------------------
>
> Key: WFLY-2471
> URL: https://issues.jboss.org/browse/WFLY-2471
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Reporter: Darran Lofthouse
> Assignee: Paul Ferraro
> Fix For: 8.0.0.CR1
>
>
> The schema 'jboss-as-infinispan_1_4.xsd' is not in sync between EAP and WildFly.
> For a given namespace there is supposed to be only one definition and that definition is frozen as soon as it reaches a Final release.
> The following commit affected version 1.4 of the schema in WildFly but did not make it to the EAP version: -
> https://github.com/wildfly/wildfly/commit/a9ed468bba498d55c2aa8008100f0f90140d24e8
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list