Hi Damitha, In your article titled, "Web Services Eventing with Apache Savan/C - Part 1<http://wso2.org/library/3149>" there is a picture demonstrating the subscriber model.
[image: ws_eventing_with_savan-part1-img-2.png] Please tell us how the data sink talks to the subscriber? Were you able to debug the sample app? Regards Anees On Tue, Dec 7, 2010 at 11:21 PM, Damitha Kumarage <[email protected]> wrote: > Stadelmann Josef wrote: > >> So are you "basically" saing that Savan/C informs a subscriber about >> availability of information by a callback mechanism? >> >> > Savan/C implements the Web services Eventing specification > > Damitha > > Josef >> >> >> >> -----Ursprüngliche Nachricht----- >> Von: Damitha Kumarage [mailto:[email protected]] Gesendet: Montag, 6. >> Dezember 2010 19:10 >> An: Apache AXIS C User List >> Betreff: Re: AW: Publishing to the Data Sink url failed >> >> Stadelmann Josef wrote: >> >> >>> I am interested in this aspects too. >>> >>> >>> From an architectural point of view we have two paradigms >>> >>> >>> 1. We have the provider / consumer paradigm and >>> >>> 2. We have the publisher / subscriber paradigm >>> >>> >>> In the provider / consumer paradigm the consumer polls on a regular basis >>> for information provided by the provider >>> >>> >>> In a publisher / subscriber paradigm, the subscriber subscribes once with >>> the publisher and defines the information it is interested in and >>> >>> the publisher informs the subscriber when the information becomes >>> available or it delivers the information straight to the subscriber up on >>> availability >>> >>> >>> Can you provide the implementations used to implement one or both >>> paradigms. >>> >>> >>> >> Savan/C is basically a pub/sub implementation >> >> Damitha >> >> >>> >>> Josef >>> >>> >>> *Von:* anees k A [mailto:[email protected]] >>> *Gesendet:* Montag, 6. Dezember 2010 11:01 >>> *An:* Apache AXIS C User List >>> *Betreff:* Re: Publishing to the Data Sink url failed >>> >>> >>> Damitha, >>> >>> >>> Have you found any solution to the problem? >>> >>> >>> -- anees >>> >>> On Thu, Dec 2, 2010 at 9:39 AM, anees k A <[email protected]<mailto: >>> [email protected]>> wrote: >>> >>> Damitha, >>> >>> >>> Thank you very much for your response. Kindly let me know if you find >>> anything on the matter. >>> >>> >>> -- anees >>> >>> >>> On Thu, Dec 2, 2010 at 7:06 AM, Damitha Kumarage <[email protected]<mailto: >>> [email protected]>> wrote: >>> >>> anees k A wrote: >>> >>> Hi, >>> >>> I am still stuck at this. Can anyone please help me. >>> >>> Could reproduce your problem. Will look into this asap >>> >>> >>> >>> Also please help me understand the following point. >>> >>> "This is not part of Savan implementation. Subscriber is supposed >>> to "know" his own data sink." >>> >>> So how does the subscriber know some data is published? Will it >>> keep on polling the sink at periodic interval? (Please excuse my >>> lack of understanding.) >>> >>> You need to handle the communication between your listner service and >>> your client program >>> >>> Damitha >>> >>> >>> -- anees >>> >>> >>> >>> On Tue, Nov 30, 2010 at 9:51 AM, anees k A <[email protected]<mailto: >>> [email protected]> <mailto:[email protected] <mailto: >>> [email protected]>>> wrote: >>> >>> Damitha, >>> >>> Were you able to locate anything from the logs? I can see the >>> service getting listed using web-browser. Also if I invoke >>> "listener" (sink) separately, it is working. Any idea why this is >>> happening? >>> >>> -- anees >>> >>> On Mon, Nov 29, 2010 at 11:01 AM, anees k A <[email protected]<mailto: >>> [email protected]> >>> >>> <mailto:[email protected] <mailto:[email protected]>>> wrote: >>> >>> Damitha, >>> >>> 1. No data is published. >>> Log files are attached with this mail. Please note that the >>> logs attached are only for two commands from "subscriber" app >>> - Subscribe and Generate weather event. >>> 2. "This is not part of Savan implementation. Subscriber is >>> supposed to "know" his own data sink." >>> >>> So how does the subscriber know some data is published? Will >>> it keep on polling the sink at periodic interval? (Please >>> excuse my lack of understanding.) >>> >>> -- anees >>> >>> >>> On Mon, Nov 29, 2010 at 7:55 AM, Damitha Kumarage >>> >>> <[email protected] <mailto:[email protected]> <mailto: >>> [email protected] <mailto:[email protected]>>> wrote: >>> >>> anees k A wrote: >>> >>> Samisa, >>> >>> Using the browser I can see the data sync listed. Also >>> I used the sample application hello that comes with >>> Axis2/C to check the functionality of the "listener" >>> data sync. It is working fine. >>> >>> Can you grab the message published to the data sink >>> through tcpmon?. If the data is not published at all, >>> please send me the savan log file >>> >>> >>> To verify my understanding : >>> >>> 1. Subscriber subscribes to Data source for an event >>> 2. Data source, when an event, as subscribed by the >>> subscriber, is generated, publishes the data to the >>> data sink >>> >>> Yes when an event generated the data source publish it to >>> the corresponding subscribers, data sink. >>> >>> who in turn informs the subscriber. >>> >>> This is not part of Savan implementation. Subscriber is >>> supposed to "know" his own data sink. >>> >>> Damitha >>> >>> >>> Is this understanding correct? In this tutorial, >>> http://wso2.org/library/3149 this is not clearly >>> mentioned. Can you please help me? >>> >>> -- anees >>> >>> On Fri, Nov 26, 2010 at 6:02 AM, Samisa Abeysinghe >>> <[email protected] <mailto: >>> [email protected]> >>> <mailto:[email protected] <mailto: >>> [email protected]>> >>> <mailto:[email protected] <mailto: >>> [email protected]> >>> <mailto:[email protected] <mailto: >>> [email protected]>>>> wrote: >>> >>> Do you have your data sync working? Can you see if >>> that is working >>> using the browser or something? >>> >>> On Thu, Nov 25, 2010 at 12:32 PM, anees k A >>> <[email protected] <mailto:[email protected]> >>> <mailto:[email protected] <mailto:[email protected]>> >>> <mailto:[email protected] <mailto: >>> [email protected]> >>> <mailto:[email protected] <mailto: >>> [email protected]>>>> wrote: >>> >>> Hi, >>> >>> I am trying to understand Savan/C >>> implementation. While trying >>> out the sample subscriber-weather-listener >>> example, I am >>> seeing the below error : >>> >>> [error] publisher.c(225) Publishing to the Data >>> Sink: >>> http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:d22426a8-f85b-1df1-283b-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> >>> This happens when I am trying to issue the >>> command "5 Generate >>> weather event" from subscriber app. Any idea >>> why this is >>> happening ? I am running axis2c server and >>> installed Savan/C >>> to axis2c. >>> Regards >>> >>> Anees >>> >>> >>> Detailed Log <axis2c> >>> >>> [Thu Nov 25 12:32:31 2010] [info] Starting >>> addressing in handler >>> [Thu Nov 25 12:32:31 2010] [info] [savan][in >>> handler] >>> Unhandled message type >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:2a1d9ccc-f79e-1df1-2aa4-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:40f0c8c0-f79e-1df1-2aaf-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:deb954d4-f7ab-1df1-2ac3-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:4d5f6c30-f7c4-1df1-3254-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:cfade486-f7c5-1df1-3b39-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:44b5f7d2-f7c6-1df1-3b40-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:6f047970-f7c9-1df1-3b47-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:fe13e6e6-f7c9-1df1-3886-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:0d3574a0-f7f2-1df1-2241-000000000000 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:5b86caa4-f852-1df1-21d1-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:77a2f500-f852-1df1-21d4-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:d22426a8-f85b-1df1-283b-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:dd3bc4dc-f861-1df1-2be6-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(308) Could not >>> create the filter module >>> [Thu Nov 25 12:32:31 2010] [error] >>> publisher.c(225) Publishing >>> to the Data >>> Sink:http://localhost:9090/axis2/services/listener >>> proviced by >>> >>> subscriber:urn:uuid:f6c3869c-f861-1df1-3c59-00215c16d651 >>> Failed. Check whether the Data Sink url is correct >>> [Thu Nov 25 12:32:31 2010] [info] Request >>> served in 0.152 seconds >>> >>> Samisa ... >>> >>> http://samisa-abeysinghe.blogspot.com/ >>> >>> >>> >>> >>> -- >>> __________________________________________________________________ >>> >>> Damitha Kumarage >>> Technical Lead; WSO2 Inc. >>> "Oxygenating the Web Service Platform; " http://www.wso2.com/ >>> >>> blog: " http://damithakumarage.wordpress.com/ >>> >>> __________________________________________________________________ >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected]<mailto: >>> [email protected]> >>> >>> <mailto:[email protected] <mailto: >>> [email protected]>> >>> >>> >>> For additional commands, e-mail: >>> [email protected] <mailto: >>> [email protected]> >>> >>> <mailto:[email protected] <mailto: >>> [email protected]>> >>> >>> >>> >>> >>> >>> -- >>> __________________________________________________________________ >>> >>> Damitha Kumarage >>> Technical Lead; WSO2 Inc. >>> "Oxygenating the Web Service Platform; " http://www.wso2.com/ >>> >>> blog: " http://damithakumarage.wordpress.com/ >>> __________________________________________________________________ >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] <mailto: >>> [email protected]> >>> For additional commands, e-mail: [email protected] <mailto: >>> [email protected]> >>> >>> >>> >>> >>> >> >> >> >> > > > -- > __________________________________________________________________ > > Damitha Kumarage > Technical Lead; WSO2 Inc. > "Oxygenating the Web Service Platform; " http://www.wso2.com/ > > blog: " http://damithakumarage.wordpress.com/ > __________________________________________________________________ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
