[Architecture] apache-wink as a carbon component.
sanjiva at wso2.com
Sun Jan 29 19:40:21 EST 2012
On Sun, Jan 29, 2012 at 11:06 PM, Samisa Abeysinghe <samisa at wso2.com> wrote:
> Specially, the question are:
> 1. Can I just drop or upload a JAX-RS annotated class (or
> more practically a bunch of annotated classes, and their expediencies as a
> Jar) and get the REST service exposed.
> 2.Then move on to pick Basic Auth/OAusth and secure that as we do in case
> of SOAP services.
> 3. And try-it, not just with GET using current try-it, but using
> respective verbs in sych with the annotated verbs for each method, rather
> than having to use curl for verbs other than GET.
> 4. And then monitor the stats as we do with SOAP services.
> 5. And more advanced, enable/disable some of the annotated methods being
> exposed as operations using the UI, rather than having to change code.
> 6. Still advanced, can we inject annotations, using the UI to the already
> uploaded Java classes
> 7. And 7 above leads to the ability to upload a lame Jar, without
> annotations and make it JAX-RS (yes, I am dreaming, not sure if that is
> technically feasible, but my gut says yes, and that would yield the same
> value as Jar services in SOAP space)
Between 4 and 5:
4.5. Enable fine grained authorization of specific URLs using XACML
4.6. Throttle particular URLs by inserting a throttling policy like we do
with SOAP services.
So basically first get all the things "external" to the actual JAX-RS file
done first and then look at a UI that lets you edit the JAX-RS artifact in
various ways (5, 6, 7 and I'm sure more later).
Excellent list Samisa!
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanjiva at wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
Lean . Enterprise . Middleware
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Architecture