Dan wrote > I didn't implement Unsubscribe and Renew because a) time is short, and > b) > they are redundant. I believe that the reason these two operations exist > > is to allow people to implement subscription resources without a > dependency on WSRF. Subscriptions that are WSRF-based use Destroy for > Unsubscribe and SetTerminationTime for Renew - the concepts are exactly > the same, but in each case, the former is based on WSRL. With Muse, all > resources implement the implied resource pattern, so most of the WS-* > foundation that one would be looking to avoid when ditching WSRF is > already present; that being the case, I would advise someone to just add > > in the WSRL capabilities if either of these operations are desired. > You're already pulling in WSRF for the NotificationProducer impl, so > you might as > well take advantage of that and use WSRL in the subscription resource > rather than adding duplicate code to the app. >
Well, when I remove SubscriptionManager from the mix, I get the following out of SimpleNotificationProducer's initialize method: [ID = 'NoSubscriptionManager'] There is no resource that implements the WS-N SubscriptionManager portType defined in touchpoint.xml. In order to use and manage subscriptions, a touchpoint must expose a resource of type com.ibm.ws.notification.Subscription (or a sub-type); this resource will represent all new subscriptions created by the resource. I'm at a bit of a loss - any ideas? The com.ibm bit makes me a bit squeamish... am I still skiing out of bounds here? Thanks, Joel The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
