Web service initialization using Axis2

["Doughty, Michael" <Mi...@bmc.com>]

I have a question on the Web service initialization using AXIS2.  We have an eventing service which keeps persistent data on events serialized to disc.  We do this because our events are stateful in a sense -- they have a status and can be modified over time, meaning that the same event can be sent out multiple times with updated information.

The problem we are running into is that the Web service code is never unless a client request is made to the service to either subscribe or poll for events.  This means that until a request is made, clients that consume events in the push model rather than the pull model won't receive events until a client that receives events through the pull model makes a request because the data and processes needed for this activity won't start until that time.

Another reason is for persistency in case the server goes down.  Since the eventing service saves persistent events on the service side in case the events did not send to cell or events did not retrieved by the clients. If the eventing service restarts, it should load the events and attempted to send to cell without a dependency on receiving a request from a client.