Discussions
- General Development
- Schema Development
- Apex Code Development
- Visualforce Development
- Formulas & Validation Rules
- Security
- Mobile
- Force.com Sites & Site.com
- Chatter Development
- Java Development
- .NET Development
- Perl, PHP, Python & Ruby
- Desktop Integration
- APIs and Integrations
- Visual Workflow
- Apple, Mac and OS X
- VB and Office Development
- AppExchange Directory & Packaging
- Salesforce Labs & Open Source Projects
- Other Salesforce Applications
- Jobs Board
- Force.com Discussion Boards
- :
- Developer Boards for Force.com and Database.com
- :
- Perl, PHP, Python & Ruby Development
- :
- Problem with different API-versions and WSDL
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Problem with different API-versio ns and WSDL
[ Edited ]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
10-15-2012 05:01 AM - edited 10-15-2012 05:02 AM
Hi!
I need to generate a new Enterprise WSDL for a web application built on API-version 22. However, I can only seem to generate one in ver 26, which does not seem to work out very well with the application. When switching wsdl-files (same name, same location), SOAP cannot find the new wsdl-file. Though it can find the old wsdl-file when I put it back.
Error message when using WSDL for ver 26:
Warning: SoapClient::SoapClient() [soapclient.soapclient]: I/O warning : failed to load external entity "/sf-lib/soapclient/enterprise.wsdl.xml" in /sf-lib/soapclient/SforceBaseClient.php on line 121
(I edited out some parts of the locations, but they are the same)
Does anyone know how to fix the location problem or how to generate a WSDL based on API ver 22?
Thanks in advance!
Re: Problem with different API-versio ns and WSDL
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
10-16-2012 08:51 AM
You cannot generate an Enterprise WSDL for anything other than the current version. There shouldn't be any reason why your code cannot open the new file as long as the location is correct, you have set the permissions to allow the code at least read access and you have deleted any copy of the WSDL that is cached. Check phpinfo() for the location of the cache if you do not know it.
Park

