Reference Guide
Table Of Contents
- 1 Introduction
- 2 Establishing Your Test and Development Environments
- 3 Developing Applications
- Introduction
- Authentication
- REST API
- Audit Logging
- Alert Logging
- Configuration
- High Availability
- OpenFlow
- Metrics Framework
- GUI
- SKI Framework - Overview
- SKI Framework - Navigation Tree
- SKI Framework - Hash Navigation
- SKI Framework - View Life-Cycle
- SKI Framework - Live Reference Application
- UI Extension
- Introduction
- Controller Teaming
- Distributed Coordination Service
- Persistence
- Backup and Restore
- Device Driver Framework
- 4 Application Security
- 5 Including Debian Packages with Applications
- 6 Sample Application
- Application Description
- Creating Application Development Workspace
- Application Generator (Automatic Workspace Creation)
- Creating Eclipse Projects
- Updating Project Dependencies
- Building the Application
- Installing the Application
- Application Code
- 7 Testing Applications
- 8 Built-In Applications
- Appendix A
- Appendix B
- Bibliography
consumption or because it is meant to be used internally by a sideway API (see Controller-
Controller Communication via REST (Sideways APIs) on page 190) it may be annotated with
@RsDocIgnore as illustrated in the following listing.
RsDocIgnore Annotation:
package com.hp.hm.rs;
import com.hp.api.rsdoc.RsDocIgnore;
...
@Path("mypath")
public class MyResource extends ControllerResource {
@GET
@Path("internal")
@Produces(MediaType.APPLICATION_JSON)
@RsDocIgnore
public Response internalMethod() {
...
}
}
Trying the REST API with RSdoc
At this point try the REST API using the RSdoc, which is the preferred method. Follow the steps from
Rsdoc Live Reference on page 17 to open Rsdoc and authenticate, and then try the sample
application’s REST API as illustrated in Figure 57. Modify SwitchManager to return some fake data
in the getAll method and try GET switches from the RSdoc.
196