From: James Strachan <james.strachan_at_gmail.com>
Date: Mon, 27 Apr 2009 13:15:12 +0100

As mentioned on this thread...
http://n2.nabble.com/using-Lift-templates-with-Jersey-%28was-Re%3A--Jersey--custom--TemplateProcessor-not-having-its-constructor-injected-%29-td2675518.html

I've just made my first commit (yay!) to solve this issue
https://jersey.dev.java.net/issues/show_bug.cgi?id=281

by adding a new jersey-scala library (to the contribs area) along with
an example of it in use in the samples...
https://jersey.dev.java.net/source/browse/jersey/trunk/jersey/samples/scala-helloworld-webapp/src/main/scala/com/sun/jersey/samples/helloworld/resources/MarkupResource.scala?annotate=2305

the only icky part of this is having to remember to add the
jersey-scala package to the list of packages in your web.xml (e.g.
look for the 'jersey.scala' in here on line 8...)
https://jersey.dev.java.net/source/browse/jersey/trunk/jersey/samples/scala-helloworld-webapp/src/main/webapp/WEB-INF/web.xml?annotate=2305

it would be nice to make jersey extensions & resource beans
auto-discoverable (either on OSGi via a bundle activator looking for
jersey extensions, or in non-OSGi using a META-INF/services type thing
where all Jersey extensions can be advertised using a canonical file
that Jersey can load on startup) - then just adding jersey-scala to
your classpath would be enough.
http://n2.nabble.com/-IDEA--making-resource-beans-auto-discoverable-when-making-modular--web-applications-td2389256.html#a2389256

-- 
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/