KickJava   Java API By Example, From Geeks To Geeks.

Java > Open Source Codes > com > sun > enterprise > tools > common > dd > ejb > IorSecurityConfig


1 /*
2  * The contents of this file are subject to the terms
3  * of the Common Development and Distribution License
4  * (the License). You may not use this file except in
5  * compliance with the License.
6  *
7  * You can obtain a copy of the license at
8  * https://glassfish.dev.java.net/public/CDDLv1.0.html or
9  * glassfish/bootstrap/legal/CDDLv1.0.txt.
10  * See the License for the specific language governing
11  * permissions and limitations under the License.
12  *
13  * When distributing Covered Code, include this CDDL
14  * Header Notice in each file and include the License file
15  * at glassfish/bootstrap/legal/CDDLv1.0.txt.
16  * If applicable, add the following below the CDDL Header,
17  * with the fields enclosed by brackets [] replaced by
18  * you own identifying information:
19  * "Portions Copyrighted [year] [name of copyright owner]"
20  *
21  * Copyright 2006 Sun Microsystems, Inc. All rights reserved.
22  */

23
24 /**
25  * This generated bean class IorSecurityConfig matches the schema element ior-security-config
26  *
27  * Generated on Wed Aug 13 10:43:33 PDT 2003
28  */

29
30 package com.sun.enterprise.tools.common.dd.ejb;
31
32 import org.w3c.dom.*;
33 import org.netbeans.modules.schema2beans.*;
34 import java.beans.*;
35 import java.util.*;
36
37 // BEGIN_NOI18N
38

39 public class IorSecurityConfig extends com.sun.enterprise.tools.common.dd.SunBaseBean
40 {
41
42     static Vector comparators = new Vector();
43
44     static public final String JavaDoc TRANSPORT_CONFIG = "TransportConfig"; // NOI18N
45
static public final String JavaDoc AS_CONTEXT = "AsContext"; // NOI18N
46
static public final String JavaDoc SAS_CONTEXT = "SasContext"; // NOI18N
47

48     public IorSecurityConfig() {
49         this(Common.USE_DEFAULT_VALUES);
50     }
51
52     public IorSecurityConfig(int options)
53     {
54         super(comparators, new org.netbeans.modules.schema2beans.Version(1, 2, 0));
55         // Properties (see root bean comments for the bean graph)
56
this.createProperty("transport-config", // NOI18N
57
TRANSPORT_CONFIG,
58             Common.TYPE_0_1 | Common.TYPE_BEAN | Common.TYPE_KEY,
59             TransportConfig.class);
60         this.createProperty("as-context", // NOI18N
61
AS_CONTEXT,
62             Common.TYPE_0_1 | Common.TYPE_BEAN | Common.TYPE_KEY,
63             AsContext.class);
64         this.createProperty("sas-context", // NOI18N
65
SAS_CONTEXT,
66             Common.TYPE_0_1 | Common.TYPE_BEAN | Common.TYPE_KEY,
67             SasContext.class);
68         this.initialize(options);
69     }
70
71     // Setting the default values of the properties
72
void initialize(int options)
73     {
74
75     }
76
77     // This attribute is optional
78
public void setTransportConfig(TransportConfig value) {
79         this.setValue(TRANSPORT_CONFIG, value);
80     }
81
82     //
83
public TransportConfig getTransportConfig() {
84         return (TransportConfig)this.getValue(TRANSPORT_CONFIG);
85     }
86
87     // This attribute is optional
88
public void setAsContext(AsContext value) {
89         this.setValue(AS_CONTEXT, value);
90     }
91
92     //
93
public AsContext getAsContext() {
94         return (AsContext)this.getValue(AS_CONTEXT);
95     }
96
97     // This attribute is optional
98
public void setSasContext(SasContext value) {
99         this.setValue(SAS_CONTEXT, value);
100     }
101
102     //
103
public SasContext getSasContext() {
104         return (SasContext)this.getValue(SAS_CONTEXT);
105     }
106
107     //
108
public static void addComparator(org.netbeans.modules.schema2beans.BeanComparator c) {
109         comparators.add(c);
110     }
111
112     //
113
public static void removeComparator(org.netbeans.modules.schema2beans.BeanComparator c) {
114         comparators.remove(c);
115     }
116     public void validate() throws org.netbeans.modules.schema2beans.ValidateException {
117         boolean restrictionFailure = false;
118         // Validating property transportConfig
119
if (getTransportConfig() != null) {
120             getTransportConfig().validate();
121         }
122         // Validating property asContext
123
if (getAsContext() != null) {
124             getAsContext().validate();
125         }
126         // Validating property sasContext
127
if (getSasContext() != null) {
128             getSasContext().validate();
129         }
130     }
131
132     // Dump the content of this bean returning it as a String
133
public void dump(StringBuffer JavaDoc str, String JavaDoc indent){
134         String JavaDoc s;
135         Object JavaDoc o;
136         org.netbeans.modules.schema2beans.BaseBean n;
137         str.append(indent);
138         str.append("TransportConfig"); // NOI18N
139
n = (org.netbeans.modules.schema2beans.BaseBean) this.getTransportConfig();
140         if (n != null)
141             n.dump(str, indent + "\t"); // NOI18N
142
else
143             str.append(indent+"\tnull"); // NOI18N
144
this.dumpAttributes(TRANSPORT_CONFIG, 0, str, indent);
145
146         str.append(indent);
147         str.append("AsContext"); // NOI18N
148
n = (org.netbeans.modules.schema2beans.BaseBean) this.getAsContext();
149         if (n != null)
150             n.dump(str, indent + "\t"); // NOI18N
151
else
152             str.append(indent+"\tnull"); // NOI18N
153
this.dumpAttributes(AS_CONTEXT, 0, str, indent);
154
155         str.append(indent);
156         str.append("SasContext"); // NOI18N
157
n = (org.netbeans.modules.schema2beans.BaseBean) this.getSasContext();
158         if (n != null)
159             n.dump(str, indent + "\t"); // NOI18N
160
else
161             str.append(indent+"\tnull"); // NOI18N
162
this.dumpAttributes(SAS_CONTEXT, 0, str, indent);
163
164     }
165     public String JavaDoc dumpBeanNode(){
166         StringBuffer JavaDoc str = new StringBuffer JavaDoc();
167         str.append("IorSecurityConfig\n"); // NOI18N
168
this.dump(str, "\n "); // NOI18N
169
return str.toString();
170     }}
171
172 // END_NOI18N
173

