KickJava   Java API By Example, From Geeks To Geeks.

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


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 SasContext matches the schema element sas-context
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 SasContext extends com.sun.enterprise.tools.common.dd.SunBaseBean
40 {
41
42     static Vector comparators = new Vector();
43
44     static public final String JavaDoc CALLER_PROPAGATION = "CallerPropagation"; // NOI18N
45

46     public SasContext() {
47         this(Common.USE_DEFAULT_VALUES);
48     }
49
50     public SasContext(int options)
51     {
52         super(comparators, new org.netbeans.modules.schema2beans.Version(1, 2, 0));
53         // Properties (see root bean comments for the bean graph)
54
this.createProperty("caller-propagation", // NOI18N
55
CALLER_PROPAGATION,
56             Common.TYPE_1 | Common.TYPE_STRING | Common.TYPE_KEY,
57             String JavaDoc.class);
58         this.initialize(options);
59     }
60
61     // Setting the default values of the properties
62
void initialize(int options)
63     {
64     
65     }
66
67     // This attribute is mandatory
68
public void setCallerPropagation(String JavaDoc value) {
69         this.setValue(CALLER_PROPAGATION, value);
70     }
71
72     //
73
public String JavaDoc getCallerPropagation() {
74         return (String JavaDoc)this.getValue(CALLER_PROPAGATION);
75     }
76
77     //
78
public static void addComparator(org.netbeans.modules.schema2beans.BeanComparator c) {
79         comparators.add(c);
80     }
81
82     //
83
public static void removeComparator(org.netbeans.modules.schema2beans.BeanComparator c) {
84         comparators.remove(c);
85     }
86     public void validate() throws org.netbeans.modules.schema2beans.ValidateException {
87         boolean restrictionFailure = false;
88         // Validating property callerPropagation
89
if (getCallerPropagation() == null) {
90             throw new org.netbeans.modules.schema2beans.ValidateException("getCallerPropagation() == null", "callerPropagation", this); // NOI18N
91
}
92     }
93
94     // Dump the content of this bean returning it as a String
95
public void dump(StringBuffer JavaDoc str, String JavaDoc indent){
96         String JavaDoc s;
97         Object JavaDoc o;
98         org.netbeans.modules.schema2beans.BaseBean n;
99         str.append(indent);
100         str.append("CallerPropagation"); // NOI18N
101
str.append(indent+"\t"); // NOI18N
102
str.append("<"); // NOI18N
103
s = this.getCallerPropagation();
104         str.append((s==null?"null":s.trim())); // NOI18N
105
str.append(">\n"); // NOI18N
106
this.dumpAttributes(CALLER_PROPAGATION, 0, str, indent);
107
108     }
109     public String JavaDoc dumpBeanNode(){
110         StringBuffer JavaDoc str = new StringBuffer JavaDoc();
111         str.append("SasContext\n"); // NOI18N
112
this.dump(str, "\n "); // NOI18N
113
return str.toString();
114     }}
115
116 // END_NOI18N
117

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

963
Popular Tags