Not to throw a wrench in anyone's plans, but I hope Jersey 2.0
isn't rushed out the door. Let's knock out as many feature requests that
break backwards compatibility and be 100% sure that end up with a sound
design before making this release.
Out of curiosity, which 2.0-specific features are you looking
forward to use?
Gili
On 07/01/2013 2:15 AM, Vikram Jit Singh wrote:
> Hi,
>
> I am currently in the process of evaluating a RESTful framework for a
> project of mine which needs to go out in production in April-May. I am
> very much interested in some of the features which are available in
> JAX-RS 2.0 since I can find use-cases to make good use of them and
> hence am very much inclined in using JAX-RS 2.0. My other choice would
> be Play framework, which is although a tad different from the
> ecosystem that JAX-RS belongs too and hence I would like to first
> clarify some of my doubts which are as follows:
>
> * Is it a good idea to use Jersey 2.0 for a project to be put in
> production mode in April-May using the current monthly builds and
> keeping them updated?
> * When is Jersey 2.0 full going to be released? (Taking into
> consideration the JAX-RS 2.0 spec timeline it may be around
> April-May I guess)
> * Currently Jersey 2.0 does not implement the Viewable feature,
> which is a very important feature for my use-case and probably
> makes Jersey 2.0 unusable for me without custom implementations.
> What is the roadmap for including it? Is there any other
> alternative for the meantime?
>
> I will be obliged if you can answer my doubts as soon as possible.
>
> Regards.
> Vikram.
>
>