Web Service LOCATION configuration

[Rodrigo Werneck]

How one can have the LOCATION parameter of web service server classes (%SOAP.WebService) defined somewhere outside the class code so as not to have problems when deploying changes come from development/test systems where the LOCATION is typically different than the prod´?

[pavlov...@alanov.ru]

You can Set ..Location property in %OnNew() method. 

четверг, 17 января 2019 г., 7:10:09 UTC+7 пользователь Rodrigo Werneck написал:

[Raw Conscience]

It only works for clients, doesn't It? Or It does not work in the case of WSDL response, am I wrong? I,ve been recently inspecting the method which generates It, in %XML.Implementation class and It only looks to the class parameter LOCATION. Also it seems that no object is instatiated for WSDL request If any in the case of server classes when responding to real requests. Wrong again?

--
--
IRIS, Caché, Ensemble
---
You received this message because you are subscribed to the Google Groups "IRIS, Caché, Ensemble" group.
To unsubscribe from this group and stop receiving emails from it, send an email to intersystems-publi...@googlegroups.com.
To post to this group, send email to intersystems...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[pavlov...@alanov.ru]

Oh, I've misread you question.

Afaik, to get a WSDL by ?WSDL=1 URL from Caché web-service you already need to know the URL of service. Basically, a client needs to know there the service is to ask for it's WSDL, if you don't supply it some other way.
Then a client can send a web-service request to any URL, it does not matter what location is in in WSDL xml.

The service itself only works (natively) on /csp/csp-applicaton-name/classname.csl URL. To change it's "location", I mean, the URL on which the web-service is accessible, you need to setup rewrite or proxy rules in your production web-server which should be nginx or apache or some other external application.

But - you can change the parameter value on compile time by writing in class, if you want to.

Parameter LOCATION;

ClassMethod Location() As %Status [ CodeMode = generator ]
{
Set o=##class(%Dictionary.ParameterDefinition).%OpenId(%class_"||LOCATION")
Set o.Default="test"
Quit o.%Save()
}

пятница, 18 января 2019 г., 16:15:01 UTC+7 пользователь Rodrigo Werneck написал:

It only works for clients, doesn't It? Or It does not work in the case of WSDL response, am I wrong? I,ve been recently inspecting the method which generates It, in %XML.Implementation class and It only looks to the class parameter LOCATION. Also it seems that no object is instatiated for WSDL request If any in the case of server classes when responding to real requests. Wrong again?

Em sex, 18 de jan de 2019 00:55, <pavlov...@alanov.ru escreveu:

You can Set ..Location property in %OnNew() method. 

четверг, 17 января 2019 г., 7:10:09 UTC+7 пользователь Rodrigo Werneck написал:

How one can have the LOCATION parameter of web service server classes (%SOAP.WebService) defined somewhere outside the class code so as not to have problems when deploying changes come from development/test systems where the LOCATION is typically different than the prod´?

--
--
IRIS, Caché, Ensemble
---
You received this message because you are subscribed to the Google Groups "IRIS, Caché, Ensemble" group.

To unsubscribe from this group and stop receiving emails from it, send an email to intersystems-public-cache+unsub...@googlegroups.com.

[Rodrigo Werneck]

The case is that some clients (like PHP SoapClient on WSDL mode) do read the WSDL and parse it, including the Location information and use it dynamically at every operation/method invocation and that the accessible/external address is diferent than the default automatically formed by Caché and, finally, that it is different on each system (test, QA, live).

So it´s highly desirable that the LOCATION were kept in configuration files (or tables), separated from the class code itself.

But how?

[Rodrigo Werneck]

Oops, I just now tested and understood your suggestion.

It solves the problem.

Thank you

[Rodrigo Werneck]

Just now I´ve realized that as soon as the %SOAP.WebService subclass is imported and before it´s compiled (generally a few seconds, depend on the class code size), the imported LOCATION, usually different than the one generated dynamically, is exposed to WSDL requests.
How to circumvent this?

Thanks