Question
· Oct 17, 2023
Debugging a SOAP web-client

Pointers please for debugging a SOAP web-client.

We have several clients in different productions all accessing a web-service. We are trying to add another client in a new production, and its not working. The messages between the relevant Process and the SOAP web-client Operation are the same in the working and the non-working productions. But the web-service is reporting an XML parsing error to the non-working production. Here's the error as reported in the SOAP web-client Operation...

0 3
0 160

Hello

I am trying to import a WSDL using the wizard and it outputs:

ERROR #6413: Element 'wsdl:binding:operation:msg': corresponding to message null : http://services.sanidad....

I have tried to find more information:

It is close to this case, however it is not the same error number:

0 1
0 374
Question
· Jun 22, 2020
Stunnel setup?

Hi I'm trying to setup STUNNEL between my pc and the cache database on the server, I'm trying to define port 1972 on my pc with out any luck.

has anyone done this?

thanks

Paul

0 11
0 403
Question
· May 3, 2018
Custom %ListOfDataTypes

Hi community.

I want to create a custom list inheriting %ListOfDatatypes in order to implement some methods like Map, Filter, ForEach, but I have some questions.
Just to mention, I have already read the topic about DeclarativeCOS.

When I define a property like following, caché uses %Collection.ListOfDT or %Collection.ListOfObj, as it's shown in the documentation

0 1
0 622

Im exporting our xml project from a QA server that has NOT upgraded to a production server that has been upgraded to HealthShare.

We are importing the exported xml over to this production server that is on HealthShare.

Now I havent been able to find the document link today, but I remember reading HealthShare puts all of the imports under a csp/healthshare/ directory.

We are able to view our .csp pages after importing them as xml into Studio on the production server running on HealthShare

0 2
0 191
Question
· Jun 4, 2018
Cache Studio 2017.2

Hi all,

I hope this is the right forum to ask this type of question, but I'm running out of ideas.

For reasons beyond my control, we run a version of Intersystems Caché (2013.1) that is not supported by Atelier. As such, I use Caché Studio to do my development.
The issue I have is, I don't run Windows or MAC, but Linux (Ubuntu 18.04 in my case). I've successfully managed to get Studio working using Wine and pretty much everything is usable.

0 8
0 1.9K

Hello,

Last weekend we've updated our Caché version to

Versie:Cache for Windows (x86-64) 2018.1.1 (Build 312U)

I'm using Studio to develop. I've been using the built-in debugger and it has been working nicely. But now, since the upgrade, I'm getting this error when trying to debug any routine or class method:

0 11
0 895

Presenter: Bill McCormick
Task: Migrate your development environment from Studio to Atelier
Approach: Give examples of various migration paths. Provide guidance for dealing with issues such as source control, source format, distributing code to previous versions, etc.

Moving from Studio to Atelier Session Code: ATMOVE In this session we will show you a variety of paths for migrating your development environment from Studio to Atelier. We will cover Source Control, Source Format, Distributing code to previous versions and more.

Content related to this session, including slides, video and additional learning content can be found here.

0 0
0 424