&quot;alex.loubyansky(a)jboss.com&quot; wrote : &quot;adrian(a)jboss.org&quot; wrote : &quot;alex.loubyansky(a)jboss.com&quot; wrote : adrian wrote : Maybe there should be some kind of @JBossXmlValue | | | | annotation where we can say we want the empty string even for complex types. | | | | | | This alone doesn't make sense to me. I.e. the property could always be initialized to an empty string and if there was actual data it would override it. | | | | | | | You could have the case (not this one) where you have a mixed | | complex type and you want to know the value is "" | | | | But with that annotation the value always will be "" (unless of course there is actual text data), won't it? | The raw text data will be "", but the mixed complex type (if it is interested in it) might want to do some kind of value adapter processing on it? All I'm saying is that for a mixed complex type | <blah/> is the same as <blah></blah> | which should pass "" through the @XmlValue setter processing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172638#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...