Difference between revisions of "Application Level Events (ALE) User's Guide"

From RifidiWiki

Jump to: navigation, search
(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

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

getEndpoint()

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

Example Rifidi App/Client

Personal tools