Best Of
Re: Custom Scripting using Java
See https://docs.parasoft.com/display/SOA9106/Configuring+Localsettings - look for the property system.properties.classpath.
jakubiak
Parasoft support for Oracle Java in 2019 and beyond
Beginning in January 2019, Oracle will no longer release updates to Java 8 for commercial use (see https://www.oracle.com/technetwork/es/java/javase/documentation/eol-135779.html). Some Parasoft products (SOAtest, Virtualize, C/C++test, and DTP) currently ship Oracle Java 8 as part of the installation. As of January 2019, those products will continue to ship a publicly available version of Oracle Java 8 released prior to January 2019 that is free for commercial use. When deemed appropriate, Parasoft may upgrade the version of Java shipped within its products to a different version of Java (for example Oracle Java 11 or OpenJDK) that is still free for commercial use. Parasoft is currently evaluating the changes in Oracle's support for Java and will adjust strategy as needed.
jakubiak
Re: Compare XML and Json Response
You could write a script to covert the XML to JSON or the JSON to XML and then compare the documents after conversion. However, there is no universal way to map XML elements to JSON objects/arrays (or vice versa). This is especially true with respect to XML namespaces, XML attributes, and repeating XML elements. There are similarly different ways to map JSON arrays (single and multi-dimensional) to XML elements. There are different libraries for doing conversions but they all behave differently. Some are good about converting for JSON to XML and back but not the other way around. Similarly, others are good at converting XML to JSON and back but not the other way around. Basically, you end up with JSON-looking XML or XML-looking JSON. There's a good document from W3C I like to refer back to that describes the trouble and complications mapping between the two message formats. There is no good 1-to-1 mapping between JSON and XML. So, how things from your XML messages map to your new JSON messages would be somewhat specific to your service implementation.
You might also consider simply updating your tests to assert on the new JSON messages directly instead of trying to convert and compare the old XML messages against the new JSON messages.
Re: Insure++ 7.5.1- Release_notes and Readme
Well, now I'm embarrassed. 
We fundamentally changed the way we make these documents beginning with 7.5, and it looks like our packaging engine decided to pick up the old documents instead. I'll be looking into this.
The Readme files are mostly about installation instructions, but here are the Release notes, (applicable to both Unix and Windows platforms):
Insure++ Release Notes
Table of Contents
- General Release Notes for Insure++
- What’s New in 7.5.2
- What’s New in 7.5.1
- What’s New in 7.5
- Known Issues
- Supported Platforms
ParaSoft Corporation
http://www.parasoft.com
Voice: (626) 305-0041
Fax: (626) 305-9048
© Copyright, 1996-2018 Parasoft Corporation
General Release Notes for Insure++
What’s New in 7.5.2
- New parser, C++17 feature complete.
- Dropping support for MSVC++-10.0 (Visual Studio 2010).
- Adding support for MSVC++-15.0 (Visual Studio 2015).
What’s New in 7.5.1
- Windows 10 support.
- New Licensing schema
- 64-bit updates
- Several parser improvements and updates — continuing support for C++17.
What’s New in 7.5
- New EDG 4.14 parser full support for C++14, starting support for C++17.
- Support for GCC 6 and GCC 7, (-stdc++=17 not fully supported yet.)
- Support for newer GLIBC (version 2.14 and above)
- Support for new linux kernels (Fedora, Ubuntu 16, Centos 7)
- Dropped support for older GCC.
Known Issues
All Platforms
- C++11, C++14 and C++17 features are not compatible with object wrapping, please turn off tempInitWrapping in your .psrc configuration file. (Add directive: Insure++.tempInitWrapping off). In some instances this may also require checkingUninitObject wrapping to be turned off as well: (Add directive: Insure++.checkingUninitObjects off).
Windows
Support for Visual Studio 2010 is dropped in this release.
Use of constructs, (e.g. typeid(type).name()) causes heap corruption. The workaround is to turn off guardzones: Insure++.guardSize 0 in .psrc or “Advanced Options” in Insure Control panel.
In Visual Studio 2012, (and above)
Debugging managed executables with Insure++ and Visual Studio 2008 is not supported. This means that while you can run the instrumented code, and see Insure++ error messages, you cannot set breakpoints, or use the debugging features of Visual Studio. This is due to an incompatibility in the way that managed executables are handled by Visual Studio
Insure++ Build does not rebuild anything when only header files are changed. This is actually a Microsoft dependency tracking bug; the workaround is to use Insure++ Instrument File, Insure++ Rebuild Selection, or Insure++ Rebuild Solution when necessary.
When only the Visual C++ component is installed, the Insure++ toolbar is ineffective. After restarting Visual Studio, the buttons work, but the Tools → Insure++ menu remains unavailable. .NET components must be installed for the toolbar and menu items to work.
Windows 7, Windows Server 2008R2 (and later)
Users who run from Visual Studio without elevated privileges may see INSURE_ERRORs regarding .gus files. The workaround is to run with elevated privileges once, to "prime" the cache.
The Suppressions Panel will not work properly unless run with elevated privileges or Enable user specific options is selected in the Insure++ Control Panel.
Session zero isolation prevents user interaction with Insra when injecting system services. The workaround is to use a report file.
Windows x64
On Windows 7 and Windows 10, you may see USER_ERROR messages whose stack trace does not include any user code. These messages are often due to undocumented aspects of Windows interfaces and may be safely ignored.
C# executables built with “/platform:anycpu” (the default) fail to run under Insure++. The workaround is to build with either “/platform:x86” or “/platform:x64”.
AutoCAD plugins are incompatible with Insure++. Consider C++Test with BugDetective.
Supported Platforms
Insure++ no longer supports 32-bit archtectures. 32-bit applications running on 64-bit architectures are still supported. In other words, you must run Insure++ on a 64-bit host for instrumentation. You can build a 32-bit application, and run it on a 64-bit host, or a 32-bit host. We no longer support instrumenting on a 32-bit host at all.
The following are the only tested and officially supported platforms for this release:
Linux
We support Linux/x64 with the following compilers:
- GNU GCC 4.8 - 8.1
- Intel C/C++ 8.0 - 12.1
Earlier compilers, (e.g. gcc-3.x), may work, but we don’t test them, and can’t guarantee that they will work.
Only the features supported by the compilers are supported by Insure++. For example, g++-4.8 doesn’t support C++14, so Insure++ doesn’t support it either when compiling with g++-4.8. On the other hand, g++-5.4 does support C++14, and so does Insure++ when compiling with g++-5.4.
Note
In general, we support Linux, but only the following distributions are tested.
- CentOS 7
- Ubuntu 14
- Ubuntu 16
- Fedora 18
Windows
We support Windows/x64. There is no support for Windows/ppc, or Windows/IA-64.
The following are the only tested and officially supported platforms.
- Windows 7
- Windows Server 2008R2
- Windows Server 2012 (not tested nightly)
- Windows 10
The following Visual Studio products are supported:
- Visual Studio 2012 (VC 11.0)
- Visual Studio 2013 (VC 12.0)
- Visual Studio 2015 (VC 14.0)
- Visual Studio 2017 (VC 15.0)
Insure++ no longer supports any Visual Studio prior to 2012.
Rich
Re: Before you ask a question
Also if you have already submitted a support case, can you please also provide an Insure++ log from the execution run that you are seeing the behavior with. The steps to create an Insure++ log can be found here:
Before you ask a question
OS
Architecture (x86, x64, etc.)
Compiler
Insure++ version
If the problem is a compile/link time problem, include your compile/link line.
If the problem is a bug report you do not understand, please include the complete text of the bug report (note - not the entire insra report, just the bug in question), in your post, along with a code snippet if applicable.
Of course, other, more general questions are welcome as well.
Re: Not able to add "Key Columns" on Data Repository
Hi
Make sure you are clicking on a data set node in the repository. The editor for record types and data sets look very similar but record types don't have key columns. Also attaching a screenshot of the repository view and the editor where you don't have the option to add the key column may be helpful.
Re: Not able to add "Key Columns" on Data Repository
Hi hcavasos,
To build off of what @williammccusker said, the easiest way to do this is by closing any open repository editors, going into the data repository view, expanding your data set, and double clicking on it. For a better example: 
Once the repository window opens, you should be in the correct hierarchy level to right click and add in your key column.
Hope this helps!
