OOAD Object Oriented Analysis design, objects-oriented analytics and design
JNDI Java naming and directory Interface,java naming and catalog interfaces
JTA Java Transaction API
Distributed transactions (distributed Transaction) include the transaction manager (Transaction Manager) and one or more resource managers (Resource Manager) that support the XA protocol
RPC Remote Procedure call Protocol RPC does not allow transitive objects advantage is cross-language cross-platform
RMI Remote Method invocation remotely object methods call can say RMI is an object-oriented Java RPC, RMI only supports Java
Corrba Common Object Request Broker Architecture, common Object Solicitation Broker architecture, generic object Request Broker architecture, language neutral
RMI and the combination and complementarity of CORBA produces Rmi-iiop , RMI-IIOP is the enterprise server side the foundation of Java Development.
IIOP Internet Inter-ORB Protocol (Internet Internal object Request Proxy protocol), which is a protocol for CORBA 2.0 and compatible platforms
JMS Java Messaging service Java Message Service, the general JMS message is not an XML, but a Java object, it is clear that JMS does not consider heterogeneous systems, frankly speaking, JMS does not consider non-Java things. But fortunately, most of the JMS provider (that is, the various implementations of JMS) solve the heterogeneous problem.
With JMS services, objects are physically asynchronously moved directly from one JVM on the network to another (the message notification mechanism )
The RMI object is bound to the local JVM, and only the function arguments and return values are transmitted over the network (the request answering mechanism ).
JAXP Java API for Xmlprocessing
Two different parsing methods of XML
DOM: Document Object model,w3c is recommended for use.
Features: One-time import of the entire XML into memory, converted to a DOM tree, so the conversion speed is slow, but because of resident memory, so the repeated access is efficient, and can modify the node content.
SAX: Simple API-for-XML, cost-recommended standard, but really XML industry specification.
Features: Sequential parsing, no one-time import, fast conversion, no data to be accessed, repeated access is inefficient (XML needs to be re-parsed), and node content cannot be modified.
Reference article:
http://acooly.iteye.com/blog/1706943
Reference article:
http://visionsky.blog.51cto.com/733317/438693/
This article is from the "bit accumulation" blog, please be sure to keep this source http://tianxingzhe.blog.51cto.com/3390077/1744781
Common confusing concepts in the Java EE