Hi Chanaka, With the current level of the implementation we are creating a data mapper configuration and it is saved as a registry resource in the Registry project and when we double click on the DM Mediator it should open the datamapper configuration in the DM Editor. Therefore, there should be a way for us to identify the local path of the configuration.The basic idea of introducing this property is to keep track of the local path of the datamapper configuration.
Please note that this property should not be included in the XML configuration of the DM Mediator and should not be visible as a property to the end user. Thanks, Sohani Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine On Fri, Feb 19, 2016 at 10:20 AM, Susinda Perera <[email protected]> wrote: > Hi Cahanka/Sohani et al > > We have some other options for this. > 1 - Have mapping config inline with datamapper mediator > 2 - Have mapping config as a local entry > 3 - Have mapping-config as registry-resource (as we have now) and when > opening the editor, we will try to find the mapping config (.dmc) resource > in the workspace, based on the resource path. If we find multiple entries > or if we do not find any we may give a dialog-box to chose it. > WDYT? > > Thanks > Susinda > > > On Thu, Feb 18, 2016 at 9:44 PM, Chanaka Fernando <[email protected]> > wrote: > >> Hi Sohani, >> >> Can you elaborate on the existing XML configuration of the DM mediator >> and the proposed property for this localpath? >> >> >> >> On Thu, Feb 18, 2016 at 4:09 PM, Sohani Weerasinghe <[email protected]> >> wrote: >> >>> Hi All, >>> >>> When considering the current level of the implementation of Visual >>> DataMapper Editor, following steps are needed in opening the Visual >>> DataMapper Editor >>> >>> 1. Drag and drop a DataMapper Mediator to the mediation flow (eg: Proxy) >>> 2. Double click on the Mediator, then it pop-ups a dialog to save the >>> datamapper configuration as a registry resource ( inside a Registry Project) >>> 3. Then it opens the configuration in the Visual DataMapper Editor >>> 4. After saving, you can open and view the configuration in the >>> DataMapper Editor. >>> >>> In order to open the Data Mapper Editor while double clicking on the >>> DataMapper mediator, we need to keep track on the local path of the >>> configuration (path of the registry resource inside the Registry Project). >>> >>> This property needs to be saved in the DataMapper Mediator object at the >>> time of creating the configuration (DataMapperMediatorTransformer) , so >>> that this can be retrieved when opening the >>> Editor(DataMapperMediatorDeserializer) >>> >>> Shall we introduce a new property (meta data) to the DataMapper Mediator >>> to save the localPath of the configuration? Really appreciate your input on >>> this >>> >>> Thanks, >>> Sohani >>> Sohani Weerasinghe >>> Software Engineer >>> WSO2, Inc: http://wso2.com >>> >>> Mobile : +94 716439774 >>> Blog :http://christinetechtips.blogspot.com/ >>> Twitter : https://twitter.com/sohanichristine >>> >> >> >> >> -- >> Thank you and Best Regards, >> Chanaka Fernando >> Senior Technical Lead >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 773337238 >> Blog : http://soatutorials.blogspot.com >> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >> Twitter:https://twitter.com/chanakaudaya >> >> >> >> >> > > > -- > *Susinda Perera* > Software Engineer > B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL) > Mobile:(+94)716049075 > Blog: susinda.blogspot.com > WSO2 Inc. http://wso2.com/ > Tel : 94 11 214 5345 Fax :94 11 2145300 > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
