How to create a custom dialect for TopicExpression

[nero_s]

Hi,
I am implementing a prototype using muse-wsn, and our prototype requires usage of a custom Dialect for TopicExpression.

Muse currently supports only Concrete (<wsnt:TopicExpression Dialect="http://docs.oasis-open.org/wsn/t-1/TopicExpression/Concrete">tns:MyTopic</wsnt:TopicExpression>)

We want implement a custom dialect, Dialect="urn:ihe:iti:xds-b:pubsub:2008" and with XML as the actual topic.

 <wsnt:Filter  xmlns="urn:ihe:iti:pub-sub:2008" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:tns="http://ws.apache.org/muse/test/wsrf">
        <wsnt:TopicExpression Dialect="urn:ihe:iti:xds-b:pubsub:2008">  
                <rim:AdhocQuery id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
                        <rim:Slot name="$XDSDocumentEntryPatientId">
                                    :
                                    :
                </rim:AdhocQuery>
        </wsnt:TopicExpression>
</wsnt:Filter>

I am new to muse and really need some help here, So far i have:
1) Created a filter class:  public class IHEFilter implements Filter
2) Created Handler:        public class IHEFilterHandler implements FilterFactoryHandler
3) in initialize() method of SimpleNotificationProducer added FilterFactory.getInstance().addHandler(new IHEFilterHandler());

Is this the right approach?

[nero_s]

ok, some progress, i got my subscriptions to work, now i want to implement a notification publisher. But am stuck here, since muse uses SimpleNotificationMessage which supports only concrete dialect and topicName as QName, i want to publish send Notify which will have Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content : <rim:AdhocQuery id="urn .....

Need some directions on where to start, thanks in advance...

[Chris Twiner]

Hiya,

I'm a little confused, you have implemented a non topic based
subscription, ie. it looks at the message contents.  From that
perspective it doesn't matter which topic you publish on.  You could
for example publish on a QName of namespace
urn:ihe:iti:xds-b:pubsub:2008 to signify that its intended only for
that type of subscription.

You must publish on a topic but all Filters will get called.

cheers,
Chris

On 2/6/09, nero_s <shailesh.soliwal@...> wrote:

>
>  ok, some progress, i got my subscriptions to work, now i want to implement a
>  notification publisher. But am stuck here, since muse uses
>  SimpleNotificationMessage which supports only concrete dialect and topicName
>  as QName, i want to publish send Notify which will have
>  Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content :
>  <rim:AdhocQuery id="urn .....
>
>  Need some directions on where to start, thanks in advance...
>
> --
>  View this message in context: http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21868551.html
>
> Sent from the Muse User mailing list archive at Nabble.com.
>
>

[nero_s]

Hi Chris
Yes, you're right and thats where am stuck :)

I want to implement custom Topic, i.e, my Topic would xml content.
For example My topic would be :
                <rim:AdhocQuery id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
                        <rim:Slot name="$XDSDocumentEntryPatientId">
                                    :
                                    :
                </rim:AdhocQuery>

I am trying to send notification, but currently there is no way to set topic as XML content, only Qname is supported.

If i can implement this, next step would be to handle topic in my custom filter(IHEFilter).

Is it possible to have xml as topic?

Thanks
nero

Chris Twiner wrote:

Hiya,

I'm a little confused, you have implemented a non topic based
subscription, ie. it looks at the message contents.  From that
perspective it doesn't matter which topic you publish on.  You could
for example publish on a QName of namespace
urn:ihe:iti:xds-b:pubsub:2008 to signify that its intended only for
that type of subscription.

You must publish on a topic but all Filters will get called.

cheers,
Chris

On 2/6/09, nero_s <[e-mail]> wrote:
>
>  ok, some progress, i got my subscriptions to work, now i want to implement a
>  notification publisher. But am stuck here, since muse uses
>  SimpleNotificationMessage which supports only concrete dialect and topicName
>  as QName, i want to publish send Notify which will have
>  Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content :
>  <rim:AdhocQuery id="urn .....
>
>  Need some directions on where to start, thanks in advance...
>
> --
>  View this message in context: http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21868551.html
>
> Sent from the Muse User mailing list archive at Nabble.com.
>
>

[nero_s]

To give a background, I am trying to create a prototype on IHE pub/sub profile,

http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Whitepaper_XDS-b_pub_sub_2008_08_22.pdf


Thanks again,
nero



Hi Chris
Yes, you're right and thats where am stuck :)

I want to implement custom Topic, i.e, my Topic would xml content.
For example My topic would be :
                <rim:AdhocQuery id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
                        <rim:Slot name="$XDSDocumentEntryPatientId">
                                    :
                                    :
                </rim:AdhocQuery>

