Hi Doc Manalastas,
1. soap, uddi, wsdl, xml server, webservice, web app server,
SOAP is Simple Object Access Protocol. It's a fancy name for RPC with XML
as envelope (request, and reply formatting). Most implamentations use
HTTP, and SMTP-POP3 combo as data transport.
Now, Microsoft's evolving .NET initiative is betting the farm on SOAP over
HTTP as RPC mechanism (DCOM no more). WebServices is a facade of a
service to the web. Most articles, and .NET evangelists might say a lot
more, but to me it's just some service available for use. e.g. credit card
verification webservice, and daily quote webservice.
WSDL is WebServices Description Language is a standard that describes what
make up a WebService -- it's description, methods, method signatures,
etc. I believe this was added so webservices can be dynamically
discovered by user applications.
UDDI is Universal Description, Discovery and Ingeration. Simply put, it
is a descriptor for WebServices. Kasi, they anticipate WebServices to be
a service-component business where system integrators could pick, and
choose what they need. It's like a DNS of WebServices.
What's interesting to me with the whole webservices space is all the
components are anywhere with in a network, or the internet. It's building
applications where components can be anywhere within a network. There's
more. WebServices is an open stardard (?).. I'm currently doing
WebServices in Java.
Application Servers are just servers where applications can be developed
from. In the J2EE world, application servers provide database connection
pool, various containers (EJB, Servlet, JMS, JNDI, etc), transaction
services, etc. For short, it's just a middleware.
Now, the way I see .NET is, it's Microsoft's stab at the application
services business.
#linear scalability, load-balancing, auto-failover by clustering,
#
Well, You'd probably know those better than I do. ;)
#servlet, jsp, ejb, containers,
#
Servlet or JavaServlet is the J2EE world's CGI. JSP is to ASP in the M$
world. What's interesting is a JSP is just translated to a Servlet source
file then passed to a java compiler to build a Servlet. A Servlet/JSP
container is just an implementation of the Servlet, and JSP
specifications where Servlets, and JSPs live.
Enterprise JavaBean is a framework where server-side components (EJBs) can
be developed from. An EJB container host the EJBs. It provides EJBs
distributed transactions, persistence service, event notification service,
etc.
#model-view controller design paradigm,
#
Bong Munoz (or some who knows SmallTalk) might probably explain this
better.. ;) But I'll take a stab at it. MVC design paradigm is just a
way of designing applications, or components. The view manages the GUI
output (e.g. graph). The controller interprets external actions
(e.g. mouse, keyboard) from say a user, telling the model or the view to
change appropriately. The model manages the data, gives information
about its state to the view, and responds to state change
(setters) requests from the controller.
#struts-jakarta,
#
Struts is an Jakarta-Apache that promotes MVC to web application
development. (http://jakarta.apache.org/structs). It heavily uses
Servlets, and JSPs.
#packaging: *.jar, *.war, *.rar, *.ear
#
A JAR is a Java ARchive where all Java classes, and descrptions (META
file) are packed. It's just a ZIP file with a specific/well-known file
organization. A WAR is Web ARchive where Java web-applications (JAR
files, JSP, Servlets, and settings) can be packaged.
Resource AdapteR (RAR), and Enterpise Application aRchive (EAR) are yet
another packaging formats specific to J2EE. I have not used them.. so I
can't give much about them.
stay cool.
jeff --
--
Jeff Gutierrez
Mapua Online!
http://www.mapua.org
http://www.mapua.com
http://www.mapua.net
Pinoy Ako! May reklamo?
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