174
175 /*
176         The following schema file has been used for generation:
177
178 <!--
179   XML DTD for Sun ONE Application Server specific EJB jar module
180   deployment descriptor. This is a companion DTD for ejb-jar_2_1.xsd
181
182   $Revision: 1.3 $
183 -->
184
185 <!--
186 This is the root element of the ejb module descriptor document.
187 -->
188 <!ELEMENT sun-ejb-jar (security-role-mapping*, enterprise-beans) >
189
190 <!--
191 System unique object id. Automatically generated and updated at deployment/redeployment
192 -->
193 <!ELEMENT unique-id (#PCDATA)>
194
195 <!--
196 This is the root element describing all the runtime of an ejb-jar in the application.
197 -->
198 <!ELEMENT enterprise-beans (name?, unique-id?, ejb*, pm-descriptors?, cmp-resource?,
199     message-destination*, webservice-description*)>
200
201 <!--
202 This is the element describing runtime bindings for a single ejb.
203
204 Properties applicable to all types of beans:
205      ejb-name, ejb-ref*, jndi-name, resource-ref*, resource-env-ref*, pass-by-reference?,
206      ior-security-config?, gen-classes?, service-ref*
207
208 Additional properties applicable to a stateless session bean:
209     bean-pool, webservice-endpoint
210
211 Additional properties applicable to a stateful session bean:
212     bean-cache, webservice-endpoint
213
214 Additional properties applicable to an entity bean:
215    is-read-only-bean?, refresh-period-in-seconds?, cmp?, commit-option?, bean-cache?, bean-pool?
216
217 Additional properties applicable to a message-driven bean:
218    mdb-resource-adapter?, mdb-connection-factory?, jms-durable-subscription-name?,
219    jms-max-messages-load?, bean-pool?
220    ( In case of MDB, jndi-name is the jndi name of the associated jms destination )
221 -->
222
223 <!ELEMENT ejb (ejb-name, jndi-name?, ejb-ref*, resource-ref*, resource-env-ref*, service-ref*, pass-by-reference?,
224                cmp?, principal?, mdb-connection-factory?, jms-durable-subscription-name?,
225                jms-max-messages-load?, ior-security-config?, is-read-only-bean?,
226                refresh-period-in-seconds?, commit-option?, cmt-timeout-in-seconds?, gen-classes?,
227                bean-pool?, bean-cache?, mdb-resource-adapter?, webservice-endpoint*, session?)>
228 <!--
229 The text in this element matches the ejb-name of the ejb to which it refers in ejb-jar.xml.
230 -->
231 <!ELEMENT ejb-name (#PCDATA)>
232
233 <!--
234 The text in this element is a true/false flag for read only beans.
235 -->
236 <!ELEMENT is-read-only-bean (#PCDATA)>
237
238 <!--
239 This is the root element which binds an ejb reference to a jndi name.
240 -->
241 <!ELEMENT ejb-ref (ejb-ref-name, jndi-name)>
242
243 <!--
244 The ejb ref name locates the name of the ejb reference in the application.
245 -->
246 <!ELEMENT ejb-ref-name (#PCDATA)>
247
248 <!--
249 This element describes runtime information for a CMP EntityBean object for
250 EJB1.1 and EJB2.0 beans.
251 -->
252 <!ELEMENT cmp (mapping-properties?, is-one-one-cmp?, one-one-finders?)>
253
254 <!--
255 This contains the location of the persistence vendor specific O/R mapping file
256 -->
257 <!ELEMENT mapping-properties (#PCDATA)>
258
259 <!--
260 This element in deprecated. It has been left in the DTD for validation purposes.
261 Any value will be ignored by the runtime.
262 -->
263 <!ELEMENT is-one-one-cmp (#PCDATA)>
264
265 <!--
266 This root element contains the finders for CMP 1.1.
267 -->
268 <!ELEMENT one-one-finders (finder+ )>
269
270 <!--
271 This root element contains the finder for CMP 1.1 with a method-name and query parameters
272 -->
273 <!ELEMENT finder (method-name, query-params?, query-filter?, query-variables?, query-ordering?)>
274
275 <!--
276 This contains the query parameters for CMP 1.1 finder
277 -->
278 <!ELEMENT query-params (#PCDATA)>
279
280 <!--
281 This optional element contains the query filter for CMP 1.1 finder
282 -->
283 <!ELEMENT query-filter (#PCDATA)>
284
285 <!--
286 This optional element contains variables in query expression for CMP 1.1 finder
287 -->
288 <!ELEMENT query-variables (#PCDATA)>
289
290 <!--
291 This optional element contains the ordering specification for CMP 1.1 finder.
292 -->
293
294 <!ELEMENT query-ordering (#PCDATA)>
295
296 <!--
297 This element identifies the database and the policy for processing CMP beans
298 storage. The jndi-name element identifies either the persistence-manager-
299 factory-resource or the jdbc-resource as defined in the server configuration.
300 -->
301 <!ELEMENT cmp-resource (jndi-name, default-resource-principal?, property*,
302         create-tables-at-deploy?, drop-tables-at-undeploy?,
303         database-vendor-name?, schema-generator-properties?)>
304
305 <!--
306 This element contains the override properties for the schema generation
307 from CMP beans in this module.
308 -->
309 <!ELEMENT schema-generator-properties (property*) >
310
311 <!--
312 This element specifies whether automatic creation of tables for the CMP beans
313 is done at module deployment. Acceptable values are true or false
314 -->
315 <!ELEMENT create-tables-at-deploy ( #PCDATA )>
316
317 <!--
318 This element specifies whether automatic dropping of tables for the CMP beans
319 is done at module undeployment. Acceptabel values are true of false
320 -->
321 <!ELEMENT drop-tables-at-undeploy ( #PCDATA )>
322
323 <!--
324 This element specifies the database vendor name for ddl files generated at
325 module deployment. Default is SQL92.
326 -->
327 <!ELEMENT database-vendor-name ( #PCDATA )>
328
329 <!--
330 This element specifies the connection factory associated with a message-driven bean.
331 -->
332 <!ELEMENT mdb-connection-factory (jndi-name, default-resource-principal?)>
333
334 <!--
335 This node holds information about a logical message destination
336 -->
337 <!ELEMENT message-destination (message-destination-name, jndi-name)>
338
339 <!--
340 This node holds the name of a logical message destination
341 -->
342 <!ELEMENT message-destination-name (#PCDATA)>
343
344 <!--
345 Specifies the name of a durable subscription associated with a message-driven bean's
346 destination. Required for a Topic destination, if subscription-durability is set to
347 Durable (in ejb-jar.xml)
348 -->
349 <!ELEMENT jms-durable-subscription-name (#PCDATA)>
350
351 <!--
352 A string value specifies the maximum number of messages to load into a JMS session
353 at one time for a message-driven bean to serve. If not specified, the default is 1.
354 -->
355 <!ELEMENT jms-max-messages-load (#PCDATA)>
356
357 <!--
358 This element contains all the generated class names for a bean.
359 -->
360 <!ELEMENT gen-classes ( remote-impl?, local-impl?, remote-home-impl?, local-home-impl? )>
361
362 <!--
363 This contains the fully qualified class name of the generated EJBObject impl class.
364 -->
365 <!ELEMENT remote-impl (#PCDATA)>
366
367 <!--
368 This contains the fully qualified class name of the generated EJBLocalObject impl class.
369 -->
370 <!ELEMENT local-impl (#PCDATA)>
371
372 <!--
373 This contains the fully qualified class name of the generated EJBHome impl class.
374 -->
375 <!ELEMENT remote-home-impl (#PCDATA)>
376
377 <!--
378 This contains the fully qualified class name of the generated EJBLocalHome impl class.
379 -->
380 <!ELEMENT local-home-impl (#PCDATA)>
381
382 <!--
383 This contains the bean cache properties. Used only for entity beans and stateful session beans
384 -->
385 <!ELEMENT bean-cache (max-cache-size?, resize-quantity?, is-cache-overflow-allowed?, cache-idle-timeout-in-seconds?, removal-timeout-in-seconds?, victim-selection-policy?)>
386
387 <!--
388 max-cache-size defines the maximum number of beans in the cache. Should be greater than 1.
389 Default is 512.
390 -->
391 <!ELEMENT max-cache-size (#PCDATA)>
392
393 <!--
394 is-cache-overflow-allowed is a boolean which indicates if the cache size is a hard limit or not.
395 Default is true i.e there is no hard limit. max-cache-size is a hint to the cache implementation.
396 -->
397 <!ELEMENT is-cache-overflow-allowed (#PCDATA)>
398
399 <!--
400 cache-idle-timeout-in-seconds specifies the maximum time that a stateful session bean or
401 entity bean is allowed to be idle in the cache. After this time, the bean is passivated
402 to backup store. This is a hint to server. Default value for cache-idle-timeout-in-seconds
403 is 600 seconds.
404 -->
405 <!ELEMENT cache-idle-timeout-in-seconds (#PCDATA)>
406
407
408 <!--
409 The amount of time that the bean remains passivated (i.e. idle in the backup store) is
410 controlled by removal-timeout-in-seconds parameter. Note that if a bean was not accessed beyond
411 removal-timeout-in-seconds, then it will be removed from the backup store and hence will not
412 be accessible to the client. The Default value for removal-timeout-in-seconds is 60min.
413 -->
414 <!ELEMENT removal-timeout-in-seconds (#PCDATA)>
415
416 <!--
417 victim-selection-policy specifies the algorithm to use to pick victims.
418 Possible values are FIFO | LRU | NRU. Default is NRU, which is actually
419 pseudo-random selection policy.
420 -->
421 <!ELEMENT victim-selection-policy (#PCDATA)>
422
423 <!--
424 bean-pool is a root element containing the bean pool properties. Used only for stateless session
425 bean and message-driven bean pools.
426 -->
427 <!ELEMENT bean-pool (steady-pool-size?, resize-quantity?, max-pool-size?, pool-idle-timeout-in-seconds?, max-wait-time-in-millis?)>
428
429 <!--
430 steady-pool-size specified the initial and minimum number of beans that must be maintained in the pool.
431 Valid values are from 0 to MAX_INTEGER.
432 -->
433 <!ELEMENT steady-pool-size (#PCDATA)>
434
435 <!--
436 resize-quantity specifies the number of beans to be created or deleted when the pool
437 or cache is being serviced by the server. Valid values are from 0 to MAX_INTEGER and
438 subject to maximum size limit). Default is 16.
439 -->
440 <!ELEMENT resize-quantity (#PCDATA)>
441
442 <!--
443 max-pool-size speifies the maximum pool size. Valid values are from 0 to MAX_INTEGER.
444 Default is 64.
445 -->
446 <!ELEMENT max-pool-size (#PCDATA)>
447
448 <!--
449 pool-idle-timeout-in-seconds specifies the maximum time that a stateless session bean or
450 message-driven bean is allowed to be idle in the pool. After this time, the bean is
451 passivated to backup store. This is a hint to server. Default value for
452 pool-idle-timeout-in-seconds is 600 seconds.
453 -->
454 <!ELEMENT pool-idle-timeout-in-seconds (#PCDATA)>
455
456 <!--
457 A string field whose valid values are either "B", or "C". Default is "B"
458 -->
459 <!ELEMENT commit-option (#PCDATA)>
460
461 <!--
462 Specifies the timeout for transactions started by the container. This value must be greater than zero, else it will be ignored by the container.
463 -->
464 <!ELEMENT cmt-timeout-in-seconds (#PCDATA)>
465
466 <!--
467 Specifies the maximum time that the caller is willing to wait to get a bean from the pool.
468 Wait time is infinite, if the value specified is 0. Deprecated.
469 -->
470 <!ELEMENT max-wait-time-in-millis (#PCDATA)>
471
472 <!--
473 refresh-period-in-seconds specifies the rate at which the read-only-bean must be refreshed
474 from the data source. 0 (never refreshed) and positive (refreshed at specified intervals).
475 Specified value is a hint to the container. Default is 600 seconds.
476 -->
477 <!ELEMENT refresh-period-in-seconds (#PCDATA)>
478
479 <!--
480 Specifies the jndi name string.
481 -->
482 <!ELEMENT jndi-name (#PCDATA)>
483
484 <!--
485 This text nodes holds a name string.
486 -->
487 <!ELEMENT name (#PCDATA)>
488
489 <!--
490 This element holds password text.
491 -->
492 <!ELEMENT password (#PCDATA)>
493
494 <!--
495 This node describes a username on the platform.
496 -->
497 <!ELEMENT principal (name)>
498
499 <!--
500 security-role-mapping element maps the user principal or group
501 to a different principal on the server.
502 -->
503 <!ELEMENT security-role-mapping (role-name, (principal-name | group-name)+)>
504
505 <!--
506 role-name specifies an accepted role
507 -->
508 <!ELEMENT role-name (#PCDATA)>
509
510 <!--
511 principal-name specifies a valid principal
512 -->
513 <!ELEMENT principal-name (#PCDATA)>
514
515 <!--
516 group-name specifies a valid group name
517 -->
518 <!ELEMENT group-name (#PCDATA)>
519
520 <!--
521 The name of a resource reference.
522 -->
523 <!ELEMENT res-ref-name (#PCDATA)>
524
525 <!--
526 resource-env-ref holds all the runtime bindings of a resource env reference.
527 -->
528 <!ELEMENT resource-env-ref ( resource-env-ref-name, jndi-name )>
529
530 <!--
531 name of a resource env reference.
532 -->
533 <!ELEMENT resource-env-ref-name (#PCDATA)>
534
535 <!--
536 resource-ref node holds all the runtime bindings of a resource reference.
537 -->
538 <!ELEMENT resource-ref (res-ref-name, jndi-name, default-resource-principal?)>
539
540 <!--
541 user name and password to be used when none are specified while accesing a resource
542 -->
543 <!ELEMENT default-resource-principal ( name, password)>
544
545 <!--
546 ior-security-config element describes the security configuration information for the IOR.
547 -->
548 <!ELEMENT ior-security-config ( transport-config? , as-context?, sas-context? )>
549
550 <!--
551 transport-config is the root element for security between the end points
552 -->
553 <!ELEMENT transport-config ( integrity, confidentiality, establish-trust-in-target, establish-trust-in-client )>
554
555 <!--
556 integrity element indicates if the server (target) supports integrity protected messages.
557 The valid values are NONE, SUPPORTED or REQUIRED
558 -->
559 <!ELEMENT integrity ( #PCDATA)>
560
561 <!--
562 confidentiality element indicates if the server (target) supports privacy protected
563 messages. The values are NONE, SUPPORTED or REQUIRED
564 -->
565 <!ELEMENT confidentiality ( #PCDATA)>
566
567 <!--
568 establish-trust-in-target element indicates if the target is capable of authenticating to a client.
569 The values are NONE or SUPPORTED.
570 -->
571 <!ELEMENT establish-trust-in-target ( #PCDATA)>
572
573 <!--
574 establish-trust-in-client element indicates if the target is capable of authenticating a client. The
575 values are NONE, SUPPORTED or REQUIRED.
576 -->
577 <!ELEMENT establish-trust-in-client ( #PCDATA)>
578
579 <!--
580 as-context (CSIv2 authentication service) is the element describing the authentication
581 mechanism that will be used to authenticate the client. If specified it will be the
582 username-password mechanism.
583 -->
584 <!ELEMENT as-context ( auth-method, realm, required )>
585
586 <!--
587 required element specifies if the authentication method specified is required
588 to be used for client authentication. If so the EstablishTrustInClient bit
589 will be set in the target_requires field of the AS_Context. The element value
590 is either true or false.
591 -->
592 <!ELEMENT required ( #PCDATA )>
593
594 <!--
595 auth-method element describes the authentication method. The only supported value
596 is USERNAME_PASSWORD
597 -->
598 <!ELEMENT auth-method ( #PCDATA )>
599
600 <!--
601 realm element describes the realm in which the user is authenticated. Must be
602 a valid realm that is registered in server configuration.
603 -->
604 <!ELEMENT realm ( #PCDATA )>
605
606 <!--
607 sas-context (related to CSIv2 security attribute service) element describes
608 the sas-context fields.
609 -->
610 <!ELEMENT sas-context ( caller-propagation )>
611
612 <!--
613 caller-propagation element indicates if the target will accept propagated caller identities
614 The values are NONE or SUPPORTED.
615 -->
616 <!ELEMENT caller-propagation ( #PCDATA) >
617
618 <!--
619 pass-by-reference elements controls use of Pass by Reference semantics.
620 EJB spec requires pass by value, which will be the default mode of operation.
621 This can be set to true for non-compliant operation and possibly higher
622 performance. For a stand-alone server, this can be used. By setting a similarly
623 named element at sun-application.xml, it can apply to all the enclosed ejb
624 modules. Allowed values are true and false. Default will be false.
625  -->
626 <!ELEMENT pass-by-reference (#PCDATA)>
627
628 <!--
629 PM descriptors contain one or more pm descriptors, but only one of them must
630 be in use at any given time. If not specified, the Sun ONE CMP is used.
631 -->
632 <!ELEMENT pm-descriptors ( pm-descriptor+, pm-inuse)>
633
634 <!--
635 pm-descriptor describes the pluggable vendor implementation for the CMP
636 support of the CMP entity beans in this module.
637 -->
638 <!ELEMENT pm-descriptor ( pm-identifier, pm-version, pm-config?, pm-class-generator, pm-mapping-factory?)>
639
640 <!--
641 pm-identifier element identifies the vendor who provides the CMP implementation
642 -->
643 <!ELEMENT pm-identifier (#PCDATA)>
644
645 <!--
646 pm-version further specifies which version of PM vendor product to be used
647 -->
648 <!ELEMENT pm-version (#PCDATA)>
649
650 <!--
651 pm-config specifies the vendor specific config file to be used
652 -->
653 <!ELEMENT pm-config (#PCDATA)>
654
655 <!--
656 pm-class-generator specifies the vendor specific class generator to be used
657 at the module deploymant time. This is the name of the class specific to this
658 vendor.
659 -->
660 <!ELEMENT pm-class-generator (#PCDATA)>
661
662 <!--
663 pm-mapping-factory specifies the vendor specific mapping factory
664 This is the name of the class specific to a vendor.
665 -->
666 <!ELEMENT pm-mapping-factory (#PCDATA)>
667
668 <!--
669 pm-inuse specifies which CMP vendor is used.
670 -->
671 <!ELEMENT pm-inuse (pm-identifier, pm-version)>
672
673
674 <!--
675 This holds the runtime configuration properties of the message-driven bean
676 in its operation environment. For example, this may include information
677 about the name of a physical JMS destination etc.
678 Defined this way to match the activation-config on the standard
679 deployment descriptor for message-driven bean.
680 -->
681 <!ELEMENT activation-config ( description?, activation-config-property+ ) >
682
683 <!--
684 provide an element description
685 -->
686 <!ELEMENT description (#PCDATA)>
687
688 <!--
689 This hold a particular activation config propery name-value pair
690 -->
691 <!ELEMENT activation-config-property (
692   activation-config-property-name, activation-config-property-value ) >
693
694 <!--
695 This holds the name of a runtime activation-config property
696 -->
697 <!ELEMENT activation-config-property-name ( #PCDATA ) >
698
699 <!--
700 This holds the value of a runtime activation-config property
701 -->
702 <!ELEMENT activation-config-property-value ( #PCDATA ) >
703
704 <!--
705 This node holds the module ID of the resource adapter that
706 is responsible for delivering messages to the message-driven
707 bean, as well as the runtime configuration information for
708 the mdb.
709 -->
710 <!ELEMENT mdb-resource-adapter ( resource-adapter-mid, activation-config? )>
711
712 <!--
713 This node holds the module ID of the resource adapter that is responsible
714 for delivering messages to the message-driven bean.
715 -->
716 <!ELEMENT resource-adapter-mid ( #PCDATA ) >
717
718 <!--
719 Generic name-value pairs property
720 -->
721 <!ELEMENT property ( name, value ) >
722
723 <!--
724 This text nodes holds a value string.
725 -->
726 <!ELEMENT value (#PCDATA)>
727
728
729
730 <!--
731             W E B S E R V I C E S
732 -->
733 <!--
734 Information about a web service endpoint.
735 -->
736 <!ELEMENT webservice-endpoint ( port-component-name, endpoint-address-uri?, login-config?, transport-guarantee?, service-qname?, tie-class?, servlet-impl-class? )>
737
738 <!--
739 Unique name of a port component within a module
740 -->
741 <!ELEMENT port-component-name ( #PCDATA )>
742
743 <!--
744 Relative path combined with web server root to form fully qualified
745 endpoint address for a web service endpoint. For servlet endpoints, this
746 value is relative to the servlet's web application context root. In
747 all cases, this value must be a fixed pattern(i.e. no "*" allowed).
748 If the web service endpoint is a servlet that only implements a single
749 endpoint has only one url-pattern, it is not necessary to set
750 this value since the container can derive it from web.xml.
751 -->
752 <!ELEMENT endpoint-address-uri ( #PCDATA )>
753
754 <!--
755 The name of tie implementation class for a port-component. This is
756 not specified by the deployer. It is derived during deployment.
757 -->
758 <!ELEMENT tie-class (#PCDATA)>
759
760 <!--
761 The service-qname element declares the specific WSDL service
762 element that is being refered to. It is not set by the deployer.
763 It is derived during deployment.
764 -->
765 <!ELEMENT service-qname (namespaceURI, localpart)>
766
767 <!--
768 The localpart element indicates the local part of a QNAME.
769 -->
770 <!ELEMENT localpart (#PCDATA)>
771
772 <!--
773 The namespaceURI element indicates a URI.
774 -->
775 <!ELEMENT namespaceURI (#PCDATA)>
776
777 <!--
778 Optional authentication configuration for an EJB web service endpoint.
779 Not needed for servet web service endpoints. Their security configuration
780 is contained in the standard web application descriptor.
781 -->
782 <!ELEMENT login-config ( auth-method )>
783
784 <!--
785 Name of application-written servlet impl class contained in deployed war.
786 This is not set by the deployer. It is derived by the container
787 during deployment.
788 -->
789 <!ELEMENT servlet-impl-class (#PCDATA)>
790
791 <!--
792 Runtime settings for a web service reference. In the simplest case,
793 there is no runtime information required for a service ref. Runtime info
794 is only needed in the following cases :
795  * to define the port that should be used to resolve a container-managed port
796  * to define default Stub/Call property settings for Stub objects
797  * to define the URL of a final WSDL document to be used instead of
798 the one packaged with a service-ref
799 -->
800 <!ELEMENT service-ref ( service-ref-name, port-info*, call-property*, wsdl-override?, service-impl-class?, service-qname? )>
801
802 <!--
803 Coded name (relative to java:comp/env) for a service-reference
804 -->
805 <!ELEMENT service-ref-name ( #PCDATA )>
806
807 <!--
808 Name of generated service implementation class. This is not set by the
809 deployer. It is derived during deployment.
810 -->
811 <!ELEMENT service-impl-class ( #PCDATA )>
812
813 <!--
814 Information for a port within a service-reference.
815
816 Either service-endpoint-interface or wsdl-port or both
817 (service-endpoint-interface and wsdl-port) should be specified.
818
819 If both are specified, wsdl-port represents the
820 port the container should choose for container-managed port selection.
821
822 The same wsdl-port value must not appear in
823 more than one port-info entry within the same service-ref.
824
825 If a particular service-endpoint-interface is using container-managed port
826 selection, it must not appear in more than one port-info entry
827 within the same service-ref.
828
829 -->
830 <!ELEMENT port-info ( service-endpoint-interface?, wsdl-port?, stub-property*, call-property* )>
831
832 <!--
833 Fully qualified name of service endpoint interface
834 -->
835 <!ELEMENT service-endpoint-interface ( #PCDATA )>
836
837 <!--
838 Specifies that the communication between client and server should
839 be NONE, INTEGRAL, or CONFIDENTIAL. NONE means that the application
840 does not require any transport guarantees. A value of INTEGRAL means
841 that the application requires that the data sent between the client
842 and server be sent in such a way that it can't be changed in transit.
843 CONFIDENTIAL means that the application requires that the data be
844 transmitted in a fashion that prevents other entities from observing
845 the contents of the transmission. In most cases, the presence of the
846 INTEGRAL or CONFIDENTIAL flag will indicate that the use of SSL is
847 required.
848 -->
849 <!ELEMENT transport-guarantee ( #PCDATA )>
850
851
852 <!--
853 Port used in port-info.
854 -->
855 <!ELEMENT wsdl-port ( namespaceURI, localpart )>
856
857 <!--
858 JAXRPC property values that should be set on a stub before it's returned to
859 to the web service client. The property names can be any properties supported
860 by the JAXRPC Stub implementation. See javadoc for javax.xml.rpc.Stub
861 -->
862 <!ELEMENT stub-property ( name, value )>
863
864 <!--
865 JAXRPC property values that should be set on a Call object before it's
866 returned to the web service client. The property names can be any
867 properties supported by the JAXRPC Call implementation. See javadoc
868 for javax.xml.rpc.Call
869 -->
870 <!ELEMENT call-property ( name, value )>
871
872 <!--
873 Runtime information about a web service.
874
875 wsdl-publish-location is optionally used to specify
876 where the final wsdl and any dependent files should be stored. This location
877 resides on the file system from which deployment is initiated.
878
879 -->
880 <!ELEMENT webservice-description ( webservice-description-name, wsdl-publish-location? )>
881
882 <!--
883 Unique name of a webservice within a module
884 -->
885 <!ELEMENT webservice-description-name ( #PCDATA )>
886
887 <!--
888 This is a valid URL pointing to a final WSDL document. It is optional.
889 If specified, the WSDL document at this URL will be used during
890 deployment instead of the WSDL document associated with the
891 service-ref in the standard deployment descriptor.
892
893 Examples :
894
895   // available via HTTP
896   <wsdl-override>http://localhost:8000/myservice/myport?WSDL</wsdl-override>
897
898   // in a file
899   <wsdl-override>file:/home/user1/myfinalwsdl.wsdl</wsdl-override>
900
901 -->
902 <!ELEMENT wsdl-override ( #PCDATA )>
903
904 <!--
905 file: URL of a directory to which a web-service-description's wsdl should be
906 published during deployment. Any required files will be published to this
907 directory, preserving their location relative to the module-specific
908 wsdl directory(META-INF/wsdl or WEB-INF/wsdl).
909
910 Example :
911
912   For an ejb.jar whose webservices.xml wsdl-file element contains
913     META-INF/wsdl/a/Foo.wsdl
914
915   <wsdl-publish-location>file:/home/user1/publish
916   </wsdl-publish-location>
917
918   The final wsdl will be stored in /home/user1/publish/a/Foo.wsdl
919
920 -->
921 <!ELEMENT wsdl-publish-location ( #PCDATA )>
922
923
924 <!--
925             S E / E E V e r s i o n r e l a t e d f i e l d s
926 -->
927 <!--
928 The session element specifies a Stateful enterprise bean's check pointing mechanism properties
929 Used in: ejb
930 -->
931 <!ELEMENT session ( checkpoint-location?, quick-checkpoint?, checkpointed-methods? )>
932
933 <!--
934 The checkpoint-location element specifies a Stateful enterprise bean's check pointing mechanism type. The checkpoint-location element must be one of the following:
935 <checkpoint-location>end-of-transaction</checkpoint-location>
936 <checkpoint-location>end-of-method</checkpoint-location>
937 <checkpoint-location>end-of-transaction-or-method</checkpoint-location>
938 Default value: end-of-transaction
939 Used in: session
940 -->
941 <!ELEMENT checkpoint-location (#PCDATA)>
942
943
944 <!--
945 The quick-checkpoint element specifies an enterprise bean's if ejbPassivate/ejbActivate must be called or not during check pointing.
946 The checkpointing-type element must be one of the two following:
947         <quick-checkpoint>true</quick-checkpoint>
948         <quick-checkpoint>false</quick-checkpoint>
949 Dafault: true
950 Used in: session
951 -->
952 <!ELEMENT quick-checkpoint (#PCDATA)>
953
954 <!--
955 This element specifies which methods require checkpointing. The methods specified in here, will be checkpointed, when the checkpoint-location is set to end-of-method.
956
957 Default: none or all methods if failover is enabled at application or cluster/instance levels
958 Used in: session
959 -->
960 <!ELEMENT checkpointed-methods (description?, method+)>
961
962 <!--
963
964 Method as defined in the standard deployment descriptors.
965
966 Used in : checkpointed-methods
967 -->
968 <!ELEMENT method (description?, method-intf?, method-name,
969 method-params?)>
970
971 <!--
972
973 The method-intf element allows a method element to differentiate
974 between the methods with the same name and signature that are multiply
975 defined across the component and home interfaces (e.g, in both an
976 enterprise bean's remote and local interfaces; in both an enterprise bean's
977 home and remote interfaces, etc.)
978
979 The method-intf element must be one of the following:
980
981     <method-intf>Home</method-intf>
982     <method-intf>Remote</method-intf>
983     <method-intf>LocalHome</method-intf>
984     <method-intf>Local</method-intf>
985
986 Used in: method
987 -->
988 <!ELEMENT method-intf (#PCDATA)>
989
990 <!--
991 The method-name element contains a name of an enterprise bean method
992 or the asterisk (*) character. The asterisk is used when the element
993 denotes all the methods of an enterprise bean's component and home
994 interfaces.
995
996 Used in: method, query-method
997 -->
998 <!ELEMENT method-name (#PCDATA)>
999
1000<!--
1001The method-param element contains the fully-qualified Java type name
1002of a method parameter.
1003
1004Used in: method-params
1005-->
1006<!ELEMENT method-param (#PCDATA)>
1007
1008<!--
1009The method-params element contains a list of the fully-qualified Java
1010type names of the method parameters.
1011
1012Used in: method, query-method
1013-->
1014<!ELEMENT method-params (method-param*)>
1015
1016
1017
1018*/

1019
Popular Tags