dump wrongfully omits JavaBean class name

[GoogleCodeExporter]

STEPS TO REPRODUCE:
Run BasicDumpTest.java, which generates an error.

OUTPUT OF DUMP:

!!DataSources
dataSources:
- &id001 {name: null}
- name: null
  parent: *id001
  password: null
  url: null
  username: null

EXPECTED OUTPUT:

!!DataSources
dataSources:
- &id001 !!DataSource {name: null}
- !!JDBCDataSource 
  name: null
  parent: *id001
  password: null
  url: null
  username: null

VERSION
snakeyaml 1.3

Original issue reported on code.google.com by derrick....@gmail.com on 27 Jul 2009 at 9:03

Attachments:

• BasicDumpTest.java
• DataSource.java
• DataSources.java
• JDBCDataSource.java

[GoogleCodeExporter]

Oh, and a canonical dump does this, which also seems wrong (it is explicitly
declaring the JavaBean objects as maps)

---
!!DataSources {
  ? !!str "dataSources"
  : !!seq [
    &id001 !!map {
      ? !!str "name"
      : !!null "null",
    },
    !!map {
      ? !!str "name"
      : !!null "null",
      ? !!str "parent"
      : *id001,
      ? !!str "password"
      : !!null "null",
      ? !!str "url"
      : !!null "null",
      ? !!str "username"
      : !!null "null",
    },
  ],
}

Original comment by derrick....@gmail.com on 27 Jul 2009 at 9:26

[GoogleCodeExporter]

Original comment by aso...@gmail.com on 28 Jul 2009 at 6:30

• Changed state: Accepted

[GoogleCodeExporter]

Thank you for your time. The bug is fixed. (it will be released in version 1.4)
I have extended the test you provided. You can see it here:
http://code.google.com/p/snakeyaml/source/browse/src/test/java/org/yaml/snakeyam
l/issues/issue10/BasicDumpTest.java

testTag -  your code
testTag2 - using JavaBeanDumper
testTag3 - different order. This order makes the global tag for DataSource 
redundant.

Original comment by aso...@gmail.com on 28 Jul 2009 at 8:11

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by aso...@gmail.com on 6 Aug 2009 at 10:00

• Added labels: Milestone-Release1.4