This is what I was trying to communicate but did very poorly. Thank you for clarifying!
1) "Internal" tools such as Studio and System Explorer support these comments since they're valid in objectscript. However, the recommended way for classes is using the /// notation since that's what documentation and other things are generated. VS Code, I'm guessing, went for the "expected" notation rather than going for backward compatibility.
2) That would be my guess too.
3) Most likely someone modified the class to comment the property.
4) See #1
5) Assuming you don't want manually modify the class definition, you can always find the offending properties and modify(using %Dictionary classes) then compile the class definitions to change to proper notation. Then export/serialize with the changes.
Since you're using Cache, the options are "limited" compared to those in IRIS. Out of the box you can't call routines with the provided APIs, so you have the following options (can be combined depending on your needs):
- Create SQL mappings (classes)
- Expose the routines you want to call as stored procedure
- Create an "API" class in your system that expose the routines you want to call
- Create an "API" class that exposes a generic method where you can pass the routine name and parameters (similar to what IRIS does)
- Create a REST API similar to the APIs in before points
- There may be other options
For the REST API, apart from making the Cache changes you won't need any other Cache libraries in your Java code. For the other options you'd need one of the libraries/options provided by cache https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls