Hey all,
I've been reading through the following resources, and I can not seem to
find a reference to the 'best practice' to handle plugin-specific
configuration files.
http://wiki.pentaho.org/display/EAI/...ho+Data+Integr
ation+Plug-In
http://wiki.pentaho.org/display/COM/PDI+Plugin+Loading
To be more precise, having an External Plugin read and write XML or
Property files from it's own folder. The usecase that I have is for
multiple common defaults that may change/get added frequently that the
UI can load from the config files. These configs are plugin specific,
not job/transformation specific.
KETTLE_HOME\plugins\<steps|jobentries>\mypluginfolder
\myplugin.jar
\plugin.xml
\data1-mypluginconfig.xml
\data2-mypluginconfig.xml
\mypluginconfig.properties
I started investigating using the KettleVFS (to at least re-use that
piece), but before I got too far I wanted to verify this does not
already exist (and if someone has any pointers).
My personal intent is to replicate the XML-version of the Plugin's Meta
as one of the 'common defaults' that could be quickly re-loaded from the
UI, as well as save as a common default using the same XML format.
Thanks,
-D
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "kettle-developers" group.
To post to this group, send email to kettle-developers (AT) googlegroups (DOT) com
To unsubscribe from this group, send email to kettle-developers-unsubscribe (AT) g...oups (DOT) com
For more options, visit this group at http://groups.google.com/group/kettle-developers?hl=en
-~----------~----~----~----~------~----~------~--~---