well formed xml
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 3103
MillScript-XML 0.3
MillScript-XML is an alternative Java XML parsing library with its own custom API. more>>
MillScript-XML project is an alternative Java XML parsing library with its own custom API. The underlying tokenizer can be configured to permit non-well-formed XML.
This librarys API provides both an event model and a more conventional token stream model. The authors believe that the token stream is more friendly to applications, easier to use, and helps to minimise object creation and inter-conversion of types with the parser. A SAX2 implementation is provided for compatibility with existing applications.
In particular by making the tokenizer return Token objects instead of ints, we reduce the scope for unsupported token type creeping in. We have then implemented the visitor pattern for our Token objects, effectively bringing together the tokenizing and even style parsers into a common structure.
<<lessThis librarys API provides both an event model and a more conventional token stream model. The authors believe that the token stream is more friendly to applications, easier to use, and helps to minimise object creation and inter-conversion of types with the parser. A SAX2 implementation is provided for compatibility with existing applications.
In particular by making the tokenizer return Token objects instead of ints, we reduce the scope for unsupported token type creeping in. We have then implemented the visitor pattern for our Token objects, effectively bringing together the tokenizing and even style parsers into a common structure.
Download (0.066MB)
Added: 2007-03-26 License: GPL (GNU General Public License) Price:
942 downloads
mod_xhtml 0.9
mod_xhtml is a namespace module for XHTML (ensure W3C Appendix C) and SSI implementation. more>>
mod_xhtml is a namespace module for XHTML (ensure W3C Appendix C) and SSI implementation.
mod_xhtml provides a namespace processor for http://www.w3.org/1999/xhtml that serves to ensure XHTML meets the W3C Appendix C guidelines for compatibility with HTML browsers and the text/html MIME type. In addition, mod_xhtml implements Server Side Includes (SSI), both as Apaches comment-driven processing language and as a separate XML namespace processor.
SSI Implementation
The mod_xhtml SSI implementation is simpler than Apaches traditional mod_include, in that it decouples the task of markup parsing from SSI processing. Most importantly, as a namespace processor, it plugs directly in to general XML-based publishing systems, without the overhead of having to parse the markup twice.
mod_xhtml actually provides two ways to implement SSI:
- Using traditional comments [an error occurred while processing this directive]
- Using a separate namespace processor
The two are exactly equivalent and are implemented by the same code. They can be enabled separately or mixed in a single document.
Limitations
The principal limitation in mod_xhtml is in what it works on. Unlike mod_include, it requires its input to be well-formed XML, and cannot be used on HTML4 or tagsoup input.
The SSI implementation is also incomplete:
- The SSI exec directive is deprecated in Apache, and not implemented in mod_xhtml. - This will probably never be implemented. As in mod_include, include virtual is preferred.
- Regular expressions in expression matching are not supported. This will probably be implemented sometime in future.
<<lessmod_xhtml provides a namespace processor for http://www.w3.org/1999/xhtml that serves to ensure XHTML meets the W3C Appendix C guidelines for compatibility with HTML browsers and the text/html MIME type. In addition, mod_xhtml implements Server Side Includes (SSI), both as Apaches comment-driven processing language and as a separate XML namespace processor.
SSI Implementation
The mod_xhtml SSI implementation is simpler than Apaches traditional mod_include, in that it decouples the task of markup parsing from SSI processing. Most importantly, as a namespace processor, it plugs directly in to general XML-based publishing systems, without the overhead of having to parse the markup twice.
mod_xhtml actually provides two ways to implement SSI:
- Using traditional comments [an error occurred while processing this directive]
- Using a separate namespace processor
The two are exactly equivalent and are implemented by the same code. They can be enabled separately or mixed in a single document.
Limitations
The principal limitation in mod_xhtml is in what it works on. Unlike mod_include, it requires its input to be well-formed XML, and cannot be used on HTML4 or tagsoup input.
The SSI implementation is also incomplete:
- The SSI exec directive is deprecated in Apache, and not implemented in mod_xhtml. - This will probably never be implemented. As in mod_include, include virtual is preferred.
- Regular expressions in expression matching are not supported. This will probably be implemented sometime in future.
Download (0.044MB)
Added: 2006-04-05 License: GPL (GNU General Public License) Price:
1297 downloads
FiForms 0.9.3
FiForms started as a collection of PHP classes for creating web-based data entry screens for a MySQL database. more>>
FiForms started as a collection of PHP classes for creating web-based data entry screens for a MySQL database.
FiForms library has since grown into a collection of projects addressing many aspects of web-database development needs. The FiForms framework currently includes the FiForms data-entry classes and the FiReports XML report generation scripts.
These libraries are combined scripts which utilize the new XML capabilities of PHP version 5 to create a framework for developing web applications completely in XML languages.
The FiForms framework also includes a collection of XML Schemas for building these forms, reports, and scripts in XML.
FiForms creates a loose, modular hierarchy of PHP classes which binds HTML input boxes to fields in a MySQL database. FiForms does the work of querying the database, navigating through records, and outputting the data in HTML.
All the developer has to do is declare the objects and set a few parameters. Thus, you can create a working web database by writing less than two dozen lines of PHP script.
FiReports is a set of scripts designed to generate printable XML/HTML reports from a simple PHP or XML definition. The included stylesheets allow the user to generate custom reports in XML, submit them to the server, and receive the results from the server in XML formatted to whatever stylesheet the user requests.
<<lessFiForms library has since grown into a collection of projects addressing many aspects of web-database development needs. The FiForms framework currently includes the FiForms data-entry classes and the FiReports XML report generation scripts.
These libraries are combined scripts which utilize the new XML capabilities of PHP version 5 to create a framework for developing web applications completely in XML languages.
The FiForms framework also includes a collection of XML Schemas for building these forms, reports, and scripts in XML.
FiForms creates a loose, modular hierarchy of PHP classes which binds HTML input boxes to fields in a MySQL database. FiForms does the work of querying the database, navigating through records, and outputting the data in HTML.
All the developer has to do is declare the objects and set a few parameters. Thus, you can create a working web database by writing less than two dozen lines of PHP script.
FiReports is a set of scripts designed to generate printable XML/HTML reports from a simple PHP or XML definition. The included stylesheets allow the user to generate custom reports in XML, submit them to the server, and receive the results from the server in XML formatted to whatever stylesheet the user requests.
Download (0.17MB)
Added: 2005-12-22 License: LGPL (GNU Lesser General Public License) Price:
1402 downloads
Pod::XML 0.96
Pod::XML is a Perl module to convert POD to XML. more>>
Pod::XML is a Perl module to convert POD to XML.
SYNOPSIS
use Pod::XML;
my $parser = Pod::XML->new();
$parser->parse_from_file("foo.pod");
This module uses Pod::Parser to parse POD and generates XML from the resulting parse stream. It uses its own format, described below.
<<lessSYNOPSIS
use Pod::XML;
my $parser = Pod::XML->new();
$parser->parse_from_file("foo.pod");
This module uses Pod::Parser to parse POD and generates XML from the resulting parse stream. It uses its own format, described below.
Download (0.007MB)
Added: 2006-08-15 License: Perl Artistic License Price:
1165 downloads
ezXML 0.8.6
ezXML is a C library for parsing XML documents inspired by simpleXML for PHP. more>>
ezXML is a C library for parsing XML documents inspired by simpleXML for PHP. As the name implies, its easy to use.
Its also fast and lightweight (less than 20k compiled).
Example Usage
Given the following example XML document:
< ?xml version="1.0"?>
< formula1>
< team name="McLaren">
< driver>
< name>Kimi Raikkonen< /name>
< points>45< /points>
< /driver>
< driver>
< name>David Coultard< /name>
< points>24< /points>
< /driver>
< /team>
< /formula1>
This code snippet prints out a list of drivers, which team they drive for, and how many championship points they have:
ezxml_t f1 = ezxml_parse_file("formula1.xml"), team, driver;
const char *teamname;
for (team = ezxml_child(f1, "team"); team; team = team->next) {
teamname = ezxml_attr(team, "name");
for (driver = ezxml_child(team, "driver"); driver; driver = driver->next) {
printf("%s, %s: %sn", ezxml_child(driver, "name")->txt, teamname,
ezxml_child(driver, "points")->txt);
}
}
ezxml_free(f1);
Alternately, the following would print out the name of the second driver of the first team:
ezxml_t f1 = ezxml_parse_file("formula1.xml");
printf("%sn", ezxml_get(f1, "team", 0, "driver", 1, "name", -1)->txt);
ezxml_free(f1);
The -1 indicates the end of the argument list. Thats pretty much all there is to it. Complete API documentation can be found in ezxml.h.
Version restrictions:
- ezXML is not a validating parser.
- Loads the entire XML document into memory at once and does not allow for documents to be passed in a chunk at a time. Large XML files can still be handled though through ezxml_parse_file() and ezxml_parse_fd(), which use mmap to map the file to a virtual address space and rely on the virtual memory system to page in data as needed.
- Does not currently recognize all possible well-formedness errors. It should correctly handle all well-formed XML documents and will either ignore or halt XML processing on well-formedness errors. More well-formedness checking will be added in subsiquent releases.
- In making the character content of tags easy to access, there is no way provided to keep track of the location of sub tags relative to the character data. Example:
< doc>line one< br/>
line two< /doc>
- The character content of the doc tag is reported as "line onenline two", and < br/> is reported as a sub tag, but the location of < br/> within the character data is not. The function ezxml_toxml() will convert an ezXML structure back to XML with sub tag locations intact.
Enhancements:
- A bug was fixed in ezxml_add_child() that could occur when adding tags out of order.
- For consistency, ezxml_set_attr() now returns the tag given.
- ezxml_move() was added, along with its supporting functions ezxml_cut() and ezxml_insert().
- A bug was fixed where parsing an empty file could cause a segfault.
<<lessIts also fast and lightweight (less than 20k compiled).
Example Usage
Given the following example XML document:
< ?xml version="1.0"?>
< formula1>
< team name="McLaren">
< driver>
< name>Kimi Raikkonen< /name>
< points>45< /points>
< /driver>
< driver>
< name>David Coultard< /name>
< points>24< /points>
< /driver>
< /team>
< /formula1>
This code snippet prints out a list of drivers, which team they drive for, and how many championship points they have:
ezxml_t f1 = ezxml_parse_file("formula1.xml"), team, driver;
const char *teamname;
for (team = ezxml_child(f1, "team"); team; team = team->next) {
teamname = ezxml_attr(team, "name");
for (driver = ezxml_child(team, "driver"); driver; driver = driver->next) {
printf("%s, %s: %sn", ezxml_child(driver, "name")->txt, teamname,
ezxml_child(driver, "points")->txt);
}
}
ezxml_free(f1);
Alternately, the following would print out the name of the second driver of the first team:
ezxml_t f1 = ezxml_parse_file("formula1.xml");
printf("%sn", ezxml_get(f1, "team", 0, "driver", 1, "name", -1)->txt);
ezxml_free(f1);
The -1 indicates the end of the argument list. Thats pretty much all there is to it. Complete API documentation can be found in ezxml.h.
Version restrictions:
- ezXML is not a validating parser.
- Loads the entire XML document into memory at once and does not allow for documents to be passed in a chunk at a time. Large XML files can still be handled though through ezxml_parse_file() and ezxml_parse_fd(), which use mmap to map the file to a virtual address space and rely on the virtual memory system to page in data as needed.
- Does not currently recognize all possible well-formedness errors. It should correctly handle all well-formed XML documents and will either ignore or halt XML processing on well-formedness errors. More well-formedness checking will be added in subsiquent releases.
- In making the character content of tags easy to access, there is no way provided to keep track of the location of sub tags relative to the character data. Example:
< doc>line one< br/>
line two< /doc>
- The character content of the doc tag is reported as "line onenline two", and < br/> is reported as a sub tag, but the location of < br/> within the character data is not. The function ezxml_toxml() will convert an ezXML structure back to XML with sub tag locations intact.
Enhancements:
- A bug was fixed in ezxml_add_child() that could occur when adding tags out of order.
- For consistency, ezxml_set_attr() now returns the tag given.
- ezxml_move() was added, along with its supporting functions ezxml_cut() and ezxml_insert().
- A bug was fixed where parsing an empty file could cause a segfault.
Download (0.017MB)
Added: 2006-06-08 License: MIT/X Consortium License Price:
1237 downloads
VTD-XML 2.1
VTD-XML is a non-extractive XML processing software API implementing Virtual Token Descriptor. more>>
VTD-XML is a "non-extractive" XML processing software API implementing Virtual Token Descriptor. Currently, VTD-XML only supports built-in entity references (" &s ><<less
Download (0.64MB)
Added: 2007-06-16 License: GPL (GNU General Public License) Price:
863 downloads
Any::Renderer::XML 1.014
Any::Renderer::XML Perl module can render a data structure as element-only XML. more>>
Any::Renderer::XML Perl module can render a data structure as element-only XML.
SYNOPSIS
use Any::Renderer;
my %xml_options = ();
my %options = ( XmlOptions => %xml_options );
my $format = "XML";
my $r = new Any::Renderer ( $format, %options );
my $data_structure = [...]; # arbitrary structure code
my $string = $r->render ( $data_structure );
You can get a list of all formats that this module handles using the following syntax:
my $list_ref = Any::Renderer::XML::available_formats ();
Also, determine whether or not a format requires a template with requires_template:
my $bool = Any::Renderer::XML::requires_template ( $format );
Any::Renderer::XML renders any Perl data structure passed to it as element-only XML. For example:
perl -MAny::Renderer -e "print Any::Renderer->new(XML)->render({a => 1, b => [2,3]})"
results in:
< ?xml version="1.0" encoding="ISO-8859-1" standalone="yes"? >
< output >
< a >1< /a >
< b >2< /b >
< b >3< /b >
< /output >
The rendering process comes with all the caveats cited in the XML::Simple documentation. For example if your data structure contains binary data or ASCII control characters, then the XML document that is generated may not be well-formed.
<<lessSYNOPSIS
use Any::Renderer;
my %xml_options = ();
my %options = ( XmlOptions => %xml_options );
my $format = "XML";
my $r = new Any::Renderer ( $format, %options );
my $data_structure = [...]; # arbitrary structure code
my $string = $r->render ( $data_structure );
You can get a list of all formats that this module handles using the following syntax:
my $list_ref = Any::Renderer::XML::available_formats ();
Also, determine whether or not a format requires a template with requires_template:
my $bool = Any::Renderer::XML::requires_template ( $format );
Any::Renderer::XML renders any Perl data structure passed to it as element-only XML. For example:
perl -MAny::Renderer -e "print Any::Renderer->new(XML)->render({a => 1, b => [2,3]})"
results in:
< ?xml version="1.0" encoding="ISO-8859-1" standalone="yes"? >
< output >
< a >1< /a >
< b >2< /b >
< b >3< /b >
< /output >
The rendering process comes with all the caveats cited in the XML::Simple documentation. For example if your data structure contains binary data or ASCII control characters, then the XML document that is generated may not be well-formed.
Download (0.023MB)
Added: 2007-07-21 License: Perl Artistic License Price:
825 downloads
Modularized Information Environment 0.8.0
Modularized Information Environment (MIE) is a Web-based information management tool. more>>
Modularized Information Environment (MIE) is a Web-based information management tool designed to meet the needs of small or medium sized organizations.
Modularized Information Environment implements user authentication, storage of settings in a database, multi-lingual support and a presentation layer API that always generates well-formed XML.
<<lessModularized Information Environment implements user authentication, storage of settings in a database, multi-lingual support and a presentation layer API that always generates well-formed XML.
Download (0.36MB)
Added: 2006-10-16 License: GPL (GNU General Public License) Price:
1103 downloads
CyberNeko HTML Parser 0.9.5
NekoHTML is a simple HTML scanner and tag balancer that enables application programmers to parse HTML documents. more>>
NekoHTML is a simple HTML scanner and tag balancer that enables application programmers to parse HTML documents and access the information using standard XML interfaces.
The parser can scan HTML files and "fix up" many common mistakes that human (and computer) authors make in writing HTML documents. NekoHTML adds missing parent elements; automatically closes elements with optional end tags; and can handle mismatched inline element tags.
NekoHTML is written using the Xerces Native Interface (XNI) that is the foundation of the Xerces2 implementation. This enables you to use the NekoHTML parser with existing XNI tools without modification or rewriting code.
Version restrictions:
- There are HTML documents for which NekoHTML cannot properly generate a well-formed XML document event stream. For example, documents with multiple tags are inherently ill-formed because XML documents may only have a single root element.
- Code added to the core DOM implementation in Xerces-J 2.0.1 introduced a bug in the HTML DOM implementation based on it.
The bug causes the element nodes in the resultant HTML document object to be of type org.apache.xerces.dom.ElementNSImpl instead of the appropriate HTML DOM element objects.
The problem affects NekoHTML users who use the parser with Xerces-J 2.0.1 and anyone using the HTML DOM implementation in Xerces-J 2.0.1.
- There are no other known major limitations with this release. However, additional work can always be done to improve performance, fix bugs, and add functionality.
<<lessThe parser can scan HTML files and "fix up" many common mistakes that human (and computer) authors make in writing HTML documents. NekoHTML adds missing parent elements; automatically closes elements with optional end tags; and can handle mismatched inline element tags.
NekoHTML is written using the Xerces Native Interface (XNI) that is the foundation of the Xerces2 implementation. This enables you to use the NekoHTML parser with existing XNI tools without modification or rewriting code.
Version restrictions:
- There are HTML documents for which NekoHTML cannot properly generate a well-formed XML document event stream. For example, documents with multiple tags are inherently ill-formed because XML documents may only have a single root element.
- Code added to the core DOM implementation in Xerces-J 2.0.1 introduced a bug in the HTML DOM implementation based on it.
The bug causes the element nodes in the resultant HTML document object to be of type org.apache.xerces.dom.ElementNSImpl instead of the appropriate HTML DOM element objects.
The problem affects NekoHTML users who use the parser with Xerces-J 2.0.1 and anyone using the HTML DOM implementation in Xerces-J 2.0.1.
- There are no other known major limitations with this release. However, additional work can always be done to improve performance, fix bugs, and add functionality.
Download (0.38MB)
Added: 2005-09-28 License: The Apache License Price:
1486 downloads
CGI::FormMagick 0.89
CGI::FormMagick is a Perl module to easily create CGI form-based applications. more>>
CGI::FormMagick is a Perl module to easily create CGI form-based applications.
SYNOPSIS
use CGI::FormMagick;
my $f = new CGI::FormMagick();
# all options available to new()
my $f = new CGI::FormMagick(
type => file,
source => $myxmlfile,
);
# other types available
my $f = new CGI::FormMagick(type => string, source => $data );
$f->display();
FormMagick is a toolkit for easily building fairly complex form-based web applications. It allows the developer to specify the structure of a multi-page "wizard" style form using XML, then display that form using only a few lines of Perl.
<<lessSYNOPSIS
use CGI::FormMagick;
my $f = new CGI::FormMagick();
# all options available to new()
my $f = new CGI::FormMagick(
type => file,
source => $myxmlfile,
);
# other types available
my $f = new CGI::FormMagick(type => string, source => $data );
$f->display();
FormMagick is a toolkit for easily building fairly complex form-based web applications. It allows the developer to specify the structure of a multi-page "wizard" style form using XML, then display that form using only a few lines of Perl.
Download (0.074MB)
Added: 2006-10-07 License: Perl Artistic License Price:
1112 downloads
MARC::XML 0.4
MARC::XML is a subclass of MARC.pm to provide XML support. more>>
MARC::XML is a subclass of MARC.pm to provide XML support.
SYNOPSIS
use MARC::XML;
#read in some MARC and output some XML
$myobject = MARC::XML->new("marc.mrc","usmarc");
$myobject->output({file=>">marc.xml",format=>"xml"});
#read in some XML and output some MARC
$myobject = MARC::XML->new("marc.xml","xml");
$myobject->output({file=>">marc.mrc","usmarc");
MARC::XML is a subclass of MARC.pm which provides methods for round-trip conversions between MARC and XML. MARC::XML requires that you have the CPAN modules MARC.pm and XML::Parser installed in your Perl library. Version 1.04 of MARC.pm and 2.27 of XML::Parser (or later) are required. As a subclass of MARC.pm a MARC::XML object will by default have the full functionality of a MARC.pm object. See the MARC.pm documentation for details.
The XML file that is read and generated by MARC::XML is not associated with a Document Type Definition (DTD). This means that your files need to be well-formed, but they will not be validated. When performing XML->MARC conversion it is important that the XML file is structured in a particular way. Fortunately, this is the same format that is generated by the MARC->XML conversion, so you should be able to be able to move your data easily between the two formats.
<<lessSYNOPSIS
use MARC::XML;
#read in some MARC and output some XML
$myobject = MARC::XML->new("marc.mrc","usmarc");
$myobject->output({file=>">marc.xml",format=>"xml"});
#read in some XML and output some MARC
$myobject = MARC::XML->new("marc.xml","xml");
$myobject->output({file=>">marc.mrc","usmarc");
MARC::XML is a subclass of MARC.pm which provides methods for round-trip conversions between MARC and XML. MARC::XML requires that you have the CPAN modules MARC.pm and XML::Parser installed in your Perl library. Version 1.04 of MARC.pm and 2.27 of XML::Parser (or later) are required. As a subclass of MARC.pm a MARC::XML object will by default have the full functionality of a MARC.pm object. See the MARC.pm documentation for details.
The XML file that is read and generated by MARC::XML is not associated with a Document Type Definition (DTD). This means that your files need to be well-formed, but they will not be validated. When performing XML->MARC conversion it is important that the XML file is structured in a particular way. Fortunately, this is the same format that is generated by the MARC->XML conversion, so you should be able to be able to move your data easily between the two formats.
Download (0.050MB)
Added: 2007-07-17 License: Perl Artistic License Price:
830 downloads
RocketSled 0.4
RocketSled is a full featured, object-oriented, Web-based application development framework for PHP 5. more>>
RocketSled is a object-oriented, full featured, Web-based application development framework for PHP 5.
Its packages include Active Record and Object Relational Mapping, an advanced XML-based templating language, and a multi-user management suite.
Main features:
- Completely Object Orientated
- Flexible program structure
- Package-centric applications for easy re-deployment
- Integrated XML based templating language (RSML)
- XML based form validation engine (FormML)
- Does not require database for basic install
- Extra packages (currently 2 available) for ActiveRecord and user management
- ActiveRecord package with automated data tainting and universal pagination
- MIT License
Enhancements:
- All packages are now included in the same CVS repository for more basic version numbering, and the system has increased in stability and is more mature.
- It has also had numerous bugfixes and feature enhancements.
- Although the documentation is still very lacking, there is a Getting Started tutorial that will hopefully allow people to start looking at the framework more seriously.
<<lessIts packages include Active Record and Object Relational Mapping, an advanced XML-based templating language, and a multi-user management suite.
Main features:
- Completely Object Orientated
- Flexible program structure
- Package-centric applications for easy re-deployment
- Integrated XML based templating language (RSML)
- XML based form validation engine (FormML)
- Does not require database for basic install
- Extra packages (currently 2 available) for ActiveRecord and user management
- ActiveRecord package with automated data tainting and universal pagination
- MIT License
Enhancements:
- All packages are now included in the same CVS repository for more basic version numbering, and the system has increased in stability and is more mature.
- It has also had numerous bugfixes and feature enhancements.
- Although the documentation is still very lacking, there is a Getting Started tutorial that will hopefully allow people to start looking at the framework more seriously.
Download (0.20MB)
Added: 2007-03-16 License: MIT/X Consortium License Price:
952 downloads
ObjectBox o:XML Compiler 1.1.7
ObjectBox o:XML Compiler is an o:XML compiler and interpretor. more>>
ObjectBox is a free, opensource o:XML compiler and interpretor written entirely in Java. ObjectBox o:XML Compiler implements The o:XML Programming Language specification, and provides a complete compilation and runtime environment.
Main features:
- Java extensions - o:XML procedure that converts any Java class/object to an o:XML type for seamless language integration, making existing Java classes instantly available for instantiation and subtyping as any other o:XML type.
- Java Servlet support for deployment in J2EE environments.
- Caching of compiled programs allowing threadsafe concurrent execution.
- Commandline executable that passes arguments to o:XML program.
- Java Ant task for powerful content generation and integration in XML publishing systems.
Before compilation the program file is parsed and validated for well-formedness. The result of compiling a program is an object hierarchy of actions, that will produce the program result as a sequential output to either a DOM tree, output stream or a SAX content handler.
In order to obtain a complete and fully valid XML document, the program must terminate successfully. However all o:XML programs dont necessarily terminate - see the Fibonacci Series for an example of a program that generates an infinite, unbroken XML stream.
A compiled o:XML program contains all parsed o:Path expressions and XML-generating objects. It is thread-safe and can execute concurrently in different runtime environments, producing output to different result handlers. The program in its compiled form is independent of the XML file it was generated from as well as the physical form of its output.
Version restrictions:
- Access Specifiers (public/private/protected) not fully implemented
- Context Node probably not always correct
Enhancements:
- Integration with the Spring 2.0 framework.
- Allows for the creation of o:XML beans in Spring 2.0.
- Full integration with support for XML schema configuration, and the ability to mix and match beans: o:XML, Java, JRuby, Groovy, Beanshell, etc.
<<lessMain features:
- Java extensions - o:XML procedure that converts any Java class/object to an o:XML type for seamless language integration, making existing Java classes instantly available for instantiation and subtyping as any other o:XML type.
- Java Servlet support for deployment in J2EE environments.
- Caching of compiled programs allowing threadsafe concurrent execution.
- Commandline executable that passes arguments to o:XML program.
- Java Ant task for powerful content generation and integration in XML publishing systems.
Before compilation the program file is parsed and validated for well-formedness. The result of compiling a program is an object hierarchy of actions, that will produce the program result as a sequential output to either a DOM tree, output stream or a SAX content handler.
In order to obtain a complete and fully valid XML document, the program must terminate successfully. However all o:XML programs dont necessarily terminate - see the Fibonacci Series for an example of a program that generates an infinite, unbroken XML stream.
A compiled o:XML program contains all parsed o:Path expressions and XML-generating objects. It is thread-safe and can execute concurrently in different runtime environments, producing output to different result handlers. The program in its compiled form is independent of the XML file it was generated from as well as the physical form of its output.
Version restrictions:
- Access Specifiers (public/private/protected) not fully implemented
- Context Node probably not always correct
Enhancements:
- Integration with the Spring 2.0 framework.
- Allows for the creation of o:XML beans in Spring 2.0.
- Full integration with support for XML schema configuration, and the ability to mix and match beans: o:XML, Java, JRuby, Groovy, Beanshell, etc.
Download (0.88MB)
Added: 2007-03-26 License: GPL (GNU General Public License) Price:
949 downloads
eXcavator 1.0.6
eXcavator is an XML query processing class for PHP. more>>
eXcavator is an XML query processing class for PHP. Queries are constructed using a small query language, and query results are returned as either loosely formed or strict XML, in formats suitable for both text and HTML.
One of eXcavators most useful features is its facility to insert query results into user-defined templates, which allow for a free interpolation of user text and the data extracted by the query. eXcavator runs on top of XML_PullParser, but uses a completely independent API. However, it does offer opportunities to use the facilities of both packages side by side for programmers familiar with both.
<<lessOne of eXcavators most useful features is its facility to insert query results into user-defined templates, which allow for a free interpolation of user text and the data extracted by the query. eXcavator runs on top of XML_PullParser, but uses a completely independent API. However, it does offer opportunities to use the facilities of both packages side by side for programmers familiar with both.
Download (0.047MB)
Added: 2006-11-03 License: GPL (GNU General Public License) Price:
1088 downloads
E/AS Automation Solutions 0.2.0
E/AS Automation Solutions is open source software system for help automate your solutions even for personal or corporate ones. more>>
E/AS Automation Solutions is open source software system for help automate your solutions even for personal and/or corporate ones.
E/AS written on CLIP language (CA-Clipper dialect, compiler can be obtained from ITK.ru) and uses CODB (CLIP Object Database) as data storage.
Main features:
- client-server technology (both data and interface forms)
- component infrastructure with interaction between components by messages
- interface forms on XML
- MDI
E/AS contains in typical distribution:
- client software written on clip-ui library
- server software with wrapper for run as daemon
- maintenance tools: CODB console and component manager
- base (form, auth) and example (contact) components
Enhancements:
- completely rewrite code for implement E/AS architecture
- component infrastructure
- own server program instead COBRA
- maintenance tools: CODB console and component manager
- base and example components
- autoupdate views
<<lessE/AS written on CLIP language (CA-Clipper dialect, compiler can be obtained from ITK.ru) and uses CODB (CLIP Object Database) as data storage.
Main features:
- client-server technology (both data and interface forms)
- component infrastructure with interaction between components by messages
- interface forms on XML
- MDI
E/AS contains in typical distribution:
- client software written on clip-ui library
- server software with wrapper for run as daemon
- maintenance tools: CODB console and component manager
- base (form, auth) and example (contact) components
Enhancements:
- completely rewrite code for implement E/AS architecture
- component infrastructure
- own server program instead COBRA
- maintenance tools: CODB console and component manager
- base and example components
- autoupdate views
Download (0.060MB)
Added: 2005-11-15 License: GPL (GNU General Public License) Price:
1440 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above well formed xml search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed