J2EE deployment files (ejb-jar.xml)

j2ee|xml

<ejb-jar>
The ejb-jar element is the root element of the EJB deployment descriptor. It contains an optional description of the ejb-jar file, optional display name, optional small icon file name, optional large icon file name, mandatory structural information about all included enterprise beans, optional application-assembly descriptor, and an optional name of an ejb-client-jar file for the ejb-jar.

<description>A short description</description>
A short description.

<display-name>A name</display-name>
The display-name element contains a short name that is intended to be display by tools.

<small-icon>employee-service-icon16x16.jpg</small-icon>
The small-icon element contains the name of a file containing a small (16 x 16) icon image. The file name is relative path within the ejb-jar file. The image must be either in the JPEG or GIF format, and the file name must end with the suffix ".jpg" or ".gif" respectively. The icon can be used by tools.

<large-icon>employee-service-icon32x32.jpg</large-icon>
The large-icon element contains the name of a file containing a large (32 x 32) icon image. The file name is relative path within the ejb-jar file. The image must be either in the JPEG or GIF format, and the file name must end with the suffix ".jpg" or ".gif" respectively. The icon can be used by tools.

<enterprise-beans>
The enterprise-beans element contains the declarations of one or more enterprise beans.

<session>
The session element declares an session bean. The declaration consists of: an optional description; optional display name; optional small icon file name; optional large icon file name; a name assigned to the enterprise bean in the deployment description; the names of the session bean's home and remote interfaces; the session bean's implementation class; the session bean's state management type; the session bean's transaction management type; an optional declaration of the bean's environment entries; an optional declaration of the bean's EJB references; an optional declaration of the security role references; and an optional declaration of the bean's resource factory references. The elements that are optional are "optional" in the sense that they are omitted when if lists represented by them are empty.

<description>A short description</description>
A short description.

<display-name>A name</display-name>
The display-name element contains a short name that is intended to be display by tools.

<small-icon>employee-service-icon16x16.jpg</small-icon>
The small-icon element contains the name of a file containing a small (16 x 16) icon image. The file name is relative path within the ejb-jar file. The image must be either in the JPEG or GIF format, and the file name must end with the suffix ".jpg" or ".gif" respectively. The icon can be used by tools.

<large-icon>employee-service-icon32x32.jpg</large-icon>
The large-icon element contains the name of a file containing a large (32 x 32) icon image. The file name is relative path within the ejb-jar file. The image must be either in the JPEG or GIF format, and the file name must end with the suffix ".jpg" or ".gif" respectively. The icon can be used by tools.

<ejb-name>EmployeeService</ejb-name>
The ejb-name element specifies an enterprise bean's name. This name is assigned by the ejb-jar file producer to name the enterprise bean in the ejb-jar file's deployment descriptor. The name must be unique among the names of the enterprise beans in the same ejb-jar file. The enterprise bean code does not depend on the name; therefore the name can be changed during the application-assembly process without breaking the enterprise bean's function. There is no architected relationship between the ejb-name in the deployment descriptor and the JNDI name that the Deployer will assign to the enterprise bean's home. The name must conform to the lexical rules for an NMTOKEN.

<home>com.aardvark.payroll.PayrollHome</home>
The home element contains the fully-qualified name of the enterprise bean's home interface.

<remote>com.wombat.empl.EmployeeService</remote>
The remote element contains the fully-qualified name of the enterprise bean's remote interface.

<ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
The ejb-class element contains the fully-qualified name of the enterprise bean's class.

<session-type>Stateful/Stateless</session-type>
The session-type element describes whether the session bean is a stateful session, or stateless session. The session-type element must be one of the two following: Stateful or Stateless.

<transaction-type>Bean/Container</transaction-type>
The transaction-type element must be one of the two following: Bean or Container.

<env-entry>
The env-entry element contains the declaration of an enterprise bean's environment entries. The declaration consists of an optional description, the name of the environment entry, and an optional value.

<description>A short description</description>
A short description.

<env-entry-name>minAmount</env-entry-name>
The env-entry-name element contains the name of an enterprise bean's environment entry.

<env-entry-type>java.lang.String</env-entry-type>
The env-entry-type element contains the fully-qualified Java type of the environment entry value that is expected by the enterprise bean's code. The following are the legal values of env-entry-type: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, and java.lang.Float.

