Empty XML Tag errors about tikxml HOT 7 CLOSED

Thanks for reporting, seems to be a bug ...

from tikxml.

Hm, I'm not able to reproduce this ...
See Tests added: 15fd016

Could you provide your annotated classes or even better a Unit Test with annotated classes and xml you are going to parse that shows that this is failing?

from tikxml.

When I do like

<example>
    <empty />
</example>

Java model class would be like

@Xml
public class Example {
    @PropertyElement
    String empty;
}

from tikxml.

I see your problem, obviously in such a case the <empty /> tag shouldn't appear at all in your xml file.
Nevertheless, what would be the expected result then? null or emptyString? I guess null? But if it's null, how do we represent an empty string? What if it is a primitive like Integer that doesn't have null nor empty string alike values?

In general, should we simply do nothing in such a case so that the default value will be remain (i.e. null for objects like Strings, 0 for integers, false for booleans etc.?

You see, this is harder to do right then expected. I would like to see such things fixed on backend site or whoever provides the xml file.

note to myself: also happens when:

<example>
    <empty></empty>
</example>

from tikxml.

Set default values would be best to handle this situations.

from tikxml.

The xml pull parser has also a bug when you give him something like <empty />. He is using the value from the next tag then.

from tikxml.

Parser returns now the default values like "" (empty String) for empty elements like <element></element>. For booleans false will be returned, for numbers 0.

If you want to model null values, simply don't write a empty tag in your xml file.

This fix is available in 0.5.3-SNAPSHOT

from tikxml.