You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-user@ws.apache.org by Riaz <Ri...@scisys.co.uk> on 2007/06/11 18:19:43 UTC
Re: Problem with pauseSubscription
What should the entry in muse.xml be for the pause/resume capabilities?
Currently I get the error message:
java.lang.RuntimeException: [ID = 'MissingOperationImplementations'] The
WSDL file '/wsdl/FMSresource.wsdl' has the following operations which have
no match in any of the resource's capabilities:
[http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscriptionRequest,
http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/ResumeSubscriptionRequest]
Daniel Jemiolo wrote:
>
> The SubscriptionManager portType in WS-BaseNotification-1_3.wsdl does not
> have the Pause/Resume operations (they are optional). These operations are
> implemented as part of the SubscriptionManager capability, though, so all
> you have to do to expose them is add them to the WSDL. Just add the two
> <wsdl:operation/> elements to the SubscriptionManager portType (the
> <wsdl:message/>s are already defined), remembering to include the
> wsa:Action for each.
>
> If you're an Axis2 user, you must also add the WS-A Action to the
> services.xml file, or Axis2 won't let your request through.
>
> The two Action URIs are:
>
> http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscriptionRequest
>
> http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/ResumeSubscriptionRequest
>
>
>
> "Rosberg Mattias" <Ma...@tetrapak.com> wrote on 02/27/2007
> 07:00:11 AM:
>
>> I have created a wsn-producer/consumer system not very different from
> the
>> sample included in Muse. To create subscriptions I use the
>> NotificationProducerClient.subscribe(). This method returns a
>> SubscriptionClient object. The subscription works fine but when I try to
> pause
>> the subscription by calling pauseSubscription on the returned
>> SubscriptionClient object. I get the following error in return.
>>
>> <soap:Reason>
>> <soap:Text>[ID = 'ActionNotSupported'] The resource at
>> 'SubscriptionManager' does not expose an operation with the WS-Action
> 'http:
>>
> //docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscriptionRequest'
>
>> through any of its capabilities.</soap:Text>
>> </soap:Reason>
>>
>> In Muse every subscription creates a new resource, right? After
> debugging the
>> above scenario I end up in my subscription resource (SimpleWsResource)
>> 'MuseResource-1' trying to find a Capability to handle the
>> PauseSubscriptionRequest (getCapabilityForAction(action)). I believed
> that
>> pause and resume should be handled automatically by the
> SubscriptionManager.
>>
>> Any ideas what's missing? Do I have to implement my own
> "PausableSubscriptionResource"?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Problem-with-pauseSubscription-tf3300334.html#a11063583
Sent from the Muse User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: Problem with pauseSubscription
Posted by "Vinh Nguyen (vinguye2)" <vi...@cisco.com>.
Hi Dan,
You are correct. I spotted these methods in SubscriptionManager last
week, and they can only be called from the SubscriptionClient object.
But, if someone wanted to called Pause/Resume from the producer resource
in the same way they call Subscribe, then they'd have to add these
operations to their producer resource wsdl and create capability methods
for it (i.e. in an extended version of SimpleNotificationProducer).
As a note, Muse's implementation of Pause/Resume only sets a flag that
is checked when a notification message is published. If set, the
message will not be published until Resume is called to reset the flag.
Muse does not cache the unsent notifications. So if anyone wants
unpublished messages will be sent upon Resume, they'd have to add that
caching logic.
-----Original Message-----
From: Daniel Jemiolo [mailto:danjemiolo@us.ibm.com]
Sent: Monday, June 18, 2007 10:25 AM
To: muse-user@ws.apache.org
Subject: RE: Problem with pauseSubscription
PauseSubscription and ResumeSubscription *are* in Muse, as part of the
SubscriptionManager capability. You just need to add these two
operations to your WSDL in order to have them be part of the generated
muse.xml (and services.xml, if Axis2 is used).
Dan
"Vinh Nguyen \(vinguye2\)" <vi...@cisco.com> wrote on 06/12/2007
03:27:11 PM:
> Pause and Resume are not currently implemented in Muse. You will have
> write your own capability logic for these operations, and specify
> those custom capabilities in muse.xml.
>
>
> -----Original Message-----
> From: Riaz [mailto:Riaz.Shafi@scisys.co.uk]
> Sent: Monday, June 11, 2007 9:20 AM
> To: muse-user@ws.apache.org
> Subject: Re: Problem with pauseSubscription
>
>
> What should the entry in muse.xml be for the pause/resume
capabilities?
>
> Currently I get the error message:
> java.lang.RuntimeException: [ID = 'MissingOperationImplementations']
> The WSDL file '/wsdl/FMSresource.wsdl' has the following operations
> which have no match in any of the resource's capabilities:
> [http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscrip
> ti
> onRequest,
> http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/ResumeSubscrip
> ti
> onRequest]
>
>
> Daniel Jemiolo wrote:
> >
> > The SubscriptionManager portType in WS-BaseNotification-1_3.wsdl
> > does not have the Pause/Resume operations (they are optional). These
> > operations are implemented as part of the SubscriptionManager
> > capability, though, so all you have to do to expose them is add them
> > to the WSDL. Just add the two <wsdl:operation/> elements to the
> > SubscriptionManager portType (the <wsdl:message/>s are already
> > defined), remembering to include the wsa:Action for each.
> >
> > If you're an Axis2 user, you must also add the WS-A Action to the
> > services.xml file, or Axis2 won't let your request through.
> >
> > The two Action URIs are:
> >
> > http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscri
> > pt
> > ionRequest
> >
> > http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/ResumeSubscr
> > ip
> > tionRequest
> >
> >
> >
> > "Rosberg Mattias" <Ma...@tetrapak.com> wrote on 02/27/2007
> > 07:00:11 AM:
> >
> >> I have created a wsn-producer/consumer system not very different
> >> from
> > the
> >> sample included in Muse. To create subscriptions I use the
> >> NotificationProducerClient.subscribe(). This method returns a
> >> SubscriptionClient object. The subscription works fine but when I
> >> try
>
> >> to
> > pause
> >> the subscription by calling pauseSubscription on the returned
> >> SubscriptionClient object. I get the following error in return.
> >>
> >> <soap:Reason>
> >> <soap:Text>[ID = 'ActionNotSupported'] The resource
> >> at 'SubscriptionManager' does not expose an operation with the
> >> WS-Action
> > 'http:
> >>
> >
> //docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscriptionRe
> qu
> est'
> >
> >> through any of its capabilities.</soap:Text>
> >> </soap:Reason>
> >>
> >> In Muse every subscription creates a new resource, right? After
> > debugging the
> >> above scenario I end up in my subscription resource
> >> (SimpleWsResource) 'MuseResource-1' trying to find a Capability to
> >> handle the PauseSubscriptionRequest
(getCapabilityForAction(action)).
>
> >> I believed
> > that
> >> pause and resume should be handled automatically by the
> > SubscriptionManager.
> >>
> >> Any ideas what's missing? Do I have to implement my own
> > "PausableSubscriptionResource"?
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: muse-user-help@ws.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Problem-with-pauseSubscription-tf3300334.html#a1
> 10
> 63583
> Sent from the Muse User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: Problem with pauseSubscription
Posted by Daniel Jemiolo <da...@us.ibm.com>.
PauseSubscription and ResumeSubscription *are* in Muse, as part of the
SubscriptionManager capability. You just need to add these two operations
to your WSDL in order to have them be part of the generated muse.xml (and
services.xml, if Axis2 is used).
Dan
"Vinh Nguyen \(vinguye2\)" <vi...@cisco.com> wrote on 06/12/2007
03:27:11 PM:
> Pause and Resume are not currently implemented in Muse. You will have
> write your own capability logic for these operations, and specify those
> custom capabilities in muse.xml.
>
>
> -----Original Message-----
> From: Riaz [mailto:Riaz.Shafi@scisys.co.uk]
> Sent: Monday, June 11, 2007 9:20 AM
> To: muse-user@ws.apache.org
> Subject: Re: Problem with pauseSubscription
>
>
> What should the entry in muse.xml be for the pause/resume capabilities?
>
> Currently I get the error message:
> java.lang.RuntimeException: [ID = 'MissingOperationImplementations'] The
> WSDL file '/wsdl/FMSresource.wsdl' has the following operations which
> have no match in any of the resource's capabilities:
> [http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscripti
> onRequest,
> http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/ResumeSubscripti
> onRequest]
>
>
> Daniel Jemiolo wrote:
> >
> > The SubscriptionManager portType in WS-BaseNotification-1_3.wsdl does
> > not have the Pause/Resume operations (they are optional). These
> > operations are implemented as part of the SubscriptionManager
> > capability, though, so all you have to do to expose them is add them
> > to the WSDL. Just add the two <wsdl:operation/> elements to the
> > SubscriptionManager portType (the <wsdl:message/>s are already
> > defined), remembering to include the wsa:Action for each.
> >
> > If you're an Axis2 user, you must also add the WS-A Action to the
> > services.xml file, or Axis2 won't let your request through.
> >
> > The two Action URIs are:
> >
> > http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscript
> > ionRequest
> >
> > http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/ResumeSubscrip
> > tionRequest
> >
> >
> >
> > "Rosberg Mattias" <Ma...@tetrapak.com> wrote on 02/27/2007
> > 07:00:11 AM:
> >
> >> I have created a wsn-producer/consumer system not very different from
> > the
> >> sample included in Muse. To create subscriptions I use the
> >> NotificationProducerClient.subscribe(). This method returns a
> >> SubscriptionClient object. The subscription works fine but when I try
>
> >> to
> > pause
> >> the subscription by calling pauseSubscription on the returned
> >> SubscriptionClient object. I get the following error in return.
> >>
> >> <soap:Reason>
> >> <soap:Text>[ID = 'ActionNotSupported'] The resource
> >> at 'SubscriptionManager' does not expose an operation with the
> >> WS-Action
> > 'http:
> >>
> >
> //docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscriptionRequ
> est'
> >
> >> through any of its capabilities.</soap:Text>
> >> </soap:Reason>
> >>
> >> In Muse every subscription creates a new resource, right? After
> > debugging the
> >> above scenario I end up in my subscription resource
> >> (SimpleWsResource) 'MuseResource-1' trying to find a Capability to
> >> handle the PauseSubscriptionRequest (getCapabilityForAction(action)).
>
> >> I believed
> > that
> >> pause and resume should be handled automatically by the
> > SubscriptionManager.
> >>
> >> Any ideas what's missing? Do I have to implement my own
> > "PausableSubscriptionResource"?
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: muse-user-help@ws.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Problem-with-pauseSubscription-tf3300334.html#a110
> 63583
> Sent from the Muse User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
RE: Problem with pauseSubscription
Posted by "Vinh Nguyen (vinguye2)" <vi...@cisco.com>.
Pause and Resume are not currently implemented in Muse. You will have
write your own capability logic for these operations, and specify those
custom capabilities in muse.xml.
-----Original Message-----
From: Riaz [mailto:Riaz.Shafi@scisys.co.uk]
Sent: Monday, June 11, 2007 9:20 AM
To: muse-user@ws.apache.org
Subject: Re: Problem with pauseSubscription
What should the entry in muse.xml be for the pause/resume capabilities?
Currently I get the error message:
java.lang.RuntimeException: [ID = 'MissingOperationImplementations'] The
WSDL file '/wsdl/FMSresource.wsdl' has the following operations which
have no match in any of the resource's capabilities:
[http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscripti
onRequest,
http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/ResumeSubscripti
onRequest]
Daniel Jemiolo wrote:
>
> The SubscriptionManager portType in WS-BaseNotification-1_3.wsdl does
> not have the Pause/Resume operations (they are optional). These
> operations are implemented as part of the SubscriptionManager
> capability, though, so all you have to do to expose them is add them
> to the WSDL. Just add the two <wsdl:operation/> elements to the
> SubscriptionManager portType (the <wsdl:message/>s are already
> defined), remembering to include the wsa:Action for each.
>
> If you're an Axis2 user, you must also add the WS-A Action to the
> services.xml file, or Axis2 won't let your request through.
>
> The two Action URIs are:
>
> http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscript
> ionRequest
>
> http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager/ResumeSubscrip
> tionRequest
>
>
>
> "Rosberg Mattias" <Ma...@tetrapak.com> wrote on 02/27/2007
> 07:00:11 AM:
>
>> I have created a wsn-producer/consumer system not very different from
> the
>> sample included in Muse. To create subscriptions I use the
>> NotificationProducerClient.subscribe(). This method returns a
>> SubscriptionClient object. The subscription works fine but when I try
>> to
> pause
>> the subscription by calling pauseSubscription on the returned
>> SubscriptionClient object. I get the following error in return.
>>
>> <soap:Reason>
>> <soap:Text>[ID = 'ActionNotSupported'] The resource
>> at 'SubscriptionManager' does not expose an operation with the
>> WS-Action
> 'http:
>>
>
//docs.oasis-open.org/wsn/bw-2/SubscriptionManager/PauseSubscriptionRequ
est'
>
>> through any of its capabilities.</soap:Text>
>> </soap:Reason>
>>
>> In Muse every subscription creates a new resource, right? After
> debugging the
>> above scenario I end up in my subscription resource
>> (SimpleWsResource) 'MuseResource-1' trying to find a Capability to
>> handle the PauseSubscriptionRequest (getCapabilityForAction(action)).
>> I believed
> that
>> pause and resume should be handled automatically by the
> SubscriptionManager.
>>
>> Any ideas what's missing? Do I have to implement my own
> "PausableSubscriptionResource"?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
>
>
--
View this message in context:
http://www.nabble.com/Problem-with-pauseSubscription-tf3300334.html#a110
63583
Sent from the Muse User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org