Re: [osgi-dev] Basic feedback on JAX-RS whiteboard spec

[Timothy Ward]

Also, thank you for reading the RFC and providing feedback!

I will make sure to clarify the rules around pre and post match filters.

Regards,

Tim

> On 10 Nov 2016, at 18:39, BJ Hargrave <hargr...@us.ibm.com> wrote:
> 
> As stated in the front matter of the RFC, you should provide feedback to the 
> OSGi public bugzilla system at https://osgi.org/bugzilla/ 
> <https://osgi.org/bugzilla/>.
>  
> Thanks,
>  
> --
> 
> BJ Hargrave
> Senior Technical Staff Member, IBM // office: +1 386 848 1781
> OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
> hargr...@us.ibm.com
>  
>  
> - Original message -
> From: Sergey Beryozkin <sberyoz...@gmail.com>
> Sent by: osgi-dev-boun...@mail.osgi.org
> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org>
> Cc:
> Subject: [osgi-dev] Basic feedback on JAX-RS whiteboard spec
> Date: Thu, Nov 10, 2016 12:29 PM
>  
> Hi,
> Sorry if it is not the right place to provide the feedback, I just
> wanted to share some basic feedback.
> 
> - The text is written well and is easy to understand
> - May be worth distinguishing between PreMatch and PostMatch filters -
> the former are run before a resource method has been found
> - JAX-RS 2.1 draft introduces a client support for CompletableFuture or
> other alternatives (such as RxJava) via an rx() as opposed to async()
> bridge, with an RxInvoker wrapping a specific Rx library/code.
> - The use of List in the examples - the minor issue is that it
> is generally difficult to write an interoperable code in such cases for
> XML formats - every JAX-RS 2.0 impl or List handler may have its own
> idea on what the root name is.
> 
> That is it
> Cheers, Sergey
> ___
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev 
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>  
>  
> 
> ___
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev

___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Re: [osgi-dev] Basic feedback on JAX-RS whiteboard spec

[BJ Hargrave]

As stated in the front matter of the RFC, you should provide feedback to the OSGi public bugzilla system at https://osgi.org/bugzilla/.
 
Thanks,
 
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
 
 
- Original message -From: Sergey Beryozkin Sent by: osgi-dev-boun...@mail.osgi.orgTo: OSGi Developer Mail List Cc:Subject: [osgi-dev] Basic feedback on JAX-RS whiteboard specDate: Thu, Nov 10, 2016 12:29 PM 
Hi,Sorry if it is not the right place to provide the feedback, I justwanted to share some basic feedback.- The text is written well and is easy to understand- May be worth distinguishing between PreMatch and PostMatch filters -the former are run before a resource method has been found- JAX-RS 2.1 draft introduces a client support for CompletableFuture orother alternatives (such as RxJava) via an rx() as opposed to async()bridge, with an RxInvoker wrapping a specific Rx library/code.- The use of List in the examples - the minor issue is that itis generally difficult to write an interoperable code in such cases forXML formats - every JAX-RS 2.0 impl or List handler may have its ownidea on what the root name is.That is itCheers, Sergey___OSGi Developer Mail Listosgi-dev@mail.osgi.orghttps://mail.osgi.org/mailman/listinfo/osgi-dev 
 

___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

[osgi-dev] Basic feedback on JAX-RS whiteboard spec

[Sergey Beryozkin]

Hi,
Sorry if it is not the right place to provide the feedback, I just 
wanted to share some basic feedback.


- The text is written well and is easy to understand
- May be worth distinguishing between PreMatch and PostMatch filters - 
the former are run before a resource method has been found
- JAX-RS 2.1 draft introduces a client support for CompletableFuture or 
other alternatives (such as RxJava) via an rx() as opposed to async() 
bridge, with an RxInvoker wrapping a specific Rx library/code.
- The use of List in the examples - the minor issue is that it 
is generally difficult to write an interoperable code in such cases for 
XML formats - every JAX-RS 2.0 impl or List handler may have its own 
idea on what the root name is.


That is it
Cheers, Sergey
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev