The following yaml documents cannot be read, but should.

--- !!org.yaml.snakeyaml.noprop.BeanHolder bean : !!org.yaml.snakeyaml.noprop.Bean1

--- !!org.yaml.snakeyaml.noprop.BeanHolder

The attached patch contains testcases that reproduce the problem.

Thank you. This is in fact not a bug but a feature request. Because {} are not used for the leaf bean SnakeYAML tries to construct a scalar. Since there is no single-argument (the empty String as the argument) constructor it fails. Nevertheless this is an interesting case. I will think how we can improve the implementation.

Question: if a Java instance is created out of following YAML document:

"!!com.package.Name" and 2 constructors are present in the Name class: no-argument constructor and with a String argument which constructor shall be used and why ?

Current situation:

"!!com.package.Name {}" - empty constructor is called

"!!com.package.Name" - constructor with an empty String is called

Comment deleted

Comment deleted

Comment deleted

Comment deleted

Fixed.

Take the latest source and check: http://code.google.com/p/snakeyaml/source/browse/src/test/java/org/yaml/snakeyaml/issu es/issue9/NopropTest.java

The support is done via a custom Constructor (BeanConstructor). We need that because there is more then 1 way to create an instance.