Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

How does Web Services relate to Java Technology?

 
Stephen Wei
Ranch Hand
Posts: 73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello everyone, this forum is not very active yet, maybe because many people like me have not got a clue about this topic and never worked on Web services before.
As a start I want to ask a question. How does the Web services thing relate to Java technology? For example: Is Soap/XMl a competing technology for Java/Servlet/JSP? When we make Web services application, in Soap/XML or other things, do we still need Java? Do Web Services and Java technology depend on each other?
I am a baby in this field, Thanks!
------------------
Sun Certified Programmer for Java Platform
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, they do depend on each other. SOAP is a way of communicating from program to program. However, you still have to write the programs. Java is perfect for that. However, you can use Perl, Visual Basic, Visual C++ or whatever else you like too. That's part of the beauty of it. SOAP and Web Services allow programs written in many different languages to communicate transparently (like CORBA promised but never lived up to).
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13077
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As far as competition between servlets/JSP versus SOAP / XML-RPC goes, I don't think they compete directly. Servlets/JSP are all about data presentation and SOAP is all about data communication.
Here is my view of how you might create a web service - this service would present a customized view of certain kinds of data for your customers. Say for instance, a combination of agricultural commodity prices, stocks of certain companies and current weather information. Your service would use SOAP to grab data from a variety of sources in background processes, then present a composite to your customer in a customized JSP view.
There are an awful lot of resources for SOAP, XML and related topics out there. I have some listed at this page: http://www.lanw.com/books/javasoap/
Bill
(Currently working on a SOAP book for Java programmers)
 
faisal mahmood
Ranch Hand
Posts: 349
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Please correct me if I am wrong.
I think it is both language and platform independant.
Now a days any new standard comes out falls to one of the
above category.
Faisal
 
Andy Rodriguez
Ranch Hand
Posts: 95
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by William Brogden:
As far as competition between servlets/JSP versus SOAP / XML-RPC goes, I don't think they compete directly. Servlets/JSP are all about data presentation and SOAP is all about data communication.
Here is my view of how you might create a web service - this service would present a customized view of certain kinds of data for your customers. Say for instance, a combination of agricultural commodity prices, stocks of certain companies and current weather information. Your service would use SOAP to grab data from a variety of sources in background processes, then present a composite to your customer in a customized JSP view.
There are an awful lot of resources for SOAP, XML and related topics out there. I have some listed at this page: http://www.lanw.com/books/javasoap/
Bill
(Currently working on a SOAP book for Java programmers)

Agreed , but i think we need to emphasise more on UDDI as well , its more than just getting info for presentation purposes , it could be more of a middleware oriented approach. Also other point worth mentioning is that of the capability of SOAP and webservices - Its capable of doing more than just getting weather info or stock quote . Stock quote / weather info is probably the "hello world" app of the Soap world .
To emphasise this further - The concept of SOAP-UDDI / webservices is not something that was thought of in the past couple of months , the underlying concept is the same as that of EDI.
Typical usage of Webservices from a business perspective will obviously be in the digital marketplace scenario , supply chain etc .,
More on EDI here : http://www.webopedia.com/TERM/E/EDI.html
Note to self � The total sum of my 0.02$ contributions so far has exceeded 20.00$ �hmmm..


------------------
My ramblings @
http://javarecon.tripod.com
 
Tiger Scott
Ranch Hand
Posts: 223
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The short answer to what webservices is- it is B2B eCommerce- XML/SOAP/WDDI/WSDL/ etc being the enabling technologies.
Sanjay
[This message has been edited by Sanjay Bahal (edited November 06, 2001).]
 
anne lai
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree that soap/uddi/wsdl/ebXML will replace the legacy middleware like CORBA/COM over time. But what about RMI in java side? Thanks.
Anne
 
Michael Dean
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From what I've seen, the Web Services model using UDDI, SOAP, WSDL provides arguable advantages in terms of network/transport:
Security/firewall: by using a text-based protocol such as SOAP over HTTP, all traffic can go over port 80 (normally, firewalls limit port access)...this infers several things:
1) Maintaining a of port numbers between producer/consumer not required
2) A single "pinch point" for control of network traffic. Running from behind a firewall becomes much less of a security issue
3) text-based traffic is easily monitored (Note: HTTP messages *can* contain binary streams coded directly into the document using Base 64 encoding)
>Complete with servlet/JSP?
Eventually, it may compete but right now it can complement. Because only one browser(to my knowledge) parses XML and it is buggy (msxml.dll), the standard approach is to use XML as a platform-neutral data format processed @ the servlet layer, which then renders HTML to the GUI layer. The Servlet/JSP model is not precluded when XML is simply the p/n data format. Thus, you still write your servlets in Java...with XML you get a neutral data format and with SOAP, you get a special type of HTTP/MIME "message type for XML-tagged data interchange.
Best Regards,
Michael Dean
Sun Certified Programmer for the Java 2 Platform
OMNI Project
Washington State Department of Corrections
 
faisal mahmood
Ranch Hand
Posts: 349
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi michael,
>Complete with servlet/JSP?
How can it compete with servlet/JSPs. They are web technologies for presentation purposes on the web browsers.
SOAP and webservices are for different purposes. I know that you can to XML-RPC style transfers with servlets - but that's different story all together
Faisal
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic