Problems saving xdata block combinations

[TwaHendrik]

Hello,

we receive an error message when we edit a class with an xdata block via Server-Side editing:

Failed to save 'Example.cls': Unable to write file 'isfs://localhost:test/Example.cls' (Body of '403 Forbidden' response to /api/atelier/v8/TEST/doc/Example.cls?ignoreConflict=1 request is not JSON. Is the web server suppressing detailed errors?)

We were able to simplify the example to this code:

Class Example Extends %RegisteredObject
{
XData motherPane [ XMLNamespace = "http://www.intersystems.com/zen" ]
{
<pane xmlns="http://www.intersystems.com/zen" >
<MYCOMP:MyTablePane>
<column  
filterType="query" 
filterQuery="SELECT 'Test' union SELECT 'Test'" />
</MYCOMP:MyTablePane>
</pane>
}
}

It seems that the problem occurs with the union. If you set filterQuery="SELECT ‘Test’", there is no problem. If you set filterQuery="SELECT ‘Test’ union SELECT ‘Test’" /> with 6 spaces after the union, it also works.

The code can be successfully compiled in Studio,

For other classes with the Union combination, the same error occurs.

[isc-bsaviano]

Hi @TwaHendrik, I created a new class in my USER namespace with the text above and it saved and compiled fine. What's your $ZV? The 403 error you got back is not what I would expect if there was an error saving the file. IRIS returns a 403 when you are not authorized to call that endpoint (you don't have %Development). The "not JSON" part is means that your web server is replacing the Atelier API error body with its own content. That's not desirable because VS Code relies on those error bodies to show your detailed messages.

[TWAMatthias]

@isc-bsaviano
We are working on windows... are you testing in mac?
Keep in mind, this happen only in server side mode.

I send you the version via PM/mail.

[isc-bsaviano]

I was testing on Mac, but I have a Windows VM I can use to test this.

EDIT: This is working fine for me on Windows as well

[isc-bsaviano]

I discussed this with @TwaHendrik and @TWAMatthias and we think this is a problem with a specific server and not a defect in this extension.