Some building adjust.
[i18n-zh.git] / cauchy / JavaEE / 1.3 / slee-deployable-unit_1_0.dtd
blobbf7aec70a58bb7e5b0fd247bb48aab2de90f56ca
1 <?xml version="1.0" encoding="ISO-8859-1"?>
3 <!--
4 This is the XML DTD for the JAIN SLEE 1.0 deployable unit jar file deployment
5 descriptor. All JAIN SLEE 1.0 deployable unit jar file deployment descriptors
6 must include a DOCTYPE of the following form:
8 <!DOCTYPE deployable-unit PUBLIC
9 "-//Sun Microsystems, Inc.//DTD JAIN SLEE Deployable Unit 1.0//EN"
10 "http://java.sun.com/dtd/slee-deployable-unit_1_0.dtd">
11 -->
14 <!--
15 The deployable-unit element is the root element of the deployable unit
16 deployment descriptor. It contains an optional description about the
17 deployable unit jar file and the names of one or more component jars or
18 service deployment descriptors to be installed.
19 -->
20 <!ELEMENT deployable-unit (description?, (jar|service-xml)+)>
22 <!--
23 The description element may contain any descriptive text about the parent
24 element.
26 Used in: deployable-unit
27 -->
28 <!ELEMENT description (#PCDATA)>
30 <!--
31 The jar element contains the name of a component jar file packaged within the
32 deployable unit jar file, to be installed with the deployable unit. The name
33 must be relative URL, relative to the base of the deployable unit jar file.
35 Used in: deployable-unit
37 Example:
38 <jar>components/sbbs.jar</jar>
39 -->
40 <!ELEMENT jar (#PCDATA)>
42 <!--
43 The service-xml element contains the name of a service deployment descriptor
44 file packaged within the deployable unit jar file, and containing the
45 definitions of one or more services to be installed with the deployable unit.
46 The name must be a relative URL, relative to the base of the deployable unit
47 jar file.
49 Used in: deployable-unit
51 Example:
52 <service-xml>services/myservice.xml</service-xml>
53 -->
54 <!ELEMENT service-xml (#PCDATA)>
57 <!--
58 The ID mechanism is to allow tools that produce additional deployment
59 information (ie. information beyond that contained by the standard SLEE
60 deployment descriptors) to store the non-standard information in a separate
61 file, and easily refer from those tools-specific files to the information in
62 the standard deployment descriptor. The SLEE architecture does not allow the
63 tools to add the non-standard information into the SLEE-defined deployment
64 descriptors.
65 -->
66 <!ATTLIST deployable-unit id ID #IMPLIED>
67 <!ATTLIST description id ID #IMPLIED>
68 <!ATTLIST jar id ID #IMPLIED>
69 <!ATTLIST service-xml id ID #IMPLIED>