Hi, Just to note. Here are the things needs to do as per the offline chat. * CXF Intercepter for jax-rs/ws applications. * Handle application (Tomcat, CXF) context and version * db schemas for AM tables and Oauth tables. This is needed for publisher/ store to work. * Concrete use cases for both product store and applications/services store.
Kasung pls add anything I missed. On Wed, Oct 30, 2013 at 2:15 PM, Vijayaratha Vijayasingam <[email protected]>wrote: > Hi all; > > We try to make managed API capability for platform. We added this feature > for GREG in the latest release. > As a next step we try to do this in AS for axis2 services/jax-rs/webapps > etc.. > We tried the existing tomcat valve implementation for a sample jax-rs > service. > Appserver needs managed api capabilities for; > > - JAX-* services > - Axis2 services > - webapps > > The required features are; > > - Token validation for keymanager > - API store : configurable, embedded or external > - API publisher : can use the existing publisher app or, can use > jaggery APIs > - Gateway > - JAX-* - CXF valve/tomcat valve > - Axis2 services - axis2 handler > - webapps - servlet filter > > Can AS team add your thoughts on this? (what will you need,what is lacking > now, etc..) > Thanks. > > -- > -Ratha > mobile: (+94)755906608 > -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: [email protected] <[email protected]> mobile: +94 (0)71 56 91 321
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
