« Return to Thread: How to create a custom dialect for TopicExpression

Re: How to create a custom dialect for TopicExpression

by nero_s :: Rate this Message:

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 <shailesh.soliwal@gmail.com> 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.
>
>

« Return to Thread: How to create a custom dialect for TopicExpression