[infinispan-dev] 4.2.ALPHA4 contains errors in schema

[Sanne Grinovero]

Hi,
I can confirm that the currently created schema is fine, working from
branch 4.2.
Not sure what happened during the release process.

Cheers,
Sanne

2010/10/25 Manik Surtani <manik at jboss.org>:
> Vladimir,
>
> Can you confirm that building off the branch generates the correct schema?
>
> Cheers
> Manik
>
> On 25 Oct 2010, at 06:46, Vladimir Blagojevic wrote:
>
>> Proper schema is the one that contains strictPeerToPeer as an attribute. StrictPerToPeer was annotated with @XMLElement but I corrected it a few days before the release to @XMLAttribute. And it built fine just as it is now. Not sure how it ended up in the release!!!
>> On 2010-10-24, at 6:49 PM, Sanne Grinovero wrote:
>>
>>> Hello all,
>>> I was successfully using 4.2.0-SNAPSHOT before the ALPHA4, and I'm
>>> also successful in using it just after the release,
>>> but if I try pinning the version to 4.2.0-ALPHA4 my builds fail with
>>> "Caused by: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2:
>>> Attribute 'strictPeerToPeer' is not allowed to appear in element
>>> 'transport'."
>>>
>>> Indeed the schema included in the release doesn't include the new
>>> "strictPeerToPeer" attribute, but lists it in the sequence, as the
>>> properties (see below).
>>>
>>> Strange thing is that versions I tested just before the release where
>>> fine, and the schema I get when building it now from 4.2 branch are
>>> also correct.
>>>
>>> 4.2.0-ALPHA4 contains:
>>>
>>> <xs:complexType name="transportType">
>>>   <xs:complexContent>
>>>     <xs:extension base="tns:abstractConfigurationBeanWithGCR">
>>>       <xs:sequence>
>>>         <xs:element name="properties" type="tns:propertiesType"
>>> minOccurs="0"/>
>>>         <xs:element name="strictPeerToPeer" type="xs:boolean" minOccurs="0"/>
>>>       </xs:sequence>
>>>       <xs:attribute name="clusterName" type="xs:string"/>
>>>       <xs:attribute name="distributedSyncTimeout" type="xs:long"/>
>>>       <xs:attribute name="nodeName" type="xs:string"/>
>>>       <xs:attribute name="transportClass" type="xs:string"/>
>>>     </xs:extension>
>>>   </xs:complexContent>
>>> </xs:complexType>
>>>
>>> 4.2.0-SNAPSHOT (correct):
>>>
>>> <xs:complexType name="transportType">
>>>   <xs:complexContent>
>>>     <xs:extension base="tns:abstractConfigurationBeanWithGCR">
>>>       <xs:sequence>
>>>         <xs:element name="properties" type="tns:propertiesType"
>>> minOccurs="0"/>
>>>       </xs:sequence>
>>>       <xs:attribute name="clusterName" type="xs:string"/>
>>>       <xs:attribute name="distributedSyncTimeout" type="xs:long"/>
>>>       <xs:attribute name="nodeName" type="xs:string"/>
>>>       <xs:attribute name="strictPeerToPeer" type="xs:boolean"/>
>>>       <xs:attribute name="transportClass" type="xs:string"/>
>>>     </xs:extension>
>>>   </xs:complexContent>
>>> </xs:complexType>
>>>
>>> any idea of how this could happen?
>>> Having this schema makes Alpha4 unusable for me.
>>>
>>> Cheers,
>>> Sanne
>>> _______________________________________________
>>> infinispan-dev mailing list
>>> infinispan-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>> --
>> Vladimir Blagojevic
>> JBoss Clustering Team
>> JBoss, by Red Hat
>>
>>
>>
>>
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
> --
> Manik Surtani
> manik at jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
>
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>