We were evaluating the possibility of using this to pull out fields in the configurations we define
i.e when we introduce a transport module we could have transport related configs/fields being identified and populated through this. On Thu, Feb 11, 2016 at 9:51 AM, Kishanthan Thangarajah <kishant...@wso2.com > wrote: > We can use this and this used within a DS component in a dynamic manner. > Can you tell me the exact use case you are trying out? > > On Wed, Feb 10, 2016 at 11:54 AM, Pamod Sylvester <pa...@wso2.com> wrote: > >> Hi All, >> >> DS 1.3 provides the capability of defining custom types for >> configurations. This might be a cleaner approach we could use to interpret >> our configurations. using @interface annotation. >> >> WDYT ? >> >> [1] http://njbartlett.name/2015/08/17/osgir6-declarative-services.html >> >> Thanks, >> Pamod >> >> -- >> *Pamod Sylvester * >> >> *WSO2 Inc.; http://wso2.com <http://wso2.com>* >> cell: +94 77 7779495 >> > > > > -- > *Kishanthan Thangarajah* > Associate Technical Lead, > Platform Technologies Team, > WSO2, Inc. > lean.enterprise.middleware > > Mobile - +94773426635 > Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* > Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>* > -- *Pamod Sylvester * *WSO2 Inc.; http://wso2.com <http://wso2.com>* cell: +94 77 7779495
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
