On Fri, Jun 7, 2013 at 12:38 PM, Reto Bachmann-Gmür <[email protected]> wrote: > Hello, > > I wanted to give you a quick update on the status of the commons-ng branch. > > > - The updated dependency with the biggest impact is jersey which is now > in version 2.0 which is a jax-rs 2.0 implementation. I've found no > incompatibilities between jax-rs 2.0 and 1.1 so I've broadened the import > range for the dependency.
So you plan to still stick with jersey as default jax-rs implementation? But I guess Stanbol will only use standard APIs so we can easily switch the implementation, right? > - I've also updated the scr plugin to allow dependency injections in > superclasses > - WebFragement will still be there as a deprecated class > - Accessing services and properties via ServletContext is no longer > supported (but BaseStanbolResource is still there and provide the legacy > global script/css support) > - There is an issue with the new jersey version when security is enabled > - CORS has not yet been ported, the respective classes are disabled# I would like to change CORS support in a way that developers do not need to handle this within JAX-RS resources. Maybe via a ServletFilter or something similar. > - The job manager is not yet working (missing service, probably since > scr update) > - A mini launcher shall provide the common bundle and minimum support > classes to test new modules > > To summarize what is there: You can launch the mini-launcher and access the > start page which is now powered by a jax-rs 2.0 implementation. I hope I will find some time to look into this on Sunday. Otherwise I will not have time until later next week. best Rupert > > Cheers, > Reto -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
