On Dec 11, 2009, at 9:42 PM, Tatu Saloranta wrote:
> On Fri, Dec 11, 2009 at 2:44 AM, Paul Sandoz <Paul.Sandoz_at_sun.com>
> wrote:
>>
> ...
>> BTW i also used Jackson/JAX-RS recently with a bit of Scala as i
>> did not
>> want to introduce JAXB annotations:
>>
>> http://blogs.sun.com/sandoz/entry/simple_long_polling_in_scala
>>
>> I had to do a little "code gymnastics" due do a bug (not in Jackson/
>> JAX-RS)
>> and because Jackson does not (yet???) understand Scala types such
>> as List.
>> IMHO having Scala-based support for Jackson would be really nice.
>
Some observations when using Jackson 1.3.1:
- when including the dependency on jackson-jaxrs version 1.3.1 i also
had to add the following dependency otherwise a
ClassNotFound would occur:
<dependency>
<groupId>org.codehaus.jackson</groupId>
<artifactId>jackson-xc</artifactId>
<version>1.3.1</version>
</dependency>
- there is a static dependency on JAXB. If the JAXB dependency is not
included a ClassNotFound may occur. It might be
beneficial to make JAXB a runtime dependency (or as a separate
module) as not everyone will utilize the JAXB APIs.
> Definitely. Some support has been added for various
> platform/frameworks (like ignoring of certain groovy-induced bogus
> setters/getters). I have only used Scala a little bit at work (a
> co-worker is big fan, wrote pile of unit tests in Scala), so I could
> use some help in pointing out how to tell Scala lists (and Maps, maybe
> general collections) from other objects.
> So if you (or anyone else) can help, I would definitely want to add
> support.
>
If only i have more time ! :-(
Paul.