I low prioritized it to work on other urgent stuff. I will be coming
back to notifications module this week-end. I will update you the
outcome.

Ramesh

On 12/21/06, Grady, Brendan (Mission Systems) <[EMAIL PROTECTED]> wrote:


Ramesh,

Did Dan's advice solve your issue?  I have the same problem that you are
describing, but as far as I can tell, I have the elements Dan listed below
in my WSDL's resource properties document.
e.g.

<xsd:schema elementFormDefault="qualified"
   targetNamespace="http://ws.apache.org/muse/test/wsrf";>

   <xsd:element name="ServerName" type="xsd:string" />
   <xsd:element name="MessageInterval" type="xsd:integer" />

   <xsd:element name="WsResourceProperties">
    <xsd:complexType>
     <xsd:sequence>
      <xsd:element ref="wsrf-rl:CurrentTime" />
      <xsd:element ref="wsrf-rl:TerminationTime" />
      <xsd:element
       ref="wsrf-rp:QueryExpressionDialect" minOccurs="0"
       maxOccurs="unbounded" />
      <xsd:element ref="wsnt:FixedTopicSet" />
      <xsd:element ref="wst:TopicSet" minOccurs="0" />
      <xsd:element ref="wsnt:TopicExpression" minOccurs="0"
maxOccurs="unbounded" />
      <xsd:element ref="wsnt:TopicExpressionDialect"
minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="muws1:ResourceId" />
      <xsd:element ref="muws1:ManageabilityCapability"
       minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="muws2:Caption" minOccurs="0"
       maxOccurs="unbounded" />
      <xsd:element ref="muws2:Description"
       minOccurs="0" maxOccurs="unbounded" />
      <xsd:element ref="muws2:Version" minOccurs="0" />
      <xsd:element ref="muws2:OperationalStatus" />
      <xsd:element ref="tns:ServerName" />
      <xsd:element ref="tns:MessageInterval" />
     </xsd:sequence>
    </xsd:complexType>
   </xsd:element>
<!-- Insert -->
   <xsd:element name="Update">
    <xsd:complexType>
      <xsd:sequence>
     <xsd:element name="arg" type="xsd:string"/>
      </xsd:sequence>
    </xsd:complexType>
   </xsd:element>

   <xsd:element name="UpdateResponse"/>
<!-- Insert -->
  </xsd:schema>


Thanks,
Brendan

On 12/09/06, Daniel Jemiolo <[EMAIL PROTECTED]> wrote:
In order to have a functional WSN producer, you need to have the following
four resource properties in your WSDL's resource properties document:

<xsd:element ref="wsnt:FixedTopicSet" />
<xsd:element ref="wst:TopicSet" minOccurs="0" />
<xsd:element ref="wsnt:TopicExpression" minOccurs="0" maxOccurs=
"unbounded" />
<xsd:element ref="wsnt:TopicExpressionDialect" minOccurs="0" maxOccurs=
"unbounded" />


where wsnt maps to the WS-BaseNotification namespace and wst maps to the
WS-Topics namespace. These properties, plus the Subscribe and
GetCurrentMessage operations, complete the WSN producer interface. Now
when you make a GetRP call, Muse will ask the WSN NotificationProducer
implementation for the values of the wsnt:Topic property.

Dan


"Ramesh Gurunathan" <[EMAIL PROTECTED]> wrote on 12/09/2006
01:11:07 PM:

> Dan,
>
> Pardon my ignorance... could you give me some more details on this? I
> am not sure what I should do here... still learning Muse.
>
> Ramesh
>
> On 12/10/06, Daniel Jemiolo <[EMAIL PROTECTED]> wrote:
> > The WSDL for your resource does not include the WSN Topic property.
Make
> > sure that your resource has the properties and operations for the WSN
> > NotificationProducer capability:
> >
> >
http://ws.apache.org/muse/docs/2.0.0/manual/capabilities/wsn-np.html
> >
> >
> > "Ramesh Gurunathan" <[EMAIL PROTECTED]> wrote on 12/09/2006
> > 12:55:15 PM:
> >
> > > I used the WsResourceClient to get the list of Topics but got the
> > > below error. I'm using the nightly build. Any ideas what is wrong
> > > here?
> > >
> > > org.apache.muse.ws.addressing.soap.SoapFault: [ID =
> > > 'PropertyNotInSchema'] There is no property named
> > > '{http://docs.oasis-open.org/wsn/b-2}Topic' defined
in the schema. A
> > > property should not have any operations or metadata applied to it if
> > > it is not in the WS-RP document.
> > >    at org.apache.muse.core.AbstractResourceClient.
> > > invoke(AbstractResourceClient.java:279)
> > >    at org.apache.muse.core.AbstractResourceClient.
> > > invoke(AbstractResourceClient.java:235)
> > >    at
org.apache.muse.ws.resource.remote.WsResourceClient.
> > > getResourceProperty(WsResourceClient.java:134)
> > >    at
> >
com.savi.fw.remote.notification.NotificationUtil.main(NotificationUtil.java:18)
> > >
> > > Ramesh
> > >
> > > On 12/9/06, Daniel Jemiolo <[EMAIL PROTECTED]> wrote:
> > > > You need to invoke GetResourceProperty on the wsnt:Topic property:
> > > >
> > > >
> > > > WsResourceClient client = new WsResourceClient(...);
> > > > Element[] topicXML =
> > client.getResourceProperty(WsnConstants.TOPIC_QNAME);
> > > >
> > > > //
> > > > // you can also do this, but only with Muse's client:
> > > > //
> > > > QName[] topicNames =
> > client.getPropertyAsObject(WsnConstants.TOPIC_QNAME,
> > > > QName.class);
> > > >
> > > >
> > > > Assuming this is a non-Java client, just make a GetRP request for
the
> > > > wsnt:Topic property:
> > > >
> > > > <wsrf-rp:GetResourceProperty
> > > >
xmlns:wsrf-rp="http://docs.oasis-open.org/wsrf/rp-2";
> > > >
xmlns:wsnt="http://docs-oasis-open.org/wsn/b-2";>
> > > >    wsnt:Topic
> > > > </wsrf-rp:GetResourceProperty>
> > > >
> > > >
> > > >
> > > > "Ramesh Gurunathan" <[EMAIL PROTECTED]> wrote on
12/08/2006
> > > > 11:28:08 AM:
> > > >
> > > > > Hi,
> > > > >
> > > > > I would like to retrieve the list of Topics that are available
for
> > > > > subscription. Could anyone advice me how I can do this? Let me
be
> > more
> > > > > specific. The web services client will retrieve list of Topics
from
> > > > > the server and lets the user to select the appropriate
subscription.
> > > > > Can this be achieved?
> > > > >
> > > > > Thank you for your input
> > > > >
> > > > > Ramesh
> > > > >
> > > > >
> >
---------------------------------------------------------------------
> > > > > 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]
> > > >
> > > >
> > >
> > >
---------------------------------------------------------------------
> > > 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]
> >
> >
>
>
---------------------------------------------------------------------
> 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]


---------------------------------------------------------------------
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]

Reply via email to