<env-entry-value>100.00</env-entry-value>
The env-entry-value element contains the value of an enterprise bean's environment entry.

<ejb-ref>
The ejb-ref element is used for the declaration of a reference to another enterprise bean's home. The declaration consists of an optional description; the EJB reference name used in the code of the referencing enterprise bean; the expected type of the referenced enterprise bean; the expected home and remote interfaces of the referenced enterprise bean; and an optional ejb-link information. The optional ejb-link element is used to specify the referenced enterprise bean. It is used typically in ejb-jar files that contain an assembled application.

<description>A short description</description>
A short description.

<ejb-ref-name>ejb/Payroll</ejb-ref-name>
The ejb-ref-name element contains the name of an EJB reference. The EJB reference is an entry in the enterprise bean's environment. It is recommended that name is prefixed with "ejb/".

<ejb-ref-type>Entity/Session</ejb-ref-type>
The ejb-ref-type element contains the expected type of the referenced enterprise bean. The ejb-ref-type element must be one of the following: Entity Session

<home>com.aardvark.payroll.PayrollHome</home>
The home element contains the fully-qualified name of the enterprise bean's home interface.

<remote>com.wombat.empl.EmployeeService</remote>
The remote element contains the fully-qualified name of the enterprise bean's remote interface.

<ejb-link>EmployeeRecord</ejb-link>
The ejb-link element is used in the ejb-ref element to specify that an EJB reference is linked to another enterprise bean in the ejb-jar file. The value of the ejb-link element must be the ejb-name of an enterprise bean in the same ejb-jar file, or in another ejb-jar file in the same J2EE application unit.

<security-role-ref>
The security-role-ref element contains the declaration of a security role reference in the enterprise bean's code. The declaration consists of an optional description, the security role name used in the code, and an optional link to a defined security role. The value of the role-name element must be the String used as the parameter to the EJBContext.isCallerInRole(String roleName) method. The value of the role-link element must be the name of one of the security roles defined in the security-role elements.

<description>A short description</description>
A short description.

<role-name>name</role-name>
The role-name element contains the name of a security role. The name must conform to the lexical rules for an NMTOKEN.

<role-link>name</role-link>
The role-link element is used to link a security role reference to a defined security role. The role-link element must contain the name of one of the security roles defined in the security-role elements.

<resource-ref>
The resource-ref element contains a declaration of enterprise bean's reference to an external resource. It consists of an optional description, the resource factory reference name, the indication of the resource factory type expected by the enterprise bean code, and the type of authentication (bean or container).

<description>A short description</description>
A short description.

<res-ref-name>name</res-ref-name>
The res-ref-name element specifies the name of a resource factory reference.

<res-type>javax.sql.DataSource</res-type>
The res-type element specifies the type of the data source. The type is specified by the Java interface (or class) expected to be implemented by the data source.

<res-auth>Application/Container</res-auth>
The res-auth element specifies whether the enterprise bean code signs on programmatically to the resource manager, or whether the Container will sign on to the resource manager on behalf of the bean. In the latter case, the Container uses information that is supplied by the Deployer. The value of this element must be one of the two following: Application or Container

<entity>
The entity element declares an entity bean. The declaration consists of: an optional description; optional display name; optional small icon file name; optional large icon file name; a name assigned to the enterprise bean in the deployment descriptor; the names of the entity bean's home and remote interfaces; the entity bean's implementation class; the entity bean's persistence management type; the entity bean's primary key class name; an indication of the entity bean's reentrancy; an optional list of container-managed fields; an optional specification of the primary key field; an optional declaration of the bean's environment entries; an optional declaration of the bean's EJB references; an optional declaration of the security role references; and an optional declaration of the bean's resource factory references. The optional primkey-field may be present in the descriptor if the entity's persistency-type is Container. The other elements that are optional are "optional" in the sense that they are omitted if the lists represented by them are empty. At least one cmp-field element must be present in the descriptor if the entity's persistency-type is Container, and none must not be present if the entity's persistence-type is Bean.

<description>A short description</description>
A short description.

<display-name>A name</display-name>
The display-name element contains a short name that is intended to be display by tools.

