Hi Sanjeewa
On Wed, Oct 14, 2015 at 11:55 AM, Sanjeewa Malalgoda
wrote:
>
> Since we all agreed on two different services(store and publisher APIs)
> shall we conclude on data model as well.
> Do we need to have common model shared with both store,publisher and
> refine parameters at service laye
Hi,
We have been developing our own JAX-RS runtime for WSO2 Micro Services
Server (MSS). The purpose of that runtime is not to support the full JAX-RS
specification but to support a subset of the JAX-RS specification plus a
set of additional features focusing on performance and lightweightness to
Shall we also create a doc with all JAX-RS annotations, extensions and
mentioning what MSS supported and what not supported ?
Thanks !
On Thu, Oct 15, 2015 at 10:30 AM, Samiyuru Senarathne
wrote:
> Hi,
>
> We have been developing our own JAX-RS runtime for WSO2 Micro Services
> Server (MSS). Th
Sure, we will.
On Thu, Oct 15, 2015 at 10:33 AM, Sagara Gunathunga wrote:
>
> Shall we also create a doc with all JAX-RS annotations, extensions and
> mentioning what MSS supported and what not supported ?
>
> Thanks !
>
> On Thu, Oct 15, 2015 at 10:30 AM, Samiyuru Senarathne
> wrote:
>
>> Hi,
On Tue, Oct 13, 2015 at 7:45 PM, Sanjeewa Malalgoda
wrote:
> Hi All,
> We are working on complete REST complaint API for API Management
> operations in product.
> We have already discussed about design and implementation details in
> architecture mail list.
> Now we need to finalize security mode
+1. Since we are providing a subset of JAX-RC specification, we need to be
clear on what we support. Otherwise we will get into trouble later. This
got to be a public doc.
Initially we forked netty-http to process JAX-RC annotations, but later
decided to completely revamp that implementation. Can
