DPATools README

1.3.0 Release

Enhancements

• 46 - Extend facilities for profile xs:Any elements to allow generation and validation In prior versions xs:Any elements were validated as ‘processContents = skip”, meaning no validation was performed under an xs:Any. Further, it was not possible to define document nodes to be generated under an xs:Any. An extension in 1.3.0 allows binding a global element from any schema of the profile to an xs:Any and using that element for validation or generation of document elements. The option is found in the profile node right-click menu and active only for an xs:Any element. The actual mechanism is to create a zero to unbounded occurs and a switch under the xs:Any, with each added global element as a child. This implements the functionality defined for interpretation of an xs:Any as ‘processContents = strict”, by allowing zero or more of the specifically identified global elements to appear in the profile. After extending the xs:Any, the actual occurrences and switch cases can be further restricted normally to limit the profile. Similarly, specific instances can be defined in exemplars.
• 73 - Add an "Extend Recursion" option to profile editor - In prior versions, recursive schema elements were detected and only one level of recursion was generated in the profile. In 1.3.0 a facility is added to the profile to allow the user to extend the terminal recursive element for another level. The option is found in the profile node right-click menu and active only for a terminal recursion element. When selected, the subtree under the recursive parent is re-expanded under the recursive child until each branch encounters a terminal or another occurrence of the recursive element. The expansion can them be repeated on the new terminal recursion. The expanded portion of the profile has all the functionality of any other profile subtree. For example, an exemplar can reference all the expanded nodes normally, but is unable to refer to a recursion level not present in the profile, just as it cannot reference any other non-profile subtree.
• 56 - Add a Populate function to the exemplar editor - Beginning in 1.3.0 an existing XML document can be used to populate an entire exemplar, in place of editing each field in the exemplar editor. This populate option is found in the exemplar node right-click menu. If the selected document is not valid under the schema of the exemplar an error is reported and no updates occur. Otherwise, document nodes valid in the exemplar are updated there if the document value is valid in the profile, and if not an error is reported. Optional exemplar nodes that do not exist in the document are ignored (a missing required node invalides the doc), and document nodes that do not appear in the profile are reported as errors. Note that all matching nodes are updated, so previous edits made to the exemplar are lost if the edited node exists in the document. This facility uses the same internal logic as validation, and, like validation, will create exemplar nodes from the document provided they are permitted under the profile. Consequently a ‘populate’ may be performed on a newly created exemplar and it will acquire the structure and content of a valid document.
• 81 Allow addition of a schema to an existing profile - If additional schemas are found to be necessary in a profile, such as to expand an xs:Any element, they may be added at any time. This ‘add schema’ option is found in the profile-level right-click menu. There is no functional difference between schemas added at profile-creation time or schemas added after the fact. The added schemas have the normal options for identifying namespace prefixes and selecting new root elements. A schema may be added with no root elements to allow later selection of global elements from the schema as either added roots (below) or xs:Any expansion elements.
• 80 Allow addition of a new root element to an existing profile - If additional root elements are found to be necessary in a profile they may be added at any time. This ‘add root’ option is found in the profile-level right-click menu. All global elements defined in the profile’s current schema set are available as root elements. There is no functional difference between root elements added at profile-creation time or added after the fact.
• 66 Support a WSDL-less service point - There are cases where a web service request is made by a “client-only’ actor that is not defined as a service point in any WSDL. For example, the WSDL may define a service offered to browsers, so their input appears as a defined input at the service and the output is returned, but the browser itself is not defined. Beginning in 1.3.0 a service point with the name ‘UniversalClient’is available in the Protocol ‘Service Points’ list to assign to such message sources or sinks.
• 45 Permit users to add annotations to the log file - A new “words cloud” below the “server busy” icon allows the user to add a comment to the log file, catalina.out in 1.3.0. This is of value when preparing examples of an issue for support, as it makes it possible for others to locate the log file entries related to the reported issue. Log comments immediately prior to and immediately following the issue are desirable.

Defects corrected

• #52 First node can now have more than one issued message. This removes a restriction on the possible message graphs for protocols.
• #8 Exemplar Set help now shows date-time and duration formats
• #25 Corrected failure to delete switch case occurrence
• #13 No longer render every tab for every page in render cycle. This represents a significant performance improvement.
• #24 Occurs Instance element zero [0] is no longer inappropriately editable
• #16 Removed spurious validation errors in validate-only subtrees
• #9 Fixed null pointer exception in Supervisor when unexpected message is received
• #53 Conversation message options for an edge now come from wsdl port inputs and outputs
• #18 Attempt to Delete Profile Tied to Exemplar no longer causes Tomcat crash
• #19 Correct failure if several exemplars in one SIF file and there are errors
• #31 Changing 'Attribute Optional' to 'Attribute Required' now generates correct SIF.
• #54 Validate does not expand switch cases at all
• #55 Validate expansions that are OK in UI don’t generate completely
• #92 Validate and generate have errors on minimally defined exemplars

---

1.2.1.RC1 Release

The 1.2.1.RC2 is a bug fix release from 1.2.1.RC1. Included in this release are:
49 - Externally resolved exemplar links may not generate values

---

1.2.1.RC1 Release

The 1.2.1.RC1 is a bug fix release from 1.2.0.RC2. Included in this release are:
48 - Message Reference parsing error reporting

---

1.2.0.RC2 Release

The 1.2.0.RC2 is a bug fix and open source prep release from 1.2.0.RC1. Included in this release are:
7 - add copyright notice to all source files
11 - No virtual occurrence node created from anonymous occurs in profile
15 - update to Axis2 1.6.1