Thanks NuwanD for the clarification. Yes I agree with the fact that, UX point of view its the best way to provide an UI for that.
Sorry I didn't mention the requirement behind this scenario. I'm trying to automate API deployment. So first thought of creating an ESB project to contain the sequences for the file based mediation extension. Then I ran in to a trouble because DevS + Maven plugins didn't allow the sequence names like 'API-NAME:Vversio--IN' Then I created a registry resource project and added the sequences with a standard name. It works fine now. I'm going to use the Publisher ReST API to create the API specifying the in/out sequence extensions. Please let me know if I'm doing something wrong here. Thanks Rushmin On Tue, Nov 3, 2015 at 4:05 PM, Nuwan Dias <[email protected]> wrote: > > > On Tue, Nov 3, 2015 at 2:03 AM, Rushmin Fernando <[email protected]> wrote: > >> >> Hi APIM team, >> >> The doc [1] says that the recommended way to add a mediation extension is >> the registry approach. >> >> *"The recommended way to engage a mediation extension sequence per API is >> to upload an XML file through the registry and then engage it using the API >> Publisher."* >> >> Are there any drawbacks in using the file based mediation extensions ? >> > > No drawbacks. Even when you select a sequence from the UI and publish an > API, we deploy the sequence xml in the file system. > > The reason we ask to upload to registry is because.. > > 1. It gives the opportunity for others to reuse the same sequence. > 2. Its not nice to say use the UI for API Publishing and go to the > filesystem to deploy a sequence. > 3. In most cases people don't have access to the filesystem (ex: Cloud) > > Thanks, > NuwanD. > >> >> >> Thanks >> Rushmin >> >> [1] - https://docs.wso2.com/display/AM191/Adding+Mediation+Extensions >> >> >> >> -- >> *Rushmin Fernando* >> *Technical Lead* >> >> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware >> >> email : [email protected] >> mobile : +94772310855 >> >> >> > > > -- > Nuwan Dias > > Technical Lead - WSO2, Inc. http://wso2.com > email : [email protected] > Phone : +94 777 775 729 > -- *Rushmin Fernando* *Technical Lead* WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware email : [email protected] mobile : +94772310855
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
