iXml is an Xml Interpreter.
It is unlike anything that has been presented to the Xml community
previously, and enables you to take your Xml interogation and
manipulation to a whole new level, once I understand how to use it
most efficiently.
iXml is a UtilityClass/Bean/Ejb that allows you to control, navigate, intergoate and manipualte Xml nodes through a scripting interface or through the direct iXml Api.
There appears to be a need to control Xml on the fly, to generate it and manipulate it at run time, and everything that I have seen or considered to date seems bulky or bloated to be of any practical use. Exceptions to this are embedded RhinoScript or Object/Xml Databases with builtin scripting languages, but these too have their limitations.
In iXml you deal with Nodes within the ROOT.XML all of the time, or Nodes of Xml that do not live anywhere but in memory for the duration of their lifetime.
iXml has been implemented to a BARE minimum, and it is very VERY rough and unfinished by a long way... It revolved around a standard calling convention for Native functions, and TWO other main Native functions, RunNative, and Interpret!
To use just the Native interface you may, examples are provided to demonstate this, directly from your java.
Alternatively, you may call the Native Interpret function from your Java code and pass through an iXml script to do some work.
And finally, you do not need your own code. You may be able to do your whole App and Logic and Controller mechanisms and Input and Output and parsing or sourcing of existing file formats and datasource material all via iXml.
The iXml scripting interface need not be used, but it is the reason for continuing on with this project for so long. I am not about the standards that we are supposed to use, but more for the boundries we break when we make software born from completely new approaches and ideas!