Do you think you can post an example of the xml exchange?
On 4/30/13 7:46 PM, Alex O'Ree wrote:
I recently discovered that the subscription API has a plugin type system that let's system owners extend jUDDI to push notifications via other outlets. The default ones that come with jUDDI are for the UDDI v3 subscription callback API and for email based alerts. I wanted to make a sample projects to demonstrate out how use it and the best use case I came up with was to use Apache Qpid. It's an AMQP implementation, which is basically a publish and subscribe system. The use case is that jUDDI would publish subscription updates to a specific Qpid server for a specific Qpid exchange (such as a topic, queue, etc). The question is, should jUDDI be configured for a single Qpid server and the exchange be defined as the bindingTemplate Access Point, or should the bindingTemplate represent the URL to a Qpid server and some how define the exchange name else where? So to summarize, per subscription url + exchange, or per subscription exchange only
