On Thu, Jun 30, 2011 at 12:18 PM, Samisa Abeysinghe <[email protected]> wrote:
> > > On Thu, Jun 30, 2011 at 12:11 PM, Senaka Fernando <[email protected]> wrote: > >> Hi Samisa, Sumedha, >> >> On Thu, Jun 30, 2011 at 11:30 AM, Samisa Abeysinghe <[email protected]>wrote: >> >>> >>> >>> On Thu, Jun 30, 2011 at 7:27 AM, Sumedha Rubasinghe <[email protected]>wrote: >>> >>>> >>>> >>>> On Thu, Jun 30, 2011 at 6:59 AM, Samisa Abeysinghe <[email protected]>wrote: >>>> >>>>> $subject? >>>>> >>>>> Can I use only HTTP style calls without SOAP with the same API? >>>>> >>>> >>>> Nope. We haven't enabled REST for the same services exposed by WS API. >>>> However, SOAP HTTP Bindings should work by default. >>>> >>> >>> Can we get HTTP style calls working with the same API - how much work >>> does that involve? >>> >> >> This is a WebService, if REST works for any other WebService deployed in >> Axis2, this is no different. IMO, we do not require any further work to get >> this to work over HTTP/REST. >> >> >>> Basically the question is along the lines of how easy I could write a >>> non-Java based client for the same API. >>> >>> As I understand, even to use WS API, with something like a .NET client, >>> we need to enable WS-Sec. https://wso2.org/jira/browse/CARBON-10934 >>> >> >> The JKS is required in order to obtain the cookie to make subsequent HTTPS >> calls. AFAIU, the Carbon Authenticators should be able to work with >> WS-Security if we are do this. >> >> Further, I recall an older discussion where Tharindu, and Chintana >> participated in getting WS API to work against a .NET client. I'm not sure >> whether they used a policy or just invoked the service. >> > > See the bottom of > http://wso2.org/project/registry/4.0.0/docs/developer_guide/ws_api.html > > "To add WS-Security for the WS-API, just name the relevant policy file as > *"ws-api-sec-policy.xml"* and place it into GREG_HOME/repository/conf. > WS-Security will now be engaged!" > > So looks like we need to add a policy. At least that is what the doc says! > The provision was made to add WS-Security IF we want. It's not mandatory, it's on a need to basis. > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Regards, Tharindu
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
