My Stuff
Comments
-
Just in case it helps anyone: This is a defect with 2015.2. NS is still investigating, but the temporary workarounds are the following: - either pass warningAsError=false on the request preferences (or turn it off globally: "Treat warnings as errors") - this is the one we chose - or use a RESTlet Gabe