Be the first to post a text review of PHP - XML_XSLT2Processor. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Project Information Updated

  boen_robot changed the public information on the PHP - XML_XSLT2Processor project

  posted by boen_robot 103 days ago

• Project Information Updated

  boen_robot changed the public information on the PHP - XML_XSLT2Processor project

  posted by boen_robot 103 days ago

• Project Information Updated

  boen_robot changed the public information on the PHP - XML_XSLT2Processor project

  posted by boen_robot 103 days ago

• Project Information Updated

  boen_robot changed the public information on the PHP - XML_XSLT2Processor project

  posted by boen_robot 103 days ago

• XML_XSLT2Processor XML_XSLT2Processor v0.5.2 file released: XML_XSLT2Processor_v0_5_2.zip

  ==Class changes== Implemented issue 1907670 (reported by orzccc) - XSLT messages support is present for SAXON/JAVA-CLI. Messages can be seen in the error log. Their contents is shown as a serialized XML string. XML parser errors are shown in the error log with SAXON/JAVA-CLI. For many errors on SAXON9/JAVA-CLI, a column number is also available. Oddly enough, SAXON doesn't natively display it most of the time, and SAXON8 doesn't even appear to support it. Most other kinds of errors should now display flawlessly on the JAVA-CLI interface. When $processorPath is used with AltovaXML/COM, it now means a DCOM server. It was previously ignored altogether. The constructor now throws an exception when the COM interface is used and the com_dotnet extension is not available (e.g. on Linux). ==Test suite changes== AltovaXML/COM tests should now be skippable even on Linux. There was previously an error, because the com_dotnet extension was assumed to always be available. Added a lot of missing options tests, mostly for the JAVA-CLI interface, since it's the one known and expected to implement them correctly. The test suite now differentiates between SAXON8 and SAXON9. Note that since SAXON8/CLI and SAXON9/CLI both use "transform.exe" as their filename (unlike their JAVA-CLI counterparts), it's still very likely that one will incorrectly be used instead of the other.

  posted 345 days ago

• XML_XSLT2Processor XML_XSLT2Processor v0.5.2 file released: XML_XSLT2Processor_v0_5_2.tgz

  ==Class changes== Implemented issue 1907670 (reported by orzccc) - XSLT messages support is present for SAXON/JAVA-CLI. Messages can be seen in the error log. Their contents is shown as a serialized XML string. XML parser errors are shown in the error log with SAXON/JAVA-CLI. For many errors on SAXON9/JAVA-CLI, a column number is also available. Oddly enough, SAXON doesn't natively display it most of the time, and SAXON8 doesn't even appear to support it. Most other kinds of errors should now display flawlessly on the JAVA-CLI interface. When $processorPath is used with AltovaXML/COM, it now means a DCOM server. It was previously ignored altogether. The constructor now throws an exception when the COM interface is used and the com_dotnet extension is not available (e.g. on Linux). ==Test suite changes== AltovaXML/COM tests should now be skippable even on Linux. There was previously an error, because the com_dotnet extension was assumed to always be available. Added a lot of missing options tests, mostly for the JAVA-CLI interface, since it's the one known and expected to implement them correctly. The test suite now differentiates between SAXON8 and SAXON9. Note that since SAXON8/CLI and SAXON9/CLI both use "transform.exe" as their filename (unlike their JAVA-CLI counterparts), it's still very likely that one will incorrectly be used instead of the other.

  posted 345 days ago

• File released: /XML_XSLT2Processor/XML_XSLT2Processor v0.5.2/XML_XSLT2Processor_v0_5_2.zip

  posted 345 days ago

• File released: /XML_XSLT2Processor/XML_XSLT2Processor v0.5.2/XML_XSLT2Processor_v0_5_2.tgz

  posted 345 days ago