I am trying to send notification, but currently there is no way to set topic as XML content, only Qname is supported.

If i can implement this, next step would be to handle topic in my custom filter(IHEFilter).

Is it possible to have xml as topic?

Thanks
nero

Chris Twiner wrote:

Hiya,

I'm a little confused, you have implemented a non topic based
subscription, ie. it looks at the message contents.  From that
perspective it doesn't matter which topic you publish on.  You could
for example publish on a QName of namespace
urn:ihe:iti:xds-b:pubsub:2008 to signify that its intended only for
that type of subscription.

You must publish on a topic but all Filters will get called.

cheers,
Chris

On 2/6/09, nero_s <[e-mail]> wrote:
>
>  ok, some progress, i got my subscriptions to work, now i want to implement a
>  notification publisher. But am stuck here, since muse uses
>  SimpleNotificationMessage which supports only concrete dialect and topicName
>  as QName, i want to publish send Notify which will have
>  Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content :
>  <rim:AdhocQuery id="urn .....
>
>  Need some directions on where to start, thanks in advance...
>
> --
>  View this message in context: http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21868551.html
>
> Sent from the Muse User mailing list archive at Nabble.com.
>
>

[Chris Twiner]

There is no direct support for this in Muse.   You can implement
you're own Topic that provides this, returning an empty QName for the
topic interface etc.

Additionally createNotificationMessage in SimpleNotificationProducer
can be overriden to handle the new notificationmessage type.  This
just leaves the processing in the clients / a new
SimpleNotifactionConsumer (to use a different serializer /
MessageHandler).

Be ware that for strict WS-N topic support that you must have a fixed
topic namespace.  If you want to create these dynamically (I'm
guessing so) the standard says to use the empty namespace "" for
dynamic topics.

On 2/6/09, nero_s <shailesh.soliwal@...> wrote:

>
>  Hi Chris
>  Yes, you're right and thats where am stuck :)
>
>  I want to implement custom Topic, i.e, my Topic would xml content.
>  For example My topic would be :
>
>                 <rim:AdhocQuery
>  id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
>                         <rim:Slot name="$XDSDocumentEntryPatientId">
>                                     :
>                                     :
>                 </rim:AdhocQuery>
>
>
> I am trying to send notification, but currently there is no way to set topic
>  as XML content, on Qname is supported.
>
>  If i can implement this, next step would be to handle topic in my custom
>  filter(IHEFilter).
>
>  Is it possible to have xml as topic?
>
>  Thanks
>  nero
>
>
>
>
>
>  Chris Twiner wrote:
>  >
>  > Hiya,
>  >
>  > I'm a little confused, you have implemented a non topic based
>  > subscription, ie. it looks at the message contents.  From that
>  > perspective it doesn't matter which topic you publish on.  You could
>  > for example publish on a QName of namespace
>  > urn:ihe:iti:xds-b:pubsub:2008 to signify that its intended only for
>  > that type of subscription.
>  >
>  > You must publish on a topic but all Filters will get called.
>  >
>  > cheers,
>  > Chris
>  >
>  > On 2/6/09, nero_s <shailesh.soliwal@...> wrote:
>  >>
>  >>  ok, some progress, i got my subscriptions to work, now i want to
>  >> implement a
>  >>  notification publisher. But am stuck here, since muse uses
>  >>  SimpleNotificationMessage which supports only concrete dialect and
>  >> topicName
>  >>  as QName, i want to publish send Notify which will have
>  >>  Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content :
>  >>  <rim:AdhocQuery id="urn .....
>  >>
>  >>  Need some directions on where to start, thanks in advance...
>  >>
>  >> --
>  >>  View this message in context:
>  >> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21868551.html
>  >>
>  >> Sent from the Muse User mailing list archive at Nabble.com.
>  >>
>  >>
>  >
>  >
>
>
> --
>  View this message in context: http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21872536.html
>
> Sent from the Muse User mailing list archive at Nabble.com.
>
>

[nero_s]

great, thanks a lot, will start looking at that..

Chris Twiner wrote:

There is no direct support for this in Muse.   You can implement
you're own Topic that provides this, returning an empty QName for the
topic interface etc.

Additionally createNotificationMessage in SimpleNotificationProducer
can be overriden to handle the new notificationmessage type.  This
just leaves the processing in the clients / a new
SimpleNotifactionConsumer (to use a different serializer /
MessageHandler).

Be ware that for strict WS-N topic support that you must have a fixed
topic namespace.  If you want to create these dynamically (I'm
guessing so) the standard says to use the empty namespace "" for
dynamic topics.