<small-icon>employee-service-icon16x16.jpg</small-icon>
The small-icon element contains the name of a file containing a small (16 x 16) icon image. The file name is relative path within the ejb-jar file. The image must be either in the JPEG or GIF format, and the file name must end with the suffix ".jpg" or ".gif" respectively. The icon can be used by tools.

<large-icon>employee-service-icon32x32.jpg</large-icon>
The large-icon element contains the name of a file containing a large (32 x 32) icon image. The file name is relative path within the ejb-jar file. The image must be either in the JPEG or GIF format, and the file name must end with the suffix ".jpg" or ".gif" respectively. The icon can be used by tools.

<ejb-name>EmployeeService</ejb-name>
The ejb-name element specifies an enterprise bean's name. This name is assigned by the ejb-jar file producer to name the enterprise bean in the ejb-jar file's deployment descriptor. The name must be unique among the names of the enterprise beans in the same ejb-jar file. The enterprise bean code does not depend on the name; therefore the name can be changed during the application-assembly process without breaking the enterprise bean's function. There is no architected relationship between the ejb-name in the deployment descriptor and the JNDI name that the Deployer will assign to the enterprise bean's home. The name must conform to the lexical rules for an NMTOKEN.

<home>com.aardvark.payroll.PayrollHome</home>
The home element contains the fully-qualified name of the enterprise bean's home interface.

<remote>com.wombat.empl.EmployeeService</remote>
The remote element contains the fully-qualified name of the enterprise bean's remote interface.

<ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
The ejb-class element contains the fully-qualified name of the enterprise bean's class.

<persistence-type>Bean/Container</persistence-type>
The persistence-type element specifies an entity bean's persistence management type. The persistence-type element must be one of the two following: Bean or Container.

<prim-key-class>com.wombat.empl.EmployeeID</prim-key-class>
The prim-key-class element contains the fully-qualified name of an entity bean's primary key class. If the definition of the primary key class is deferred to deployment time, the prim-key-class element should specify java.lang.Object.

<reentrant>True/False</reentrant>
The reentrant element specifies whether an entity bean is reentrant or not. The reentrant element must be one of the two following: True or False

<cmp-field>
The cmp-field element describes a container-managed field. The field element includes an optional description of the field, and the name of the field.

<description>A short description</description>
A short description.

<field-name>firstName</field-name>
The field-name element specifies the name of a container managed field. The name must be a public field of the enterprise bean class or one of its superclasses.

<primkey-field>fieldName</primkey-field>
The primkey-field element is used to specify the name of the primary key field for an entity with container-managed persistence. The primkey-field must be one of the fields declared in the cmp-field element, and the type of the field must be the same as the primary key type. The primkey-field element is not used if the primary key maps to multiple container-managed fields (i.e. the key is a compound key). In this case, the fields of the primary key class must be public, and their names must correspond to the field names of the entity bean class that comprise the key.

<env-entry>
The env-entry element contains the declaration of an enterprise bean's environment entries. The declaration consists of an optional description, the name of the environment entry, and an optional value.

<description>A short description</description>
A short description.

<env-entry-name>minAmount</env-entry-name>
The env-entry-name element contains the name of an enterprise bean's environment entry.

<env-entry-type>java.lang.String</env-entry-type>
The env-entry-type element contains the fully-qualified Java type of the environment entry value that is expected by the enterprise bean's code. The following are the legal values of env-entry-type: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, and java.lang.Float.

<env-entry-value>100.00</env-entry-value>
The env-entry-value element contains the value of an enterprise bean's environment entry.

<ejb-ref>
The ejb-ref element is used for the declaration of a reference to another enterprise bean's home. The declaration consists of an optional description; the EJB reference name used in the code of the referencing enterprise bean; the expected type of the referenced enterprise bean; the expected home and remote interfaces of the referenced enterprise bean; and an optional ejb-link information. The optional ejb-link element is used to specify the referenced enterprise bean. It is used typically in ejb-jar files that contain an assembled application.

<description>A short description</description>
A short description.

<ejb-ref-name>ejb/Payroll</ejb-ref-name>
The ejb-ref-name element contains the name of an EJB reference. The EJB reference is an entry in the enterprise bean's environment. It is recommended that name is prefixed with "ejb/".

<ejb-ref-type>Entity/Session</ejb-ref-type>
The ejb-ref-type element contains the expected type of the referenced enterprise bean. The ejb-ref-type element must be one of the following: Entity Session

