What options do I have to change WSDL location for a web service used within Apex?

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.

Thanks for the prompt response Tony. I thought that wwas a superb idea, but unfortunately it doesn't work. On invoking the webservice I see the error...ORA-20001: The webservice was unreachable because either the etc... (If I amend the WS and put in the hard coded value, then it works as expected)

carpenteri 2010-03-03 14:09:26

That's a pity. It works for some things, such as paths to Javascript libraries in templates, so I just hoped it might work for your WSDL location too!

Tony Andrews 2010-03-03 14:54:47

It is, it would have been an ideal solution, but really appreciate your input.

carpenteri 2010-03-04 09:23:28

Thanks for the response Jeffrey - That looks a very promising lead, I'm off to give it try and will let you know how I get on.

carpenteri 2010-03-04 08:03:59

The rudimentary testing I performed shows this works.(webservice working --> update url to foo --> webservice stops working --> update back to correct address --> webservice working) I will need to perform more robust testing but the first impressions are good. I understand that updating the apex tables is not supported but it is a big step up from editing the export file.Thanks again for your help.

carpenteri 2010-03-04 09:33:36

I was thinking about this last night and my main fear about this approach is that we don't know how Oracle uses the value - e.g. it might be denormalised internally - copied to one or more other tables - and we wouldn't know. More likely, with a patch or version change the structure will later change in some way which breaks this approach.

Jeffrey Kemp 2010-03-05 00:49:24

Also, I would suggest you test it by changing the url to a known working webservice, then test that it actually calls the new URL correctly.

Jeffrey Kemp 2010-03-05 00:50:27

Thanks for the futher thoughts on this Jeffrey. This option will need further testing as you say and thanks for the idea on testing against another web service, I will add it to my suite of tests. If had several options then going down the route of updating the apex tables directly would be leave me feeling uneasy (especially after reading Scott Spendolini's Blog post on the subject) but as it appears to be my only viable option at this time I'm willing to try it out.

carpenteri 2010-03-05 13:58:14

ansaurus

tags:

views:

answers:

What options do I have to change WSDL location for a web service used within Apex?

related questions