On 2/6/09, nero_s <[e-mail]> wrote:
>
>  Hi Chris
>  Yes, you're right and thats where am stuck :)
>
>  I want to implement custom Topic, i.e, my Topic would xml content.
>  For example My topic would be :
>
>                 <rim:AdhocQuery
>  id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
>                         <rim:Slot name="$XDSDocumentEntryPatientId">
>                                     :
>                                     :
>                 </rim:AdhocQuery>
>
>
> I am trying to send notification, but currently there is no way to set topic
>  as XML content, on Qname is supported.
>
>  If i can implement this, next step would be to handle topic in my custom
>  filter(IHEFilter).
>
>  Is it possible to have xml as topic?
>
>  Thanks
>  nero
>
>
>
>
>
>  Chris Twiner wrote:
>  >
>  > Hiya,
>  >
>  > I'm a little confused, you have implemented a non topic based
>  > subscription, ie. it looks at the message contents.  From that
>  > perspective it doesn't matter which topic you publish on.  You could
>  > for example publish on a QName of namespace
>  > urn:ihe:iti:xds-b:pubsub:2008 to signify that its intended only for
>  > that type of subscription.
>  >
>  > You must publish on a topic but all Filters will get called.
>  >
>  > cheers,
>  > Chris
>  >
>  > On 2/6/09, nero_s <[e-mail]> wrote:
>  >>
>  >>  ok, some progress, i got my subscriptions to work, now i want to
>  >> implement a
>  >>  notification publisher. But am stuck here, since muse uses
>  >>  SimpleNotificationMessage which supports only concrete dialect and
>  >> topicName
>  >>  as QName, i want to publish send Notify which will have
>  >>  Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content :
>  >>  <rim:AdhocQuery id="urn .....
>  >>
>  >>  Need some directions on where to start, thanks in advance...
>  >>
>  >> --
>  >>  View this message in context:
>  >> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21868551.html
>  >>
>  >> Sent from the Muse User mailing list archive at Nabble.com.
>  >>
>  >>
>  >
>  >
>
>
> --
>  View this message in context: http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21872536.html
>
> Sent from the Muse User mailing list archive at Nabble.com.
>
>

[nero_s]

This would mean I cannot use the Topic interface provided by muse either, since it has no support for xml type of filter. This seems to get a little complex, it will be great if you can give me some initial directions to get started and get it right.

Thanks,
Nero.

Chris Twiner wrote:

There is no direct support for this in Muse.   You can implement
you're own Topic that provides this, returning an empty QName for the
topic interface etc.

Additionally createNotificationMessage in SimpleNotificationProducer
can be overriden to handle the new notificationmessage type.  This
just leaves the processing in the clients / a new
SimpleNotifactionConsumer (to use a different serializer /
MessageHandler).

Be ware that for strict WS-N topic support that you must have a fixed
topic namespace.  If you want to create these dynamically (I'm
guessing so) the standard says to use the empty namespace "" for
dynamic topics.

On 2/6/09, nero_s <[e-mail]> wrote:
>
>  Hi Chris
>  Yes, you're right and thats where am stuck :)
>
>  I want to implement custom Topic, i.e, my Topic would xml content.
>  For example My topic would be :
>
>                 <rim:AdhocQuery
>  id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
>                         <rim:Slot name="$XDSDocumentEntryPatientId">
>                                     :
>                                     :
>                 </rim:AdhocQuery>
>
>
> I am trying to send notification, but currently there is no way to set topic
>  as XML content, on Qname is supported.
>
>  If i can implement this, next step would be to handle topic in my custom
>  filter(IHEFilter).
>
>  Is it possible to have xml as topic?
>
>  Thanks
>  nero
>
>
>
>
>
>  Chris Twiner wrote:
>  >
>  > Hiya,
>  >
>  > I'm a little confused, you have implemented a non topic based
>  > subscription, ie. it looks at the message contents.  From that
>  > perspective it doesn't matter which topic you publish on.  You could
>  > for example publish on a QName of namespace
>  > urn:ihe:iti:xds-b:pubsub:2008 to signify that its intended only for
>  > that type of subscription.
>  >
>  > You must publish on a topic but all Filters will get called.
>  >
>  > cheers,
>  > Chris
>  >
>  > On 2/6/09, nero_s <[e-mail]> wrote:
>  >>
>  >>  ok, some progress, i got my subscriptions to work, now i want to
>  >> implement a
>  >>  notification publisher. But am stuck here, since muse uses
>  >>  SimpleNotificationMessage which supports only concrete dialect and
>  >> topicName
>  >>  as QName, i want to publish send Notify which will have
>  >>  Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content :
>  >>  <rim:AdhocQuery id="urn .....
>  >>
>  >>  Need some directions on where to start, thanks in advance...
>  >>
>  >> --
>  >>  View this message in context:
>  >> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21868551.html
>  >>
>  >> Sent from the Muse User mailing list archive at Nabble.com.
>  >>
>  >>
>  >
>  >
>
>
> --
>  View this message in context: http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21872536.html
>
> Sent from the Muse User mailing list archive at Nabble.com.
>
>

