Hi Melan
Can't we give both datamapper-mediator and
datamapper-mediator-graphical-editor as a single feature, s.t if it is
installed only it will enable datamapper mediator in tool palatte and etc.
I feel like this is something good to have, but still i dont have much idea
of the difficulty of
+1 to put it all together - DataMapping is an integral part of creating
mediation flows . We did not decouple Smooks, why would we decouple this
one ?
Isabelle.
-
*Isabelle Mauny*
VP, Product Management; WSO2,
Hi All
I came across few dependancy resolving issues while i was trying to build
an installed-distribution pack, As i feels these issues could be eliminated
if we could think on $subject and seperate the coupling. WDYT
@ Viraj/Jasintha : Is this required or(the other alternative is) can we
simply
Hi,
I think Datamapper should be a separate feature and decouple from ESB
graphical editor.
Thanks,
Viraj.
On Mon, Apr 28, 2014 at 8:46 PM, Susinda Perera susi...@wso2.com wrote:
Hi All
I came across few dependancy resolving issues while i was trying to build
an installed-distribution
Hi,
IMO, 'adding datamapper mediator to a proxy' is equal to 'adding a sequence
mediator to a proxy'. If we haven't separate the sequence graphical editor
from ESB graphical editor, Why we needs to decouple datamapper editor ?
Thanks,
/Lali
On Tue, Apr 29, 2014 at 9:55 AM, Viraj Rajaguru
Hi Susinda,
I guess ESB graphical editor depends on data-mapper mediator, so you can
pack datamapper mediator and it's dependencies (datamapper engine,etc) with
developer studio library bundle
(org.wso2.eclipse:org.wso2.developerstudio.eclipse.libraries) and you can
keep data-mapper editor as
