Hi, We're supporting WSN 1.3 because that is a ratified standard[1], while 1.2.x is just a draft. There are a number of message changes from 1.2 to 1.3, and the namespaces are quite different, so it's not possible to achieve backwards compatibility. You could use wsdl2java to generate a client for a WSDL that included WSN 1.2 definitions, but it wouldn't use Muse's NotificationProducerClient.
We'll be working to get Muse 2.x into the Maven2 repository as soon as possible - I don't have a date yet, but it will be part of our workload for 2.1. Dan Gero Vermaas <[EMAIL PROTECTED]> wrote on 10/02/2006 10:39:22 AM: > Hi, > > Thanks for the answers. > > Yes, I was referring to the 2.0 RC. > > Couple of additional questions: > > * The system that my client will talk with is based on > WS-Notification 1.2. I noted that Muse 2.0 supports > WS-Notification 1.3. Is this backwards compatible, in other words, > will it be possible to use Muse 2.0 to generate a client that > talks to a 1.2 WS-Notification producer implementation that is not > build using Muse. > * I noted that muse 1.0 is available on the ibilio.org maven2 > repository. Any plans to make the 2.0 version available there also? > > Thanks again, > Gero > > Daniel Jemiolo wrote: > > Hi, > > > > I assume you're referring to the Muse 2.0 release candidate, but I'm not > > sure since we haven't published the docs on the web site yet (just in the > > .zip files). > > > > Muse's command line tooling generates the server and client side of a > > project. It encorporates WSRF/WSN/WSDM implementations from Muse and > > creates new code for custom features you've added to your WSDL. For client > > generation, it will use pre-existing classes like > > NotificationProducerClient as a base class when generating a new Java > > client that is custom to your WSDL. > > > > The NotificationProducerClient, NotificationConsumerClient, and > > SubscriptionClient can all be used to send WSN messages. Based on what > > you've told me so far, I'm guessing that you'd want to write a service > > that implemented the WSN Notify operation so it could receive messages; > > you could then use NotificationProducerClient to subscribe and > > SubscriptionClient to destroy the subscription (unsubscribe). From the > > producer side, you can use NotificationConsumerClient to send messages. > > > > Dan > > > > > > Gero Vermaas <[EMAIL PROTECTED]> wrote on 09/28/2006 05:42:15 AM: > > > > > >> Hi, > >> > >> I'm developing an application that needs acts as a client to a > >> WS-Notification service (this is not implemented using Apache Muse). It > >> must be able to (un)subscribe and get notifications. I stumbled across > >> Apache Muse and scanned the documentation on the site and am not sure if > >> > > > > > >> I could use Apache Muse for this. > >> > >> Reading the documentation my initial feeling was that Muse is primarily > >> intended to build the server side of WS-Notifications and not the client > >> > > > > > >> side.... on the other hand... when I started browsing the download I > >> noticed the wsn-consumer sample which seems to do just what I want. It > >> subscribes to a NotificationProducerClient. So I think I can use Apache > >> Muse, is that correct? > >> > >> Regards, > >> Gero > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
