For the last week I have been working on 1.3 Xuixo (another wonderful pastry originated in my hometown). The web service api is still the same, so you intrepid soul should be able to still used it without noticing the change (unless I added some funny bug, not unlikely). The main changes though are under the hood. I refactored most of the code to remove the static dependences and now you can start as many self-contained MeandreServers on your embedded usage of Meandre. This will simplify writing test cases against the web services api. I have not moved the old (1.2) web services test because they need revamping.
I have also been working on adding new tools:
- Mau files are now self contained. A mau file is a jar containing the repository rdf and all the contexts required to run (jars). This is usually generated via the ZigZag compiler or interpreter (yes, you read it right, interpreter).
- Improved the ZigZag compiler to generate the new mau file format.
- Modified the ZigZag run time to be able to run the new mau files.
- Yes, you heard it right. I added a ZigZag interpreter. Yes it comes with a console and you can build flows incrementally, merge flows together, save flows and maus, run a flow, etc, among others. Just type help on it and it will talk to you.
I finally gave up and learned ant. Yup, great news, I guess for the rest of the people :). This version (1.3) has my take to the old (1.2) build.xml. It provides the following tasks:
- compile
- compile-tests
- clean
- run-tests
- test-reports
- javadoc
- dist
No, it does not provide a run task or alike. You should not run the Meandre server there. The dist task generates the usual libraries (and a few more I added) and 4 standalone jars:
- meandre-server-X.Y.jar (Meandre server)
- zz-X.Y.jar (The ZigZag interpreter conole)
- zzc-X.Y.jar (The ZigZag compiler)
- zzre-X.Y.jar (The ZigZag runtime for MAU files)
You can run each of them by typing java -jar name.jar. So, for instance if you want to run the core, copy meandre-server-X.Y.jar to where ever you want to have the working directory and run java -jar meandre-server-X.Y.jar. That’s it, self contained and auto configured. You can stop it then and play with the config files if you want to tweak things, for instance use MySQL/Oracle instead of the embedded Derby.
As I said before, this is for intrepid souls, please let me know if you run into problems, bugs, etc. Also, jira now contains a Meandre-Terracota-Executor project, feel free to report the bugs directly to there and I will do my best to catch up.