<home>com.aardvark.payroll.PayrollHome</home>
The home element contains the fully-qualified name of the enterprise bean's home interface.

<remote>com.wombat.empl.EmployeeService</remote>
The remote element contains the fully-qualified name of the enterprise bean's remote interface.

<ejb-link>EmployeeRecord</ejb-link>
The ejb-link element is used in the ejb-ref element to specify that an EJB reference is linked to another enterprise bean in the ejb-jar file. The value of the ejb-link element must be the ejb-name of an enterprise bean in the same ejb-jar file, or in another ejb-jar file in the same J2EE application unit.

<security-role-ref>
The security-role-ref element contains the declaration of a security role reference in the enterprise bean's code. The declaration consists of an optional description, the security role name used in the code, and an optional link to a defined security role. The value of the role-name element must be the String used as the parameter to the EJBContext.isCallerInRole(String roleName) method. The value of the role-link element must be the name of one of the security roles defined in the security-role elements.

<description>A short description</description>
A short description.

<role-name>name</role-name>
The role-name element contains the name of a security role. The name must conform to the lexical rules for an NMTOKEN.

<role-link>name</role-link>
The role-link element is used to link a security role reference to a defined security role. The role-link element must contain the name of one of the security roles defined in the security-role elements.

<resource-ref>
The resource-ref element contains a declaration of enterprise bean's reference to an external resource. It consists of an optional description, the resource factory reference name, the indication of the resource factory type expected by the enterprise bean code, and the type of authentication (bean or container).

<description>A short description</description>
A short description.

<res-ref-name>name</res-ref-name>
The res-ref-name element specifies the name of a resource factory reference.

<res-type>javax.sql.DataSource</res-type>
The res-type element specifies the type of the data source. The type is specified by the Java interface (or class) expected to be implemented by the data source.

<res-auth>Application/Container</res-auth>
The res-auth element specifies whether the enterprise bean code signs on programmatically to the resource manager, or whether the Container will sign on to the resource manager on behalf of the bean. In the latter case, the Container uses information that is supplied by the Deployer. The value of this element must be one of the two following: Application or Container

<assembly-descriptor>
The assembly-descriptor element contains application-assembly information. The application-assembly information consists of the following parts: the definition of security roles, the definition of method permissions, and the definition of transaction attributes for enterprise beans with container-managed transaction demarcation. All the parts are optional in the sense that they are omitted if the lists represented by them are empty. Providing an assembly-descriptor in the deployment descriptor is optional for the ejb-jar file producer.

<security-role>
The security-role element contains the definition of a security role. The definition consists of an optional description of the security role, and the security role name.

<description>A short description</description>
A short description.

<role-name>name</role-name>
The role-name element contains the name of a security role. The name must conform to the lexical rules for an NMTOKEN.

<method-permission>
The method-permission element specifies that one or more security roles are allowed to invoke one or more enterprise bean methods. The method-permission element consists of an optional description, a list of security role names, and a list of method elements. The security roles used in the method-permission element must be defined in the security-role element of the deployment descriptor, and the methods must be methods defined in the enterprise bean's remote and/or home interfaces.

<description>A short description</description>
A short description.

<role-name>name</role-name>
The role-name element contains the name of a security role. The name must conform to the lexical rules for an NMTOKEN.

<method>
1. <method>
<ejb-name>EJBNAME</ejb-name>
<method-name>*</method-name>
</method>

This style is used to refer to all the methods of the specified
enterprise bean's home and remote interfaces.

2. <method>
<ejb-name>EJBNAME</ejb-name>
<method-name>METHOD</method-name>
</method>>

This style is used to refer to the specified method of the
specified enterprise bean. If there are multiple methods with
the same overloaded name, the element of this style refers to
all the methods with the overloaded name.

3. <method>
<ejb-name>EJBNAME</ejb-name>
<method-name>METHOD</method-name>
<method-params>
<method-param>PARAM-1</method-param>
<method-param>PARAM-2</method-param>
...
<method-param>PARAM-n</method-param>
</method-params>
<method>

This style is used to refer to a single method within a set of
methods with an overloaded name. PARAM-1 through PARAM-n are the
fully-qualified Java types of the method's input parameters (if
the method has no input arguments, the method-params element
contains no method-param elements). Arrays are specified by the
array element's type, followed by one or more pair of square
brackets (e.g. int[][]).

