**1) What to do:**
This ([url removed, login to view] - specified the contracts) file is the WS-Eventing specification document which I need to implement for my project. Have look at the this specification especially page (3,4,5,8,12,13,14). In the section 3, I need to implement only the **Subscribe**, **Renew**, **Unsubscribe, and Fault** operations. No need to implement the GetStatus and Subscription End operation right now. You don't have to read section 6 no need at all. The SubscriptionManager class and the Event Source Class should be made in 2 separate classes. [url removed, login to view]
**2) How to do**
Implement this using JAVA, the **WSPEER** will host the web service
The FINS project has implemented WS-Eventing. However it is not 100% compliant. You may use this as a basis to complete it, but you will need to remove other functions that it has - all we need is the features in (1). All other features must be removed if you want to use FINS as a base for your code. FINS has numerous dependancies on OMNIdatabase. Instead of OMNI, use XML to store the state of the WS.
**Download these too:**
1) FINS is an independent project which tries to implement the WS-EVENTING standard in its own way. I only need a few functions of WS-EVENTING and it must be 100% compliant with the research paper
[url removed, login to view]
2) The (\wspeer\src\com) folder is part of the WS-Eventing implementation which I made. This implementation is working but needs some modifications.
[[url removed, login to view]<wbr />/1B14566B0B676646]
I have attempted to modify the source of WSPEER to try to implement WS-EVENTING. I have not been successful. The (\wspeer) folder is the WSPeer where my staff (\wspeer\src\com) is fitted in. The WSPeer take care of the deployment web service and other thing. It acts as tomcat container and Axis engine. Your implementation should be in **JAVA**, using **WSPEER to host** your webservices. WSPEER is like an incubator
Add all these path:
(\wspeer\lib) [url removed, login to view] and [url removed, login to view] in (\wseventing) folder
To see how these thing work run the class DeploySourceService in (\wspeer\src\com\wse\example) DeploySourceService class will deploy the Calculator service(\wspeer/src/com/wse/example) which extend Source class that act as source web service that allow other service to subscribe to add operation that implemented by Calculator service.
If the every thing is ok you will get the WSDL file by http://localhost:4899/wspeer/Calculator?wsdl Then run the **DeploySinkService** calss in (\wspeer/src/com/wse/example). DeploySinkService class deploys the **SubscriberAhmed** service (\wspeer/src/com/wse/example). Which implements Sink class that act as web service sink. If everything is ok you will get the WSDL file by http://localhost:4815/wspeer/SubscriberAhmed?wsdl
3) Assuming your implementation is perfect, I can then use Triana as a client to test it. I will be using **Triana** as a client to test your implementation
[url removed, login to view]
How to verify using TRIANA:
[[url removed, login to view]<wbr />/584487CE4377D132]