Sven Ewald

Like #51, I have a workaround: Use ` Child child = projector.projectEmptyElement("Child",Child.class);` instead of ` Child child = projector.projectEmptyDocument(Child.class);` Again, I will try to make easier working with document projections...

Yes. Can confirm that it works using the API key :-)

I added the tmp files to have the unit tests passing when the origin of the data changes. Happened with the msn weather service. Why is the .project file obsolete?...

The documentation is not good enough, obviously ;-) Maby you are looking for the `@XBDelete` annotation? Can you provice an example what kind of node should be deleted?

Ah... this is not possible right now, but I can give you an workaround: public interface Child { @XBWrite("ChildData") void setData(String data); } public interface ParentNoRootElement { @XBWrite("/*") void setChild(Child...

Really like the Spring MVC integration, cannot wait to play around with it ;-). I decided not to add JSON support to XMLBeam. But I'm already working on a separate...