Hi Gabo We're planning to support JAXRS on a 2.1.x for as long as merging any new fixes won't make sense, but we're probably talking about JAXRS 2.0 may be.
There's really a very little difference between 0.8 and 1.0 API. I sent an email to a users list awhile back soliciting some feedback on whether users want 1.0 api merged into 2.1.x but no feedback followed so it's unlikely the coming 2.1.4 release will have 1.0 api support. We can eventually push 1.0 api to 2.1.x too but if some users have some JAXRS services in production then it can be a bit of pain for them to start changing ProduceMime to Produces - it won't make difference to the quality of services. So I guess we can keep 2.1.x at 0.8 api level but if people will want it they we can put 1.0 api into, say, CXF 2.1.5. At that time though it's likely 2.2 will've been released, so may be it would make sense just to keep 2.1.x with 0.8 for as long as needed, we'll see. I said in some other email that the regex stuff was part of the 1.0 api. In principle yes as 1.0 JavaDocs for say @Path talk about the regex stuff while in 0.8 it's not the case. But I see no reasons for why it can be supported on the 2.1.x line as the Path's value can accommodate the arbitrary expressions. Spring security work will unlikely have any impact - apart from us fixing whatever bugs we may find while looking at building a system test/demo. Cheers, Sergey -----Original Message----- From: Gabo Manuel [mailto:[EMAIL PROTECTED] Sent: 05 December 2008 09:50 To: [email protected] Subject: Re: [JAX-RS][PathParam] object field injection Hi Sergey, That's another thing I am a bit worried about. Which "trail"/version should I be using. It is a new project, so somewhat clean slate so to speak. Do you guys plan to support 2 (or more?) different version trails for a long time? I'm thinking of using the version which includes the changes related to this, the regex, jsr1 and that of spring security. There is not much rush at the moment to get things into production yet, so there is still some time to wait. :D > no FormParam and GenericEntity support... I don't use them at the moment so not much issue there :) Gabo