<description>A short description</description>
A short description.

<ejb-name>EmployeeService</ejb-name>
The ejb-name element specifies an enterprise bean's name. This name is assigned by the ejb-jar file producer to name the enterprise bean in the ejb-jar file's deployment descriptor. The name must be unique among the names of the enterprise beans in the same ejb-jar file. The enterprise bean code does not depend on the name; therefore the name can be changed during the application-assembly process without breaking the enterprise bean's function. There is no architected relationship between the ejb-name in the deployment descriptor and the JNDI name that the Deployer will assign to the enterprise bean's home. The name must conform to the lexical rules for an NMTOKEN.

<method-intf>Home/Remote</method-intf>
The method-intf element allows a method element to differentiate between the methods with the same name and signature that are defined in both the remote and home interfaces. The method-intf element must be one of the following: Home or Remote.

<method-name>nameOfMethod</method-name>
The method-name element contains a name of an enterprise bean method, or the asterisk (*) character. The asterisk is used when the element denotes all the methods of an enterprise bean's remote and home interfaces.

<method-params>
The method-params element contains a list of the fully-qualified Java type names of the method parameters.

<method-param>int[]</method-param>
The method-param element contains the fully-qualified Java type name of a method parameter.

<container-transaction>
The container-transaction element specifies how the container must manage transaction scopes for the enterprise bean's method invocations. The element consists of an optional description, a list of method elements, and a transaction attribute.The transaction attribute is to be applied to all the specified methods.

<description>A short description</description>
A short description.

<method>
1. >method< >ejb-name<EJBNAME>/ejb-name< >method-name<*>/method-name< >/method< This style is used to refer to all the methods of the specified enterprise bean's home and remote interfaces. 2. >method< >ejb-name<EJBNAME>/ejb-name< >method-name<METHOD>/method-name< >/method<< This style is used to refer to the specified method of the specified enterprise bean. If there are multiple methods with the same overloaded name, the element of this style refers to all the methods with the overloaded name. 3. >method< >ejb-name<EJBNAME>/ejb-name< >method-name<METHOD>/method-name< >method-params< >method-param<PARAM-1>/method-param< >method-param<PARAM-2>/method-param< ... >method-param<PARAM-n>/method-param< >/method-params< >method< This style is used to refer to a single method within a set of methods with an overloaded name. PARAM-1 through PARAM-n are the fully-qualified Java types of the method's input parameters (if the method has no input arguments, the method-params element contains no method-param elements). Arrays are specified by the array element's type, followed by one or more pair of square brackets (e.g. int[][]).

<description>A short description</description>
A short description.

<ejb-name>EmployeeService</ejb-name>
The ejb-name element specifies an enterprise bean's name. This name is assigned by the ejb-jar file producer to name the enterprise bean in the ejb-jar file's deployment descriptor. The name must be unique among the names of the enterprise beans in the same ejb-jar file. The enterprise bean code does not depend on the name; therefore the name can be changed during the application-assembly process without breaking the enterprise bean's function. There is no architected relationship between the ejb-name in the deployment descriptor and the JNDI name that the Deployer will assign to the enterprise bean's home. The name must conform to the lexical rules for an NMTOKEN.

<method-intf>Home/Remote</method-intf>
The method-intf element allows a method element to differentiate between the methods with the same name and signature that are defined in both the remote and home interfaces. The method-intf element must be one of the following: Home or Remote.

<method-name>nameOfMethod</method-name>
The method-name element contains a name of an enterprise bean method, or the asterisk (*) character. The asterisk is used when the element denotes all the methods of an enterprise bean's remote and home interfaces.

<method-params>
The method-params element contains a list of the fully-qualified Java type names of the method parameters.

<method-param>int[]</method-param>
The method-param element contains the fully-qualified Java type name of a method parameter.

<trans-attribute>Supports</trans-attribute>
The trans-attribute element specifies how the container must manage the transaction boundaries when delegating a method invocation to an enterprise bean's business method. The value of trans-attribute must be one of the following: NotSupported, Supports, Required, RequiresNew, Mandatory or Never

<ejb-client-jar>employee_service_client.jar</ejb-client-jar>
The optional ejb-client-jar element specifies a JAR file that contains the class files necessary for a client program to access the enterprise beans in the ejb-jar file. The Deployer should make the ejb-client JAR file accessible to the client's class-loader.

