Hi Samitha, Since this a user issue, you won't be able to directly update the RXT. However there are multiple workarounds as well. I think the best option is using the admin console to delete the RXT first and add it again.
Regards, Chandana On 29 Jan. 2018 5:31 pm, "Samitha Chathuranga" <[email protected]> wrote: > Hi Chandana, > > So that means I cannot update RXT via Asset Type management UI? > > Regards, > Samitha > > On Mon, Jan 29, 2018 at 12:21 PM, Chandana Napagoda <[email protected]> > wrote: > >> Hi Samitha, >> >> The reason for this issue is, originally your RXT was saved to the >> registry with "documentation" short name and when you are trying to update >> RXT content, it will validate the original short name with the short name >> available in the RXT content. >> >> Regards, >> Chandana >> >> On 28 January 2018 at 18:02, Samitha Chathuranga <[email protected]> >> wrote: >> >>> Hi Chandanda, >>> >>> On Sat, Jan 27, 2018 at 1:41 PM, Chandana Napagoda <[email protected]> >>> wrote: >>> >>>> Hi Samitha, >>>> >>>> If you have access to the admin console, is there any reason to update >>>> RXT content using registry instead of the Asset Type management UI? >>>> >>> There is no specific reason. >>> >>>> What is your actual requirement here? Do you want to update the RXT >>>> content without using Asset Type management UI(ex: using Java API)? >>>> >>> >>> The actual requirement is to update the RXT content via any approach. >>> I think you meant editing via, *Home > Extensions > Configure > >>> Artifact Types > Artifact Source* in management console, "Asset Type >>> management UI". But editing via this popped error alert that "Failed to >>> save the configuration. RXT short name can't be modified". >>> >>> [image: Inline image 1] >>> >>> Seems no any field in this documentation.rxt (not only short name) can >>> be modified. What I originally wanted to edit was storage path. i.e. >>> >>> <storagePath>/*appmgt*/applicationdata/provider/@{overview_api >>> BasePath}/documentation/@{overview_name}</storagePath> >>> to >>> <storagePath>/*apimgt*/applicationdata/provider/@{overview_api >>> BasePath}/documentation/@{overview_name}</storagePath> >>> >>> As editing via this approach was impossible, I updated via registry. >>> >>> Please note also the below fact I have mentioned previously. >>> >>> I tried this with wso2 cloud but not with a standalone apim pack. I just >>>> tested, this works without issues with standalone apim packs; rxt update is >>>> effected just after, without restarting, even without waiting for 15 >>>> minutes to upload after deletion. >>>> >>> >>> Thanks, >>> Samitha >>> >>> >>>> Regards, >>>> Chandana >>>> >>>> On 19 January 2018 at 18:36, Samitha Chathuranga <[email protected]> >>>> wrote: >>>> >>>>> Hi Viraj, >>>>> >>>>> Thanks for your suggestions. I tested that with WSO2 Cloud(staging), >>>>> but no luck. >>>>> >>>>> Regards, >>>>> Samitha >>>>> >>>>> On Fri, Jan 19, 2018 at 12:02 PM, Viraj Warnakulasinghe < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Samitha, >>>>>> >>>>>> I encountered previously mention issue with APIM 2.0.0. It may be >>>>>> fixed with APIM 2.1.0. Better if you could check and verify in the WSO2 >>>>>> cloud. >>>>>> >>>>>> Regards, >>>>>> Viraj >>>>>> >>>>>> On Fri, Jan 19, 2018 at 11:36 AM, Samitha Chathuranga < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> I have WSO2 APIM 2.1.0 server started and logged into management >>>>>>>> console with a tenant admin. Here I browse the registry and update a >>>>>>>> certain resource (i.e. /_system/governance/repository >>>>>>>> /components/org.wso2.carbon.governance/types/documentation.rxt). >>>>>>>> But this change seems not to effect until I restart the server. I am >>>>>>>> not >>>>>>>> certain if there is a connection with the tenant load/unload, but even >>>>>>>> waiting more than 30 mins won't reload the updated resource. >>>>>>>> >>>>>>>> Correction; I tried this with wso2 cloud but not with a standalone >>>>>>> apim pack. I just tested, this works without issues with standalone apim >>>>>>> packs; rxt update is effected just after, without restarting, even >>>>>>> without >>>>>>> waiting for 15 minutes to upload after deletion. >>>>>>> >>>>>>> @Viraj, >>>>>>> >>>>>>> Similar behavior encountered when updating in-flow mediation policy >>>>>>>> file to an API with the same name. Upload the file and have to wait 15 >>>>>>>> minutes to publish again the API in order to update the resource. This >>>>>>>> occurred due to the registry cache. >>>>>>>> Could you please try removing existing resource from the registry >>>>>>>> and wait 15 minutes until the registry cache expiration and upload the >>>>>>>> resource file and check whether the resource is updated (without >>>>>>>> restarting >>>>>>>> the server)? >>>>>>>> >>>>>>> I will try this in WSO2 cloud. >>>>>>> BTW what is the rationale behind the requirement to wait for cache >>>>>>> expiration to upload the updated file, after deleting the resource? Why >>>>>>> the >>>>>>> updated file doesn't gets reloaded after merely (without waiting for 15 >>>>>>> mins to upload after deletion) the cache expiration duration? >>>>>>> >>>>>>> Regards, >>>>>>> Samitha >>>>>>> >>>>>>> >>>>>>> On Fri, Jan 19, 2018 at 11:11 AM, Viraj Warnakulasinghe < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi Samitha, >>>>>>>> >>>>>>>> Similar behavior encountered when updating in-flow mediation policy >>>>>>>> file to an API with the same name. Upload the file and have to wait 15 >>>>>>>> minutes to publish again the API in order to update the resource. This >>>>>>>> occurred due to the registry cache. >>>>>>>> Could you please try removing existing resource from the registry >>>>>>>> and wait 15 minutes until the registry cache expiration and upload the >>>>>>>> resource file and check whether the resource is updated (without >>>>>>>> restarting >>>>>>>> the server)? >>>>>>>> >>>>>>>> Regards, >>>>>>>> Viraj >>>>>>>> >>>>>>>> On Fri, Jan 19, 2018 at 10:42 AM, Samitha Chathuranga < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I have WSO2 APIM 2.1.0 server started and logged into management >>>>>>>>> console with a tenant admin. Here I browse the registry and update a >>>>>>>>> certain resource (i.e. /_system/governance/repository >>>>>>>>> /components/org.wso2.carbon.governance/types/documentation.rxt). >>>>>>>>> But this change seems not to effect until I restart the server. I am >>>>>>>>> not >>>>>>>>> certain if there is a connection with the tenant load/unload, but even >>>>>>>>> waiting more than 30 mins won't reload the updated resource. >>>>>>>>> >>>>>>>>> Is there some caching scenario behind this? Or what is the correct >>>>>>>>> clarification for this behavior ? >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Samitha >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Samitha Chathuranga* >>>>>>>>> *Software Engineer*, *WSO2 Inc.* >>>>>>>>> lean.enterprise.middleware >>>>>>>>> Mobile: +94715123761 >>>>>>>>> >>>>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> *Viraj Warnakulasinghe* >>>>>>>> Software Engineer | WSO2 >>>>>>>> >>>>>>>> Email : [email protected] <[email protected]> >>>>>>>> Mobile : +94715538006 <+94%2071%20553%208006> >>>>>>>> Web : http://wso2.com >>>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Samitha Chathuranga* >>>>>>> *Software Engineer*, *WSO2 Inc.* >>>>>>> lean.enterprise.middleware >>>>>>> Mobile: +94715123761 >>>>>>> >>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Viraj Warnakulasinghe* >>>>>> Software Engineer | WSO2 >>>>>> >>>>>> Email : [email protected] <[email protected]> >>>>>> Mobile : +94715538006 <+94%2071%20553%208006> >>>>>> Web : http://wso2.com >>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Samitha Chathuranga* >>>>> *Software Engineer*, *WSO2 Inc.* >>>>> lean.enterprise.middleware >>>>> Mobile: +94715123761 >>>>> >>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Blog: http://blog.napagoda.com >>>> Linkedin: https://www.linkedin.com/in/chandananapagoda/ >>>> >>>> >>> >>> >>> -- >>> *Samitha Chathuranga* >>> *Software Engineer*, *WSO2 Inc.* >>> lean.enterprise.middleware >>> Mobile: +94715123761 >>> >>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>> >> >> >> >> -- >> >> Blog: http://blog.napagoda.com >> Linkedin: https://www.linkedin.com/in/chandananapagoda/ >> >> > > > -- > *Samitha Chathuranga* > *Software Engineer*, *WSO2 Inc.* > lean.enterprise.middleware > Mobile: +94715123761 > > [image: http://wso2.com/signature] <http://wso2.com/signature> >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
