Folks,
I have committed the initial version of the schema of the Synapse
Configuration.
We need to do certain changes in the configuration building code to make
sure we can write a proper schema. In any case if we do any change into the
configuration factories/serializers please make sure to add the relevant
transformation to the synapse-configuration-migrator.xslt (for the moment it
is an identity transformation since we have not done any changes in the
config yet), if you do any changes without modifying the migration XSLT, we
will have to revert your commit.
That is the only way we can guarantee that we capture all the changes in the
migration tool.
Please note that the migration tool is going to be a XSLT, while we are
going to provide a XSLT invoker and a small script for it to look like a
real tool. I have committed the invoking calls, and working on a script and
including that into the build, basically you will ultimately be able to
invoke it as follows;
./configuration-migrator.sh ${path-to-the-1.x-config}
${path-to-write-the-2.x-config}
I am also planning to support a -v (verbose) mode, for the migrator.
Thanks,
Ruwan
--
Ruwan Linton
Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton
