Two things : content organization in registry & how extension is loaded by the gateway.
In registry we have in/out grouping for proper organization of content. Syntax in the name is used by the MediationExtension Handler[1]. In reality these sequences can be deployed anywhere within Synapse config. The particular registry location is being used by the API Publisher UI component. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.gateway/1.2.1/src/main/java/org/wso2/carbon/apimgt/gateway/handlers/ext/APIManagerExtensionHandler.java On Fri, Mar 28, 2014 at 11:53 AM, Subash Chaturanga <[email protected]> wrote: > Hi AM folks, > This is FMI, correct me if I am missing anything. Since we are suppose to > store these global/non-global sequences in registry under "in" and "out" > collections separately why we need that info included again in the sequence > names ? > > -- > Thanks > /subash > > *Subash Chaturanga* > Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com > > email: [email protected] > blog: http://subashsdm.blogspot.com/ > twitter: @subash89 > phone: +9477 2225922 > Lean . Enterprise . Middleware > -- /sumedha b : bit.ly/sumedha
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
