There have been some email threads on this list about sharing configuration and code between conventional web services and JAX-RS. At the same time, we're having a bit of a debate over on the dev side. So I'm writing this message to solicit some thoughts from users.
Do you use JSON, XML, or both? If you use JSON, are you happy with it? Have you looked into jackson.codehaus.org's JSON provider? If you have an existing conventional service, and you are looking to add (or have added) JSON support, read on. How much investment do you have in data binding configuration? I'm particularly interested in Aegis. Are any of you using Aegis with an investment in .aegis.xml files or @nnotations? If so, what expectations do you have for JSON? In 2.2.x, Aegis+JAX-RS+JSON only works for fairly simple data types. Problems with namespaces and generic types cripple more complex cases. These problems would require a whole lot of effort to solve. I'm wondering, really, if all of you could just plug in Jackson and get the results you want. You might have to add some Jackson-specific @nnotations. If you are dependent on .aegis.xml files to avoid @nnotations, this would be a problem. If you have a giant raft of .aegis.xml files, or you have custom type mappings, it might be a really big problem. In which case, I wonder, ahem, if you'd like to help me implement the changes to Aegis needed. Anyhow, please let us know.
