It finally dawned on me what you are saying and what those reference pages are saying. I was really sure that notifications were something you had to include in each of your service wsdls, not that it was actually a generic service itself.
Thanks! On 9/18/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > The WSDL defined by WS-Notification only refer to the implementation of > the > services provided by WS-Notification. As a user, you just need to use > them, > i.e. send requests to the services. Make sure you read > http://incubator.apache.org/servicemix/servicemix-wsn2005.html > and > http://incubator.apache.org/servicemix/example-scenario.html > > On 9/18/07, Ryan Moquin <[EMAIL PROTECTED]> wrote: > > > > We need to convert one of our services to use notifications. Currently > > it's > > a jsr181 webservice. I've been doing searches about how to ws-notify a > > wsdl > > (which I just cannot find anywhere for some reason), I looked at the > > servicemix 3.2 examples and only find servicemix.xml files (which I > never > > figured out how to use a separate servicemix.xml anyhow), not wsdl > files. > > It seems as though people aren't having trouble getting started with > > notifications and servicemix, so I HAVE to be missing something very > > obvious. I just need a place to start so that a consumer in our > appserver > > can subscribe to notifications from our jsr 181 webservice without > > polling. > > I looked through the spec and it all makes sense, I just don't > understand > > how the wsdl fits in. > > > > Can someone point me in the right direction? Thanks! > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ >
