I had the same experience, it looked like JvYaml was the preferred library but JYaml seems usable and has much better docs. However, it's support for different input/output methods, particularly streams and readers/writers, needs some work, as I had to do things like:
instead of using the proper APIs. Also, I had to write my own simple stream chunking, as the JYaml code didn't appear to be working. However, the complete lack of docs for JvYaml, as well as its dormant state, makes it way less attractive. On the other hand, it is a 1.1 compliant parser, which is possibly why the Yaml home page points to it. There's nothing on the JYaml page that says what version of Yaml it supports, which probably means it's still 1.0. (Someone please correct any of my statements as I am still very new to Yaml.)
At one time there was mention of JYaml on the YAML website, however it
is no longer mentioned but JvYaml seems to have been added instead as
current projects. However, the last release of JvYaml is Sept. 2006,
which doesn't seem like a current project, whereas the last release of
JYaml is Sept. 2007.
1. Why isn't JYaml mentioned any more?
2. What is the development status of JvYaml? Is it being
3. What is the Yaml implementation of choice for Java?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
IRS Circular 230 Disclosure:
Please be advised that any discussion of U.S. tax matters contained within this communication (including any attachments) is not intended or written to be used and cannot be used for the purpose of (i) avoiding U.S. tax related penalties or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Yaml-core mailing list