[nero_s]

One more question, is there a need to modify WS-Topics-1_3.xsd ?



This would mean I cannot use the Topic interface provided by muse either, since it has no support for xml type of filter. This seems to get a little complex, it will be great if you can give me some initial directions to get started and get it right.

Thanks,
Nero.

Chris Twiner wrote:

There is no direct support for this in Muse.   You can implement
you're own Topic that provides this, returning an empty QName for the
topic interface etc.

Additionally createNotificationMessage in SimpleNotificationProducer
can be overriden to handle the new notificationmessage type.  This
just leaves the processing in the clients / a new
SimpleNotifactionConsumer (to use a different serializer /
MessageHandler).

Be ware that for strict WS-N topic support that you must have a fixed
topic namespace.  If you want to create these dynamically (I'm
guessing so) the standard says to use the empty namespace "" for
dynamic topics.

On 2/6/09, nero_s <[e-mail]> wrote:
>
>  Hi Chris
>  Yes, you're right and thats where am stuck :)
>
>  I want to implement custom Topic, i.e, my Topic would xml content.
>  For example My topic would be :
>
>                 <rim:AdhocQuery
>  id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
>                         <rim:Slot name="$XDSDocumentEntryPatientId">
>                                     :
>                                     :
>                 </rim:AdhocQuery>
>
>
> I am trying to send notification, but currently there is no way to set topic
>  as XML content, on Qname is supported.
>
>  If i can implement this, next step would be to handle topic in my custom
>  filter(IHEFilter).
>
>  Is it possible to have xml as topic?
>
>  Thanks
>  nero
>
>
>
>
>
>  Chris Twiner wrote:
>  >
>  > Hiya,
>  >
>  > I'm a little confused, you have implemented a non topic based
>  > subscription, ie. it looks at the message contents.  From that
>  > perspective it doesn't matter which topic you publish on.  You could
>  > for example publish on a QName of namespace
>  > urn:ihe:iti:xds-b:pubsub:2008 to signify that its intended only for
>  > that type of subscription.
>  >
>  > You must publish on a topic but all Filters will get called.
>  >
>  > cheers,
>  > Chris
>  >
>  > On 2/6/09, nero_s <[e-mail]> wrote:
>  >>
>  >>  ok, some progress, i got my subscriptions to work, now i want to
>  >> implement a
>  >>  notification publisher. But am stuck here, since muse uses
>  >>  SimpleNotificationMessage which supports only concrete dialect and
>  >> topicName
>  >>  as QName, i want to publish send Notify which will have
>  >>  Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content :
>  >>  <rim:AdhocQuery id="urn .....
>  >>
>  >>  Need some directions on where to start, thanks in advance...
>  >>
>  >> --
>  >>  View this message in context:
>  >> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21868551.html
>  >>
>  >> Sent from the Muse User mailing list archive at Nabble.com.
>  >>
>  >>
>  >
>  >
>
>
> --
>  View this message in context: http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21872536.html
>
> Sent from the Muse User mailing list archive at Nabble.com.
>
>

[Chris Twiner]

No its supported by the standard, any topic can have additional xml
elements the only requirement is that there is a qname that matches
it.

On 2/7/09, nero_s <shailesh.soliwal@...> wrote:

