Hi Sanjiva, Yes, We dont need Jersey for this REST service. It will be on top of MSF4J.
Regards, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +94777688882 On Sat, Feb 27, 2016 at 11:39 AM, Sanjiva Weerawarana <[email protected]> wrote: > Hemika why do you have Jersey? From C5 onwards we are doing JAX-RS but > rather MSF4J microservices. > > On Wed, Feb 24, 2016 at 6:24 PM, Hemika Kodikara <[email protected]> wrote: > >> Hi All, >> >> We are planning move all MB admin services which was supported through >> web services to REST services. >> >> The proposed REST services will built on top of org.wso2.msf4j.feature >> feature along with Jersey. The REST service component will reside alongside >> with the broker in the andes bundle(the broker bundle). Implying that the >> REST service component and the andes broker will be in the same bundle. >> Having the REST component in a separate bundle would not make sense as the >> services rely on the broker and would not work independently. >> >> The main resources in MB are the queues, topics, durable topics and their >> subscriptions. All these resources will be exposed through REST services. >> The UI for MB will be using the REST services when managing MB resources. >> >> So far the security aspect(authorization/authentication) of these service >> are yet to be decided. >> >> Work done so far : >> 1. Integrated msf4j feature to MB product. >> 2. Created a mock REST service which gets the existing queues from the >> broker. >> >> Features proposed : >> 1. Filtering mechanism through query params. >> Example : GET /queues?fields=name,messageCount >> 2. Pagination for collection(lists) resources. >> Example : GET /queues?offset=50&limit=25 >> 3. Support JSON only. >> >> Concerns : >> 1. Would we need versioning for this REST service ? Version to be >> embedded in the url. >> 2. The naming convention for the URLs ? To use underscore or hyphen. >> Currently facebook and twitter are using underscore [2]. >> >> The proposed URLs for the REST services are available at [1]. Only the >> services from 3.1.0 are added to this list. >> >> Feedback is appreciated. >> >> [1] - >> https://docs.google.com/a/wso2.com/spreadsheets/d/1xO40gjTNhQgJnmz7_xZcue1FtQ14IlSdFI0jFIwnsF0/edit?usp=sharing >> [2] - http://stackoverflow.com/a/8738518 >> >> >> Regards, >> Hemika >> >> Hemika Kodikara >> Software Engineer >> WSO2 Inc. >> lean . enterprise . middleware >> http://wso2.com >> >> Mobile : +94777688882 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, CEO & Chief Architect; WSO2, Inc.; http://wso2.com/ > email: [email protected]; office: (+1 650 745 4499 | +94 11 214 5345) > x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311 > blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