• XML_XSLT2Processor XML_XSLT2Processor v0.5.1 file released: XML_XSLT2Processor_v0_5_1.zip

  ==Class changes== Attempted to resolve Linux compatibility issues (reported by escapenguin). Actual tests on Linux (by me) are still to be done. PATH searching is now completely manual. This allows the constructor to throw an Exception when the processor can't be found. When used with the COM interface, the instance is now initialized at construction time instead of transformation time. This not only gives better performance, but also enables easier error recovery. setParameter() now performs more extensive validation of its arguments. The namespace is verified to be a valid xs:anyURI, and the name is verified to be a valid xs:NCName. Note that the 2** error codes have changed because of those changes. transformToURI() is now what I personally call "the main load method". In other words, transformToURI() is the method executing commands. This change was done for a lot of good reasons, but has one known slight side effect: When you use transformToXML() or transformToDoc(), you need to have writing permissions in the CWD. Previously, you'd only need them if you were using DOMDocument objects or transformToURI(). Remove excessive whitespace with AltovaXML on the CLI interface. There were a few new lines at the start and end of the output. AltovaXML now supports parameters with mode "FILE". "SAFE-STRING" parameters on AltovaXML finally work properly. It should even work with AltovaXML2007 and XSLT 1.0 stylesheets. Escaping is now done in a SAXON like fashion, where the contents is placed in a temporary file, and then read out with the document() function. Enabled "OUTPUT_VALIDATION" with setParameter(). It was previously not registered in the list of acceptable options, even though it would work if you use the options property. Boolean options are now strictly compared. They were previously loosely compared, making any "truthy" value set the option to "true" and any "falsy" value set the option to "false". Fixed issue 1907649 (reported by orzccc) - Paths are now resolved before they are given to the XSLT processor. This applies to all processors and interfaces, stylesheets and sources. In source documentation altered to show the changes made in 0.5.0 and this release. ==Test suite changes== trim() calls removed in accorance with the excessive whitespace fix. Tests can now be ran even if you haven't installed XML_XSLT2Processor with the PEAR installer. In this case, the files from the archive must be present as is. Tests are now skippable thanks to the manual path searching, and COM instance changes. For example, if you run "All_Tests" while having only SAXON, AltovaXML tests will be skipped. Changed the names of the SAXON construction classes to match the "testProcessor_Interface" pattern described in the Wiki. That is, testSAXON_N is now testSAXON_CLI, and testSAXON_J is now testSAXON_JAVACLI. Added tests for a few of SAXON's options.

  posted 591 days ago

• XML_XSLT2Processor XML_XSLT2Processor v0.5.1 file released: XML_XSLT2Processor_v0_5_1.tgz

  ==Class changes== Attempted to resolve Linux compatibility issues (reported by escapenguin). Actual tests on Linux (by me) are still to be done. PATH searching is now completely manual. This allows the constructor to throw an Exception when the processor can't be found. When used with the COM interface, the instance is now initialized at construction time instead of transformation time. This not only gives better performance, but also enables easier error recovery. setParameter() now performs more extensive validation of its arguments. The namespace is verified to be a valid xs:anyURI, and the name is verified to be a valid xs:NCName. Note that the 2** error codes have changed because of those changes. transformToURI() is now what I personally call "the main load method". In other words, transformToURI() is the method executing commands. This change was done for a lot of good reasons, but has one known slight side effect: When you use transformToXML() or transformToDoc(), you need to have writing permissions in the CWD. Previously, you'd only need them if you were using DOMDocument objects or transformToURI(). Remove excessive whitespace with AltovaXML on the CLI interface. There were a few new lines at the start and end of the output. AltovaXML now supports parameters with mode "FILE". "SAFE-STRING" parameters on AltovaXML finally work properly. It should even work with AltovaXML2007 and XSLT 1.0 stylesheets. Escaping is now done in a SAXON like fashion, where the contents is placed in a temporary file, and then read out with the document() function. Enabled "OUTPUT_VALIDATION" with setParameter(). It was previously not registered in the list of acceptable options, even though it would work if you use the options property. Boolean options are now strictly compared. They were previously loosely compared, making any "truthy" value set the option to "true" and any "falsy" value set the option to "false". Fixed issue 1907649 (reported by orzccc) - Paths are now resolved before they are given to the XSLT processor. This applies to all processors and interfaces, stylesheets and sources. In source documentation altered to show the changes made in 0.5.0 and this release. ==Test suite changes== trim() calls removed in accorance with the excessive whitespace fix. Tests can now be ran even if you haven't installed XML_XSLT2Processor with the PEAR installer. In this case, the files from the archive must be present as is. Tests are now skippable thanks to the manual path searching, and COM instance changes. For example, if you run "All_Tests" while having only SAXON, AltovaXML tests will be skipped. Changed the names of the SAXON construction classes to match the "testProcessor_Interface" pattern described in the Wiki. That is, testSAXON_N is now testSAXON_CLI, and testSAXON_J is now testSAXON_JAVACLI. Added tests for a few of SAXON's options.

  posted 591 days ago