JavaBeans technology is the component architecture for the Java 2 Platform, Standard Edition (J2SE). Components (JavaBeans) are reusable software programs that you can develop and assemble easily to create sophisticated applications. JavaBeans technology is based on the JavaBeans specification (Definition by Sun Microsystems)
JavaServer Faces technology simplifies building user interfaces for JavaServer applications. With the well-defined programming model that JavaServer Faces provides, developers of varying skill levels can quickly and easily build web applications by: assembling reusable UI components in a page, connecting these components to an application data source, and wiring client-generated events to server-side event handlers. With the power of JavaServer Faces technology, these web applications handle all of the complexity of managing the user interface on the server, allowing the application developer to focus on application code. (Definition by Sun Microsystems)
The MVC paradigm is a way of breaking an application, or even just a piece of an application's interface, into three parts: the model, the view, and the controller. MVC was originally developed to map the traditional input, processing, output roles into the GUI realm:
Input – Processing – Output
Controller – Model – View
The user input, the modeling of the external world, and the visual feedback to the user are separated and handled by model, viewport and controller objects. The controller interprets mouse and keyboard inputs from the user and maps these user actions into commands that are sent to the model and/or viewport to effect the appropriate change. The model manages one or more data elements, responds to queries about its state, and responds to instructions to change state. The viewport manages a rectangular area of the display and is responsible for presenting data to the user through a combination of graphics and text. (Definition by OOTIPS.org)
RPC is a powerful technique for constructing distributed, client-server based applications. It is based on extending the notion of conventional, or local procedure calling, so that the called procedure need not exist in the same address space as the calling procedure. The two processes may be on the same system, or they may be on different systems with a network connecting them. By using RPC, programmers of distributed applications avoid the details of the interface with the network. The transport independence of RPC isolates the application from the physical and logical elements of the data communications mechanism and allows the application to use a variety of transports. (Definition by Dave Marshall)
SOA: Service-oriented Architecture
A service-oriented architecture is essentially a collection of services. These services communicate with each other. The communication can involve either simple data passing or it could involve two or more services coordinating some activity. Some means of connecting services to each other is needed. (Definition by Service Architecture.com)
SOAP: Simple Object Access Protocol
SOAP provides the definition of the XML-based information which can be used for exchanging structured and typed information between peers in a decentralized, distributed environment. A SOAP message is formally specified as an XML Infoset, which provides an abstract description of its contents. Infosets can have different on-the-wire representations, one common example of which is as an XML 1.0 document. (Definition by W3C)
UDDI: Universal Description, Discovery and Integration
The Universal Description, Discovery and Integration (UDDI) protocol is one of the major building blocks required for successful web services. UDDI creates a standard interoperable platform that enables companies and applications to quickly, easily, and dynamically find and use Web services over the Internet. UDDI also allows operational registries to be maintained for different purposes in different contexts. UDDI is a cross-industry effort driven by major platform and software providers, as well as marketplace operators and e-business leaders within the OASIS standards consortium. (Definition by OASIS)
An alternative definition can be found on the JISC pages:
UDDI is an initiative lead by Ariba, IBM and Microsoft for developing a global registry of web services. It recognises that in order for an electronic marketplace to succeed there needs to be a mechanism for the discovery of relevant electronic services. It provides a directory, with a simple discovery interface for use by developers and computer systems, and mechanisms for describing the computer interfaces a client application would use to communicate with that service. Brokers would make use of this directory service in locating relevant electronic services for the user and interacting with them on the users’ behalf. Unlike previous endeavours (such as X.500, DAP and LDAP), it is addressing the non-technical issues in that UDDI also includes an initiative to building a single global registry with support from over 250 industrial partners. (Definition by JISC)
uPortal is a framework for producing a campus portal. We don't intend it to be an out-of-the-box or 'turn key' portal 'solution'. Instead, uPortal is a set of Java classes and XML/XSL documents that you can use to produce a portal for use on your campus. (Definition by JA-SIG)
WSDL: Web Service Description Language
WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what message formats or network protocols are used to communicate, however, the only bindings described in this document describe how to use WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME. (Definition by W3C)
WSRP: Web Service for Remote Portlets
WSRP is a standard for interactive, presentation-oriented web services. It is a web services protocol for aggregating content and interactive web applications from remote sources. (Definition by OASIS)
WSS is a technical foundation for implementing security functions such as integrity and confidentiality in messages implementing higher-level Web services applications. (Definition by OASIS)
Extensible Markup Language (XML) is a simple, very flexible text format derived from SGML (ISO 8879). Originally designed to meet the challenges of large-scale electronic publishing, XML is also playing an increasingly important role in the exchange of a wide variety of data on the Web and elsewhere. (Definition by W3C)
© Internet Archaeology/Author(s)
University of York legal statements | Terms and Conditions
| File last updated: Tue Sep 27 2005