Hi all, On 9 October 2013 11:04, Shavantha Weerasinghe <shavan...@wso2.com> wrote:
> Hi All > > with the GReg pack on 8th October I was not able to login to CMIS as > per the > http://docs.wso2.org/display/Governance460/Integrate+CMIS+Client+with+WSO2+Governance+Registry > . > however, I reverted back to 3rd September pack which allowed me to > gain access to CMIS. Jira is > https://wso2.org/jira/browse/REGISTRY-2031 > CMIS is registered as a local API in GREG. It is published as an APIwith 'cmis' as the context and '1.0.0' as the version. If someone invokes cmis as, http://localhost:9764/cmis/atoms , then with embedded API Management, it is not identified as an existing resource match. The correct access url should be cmis/1.0.0/atoms. Hence we need to get this fixed. Otherwise we should not expose this as a published API through embedded api manager. Thanks, Lakmali > > > Shavantha Weerasinghe > Senior Software Engineer QA > WSO2, Inc. > lean.enterprise.middleware. > http://wso2.com > http://wso2.org > Tel : 94 11 214 5345 > Fax :94 11 2145300 > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Lakmali Baminiwatta* * Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com * *
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