>
>  One more question, is there a need to modify WS-Topics-1_3.xsd ?
>
>
>
>
>  nero_s wrote:
>  >
>  > This would mean I cannot use the Topic interface provided by muse either,
>  > since it has no support for xml type of filter. This seems to get a little
>  > complex, it will be great if you can give me some initial directions to
>  > get started and get it right.
>  >
>  > Thanks,
>  > Nero.
>  >
>  >
>  > Chris Twiner wrote:
>  >>
>  >> There is no direct support for this in Muse.   You can implement
>  >> you're own Topic that provides this, returning an empty QName for the
>  >> topic interface etc.
>  >>
>  >> Additionally createNotificationMessage in SimpleNotificationProducer
>  >> can be overriden to handle the new notificationmessage type.  This
>  >> just leaves the processing in the clients / a new
>  >> SimpleNotifactionConsumer (to use a different serializer /
>  >> MessageHandler).
>  >>
>  >> Be ware that for strict WS-N topic support that you must have a fixed
>  >> topic namespace.  If you want to create these dynamically (I'm
>  >> guessing so) the standard says to use the empty namespace "" for
>  >> dynamic topics.
>  >>
>  >> On 2/6/09, nero_s <shailesh.soliwal@...> wrote:
>  >>>
>  >>>  Hi Chris
>  >>>  Yes, you're right and thats where am stuck :)
>  >>>
>  >>>  I want to implement custom Topic, i.e, my Topic would xml content.
>  >>>  For example My topic would be :
>  >>>
>  >>>                 <rim:AdhocQuery
>  >>>  id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
>  >>>                         <rim:Slot name="$XDSDocumentEntryPatientId">
>  >>>                                     :
>  >>>                                     :
>  >>>                 </rim:AdhocQuery>
>  >>>
>  >>>
>  >>> I am trying to send notification, but currently there is no way to set
>  >>> topic
>  >>>  as XML content, on Qname is supported.
>  >>>
>  >>>  If i can implement this, next step would be to handle topic in my
>  >>> custom
>  >>>  filter(IHEFilter).
>  >>>
>  >>>  Is it possible to have xml as topic?
>  >>>
>  >>>  Thanks
>  >>>  nero
>  >>>
>  >>>
>  >>>
>  >>>
>  >>>
>  >>>  Chris Twiner wrote:
>  >>>  >
>  >>>  > Hiya,
>  >>>  >
>  >>>  > I'm a little confused, you have implemented a non topic based
>  >>>  > subscription, ie. it looks at the message contents.  From that
>  >>>  > perspective it doesn't matter which topic you publish on.  You could
>  >>>  > for example publish on a QName of namespace
>  >>>  > urn:ihe:iti:xds-b:pubsub:2008 to signify that its intended only for
>  >>>  > that type of subscription.
>  >>>  >
>  >>>  > You must publish on a topic but all Filters will get called.
>  >>>  >
>  >>>  > cheers,
>  >>>  > Chris
>  >>>  >
>  >>>  > On 2/6/09, nero_s <shailesh.soliwal@...> wrote:
>  >>>  >>
>  >>>  >>  ok, some progress, i got my subscriptions to work, now i want to
>  >>>  >> implement a
>  >>>  >>  notification publisher. But am stuck here, since muse uses
>  >>>  >>  SimpleNotificationMessage which supports only concrete dialect and
>  >>>  >> topicName
>  >>>  >>  as QName, i want to publish send Notify which will have
>  >>>  >>  Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content :
>  >>>  >>  <rim:AdhocQuery id="urn .....
>  >>>  >>
>  >>>  >>  Need some directions on where to start, thanks in advance...
>  >>>  >>
>  >>>  >> --
>  >>>  >>  View this message in context:
>  >>>  >>
>  >>> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21868551.html
>  >>>  >>
>  >>>  >> Sent from the Muse User mailing list archive at Nabble.com.
>  >>>  >>
>  >>>  >>
>  >>>  >
>  >>>  >
>  >>>
>  >>>
>  >>> --
>  >>>  View this message in context:
>  >>> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21872536.html
>  >>>
>  >>> Sent from the Muse User mailing list archive at Nabble.com.
>  >>>
>  >>>
>  >>
>  >>
>  >
>  >
>
>  --
>
> View this message in context: http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21887434.html
>
> Sent from the Muse User mailing list archive at Nabble.com.
>
>

[Chris Twiner]

I don't see why you can't use it.  To be honest if the Topic interface
doesn't fit for what you want then you probably can't use
WS-Notification as a standard and therefore twisting Muse to do it
probably won't help either.

While the standard allows for extra elements to be added it still
requires that Topics fit that kind of interface.  They must belong to
a topic namespace and they must have the ability to nest.

On 2/7/09, nero_s <shailesh.soliwal@...> wrote:

>
>  This would mean I cannot use the Topic interface provided by muse either,
>  since it has no support for xml type of filter. This seems to get a little
>  complex, it will be great if you can give me some initial directions to get
>  started and get it right.
>
>  Thanks,
>  Nero.
>
>
>
>  Chris Twiner wrote:
>  >
>  > There is no direct support for this in Muse.   You can implement
>  > you're own Topic that provides this, returning an empty QName for the
>  > topic interface etc.
>  >
>  > Additionally createNotificationMessage in SimpleNotificationProducer
>  > can be overriden to handle the new notificationmessage type.  This
>  > just leaves the processing in the clients / a new
>  > SimpleNotifactionConsumer (to use a different serializer /
>  > MessageHandler).
>  >
>  > Be ware that for strict WS-N topic support that you must have a fixed
>  > topic namespace.  If you want to create these dynamically (I'm
>  > guessing so) the standard says to use the empty namespace "" for
>  > dynamic topics.
>  >
>  > On 2/6/09, nero_s <shailesh.soliwal@...> wrote:
>  >>
>  >>  Hi Chris
>  >>  Yes, you're right and thats where am stuck :)
>  >>
>  >>  I want to implement custom Topic, i.e, my Topic would xml content.
>  >>  For example My topic would be :
>  >>
>  >>                 <rim:AdhocQuery
>  >>  id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
>  >>                         <rim:Slot name="$XDSDocumentEntryPatientId">
>  >>                                     :
>  >>                                     :
>  >>                 </rim:AdhocQuery>
>  >>
>  >>
>  >> I am trying to send notification, but currently there is no way to set
>  >> topic
>  >>  as XML content, on Qname is supported.
>  >>
>  >>  If i can implement this, next step would be to handle topic in my custom
>  >>  filter(IHEFilter).
>  >>
>  >>  Is it possible to have xml as topic?
>  >>
>  >>  Thanks
>  >>  nero
>  >>
>  >>
>  >>
>  >>
>  >>
>  >>  Chris Twiner wrote:
>  >>  >
>  >>  > Hiya,
>  >>  >
>  >>  > I'm a little confused, you have implemented a non topic based
>  >>  > subscription, ie. it looks at the message contents.  From that
>  >>  > perspective it doesn't matter which topic you publish on.  You could
>  >>  > for example publish on a QName of namespace
>  >>  > urn:ihe:iti:xds-b:pubsub:2008 to signify that its intended only for
>  >>  > that type of subscription.
>  >>  >
>  >>  > You must publish on a topic but all Filters will get called.
>  >>  >
>  >>  > cheers,
>  >>  > Chris
>  >>  >
>  >>  > On 2/6/09, nero_s <shailesh.soliwal@...> wrote:
>  >>  >>
>  >>  >>  ok, some progress, i got my subscriptions to work, now i want to
>  >>  >> implement a
>  >>  >>  notification publisher. But am stuck here, since muse uses
>  >>  >>  SimpleNotificationMessage which supports only concrete dialect and
>  >>  >> topicName
>  >>  >>  as QName, i want to publish send Notify which will have
>  >>  >>  Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content :
>  >>  >>  <rim:AdhocQuery id="urn .....
>  >>  >>
>  >>  >>  Need some directions on where to start, thanks in advance...
>  >>  >>
>  >>  >> --
>  >>  >>  View this message in context:
>  >>  >>
>  >> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21868551.html
>  >>  >>
>  >>  >> Sent from the Muse User mailing list archive at Nabble.com.
>  >>  >>
>  >>  >>
>  >>  >
>  >>  >
>  >>
>  >>
>  >> --
>  >>  View this message in context:
>  >> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21872536.html
>  >>
>  >> Sent from the Muse User mailing list archive at Nabble.com.
>  >>
>  >>
>  >
>  >
>
>
> --
>  View this message in context: http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21887144.html
>
> Sent from the Muse User mailing list archive at Nabble.com.
>
>

[nero_s]

Hi Chris,
Thanks for the comments.
The Topic interface accepts only QName's, and lets say if i have to create Topic, how will I add a topic of type Element, which has its own structure similar to what i had posted earlier?

I am trying to create a IHENotificationMessage(similar to SimpleNotificationMessage) and unable to represent Topic in the XML. It will be great if you can tell me how i can do that.

Chris Twiner wrote:

I don't see why you can't use it.  To be honest if the Topic interface
doesn't fit for what you want then you probably can't use
WS-Notification as a standard and therefore twisting Muse to do it
probably won't help either.

While the standard allows for extra elements to be added it still
requires that Topics fit that kind of interface.  They must belong to
a topic namespace and they must have the ability to nest.

