This is a conscious choice. In our GitHub home page we have mentioned that only a subset is supported.
On Tue, Mar 8, 2016 at 3:37 PM, Asanka Vithanage <asan...@wso2.com> wrote: > > Hi All, > > Currently MSF4J do support few annotations as listed on [1]. They seams to > be look like JAX-RS annotations. > Even while using annotations we do imports like > import javax.ws.rs.GET; > import javax.ws.rs.POST; > import javax.ws.rs.PUT; > import javax.ws.rs.Path; > > So users may tend to think we do support JAX-RS annotations(Personally > myself tend believe the same). But we are supporting only few annotations > and not all the JAX-RS annotations[2]. > Basically we haven't fully implemented JAX-RS spec [2] and heard that we > are not going to do that in future as well. > So I believe we should update our documentation to clarify about this > situation. > WDYT? > > Further AFAIU with this approach Developers will loose the freedom to use > other JAX-RS implementations like Jersey as well. Hence Devs wont be able > to use other JAX-RS annotations for their developments. > Do we have any workaround or solution to overcome this situation. > > > [1] https://docs.wso2.com/display/MSF4J100/Key+Concepts > [2] https://jax-rs-spec.java.net/nonav/2.0-rev-a/apidocs/index.html > > -- > Asanka Vithanage > Senior Software Engineer -QA > Mobile: +94 0716286708 > Email: asan...@wso2.com > WSO2 Inc. www.wso2.com > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>* *email: **az...@wso2.com* <az...@wso2.com> * cell: +94 77 3320919blog: **http://blog.afkham.org* <http://blog.afkham.org> *twitter: **http://twitter.com/afkham_azeez* <http://twitter.com/afkham_azeez> *linked-in: **http://lk.linkedin.com/in/afkhamazeez <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
