Download xalan java
Author: c | 2025-04-24
For more information, go to Xalan-Java Overview, Xalan-Java Downloads, Getting Started with Interpretive Processing and Getting Started with XSLTC. All of the Xalan-Java documentation on this website is included in the Xalan-Java download, as are a number of Samples to help you start using Xalan-Java to transform XML documents.
xalan-java/xalan/pom.xml at master apache/xalan-java - GitHub
One PDF. The EMF files are memory-based and will be deleted from memory after the successful generation of the PDF file. During the PDF generation process, an "Appeon" folder (containing a "NativePDF" sub-folder which contains a "Log" and a "Temp" sub-folders) will be generated in the temporary directory; the temporary files in these folders will be deleted after the PDF file is created but the folders will be kept for future use. For how to set PDFLib as the default PDF method and the other properties, see the section called “Saving as PDF using NativePDF! method with PDFlib” in Users Guide. Using the Apache FO processor If your application uses the Apache processor to save as PDF or XSL-FO, you must deploy the fop-0.20.4 directory and the Java Runtime Environment (JRE) with your application. They must be deployed in the same directory as the PowerBuilder runtime files. For example, if you deploy your application and pbvm.dll and the other PowerBuilder runtime files in a directory called MyApplication, the Apache processor must be deployed in MyApplication/fop-0.20.4, and the JRE in MyApplication/jre. However, you do not need to place a copy of the JRE in this location if the full JDK is installed on the target computer and is in the classpath. The following JAR files must be in the user's classpath: fop-0.20.4\build\fop.jar fop-0.20.4\lib\batik.jar fop-0.20.4\lib\xalan-2.3.1.jar fop-0.20.4\lib\xercesImpl-2.1.0.jar fop-0.20.4\lib\xml-apis.jar fop-0.20.4\lib\avalon-framework-cvs-20020315.jar For more information about the JRE, see Java support. On Windows DBCS platforms, you also need to deploy a file that supports DBCS characters
ASF: Xalan-Java - Apache Xalan
EsProc provides its own JDBC driver to become integration-friendly with a Java application. The method of calling an esProc SPL script is similar to the execution of SQL queries and stored procedures in Java.Deploying esProc JDBC in a Java applicationSimply put, to deploy JDBC in a Java application is to put in place the necessary jars and configuration files for loading esProc when starting the application. esProc JDBC requires JDK 1.8 or a higher version.1. Load driver jarsesProc JDBC is like a database JDBC driver without physical tables. It can be regarded simply as a database that only supports the stored procedure. It has a built-in computing engine that can perform all calculations independently. A database’s JDBC, however, functions only as an interface and an extra standalone server is needed to perform calculations.esProc JDBC has two basic jars, which are all situated in [installation directory]\esProc\lib. With a web application project, these jars can be put in WEB-INF\lib.esproc-bin-xxxx.jar //esProc computing engine and JDBC drivericu4j-60.3.jar //Handle internationalizationBesides, there are jars for fulfilling specific functionalities:To use databases as the data sources in esProc JDBC, their driver jars are required.To read and write an Office file, poi*.jar and xmlbeans-4.0.0.jar are needed.To use the graphic function in esProc JDBC, jars for SVG-typed image processing are required, including batik*.jar, js-1.0.jar, pdf-transcoder-1.0.jar, xalan-2.7.0.jar, xercesImpl-2.12.1.jar, xml-apis-xerces-2.7.1.jar and xml-apis-ext-2.5.0.jar.2. Configure raqsoftConfig.xmlraqsoftConfig.xml is an important configuration file for deploying esProc JDBC, which is located in [installation directory]\esProc\config. It should be copied and placed in the class path of the application project, and its name must not be changed.The raqsoftConfig.xml file contains esProc main path, dfx file’s search path, and etc.Java invocationThe following explains how to call a SPL script from Java.Execute SPL queriesCreate a data table consisting of two fields – baseNum (a natural number less than or equal to 100) and square2 (the number’s square), insert 100 records into it, and return the data as result set.Java code: 1 ) { System.out.print("\t"); } else{ System.out.print("\n"); } System.out.print(title); } while(rs.next()) { for(int c = 1; c 1 ) { System.out.print("\t"); } else { System.out.print("\n"); } Object o = rs.getObject(c); System.out.print(o.toString()); } } //Close the connection if(con!=null) { con.close(); }"> public void runSPL() throws ClassNotFoundException, SQLException{ Connection con = null; PreparedStatement st; ResultSet set ; //Establish a connection Class.forName("com.esproc.jdbc.InternalDriver"); con= DriverManager.getConnection("jdbc:esproc:local://"); // Execute the SPL statement and return result set st = (PreparedStatement)con.createStatement(); ResultSet rs = st.executeQuery("=100.new(~:baseNum,~*~:square2)"); // Output field namesapache/xalan-java: Apache Xalan-Java - GitHub
Download Java JDK 23.0.2 (64-bit) Date released: 22 Jan 2025 (one month ago) Download Java JDK 23.0.1 (64-bit) Date released: 16 Oct 2024 (5 months ago) Download Java JDK 23 (64-bit) Date released: 18 Sep 2024 (6 months ago) Download Java JDK 22.0.1 (64-bit) Date released: 17 Apr 2024 (11 months ago) Download Java JDK 22 (64-bit) Date released: 19 Mar 2024 (one year ago) Download Java JDK 21.0.2 (64-bit) Date released: 18 Jan 2024 (one year ago) Download Java JDK 21.0.1 (64-bit) Date released: 18 Oct 2023 (one year ago) Download Java JDK 21 (64-bit) Date released: 24 Sep 2023 (one year ago) Download Java JDK 20.0.2 (64-bit) Date released: 19 Jul 2023 (one year ago) Download Java JDK 20.0.1 (64-bit) Date released: 19 Apr 2023 (one year ago) Download Java JDK 19.0.2 (64-bit) Date released: 20 Jan 2023 (2 years ago) Download Java JDK 19.0.1 (64-bit) Date released: 19 Oct 2022 (2 years ago) Download Java JDK 19.0.0.0 (64-bit) Date released: 22 Sep 2022 (3 years ago) Download Java JDK 18.0.2.1 (64-bit) Date released: 19 Aug 2022 (3 years ago) Download Java JDK 18.0.2 (64-bit) Date released: 20 Jul 2022 (3 years ago) Download Java JDK 18.0.1.1 (64-bit) Date released: 03 May 2022 (3 years ago) Download Java JDK 18.0.1 (64-bit) Date released: 20 Apr 2022 (3 years ago) Download Java JDK 18 (64-bit) Date released: 29 Mar 2022 (3 years ago) Download Java JDK 17.0.4 (64-bit) Date released: 20 Jul 2022 (3 years ago) Download Java JDK 17.0.3 (64-bit) Date released: 20 Apr 2022 (3 years ago). For more information, go to Xalan-Java Overview, Xalan-Java Downloads, Getting Started with Interpretive Processing and Getting Started with XSLTC. All of the Xalan-Java documentation on this website is included in the Xalan-Java download, as are a number of Samples to help you start using Xalan-Java to transform XML documents. For more information, go to Xalan-Java Overview, Xalan-Java Downloads, Getting Started with Interpretive Processing and Getting Started with XSLTC. All of the Xalan-Java documentation on this website is included in the Xalan-Java download, as are a number of Samples to help you start using Xalan-Java to transform XML documents. Apachexalan-java/README at master apache/xalan-java - GitHub
When parsing. format-space This is the number of tabulationused when formatting a document. By default 1. format-replaceAmp If true, an entity & isgenerated for each & character in text or attribute value format-replaceGt if true, an entity > isgenerated for each format-replaceLt if true, an entity < isgenerated for each > character in text or attribute value format-replaceApos if true, an entity ' isgenerated for each ' character in text or attribute value format-replaceQuote if true, an entity " isgenerated for each " character in text or attribute value transformer This is the default JAXPtransformer for XSLT. The default value is XALAN else it must be avalid class name. default-encoding This is the encoding inside the XML declaration. This isuseful when creating a new XML document. W3C XML Schema prefix This is the default prefix whengenerating a new W3C XML Schema from the current document. - xpath Name Usage maxVariables This is the maximum number ofXPath variables the user can manage inside its expression. maxNamespaces This is the maximum number ofXPath namespaces the user can manage inside its expression. - xslt Name Usage parameter This is the maximum number ofXSLT parameters - docbookEach preference will be available after at least one docbook usage forthe specified output type.Here a sample for HTML and PDF. Name Usage htmlstylesheet Path for the XSL documents forthe HTML output pdfstylesheet Path for the XSL documents forthe PDF output Note that the path is relative to the editix installation directory andis located inside the resdirectory.b. Installing a newXML ParserClick on the item 'install a custom parser' inside the Options menu.Add your java Jar(s), click on the button Search a JAXP class. If aclass name appears under the class name field your JAXP parser isfound. You may also enter manually the JAXP class name and check withthe bound button. Press OK and the parser is enabled the next time yourestart EditiX.Another option :You can install another JAXP compatible parser inside EditiX replacingthe default one (Xerces 2.6.2). You must : Copy inside the EDITIX_INSTALL_DIRECTORY/ext/parser directoryyour jar file(s) Modify the xmlconfig / parser preference with your JAXP SAXParserfactory class Restart EditiXFor information the default SAXParser factory has the value "XERCES"which is equal to "org.apache.xerces.jaxp.SAXParserFactoryImpl".c. Installing a newXSLT TransformerClick on the item 'install a custom transformer' inside the Optionsmenu. Add your java Jar(s), click on the button Search a JAXP class. Ifa class name appears under the class name field your JAXP transformerisfound. You may also enter manually the JAXP class name and check withthe bound button. Press OK and the transformer is enabled the next timeyourestart EditiX.Another possibility :You can install another JAXP compatible XSLT Transformer inside EditiXreplacing the default one (Saxon 6.5). You must : Copy inside theASF: Xalan-Java Overview - Apache Xalan
Used when creating a newdocument from a template address This is used when creating a newdocument from a template - tree Name Usage font This is the font for the treetext selection This is the color of the treeselection text This is the color of the treetext background This is the color of the treebackground - xmlconfig Name Usage xinclude Add xinclude support whenparsing a document. By default activated. parser This is the default JAXP parser.The default value is XERCES, else it must be a valid class name. namespaceAware By default activated, it willcheck for namespace validity when parsing. format-space This is the number of tabulationused when formatting a document. By default 1. format-replaceAmp If true, an entity & isgenerated for each & character in text or attribute value format-replaceGt if true, an entity > isgenerated for each format-replaceLt if true, an entity < isgenerated for each > character in text or attribute value format-replaceApos if true, an entity ' isgenerated for each ' character in text or attribute value format-replaceQuote if true, an entity " isgenerated for each " character in text or attribute value transformer This is the default JAXPtransformer for XSLT. The default value is XALAN else it must be avalid class name. default-encoding This is the encoding inside the XML declaration. This isuseful when creating a new XML document. W3C XML Schema prefix This is the default prefix whengenerating a new W3C XML Schema from the current document. - xpath Name Usage maxVariables This is the maximum number ofXPath variables the user can manage inside its expression. maxNamespaces This is the maximum number ofXPath namespaces the user can manage inside its expression. - xslt Name Usage parameter This is the maximum number ofXSLT parameters - docbookEach preference will be available after at least one docbook usage forthe specified output type.Here a sample for HTML and PDF. Name Usage htmlstylesheet Path for the XSL documents forthe HTML output pdfstylesheet Path for the XSL documents forthe PDF output Note that the path is relative to the editix installation directory andis located inside the resdirectory.b. Installing a newXML ParserClick on the item 'install a custom parser' inside the Options menu.Add your java Jar(s), click on the button Search a JAXP class. If aclass name appears under the class name field your JAXP parser isfound. You may also enter manually the JAXP class name and check withthe bound button. Press OK and the parser is enabled the next time yourestart EditiX.Another option :You can install another JAXP compatible parser inside EditiX replacingthe default one (Xerces 2.6.2). You must : Copy inside the EDITIX_INSTALL_DIRECTORY/ext/parser directoryyour jar file(s) Modify the xmlconfig / parser preference with your JAXP SAXParserfactory class Restart EditiXFor information the default SAXParser factory has the value "XERCES"which is equal to "org.apache.xerces.jaxp.SAXParserFactoryImpl".c. Installing a newXSLT TransformerClick on the item 'install a custom transformer' inside the Optionsmenu. Add your java Jar(s), click on the button Search a JAXP class. Ifa class name appears under the class name field your JAXP transformerisfound.ASF: Xalan-Java Samples - Apache Xalan
Download Java JDK 23.0.2 (64-bit) Date released: 22 Jan 2025 (one month ago) Download Java JDK 23.0.1 (64-bit) Date released: 16 Oct 2024 (5 months ago) Download Java JDK 23 (64-bit) Date released: 18 Sep 2024 (6 months ago) Download Java JDK 22.0.1 (64-bit) Date released: 17 Apr 2024 (11 months ago) Download Java JDK 22 (64-bit) Date released: 19 Mar 2024 (12 months ago) Download Java JDK 21.0.2 (64-bit) Date released: 18 Jan 2024 (one year ago) Download Java JDK 21.0.1 (64-bit) Date released: 18 Oct 2023 (one year ago) Download Java JDK 21 (64-bit) Date released: 24 Sep 2023 (one year ago) Download Java JDK 20.0.2 (64-bit) Date released: 19 Jul 2023 (one year ago) Download Java JDK 20.0.1 (64-bit) Date released: 19 Apr 2023 (one year ago) Download Java JDK 19.0.2 (64-bit) Date released: 20 Jan 2023 (2 years ago) Download Java JDK 19.0.1 (64-bit) Date released: 19 Oct 2022 (2 years ago) Download Java JDK 19.0.0.0 (64-bit) Date released: 22 Sep 2022 (2 years ago) Download Java JDK 18.0.2.1 (64-bit) Date released: 19 Aug 2022 (3 years ago) Download Java JDK 18.0.2 (64-bit) Date released: 20 Jul 2022 (3 years ago) Download Java JDK 18.0.1.1 (64-bit) Date released: 03 May 2022 (3 years ago) Download Java JDK 18.0.1 (64-bit) Date released: 20 Apr 2022 (3 years ago) Download Java JDK 18 (64-bit) Date released: 29 Mar 2022 (3 years ago) Download Java JDK 17.0.4 (64-bit) Date released: 20 Jul 2022 (3 years ago) Download Java JDK 17.0.3 (64-bit) Date released: 20 Apr 2022 (3 years ago). For more information, go to Xalan-Java Overview, Xalan-Java Downloads, Getting Started with Interpretive Processing and Getting Started with XSLTC. All of the Xalan-Java documentation on this website is included in the Xalan-Java download, as are a number of Samples to help you start using Xalan-Java to transform XML documents. For more information, go to Xalan-Java Overview, Xalan-Java Downloads, Getting Started with Interpretive Processing and Getting Started with XSLTC. All of the Xalan-Java documentation on this website is included in the Xalan-Java download, as are a number of Samples to help you start using Xalan-Java to transform XML documents. ApacheComments
One PDF. The EMF files are memory-based and will be deleted from memory after the successful generation of the PDF file. During the PDF generation process, an "Appeon" folder (containing a "NativePDF" sub-folder which contains a "Log" and a "Temp" sub-folders) will be generated in the temporary directory; the temporary files in these folders will be deleted after the PDF file is created but the folders will be kept for future use. For how to set PDFLib as the default PDF method and the other properties, see the section called “Saving as PDF using NativePDF! method with PDFlib” in Users Guide. Using the Apache FO processor If your application uses the Apache processor to save as PDF or XSL-FO, you must deploy the fop-0.20.4 directory and the Java Runtime Environment (JRE) with your application. They must be deployed in the same directory as the PowerBuilder runtime files. For example, if you deploy your application and pbvm.dll and the other PowerBuilder runtime files in a directory called MyApplication, the Apache processor must be deployed in MyApplication/fop-0.20.4, and the JRE in MyApplication/jre. However, you do not need to place a copy of the JRE in this location if the full JDK is installed on the target computer and is in the classpath. The following JAR files must be in the user's classpath: fop-0.20.4\build\fop.jar fop-0.20.4\lib\batik.jar fop-0.20.4\lib\xalan-2.3.1.jar fop-0.20.4\lib\xercesImpl-2.1.0.jar fop-0.20.4\lib\xml-apis.jar fop-0.20.4\lib\avalon-framework-cvs-20020315.jar For more information about the JRE, see Java support. On Windows DBCS platforms, you also need to deploy a file that supports DBCS characters
2025-04-16EsProc provides its own JDBC driver to become integration-friendly with a Java application. The method of calling an esProc SPL script is similar to the execution of SQL queries and stored procedures in Java.Deploying esProc JDBC in a Java applicationSimply put, to deploy JDBC in a Java application is to put in place the necessary jars and configuration files for loading esProc when starting the application. esProc JDBC requires JDK 1.8 or a higher version.1. Load driver jarsesProc JDBC is like a database JDBC driver without physical tables. It can be regarded simply as a database that only supports the stored procedure. It has a built-in computing engine that can perform all calculations independently. A database’s JDBC, however, functions only as an interface and an extra standalone server is needed to perform calculations.esProc JDBC has two basic jars, which are all situated in [installation directory]\esProc\lib. With a web application project, these jars can be put in WEB-INF\lib.esproc-bin-xxxx.jar //esProc computing engine and JDBC drivericu4j-60.3.jar //Handle internationalizationBesides, there are jars for fulfilling specific functionalities:To use databases as the data sources in esProc JDBC, their driver jars are required.To read and write an Office file, poi*.jar and xmlbeans-4.0.0.jar are needed.To use the graphic function in esProc JDBC, jars for SVG-typed image processing are required, including batik*.jar, js-1.0.jar, pdf-transcoder-1.0.jar, xalan-2.7.0.jar, xercesImpl-2.12.1.jar, xml-apis-xerces-2.7.1.jar and xml-apis-ext-2.5.0.jar.2. Configure raqsoftConfig.xmlraqsoftConfig.xml is an important configuration file for deploying esProc JDBC, which is located in [installation directory]\esProc\config. It should be copied and placed in the class path of the application project, and its name must not be changed.The raqsoftConfig.xml file contains esProc main path, dfx file’s search path, and etc.Java invocationThe following explains how to call a SPL script from Java.Execute SPL queriesCreate a data table consisting of two fields – baseNum (a natural number less than or equal to 100) and square2 (the number’s square), insert 100 records into it, and return the data as result set.Java code: 1 ) { System.out.print("\t"); } else{ System.out.print("\n"); } System.out.print(title); } while(rs.next()) { for(int c = 1; c 1 ) { System.out.print("\t"); } else { System.out.print("\n"); } Object o = rs.getObject(c); System.out.print(o.toString()); } } //Close the connection if(con!=null) { con.close(); }"> public void runSPL() throws ClassNotFoundException, SQLException{ Connection con = null; PreparedStatement st; ResultSet set ; //Establish a connection Class.forName("com.esproc.jdbc.InternalDriver"); con= DriverManager.getConnection("jdbc:esproc:local://"); // Execute the SPL statement and return result set st = (PreparedStatement)con.createStatement(); ResultSet rs = st.executeQuery("=100.new(~:baseNum,~*~:square2)"); // Output field names
2025-04-01When parsing. format-space This is the number of tabulationused when formatting a document. By default 1. format-replaceAmp If true, an entity & isgenerated for each & character in text or attribute value format-replaceGt if true, an entity > isgenerated for each format-replaceLt if true, an entity < isgenerated for each > character in text or attribute value format-replaceApos if true, an entity ' isgenerated for each ' character in text or attribute value format-replaceQuote if true, an entity " isgenerated for each " character in text or attribute value transformer This is the default JAXPtransformer for XSLT. The default value is XALAN else it must be avalid class name. default-encoding This is the encoding inside the XML declaration. This isuseful when creating a new XML document. W3C XML Schema prefix This is the default prefix whengenerating a new W3C XML Schema from the current document. - xpath Name Usage maxVariables This is the maximum number ofXPath variables the user can manage inside its expression. maxNamespaces This is the maximum number ofXPath namespaces the user can manage inside its expression. - xslt Name Usage parameter This is the maximum number ofXSLT parameters - docbookEach preference will be available after at least one docbook usage forthe specified output type.Here a sample for HTML and PDF. Name Usage htmlstylesheet Path for the XSL documents forthe HTML output pdfstylesheet Path for the XSL documents forthe PDF output Note that the path is relative to the editix installation directory andis located inside the resdirectory.b. Installing a newXML ParserClick on the item 'install a custom parser' inside the Options menu.Add your java Jar(s), click on the button Search a JAXP class. If aclass name appears under the class name field your JAXP parser isfound. You may also enter manually the JAXP class name and check withthe bound button. Press OK and the parser is enabled the next time yourestart EditiX.Another option :You can install another JAXP compatible parser inside EditiX replacingthe default one (Xerces 2.6.2). You must : Copy inside the EDITIX_INSTALL_DIRECTORY/ext/parser directoryyour jar file(s) Modify the xmlconfig / parser preference with your JAXP SAXParserfactory class Restart EditiXFor information the default SAXParser factory has the value "XERCES"which is equal to "org.apache.xerces.jaxp.SAXParserFactoryImpl".c. Installing a newXSLT TransformerClick on the item 'install a custom transformer' inside the Optionsmenu. Add your java Jar(s), click on the button Search a JAXP class. Ifa class name appears under the class name field your JAXP transformerisfound. You may also enter manually the JAXP class name and check withthe bound button. Press OK and the transformer is enabled the next timeyourestart EditiX.Another possibility :You can install another JAXP compatible XSLT Transformer inside EditiXreplacing the default one (Saxon 6.5). You must : Copy inside the
2025-04-14Used when creating a newdocument from a template address This is used when creating a newdocument from a template - tree Name Usage font This is the font for the treetext selection This is the color of the treeselection text This is the color of the treetext background This is the color of the treebackground - xmlconfig Name Usage xinclude Add xinclude support whenparsing a document. By default activated. parser This is the default JAXP parser.The default value is XERCES, else it must be a valid class name. namespaceAware By default activated, it willcheck for namespace validity when parsing. format-space This is the number of tabulationused when formatting a document. By default 1. format-replaceAmp If true, an entity & isgenerated for each & character in text or attribute value format-replaceGt if true, an entity > isgenerated for each format-replaceLt if true, an entity < isgenerated for each > character in text or attribute value format-replaceApos if true, an entity ' isgenerated for each ' character in text or attribute value format-replaceQuote if true, an entity " isgenerated for each " character in text or attribute value transformer This is the default JAXPtransformer for XSLT. The default value is XALAN else it must be avalid class name. default-encoding This is the encoding inside the XML declaration. This isuseful when creating a new XML document. W3C XML Schema prefix This is the default prefix whengenerating a new W3C XML Schema from the current document. - xpath Name Usage maxVariables This is the maximum number ofXPath variables the user can manage inside its expression. maxNamespaces This is the maximum number ofXPath namespaces the user can manage inside its expression. - xslt Name Usage parameter This is the maximum number ofXSLT parameters - docbookEach preference will be available after at least one docbook usage forthe specified output type.Here a sample for HTML and PDF. Name Usage htmlstylesheet Path for the XSL documents forthe HTML output pdfstylesheet Path for the XSL documents forthe PDF output Note that the path is relative to the editix installation directory andis located inside the resdirectory.b. Installing a newXML ParserClick on the item 'install a custom parser' inside the Options menu.Add your java Jar(s), click on the button Search a JAXP class. If aclass name appears under the class name field your JAXP parser isfound. You may also enter manually the JAXP class name and check withthe bound button. Press OK and the parser is enabled the next time yourestart EditiX.Another option :You can install another JAXP compatible parser inside EditiX replacingthe default one (Xerces 2.6.2). You must : Copy inside the EDITIX_INSTALL_DIRECTORY/ext/parser directoryyour jar file(s) Modify the xmlconfig / parser preference with your JAXP SAXParserfactory class Restart EditiXFor information the default SAXParser factory has the value "XERCES"which is equal to "org.apache.xerces.jaxp.SAXParserFactoryImpl".c. Installing a newXSLT TransformerClick on the item 'install a custom transformer' inside the Optionsmenu. Add your java Jar(s), click on the button Search a JAXP class. Ifa class name appears under the class name field your JAXP transformerisfound.
2025-04-06