On 2/7/09, nero_s <[e-mail]> wrote:
>
>  This would mean I cannot use the Topic interface provided by muse either,
>  since it has no support for xml type of filter. This seems to get a little
>  complex, it will be great if you can give me some initial directions to get
>  started and get it right.
>
>  Thanks,
>  Nero.
>
>
>
>  Chris Twiner wrote:
>  >
>  > There is no direct support for this in Muse.   You can implement
>  > you're own Topic that provides this, returning an empty QName for the
>  > topic interface etc.
>  >
>  > Additionally createNotificationMessage in SimpleNotificationProducer
>  > can be overriden to handle the new notificationmessage type.  This
>  > just leaves the processing in the clients / a new
>  > SimpleNotifactionConsumer (to use a different serializer /
>  > MessageHandler).
>  >
>  > Be ware that for strict WS-N topic support that you must have a fixed
>  > topic namespace.  If you want to create these dynamically (I'm
>  > guessing so) the standard says to use the empty namespace "" for
>  > dynamic topics.
>  >
>  > On 2/6/09, nero_s <[e-mail]> wrote:
>  >>
>  >>  Hi Chris
>  >>  Yes, you're right and thats where am stuck :)
>  >>
>  >>  I want to implement custom Topic, i.e, my Topic would xml content.
>  >>  For example My topic would be :
>  >>
>  >>                 <rim:AdhocQuery
>  >>  id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
>  >>                         <rim:Slot name="$XDSDocumentEntryPatientId">
>  >>                                     :
>  >>                                     :
>  >>                 </rim:AdhocQuery>
>  >>
>  >>
>  >> I am trying to send notification, but currently there is no way to set
>  >> topic
>  >>  as XML content, on Qname is supported.
>  >>
>  >>  If i can implement this, next step would be to handle topic in my custom
>  >>  filter(IHEFilter).
>  >>
>  >>  Is it possible to have xml as topic?
>  >>
>  >>  Thanks
>  >>  nero
>  >>
>  >>
>  >>
>  >>
>  >>
>  >>  Chris Twiner wrote:
>  >>  >
>  >>  > Hiya,
>  >>  >
>  >>  > I'm a little confused, you have implemented a non topic based
>  >>  > subscription, ie. it looks at the message contents.  From that
>  >>  > perspective it doesn't matter which topic you publish on.  You could
>  >>  > for example publish on a QName of namespace
>  >>  > urn:ihe:iti:xds-b:pubsub:2008 to signify that its intended only for
>  >>  > that type of subscription.
>  >>  >
>  >>  > You must publish on a topic but all Filters will get called.
>  >>  >
>  >>  > cheers,
>  >>  > Chris
>  >>  >
>  >>  > On 2/6/09, nero_s <[e-mail]> wrote:
>  >>  >>
>  >>  >>  ok, some progress, i got my subscriptions to work, now i want to
>  >>  >> implement a
>  >>  >>  notification publisher. But am stuck here, since muse uses
>  >>  >>  SimpleNotificationMessage which supports only concrete dialect and
>  >>  >> topicName
>  >>  >>  as QName, i want to publish send Notify which will have
>  >>  >>  Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content :
>  >>  >>  <rim:AdhocQuery id="urn .....
>  >>  >>
>  >>  >>  Need some directions on where to start, thanks in advance...
>  >>  >>
>  >>  >> --
>  >>  >>  View this message in context:
>  >>  >>
>  >> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21868551.html
>  >>  >>
>  >>  >> Sent from the Muse User mailing list archive at Nabble.com.
>  >>  >>
>  >>  >>
>  >>  >
>  >>  >
>  >>
>  >>
>  >> --
>  >>  View this message in context:
>  >> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21872536.html
>  >>
>  >> Sent from the Muse User mailing list archive at Nabble.com.
>  >>
>  >>
>  >
>  >
>
>
> --
>  View this message in context: http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21887144.html
>
> Sent from the Muse User mailing list archive at Nabble.com.
>
>

[Chris Twiner]

I am truly sorry but I don't have enough time to help in more detail.
The Topic interface does indeed use QNames but you can change the
surrounding ws-n code to not use them.

This does seem like it should be an interface breaking enhancement fo
2.3 (drop the QName requirement from the base interface). Additionally
adding ExtraElements to the interface should be done.  I'll think
about it but any changes will likely be over 6 months away.

Just to explain further, I am no longer being paid to work on Muse or
any WS-* related techs. I am trying, at the very least, to get version
2.2.1 out and push upstream all the fixes and enhancements I have.
I.e. this is driven from free time only.

On Tue, Feb 10, 2009 at 7:09 AM, nero_s <shailesh.soliwal@...> wrote:

>
> Hi Chris,
> Thanks for the comments.
> The Topic interface accepts only QName's, and lets say if i have to create
> Topic, how will I add a topic of type Element, which has its own structure
> similar to what i had posted earlier?
>
> I am trying to create a IHENotificationMessage(similar to
> SimpleNotificationMessage) and unable to represent Topic in the XML. It will
> be great if you can tell me how i can do that.
>
>
>
>
> Chris Twiner wrote:
>>
>> I don't see why you can't use it.  To be honest if the Topic interface
>> doesn't fit for what you want then you probably can't use
>> WS-Notification as a standard and therefore twisting Muse to do it
>> probably won't help either.
>>
>> While the standard allows for extra elements to be added it still
>> requires that Topics fit that kind of interface.  They must belong to
>> a topic namespace and they must have the ability to nest.
>>
>> On 2/7/09, nero_s <shailesh.soliwal@...> wrote:
>>>
>>>  This would mean I cannot use the Topic interface provided by muse
>>> either,
>>>  since it has no support for xml type of filter. This seems to get a
>>> little
>>>  complex, it will be great if you can give me some initial directions to
>>> get
>>>  started and get it right.
>>>
>>>  Thanks,
>>>  Nero.
>>>
>>>
>>>
>>>  Chris Twiner wrote:
>>>  >
>>>  > There is no direct support for this in Muse.   You can implement
>>>  > you're own Topic that provides this, returning an empty QName for the
>>>  > topic interface etc.
>>>  >
>>>  > Additionally createNotificationMessage in SimpleNotificationProducer
>>>  > can be overriden to handle the new notificationmessage type.  This
>>>  > just leaves the processing in the clients / a new
>>>  > SimpleNotifactionConsumer (to use a different serializer /
>>>  > MessageHandler).
>>>  >
>>>  > Be ware that for strict WS-N topic support that you must have a fixed
>>>  > topic namespace.  If you want to create these dynamically (I'm
>>>  > guessing so) the standard says to use the empty namespace "" for
>>>  > dynamic topics.
>>>  >
>>>  > On 2/6/09, nero_s <shailesh.soliwal@...> wrote:
>>>  >>
>>>  >>  Hi Chris
>>>  >>  Yes, you're right and thats where am stuck :)
>>>  >>
>>>  >>  I want to implement custom Topic, i.e, my Topic would xml content.
>>>  >>  For example My topic would be :
>>>  >>
>>>  >>                 <rim:AdhocQuery
>>>  >>  id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
>>>  >>                         <rim:Slot name="$XDSDocumentEntryPatientId">
>>>  >>                                     :
>>>  >>                                     :
>>>  >>                 </rim:AdhocQuery>
>>>  >>
>>>  >>
>>>  >> I am trying to send notification, but currently there is no way to
>>> set
>>>  >> topic
>>>  >>  as XML content, on Qname is supported.
>>>  >>
>>>  >>  If i can implement this, next step would be to handle topic in my
>>> custom
>>>  >>  filter(IHEFilter).
>>>  >>
>>>  >>  Is it possible to have xml as topic?
>>>  >>
>>>  >>  Thanks
>>>  >>  nero
>>>  >>
>>>  >>
>>>  >>
>>>  >>
>>>  >>
>>>  >>  Chris Twiner wrote:
>>>  >>  >
>>>  >>  > Hiya,
>>>  >>  >
>>>  >>  > I'm a little confused, you have implemented a non topic based
>>>  >>  > subscription, ie. it looks at the message contents.  From that
>>>  >>  > perspective it doesn't matter which topic you publish on.  You
>>> could
>>>  >>  > for example publish on a QName of namespace
>>>  >>  > urn:ihe:iti:xds-b:pubsub:2008 to signify that its intended only
>>> for
>>>  >>  > that type of subscription.
>>>  >>  >
>>>  >>  > You must publish on a topic but all Filters will get called.
>>>  >>  >
>>>  >>  > cheers,
>>>  >>  > Chris
>>>  >>  >
>>>  >>  > On 2/6/09, nero_s <shailesh.soliwal@...> wrote:
>>>  >>  >>
>>>  >>  >>  ok, some progress, i got my subscriptions to work, now i want to
>>>  >>  >> implement a
>>>  >>  >>  notification publisher. But am stuck here, since muse uses
>>>  >>  >>  SimpleNotificationMessage which supports only concrete dialect
>>> and
>>>  >>  >> topicName
>>>  >>  >>  as QName, i want to publish send Notify which will have
>>>  >>  >>  Dialect="urn:ihe:iti:xds-b:pubsub:2008" and topic as xml content
>>> :
>>>  >>  >>  <rim:AdhocQuery id="urn .....
>>>  >>  >>
>>>  >>  >>  Need some directions on where to start, thanks in advance...
>>>  >>  >>
>>>  >>  >> --
>>>  >>  >>  View this message in context:
>>>  >>  >>
>>>  >>
>>> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21868551.html
>>>  >>  >>
>>>  >>  >> Sent from the Muse User mailing list archive at Nabble.com.
>>>  >>  >>
>>>  >>  >>
>>>  >>  >
>>>  >>  >
>>>  >>
>>>  >>
>>>  >> --
>>>  >>  View this message in context:
>>>  >>
>>> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21872536.html
>>>  >>
>>>  >> Sent from the Muse User mailing list archive at Nabble.com.
>>>  >>
>>>  >>
>>>  >
>>>  >
>>>
>>>
>>> --
>>>  View this message in context:
>>> http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21887144.html
>>>
>>> Sent from the Muse User mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/How-to-create-a-custom-dialect-for-TopicExpression-tp21847884p21928257.html
> Sent from the Muse User mailing list archive at Nabble.com.
>
>