时间: 2024-10-03 23:04:20

J2EE deployment files (ejb-jar.xml)的相关文章

J2EE deployment files(ejb-jar2.0.xml)

j2ee|xml <ejb-jar> The ejb-jar element is the root element of the EJB deployment descriptor. It contains an optional description of the ejb-jar file, optional display name, optional small icon file name, optional large icon file name, mandatory stru

J2EE deployment files(web.xml)

j2ee|web|xml <web-app> This file contains the configuration for a web-application. <icon> The icon element contains a small-icon and a large-icon element which specify the location within the web application for a small and large image used to

J2EE deployment files (application.xml)

application|j2ee|xml <application> The application element is the root element of a J2EE application deployment descriptor. <icon> The icon element contains a small-icon and a large-icon element which specify the location within the applicatio

J2EE deployment files(application-client.xml)

application|client|j2ee|xml <application-client> The application-client element is the root element of an application client deployment descriptor. The application client deployment descriptor describes the EJB components and external resources refe

J2EE核心之EJB

  EJB作为EJB是sun的JavaEE服务器端组件模型,设计目标与核心应用是部署分布式应用程序.简单来说就是把已经编写好的程序(即:类)打包放在服务器上执行.凭借java跨平台的优势,用EJB技术部署的分布式系统可以不限于特定的平台.EJB (Enterprise JavaBean)是J2EE(javaEE)的一部分,定义了一个用于开发基于组件的企业多重应用程序的标准.   目前主要是用的是EJB3,与EJB2相比EJB3是JavaEE平台遇到了Dot NET平台之后的反击,也可以认为是Ja

J2EE基础之EJB全面了解_java

1.什么是EJB?  EJB(Enterprise Java Beans),是JavaEE中的商业应用组件技术,是JavaEE三大组件(Servlet,JSP,EJB)之一.EJB提供了让客户端使用远程分布式对象的框架,极大地简化了具有良好的可扩充性的企业级应用的开发.EJB组件结构是基于组件的分布式计算结构,是分布式应用系统中的组件. EJB是Java服务器端服务框架的规范,为服务器端构件系统定义了一个技术规范.该规范能提供一个标准的.分布式的.基于面向对象的体系结构.它为构件开发者和使用者屏

J2EE中使用Spring AOP框架和EJB组件

j2ee 快速发展的开发人员社区.对各种后端技术(包括JMS.JTA.JDO.Hibernate.iBATIS等等)的支持,以及(更为重要的)非侵入性的轻量级IoC容器和内置的AOP运行时,这些因素使得Spring Framework对于J2EE应用程序开发十分具有吸引力.Spring托管的组件(POJO)可以与EJB共存,并允许使用AOP方法来处理企业应用程序中的横切方面--从监控和审计.缓存及应用程序级的安全性开始,直到处理特定于应用程序的业务需求. 本文将向您介绍Spring的AOP框架在

XML和J2EE的完美结合

j2ee|xml 当前,Java 2平台企业版(J2EE)架构在厂商市场和开发者社区中倍受推崇.作为一种工具,可扩展标记语言(XML)简化了数据交换.进程间消息交换这一类的事情,因而对开发者逐渐变得有吸引力,并开始流行起来.自然,在J2EE架构中访问或集成XML解决方案的想法也很诱人.因为这将是强大系统架构同高度灵活的数据管理方案的结合.  XML的应用似乎是无穷无尽的,但它们大致上可以分为三大类:  ●简单数据的表示和交换(针对XML的简单API(SAX)和文档对象模型(DOM)语法解析,不同

XML和J2EE的组合技术

j2ee|xml 当前,Java 2平台企业版(J2EE)架构在厂商市场和开发者社区中倍受推崇.作为一种工具,可扩展标记语言(XML)简化了数据交换.进程间消息交换这一类的事情,因而对开发者逐渐变得有吸引力,并开始流行起来.自然,在J2EE架构中访问或集成XML解决方案的想法也很诱人.因为这将是强大系统架构同高度灵活的数据管理方案的结合.     XML的应用似乎是无穷无尽的,但它们大致上可以分为三大类:    * 简单数据的表示和交换(针对XML的简单API(SAX)和文档对象模型(DOM)语