The problem is, JAXB generated types do not have setters for
collections, which makes SnakeYAML throw an exception
( org.yaml.snakeyaml.error.YAMLException: No JavaBean properties found
in ...)
There may be more problems with them , but this is my show stopper at
the moment.
I have two choices, trying to modify the JAXB generator to add setters
(which I would not prefer) or to convince SnakeYAML to ignore setters,
which will not be required in my use case anyway.
Is there a way of doing this?
Best regards
Seref
--
You received this message because you are subscribed to the Google Groups "SnakeYAML" group.
To view this discussion on the web visit https://groups.google.com/d/msg/snakeyaml-core/-/veAZ1DR4AZMJ.
To post to this group, send email to snakeya...@googlegroups.com.
To unsubscribe from this group, send email to snakeyaml-cor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/snakeyaml-core?hl=en.
Isn't DumpOptions.setAllowReadOnlyProperties(boolean allowReadOnlyProperties) is made for that?-alex
--
You received this message because you are subscribed to the Google Groups "SnakeYAML" group.
To view this discussion on the web visit https://groups.google.com/d/msg/snakeyaml-core/-/6MlXZdI3MQcJ.