Re: JAX-RS API version change
Hi This update is in place now, so if you're using CXF JAX-RS then please give it a try. Please note that a newer 0.6 version is already available, and from the user's perspective, upgrading to 0.6 will mean that existing @UriParam annotations will need to be replaced with @PathParam ones. It seems like the only change in 0.6 which can affect the existing user's code. 0.6 jar is not available on Maven yet, so this upgrade will be done a bit later Cheers, Sergey - Original Message - From: Sergey Beryozkin [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Friday, February 15, 2008 4:55 PM Subject: JAX-RS API version change Hi Currently, the CXF JAX-RS implementation depend upon a 0.4 version of the jaxrs-api. I'm looking into upgrading it to support a latest 0.5 version. There're some changes from 0.4 to 0.5 which would affect users. The following is the list of what has changed between 0.4 and 0.5 which will or may have an effect on the current JAX-RS applications built on top of CXF : 1. @HttpMethod annotation is no longer supported, instead @GET, @POST, @PUT and @DELETE annotations will be used 2. @UriTemplate is not longer supported, @Path is used instead 3. EntityProvider interface has gone too, instead it has been split into two interfaces, MessageBodyReader and MessageBodyWriter. If you provide custom providers and you'd like to have the same instance to handle both reads and writes, then you'd have to have its class implementing both interfaces. Existing spring configuration for injecting custom providers won't get changed, the runtime will sort difrerent types of handlers into the right lists itself... Cheers, Sergey IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Re: JAX-RS API version change
Sergey Beryozkin wrote: Hi This update is in place now, so if you're using CXF JAX-RS then please give it a try. Please note that a newer 0.6 version is already available, and from the user's perspective, upgrading to 0.6 will mean that existing @UriParam annotations will need to be replaced with @PathParam ones. It seems like the only change in 0.6 which can affect the existing user's code. 0.6 jar is not available on Maven yet, so this upgrade will be done a bit later Cheers, Sergey - Original Message - From: Sergey Beryozkin [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Friday, February 15, 2008 4:55 PM Subject: JAX-RS API version change Hi Currently, the CXF JAX-RS implementation depend upon a 0.4 version of the jaxrs-api. I'm looking into upgrading it to support a latest 0.5 version. There're some changes from 0.4 to 0.5 which would affect users. The following is the list of what has changed between 0.4 and 0.5 which will or may have an effect on the current JAX-RS applications built on top of CXF : 1. @HttpMethod annotation is no longer supported, instead @GET, @POST, @PUT and @DELETE annotations will be used 2. @UriTemplate is not longer supported, @Path is used instead 3. EntityProvider interface has gone too, instead it has been split into two interfaces, MessageBodyReader and MessageBodyWriter. If you provide custom providers and you'd like to have the same instance to handle both reads and writes, then you'd have to have its class implementing both interfaces. Existing spring configuration for injecting custom providers won't get changed, the runtime will sort difrerent types of handlers into the right lists itself... Cheers, Sergey IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland This is cool. Did you update the JAX-RS sample too? I do have a question. 0.6 started implementing a REST client API. Does CXF plan to use this Client API or do you suggesting using the HTTP Client used in samples? Thank you Arul
Re: JAX-RS API version change
Just to be clear: I do have a question. 0.6 started implementing a REST client API. Does CXF plan to use this Client API or do you suggesting using the HTTP Client used in samples? If it's part of the spec, then yes, we do plan on providing it, just probably not immediately. The server side parts are a bit higher priority to the folks that are paying us to work on it. :-) However, if folks would like to jump in and help, feel free to start raising jira issues, submit patches, etc We'd LOVE to have the extra help. Dan On Monday 25 February 2008, Sergey Beryozkin wrote: Hi, This is cool. Did you update the JAX-RS sample too? No, will do as part of the next patch, thanks for pointing it out.. I do have a question. 0.6 started implementing a REST client API. Does CXF plan to use this Client API or do you suggesting using the HTTP Client used in samples? This is not a priority for CXF JAX-RS at the moment. Yes, that Client API looks cool, but I believe it's not something CXF JAX-RS users can't live without at this moment of time :-). Things like providing a UriInfo implementation, support for types like byte[], improving the URITemplating, etc are of higher priority at the moment. Thank you Arul Cheers, Sergey IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: JAX-RS API version change
Client API It's not part of the spec (at the moment). It's something Jersey will provide Cheers, Sergey - Original Message - From: Daniel Kulp [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Monday, February 25, 2008 4:26 PM Subject: Re: JAX-RS API version change Just to be clear: I do have a question. 0.6 started implementing a REST client API. Does CXF plan to use this Client API or do you suggesting using the HTTP Client used in samples? If it's part of the spec, then yes, we do plan on providing it, just probably not immediately. The server side parts are a bit higher priority to the folks that are paying us to work on it. :-) However, if folks would like to jump in and help, feel free to start raising jira issues, submit patches, etc We'd LOVE to have the extra help. Dan On Monday 25 February 2008, Sergey Beryozkin wrote: Hi, This is cool. Did you update the JAX-RS sample too? No, will do as part of the next patch, thanks for pointing it out.. I do have a question. 0.6 started implementing a REST client API. Does CXF plan to use this Client API or do you suggesting using the HTTP Client used in samples? This is not a priority for CXF JAX-RS at the moment. Yes, that Client API looks cool, but I believe it's not something CXF JAX-RS users can't live without at this moment of time :-). Things like providing a UriInfo implementation, support for types like byte[], improving the URITemplating, etc are of higher priority at the moment. Thank you Arul Cheers, Sergey IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Re: JAX-RS API version change
Client API It's not part of the spec (at the moment). It's something Jersey will provide Oh. Ok. Well, my comment still stands. Any help adding it to CXF would be greatly appreciated. :-) Dan On Monday 25 February 2008, Sergey Beryozkin wrote: Cheers, Sergey - Original Message - From: Daniel Kulp [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Monday, February 25, 2008 4:26 PM Subject: Re: JAX-RS API version change Just to be clear: I do have a question. 0.6 started implementing a REST client API. Does CXF plan to use this Client API or do you suggesting using the HTTP Client used in samples? If it's part of the spec, then yes, we do plan on providing it, just probably not immediately. The server side parts are a bit higher priority to the folks that are paying us to work on it. :-) However, if folks would like to jump in and help, feel free to start raising jira issues, submit patches, etc We'd LOVE to have the extra help. Dan On Monday 25 February 2008, Sergey Beryozkin wrote: Hi, This is cool. Did you update the JAX-RS sample too? No, will do as part of the next patch, thanks for pointing it out.. I do have a question. 0.6 started implementing a REST client API. Does CXF plan to use this Client API or do you suggesting using the HTTP Client used in samples? This is not a priority for CXF JAX-RS at the moment. Yes, that Client API looks cool, but I believe it's not something CXF JAX-RS users can't live without at this moment of time :-). Things like providing a UriInfo implementation, support for types like byte[], improving the URITemplating, etc are of higher priority at the moment. Thank you Arul Cheers, Sergey IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
Re: JAX-RS API version change
Well, my comment still stands. Any help adding it to CXF would be greatly appreciated. :-) +1 :-) Cheers, Sergey Client API It's not part of the spec (at the moment). It's something Jersey will provide Oh. Ok. Well, my comment still stands. Any help adding it to CXF would be greatly appreciated. :-) Dan On Monday 25 February 2008, Sergey Beryozkin wrote: Cheers, Sergey - Original Message - From: Daniel Kulp [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Monday, February 25, 2008 4:26 PM Subject: Re: JAX-RS API version change Just to be clear: I do have a question. 0.6 started implementing a REST client API. Does CXF plan to use this Client API or do you suggesting using the HTTP Client used in samples? If it's part of the spec, then yes, we do plan on providing it, just probably not immediately. The server side parts are a bit higher priority to the folks that are paying us to work on it. :-) However, if folks would like to jump in and help, feel free to start raising jira issues, submit patches, etc We'd LOVE to have the extra help. Dan On Monday 25 February 2008, Sergey Beryozkin wrote: Hi, This is cool. Did you update the JAX-RS sample too? No, will do as part of the next patch, thanks for pointing it out.. I do have a question. 0.6 started implementing a REST client API. Does CXF plan to use this Client API or do you suggesting using the HTTP Client used in samples? This is not a priority for CXF JAX-RS at the moment. Yes, that Client API looks cool, but I believe it's not something CXF JAX-RS users can't live without at this moment of time :-). Things like providing a UriInfo implementation, support for types like byte[], improving the URITemplating, etc are of higher priority at the moment. Thank you Arul Cheers, Sergey IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Re: JAX-RS API version change
I've got it mostly finished, but I'm going to add few more tests before supplying a patch Cheers, Sergey - Original Message - From: Sergey Beryozkin [EMAIL PROTECTED] To: cxf-user@incubator.apache.org Sent: Friday, February 15, 2008 4:55 PM Subject: JAX-RS API version change Hi Currently, the CXF JAX-RS implementation depend upon a 0.4 version of the jaxrs-api. I'm looking into upgrading it to support a latest 0.5 version. There're some changes from 0.4 to 0.5 which would affect users. The following is the list of what has changed between 0.4 and 0.5 which will or may have an effect on the current JAX-RS applications built on top of CXF : 1. @HttpMethod annotation is no longer supported, instead @GET, @POST, @PUT and @DELETE annotations will be used 2. @UriTemplate is not longer supported, @Path is used instead 3. EntityProvider interface has gone too, instead it has been split into two interfaces, MessageBodyReader and MessageBodyWriter. If you provide custom providers and you'd like to have the same instance to handle both reads and writes, then you'd have to have its class implementing both interfaces. Existing spring configuration for injecting custom providers won't get changed, the runtime will sort difrerent types of handlers into the right lists itself... Cheers, Sergey IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
JAX-RS API version change
Hi Currently, the CXF JAX-RS implementation depend upon a 0.4 version of the jaxrs-api. I'm looking into upgrading it to support a latest 0.5 version. There're some changes from 0.4 to 0.5 which would affect users. The following is the list of what has changed between 0.4 and 0.5 which will or may have an effect on the current JAX-RS applications built on top of CXF : 1. @HttpMethod annotation is no longer supported, instead @GET, @POST, @PUT and @DELETE annotations will be used 2. @UriTemplate is not longer supported, @Path is used instead 3. EntityProvider interface has gone too, instead it has been split into two interfaces, MessageBodyReader and MessageBodyWriter. If you provide custom providers and you'd like to have the same instance to handle both reads and writes, then you'd have to have its class implementing both interfaces. Existing spring configuration for injecting custom providers won't get changed, the runtime will sort difrerent types of handlers into the right lists itself... Cheers, Sergey IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
