« Return to Thread: How to create a custom dialect for TopicExpression
Re: How to create a custom dialect for TopicExpression
by Chris Twiner
::
Rate this Message:
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.
>
>
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.
>
>
« Return to Thread: How to create a custom dialect for TopicExpression
| Free embeddable forum powered by Nabble | Forum Help |
