What options do I have to change WSDL location for a web service used within Apex?
https://stackoverflow.com/questions/2371115
-
24-09-2019 - |
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianQuestion
Friends,
Hope you can help with a problem I am encountering with Apex and Web Services.
I have used the wizard within Apex to to create a web service reference. The webservice works as expected however...
One of the wizard steps requires the location of the wsdl file, which for development is at location a.
However when application is moved to QA, the wsdl will be at location b, and when this goes into production it will be at various different locations dependent on customer requirments.
I exported the application and looking at the resultant sql file, I can see wsdl reference is there, but I would rather not have to keep amending this file as it could become error prone or easily forgotten during the installation process.
Are there any other options that I have to amend the wsdl location? as it now appears the development location is hard coded into the application!
I have searched the Apex OTN Forums and found this question has been asked here and here but there have been no responses.
In case of need I am using Apex 3.2.1 & Oracle 10.2.0.3
Thanks in advance.
Solution
I don't have SYS access to my instance right now, but in Apex I see that web services are described by the APEX_APPLICATION_WEB_SERVICES view, which queries WWV_FLOW_SHARED_WEB_SERVICES.
You will want to test this carefully in a non-production Apex instance, but you might be able to get away with updating the URL column of this table directly.
I can't test this right now, and there are no guarantees this unsupported method won't mess something up.
OTHER TIPS
I don't know if this will work for a WSDL location, but have you tried setting up an application item e.g. WSDL_LOCATION and then setting the WSDL location to '&WSDL_LOCATION.'? You could then select a value into the application item from a table via an application process that runs on new session. However, that wil only work if Apex does variable substitution when accessing the WSDL location.
