tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Blevins <david.blev...@visi.com>
Subject Re: A Bug in OpenEJB?
Date Thu, 10 Sep 2009 21:35:58 GMT
This is strange as the parsing is done by JAXB and the related class  
looks setup correctly:

@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "")
public class Property {

     @XmlAttribute(required = true)
     protected String name;
     @XmlAttribute(required = true)
     protected String value;

It should complain that you don't have the required attribute.

-David

On Sep 8, 2009, at 6:42 AM, Quintin Beukes wrote:

> Hey,
>
> I can reproduce it everytime. All I have to do is leave out the  
> value attribute.
>
> Q
>
> On Tue, Sep 8, 2009 at 2:06 PM, Jean-Louis MONTEIRO
> <jean-louis.monteiro@atosorigin.com> wrote:
>>
>> Hi Quintin,
>>
>> The specification only supports the second form.
>> Here is an extract from the specification:
>>                     <xsd:complexType>
>>                        <xsd:attribute name="name" type="xsd:string"
>>                                       use="required"/>
>>                        <xsd:attribute name="value" type="xsd:string"
>>                                       use="required"/>
>>                      </xsd:complexType>
>>
>>
>> Q Beukes wrote:
>>>
>>> I got the first one from an example. Can't recall where though, is  
>>> it
>>> incorrect? If I think about it I've always used the 2nd form.
>>>
>> Please, if you find it again, let us know so we can fix it.
>>
>> Thanks in advance.
>> Jean-Louis
>> --
>> View this message in context: http://www.nabble.com/Fwd%3A-A-Bug-in-OpenEJB--tp25313066p25344885.html
>> Sent from the OpenEJB User mailing list archive at Nabble.com.
>>
>>
>
>
>
> -- 
> Quintin Beukes
>


Mime
View raw message