Jon Stevens wrote:
>
> on 8/8/01 9:59 AM, "Berin Loritsch" <[EMAIL PROTECTED]> wrote:
>
> > All the stuff I've read about for WebServices comprise
> > UDDI, SOAP, and WSDL.
> >
> > The three combined provide a way to automatically discover remote resources
> > that my webapp can use and then actually use it.
>
> I'm surprised no one has mentioned JXTA. Where does that fall into this web
> services picture?
>
> <http://www.jxta.org/>
The nebulous definition of a Web Service is:
"A dynamic web resource designed to be accessed and used by applications."
The key part here is "used by applications". If you incorporate pieces of
www.jxta.org into the picture--then that is how you defined your Web Service.
The tools commonly agreed upon (according to the premier Web Services Developer's
Journal [WSDJ] that was included with the next to last JDJ issue) are UDDI, SOAP, and
WSDL. Another part that is required is Schema support (but you knew that already
because UDDI, SOAP, and WSDL either require it or provide methods of specifying it).
The compelling example that was given in WSDJ was a very simple web service to
find out how much any book from Borders would cost in any currency. The cool
part of SOAP and therefore WS is the support for transactions. You can compose
larger WS from smaller ones. The example used two existing WS--one from Borders
that returns the price of a book (specified by ISBN number) in US currency, and
one that converts from one currency to another with the current exchange rates.
The web service that was written took markup that specified the ISBN number and
the resultant currency type you wanted. The web service would create a transaction
that spanned the two other WS calls. First it accessed Border's WS and got the
US price. Then it accessed the exchange rate WS to find the price according to
the desired currency.
That relatively simple example demonstrated why the WS concept is so powerful.
The biggest thing is that this is all done from within applications. Your
front end can be a web page, or a standalone app. They would both function
identically--just with different user interfaces. In fact, you can add your
own web service that uses this example, and will bring up a list of ISBNs and
the cost from a Title.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
