SOAP 3 Callback Documentation
From
(Difference between revisions)
Line 22: | Line 22: | ||
{ | { | ||
// TODO: Implementation | // TODO: Implementation | ||
+ | // The heartbeat method is called every minute by the EService callback manager. | ||
+ | |||
} | } | ||
Line 28: | Line 30: | ||
{ | { | ||
// TODO: Implementation | // TODO: Implementation | ||
+ | // This will get fired on every user interaction which changes the state of a job, i.e. create job, dispatch, etc. | ||
} | } | ||
} | } |
Revision as of 22:34, 17 March 2010
The following callback interface is designed using VS2008 and ASMX.
An implementation of a callback service is also uploaded on our project page on Sourceforge. This implemenation contains a callback service written in ASMX and in WCF.
Need to implement three core methods (getVersion, heartBeat and eventSeq):
namespace soap2.nads.econz.co.nz { [WebService(Namespace = "http://soap2.nads.econz.co.nz")] [WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)] public class NADSCallbackService : System.Web.Services.WebService { [WebMethod] public CallbackVersion getVersion() { return CallbackVersion.VERSION_2; // should match the version of the callback interface } [WebMethod] public void heartBeat(int errorsSinceLastSuccess) { // TODO: Implementation // The heartbeat method is called every minute by the EService callback manager. } [WebMethod] public void eventSeq(UserIDBean externalServiceID, EventBean[] eventBeans) { // TODO: Implementation // This will get fired on every user interaction which changes the state of a job, i.e. create job, dispatch, etc. } } }
- CallbackVersion enumerand definition
- UserIDBean object definition
- EventBean object definition