Winter 15- WSDL generated from Apex Class is not valid, and introduces new namespaces not declared in WSDL
Last updated 2014-12-23 ·Reference W-2386690 ·Reported By 8 users
Summary
In Winter 15, WSDL generated from Apex Class is not valid because it introduces new namespaces not declared in normal places for WSDL
This change in WSDL causes external consumer of custom Apex web services to fail.
Repro
1)create the following Apex class in a Winter 15 and save it.
global class MyWebService {
webService static Id makeAccount( ) {
Account a = new Account();
a.name='test';
insert a;
return a.id;
}
}
(2) Click on "Generate WSDL"
3)Repeat the same steps in a Summer 14 org
4) Compare the two wsdls:
The WSDL generated in Winter 15 should contain a bit xmlns:ns1 as defined inline in an element within the document.
When you validate these wsdls by using a third-party WSDL validator service, you will see that the wsdl from Winter 15 org fails.
Workaround
Download the WSDL locally and replace all instances of "ns1:" and "ns2:" with "tns:"
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.