+1. And for known types (eg: connection properties for a given JMS Server) we should be able give set of predefined connection properties.
/sumedha On Wed, Jun 29, 2011 at 10:25 AM, Supun Kamburugamuva <su...@wso2.com>wrote: > +1 > > This has being discussed in various instances and we couldn't do it. > > Thanks, > Supun.. > > On Wed, Jun 29, 2011 at 10:20 AM, Kasun Indrasiri <ka...@wso2.com> wrote: > >> Hi devs, >> >> As you know, in ESB we have to deal with large number of various >> properties[1] that we set using property mediators in the mediation flows. >> When it comes to designing sequences, using either the mgmt console or CS, >> new users always need to go through the property catalog and select the >> required properties.(of course with the correct value and scope). We can >> improve the usability of property mediator by giving an option to the user >> to select the predefined properties and populate them with relevant values >> and scopes. However we need to store and maintain a list of predefined >> properties of ESB to be used by the property mediator UI and CS. >> >> WDYT? >> >> [1] http://wso2.org/project/esb/java/4.0.0/docs/properties_guide.html >> >> -- >> Kasun Indrasiri >> Associate Technical Lead >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +94 71 536 4128 >> Blog : http://kasunpanorama.blogspot.com/ >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
