You're reading from Mastering Apex Programming A Salesforce developer's guide to learn advanced techniques and programming best practices for building robust and scalable enterprise-grade applications

Product type Paperback

Published in Nov 2023

Publisher Packt

ISBN-13 9781837638352

Length 394 pages

Edition 2nd Edition

Languages

Apex

Tools

Salesforce

Concepts

CRM

Author (1):

Paul Battisson

View More author details

Table of Contents (28) Chapters

Preface

1. Section 1: Triggers, Testing, and Security

2. Chapter 1: Common Apex Mistakes FREE CHAPTER

3. Chapter 2: Debugging Apex

4. Chapter 3: Triggers and Managing Trigger Execution

5. Chapter 4: Exceptions and Exception Handling

6. Chapter 5: Testing Apex Code

7. Chapter 6: Secure Apex Programming

8. Section 2: Asynchronous Apex

9. Chapter 7: Utilizing Future Methods

10. Chapter 8: Working with Batch Apex

11. Chapter 9: Working with Queueable Apex

12. Chapter 10: Scheduling Apex Jobs

13. Section 3: Integrations

14. Chapter 11: Integrating with Salesforce

15. Chapter 12: Using Platform Events

16. Chapter 13: Apex and Flow

17. Chapter 14: Apex REST and Custom Web Services

18. Chapter 15: Outbound Integrations – REST

19. Chapter 16: Outbound Integrations – SOAP

20. Chapter 17: DataWeave in Apex

21. Section 4: Apex Performance

22. Chapter 18: Performance and the Salesforce Governor Limits

23. Chapter 19: Performance Profiling

24. Chapter 20: Improving Apex Performance

25. Chapter 21: Performance and Application Architectures

26. Index

Why subscribe?

27. Other Books You May Enjoy

Generating Apex

For the remainder of this chapter, we are going to use an example endpoint provided by W3Schools. It provides an example API for temperature conversion, the WSDL for which can be retrieved at https://www.w3schools.com/xml/tempconvert.asmx?WSDL. This file can be saved locally as an XML file and used for uploading.

Updating the WSDL file for Salesforce

If you try uploading this file, however, you will receive some error messages stopping parsing; this is due to the WSDL from W3Schools offering multiple different bindings and ports for its API. This (along with other features of the specification such as the generic anyType data type) is not supported in the Apex language and processing. As such, the file must be updated to remove some unavailable features. I have already done this, and you can find this file in a GitHub gist at http://bit.ly/TemperatureConversionWSDL, although it is a simple item to update and may be an interesting exercise for readers.

With...