+1 It would be great to simplify the options available for property lookup. I think this would increase the usability of our product. I am also concerned about customers migrating their existing xml code.
In order to gain performance by moving away from get-property, would customers need to revise all their use of these mediators? I support deprecating the get-property from the UI wizard and Dev Studio, but it would also be great to revise the get-property implementation for future versions. In other words, would it be possible to change the get-property implementation so that proxies, APIs and sequences could be migrated forward without change, and still use the more efficient scoped-style efficient implementation? This would prevent the registry performance hit, and prevent the necessity for customers to modify all their xml code. Thanks, Colin Roy-Ehri Software Engineer *WSO2, Inc. : wso2.com <http://wso2.com/>* *Mobile* : 812-219-6517 On Wed, Jun 17, 2015 at 2:41 AM, Kasun Indrasiri <ka...@wso2.com> wrote: > Hi, > > It seems we can get rid of the usage of get-property and stick to the > usage of scope variable declarations only (the current impl of get-property > function always triggers a call to ESB registry interface, which can be a > performance hit). > > For example we can use: > > $ctx, $trp etc to get required property values from the context. > @Nadeeshan : we need to include $registry: as well. > > Any other use cases that we need to cover? > > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
