Hi Chamila Best solution is to make the comparison case insensitive. In "implementation" field we capture if the api has a back-end endpoint or a in-line implementation via script mediator.
Regards Jo On Thu, Aug 14, 2014 at 1:04 PM, Chamila Adhikarinayake <[email protected]> wrote: > Hi > This is regarding this public jira[1]. The implementation tab is disabled > when a migrated api (from 1.6 to 1.7.1 ) is opened for editing (see image > in the jira), > > following code handles this in > /components/apimgt/api-publisher-web/1.2.3/src/site/themes/default/templates/item-design/template.jag > > var implement_wlabel = ""; > if(api && api.implementation != "ENDPOINT" ){ > implement_wlabel = "wizard-done" > } > else{ > implement_w_link = '#'; > } > > > for a migrated api, api.implementation has the value 'ENDPOINT' and for an > api created in 1.7 this value is 'endpoint'. If I remove the > 'api.implementation != "ENDPOINT"' part, I can enable the disabled tab. Is > there any specific reason for adding this part to the code or is it ok if I > remove this? > > [1] https://wso2.org/jira/browse/APIMANAGER-2662 > Thanks, > Chamila. > > -- > Regards, > Chamila Adhikarinayake > Software Engineer > WSO2, Inc. > Mobile - +94712346437 > Email - [email protected] > -- -- *Joseph Fonseka* WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 772 512 430 skype: jpfonseka * <http://lk.linkedin.com/in/rumeshbandara>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
