This registry reads services definitions from JSON configuration files at the application context initialization time.JSON files areexpected to be found inside a configured directory location and this registry will recursively look throughthe directory structure to find relevant JSON files.
For WickedWhims to detect the existence of strapons, the XML file has to contain its CAS Part ID. All of the variables highlighted in red should be modified for the file to work correctly and support your CAS part. 5.1 Variable 'caspartrawdisplayname’ is the name of your CAS Part that might be disabled for the user in-game. In August 1961, a couple by the name of Michael Gregsten and Valerie Storie were sitting in their Morris Minor car in Dorney Reach, UK, when an intruder forced his way into the back seat. CAS files use the filename CascadeInfo.cas. These files can potentially become corrupt if the computer unexpectedly crashes, denying access to the software. If this occurs, consult the Autodesk support to resolve the issue. By default, the CascadeInfo.cas file is located in the following directory: Windows Vista/7: C: ProgramData Autodesk ADLM.
Support is enabled by adding the following module into the Maven overlay:
Cas File Format
A sample JSON file follows:
To see the relevant list of CAS properties, please review this guide.
Clustering ServicesYou MUST consider that if your CAS server deployment is clustered, each CAS node in the cluster must haveaccess to the same set of JSON configuration files as the other, or you may have to devise a strategy to keepchanges synchronized from one node to the next.
The JSON service registry is also able to auto detect changes to the specified directory. It will monitor changes to recognizefile additions, removals and updates and will auto-refresh CAS so changes do happen instantly.
Escaping CharactersPlease make sure all field values in the JSON blob are correctly escaped, specially for the service id. If the service is defined as a regular expression, certain regex constructs such as '.' and 'd' need to be doubly escaped.
The naming convention for new JSON files is recommended to be the following:
Based on the above formula, for example the above JSON snippet shall be named: testJsonFile-103935657744185.json. Remember that because files are created based on the serviceName, you will need to make sure characters considered invalid for file names are not used as part of the name.
As you add more files to the directory, you need to be absolutely sure that no two service definitionswill have the same id. If this happens, loading one definition will stop loading the other. While service idscan be chosen arbitrarily, make sure all service numeric identifiers are unique. CAS will also output warningsif duplicate data is found.
JSON Syntax
CAS uses a version of the JSON syntax that provides a much more relaxedsyntax with the ability to specify comments.
A given JSON file for instance could be formatted as such in CAS:
Casefilexpress
Note the trailing comma at the end. See the above link for more info on the alternative syntax.
Cas File Cabinet Keys
Legacy Syntax
Cas File Download
CAS automatically should remain backwards compatible with service definitionsthat were created by a CAS 4.2.x instance. Warnings should show up in the logswhen such deprecated service definitions are found. Deployers are advised to review each definitionand consult the docs to apply the new syntax.
Case File Template
An example legacy JSON file is listed below for reference: