Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Extend Xalan-J to Process Any Data Format From XSLT

Extend Xalan-J to Process Any Data Format From XSLT

2005-11-15       - By Stylus Studio

[announce]Dear Xalan-J Users,

Stylus Studio 2006 XML Deployment Adapters are high-performance Java
components that provide bi-directional, programmatic access to
virtually any data source (relational, EDI, flat files, and more) as
XML. They make it possible to seamlessly stream non-XML data as XML to
XML processing components, including Apache's Xalan XSLT Processor,
and the Saxon XSLT and XQuery Processors, enabling developers to write
XQuery or XSLT stylesheets that read and write to non-XML data sources
as if they were XML files on the local file system. Learn more about
XML Deployment adapters at: http://www.stylusstudio.com/deployment/

Using Stylus Studio 2006 XML Enterprise Edition XML IDE, developers
can generate the Java application code required to run these data
integration applications and deploy them to any Java environment with
the click of a button. Stylus Studio 2006 XML Deployment Adapters are
a powerful and innovative approach to solving data integration
challenges involving different data sources including flat files,
relational databases, EDI (EDIFACT and X12), XML databases, Web
services, and many other file systems and data repositories.

Stylus Studio 2006 XML Deployment Adapters are available today for
$1000 (USD) per CPU, and provide access to:

* Flat Files and File Systems: Access to hundreds of common file
formats (CSV, dBase, TSV, and others); XML databases (Mark Logic
Content Interaction Server, Berkeley DB XML, TigerLogic XDMS, and
more); and File systems (WebDAV, HTTP and FTP servers, and even live
Web service data)
* Relational Databases: Integrate most relational databases including
Oracle 8i (8.1.6 and 8.1.7) and Oracle 9i (R1-R2); Microsoft SQL
Server 7 and 2000; Informix 9.2 (2000), 9.3, and 9.4; Sybase ASE 11,
12, and 12.5; IBM DB2 UDB 6.1, 7.x, and 8.1 for Windows, Unix, Linux,
and OS/390; and DB2 UDB V4R5, V5R1 for iSeries (AS/400)
* EDIFACT and X12 EDI Legacy: Out-of-the-box read and write access to
EDIFACT and X12 EDI Message types. Or customize with Stylus Studio
2006 XML Enterprise Edition.

To get started using Deployment Adapters, simply download a free trial
of Stylus Studio 2006 XML Enterprise Edition at:
http://www.stylusstudio.com/xml_download.html

Sincerely,
The Stylus Studio Team
http://www.stylusstudio.com