Building Your Own Development Tools With the Force.com Tooling API

Doug Friedman@realdoug

Featuring:Joe Ferraro, CTO, Mavens Consulting@joeferraro

About Joe

About Doug

Agenda▪ Introduction to the Tooling API▪ Key objects/features▪ MavensMate demo

Metadata API

▪ SOAP Interface▪ Eclipse Plugin▪ Ant Migration Tool

The Tooling API:A great “Alternative”

▪ Restforce Ruby Gem▪ Command Line & cURL▪ MavensMate▪ Force.com Developer Console

How to UseWorks just like the Data API

▪ Oauth▪ JSON▪ REST/HTTP▪ SOAP/XML

Metadata API & Tooling API Together

The Tooling API is best used in conjunction with the Metadata API

▪ MetadataContainer• A resource which holds the pieces of metadata in your project

▪ ApexClassMember, ApexPageMember, <any type>Member• Represents a working copy of your Apex/Visualforce metadata

▪ ContainerAsyncRequest• Compile Apex/Visualforce asynchronously

▪ SymbolTable• Represents Apex Class tokens• Assists in Code completion for IDEs

Key Tooling API Objects

Compiling Apex/Visualforce

Create MetadataContain

er

Create ApexClassMember

SubmitContainerAsyncRequest

Add ApexClassMember to ContainerAsyncRequest

▪ ApexCodeCoverage• Queryable Apex unit test coverage statistics

▪ TraceFlag• Console output / stack trace• Easy debug log retrieval

▪ ApexLog• Debug logs generated by TraceFlag definitions

More Key Tooling API Objects

Debugging Apex/Visualforce

Create TraceFlag

Run Apex Code Retrieve DebugLog from Tooling endpoint

Speaker Name

CTO, Mavens Consulting,@joeferraro

Doug Friedman

@realdoug