Difference between revisions of "Application Level Events (ALE) User's Guide"
From RifidiWiki
(→ALE Operations) |
(→ALE Operations) |
||
Line 18: | Line 18: | ||
==setEndpoint(String endPointName)== | ==setEndpoint(String endPointName)== | ||
+ | |||
+ | ==define(String specName, String specFilePath)== | ||
+ | |||
+ | ==undefine(String specName)== | ||
+ | |||
+ | ==getECSpec(String specName)== | ||
+ | |||
+ | ==getECSpecNames()== | ||
+ | |||
+ | ==subscribe(String specName, String notificationUri)== | ||
+ | |||
+ | ==unsubscribe(String specName, String notificationUri)== | ||
+ | |||
+ | ==poll(String specName)== | ||
+ | |||
+ | ==immediate(String specFilePath)== | ||
+ | |||
+ | ==getSubscribers(String specName)== | ||
+ | |||
+ | ==getStandardVersion()== | ||
+ | |||
+ | ==getVendorVersion()== | ||
=ALELR Operations= | =ALELR Operations= | ||
=Example Rifidi App/Client= | =Example Rifidi App/Client= |
Revision as of 20:24, 12 January 2016
Note: Leverage similar approach to REST - below is just my thoughts - open to other ways to approach
Contents
- 1 Introduction
- 2 Configuration
- 3 How to Test ALE Operations
- 4 ALE Operations
- 4.1 getEndpoint()
- 4.2 setEndpoint(String endPointName)
- 4.3 define(String specName, String specFilePath)
- 4.4 undefine(String specName)
- 4.5 getECSpec(String specName)
- 4.6 getECSpecNames()
- 4.7 subscribe(String specName, String notificationUri)
- 4.8 unsubscribe(String specName, String notificationUri)
- 4.9 poll(String specName)
- 4.10 immediate(String specFilePath)
- 4.11 getSubscribers(String specName)
- 4.12 getStandardVersion()
- 4.13 getVendorVersion()
- 5 ALELR Operations
- 6 Example Rifidi App/Client
Introduction
Configuration
such as JVM args with explanation
How to Test ALE Operations
Set up testing
Execute
Validate
ALE Operations
Note: for each operation example request/response/wsdl