Yeah, UDDI is one of those fancy recursive protocols. It is all simply SOAP, so XEP-0072 should work fine. The only thing is that you would need a well-known JID to work against it (so you would need an <item/> node). After that everything works using LUIDs/GUIDs and SOAP/XEP-0072. Following the discovery of UDDI there is no longer any need for extensions to XMPP for SOAP service discovery: I think it presents a rather neat entry point.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Saint-Andre Sent: Monday, August 11, 2008 8:49 PM To: Jabber/XMPP software development list Subject: Re: [jdev] Eventing and SOAP Jonathan Dickinson wrote: > Hi All, > > > > I am looking at the integration points for my server now (specifically > into the product that my employer develops). It is a workflow solution > (www.k2.net <http://www.k2.net>), and I am trying to figure out the > best way to notify users that they have work in such as way that: > > > > 1. IM clients apart from our own still tell the user that they > have work. A Sharepoint web address or such would be given in the body > of the message. > > 2. Our IM client detects that an agent (mobile agent > <http://en.wikipedia.org/wiki/Mobile_agent>) is present in the stanza > and fires it up instead of giving the user the message. > > > > My thoughts are to simply do the following: > > <message from="worklist.k2workflow.com" to="[EMAIL PROTECTED]" > type="message"> > > <body>You have work. Visit > http://www.denallix.com/workitem.aspx?uid=12345abc</body> > > <agent xmlns="urn:com:k2:agent"><!-- Agent description XML here > --></agent> > > </message> > > > > I need to know if any clients would possibly have problems with a > stanza in that form, or maybe if someone has a better idea :). Thanks in > advance. That should be just fine. > AND... I also gave some more thought to SOAP and a nice clean <pun> way > to implement discovery within a jabber context alone. I thought of > using UDDI over XMPP (as it is itself a SOAP standard), this is merely > a suggestion, but how about the following: > > > > <iq type='result' > > from='shakespeare.lit' > > to='[EMAIL PROTECTED]/orchard' > > id='info1'> > > <query xmlns='http://jabber.org/protocol/disco#items'> > > <item jid='uddi.shakespeare.lit' > > node='uddi' > > name='SOAP discovery service'/> > > <item jid='[EMAIL PROTECTED]' > > node='urn:myservices:foo' > > name='Some service'/> > > </query> > > </iq> > > > > My syntax may all be wrong, but I am sure you get the idea. The client > could the start doing UDDI calls against the uddi.shakespeare.lit node. > Also (as demonstrated) the server can broadcast any SOAP services it > supports upfront. UDDI? Ick. But if you must, it seems fine to advertise the existence of UDDI services over XMPP -- we could define a new disco identity for that and register it here: http://www.xmpp.org/registrar/disco-categories.html I suggest the "directory/uddi" identity. Once you discover such a service, how would you interact with it? Is that just straight SOAP as in XEP-0072? Peter _______________________________________________ JDev mailing list FAQ: http://www.jabber.org/discussion-lists/jdev-faq Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [EMAIL PROTECTED] _______________________________________________
