Release 1.3.0 [12-Dec-2024]
cim-compare 1.3.0 is a minor release with both enhancements and defect fixes.
Defect Issue #21:
Java 11 introduced a new feature to limit the number of characters: Java11 Release Notes. This caused cim-compare to crash with the error:
[Fatal Error] CIMModelComparison_profile1.xml_AND_profile2.xml:9321:260: Invalid byte 1 of 1-byte UTF-8
ERROR: 'JAXP0801002: the compiler encountered an XPath expression containing '101' operators that exceeds the '100' limit set by 'FEATURE_SECURE_PROCESSING'.'
FATAL ERROR: 'JAXP0801002: the compiler encountered an XPath expression containing '101' operators that exceeds the '100' limit set by 'FEATURE_SECURE_PROCESSING'.'javax.xml.transform.TransformerConfigurationException: JAXP0801002: the compiler encountered an XPath expression containing '101' operators that exceeds the '100' limit set by 'FEATURE_SECURE_PROCESSING'. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTemplates(Unknown Source) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(Unknown Source) at org.cimug.compare.app.CIMModelComparisonGenerator.main(CIMModelComparisonGenerator.java:121)
This error has been resolved by disabling the character limit programmatically within cim-compare by internally setting the JVM parameters as recommended for use on the command line. Setting these system settings programmatically eliminates this command line need:
java -Djdk.xml.xpathExprGrpLimit=0 -Djdk.xml.xpathExprOpLimit=0 -Djdk.xml.xpathTotalOpLimit=0 -jar cim-compare-1.2.2.jar CIM_profile1.eap CIM_profile_2.eap
Enhancement Issue #22:
Previously, including UML diagrams in comparison reports resulted in ZIP archives that contained all diagrams in the model. This has been changed to now include only the subset of images relevant to the report that were either changed, added, or deleted. This results in potentially much smaller ZIP archives with the minimal set of images needed for the report.
Enhancement Issue #25:
Support for the Sparx EA 16.x and 17.x releases and the new 64-bit *.qea
project file format is now supported as input to cim-compare. Visit the README or public site for further details on usage. Note that there are now individual cim-compare .jar
distributions, one per EA release. This enhancement is only relevant if using .eap
or .qea
project files as input.
Enhancement Issue #24:
Changes made to the notes associated with classes or attributes were not easily identifiable. This release introduces a simple "diff feature" that displays removals using strike-through of the text that is highlighted in red. New text is also shown highlighted in green.