cauchy/JavaEE/1.3/slee-sbb-jar_1_0.dtd

   1 <?xml version="1.0" encoding="ISO-8859-1"?>
   2
   3 <!--
   4 This is the XML DTD for the JAIN SLEE 1.0 sbb component jar file deployment
   5 descriptor.  All JAIN SLEE 1.0 sbb component jar file deployment descriptors
   6 must include a DOCTYPE of the following form:
   7
   8   <!DOCTYPE sbb-jar PUBLIC
   9         "-//Sun Microsystems, Inc.//DTD JAIN SLEE SBB 1.0//EN"
  10         "http://java.sun.com/dtd/slee-sbb-jar_1_0.dtd">
  11 -->
  12
  13
  14 <!--
  15 The sbb-jar element is the root element of the sbb jar deployment descriptor.
  16 In contains an optional description about the sbb jar file and one or more sbb
  17 definitions.
  18 -->
  19 <!ELEMENT sbb-jar (description?, sbb+)>
  20
  21
  22 <!--
  23 The sbb element defines an sbb.  It contains an optional description about the
  24 sbb being defined, the name, vendor, and version of the sbb being defined, an
  25 optional alias for referencing the sbb elsewhere in the deployment descriptor,
  26 zero or more child sbb references, zero or more profile specification
  27 references, mandatory information about the sbb's interfaces and classes, an
  28 optional reference to a profile specification to be used for the sbb's address
  29 profile table, zero or more event entries, zero or more activity context
  30 attribute alias definitions, zero or more JNDI environment entry definitions,
  31 zero or more resource adaptor type bindings, and zero or more EJB references.
  32
  33 Used in: sbb-jar
  34 -->
  35 <!ELEMENT sbb (description?, sbb-name, sbb-vendor, sbb-version, sbb-alias?,
  36           sbb-ref*, profile-spec-ref*, sbb-classes,
  37           address-profile-spec-alias-ref?, event*,
  38           activity-context-attribute-alias*, env-entry*,
  39           resource-adaptor-type-binding*, ejb-ref*)>
  40
  41 <!--
  42 The description element may contain any descriptive text about the parent
  43 element.
  44
  45 Used in: sbb-jar, sbb, activity-context-attribute-alias, cmp-field,
  46          ejb-ref, env-entry, event, get-child-relation-method,
  47          get-profile-cmp-method, profile-spec-ref, sbb-abstract-class,
  48          sbb-activity-context-interface, sbb-classes, sbb-local-interface,
  49          sbb-ref, sbb-usage-parameters-interface,
  50          resource-adaptor-entity-binding, resource-adaptor-type-binding
  51 -->
  52 <!ELEMENT description (#PCDATA)>
  53
  54 <!--
  55 The sbb-name element contains the name of the sbb component.
  56
  57 Used in: sbb
  58
  59 Example:
  60     <sbb-name>MySbb</sbb-name>
  61 -->
  62 <!ELEMENT sbb-name (#PCDATA)>
  63
  64 <!--
  65 The sbb-vendor element contains the vendor of the sbb component.
  66
  67 Used in: sbb
  68
  69 Example:
  70     <sbb-vendor>My Company, Inc.</sbb-vendor>
  71 -->
  72 <!ELEMENT sbb-vendor (#PCDATA)>
  73
  74 <!--
  75 The sbb-version element contains the version of the sbb component.  The
  76 version number typically should have the general form
  77 "major-version.minor-version".
  78
  79 Used in: sbb
  80
  81 Example:
  82     <sbb-version>1.0</sbb-version>
  83 -->
  84 <!ELEMENT sbb-version (#PCDATA)>
  85
  86 <!--
  87 The sbb-alias element contains an arbitrary name that can be used to
  88 reference, elsewhere in the deployment descriptor, the sbb component type
  89 being defined by the parent element.
  90
  91 Used in: sbb, sbb-ref
  92
  93 Example:
  94     <sbb-alias>MySbb</sbb-alias>
  95 -->
  96 <!ELEMENT sbb-alias (#PCDATA)>
  97
  98 <!--
  99 The sbb-alias-ref element contains the name of an sbb component that has been
 100 aliased elsewhere in the enclosing sbb element in the deployment descriptor.
 101
 102 Used in: cmp-field, get-child-relation-method
 103
 104 Example:
 105     <sbb-alias-ref>MySbb</sbb-alias-ref>
 106 -->
 107 <!ELEMENT sbb-alias-ref (#PCDATA)>
 108
 109 <!--
 110 The sbb-ref element declares a reference to an SBB component type and
 111 establishes an alias name to that type.  It contains an optional description
 112 about the reference, the name, vendor, and version of the referenced SBB, and
 113 the alias name for the reference.
 114
 115 Used in: sbb
 116 -->
 117 <!ELEMENT sbb-ref (description?, sbb-name, sbb-vendor, sbb-version,
 118           sbb-alias)>
 119
 120 <!--
 121 The profile-spec-ref element declares a reference to a profile specification
 122 component type and establishes an alias name to that type.  It contains an
 123 optional description about the reference, the name, vendor, and version of the
 124 referenced profile specification, and the alias name for the reference.
 125
 126 Used in: sbb
 127 -->
 128 <!ELEMENT profile-spec-ref (description?, profile-spec-name,
 129           profile-spec-vendor, profile-spec-version, profile-spec-alias)>
 130
 131 <!--
 132 The profile-spec-name element contains the name of a profile specification
 133 component.
 134
 135 Used in: profile-spec-ref
 136
 137 Example:
 138     <profile-spec-name>AddressProfileSpec</profile-spec-name>
 139 -->
 140 <!ELEMENT profile-spec-name (#PCDATA)>
 141
 142 <!--
 143 The profile-spec-vendor element contains the vendor of a profile specification
 144 component.
 145
 146 Used in: profile-spec-ref
 147
 148 Example:
 149     <profile-spec-name>javax.slee</profile-spec-name>
 150 -->
 151 <!ELEMENT profile-spec-vendor (#PCDATA)>
 152
 153 <!--
 154 The profile-spec-version element contains the version of a profile
 155 specification component.
 156
 157 Used in: profile-spec-ref
 158
 159 Example:
 160     <profile-spec-version>1.0</profile-spec-version>
 161 -->
 162 <!ELEMENT profile-spec-version (#PCDATA)>
 163
 164 <!--
 165 The profile-spec-alias element contains an arbitrary name that can be used to
 166 reference, elsewhere in the deployment descriptor, the profile specification
 167 component type identified by the parent element.
 168
 169 Used in: profile-spec-ref
 170
 171 Example:
 172     <profile-spec-alias>AddressProfile</profile-spec-alias>
 173 -->
 174 <!ELEMENT profile-spec-alias (#PCDATA)>
 175
 176 <!--
 177 The sbb-classes element contains an optional description about the classes and
 178 interfaces defined, a mandatory sbb abstract class declaration, an optional
 179 sbb local interface declaration, an optional sbb activity context interface
 180 declaration, and an optional sbb usage parameters interface declaration.
 181
 182 Used in: sbb
 183 -->
 184 <!ELEMENT sbb-classes (description?, sbb-abstract-class, sbb-local-interface?,
 185           sbb-activity-context-interface?, sbb-usage-parameters-interface?)>
 186
 187 <!--
 188 The sbb-abstract-class element contains an optional description about the sbb
 189 abstract class, the name of the sbb abstract class, zero or more cmp field
 190 declarations, zero or more get-child-relation method declarations, and zero or
 191 more get-profile-cmp method declarations.
 192
 193 The reentrant attribute of this element determines whether reentrant callbacks
 194 on the sbb abstract class are permitted.  A reentrant callback occurs when an
 195 sbb entity invokes a method on an sbb local interface object which causes,
 196 either directly or indirectly, a method on the original sbb entity to be
 197 invoked in the same transaction.  The default value of this attribute is
 198 False.
 199
 200 Used in: sbb-classes
 201 -->
 202 <!ELEMENT sbb-abstract-class (description?, sbb-abstract-class-name,
 203           cmp-field*, get-child-relation-method*, get-profile-cmp-method*)>
 204
 205 <!--
 206 The sbb-abstract-class-name contains the fully-qualified name of the sbb
 207 abstract class that implements the sbb.
 208
 209 Used in: sbb-classes
 210
 211 Example:
 212     <sbb-abstract-class-name>com.mycompany.sbb.MySbb</sbb-abstract-class-name>
 213 -->
 214 <!ELEMENT sbb-abstract-class-name (#PCDATA)>
 215
 216 <!--
 217 The cmp-field element declares a cmp field defined in the sbb abstract class.
 218 It contains an optional description, the name of the cmp field, and an
 219 optional sbb alias reference.  The sbb alias reference is required if the cmp
 220 field stores sbb local object references.
 221
 222 Used in: sbb-abstract-class
 223 -->
 224 <!ELEMENT cmp-field (description?, cmp-field-name, sbb-alias-ref?)>
 225
 226 <!--
 227 The cmp-field-name element contains the name of a cmp field defined in the sbb
 228 abstract class.
 229
 230 Used in: cmp-field
 231
 232 Example:
 233     <cmp-field-name>count</cmp-field-name>
 234 -->
 235 <!ELEMENT cmp-field-name (#PCDATA)>
 236
 237 <!--
 238 The get-child-relation-method element declares a get-child-relation method
 239 defined in the sbb abstract class.  It contains an optional description, a
 240 reference to the sbb component type of the child sbb, the name of the
 241 get-child-relation method, and a default priority for the child sbb.
 242
 243 Used in: sbb-abstract-class
 244 -->
 245 <!ELEMENT get-child-relation-method (description?, sbb-alias-ref,
 246           get-child-relation-method-name, default-priority)>
 247
 248 <!--
 249 The get-child-relation-method-name element contains the name of a
 250 get-child-relation method defined in the sbb abstract class.
 251
 252 Used in: get-child-relation-method
 253
 254 Example:
 255     <get-child-relation-method-name>
 256         getChildRelation
 257     </get-child-relation-method-name>
 258 -->
 259 <!ELEMENT get-child-relation-method-name (#PCDATA)>
 260
 261 <!--
 262 The default-priority element contains the default priority of a child sbb.
 263 The default priority must lie in the range -128 thru 127.
 264
 265 Used in: get-child-relation-method
 266
 267 Example:
 268     <default-priority>0</default-priority>
 269 -->
 270 <!ELEMENT default-priority (#PCDATA)>
 271
 272 <!--
 273 The get-profile-cmp-method declares a get-profile-cmp method defined in the
 274 sbb abstract class.  It contains an optional description, a reference to the
 275 profile specification component type expected to be returned from the method,
 276 and the name of the get-profile-cmp method.
 277
 278 Used in: sbb-abstract-class
 279 -->
 280 <!ELEMENT get-profile-cmp-method (description?, profile-spec-alias-ref,
 281           get-profile-cmp-method-name)>
 282
 283 <!--
 284 The profile-spec-alias-ref element contains the name of a profile
 285 specification component alias that has been defined in a profile-spec element
 286 elsewhere in the enclosing sbb element in the deployment descriptor.
 287
 288 Used in: get-profile-cmp-method
 289
 290 Example:
 291     <profile-spec-alias-ref>AddressProfile</profile-spec-alias-ref>
 292 -->
 293 <!ELEMENT profile-spec-alias-ref (#PCDATA)>
 294
 295 <!--
 296 The get-profile-cmp-method-name element contains the name of a get-profile-cmp
 297 method defined in the sbb-abstract class.
 298
 299 Used in get-profile-cmp-method
 300
 301 Example:
 302     <get-profile-cmp-method-name>getAddressProfile</get-profile-cmp-method-name>
 303 -->
 304 <!ELEMENT get-profile-cmp-method-name (#PCDATA)>
 305
 306 <!--
 307 The sbb-local-interface element contains an optional description about the sbb
 308 local interface and the name of the sbb local interface.
 309
 310 Used in: sbb-classes
 311 -->
 312 <!ELEMENT sbb-local-interface (description?, sbb-local-interface-name)>
 313
 314 <!--
 315 The sbb-local-interface-name element contains the fully-qualified name of the
 316 sbb local interface.
 317
 318 Used in: sbb-local-interface
 319
 320 Example:
 321     <sbb-local-interface-name>
 322         com.mycompany.sbb.MySbbLocal
 323     <sbb-local-interface-name>
 324 -->
 325 <!ELEMENT sbb-local-interface-name (#PCDATA)>
 326
 327 <!--
 328 The sbb-activity-context-interface element contains an optional description
 329 about the activity context interface and the name of the activity context
 330 interface.
 331
 332 Used in: sbb-classes
 333 -->
 334 <!ELEMENT sbb-activity-context-interface (description?,
 335           sbb-activity-context-interface-name)>
 336
 337 <!--
 338 The sbb-activity-context-interface-name element contains the fully-qualified
 339 name of the sbb activity context interface.
 340
 341 Used in: sbb-activity-context-interface
 342
 343 Example:
 344     <sbb-activity-context-interface-name>
 345         com.mycompany.sbb.MySbbActivityContextInterface
 346     </sbb-activity-context-interface-name>
 347 -->
 348 <!ELEMENT sbb-activity-context-interface-name (#PCDATA)>
 349
 350 <!--
 351 The sbb-usage-parameters-interface element declares a usage parameters
 352 interface for the sbb.  It contains an optional description and the name of
 353 the sbb usage parameters interface.
 354
 355 Used in: sbb-classes
 356 -->
 357 <!ELEMENT sbb-usage-parameters-interface (description?,
 358           sbb-usage-parameters-interface-name)>
 359
 360 <!--
 361 The sbb-usage-parameters-interface-name element contains the fully-qualified
 362 name of the sbb usage parameters interface.
 363
 364 Used in: sbb-usage-parameters-interface
 365
 366 Example:
 367     <sbb-usage-parameters-interface-name>
 368         com.mycompany.sbb.MySbbUsageParameters
 369     </sbb-usage-parameters-interface-name>
 370 -->
 371 <!ELEMENT sbb-usage-parameters-interface-name (#PCDATA)>
 372
 373 <!--
 374 The address-profile-spec-alias-ref element contains the name of a profile
 375 specification component alias that has been defined in a profile-spec-ref
 376 element elsewhere in the enclosing sbb element in the deployment descriptor.
 377 It is used to declare the profile specification of the address profile table
 378 used by the sbb.
 379
 380 Used in: sbb
 381
 382 Example:
 383     <address-profile-spec-alias-ref>
 384         AddressProfile
 385     </address-profile-spec-alias-ref>
 386 -->
 387 <!ELEMENT address-profile-spec-alias-ref (#PCDATA)>
 388
 389 <!--
 390 The event element declares an event received, fired, or both, by the sbb.  It
 391 contains an optional description, the name of the event as used by the sbb, a
 392 reference to the event type of the event, zero or more initial event selector
 393 options, an optional initial event selector method name, and an optional
 394 resource option for the event.
 395
 396 The event-direction attribute of this element declares the direction of the
 397 event to and/or from the sbb.  If the event is received by the sbb, the sbb
 398 abstract class must have an event-handler method for it.  If the event is
 399 fired by the sbb, the sbb abstract class must declare an abstract fire-event
 400 method for it.  The initial-event-select, intitial-event-selector-method-name,
 401 and event-resource-option sub-elements may only be included in the event
 402 element if the event-direction attribute indicates that the event is recieved
 403 by the sbb.  A value for this attribute must be specified in the deployment
 404 descriptor.  There is no default value.
 405
 406 The initial-event attribute of this element is only relevant if the
 407 event-direction attribute indicates that the event is recieved by the sbb.  It
 408 declares whether the event is an initial event for the sbb or not.  The
 409 initial-event-select and initial-event-selector-method-name sub-elements may
 410 only be included in the event element if the initial-event attribute is set to
 411 True.  The default value is False.
 412
 413 The mask-on-attach attribute of this element is only relevant if the
 414 event-direction attribute indicates that the event is received by the sbb.  It
 415 declares whether the receipt of the event by the sbb is initially masked on an
 416 activity when the sbb attaches to it.  The default value is False.
 417
 418 Used in: sbb
 419 -->
 420 <!ELEMENT event (description?, event-name, event-type-ref,
 421           initial-event-select*, initial-event-selector-method-name?,
 422           event-resource-option?)>
 423
 424 <!--
 425 The event-name element contains an arbitrary Java identifier that the sbb uses
 426 to refer to the event.  The name of an sbb's event-handler or fire-event
 427 method includes the event name declared here in its construction.
 428
 429 Used in: event
 430
 431 Example:
 432     <event-name>CallCreatedEvent</event-name>
 433 -->
 434 <!ELEMENT event-name (#PCDATA)>
 435
 436 <!--
 437 The event-type-ref element identifies the event type received or fired by the
 438 sbb.  It contains the name, vendor, and version of the event type.
 439
 440 Used in: event
 441 -->
 442 <!ELEMENT event-type-ref (event-type-name, event-type-vendor,
 443           event-type-version)>
 444
 445 <!--
 446 The event-type-name element contains the name of an event type.
 447
 448 Used in: event-type-ref
 449
 450 Example:
 451     <event-type-name>
 452         javax.csapi.cc.jcc.JccCallEvent.CALL_CREATED
 453     </event-type-name>
 454 -->
 455 <!ELEMENT event-type-name (#PCDATA)>
 456
 457 <!--
 458 The event-type-vendor element contains the vendor of an event type.
 459
 460 Used in: event-type-ref
 461
 462 Example:
 463     <event-type-vendor>javax.csapi.cc.jcc</event-type-vendor>
 464 -->
 465 <!ELEMENT event-type-vendor (#PCDATA)>
 466
 467 <!--
 468 The event-type-version element contains the version of an event type.
 469
 470 Used in: event-type-ref
 471
 472 Example:
 473     <event-type-version>1.1</event-type-version>
 474 -->
 475 <!ELEMENT event-type-version (#PCDATA)>
 476
 477 <!--
 478 The initial-event-select element contains no text but defines a variable
 479 attribute.  The variable attribute declares an initial event selector variable
 480 that should be included in the convergence name calculation performed by the
 481 SLEE when considering an initial event for a service's root sbb.
 482
 483 Used in: event
 484
 485 Example:
 486     <initial-event-select variable="ActivityContext" />
 487 -->
 488 <!ELEMENT initial-event-select EMPTY>
 489
 490 <!--
 491 The initial-event-selector-method-name contains the name of an initial event
 492 selector method defined in the sbb abstract class.
 493
 494 Used in: event
 495
 496 Example:
 497     <initial-event-selector-method-name>
 498         initialEventSelect
 499     </initial-event-selector-method-name>
 500 -->
 501 <!ELEMENT initial-event-selector-method-name (#PCDATA)>
 502
 503 <!--
 504 The event-resource-option element contains arbitary event handling options
 505 that the SLEE can forward to resource adaptor entities that emit the enclosing
 506 event element's event type.  The format of the element contents is typically
 507 specified by a resource adaptor vendor.
 508
 509 Used in: event
 510
 511 Example:
 512     <event-resource-option>block</event-resource-option>
 513 -->
 514 <!ELEMENT event-resource-option (#PCDATA)>
 515
 516 <!--
 517 The activity-context-attribute-alias element allows an sbb to alias activity
 518 context attributes.  Aliasing an attribute causes it to become available in a
 519 global namespace public to all sbbs.  The element contains an optional
 520 description, the attribute alias name, and the names of zero or more
 521 attributes in the sbb's activity context interface that should be aliased to
 522 the given name.
 523
 524 Used in: sbb
 525 -->
 526 <!ELEMENT activity-context-attribute-alias (description?,
 527           attribute-alias-name, sbb-activity-context-attribute-name*)>
 528
 529 <!--
 530 The attribute-alias-name element contains the aliased name of an activity
 531 context attribute.
 532
 533 Used in: activity-context-attribute-alias
 534
 535 Example:
 536     <attribute-alias-name>count</attribute-alias-name>
 537 -->
 538 <!ELEMENT attribute-alias-name (#PCDATA)>
 539
 540 <!--
 541 The sbb-activity-context-attribute-name element contains the name of an
 542 attribute in the sbb's activity context interface.
 543
 544 Used in: activity-context-attribute-alias
 545
 546 Example:
 547     <attribute-alias-name>forwardCount</attribute-alias-name>
 548 -->
 549 <!ELEMENT sbb-activity-context-attribute-name (#PCDATA)>
 550
 551 <!--
 552 The env-entry element declares a constant that should be bound into the sbb's
 553 JNDI environment.  It contains an optional description, the name and type of
 554 the constant, and an optional value.  If a value is not specified, one must be
 555 supplied during deployment.
 556
 557 Used in: sbb
 558 -->
 559 <!ELEMENT env-entry (description?, env-entry-name, env-entry-type,
 560           env-entry-value?)>
 561
 562 <!--
 563 The env-entry-name element contains the namespace path, relative to the
 564 java:comp/env context, where the environment entry constant should be bound in
 565 the sbb's JNDI environment.
 566
 567 Used in: env-entry
 568
 569 Example
 570     <env-entry-name>maxConnections</env-entry-name>
 571 -->
 572 <!ELEMENT env-entry-name (#PCDATA)>
 573
 574 <!--
 575 The env-entry-type element contains the fully-qualifed name of the class of an
 576 sbb's environment entry constant.
 577
 578 The following are the legal values of the env-entry-type element:
 579 java.lang.Integer, java.lang.Double, java.lang.Boolean, java.lang.Character,
 580 java.lang.Byte, java.lang.Short, java.lang.Long, and java.lang.Float,
 581 java.lang.String.
 582
 583 Used in: env-entry
 584
 585 Example:
 586     <env-entry-type>java.lang.Integer</env-entry-type>
 587 -->
 588 <!ELEMENT env-entry-type (#PCDATA)>
 589
 590 <!--
 591 The env-entry-value element contains the value of an sbb's environment entry
 592 contant.  The value must be a string that is valid for the constructor of the
 593 environment entry's declared type that takes a single java.lang.String
 594 parameter, or for java.lang.Character environment entry types, a single
 595 character.
 596
 597 Used in: env-entry
 598
 599 Example:
 600     <env-entry-value>5</env-entry>
 601 -->
 602 <!ELEMENT env-entry-value (#PCDATA)>
 603
 604 <!--
 605 The resource-adaptor-type-binding element declares bindings between an sbb and
 606 external resources.  It contains an optional description, a mandatory
 607 reference to a resource adaptor type, an optional name where the resource
 608 adaptor type's activity context interface object will be bound in the sbb's
 609 JNDI environment, and zero or more resource adaptor entity bindings.
 610
 611 Used in: sbb
 612 -->
 613 <!ELEMENT resource-adaptor-type-binding (description?,
 614           resource-adaptor-type-ref,
 615           activity-context-interface-factory-name?,
 616           resource-adaptor-entity-binding*)>
 617
 618 <!--
 619 The resource-adaptor-type-ref element declares the resource adaptor type the
 620 sbb is binding to.  It contains an optional description and the name, vendor,
 621 and version of the resource adaptor type.
 622
 623 Used in: resource-adaptor-type-binding
 624 -->
 625 <!ELEMENT resource-adaptor-type-ref (resource-adaptor-type-name,
 626           resource-adaptor-type-vendor, resource-adaptor-type-version)>
 627
 628 <!--
 629 The resource-adaptor-type-name element contains the name of a resource adaptor
 630 type component.
 631
 632 Used in: resource-adaptor-type-ref
 633
 634 Example:
 635     <resource-adaptor-type-name>JCC</resource-adaptor-type-name>
 636 -->
 637 <!ELEMENT resource-adaptor-type-name (#PCDATA)>
 638
 639 <!--
 640 The resource-adaptor-type-vendor element contains the vendor of a resource
 641 adaptor type component.
 642
 643 Used in: resource-adaptor-type-ref
 644
 645 Example:
 646     <resource-adaptor-type-vendor>
 647         javax.csapi.cc.jcc
 648     </resource-adaptor-type-vendor>
 649 -->
 650 <!ELEMENT resource-adaptor-type-vendor (#PCDATA)>
 651
 652 <!--
 653 The resource-adaptor-type-version element contains the version of a resource
 654 adaptor type component.
 655
 656 Used in: resource-adaptor-type-ref
 657
 658 Example:
 659     <resource-adaptor-type-version>1.1</resource-adaptor-type-version>
 660 -->
 661 <!ELEMENT resource-adaptor-type-version (#PCDATA)>
 662
 663 <!--
 664 The activity-context-interface-factory-name element contains the namespace
 665 path, relative to the java:comp/env context, where the activity context
 666 interface factory object of the corresponding resource adaptor type should be
 667 bound in the sbb's JNDI environment.
 668
 669 Used in: resource-adaptor-type-binding
 670
 671 Example:
 672     <activity-context-interface-factory-name>
 673         slee/resources/jcc/acifactory
 674     </activity-context-interface-factory-name>
 675 -->
 676 <!ELEMENT activity-context-interface-factory-name (#PCDATA)>
 677
 678 <!--
 679 The resource-adaptor-entity-binding element allows an sbb to bind to a
 680 resource adaptor entity.  It contains an optional description, the JNDI name
 681 where the resource adaptor entity's resource adaptor interface object should
 682 be bound in the sbb's environment, and an optional resource adaptor entity
 683 link name.  If the resource adaptor entity link name is not specified, one
 684 must be supplied during deployment.
 685
 686 Used in: resource-adaptor-type-binding
 687 -->
 688 <!ELEMENT resource-adaptor-entity-binding (description?,
 689           resource-adaptor-object-name, resource-adaptor-entity-link?)>
 690
 691 <!--
 692 The resource-adaptor-object-name element contains the namespace path, relative
 693 to the java:comp/env context, where the resource adaptor entity's resource
 694 adaptor interface object should be bound in the sbb's JNDI environment.
 695
 696 Used in: resource-adaptor-entity-binding
 697
 698 Example:
 699     <resource-adaptor-object-name>
 700         slee/resources/jcc/provider
 701     </resource-adaptor-object-name>
 702 -->
 703 <!ELEMENT resource-adaptor-object-name (#PCDATA)>
 704
 705 <!--
 706 The resource-adaptor-entity-link element contains an arbitrary string that the
 707 SLEE can use to locate the correct resource adaptor entity to bind into the
 708 sbb's JNDI environment.
 709
 710 Used in: resource-adaptor-entity-binding
 711
 712 Example:
 713     <resource-adaptor-entity-link>jcc<resource-adaptor-entity-link>
 714 -->
 715 <!ELEMENT resource-adaptor-entity-link (#PCDATA)>
 716
 717 <!--
 718 The ejb-ref element allows an sbb to reference an Enterprise Java Bean.  It
 719 contains an optional description, the JNDI name where the home interface of
 720 the EJB will be bound in the sbb's environment, the type of the EJB, the home
 721 and remote interface types, and an optional EJB link name.  If the EJB link
 722 name is not specified one must be supplied during deployment.
 723
 724 Used in: sbb
 725 -->
 726 <!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type, home, remote,
 727           ejb-link?)>
 728
 729 <!--
 730 The ejb-ref-name element contains the namespace path, relative to the
 731 java:comp/env context, where the resource adaptor entity's resource adaptor
 732 interface object should be bound in the sbb's JNDI environment.
 733
 734 Used in: ejb-ref
 735
 736 Example:
 737     <ejb-ref-name>ejb/externalbean</ejb-ref-name>
 738 -->
 739 <!ELEMENT ejb-ref-name (#PCDATA)>
 740
 741 <!--
 742 The <ejb-ref-type> element contains the exptected type of the referenced
 743 Enterprise Java Bean.  Valid values are Entity or Session.
 744
 745 Used in: ejb-ref
 746
 747 Example:
 748     <ejb-ref-type>Entity</ejb-ref-type>
 749 -->
 750 <!ELEMENT ejb-ref-type (#PCDATA)>
 751
 752 <!--
 753 The home element contains the fully-qualified name of a referenced Enterprise
 754 Java Bean's remote home interface.
 755
 756 Used in: ejb-ref
 757
 758 Example:
 759     <home>com.mycompany.ejb.MyEJBHome</home>
 760 -->
 761 <!ELEMENT home (#PCDATA)>
 762
 763 <!--
 764 The remote element contains the fully-qualified name of a referenced
 765 Enterprise Java Bean's remote component interface.
 766
 767 Used in: ejb-ref
 768
 769 Example:
 770     <home>com.mycompany.ejb.MyEJB</home>
 771 -->
 772 <!ELEMENT remote (#PCDATA)>
 773
 774 <!--
 775 The ejb-link element contains an arbitrary string that the SLEE can use to
 776 locate the correct Enterprise Java Bean to bind into the sbb's JNDI
 777 environment.
 778
 779 Used in: ejb-ref
 780
 781 Example:
 782     <ejb-link>myejb</ejb-link>
 783 -->
 784 <!ELEMENT ejb-link (#PCDATA)>
 785
 786
 787 <!--
 788 The ID mechanism is to allow tools that produce additional deployment
 789 information (ie. information beyond that contained by the standard SLEE
 790 deployment descriptors) to store the non-standard information in a separate
 791 file, and easily refer from those tools-specific files to the information in
 792 the standard deployment descriptor.  The SLEE architecture does not allow the
 793 tools to add the non-standard information into the SLEE-defined deployment
 794 descriptors.
 795 -->
 796 <!ATTLIST sbb-jar id ID #IMPLIED>
 797 <!ATTLIST sbb id ID #IMPLIED>
 798 <!ATTLIST description id ID #IMPLIED>
 799 <!ATTLIST sbb-name id ID #IMPLIED>
 800 <!ATTLIST sbb-vendor id ID #IMPLIED>
 801 <!ATTLIST sbb-version id ID #IMPLIED>
 802 <!ATTLIST sbb-alias id ID #IMPLIED>
 803 <!ATTLIST sbb-alias-ref id ID #IMPLIED>
 804 <!ATTLIST sbb-ref id ID #IMPLIED>
 805 <!ATTLIST profile-spec-ref id ID #IMPLIED>
 806 <!ATTLIST profile-spec-name id ID #IMPLIED>
 807 <!ATTLIST profile-spec-vendor id ID #IMPLIED>
 808 <!ATTLIST profile-spec-version id ID #IMPLIED>
 809 <!ATTLIST profile-spec-alias id ID #IMPLIED>
 810 <!ATTLIST sbb-classes id ID #IMPLIED>
 811 <!ATTLIST sbb-abstract-class reentrant (True|False) "False"
 812                              id ID #IMPLIED>
 813 <!ATTLIST sbb-abstract-class-name id ID #IMPLIED>
 814 <!ATTLIST cmp-field id ID #IMPLIED>
 815 <!ATTLIST cmp-field-name id ID #IMPLIED>
 816 <!ATTLIST get-child-relation-method id ID #IMPLIED>
 817 <!ATTLIST get-child-relation-method-name id ID #IMPLIED>
 818 <!ATTLIST default-priority id ID #IMPLIED>
 819 <!ATTLIST get-profile-cmp-method id ID #IMPLIED>
 820 <!ATTLIST profile-spec-alias-ref id ID #IMPLIED>
 821 <!ATTLIST get-profile-cmp-method-name id ID #IMPLIED>
 822 <!ATTLIST sbb-local-interface id ID #IMPLIED>
 823 <!ATTLIST sbb-local-interface-name id ID #IMPLIED>
 824 <!ATTLIST sbb-activity-context-interface id ID #IMPLIED>
 825 <!ATTLIST sbb-activity-context-interface-name id ID #IMPLIED>
 826 <!ATTLIST address-profile-spec-alias-ref id ID #IMPLIED>
 827 <!ATTLIST event event-direction (Fire|Receive|FireAndReceive) #REQUIRED
 828                 initial-event (True|False) "False"
 829                 mask-on-attach (True|False) "False"
 830                 id ID #IMPLIED>
 831 <!ATTLIST event-name id ID #IMPLIED>
 832 <!ATTLIST event-type-ref id ID #IMPLIED>
 833 <!ATTLIST event-type-name id ID #IMPLIED>
 834 <!ATTLIST event-type-vendor id ID #IMPLIED>
 835 <!ATTLIST event-type-version id ID #IMPLIED>
 836 <!ATTLIST initial-event-select variable (ActivityContext|AddressProfile|Address|EventType|Event) #REQUIRED
 837                                id ID #IMPLIED>
 838 <!ATTLIST initial-event-selector-method-name id ID #IMPLIED>
 839 <!ATTLIST event-resource-option id ID #IMPLIED>
 840 <!ATTLIST activity-context-attribute-alias id ID #IMPLIED>
 841 <!ATTLIST attribute-alias-name id ID #IMPLIED>
 842 <!ATTLIST sbb-activity-context-attribute-name id ID #IMPLIED>
 843 <!ATTLIST sbb-usage-parameters-interface id ID #IMPLIED>
 844 <!ATTLIST sbb-usage-parameters-interface-name id ID #IMPLIED>
 845 <!ATTLIST env-entry id ID #IMPLIED>
 846 <!ATTLIST env-entry-name id ID #IMPLIED>
 847 <!ATTLIST env-entry-type id ID #IMPLIED>
 848 <!ATTLIST env-entry-value id ID #IMPLIED>
 849 <!ATTLIST resource-adaptor-type-binding id ID #IMPLIED>
 850 <!ATTLIST resource-adaptor-type-ref id ID #IMPLIED>
 851 <!ATTLIST resource-adaptor-type-name id ID #IMPLIED>
 852 <!ATTLIST resource-adaptor-type-vendor id ID #IMPLIED>
 853 <!ATTLIST resource-adaptor-type-version id ID #IMPLIED>
 854 <!ATTLIST activity-context-interface-factory-name id ID #IMPLIED>
 855 <!ATTLIST resource-adaptor-entity-binding id ID #IMPLIED>
 856 <!ATTLIST resource-adaptor-object-name id ID #IMPLIED>
 857 <!ATTLIST resource-adaptor-entity-link id ID #IMPLIED>
 858 <!ATTLIST ejb-ref id ID #IMPLIED>
 859 <!ATTLIST ejb-ref-name id ID #IMPLIED>
 860 <!ATTLIST ejb-ref-type id ID #IMPLIED>
 861 <!ATTLIST home id ID #IMPLIED>
 862 <!ATTLIST remote id ID #IMPLIED>
 863 <!ATTLIST ejb-link id ID #IMPLIED>
 864
 865