[jbosstools-commits] JBoss Tools SVN: r12974 - in trunk/as/plugins/org.jboss.ide.eclipse.as.core: dtd and 1 other directory.

Author: snjeza Date: 2009-01-10 13:43:00 -0500 (Sat, 10 Jan 2009) New Revision: 12974 Added: trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-app_5_0.dtd trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-ds_5_0.dtd trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-service_5_0.dtd trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-web_5_0.dtd trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss_5_0.dtd trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/service-ref_5_0.dtd Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.core/plugin.xml Log: JBIDE-3472 XML catalog missing for JBoss 5.0 Added: trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-app_5_0.dtd =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-app_5_0.dtd (rev 0) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-app_5_0.dtd 2009-01-10 18:43:00 UTC (rev 12974) @@ -0,0 +1,194 @@ +<?xml version='1.0' encoding='UTF-8' ?> + +<!-- The JBoss 5.x specific elements for ears. +$Id: jboss-app_5_0.dtd 81860 2008-11-30 22:12:20Z alex.loubyansky(a)jboss.com $ + +DOCTYPE jboss-app + PUBLIC "-//JBoss//DTD Java EE Application 5.0//EN" + "http://www.jboss.org/j2ee/dtd/jboss-app_5_0.dtd" +--> + +<!-- The jboss-app element is the root element. +--> +<!ELEMENT jboss-app (module-order?, security-domain?, unauthenticated-principal?, + loader-repository?, jmx-name?, library-directory?, module*, security-role*)> + + +<!-- +NOTE: legacy element from 4.x. Has absolutely no effect in JBoss_5.x. + + The value of the module-order could be implicit or strict + <module-order>strict</module-order> + or + <module-order>implicit</module-order> + The strict value indicates that the deployments of the modules will + be done in the order that would be specified in the application.xml + and jboss-app.xml file . + The implicit value indicates the deployment would follow the order + which would be specified in the DeploymentSorter. + The default order will be implicit to support backward compatibility +--> +<!ELEMENT module-order (#PCDATA)> + +<!-- + The security-domain element specifies the JNDI name of the security + manager that implements the EJBSecurityManager and RealmMapping for + the domain. When specified at the jboss level it specifies the security + domain for all j2ee components in the deployment unit. + One can override the global security-domain at the container + level using the security-domain element at the container-configuration + level. + + Used in: jboss-app +--> +<!ELEMENT security-domain (#PCDATA)> + +<!-- + The unauthenticated-principal element specifies the name of the principal + that will be returned by the EJBContext.getCallerPrincipal() method if there + is no authenticated user. This Principal has no roles or privaledges to call + any other beans. +--> +<!ELEMENT unauthenticated-principal (#PCDATA)> + +<!-- The loader-repository specifies the name of the UnifiedLoaderRepository + MBean to use for the ear to provide ear level scoping of classes deployed + in the ear. It is a unique JMX ObjectName string. It may also specify + an arbitrary configuration by including a loader-repository-config element. + +Examples: + <loader-repository>jboss.test:loader=cts-cmp2v1-sar.ear</loader-repository> + + <loader-repository loaderRepositoryClass='dot.com.LoaderRepository'> + dot.com:loader=unique-archive-name + <loader-repository-config configParserClass='dot.com.LoaderParser'> + java2ParentDelegaton=true + </loader-repository-config> + </loader-repository> +--> +<!ELEMENT loader-repository (#PCDATA | loader-repository-config)*> +<!-- The loaderRepositoryClass attribute gives the classname of the +org.jboss.mx.loading.LoaderRepository implementation. +--> +<!ATTLIST loader-repository loaderRepositoryClass CDATA #IMPLIED> + +<!-- The loader-repository-config element specifies any arbitrary configuration +fragment for use in configuring the loader-repository instance. The actual +content of this element is specific to the loaderRepositoryClass and the +code parsing the element. +--> +<!ELEMENT loader-repository-config (#PCDATA)> +<!-- The configParserClass attribute gives the classname of the +org.jboss.mx.loading.LoaderRepositoryFactory.LoaderRepositoryConfigParser +implementation to use to parse the loader-repository-config content. +--> +<!ATTLIST loader-repository-config configParserClass CDATA #IMPLIED> + +<!-- The jmx-name element allows one to specify the JMX ObjectName to use +for the MBean associated with the ejb-jar module. This must be a unique +name and valid JMX ObjectName string. + + Used in: jboss-app +--> +<!ELEMENT jmx-name (#PCDATA)> + +<!-- An .ear file may contain a directory that contains libraries packaged in JAR files. +The library-directory element of the .ear files deployment descriptor contains the name +of this directory. If a library-directory element is not specified, +the directory named lib is used. + +An empty library-directory element may be used to specify that there is no library directory. + +All files in this directory (but not subdirectories) with a .jar extension must be made available +to all components packaged in the EAR file, including application clients. + + Used in: jboss-app +--> +<!ELEMENT library-directory (#PCDATA)> + +<!-- The module element is used to specify a jboss specific module archive. +--> +<!ELEMENT module (service | har | web)> + +<!-- The service element specifies a service archive (SAR) to deploy. + +Example: + <module> + <service>external.sar</service> + </module> +--> +<!ELEMENT service (#PCDATA)> + +<!-- The har element specifies a Hibernate archive (HAR) to deploy. + +Example: + <module> + <har>myapp.har</har> + </module> +--> +<!ELEMENT har (#PCDATA)> + +<!-- The web element specifies a war + +Example: + <module> + <web> + <web-uri>myapp.war</web-uri> + <context-root>/myapp</context-root> + </web> + </module> +--> +<!ELEMENT web (web-uri, context-root)> + +<!-- +The web-uri element specifies the URI of a web application file, +relative to the top level of the application package. + +Used in: web +--> +<!ELEMENT web-uri (#PCDATA)> + +<!-- The context-root element specifies the context root of a web +application. This is normally specified at the ear level using the standard +J2EE application.xml descriptor, but it may be given here for standalone wars. +This should not override the application.xml level specification. +Used in: web +--> +<!ELEMENT context-root (#PCDATA)> + +<!-- + The security-role element contains the definition of a security role. + The definition consists of an the security role name and principal name element(s). + +Used in: jboss-app + +Example: + <security-role> + <role-name>Manager</role-name> + <principal-name>j2ee</principal-name> + <principal-name>javajoe</principal-name> + </security-role> +--> +<!ELEMENT security-role (role-name, principal-name+)> + +<!-- + The role-name element is the name of the role. + + Used in: security-role +--> +<!ELEMENT role-name (#PCDATA)> + +<!-- + The principal-name element is the name of the principal that is mapped + to the assembly role-name. + + Used in: security-role +--> +<!ELEMENT principal-name (#PCDATA)> + +<!-- Allow the jboss-app to have a unique id --> +<!ATTLIST jboss-app id ID #IMPLIED> +<!-- Allow the module to have a unique id --> +<!ATTLIST module id ID #IMPLIED> +<!-- Allow the security-role to have a unique id --> +<!ATTLIST security-role id ID #IMPLIED> Added: trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-ds_5_0.dtd =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-ds_5_0.dtd (rev 0) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-ds_5_0.dtd 2009-01-10 18:43:00 UTC (rev 12974) @@ -0,0 +1,511 @@ +<?xml version='1.0' encoding='UTF-8' ?> + +<!-- DTD for the JCA 1.5 datasources and connection factory configurations (*-ds.xml) in JBoss-5.0.x, + transformed by ConnectionFactoryTemplate.xsl + +DOCTYPE datasources + PUBLIC "-//JBoss//DTD JBOSS JCA Config 5.0//EN" + "http://www.jboss.org/j2ee/dtd/jboss-ds_5_0.dtd" + +DOCTYPE connection-factories + PUBLIC "-//JBoss//DTD JBOSS JCA Config 5.0//EN" + "http://www.jboss.org/j2ee/dtd/jboss-ds_5_0.dtd" + +$Id: jboss-ds_5_0.dtd 76316 2008-07-28 17:24:52Z adrian(a)jboss.org $ +--> + +<!-- +The datasources element is the root of the jdbc datasource configuration +--> +<!ELEMENT datasources (loader-repository? , (mbean | local-tx-datasource | xa-datasource | no-tx-datasource | + ha-local-tx-datasource | ha-xa-datasource)*)> + +<!-- Specify a jca-jdbc non-XADatasource (local) wrapper, using no transactions +--> +<!ELEMENT no-tx-datasource (jndi-name , use-java-context?, connection-url , +url-delimiter?, url-selector-strategy-class-name?, +driver-class , connection-property* , user-name? , password? , +(application-managed-security | security-domain | security-domain-and-application)? , +min-pool-size? , max-pool-size? , blocking-timeout-millis? , background-validation?, background-validation-millis? , idle-timeout-minutes?, +allocation-retry?, allocation-retry-wait-millis?, validate-on-match?, new-connection-sql?, check-valid-connection-sql?, valid-connection-checker-class-name?, +exception-sorter-class-name?, stale-connection-checker-class-name?, track-statements?, +prefill?, use-fast-fail?, +prepared-statement-cache-size?, share-prepared-statements? , set-tx-query-timeout?, query-timeout?, use-try-lock?, +metadata?, type-mapping?, depends*)> + +<!-- Specify a jca-jdbc non-XADatasource (local) wrapper, using local +transactions +--> +<!ELEMENT local-tx-datasource (jndi-name , use-java-context?, connection-url , +url-delimiter?, url-selector-strategy-class-name?, +driver-class, transaction-isolation? , connection-property* , user-name? , password? , +(application-managed-security | security-domain | security-domain-and-application)? , +min-pool-size? , max-pool-size? , blocking-timeout-millis? , background-validation?, background-validation-millis?, +validate-on-match?, idle-timeout-minutes? , allocation-retry?, allocation-retry-wait-millis?, +no-tx-separate-pools? , new-connection-sql? , check-valid-connection-sql? , +valid-connection-checker-class-name? , exception-sorter-class-name? , stale-connection-checker-class-name?, track-statements? , +prefill?, use-fast-fail?, +prepared-statement-cache-size?, share-prepared-statements? , set-tx-query-timeout?, query-timeout?, use-try-lock?, +metadata?, type-mapping?, depends*)> + +<!-- Specify a jca-jdbc XADatasource wrapper +--> +<!ELEMENT xa-datasource (jndi-name , use-java-context?, track-connection-by-tx?, interleaving?, xa-datasource-class, +xa-datasource-property* , url-property?, url-delimiter?, url-selector-strategy-class-name?, +isSameRM-override-value? , transaction-isolation? , user-name? , password? , +(application-managed-security | security-domain | security-domain-and-application)? , +min-pool-size? , max-pool-size? , blocking-timeout-millis? , background-validation?, background-validation-millis? , idle-timeout-minutes? , +allocation-retry?, allocation-retry-wait-millis?, validate-on-match?, no-tx-separate-pools? , xa-resource-timeout?, new-connection-sql? , check-valid-connection-sql? , +valid-connection-checker-class-name? , exception-sorter-class-name? , stale-connection-checker-class-name?, track-statements? , +prefill?, use-fast-fail?, +prepared-statement-cache-size?, share-prepared-statements? , set-tx-query-timeout?, query-timeout?, use-try-lock?, +metadata?, type-mapping?, depends*)> + +<!-- The JNDI name under which the DataSource wrapper will be bound. Note that +this name is relative to the "java:/" prefix unless use-java-context is false. +Ex: +<jndi-name>DefaultDS</jndi-name> +--> +<!ELEMENT jndi-name (#PCDATA)> + +<!-- Setting this to false will bind the DataSource into global jndi +Ex: +<use-java-context>false</use-java-context> +--> +<!ELEMENT use-java-context (#PCDATA)> + +<!-- The JDBC driver connection URL string +Ex: +<connection-url>jdbc:hsqldb:hsql://localhost:1701</connection-url> +--> +<!ELEMENT connection-url (#PCDATA)> + +<!-- The fully qualifed name of the JDBC driver class + Ex: + <driver-class>org.hsqldb.jdbcDriver</driver-class> +--> +<!ELEMENT driver-class (#PCDATA)> + +<!-- Set java.sql.Connection transaction isolation level to use. +The constants defined in the interface Connection are the possible transaction +isolation levels and include: + TRANSACTION_READ_UNCOMMITTED + TRANSACTION_READ_COMMITTED + TRANSACTION_REPEATABLE_READ + TRANSACTION_SERIALIZABLE + TRANSACTION_NONE + + Ex: + <transaction-isolation>TRANSACTION_SERIALIZABLE</transaction-isoation> +--> +<!ELEMENT transaction-isolation (#PCDATA)> + +<!-- Specify the default username used when creating a new connection. + Ex: + <user-name>sa</user-name> +--> +<!ELEMENT user-name (#PCDATA)> + +<!-- Specify the default password used when creating a new connection. + Ex: + <password>sa-pass</password> +--> +<!ELEMENT password (#PCDATA)> + +<!-- Indicates that app supplied parameters (such as from getConnection(user, pw)) +are used to distinguish connections in the pool. + Ex: + <application-managed-security/> +--> +<!ELEMENT application-managed-security EMPTY> + +<!-- Indicates Subject (from security domain) are used to distinguish connections in the pool. +The content of the security-domain is the name of the JAAS security manager that will handle +authentication. This name correlates to the JAAS login-config.xml descriptor +application-policy/name attribute. + + Ex: + <security-domain>HsqlDbRealm</security-domain> +--> +<!ELEMENT security-domain (#PCDATA)> + +<!-- Indicates that either app supplied parameters (such as from +getConnection(user, pw)) or Subject (from security domain) are used to +distinguish connections in the pool. The content of the +security-domain is the name of the JAAS security manager that will handle +authentication. This name correlates to the JAAS login-config.xml descriptor +application-policy/name attribute. + + Ex: + <security-domain-and-application>HsqlDbRealm</security-domain-and-application> +--> +<!ELEMENT security-domain-and-application (#PCDATA)> + +<!-- Whether to use separete pools for connection retrieved in a transaction + and those retieved outside a transaction +e.g. + <no-tx-separate-pools/> +--> +<!ELEMENT no-tx-separate-pools EMPTY> + +<!-- The min-pool-size element indicates the minimum number of connections a +pool should hold. These are not created until a Subject is known from a +request for a connection. This default to 0. + + Ex: + <min-pool-size>1</min-pool-size> +--> +<!ELEMENT min-pool-size (#PCDATA)> + +<!-- The max-pool-size element indicates the maximum number of connections for a +pool. No more than MaxSize connections will be created in each sub-pool. This +defaults to 20. +--> +<!ELEMENT max-pool-size (#PCDATA)> + +<!-- The blocking-timeout-millis element indicates the maximum time in +milliseconds to block while waiting for a connection before throwing an +exception. Note that this blocks only while waiting for a permit for a +connection, and will never throw an exception if creating a new connection +takes an inordinately long time. The default is 30000 (30 seconds). +--> +<!ELEMENT blocking-timeout-millis (#PCDATA)> + +<!-- The idle-timeout-minutes elements indicates the maximum time in +minutes a connection may be idle before being closed. The actual maximum time +depends also on the IdleRemover scan time, which is 1/2 the smallest +idle-timeout-minutes of any pool. +--> +<!ELEMENT idle-timeout-minutes (#PCDATA)> + +<!-- The allocation retry element indicates the number of times that allocating +a connection should be tried before throwing an exception. The default is 0. +--> +<!ELEMENT allocation-retry (#PCDATA)> + +<!-- The allocation retry wait millis element indicates the time in +milliseconds to wait between retrying to allocate a connection. +The default is 5000 (5 seconds). +--> +<!ELEMENT allocation-retry-wait-millis (#PCDATA)> + +<!-- The validate-on-match element indicates whether or not connection level validation should be done when a connection factory attempts to +match a managed connection for a given set. This is typically exclusive to the use of background validation --> + +<!ELEMENT validate-on-match (#PCDATA)> + +<!-- An element to specify that connections should be validated on a background thread versus being validated + prior to use--> +<!ELEMENT background-validation (#PCDATA)> + +<!-- The background-validation-minutes element specifies the amount of time, in minutes, that background validation + will run. --> +<!ELEMENT background-validation-minutes (#PCDATA)> + +<!-- An element to specify that all intermediate end(suspend) and +start(resume) calls. Also, all work on one tx will go through one +connection. +A side effect of this (currently at least) is that a connection will only +be usable by one tx until the tx commits. + Ex: + <track-connection-by-tx/> +DEPRECATED: this element is now deprecated (it is assumed to present by default, also see <interleaving/>) +--> +<!ELEMENT track-connection-by-tx EMPTY> + +<!-- An element to enable interleaving for XA connection factories + Ex: + <interleaving/> +--> +<!ELEMENT interleaving EMPTY> + +<!-- The fully qualifed name of the javax.sql.XADataSource implementation class. + Ex: + <xa-datasource-class>com.informix.jdbcx.IfxXADataSource</xa-datasource-class> +--> +<!ELEMENT xa-datasource-class (#PCDATA)> + +<!-- Specify a property to assign to the XADataSource implementation class. +Each property is identified by the name attribute and the property value is +given by the xa-datasource-property element content. The property is mapped +onto the XADataSource implementation by looking for a JavaBeans style +getter method for the property name. If found, the value of the property is +set using the JavaBeans setter with the element text translated to the true +property type using the java.beans.PropertyEditor for the type. + + Ex: + <xa-datasource-property name="IfxWAITTIME">10</xa-datasource-property> + <xa-datasource-property name="IfxIFXHOST">myhost.mydomain.com</xa-datasource-property> + <xa-datasource-property name="PortNumber">1557</xa-datasource-property> + <xa-datasource-property name="DatabaseName">mydb</xa-datasource-property> + <xa-datasource-property name="ServerName">myserver</xa-datasource-property> +--> +<!ELEMENT xa-datasource-property (#PCDATA)> + +<!-- The xa-datasource-property name attribute specifies the name of the +XADataSource attribute the xa-datasource-property element content provides +the value of. +--> +<!ATTLIST xa-datasource-property name CDATA #REQUIRED> + +<!-- The isSameRM-override-value element allows one to unconditionally set +whether the javax.transaction.xa.XAResource.isSameRM(XAResource) returns +true or false. + +Ex: +<isSameRM-override-value>true</isSameRM-override-value> +--> +<!ELEMENT isSameRM-override-value (#PCDATA)> + +<!-- The connection-property element allows you to pass in arbitrary connection +properties to the Driver.connect(url, props) method. Each connection-property +specifies a string name/value pair with the property name coming from the +name attribute and the value coming from the element content. + + Ex: + <connection-property name="char.encoding">UTF-8</connection-property> +--> +<!ELEMENT connection-property (#PCDATA)> + +<!-- The connection-property name attribute gives the name of the connection +property. +--> +<!ATTLIST connection-property name CDATA #REQUIRED> + +<!-- Specify an SQL statement to execute whenever a connection is added to +the connection pool. +--> +<!ELEMENT new-connection-sql (#PCDATA)> + +<!-- Specify an SQL statement to check validity of a pool connection. This +may be called when managed connection is taken from pool for use. +--> +<!ELEMENT check-valid-connection-sql (#PCDATA)> + +<!-- An org.jboss.resource.adapter.jdbc.ValidConnectionChecker that provides +a SQLException isValidConnection(Connection e) method to validate is a connection +is valid. An exception means the connection is destroyed. +This overrides the check-valid-connection-sql when present. + +Ex: +<exception-sorter-class-name> + org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker +</exception-sorter-class-name> +--> +<!ELEMENT valid-connection-checker-class-name (#PCDATA)> + +<!-- An org.jboss.resource.adapter.jdbc.ExceptionSorter that provides +a boolean isExceptionFatal(SQLException e) method to validate is an exception +should be broadcast to all javax.resource.spi.ConnectionEventListener as +a connectionErrorOccurred message. + +Ex: +<exception-sorter-class-name> + org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter +</exception-sorter-class-name> +<exception-sorter-class-name> + org.jboss.resource.adapter.jdbc.vendor.SybaseExceptionSorter +</exception-sorter-class-name> +--> +<!ELEMENT exception-sorter-class-name (#PCDATA)> + +<!-- An org.jboss.resource.adapter.jdbc.StaleConnectionChecker that provides +a boolean isStaleConnection(SQLException e) method which if it it returns +true will wrap the exception in an +org.jboss.resource.adapter.jdbc.StaleConnectionException +which is a subclass of SQLException. + +Ex: +<stale-connection-checker-class-name> + org.jboss.resource.adapter.jdbc.vendor.OracleStaleConnectionChecker +</stale-connection-checker-class-name> +--> +<!ELEMENT stale-connection-checker-class-name (#PCDATA)> + +<!-- Whether to check for unclosed statements when a + connection is returned to the pool and result sets are + closed when a statement is closed/return to the prepared + statement cache. + valid values are: + false - do not track statements and results + true - track statements and result sets and warn when they are not closed + nowarn - track statements but do no warn about them being unclosed (the default) + e.g. + <track-statements>nowarn</track-statements> +--> +<!ELEMENT track-statements EMPTY> + +<!-- Whether to attempt to prefill the connection pool. Empty element denotes a false value. + e.g. + <prefill>true</prefill> + --> +<!ELEMENT prefill (#PCDATA) > + +<!-- Whether fail a connection allocation on the first connection if it is invalid (true) + or keep trying until the pool is exhausted of all potential connections (false) + + default false. + e.g. + <use-fast-fail>true</use-fast-fail> + --> +<!ELEMENT use-fast-fail (#PCDATA) > + +<!-- The number of prepared statements per connection in an LRU cache +--> +<!ELEMENT prepared-statement-cache-size (#PCDATA)> + +<!-- whether to share prepare statements, i.e. whether asking for same + statement twice without closing uses the same underlying prepared statement. + + The default is false. + e.g. + <share-prepared-statements/> +--> +<!ELEMENT share-prepared-statements EMPTY> + +<!-- whether to set the query timeout based on the time remaining until transaction timeout, + any configured query timeout will be used if there is no transaction. + + The default is false. + e.g. + <set-tx-query-timeout/> +--> +<!ELEMENT set-tx-query-timeout EMPTY> + +<!-- Any configured query timeout in seconds + + The default is no timeout + e.g. 5 minutes + <query-timeout>300</query-timeout> +--> +<!ELEMENT query-timeout (#PCDATA)> + +<!-- Any configured timeout for internal locks on the resource adapter objects in milli-seconds + + The default is a 60 second timeout + e.g. 5 minutes + <use-try-lock>300000</use-try-lock> +--> +<!ELEMENT use-try-lock (#PCDATA)> + +<!-- The depends element specifies the JMX ObjectName string of a service +that the connection manager services depend on. + + Ex: + <depends>jboss:service=Hypersonic</depends> +--> +<!ELEMENT depends (#PCDATA)> + +<!-- The connection-factories element is the root of the generic jca adaptor section +--> +<!ELEMENT connection-factories (loader-repository? , (mbean | tx-connection-factory | no-tx-connection-factory)*)> + +<!-- The loader repository --> +<!ELEMENT loader-repository ANY> + +<!-- Any embedded mbean --> +<!ELEMENT mbean ANY> + +<!-- The tx-connection-factory element is used to configure generic resource +adapters supporting transactions +--> +<!ELEMENT tx-connection-factory (jndi-name , (local-transaction | xa-transaction) , +track-connection-by-tx? , rar-name?, connection-definition?, config-property* , +(application-managed-security | security-domain | security-domain-and-application)? , +min-pool-size? , max-pool-size? , blocking-timeout-millis? , background-validation?, background-validation-millis? , idle-timeout-minutes? , +allocation-retry?, allocation-retry-wait-millis?, no-tx-separate-pools?, prefill?, use-fast-fail?, xa-resource-timeout?, +metadata?, type-mapping?, depends*)> + +<!-- The no-tx-connection-factory element is used to configure generic resource +adapters that do not support transactions +--> +<!ELEMENT no-tx-connection-factory (jndi-name , rar-name?, connection-definition? , config-property* , +(application-managed-security | security-domain | security-domain-and-application)? , +min-pool-size? , max-pool-size? , blocking-timeout-millis? , background-validation?, background-validation-millis? , idle-timeout-minutes? , +allocation-retry?, allocation-retry-wait-millis?, prefill?, use-fast-fail?, metadata?, type-mapping?, depends*)> + +<!-- The rar deployment to associate with the connection manager mbean. +e.g. jms-ra.rar or myapplication.ear#my.rar for nested rars +--> +<!ELEMENT rar-name (#PCDATA)> + +<!-- The connection definition inside the rar deployment uniquely identified by the +connection factory interface, e.g. javax.sql.DataSource +--> +<!ELEMENT connection-definition (#PCDATA)> + +<!-- Passed to XAResource.setTransactionTimeout() + + Default is zero which does not invoke the setter + e.g. 5 minutes + <xa-resource-timeout>300</xa-resource-timeout> +--> +<!ELEMENT xa-resource-timeout (#PCDATA)> + +<!-- The xa-transaction element is used to mark that the tx-connection-factory +supports XA transactions. +--> +<!ELEMENT xa-transaction EMPTY> + +<!-- The local-transaction element is used to mark that the tx-connection-factory +supports local transactions. +--> +<!ELEMENT local-transaction EMPTY> + +<!-- The config-property specifies a mannaged connection factory property. +--> +<!ELEMENT config-property (#PCDATA)> + +<!-- The config-property name attribute gives the name of the connection +factory property. +--> +<!ATTLIST config-property name CDATA #REQUIRED> + +<!-- The config-property type attribute gives the name of the connection +factory property. +--> +<!ATTLIST config-property type CDATA #REQUIRED> + +<!-- The type mapping from conf/standardjboss.xml --> +<!ELEMENT type-mapping (#PCDATA)> + +<!-- For backwards compatibility use type-mapping --> +<!ELEMENT metadata (type-mapping)> + +<!-- +Use local-tx-datasource +--> +<!ELEMENT ha-local-tx-datasource (jndi-name, use-java-context?, connection-url, url-delimiter, +driver-class, transaction-isolation? , connection-property* , user-name? , password?, +(application-managed-security | security-domain | security-domain-and-application)? , +min-pool-size? , max-pool-size? , blocking-timeout-millis? , idle-timeout-minutes? , +allocation-retry?, allocation-retry-wait-millis?, no-tx-separate-pools? , new-connection-sql? , check-valid-connection-sql? , +valid-connection-checker-class-name? , exception-sorter-class-name? , track-statements? , +prepared-statement-cache-size?, share-prepared-statements? , set-tx-query-timeout?, query-timeout?, use-try-lock?, +metadata?, type-mapping?, depends*)> + +<!-- +Use xa-datasource +--> +<!ELEMENT ha-xa-datasource (jndi-name , use-java-context?, track-connection-by-tx , xa-datasource-class , +xa-datasource-property* , url-property, url-delimiter, isSameRM-override-value? , transaction-isolation? , +user-name? , password? , +(application-managed-security | security-domain | security-domain-and-application)? , +min-pool-size? , max-pool-size? , blocking-timeout-millis? , idle-timeout-minutes? , +allocation-retry?, allocation-retry-wait-millis?, no-tx-separate-pools? , xa-resource-timeout? , +new-connection-sql? , check-valid-connection-sql? , +valid-connection-checker-class-name? , exception-sorter-class-name? , track-statements? , +prepared-statement-cache-size?, share-prepared-statements? , set-tx-query-timeout?, query-timeout?, use-try-lock?, +type-mapping?, depends*)> + +<!-- Specifies the delimeter for URLs in connection-url for ha datasources +--> +<!ELEMENT url-delimiter (#PCDATA)> + +<!-- A class that implements org.jboss.resource.adapter.jdbc.URLSelectorStrategy +--> +<!ELEMENT url-selector-strategy-class-name (#PCDATA)> + +<!-- For HA XA datasource specifies the name of an xa-datasource-property that contains a list of URLs +--> +<!ELEMENT url-property (#PCDATA)> Added: trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-service_5_0.dtd =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-service_5_0.dtd (rev 0) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-service_5_0.dtd 2009-01-10 18:43:00 UTC (rev 12974) @@ -0,0 +1,304 @@ +<?xml version='1.0' encoding='UTF-8' ?> + +<!-- A skeleton JBoss MBean service descriptor DTD. This cannot be used in +general to validate a jboss-service.xml descriptor due to the fact that the +'attribute' element allows ANY content. + +$Id: jboss-service_4_0.dtd 33890 2005-07-24 23:58:11 +0000 (Sun, 24 Jul 2005) starksm $ + +DOCTYPE server + PUBLIC "-//JBoss//DTD MBean Service 5.0//EN" + "http://www.jboss.org/j2ee/dtd/jboss-service_5_0.dtd" +--> +<!-- The server element is the root element. +--> +<!ELEMENT server (loader-repository? , local-directory* , classpath* , mbean*)> + +<!-- The loader-repository specifies the name of the UnifiedLoaderRepository + MBean to use for the ear to provide ear level scoping of classes deployed + in the ear. It is a unique JMX ObjectName string. It may also specify + an arbitrary configuration by including a loader-repository-config element. + +Examples: + <loader-repository>jboss.test:loader=cts-cmp2v1-sar.ear</loader-repository> + + <loader-repository loaderRepositoryClass='dot.com.LoaderRepository'> + dot.com:loader=unique-archive-name + <loader-repository-config configParserClass='dot.com.LoaderParser'> + java2ParentDelegaton=true + </loader-repository-config> + </loader-repository> +--> + +<!-- +The mode of the deployments. (optional) + +Valid Values: +'On Demand' - Don't start the service unless something depends on it. +--> +<!ATTLIST server mode CDATA #IMPLIED> + +<!ELEMENT loader-repository (#PCDATA | loader-repository-config)*> + +<!-- The loaderRepositoryClass attribute gives the classname of the +org.jboss.mx.loading.LoaderRepository implementation. +--> +<!ATTLIST loader-repository loaderRepositoryClass CDATA #IMPLIED> + +<!-- The loader-repository-config element specifies any arbitrary configuration +fragment for use in configuring the loader-repository instance. The actual +content of this element is specific to the loaderRepositoryClass and the +code parsing the element. +--> +<!ELEMENT loader-repository-config (#PCDATA)> + +<!-- The configParserClass attribute gives the classname of the +org.jboss.mx.loading.LoaderRepositoryFactory.LoaderRepositoryConfigParser +implementation to use to parse the loader-repository-config content. +--> +<!ATTLIST loader-repository-config configParserClass CDATA #IMPLIED> + +<!-- A local-directory element specifies that portions of the sar are to be unjard into the data +directory of the server configuration. +--> +<!ELEMENT local-directory EMPTY> + +<!-- The optional path attribute gives the prefix of the sar entries that should be copied +into the data directory. If it is not specified the entire sar contents will be placed into +the data directory. +--> +<!ATTLIST local-directory path CDATA #IMPLIED> + +<!-- A classpath element specifies a location which will be included in the services +deployment classpath. +--> +<!ELEMENT classpath EMPTY> + +<!-- The codebase attribute specifies the base URL from which the jars or classes +are loaded from. If the codebase is '.' then it is equal to the mbean deployment URL. +Otherwise, it is resolved as a path spec relative to the serverHomeURL (e.g., file:/jboss-3.2.0) +using the URL ctor URL(serverHomeURL, codebase) + +Examples: + + <classpath codebase='.' archives='util.jar' /> + <classpath codebase='http://classloader.dot.com' archives='*' /> + <classpath codebase="lib" archives="*"/> +--> +<!ATTLIST classpath codebase CDATA #REQUIRED> + +<!-- The archives attribute specifies either the '*' wildcard to indicate all contents of the +codebase should be included, or a comma seperated list of the jars to include. +--> +<!ATTLIST classpath archives CDATA #IMPLIED> + +<!-- The mbean element defines a JBoss MBean service. This includes the +mbean class, attributes and dependencies. +--> +<!ELEMENT mbean (constructor? , xmbean? , attribute* , depends* , depends-list*)> + +<!-- The code attributes gives the fully qualified name of the MBean +implementation class. +--> +<!ATTLIST mbean code CDATA #REQUIRED> + +<!-- The name attribute gives the JMX ObjectName string to use when registering +the MBean. This must be a unique and valid JMX name. +--> +<!ATTLIST mbean name CDATA #REQUIRED> + +<!-- The optional interface attribute gives the full qualified name of the class +uses to construct the management interface of the mbean. In absence of it an interface +with the name ending by MBean will be looked in the implementation class. When used +this interface is defined explicitely. +--> +<!ATTLIST mbean interface CDATA #IMPLIED> + +<!-- +The mode of the mbean. (optional) + +Valid Values: +'On Demand' - Don't start the service unless something depends on it. +--> +<!ATTLIST mbean mode CDATA #IMPLIED> + +<!-- The xmbean-dd attribute defines the path to the JBoss XMBean descriptor. This +is an xml document conforming to: + +<!DOCTYPE mbean PUBLIC + "-//JBoss//DTD JBOSS XMBEAN 1.0//EN" + "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_0.dtd"> + +If the descriptor is embedded via a nested xmbean element, the xmbean-dd attribute +must be given as an empty string. + +Example: + <mbean code="org.jboss.test.jmx.xmbean.User" + name="jboss.test:service=xmbean-user" + xmbean-dd="META-INF/org/jboss/test/jmx/xmbean/User.xml" /> +--> +<!ATTLIST mbean xmbean-dd CDATA #IMPLIED> + +<!-- The optional xmbean-code attribute specifies the ModelMBean implementation class +to use. This defaults to org.jboss.mx.modelmbean.XMBean. +--> +<!ATTLIST mbean xmbean-code CDATA #IMPLIED> + +<!-- The xmbean element specifies a nested JBoss XMBean descriptor fragment. Its +supported content model is the same as the mbean element of the jboss_xmbean_1_0.dtd + +Example: + <mbean code="org.jboss.test.jmx.xmbean.User" + name="jboss.test:service=xmbean-user" + xmbean-dd=""> + <xmbean> + ... + </xmbean> + </mbean> +--> +<!ELEMENT xmbean ANY> + +<!-- The constructor element defines a non-default constructor to use when +instantiating the mbean. +--> +<!ELEMENT constructor (arg*)> + +<!-- The arg element specify the constructor arguments in the order of the +ctor signature. Each arg has a type and value attribute. +--> +<!ELEMENT arg EMPTY> + +<!-- The type attribute gives the type of the argument as defined in the +ctor signature. If not defined java.lang.String is assumed. +--> +<!ATTLIST arg type CDATA #IMPLIED> + +<!-- The value attribute provides the string representation of the ctor +argument. It is converted from a string to type using Java PropertyEditor or a +ctor taking a single string as its argument. +--> +<!ATTLIST arg value CDATA #REQUIRED> + +<!-- The attribute element specifies the initial value for a management attribute of +the enclosing mbean. Typically the value of the attribute element is the string +representation of the attribute, but it can be an arbitrary xml fragment that is +parsed by the mbean. +--> +<!ELEMENT attribute ANY> + +<!-- The required name attribute gives the name of the attribute. This is the +name exposed by the mbean to the MBeanServer for the attribute. +--> +<!ATTLIST attribute name CDATA #REQUIRED> + +<!-- The optional replace attribute indicates whether references of the form ${x} +in the attribute element content should be replaced with the corresponding +System.getProperty(x) value. +--> +<!ATTLIST attribute replace (true | false) 'true'> +<!-- The optional trim attribute specifies whether the attribute element content should +be trimmed of whitespace. +--> +<!ATTLIST attribute trim (true | false) 'true'> + +<!-- The attributeClass attribute specifies that type of object that +should be created. This is needed for non-concreate attribute types +like interfaces and abstract classes. +--> +<!ATTLIST attribute attributeClass CDATA #IMPLIED> + +<!-- The serialDataType defines the how the content of the attribute +element is interpretted by the ServiceConfigurator. The possible values +are: + + text: the content is treated as the string representation of the + attribute value. It will be mapped to the attribute using the PropertyEditor + registered for the attribute type. + + javaBean: the content is a collection of property elements. + + jbxb: the content is an xml element from a namespace with an associated + xml schema that can be unmarshalled using the JBossXB framework. +--> +<!ATTLIST attribute serialDataType (text | javaBean | jbxb) 'text'> + +<!-- The property element is used to describe the JavaBean properties of +an attribute when the attribute element serialDataType is javaBean. +--> +<!ELEMENT property (#PCDATA)> +<!-- The required name attribute gives the name of the property. This is the +name of a JavaBean property for the attribute type. +--> +<!ATTLIST property name CDATA #REQUIRED> + +<!-- The depends element specifies a JMX ObjectName string for an mbean +on which the enclosing mbean depends. + +Example: + <mbean code="myBean" name="domain:name=x"> + <depends optional-attribute-name="yName">domain:name=y</depends> + </mbean> + + <mbean code="myBean" name="domain:name=x"> + <depends optional-attribute-name="anonName"> + <mbean code="nestedBean" name="domain:name=x.y"> + ... + </mbean> + </depends> + </mbean> +--> +<!ELEMENT depends (#PCDATA | mbean)*> + +<!-- The optional-attribute-name attribute specifies the attribute name +which should be populated with the JMX ObjectName of the depends element. +This allows an mbean to have access to the name of the mbean on which +it depends. +--> +<!ATTLIST depends optional-attribute-name CDATA #IMPLIED> + +<!-- The proxy-type attribute specifies the interface name +that should be exposed on an MBeanProxy pointing at the dependent +MBean, specified by the JMX ObjectName. + +The special value proxy-type="attribute" will use the +class declared in the MBeanAttributeInfo as the interface +for the MBeanProxy. + +Example: + <mbean code="org.jboss.example.Helper" name="domain:name=helper"/> + + <mbean code="myBean" name="domain:name=x"> + <depends optional-attribute-name="Helper" + proxy-type="org.jboss.example.HelperMBean" + >domain:name=helper</depends> + </mbean> + + <mbean code="myBean" name="domain:name=x"> + <depends optional-attribute-name="Helper" + proxy-type="attribute" + >domain:name=helper</depends> + </mbean> +--> +<!ATTLIST depends proxy-type CDATA #IMPLIED> + +<!-- The depends-list element specifies a series of JMX ObjectName +strings of mbeans on which the enclosing mbean depends. + +Example: + <mbean code="myBean" name="domain:name=x"> + <depends-list optional-attribute-name="myObjectNameList"> + <depends-list-element>domain:name=y</depends-list-element> + <depends-list-element>domain:name=z</depends-list-element> + </depends-list> + </mbean> +--> +<!ELEMENT depends-list (depends-list-element)+> + +<!-- The optional-attribute-name attribute specifies the attribute name +which should be populated with a java.util.List that contains the JMX +ObjectName(s) of the depends-list elements. This allows an mbean to have +access to the names of the mbeans on which it depends. +--> +<!ATTLIST depends-list optional-attribute-name CDATA #IMPLIED> + +<!-- The depends-list-element element specifies a JMX ObjectName string +for an mbean on which the enclosing mbean depends. +--> +<!ELEMENT depends-list-element (#PCDATA | mbean)*> Added: trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-web_5_0.dtd =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-web_5_0.dtd (rev 0) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss-web_5_0.dtd 2009-01-10 18:43:00 UTC (rev 12974) @@ -0,0 +1,602 @@ +<?xml version='1.0' encoding='UTF-8' ?> + +<!-- +$Id: jboss-web_5_0.dtd 81860 2008-11-30 22:12:20Z alex.loubyansky(a)jboss.com $ + +The JBoss specific elements used to integrate the servlet 2.4 web.xml +elements into a JBoss deployment. This version applies to the JBoss 5.0.x +releases. + + <!DOCTYPE jboss-web PUBLIC + "-//JBoss//DTD Web Application 5.0//EN" + "http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd"> +--> + +<!ENTITY % service-ref PUBLIC + "-//JBoss//DTD Web Service Reference 5.0//EN" + "http://www.jboss.org/j2ee/dtd/service-ref_5_0.dtd"> + +%service-ref; + +<!-- The jboss-web element is the root element. +--> +<!ELEMENT jboss-web (class-loading?, security-domain?, jacc-star-role-allow?, context-root?, + virtual-host*, use-session-cookies?, replication-config?, resource-env-ref*, + ejb-ref*, ejb-local-ref*, service-ref*, resource-ref*, + message-destination-ref*, security-role*, message-destination*, + webservice-description*, depends*, servlet*, max-active-sessions?, passivation-config?)> + +<!-- The class-loading element allows one to override the default class +loading behavior of the web container. You can specify the +Examples: + <class-loading java2ClassLoadingCompliance='false'/> + + <class-loading java2ClassLoadingCompliance='false'> + <loader-repository loaderRepositoryClass='dot.com.LoaderRepository'> + ... + </loader-repository> + </class-loading> +--> +<!ELEMENT class-loading (loader-repository?)> +<!-- The java2ClassLoadingCompliance attribute indicates if the normal Java2 +parent first class loading model should be used over the servlet 2.3 web +container first model. +--> +<!ATTLIST class-loading java2ClassLoadingCompliance CDATA #IMPLIED> + +<!-- The loader-repository specifies the name of the UnifiedLoaderRepository + MBean to use for the ear to provide ear level scoping of classes deployed + in the ear. It is a unique JMX ObjectName string. It may also specify + an arbitrary configuration by including a loader-repository-config element. + +Examples: + <class-loading> + <loader-repository>jboss.test:loader=cts-cmp2v1-sar.ear</loader-repository> + </class-loading> + + <class-loading java2ClassLoadingCompliance='false'> + <loader-repository loaderRepositoryClass='dot.com.LoaderRepository'> + dot.com:loader=unique-archive-name + <loader-repository-config configParserClass='dot.com.LoaderParser'> + java2ParentDelegaton=true + </loader-repository-config> + </loader-repository> + </class-loading> +--> +<!ELEMENT loader-repository (#PCDATA | loader-repository-config)*> +<!-- The loaderRepositoryClass attribute gives the classname of the +org.jboss.mx.loading.LoaderRepository implementation. +--> +<!ATTLIST loader-repository loaderRepositoryClass CDATA #IMPLIED> + +<!-- The loader-repository-config element specifies any arbitrary configuration +fragment for use in configuring the loader-repository instance. The actual +content of this element is specific to the loaderRepositoryClass and the +code parsing the element. +--> +<!ELEMENT loader-repository-config (#PCDATA)> +<!-- The configParserClass attribute gives the classname of the +org.jboss.mx.loading.LoaderRepositoryFactory.LoaderRepositoryConfigParser +implementation to use to parse the loader-repository-config content. +--> +<!ATTLIST loader-repository-config configParserClass CDATA #IMPLIED> + +<!-- The context-root element specifies the context root of a web +application. This is normally specified at the ear level using the standard +J2EE application.xml descriptor, but it may be given here for standalone wars. +This should not override the application.xml level specification. +--> +<!ELEMENT context-root (#PCDATA)> + +<!-- (JBAS-1824) The jacc-star-role-allow element specifies whether the +jacc permission generating agent in the web layer needs to generate a +WebResourcePermission(url,null) permission such that the jacc provider can +make a decision as to bypass authorization or not. +--> +<!ELEMENT jacc-star-role-allow (#PCDATA)> + +<!-- The security-domain element allows one to specify a module wide +security manager domain. It specifies the JNDI name of the security +manager that implements the org.jboss.security.AuthenticationManager and +org.jboss.security.RealmMapping interfaces for the domain. +--> +<!ELEMENT security-domain (#PCDATA)> + +<!-- The flushOnSessionInvalidation attribute is a boolean indicating whether +the associated security domain cache should be flushed when the web session is +invalidated. If true, the security manager service +flushAuthenticationCache(String, java.security.Principal) is called when the +session is seen to be invalid due to expiration or explicit invalidation. +--> +<!ATTLIST security-domain flushOnSessionInvalidation (true|false) 'false'> + +<!-- The virtual-host element allows one to specify which virtual host the war +should be deployed to. Example, to specify that a war should be deployed to the +www.jboss-store.org virtual host add the following virtual-host element: + <virtual-host>www.jboss-store.org</virtual-host> +--> +<!ELEMENT virtual-host (#PCDATA)> + +<!--The resource-env-ref element maps from the servlet ENC relative name +of the resource-env-ref to the deployment environment JNDI name of +the administered object resource. +Example: + <resource-env-ref> + <resource-env-ref-name>jms/NewsTopic</resource-env-ref-name> + <jndi-name>topic/NewsTopic</jndi-name> + </resource-env-ref> +--> +<!ELEMENT resource-env-ref (resource-env-ref-name , jndi-name)> + +<!-- The resource-env-ref-name specifies the name of the web.xml +resource-env-ref-name element which this mapping applies. +--> +<!ELEMENT resource-env-ref-name (#PCDATA)> + +<!--The resource-ref element maps from the servlet ENC relative name +of the resource-ref to the deployment environment JNDI name of +the resource manager connection factory. +Example: + <resource-ref> + <res-ref-name>jdbc/TheDataSource</res-ref-name> + <jndi-name>java:/DefaultDS</jndi-name> + </resource-ref> + + <resource-ref> + <res-ref-name>jdbc/TheDataSource</res-ref-name> + <res-url>http://x.y.z</res-url> + </resource-ref> +--> +<!ELEMENT resource-ref (res-ref-name , (jndi-name | res-url))> + +<!-- The res-ref-name specifies the name of the web.xml res-ref-name element +which this mapping applies. +--> +<!ELEMENT res-ref-name (#PCDATA)> + +<!-- + The security-role element contains the definition of a security role. + The definition consists of an the security role name and principal name element(s). + +Used in: jboss-web + +Example: + <security-role> + <role-name>Manager</role-name> + <principal-name>j2ee</principal-name> + <principal-name>javajoe</principal-name> + </security-role> +--> +<!ELEMENT security-role (role-name, principal-name+)> + +<!-- + The role-name element is the name of the role. + + Used in: security-role +--> +<!ELEMENT role-name (#PCDATA)> + +<!-- + The principal-name element is the name of the principal that is mapped + to the assembly role-name. + + Used in: security-role +--> +<!ELEMENT principal-name (#PCDATA)> + +<!-- The ejb-ref element maps from the servlet ENC relative name +of the ejb reference to the deployment environment JNDI name of +the bean. +Example: + <ejb-ref> + <ejb-ref-name>ejb/Bean0</ejb-ref-name> + <jndi-name>deployed/ejbs/Bean0</jndi-name> + </ejb-ref> +--> +<!ELEMENT ejb-ref (ejb-ref-name , jndi-name)> + +<!-- The ejb-local-ref element maps from the servlet ENC relative name +of the ejb local reference to the deployment environment JNDI name of +the bean. +Example: + <ejb-local-ref> + <ejb-ref-name>ejb/Bean0</ejb-ref-name> + <local-jndi-name>deployed/ejbs/Bean0</local-jndi-name> + </ejb-local-ref> +--> +<!ELEMENT ejb-local-ref (ejb-ref-name , (local-jndi-name|jndi-name))> + +<!-- The ejb-ref-name element gives the ENC relative name used +in the web.xml ejb-ref-name element. + +Used in: ejb-ref +--> +<!ELEMENT ejb-ref-name (#PCDATA)> + +<!-- The jndi-name element specifies the JNDI name of the deployed +object to which the servlet ENC binding will link to via a JNDI +LinkRef. + +Used in: resource-ref, resource-env-ref, ejb-ref, + message-destination-ref, message-destination +--> +<!ELEMENT jndi-name (#PCDATA)> + +<!-- + The JNDI name under with the local home interface should be bound + + Used in: ejb-local-ref +--> +<!ELEMENT local-jndi-name (#PCDATA)> + +<!-- The res-url element value is a URL string for a resource-ref of +res-type = java.net.URL. Using a res-url creates a binding of the URL +instance under the java:comp/env. If you want to link to another binding +of a URL, you can use the jndi-name to do so. + +// Binds the URL(http://x.y.z) under java:comp/env/jdbc/XYZHome +<resource-ref> + <res-ref-name>jdbc/XYZHome</res-ref-name> + <res-url>http://x.y.z</res-url> +</resource-ref> +// Binds a link to urls/XYZHomePage under java:comp/env/jdbc/XYZHome +<resource-ref> + <res-ref-name>jdbc/XYZHome</res-ref-name> + <res-url>urls/XYZHomePage</res-url> +</resource-ref> + + Used in: resource-ref +--> +<!ELEMENT res-url (#PCDATA)> + +<!-- + The message-destination-ref element is used to configure the + jndi-name for a message-destination-ref in ejb-jar.xml + + Used in: jboss-web +--> +<!ELEMENT message-destination-ref (message-destination-ref-name, jndi-name)> + +<!-- + The message-destination-ref-name element identifies the + message-destination-ref. It must match the name in ejb-jar.xml + + Used in: message-destination-ref +--> +<!ELEMENT message-destination-ref-name (#PCDATA)> + +<!-- + The message-destination element is used to configure the + jndi-name for a message-destination in ejb-jar.xml + + Used in: jboss-web +--> +<!ELEMENT message-destination (message-destination-name, jndi-name)> + +<!-- + The message-destination-name element identifies the + message-destination. It must match the name in ejb-jar.xml + + Used in: message-destination +--> +<!ELEMENT message-destination-name (#PCDATA)> + +<!-- The depends element gives a JMX ObjectName of a service on which the +container or ejb depends. +--> +<!ELEMENT depends (#PCDATA)> + +<!-- The use-session-cookies element controls whether this context uses session cookies + or not. + +Example: + <use-session-cookies>true</use-session-cookies> +--> +<!ELEMENT use-session-cookies (#PCDATA)> + +<!-- Http Session max allowed sessions +--> +<!-- + Clustering only: Determines the max number of active sessions allowed. + If the number of sessions managed by the the session manager exceeds this value and + passivation is enabled, the excess will be passivated based on the configured + passivation-min-idle-time. + If after passivation is completed (or if passivation is disabled), the number of + active sessions still exceeds this limit, attempts to create new sessions + will be rejected. + If set to -1, means no limit +--> +<!ELEMENT max-active-sessions (#PCDATA)> + +<!-- + Clustering only: HTTP Session passivation configuration. (optional tags) +--> +<!ELEMENT passivation-config (use-session-passivation?, passivation-min-idle-time, passivation-max-idle-time)> + +<!-- + Clustering only: Determines whether the web application should use session passivation or not + +Examples: + <use-session-passivation>true</use-session-passivation> + or + <use-session-passivation>false</use-session-passivation> (default value) +--> +<!ELEMENT use-session-passivation (#PCDATA)> + +<!-- + Clustering only: Determines the minimum time (in seconds) that a session must have been inactive + before the container will consider passivating it in order to reduce the + active session count below max-active-sessions. + A value of -1 (the default) disables passivating sessions before + passivation-max-idle-time. Neither a value of -1 nor a high + value are recommended if max-active-sessions is set + +Example: + <passivation-min-idle-time>30</passivation-min-idle-time> (seconds) + +--> +<!ELEMENT passivation-min-idle-time (#PCDATA)> + +<!-- + Clustering only: Determines the maximum time (in seconds) that a session can be inactive before + the container should attempt to passivate it to save memory. Passivation of such + sessions will take place regardless of whether the active session count exceeds + max-active-sessions. + Should be less than the web.xml session-timeout setting. + A value of -1 disables passivation based on maximum inactivity. + +Example: + <passivation-max-idle-time>300</passivation-max-idle-time> (seconds) + +--> +<!ELEMENT passivation-max-idle-time (#PCDATA)> + +<!-- + HTTP Session clustering configuration (optional tags) +--> +<!ELEMENT replication-config (cache-name?, replication-trigger?, replication-granularity?, replication-field-batch-mode?, use-jk?, max-unreplicated-interval?, snapshot-mode?, snapshot-interval?, session-notification-policy?)> + +<!-- + Clustering only: Name of the JBoss Cache or PojoCache configuration that + should be used for storing distributable sessions and replicating them around the + cluster. + + Default value if not explicitly set is the overall web container default + as set in the deployers/jbossweb.deployer service. +--> +<!ELEMENT cache-name (#PCDATA)> + +<!-- + Clustering only: Determines when the container should consider that a session + must be replicated across the cluster. + Possible values are: + 1 - "SET_AND_GET" + 2 - "SET_AND_NON_PRIMITIVE_GET" (default value) + 3 - "SET" + + The rationale for this setting is that after a mutable object stored as a session attribute + is accessed from the session, in the absence of a setAttribute call the container has no + clear way to know if the object (and hence the session state) has been modified. + + In all cases, calling setAttribute marks the session as needing replication. + + SET_AND_GET is conservative but not optimal (performance-wise): it will always replicate the + session even if its content has not been modified but simply accessed. + + SET_AND_NON_PRIMITIVE_GET is conservative but will only replicate if a non-primitive Object + has been accessed (i.e. the object is not of a well-known immutable JDK type such as Integer, + Long, String, etc.) This is the default value. + + SET assumes that the developer will explicitly call setAttribute on the session + if it needs to be replicated. This setting prevents unnecessary replication, but requires very + good coding practices to ensure setAttribute is always called whenever an attribute value + is modified. + +Examples: + <replication-trigger>SET_AND_GET</replication-trigger> + or + <replication-trigger>SET_AND_NON_PRIMITIVE_GET</replication-trigger> + or + <replication-trigger>SET</replication-trigger> +--> +<!ELEMENT replication-trigger (#PCDATA)> + +<!-- + Clustering only: Determines the session replication granularity level. + Possible values are: + 1 - "SESSION" (default) + 2 - "ATTRIBUTE" + 3 - "FIELD" + + The first option indicates that replication is done per session instance, i.e. when + the session is considered modified, the whole session object will be serialized + and replicated. This is the preferred policy when the sessions are generally small. + + The second option indicates that replication is performed only for the the dirty + attributes in the session, plus some session data, like lastAccessTime. For sessions + carrying large amounts of data, parts of which are infrequently accessed, + this option can increase replication performance. + + The third option is useful if the classes stored in the session have been bytecode + enhanced for use by JBoss PojoCache. If they have been, the session management layer + will detect field level changes within objects stored to the session, and will + replicate those changes. + +Examples: + <replication-granularity>SESSION</replication-granularity> + or + <replication-granularity>ATTRIBUTE</replication-granularity> + or + <replication-granularity>FIELD</replication-granularity> +--> +<!ELEMENT replication-granularity (#PCDATA)> + +<!-- + Determine whether to batch the replication when the granularity level is set to FIELD. + Default is true. + + If this is set to 'true', that means we will replicate the pojo changes only during the + http request is finished. To use this, the JBossCacheAop transaction manager class will + need to be configured as BatchModeTransactionManager such that a user can still have + UserTransaction inside the http request. However, note that the cache will not particiapte + in the UserTransaction in this case. + + If you want cache to participate in the UserTransaction, you can configure the transaction + manager class to JBossTransactionManager and set this option to 'false'. The result is for + those session attribute changes that are not under transaction will replicate instantaneously, + while those particiate under transaction will replicate only when the transaction is + completed. + +Examples: + <replication-field-batch-mode>TRUE</replication-field-batch-mode> + or + <replication-field-batch-mode>FALSE</replication-field-batch-mode> +--> +<!ELEMENT replication-field-batch-mode (#PCDATA)> + +<!-- + Clustering only: Whether the container should assume mod_jk is used for + load balancing for this webapp. If set to 'true', the container will examine + the session id associated with every request and replace the JvmRoute portion of + the session id if it detects a failover. In addition, for each host you will + need to set a unique JvmRoute inside the server.xml file, e.g., + + <Engine name="jboss.web" jvmRoute="Node1" defaultHost="localhost"> + ... + </Engine> + + Default value if not explicitly set is the overall web container default + as set in the deployers/jbossweb.deployer service. By default that is set + to "false". +--> +<!ELEMENT use-jk (#PCDATA)> + +<!-- + Clustering only: Determines the maximum interval between requests, in + seconds, after which a request will trigger replication of the session's + timestamp and other metadata regardless of whether the request has otherwise + made the session dirty. Such replication ensures that other nodes in the + cluster are aware of the most recent value for the session's timestamp + and won't incorrectly expire an unreplicated session upon failover. It also + results in correct values for HttpSession.getLastAccessedTime() calls + following failover. + + The cost of this metadata replication depends on the configured + replication-granularity. With <code>SESSION</code>, the session's + attribute map is replicated along with the metadata, so it can be fairly + costly. With other granularities, the metadata object is replicated + separately from the attributes and only contains a String, and a few longs, + ints and booleans. + + A value of 0 means the metadata will be replicated whenever the session is + accessed. A value of -1 means the metadata will be replicated only if some + other activity during the request (e.g. modifying an attribute) has + resulted in other replication work involving the session. A positive value + greater than the HttpSession.getMaxInactiveInterval() value will be treated + as a likely misconfiguration and converted to 0; i.e. replicate the + metadata on every request. +--> +<!ELEMENT max-unreplicated-interval (#PCDATA)> + +<!-- + Clustering only: Defines when the sessions are replicated to the other nodes. + The typical value, "instant", replicates changes to the other nodes at the end + of requests, using the request processing thread to perform the replication. + In this case, the "snapshot-interval" property is ignored. + With "interval" mode, a background process is created that runs every + "snapshot-interval" milliseconds, checking for modified sessions and replicating + them. + + Default value if not explicitly set is the overall web container default + as set in the deployers/jbossweb.deployer service. By default that is set + to "instant". + + Note that this property has no effect if replication-granularity + is set to FIELD. If it is FIELD, "instant" mode will be used. +--> +<!ELEMENT snapshot-mode (#PCDATA)> + +<!-- + Clustering only: Defines how often (in milliseconds) the background + process that replicates modified sessions should be started for this + web app. Only meaningful if snapshot-mode is set to "interval". + + Default value if not explicitly set is the overall web container default + as set in the deployers/jbossweb.deployer service. By default that is set + to "1000". +--> +<!ELEMENT snapshot-interval (#PCDATA)> + + +<!-- + Clustering only: Fully qualified class name of the implementation of the + org.jboss.web.tomcat.service.session.notification.ClusteredSessionNotificationPolicy + interface that should be used to govern whether servlet specification + notifications should be emitted to any registered HttpSessionListener, + HttpSessionAttributeListener and/or HttpSessionBindingListener. + Event notifications that may make sense in a non-clustered environment + may or may not make sense in a clustered environment; configuring an + appropriate ClusteredSessionNotificationPolicy gives the application + author fine-grained control over what notifications are issued. + + Default value if not explicitly set is the + org.jboss.web.tomcat.service.session.notification.IgnoreUndeployLegacyClusteredSessionNotificationPolicy. +--> +<!ELEMENT session-notification-policy (#PCDATA)> + +<!-- +Runtime information about a web service. + +wsdl-publish-location is optionally used to specify +where the final wsdl and any dependent files should be stored. This location +resides on the file system from which deployment is initiated. + +--> +<!ELEMENT webservice-description ( webservice-description-name, config-name?, config-file?, wsdl-publish-location? )> + +<!-- +Unique name of a webservice within a module +--> +<!ELEMENT webservice-description-name ( #PCDATA )> + +<!-- +file: URL of a directory to which a web-service-description's wsdl should be +published during deployment. Any required files will be published to this +directory, preserving their location relative to the module-specific +wsdl directory(META-INF/wsdl or WEB-INF/wsdl). + +Example : + + For an ejb.jar whose webservices.xml wsdl-file element contains + META-INF/wsdl/a/Foo.wsdl + + <wsdl-publish-location>file:/home/user1/publish + </wsdl-publish-location> + + The final wsdl will be stored in /home/user1/publish/a/Foo.wsdl + +--> +<!ELEMENT wsdl-publish-location ( #PCDATA )> + +<!-- The servlet element specifies servlet specific bindings. Currently this +is only the run-as principal identity. + + Used in: jboss-web +--> +<!ELEMENT servlet (servlet-name, run-as-principal?)> + +<!-- The servlet-name maps from the web.xml servlet/servlet-name to the +jboss-web/servlet/servlet-name. + Used in: servlet +--> +<!ELEMENT servlet-name ( #PCDATA )> + +<!-- + The run-as-principal element specifies whether a specific run-as identity is + to be used. If there is a run-as role defined for a servlet, there can also + be a run-as-principal defined here. If you don't define a run-as principal + the callee will see ctx.getUserPrincipal() == 'anonymous' + + Used in: servlet +--> +<!ELEMENT run-as-principal ( #PCDATA )> Added: trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss_5_0.dtd =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss_5_0.dtd (rev 0) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/jboss_5_0.dtd 2009-01-10 18:43:00 UTC (rev 12974) @@ -0,0 +1,1724 @@ +<?xml version='1.0' encoding='UTF-8' ?> + +<!-- +$Id: jboss_5_0.dtd 81860 2008-11-30 22:12:20Z alex.loubyansky(a)jboss.com $ + +This is the XML DTD for the JBoss 5.0.x EJB deployment descriptor. +The DOCTYPE is: + + <!DOCTYPE jboss PUBLIC + "-//JBoss//DTD JBOSS 5.0//EN" + "http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd"> + +Overview of the architecture of jboss.xml + +<jboss> + + <enforce-ejb-restrictions /> + <security-domain /> + <unauthenticated-principal /> + <webservices> + <context-root> + <webservice-description> + <webservice-description-name> + <wsdl-publish-location> + </webservice-description> + <webservices> + + <enterprise-beans> + + <entity> + <ejb-name /> + <jndi-name /> + <local-jndi-name /> + <call-by-value> + <read-only> + <call-by-value> + <configuration-name> + <security-proxy> + <ejb-ref> + <ejb-local-ref> + <service-ref> + <security-identity> + <run-as-principal> + </security-identity> + <resource-ref> + <res-ref-name /> + <resource-name /> + </resource-ref> + <resource-env-ref> + <clustered /> + <cluster-config> + </entity> + + <session> + <ejb-name /> + <jndi-name /> + <local-jndi-name /> + <call-by-value> + <configuration-name> + <security-proxy> + <ejb-ref> + <ejb-local-ref> + <service-ref> + <security-identity> + <run-as-principal> + </security-identity> + <resource-ref> + <res-ref-name /> + <resource-name /> + </resource-ref> + <resource-env-ref> + <clustered /> + <cluster-config> + <port-component> + <port-component-name> + <port-component-uri> + <auth-method> + <transport-guarantee> + </port-component> + </session> + + <message-driven> + <ejb-name> + <destination-jndi-name> + <mdb-user> + <mdb-passwd> + <mdb-client-id> + <mdb-subscription-id> + <resource-adapter-name> + <configuration-name> + <security-proxy> + <ejb-ref> + <service-ref> + <security-identity> + <run-as-principal> + </security-identity> + <resource-ref> + <resource-env-ref> + </message-driven> + + </enterprise-beans> + + <assembly-descriptor> + <security-role> + <role-name> + <principal-name> + </security-role> + </assembly-descriptor> + + <resource-managers> + + <resource-manager> + <res-name /> + <res-jndi-name /> + </resource-manager> + + <resource-manager> + <res-name /> + <res-url /> + </resource-manager> + + </resource-managers> + + <container-configurations> + + <container-configuration> + <container-name /> + <call-logging /> + <invoker-proxy-binding-name /> + <sync-on-commit-only /> + <insert-after-ejb-post-create /> + <call-ejb-store-on-clean /> + <store-not-flushed /> + <container-interceptors /> + <instance-pool /> + <instance-cache /> + <persistence-manager /> + <web-class-loader /> + <locking-policy /> + <container-cache-conf /> + <container-pool-conf /> + <commit-option /> + <optiond-refresh-rate /> + <security-domain /> + <cluster-config /> + <depends /> + </container-configuration> + + </container-configurations> + +</jboss> +--> + +<!ENTITY % service-ref PUBLIC + "-//JBoss//DTD Web Service Reference 5.0//EN" + "http://www.jboss.org/j2ee/dtd/service-ref_5_0.dtd"> + +%service-ref; + +<!-- + The jboss element is the root element of the jboss.xml file. It + contains all the information used by jboss but not described in the + ejb-jar.xml file. All of it is optional. + + 1- the application assembler can define custom container configurations + for the beans. Standard configurations are provided in standardjboss.xml + 2- the deployer can override the jndi names under which the beans are deployed + 3- the deployer can specify runtime jndi names for resource managers. + +--> +<!ELEMENT jboss (loader-repository?, jmx-name?, enforce-ejb-restrictions?, + security-domain?, missing-method-permissions-excluded-mode?, + unauthenticated-principal?, exception-on-rollback?, + webservices?, enterprise-beans?, assembly-descriptor?, + resource-managers?, invoker-proxy-bindings?, container-configurations?)> + +<!-- The loader-repository specifies the name of the UnifiedLoaderRepository + MBean to use for the ear to provide ear level scoping of classes deployed + in the ear. It is a unique JMX ObjectName string. It may also specify + an arbitrary configuration by including a loader-repository-config element. + +Examples: + <loader-repository>jboss.test:loader=cts-cmp2v1-sar.ear</loader-repository> + + <loader-repository loaderRepositoryClass='dot.com.LoaderRepository'> + dot.com:loader=unique-archive-name + <loader-repository-config configParserClass='dot.com.LoaderParser'> + java2ParentDelegaton=true + </loader-repository-config> + </loader-repository> +--> +<!ELEMENT loader-repository (#PCDATA | loader-repository-config)*> + +<!-- The loaderRepositoryClass attribute gives the classname of the +org.jboss.mx.loading.LoaderRepository implementation. +--> +<!ATTLIST loader-repository loaderRepositoryClass CDATA #IMPLIED> + +<!-- The loader-repository-config element specifies any arbitrary configuration +fragment for use in configuring the loader-repository instance. The actual +content of this element is specific to the loaderRepositoryClass and the +code parsing the element. +--> +<!ELEMENT loader-repository-config (#PCDATA)> + +<!-- The configParserClass attribute gives the classname of the +org.jboss.mx.loading.LoaderRepositoryFactory.LoaderRepositoryConfigParser +implementation to use to parse the loader-repository-config content. +--> +<!ATTLIST loader-repository-config configParserClass CDATA #IMPLIED> + +<!-- The jmx-name element allows one to specify the JMX ObjectName to use +for the MBean associated with the ejb-jar module. This must be a unique +name and valid JMX ObjectName string. + + Used in: jboss +--> +<!ELEMENT jmx-name (#PCDATA)> + +<!-- + The enforce-ejb-restrictions element tells the container to enforce ejb1.1 restrictions + It must be one of the following : + <enforce-ejb-restrictions>true</enforce-ejb-restrictions> + <enforce-ejb-restrictions>false</enforce-ejb-restrictions> + + Used in: jboss +--> +<!ELEMENT enforce-ejb-restrictions (#PCDATA)> + +<!-- + The security-domain element specifies the JNDI name of the security + manager that implements the EJBSecurityManager and RealmMapping for + the domain. When specified at the jboss level it specifies the security + domain for all j2ee components in the deployment unit. + One can override the global security-domain at the container + level using the security-domain element at the container-configuration + level. + + Used in: jboss, container-configuration +--> +<!ELEMENT security-domain (#PCDATA)> + +<!-- The missing-method-permissions-excluded-mode determines the treatment +of missing method-permission mappings in the ejb-jar descriptor. The ejb 2.1 +spec states: "It is possible that some methods are not assigned to any security +roles nor contained in the exclude-list element. In this case, it is the +responsibility of the Deployer to assign method permissions for all of the +unspecified methods, either by assigning them to security roles, or by marking +them as unchecked." The missing-method-permissions-excluded-mode is a boolean +that allows the deployer to globally indicate that all methods without a +method-permission element should be treated as excluded(= true and the default), +or that methods without a method-permission element should be treated as +unchecked(= false) + +<missing-method-permissions-excluded-mode>true</missing-method-permissions-excluded-mode> +<missing-method-permissions-excluded-mode>false</missing-method-permissions-excluded-mode> + +--> +<!ELEMENT missing-method-permissions-excluded-mode (#PCDATA)> + +<!-- + The unauthenticated-principal element specifies the name of the principal + that will be returned by the EJBContext.getCallerPrincipal() method if there + is no authenticated user. This Principal has no roles or privaledges to call + any other beans. +--> +<!ELEMENT unauthenticated-principal (#PCDATA)> + +<!-- The invoker-proxy-bindings defines the invokers available for use with +the ejb container configurations. +--> +<!ELEMENT invoker-proxy-bindings (invoker-proxy-binding*)> + +<!-- The invoker-proxy-binding defines an invoker service and proxy factory +--> +<!ELEMENT invoker-proxy-binding (name, invoker-mbean, proxy-factory, proxy-factory-config)> + +<!-- The name gives a unique name for the invoker-proxy-binding +--> +<!ELEMENT name (#PCDATA)> + +<!-- The invoker-mbean gives the JMX ObjectName of the invoker MBean service +--> +<!ELEMENT invoker-mbean (#PCDATA)> + +<!-- The org.jboss.ejb.EJBProxyFactory implementation class +--> +<!ELEMENT proxy-factory (#PCDATA)> + +<!-- The proxy-factory-config defines the client-interceptors stack +and other configuration options to use for the various EJB proxies. +--> +<!ELEMENT proxy-factory-config (client-interceptors?, endpoint-interceptors? , web-class-loader? , +activation-config?, JMSProviderAdapterJNDI? , ServerSessionPoolFactoryJNDI? , +CreateJBossMQDestination? , MinimumSize? , MaximumSize? , +KeepAliveMillis? , MaxMessages? , MDBConfig? , poa? , register-ejbs-in-jnp-context? , +jnp-context? , interface-repository-supported?)> + +<!-- + The jndi name of the jms provider adapter in the java:/ namespace. + This is mandatory for an MDB and must implement + org.jboss.jms.jndi.JMSProviderAdapter + + Used in: proxy-factory-config for JMSContainerInvoker +--> +<!ELEMENT JMSProviderAdapterJNDI (#PCDATA)> + +<!-- + The jndi name of the session pool in the java:/ namespace. + This is mandatory for an MDB and must implement + org.jboss.jms.asf.ServerSessionPoolFactory + + Used in: proxy-factory-config for JMSContainerInvoker +--> +<!ELEMENT ServerSessionPoolFactoryJNDI (#PCDATA)> + +<!-- + Whether to create destinations in JBossMQ if the + destination cannot be found. + + Used in: proxy-factory-config for JMSContainerInvoker +--> +<!ELEMENT CreateJBossMQDestination (#PCDATA)> + +<!-- + The maximum number of messages parameter for the mdb's + connection consumer. + + Used in: proxy-factory-config for JMSContainerInvoker +--> +<!ELEMENT MaxMessages (#PCDATA)> + +<!-- + Configuration for the MDB + + Used in: proxy-factory-config for JMSContainerInvoker +--> +<!ELEMENT MDBConfig (ReconnectIntervalSec , DeliveryActive? , DLQConfig?)> + +<!-- + The time to wait (in seconds) before trying to recover + the connection to the JMS server. + + Used in: MDBConfig +--> +<!ELEMENT ReconnectIntervalSec (#PCDATA)> + +<!-- + Whether delivery of messages is active at startup, + valid values are "True" or "False". + + Used in: MDBConfig +--> +<!ELEMENT DeliveryActive (#PCDATA)> + +<!-- + Configuration for an MDB's dead letter queue, used + when messages are redelivered too many times. + + Used in: MDBConfig +--> +<!ELEMENT DLQConfig (DestinationQueue , MaxTimesRedelivered , TimeToLive, DLQUser?, DLQPassword?)> + +<!-- + The jndi name of the queue to use as the dead letter queue. + + Used in: DLQConfig +--> +<!ELEMENT DestinationQueue (#PCDATA)> + +<!-- + The maximum number of times a message is redelivered before it + is placed in the dead letter queue. + + Used in: DLQConfig +--> +<!ELEMENT MaxTimesRedelivered (#PCDATA)> + +<!-- + The time-to-live of the message in the dead letter queue. + See javax.jms.Message + + Used in: DLQConfig +--> +<!ELEMENT TimeToLive (#PCDATA)> + +<!-- + The user for the dlq connection + + Used in: DLQConfig +--> +<!ELEMENT DLQUser (#PCDATA)> + +<!-- + The password for the dlq connection + + Used in: DLQConfig +--> +<!ELEMENT DLQPassword (#PCDATA)> + +<!-- + The portable object adapter usage, one of + <poa>per-servent</poa> + <poa>shared</poa> + + Used in: proxy-factory-config for IORFactory +--> +<!ELEMENT poa (#PCDATA)> + +<!-- + Whether to register ejbs in jnp (jndi) + + Used in: proxy-factory-config for IORFactory +--> +<!ELEMENT register-ejbs-in-jnp-context (#PCDATA)> + +<!-- + The jndi context in which to register ejbs + + Used in: proxy-factory-config for IORFactory +--> +<!ELEMENT jnp-context (#PCDATA)> + +<!-- + Whether a deployed ejb has its own CORBA interface repository or not + + Used in: proxy-factory-config for IORFactory +--> +<!ELEMENT interface-repository-supported (#PCDATA)> + +<!-- + The enterprise-beans element contains additional information about + the beans. These informations, such as jndi names, resource managers and + container configurations, are specific to jboss and not described in + ejb-jar.xml. + + jboss will provide a standard behaviour if no enterprise-beans element + is found, see container-configurations, jndi-name and resource-managers + for defaults. + + Used in: jboss +--> +<!ELEMENT webservices (context-root?, webservice-description*)> + +<!-- The context-root element specifies the context root of the web +application that the EJB service endpoints are deployed to. +If it is not specified it will be derived from the deployment short name. +--> +<!ELEMENT context-root (#PCDATA)> + +<!-- +Runtime information about a web service. +wsdl-publish-location is optionally used to specify +where the final wsdl and any dependent files should be stored. This location +resides on the file system from which deployment is initiated. +--> +<!ELEMENT webservice-description ( webservice-description-name, config-name?, config-file?, wsdl-publish-location? )> + +<!-- +Unique name of a webservice within a module. It corresponds to the <webservice-description-name> +element in webservices.xml +--> +<!ELEMENT webservice-description-name ( #PCDATA )> + +<!-- +file: URL of a directory to which a web-service-description's wsdl should be +published during deployment. Any required files will be published to this +directory, preserving their location relative to the module-specific +wsdl directory(META-INF/wsdl or WEB-INF/wsdl). +Example : + For an ejb.jar whose webservices.xml wsdl-file element contains + META-INF/wsdl/a/Foo.wsdl + <wsdl-publish-location>file:/home/user1/publish + </wsdl-publish-location> + The final wsdl will be stored in /home/user1/publish/a/Foo.wsdl +--> +<!ELEMENT wsdl-publish-location ( #PCDATA )> + +<!-- + The enterprise-beans element contains additional information about + the beans. These informations, such as jndi names, resource managers and + container configurations, are specific to jboss and not described in + ejb-jar.xml. + jboss will provide a standard behaviour if no enterprise-beans element + is found, see container-configurations, jndi-name and resource-managers + for defaults. + Used in: jboss +--> +<!ELEMENT enterprise-beans ((session | entity | message-driven)*)> + +<!-- + The entity element holds information specific to jboss and not declared + in ejb-jar.xml about an entity bean, such as jndi name, container + configuration, and resource managers. (see tags for details) + The bean should already be declared in ejb-jar.xml, with the same + ejb-name. + + Used in: enterprise-beans +--> +<!ELEMENT entity (ejb-name , jndi-name? , local-jndi-name? , call-by-value?, read-only?, + exception-on-rollback?, timer-persistence?, configuration-name? , invoker-bindings?, + security-proxy? , ejb-ref* , ejb-local-ref* , service-ref*, + resource-ref* , resource-env-ref*, message-destination-ref* , security-identity?, method-attributes? , + clustered? , cluster-config?, cache-invalidation? , cache-invalidation-config?, + depends*, ior-security-config?)> +<!-- Allow the entity to have a unique id --> +<!ATTLIST entity id ID #IMPLIED> + +<!-- + The session element holds information specific to jboss and not declared + in ejb-jar.xml about a session bean, such as jndi name, container + configuration, and resource managers. (see tags for details) + The bean should already be declared in ejb-jar.xml, with the same + ejb-name. + + Used in: enterprise-beans +--> +<!ELEMENT session (ejb-name , jndi-name? , home-jndi-name?, local-jndi-name?, call-by-value?, + exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?, + security-proxy? , ejb-ref* , ejb-local-ref* , service-ref* , + resource-ref* , resource-env-ref*, message-destination-ref* , security-identity?, clustered? , + cluster-config?, method-attributes?, depends*, + ior-security-config?, port-component?, ejb-timeout-identity?)> +<!-- Allow the session to have a unique id --> +<!ATTLIST session id ID #IMPLIED> + +<!-- + The message-driven element holds information specific to jboss and not declared + in ejb-jar.xml about a message-driven bean, such as container + configuration and resources. + The bean should already be declared in ejb-jar.xml, with the same + ejb-name. + + Used in: enterprise-beans +--> +<!ELEMENT message-driven (ejb-name , activation-config?, destination-jndi-name? , + local-jndi-name?, + mdb-user?, mdb-passwd? , mdb-client-id? , mdb-subscription-id? , resource-adapter-name? , + exception-on-rollback?, timer-persistence?, configuration-name? , invoker-bindings?, + security-proxy? , ejb-ref* , ejb-local-ref*, service-ref*, resource-ref*, + resource-env-ref*, message-destination-ref*, security-identity?, depends*, ior-security-config?, + ejb-timeout-identity?)> +<!-- Allow the message-driven to have a unique id --> +<!ATTLIST message-driven id ID #IMPLIED> + +<!-- + The ejb-name element gives the name of the bean, it must correspond to + an ejb-name element in ejb-jar.xml + + Used in: entity, session, and message-driven +--> +<!ELEMENT ejb-name (#PCDATA)> + +<!-- + The jndi-name element gives the actual jndi name under which + the bean will be deployed when used in the entity, session and + message-driven elements. If it is not provided jboss will assume + "jndi-name" = "ejb-name" + + When used in the ejb-ref, ejb-local-ref, resource-ref, resource-env-ref, + message-destination-ref, message-destination elements this specifies the jndi name to + which the reference should link. + + Used in: entity, session and message-driven + ejb-ref, resource-ref, resource-env-ref +--> +<!ELEMENT jndi-name (#PCDATA)> + +<!ELEMENT home-jndi-name (#PCDATA)> + +<!-- + The JNDI name under with the local home interface should be bound + + Used in: entity and session +--> +<!ELEMENT local-jndi-name (#PCDATA)> + +<!-- + Determine if the bean should use by value call semantics + + Used in: entity and session +--> +<!ELEMENT call-by-value (#PCDATA)> + +<!-- + The read-only element flags an entity bean as read only. + The bean will never be ejbStored. Defaults to false. + It must be one of the following : + <read-only>true</read-only> + <read-only>false</read-only> + + Used in: entity +--> +<!ELEMENT read-only (#PCDATA)> + +<!-- + Whether to throw an exception if the CMT controlled + transaction is no longer active (e.g. marked rollback) + but the application has not itself thrown an exception. + If the bean specifies false, it uses the + jboss/exception-on-rollback config. + Defaults to false. + It must be one of the following : + <exception-on-rollback>true</exception-on-rollback> + <exception-on-rollback>false</exception-on-rollback> + + Used in: jboss, session, entity and message-driven +--> +<!ELEMENT exception-on-rollback (#PCDATA)> + +<!-- + The timer-persistence element determines whether ejb timers should + be persisted across application redeployment. Defaults to true. + + It must be one of the following: + <timer-persistence>true</timer-persistence> + <timer-persistence>false</timer-persistence> + + Used in: session, entity and message-driven +--> +<!ELEMENT timer-persistence (#PCDATA)> + +<!-- + The configuration-name element gives the name of the container + configuration for this bean. It must match one of the container-name + tags in the container-configurations section, or one of the standard + configurations. If no element is provided, jboss will automatically use the + right standard configuration, see container-configurations. + + Note: unlike earlier releases, this element may not be specified as an + empty element to achieve the same effect as not specifying the element. + + Used in: entity, session, and message-driven +--> +<!ELEMENT configuration-name (#PCDATA)> + +<!-- The depends element gives a JMX ObjectName of a service on which the +container or ejb depends. +--> +<!ELEMENT depends (#PCDATA)> + +<!-- The queue/topic jndi name from which we receive messages --> +<!ELEMENT destination-jndi-name (#PCDATA)> + +<!-- The optional user for the jms connection that delivers messages --> +<!ELEMENT mdb-user (#PCDATA)> + +<!-- The optional password for the jms connection that delivers messages --> +<!ELEMENT mdb-passwd (#PCDATA)> + +<!-- The optional client-id for the jms connection that delivers messages --> +<!ELEMENT mdb-client-id (#PCDATA)> + +<!-- The subscription name for topic delivery --> +<!ELEMENT mdb-subscription-id (#PCDATA)> + +<!-- The name of the rar used in JCA 1.5 message inflow +e.g. + <resource-adapter-name>jms-ra.rar</resource-adapter-name> +or for embedded rars + <resource-adapter-name>myapp.ear#myconnector.rar</resource-adapter-name> +--> +<!ELEMENT resource-adapter-name (#PCDATA)> + +<!-- The security-proxy gives the class name of the security proxy implementation. + This may be an instance of org.jboss.security.SecurityProxy, or an + just an object that implements methods in the home or remote interface + of an EJB without implementating any common interface. + + Used in: entity, session, and message-driven +--> +<!ELEMENT security-proxy (#PCDATA)> + +<!-- + The ejb-ref element is used to give the jndi-name of an external + ejb reference. In the case of an external ejb reference, you don't + provide a ejb-link element in ejb-jar.xml, but you provide a jndi-name + in jboss.xml + + Used in: entity, session, and message-driven +--> +<!ELEMENT ejb-ref (ejb-ref-name , jndi-name)> + +<!-- + The ejb-ref-name element is the name of the ejb reference as given in + ejb-jar.xml. + + Used in: ejb-ref +--> +<!ELEMENT ejb-ref-name (#PCDATA)> + +<!-- + The ejb-local-ref element is used to give the jndi-name of an external + ejb reference. This is an alternative to using ejb-link in ejb-jar.xml + + Used in: entity, session, and message-driven +--> +<!ELEMENT ejb-local-ref (ejb-ref-name , local-jndi-name)> + +<!-- + The security-identity element specifies whether a specific run-as identity is to be + used. If there is a run-as role defined for an enterprise bean, there can also be a + run-as-principal define here. If you don't define a run-as principal the callee will + see ctx.getCallerPrincipal() == 'anonymous' + + Used in: entity, message-driven, session +--> +<!ELEMENT security-identity (run-as-principal)> + +<!-- + The ejb-timeout-identity element specifies the run-as used for the ejbTimeout + callback method. If the run-as-principal is specified this is the identity + that will be set as the callback run-as. If the run-as-principal is empty, + then no security context is specified at the container level. Any access of + secured resources will require that the ejbTimeout method establish the + security context. +--> +<!ELEMENT ejb-timeout-identity (run-as-principal)> + +<!-- + The run-as-principal element is the name of the principal that is used + when the enterprise bean calls out with a run-as role. + + Used in: security-identity +--> +<!ELEMENT run-as-principal (#PCDATA)> + +<!-- + The resource-env-ref element gives a mapping between the "code name" + of a env resource (res-ref-name, provided by the Bean Developer) and + its deployed JNDI name. + + Used in: session, entity, message-driven +--> +<!ELEMENT resource-env-ref (resource-env-ref-name , jndi-name)> + +<!-- + The resource-env-ref-name element gives the "code name" of a resource. It is + provided by the Bean Developer. + + Used in: resource-env-ref +--> +<!ELEMENT resource-env-ref-name (#PCDATA)> + +<!-- + The method-attributes element can be used to specify which methods are read only + or idempotent. This is used to reduce the need for locks and replication. +--> +<!ELEMENT method-attributes (method*)> + +<!-- + The method element is used to specify attributes for one method or all those + matching a pattern startingstring*. +--> +<!ELEMENT method (method-name, read-only?, idempotent?, transaction-timeout?)> + +<!-- + The method-name element specifies a complete method name or a pattern consisting of an + initial match followed by '*' +--> +<!ELEMENT method-name (#PCDATA)> + +<!-- + The idempotent element is used in method-attributes to indicate that a method + is completely stateless. Really the same as read-only and should be dropped. +--> +<!ELEMENT idempotent (#PCDATA)> + +<!-- + The transaction timeout in seconds (overriding the default timeout). + This will only work for Required (where the method starts the transaction) and RequiresNew. + The special value of 0 (zero) uses the default timeout configured on jboss:service=TransactionManager + NOTE: any subsequent use of RequiresNew that is not explicitly overridden will use this value. +--> +<!ELEMENT transaction-timeout (#PCDATA)> + +<!-- + The clustered element indicates if this bean will run in a cluster of JBoss instances. + It is provided by the deployer. If not, jboss will assume clustered = False + Possible values: "True", "False" (default) + + Used in: entity and session +--> +<!ELEMENT clustered (#PCDATA)> + +<!-- + The cluster-config element allows to specify cluster specific settings. + WARNING: session-state-manager-jndi-name is only for SFSB. + + Used in: session, entity, container-configuration +--> +<!ELEMENT cluster-config (partition-name? , home-load-balance-policy? , + bean-load-balance-policy? , session-state-manager-jndi-name?)> + +<!-- + The partition-name element indicates the name of the HAPartition to be used + by the container to exchange clustering information. This is a name and *not* + a JNDI name. Given name will be prefixed by "/HAPartition/" by the container to get + the actual JNDI name of the HAPartition. + + Must be set; there is no hard coded default. Can be set either in a bean's own + cluster-config element or in a container-configuration used by the bean. + The standard clustered bean container configurations in conf/standardjboss.xml + set this to the value of system property "jboss.partition.name", or + "DefaultPartition" if that property is not set. + + Used in: entity, session and container-configuration (in clustered-config element) +--> +<!ELEMENT partition-name (#PCDATA)> + +<!-- + The home-load-balance-policy element indicates the java class name to be used + to load balance calls in the home proxy. + + Must be set; there is no hard coded default. Can be set either in a bean's own + cluster-config element or in a container-configuration used by the bean. + The standard clustered bean container configurations in conf/standardjboss.xml + set this to "org.jboss.ha.framework.interfaces.RoundRobin". + + Used in: entity, session and container-configuration (in cluster-config element) +--> +<!ELEMENT home-load-balance-policy (#PCDATA)> + +<!-- + The bean-load-balance-policy element indicates the java class name to be used + to load balance calls in an EJB2 bean proxy. + + Must be set; there is no hard coded default. Can be set either in a bean's own + cluster-config element or in a container-configuration used by the bean. + The standard clustered bean container configurations in conf/standardjboss.xml + set this to "org.jboss.ha.framework.interfaces.RoundRobin" for SLSBs and to + "org.jboss.ha.framework.interfaces.FirstAvailable" for EB and SFSBs. + + Used in: entity, session and container-configuration (in cluster-config element) +--> +<!ELEMENT bean-load-balance-policy (#PCDATA)> + +<!-- + The cache-invalidation element indicates if this bean cache should listen to cache + invalidation events and clear its cache accordingly as well as send cache invalidation + messages. + It is provided by the deployer. If not, jboss will assume cache-invalidation = False + NOTE: This value will *only* be applied if the correct cache plugin and interceptor(s) + are defined in the container configuration. + Possible values: "True", "False" (default) + + Used in: entity (only commit-option A and D will invalidate their cache) +--> +<!ELEMENT cache-invalidation (#PCDATA)> + +<!-- + The cache-invalidation-config element allows to specify cache invalidation specific settings. + + Used in: entity +--> +<!ELEMENT cache-invalidation-config (invalidation-group-name? , invalidation-manager-name?)> + +<!-- + The invalidation-group-name element indicates the name of a group in which all + invalidation messages are exchanged i.e. all beans sharing a given invalidation-group-name + should share the same PK semantic. + By default, invalidation-group-name equals to the EJB name. Thus, when using cache invalidation + accross a cluster, it is not necessary to specify a name as all beans will have the same name + accross the cluster. Nevertheless, if you deploy, on the same node, the same EJB, once with + commit-option C (RW access) and once in commit-option A (RO) and want the RW EJB to invalidate + entries of RO EJB, each one will obviously have its own EJB name. Consequently, you can assign + a common invalidation-group-name to both EJBs so that they share their cache invalidation messages. + + Used in: entity (in cache-invalidation-config element) +--> +<!ELEMENT invalidation-group-name (#PCDATA)> + +<!-- + The invalidation-manager-name references the InvalidationManager MBean to be used. + By Default, the default InvalidationManager is used. + + Used in: entity (in cache-invalidation-config element) +--> +<!ELEMENT invalidation-manager-name (#PCDATA)> + +<!-- + The session-state-manager-jndi-name element indicates the name of the + HASessionState to be used by the container as a backend for EJB2 stateful + session bean management in the cluster. This *is* a JNDI name (unlike the + partition-name element). + + Must be set; there is no hard coded default. Can be set either in a bean's own + cluster-config element or in a container-configuration used by the bean. + The standard clustered bean container configurations in conf/standardjboss.xml + set this to "/HASessionState/" plus the value of system property + "jboss.partition.name", or "DefaultPartition" if that property is not set. + + Used in: session or container-configuration (in cluster-config element) +--> +<!ELEMENT session-state-manager-jndi-name (#PCDATA)> + +<!-- + The resource-ref element gives a mapping between the "code name" + of a resource (res-ref-name, provided by the Bean Developer) and + its "xml name" (resource-name, provided by the Application Assembler). + If no resource-ref is provided, jboss will assume that + "xml-name" = "code name" + + See resource-managers. + + Used in: entity, session, and message-driven +--> +<!ELEMENT resource-ref (res-ref-name , (resource-name | jndi-name | res-url))> + +<!-- + The res-ref-name element gives the "code name" of a resource. It is + provided by the Bean Developer. See resource-managers for the actual + configuration of the resource. + + Used in: resource-ref +--> +<!ELEMENT res-ref-name (#PCDATA)> + +<!-- + The resource-name element gives the "xml name" of the resource. It is + provided by the Application Assembler. See resource-managers for the + actual configuration of the resource. + + Used in: resource-ref +--> +<!ELEMENT resource-name (#PCDATA)> + +<!-- + The resource-managers element is used to declare resource managers. + + A resource has 3 names: + - the "code name" is the name used in the code of the bean, supplied by + the Bean Developer in the resource-ref section of the ejb-jar.xml file + + - the "xml name" is an intermediary name used by the Application Assembler + to identify resources in the XML file. + + - the "runtime jndi name" is the actual jndi-name or url of the deployed + resource, it is supplied by the Deployer. + + The mapping between the "code name" and the "xml name" is given + in the resource-ref section for the bean. If not, jboss will assume that + "xml name" = "code name". + + The mapping between the "xml name" and the "runtime jndi name" is given in + a resource-manager section. If not, and if the datasource is of type + javax.sql.DataSource, jboss will look for a javax.sql.DataSource in the jndi + tree. + + Used in: jboss +--> +<!ELEMENT resource-managers (resource-manager*)> + +<!-- + The resource-manager element is used to provide a mapping between the + "xml name" of a resource (res-name) and its "runtime jndi name" + (res-jndi-name or res-url according to the type of the resource). + If it is not provided, and if the type of the resource is + javax.sql.DataSource, jboss will look for a javax.sql.DataSource in the + jndi tree. + + See resource-managers. + + Used in: resource-managers +--> +<!ELEMENT resource-manager (res-name , (res-jndi-name | res-url))> + +<!-- + The res-name element gives the "xml name" of a resource, it is provided + by the Application Assembler. See resource-managers. + + Used in: resource-manager +--> +<!ELEMENT res-name (#PCDATA)> + +<!-- + The res-jndi-name element is the "deployed jndi name" of a resource, it + is provided by the Deployer. See resource-managers. + + Used in: resource-manager +--> +<!ELEMENT res-jndi-name (#PCDATA)> + +<!-- The res-url element value is a URL string for a resource-ref of +res-type = java.net.URL. Using a res-url creates a binding of the URL +instance under the java:comp/env. If you want to link to another binding +of a URL, you can use the jndi-name to do so. + +// Binds the URL(http://x.y.z) under java:comp/env/jdbc/XYZHome +<resource-ref> + <res-ref-name>jdbc/XYZHome</res-ref-name> + <res-url>http://x.y.z</res-url> +</resource-ref> +// Binds a link to urls/XYZHomePage under java:comp/env/jdbc/XYZHome +<resource-ref> + <res-ref-name>jdbc/XYZHome</res-ref-name> + <res-url>urls/XYZHomePage</res-url> +</resource-ref> + + Used in: resource-ref, resource-manager +--> +<!ELEMENT res-url (#PCDATA)> + +<!-- + The message-destination-ref element is used to configure the + jndi-name for a message-destination-ref in ejb-jar.xml + + Used in: entity, session, and message-driven +--> +<!ELEMENT message-destination-ref (message-destination-ref-name, jndi-name)> + +<!-- + The message-destination-ref-name element identifies the + message-destination-ref. It must match the name in ejb-jar.xml + + Used in: message-destination-ref +--> +<!ELEMENT message-destination-ref-name (#PCDATA)> + +<!-- + The assembly-descriptor element contains application-assembly information. + + The definition of security roles allows you to map assembly roles to one or more + principals. For example, you may define a run-as principal in the security-identity + element and include that principal in one or more security-role(s) in the + assembly descriptor. When called with a run-as role, the callee will see all + those roles in ctx.isCallerInRole(...) + + Used in: jboss +--> +<!ELEMENT assembly-descriptor (security-role*, message-destination*)> + +<!-- + The security-role element contains the definition of a security role. + The definition consists of an the security role name and principal name element(s). + +Used in: assembly-descriptor + +Example: + <security-role> + <role-name>Manager</role-name> + <principal-name>j2ee</principal-name> + <principal-name>javajoe</principal-name> + </security-role> +--> +<!ELEMENT security-role (role-name, principal-name+)> + +<!-- + The role-name element is the name of the role. + + Used in: security-role +--> +<!ELEMENT role-name (#PCDATA)> + +<!-- + The principal-name element is the name of the principal that is mapped + to the assembly role-name. + + Used in: security-role +--> +<!ELEMENT principal-name (#PCDATA)> + +<!-- + The message-destination element is used to configure the + jndi-name for a message-destination in ejb-jar.xml + + Used in: assembly-descriptor +--> +<!ELEMENT message-destination (message-destination-name, jndi-name)> + +<!-- + The message-destination-name element identifies the + message-destination. It must match the name in ejb-jar.xml + + Used in: message-destination +--> +<!ELEMENT message-destination-name (#PCDATA)> + +<!-- + The container-configurations element declares the different possible + container configurations that the beans can use. standardjboss.xml + provides 15 standard configurations with the following container-names: + - Standard CMP 2.x EntityBean + - Standard CMP EntityBean + - Clustered CMP 2.x EntityBean + - Clustered CMP EntityBean + - IIOP CMP 2.x EntityBean + - IIOP CMP EntityBean + - Standard Stateless SessionBean + - Clustered Stateless SessionBean + - IIOP Stateless SessionBean + - Standard Stateful SessionBean + - Clustered Stateful SessionBean + - IIOP Stateful SessionBean + - Standard BMP EntityBean + - Clustered BMP EntityBean + - IIOP BMP EntityBean + - Standard message Driven Bean + + The standard configurations will automatically be used if no custom + configuration is specified. + + The application assembler can define advanced custom configurations here. + + Used in: jboss +--> +<!ELEMENT container-configurations (container-configuration*)> + +<!-- + The container-configuration element describes a configuration for the + container. + The different plugins to use are declared here, as well as their + configurations. The configuration-class attribute is no longer used. + + Used in: container-configurations +--> +<!ELEMENT container-configuration (container-name , call-logging?, + invoker-proxy-binding-name*, sync-on-commit-only?, + insert-after-ejb-post-create?, call-ejb-store-on-clean?, store-not-flushed?, container-interceptors? , + instance-pool? , instance-cache? , persistence-manager? , web-class-loader? , + locking-policy? , container-cache-conf? , container-pool-conf? , + commit-option? , optiond-refresh-rate? , security-domain?, cluster-config?, + depends*)> + +<!-- The extends attribute gives the container-name value of the configuration the container-configuration +is extending. This allows one to specify an extension configuration without having to reiterate all of +the other duplicate configuration info. + + <container-configuration extends="Standard Stateful SessionBean"> + <container-name>Secure Stateless SessionBean</container-name> + <security-domain>java:/jaas/other</security-domain> + </container-configuration> +--> +<!ATTLIST container-configuration extends CDATA #IMPLIED> + +<!-- + The container-name element gives the name of the configuration being + defined. Beans may refer to this name in their configuration-name tag. + + Used in: container-configuration +--> +<!ELEMENT container-name (#PCDATA)> + +<!-- + The call-logging element tells if the container must log every method + invocation for this bean or not. Its value must be true or false. + + Used in: container-configuration +--> +<!ELEMENT call-logging (#PCDATA)> + +<!-- + The invoker-bindings element gives the invokers configuration for an + ejb container. + + Used in: entity, session, message-driven +--> +<!ELEMENT invoker-bindings (invoker+)> + +<!-- + --> +<!ELEMENT invoker (invoker-proxy-binding-name, jndi-name?, ejb-ref*)> + +<!-- The invoker-proxy-binding-name elements maps to the name element of +an invoker-proxy-binding definition. + + Used in: container-configuration, invoker +--> +<!ELEMENT invoker-proxy-binding-name (#PCDATA)> + +<!-- The sync-on-commit-only element determines the behavior of ejbStore +calls on finds, selects and removes. If set to true, ejbStore will only be +called on transaction commit. +--> +<!ELEMENT sync-on-commit-only (#PCDATA)> + +<!-- The insert-after-ejb-post-create element defines when the INSERT + statement will be executed for created entity instance. + Possible values are: + false - the default value, INSERT will be executed after ejbCreate but before + ejbPostCreate; + true - INSERT will be executed after ejbPostCreate. +--> +<!ELEMENT insert-after-ejb-post-create (#PCDATA)> + +<!-- The call-ejb-store-for-clean says whether ejbStore should be called on clean instances + at synchronization time. By the spec it should be true. But users wanted it to be false. + False is the default, meaning ejbStore is called only on dirty instances. +--> +<!ELEMENT call-ejb-store-on-clean (#PCDATA)> + +<!-- The store-not-flushed says whether dirty instances that could not be evicted + from the cache should or should not (to prevent potential data inconsistency) + be stored. The default value is TRUE. +--> +<!ELEMENT store-not-flushed (#PCDATA)> + +<!-- + The container-interceptors element gives the chain of Interceptors + (instances of org.jboss.ejb.Interceptor) that are associated with the container. + The declared order of the interceptor elements corresponds to the order of the + interceptor chain. + + Used in: container-configuration +--> +<!ELEMENT container-interceptors (interceptor+)> + +<!-- +The client-interceptors defines the home and bean client side interceptor chain + + Used in: proxy-factory-config +--> +<!ELEMENT client-interceptors (home , bean, list-entity?)> + +<!-- Define whether the ejb proxy should expose an org.jboss.proxy.IClientContainer + interface to provide access to the invocation context and interceptors. +--> +<!ATTLIST client-interceptors exposeContainer (true | false ) "false"> + +<!-- +The endpoint-interceptors element gives the chain of interceptors +(instances of org.jboss.proxy.Interceptor) that are associated with the +message endpoint. + + Used in: proxy-factory-config for message inflow +--> +<!ELEMENT endpoint-interceptors (interceptor+)> + +<!-- +The home element gives the chain of interceptors +(instances of org.jboss.proxy.Interceptor) that are associated with the home +proxy and operate in the client VM. The declared order of the interceptor +elements corresponds to the order of the interceptor chain. + + Used in: client-interceptors +--> +<!ELEMENT home (interceptor+)> + +<!-- +The bean element gives the chain of interceptors +(instances of org.jboss.proxy.Interceptor) that are associated with the remote +proxy and operate in the client VM. The declared order of the interceptor +elements corresponds to the order of the interceptor chain. + + Used in: client-interceptors +--> +<!ELEMENT bean (interceptor+)> + +<!-- +The list-entity element gives the chain of interceptors +(instances of org.jboss.proxy.Interceptor) that are associated with the remote +proxy and operate in the client VM. The declared order of the interceptor +elements corresponds to the order of the interceptor chain. + + Used in: client-interceptors +--> +<!ELEMENT list-entity (interceptor+)> + +<!-- + The interceptor element specifies an instance of org.jboss.ejb.Interceptor + that is to be added to the container interceptor stack. + + Used in: home, bean, list-entity, endpoint-interceptors +--> +<!ELEMENT interceptor ANY> + +<!-- possible content for the TxInterceptorCMT --> +<!ELEMENT retry-handlers (handler+)> +<!ELEMENT handler (#PCDATA)> + +<!-- + The transaction attribute is used to indicate what type of container its + interceptor applies to. It is an enumerated value that can take on one of: Bean, + Container or Both. A value of Bean indicates that the interceptor should only be + added to a container for bean-managed transaction. + A value of Container indicates that the interceptor should only be added to a + container for container-managed transactions. + A value of Both indicates that the interceptor should be added to all + containers. This is the default value if the transaction attribute is not + explictlygiven. +--> +<!ATTLIST interceptor transaction (Bean | Container | Both ) "Both"> + +<!-- + The metricsEnabled attributes is used to indicate if the interceptor + should only be included when the org.jboss.ejb.ContainerFactory metricsEnabled + flag is set to true. The allowed values are true and false with false being the + default if metricsEnabled is not explicitly given. +--> +<!ATTLIST interceptor metricsEnabled (true | false ) "false"> + +<!-- + The call-by-value attribute is used to indicate that the interceptor + should only be included when the value of the attribute corresponds + to the value of org.jboss.metadata.BeanMetaData callByValue. + For example, if a bean defines the element <call-by-value>true</call-by-value> + then a marshalling invoker interceptor will be used instead of the + non marshalling optimized invoker interceptor. +--> +<!ATTLIST interceptor call-by-value (true | false ) #IMPLIED> + +<!-- + The instance-pool element gives the class name of the instance pool + jboss must use for in this configuration. This class must implement + the org.jboss.ejb.InstancePool interface. The defaults are: + - org.jboss.ejb.plugins.EntityInstancePool for entity beans + - org.jboss.ejb.plugins.StatelessSessionInstancePool for stateless + session beans. + - no pool is used for stateful session beans + + Used in: container-configuration +--> +<!ELEMENT instance-pool (#PCDATA)> + +<!-- + The instance-cache element gives the class name of the instance cache + jboss must use for in this configuration. This class must implement + the org.jboss.ejb.InstanceCache interface. The defaults are: + - org.jboss.ejb.plugins.NoPassivationEntityInstanceCache for entity beans + - org.jboss.ejb.plugins.NoPassivationStatefulSessionInstanceCache for + stateful session beans. + - no cache is used for stateless session beans + + Used in: container-configuration +--> +<!ELEMENT instance-cache (#PCDATA)> + +<!-- + The persistence-manager element gives the class name of the persistence + manager / persistence store jboss must use for in this configuration. + This class must implement: + - org.jboss.ejb.EntityPersistenceStore for CMP Entity Beans (default is + org.jboss.ejb.plugins.jaws.JAWSPersistenceManager) + - org.jboss.ejb.EntityPersistenceManager for BMP entity beans (default + is org.jboss.ejb.plugins.BMPPersistenceManager) + - org.jboss.ejb.StatefulSessionPersistenceManager for stateless session + beans. + - no persistence-manager is used for stateless session beans + + Used in: container-configuration +--> +<!ELEMENT persistence-manager (#PCDATA)> + +<!-- + The locking-policy element gives the class name of the EJB lock + implementation JBoss must use for in this configuration. This class must + implement the org.jboss.ejb.BeanLock interface. The default is + org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock. + + Used in: container-configuration +--> +<!ELEMENT locking-policy (#PCDATA)> + +<!-- + The web-class-loader element gives the class name of the web classloader + jboss must use for in this configuration. This class must be a subclass + of org.jboss.web.WebClassLoader. The default is org.jboss.web.WebClassLoader. + + Used in: container-configuration + Used in: proxy-factory-config +--> +<!ELEMENT web-class-loader (#PCDATA)> + +<!-- + The container-cache-conf element holds dynamic configuration data + for the instance cache. + jboss does not read directly the subtree for this element: instead, + it is passed to the instance cache instance (if it implements + org.jboss.metadata.XmlLoadable) for it to load its parameters. + + Used in: container-configuration +--> +<!ELEMENT container-cache-conf (cache-policy? , cache-policy-conf?, cache-policy-conf-other?)> + +<!-- + The implementation class for the cache policy, which controls + when instances will be passivated, etc. + + Used in: container-cache-conf +--> +<!ELEMENT cache-policy (#PCDATA)> + +<!-- + The configuration settings for the selected cache policy. This + is currently only valid for the LRU cache. + When the cache is the LRU one for the stateful container, the elements + remover-period and max-bean-life specifies the period of the remover + task that removes stateful beans (that normally have been passivated) + that have age greater than the specified max-bean-life element. + + Used in: container-cache-conf (when cache-policy is the LRU cache) +--> +<!ELEMENT cache-policy-conf (min-capacity? , max-capacity? , remover-period? , + max-bean-life? , overager-period? , max-bean-age? , resizer-period? , + max-cache-miss-period? , min-cache-miss-period? , cache-load-factor?, flush-enabled?)> + +<!-- + The minimum capacity of this cache +--> +<!ELEMENT min-capacity (#PCDATA)> + +<!-- + The maximum capacity of this cache +--> +<!ELEMENT max-capacity (#PCDATA)> + +<!-- + The period of the overager's runs +--> +<!ELEMENT overager-period (#PCDATA)> + +<!-- + The period of the remover's runs +--> +<!ELEMENT remover-period (#PCDATA)> + +<!-- + The max-bean-life specifies the period of the remover + task that removes stateful beans (that normally have been passivated) + that have age greater than the specified max-bean-life element. +--> +<!ELEMENT max-bean-life (#PCDATA)> + +<!-- + The period of the resizer's runs +--> +<!ELEMENT resizer-period (#PCDATA)> + +<!-- + The age after which a bean is automatically passivated +--> +<!ELEMENT max-bean-age (#PCDATA)> + +<!-- + Shrink cache capacity if there is a cache miss every or more + this member's value +--> +<!ELEMENT max-cache-miss-period (#PCDATA)> + +<!-- + Enlarge cache capacity if there is a cache miss every or less + this member's value +--> +<!ELEMENT min-cache-miss-period (#PCDATA)> + +<!-- + The resizer will always try to keep the cache capacity so that + the cache is this member's value loaded of cached objects +--> +<!ELEMENT cache-load-factor (#PCDATA)> + +<!-- + For the NoPassivationCachePolicy. Can be true or false +--> +<!ELEMENT flush-enabled (#PCDATA)> + +<!-- + Arbitrary XML configuration +--> +<!ELEMENT cache-policy-conf-other ANY> + +<!-- + Possible content for the cache-policy-conf-other +--> +<!ELEMENT partitions (#PCDATA)> +<!ELEMENT batch-commit-strategy (#PCDATA)> +<!ELEMENT invalidable EMPTY> + +<!-- + The container-pool-conf element holds configuration data for the + instance pool. + jboss does not read directly the subtree for this element: instead, + it is passed to the instance pool instance (if it implements + org.jboss.metadata.XmlLoadable) for it to load its parameters. + + The default instance pools, EntityInstancePool and + StatelessSessionInstancePool, both accept the following configuration. + + Used in: container-configuration +--> +<!ELEMENT container-pool-conf ((MinimumSize?, MaximumSize?, + strictMaximumSize?, strictTimeout?) | Synchronized)> + +<!-- The theoretical minimum size of the pool. Currently unused by JBoss +EJB pools. + +Used in: invoker-proxy-conf for JMSContainerInvoker +--> +<!ELEMENT MinimumSize (#PCDATA)> + +<!-- + The capacity of the Pool. For pools where reclaim is possible, the pool will + also be repopulated when the instance is free to be reused. + This is not an hard limit, if instances are needed when the pool is at + its MaximumSize, new instances will be created following the demand unless + a strictMaximumSize of true is specified. + + Used in: container-pool-conf and invoker-proxy-conf for JMSContainerInvoker +--> +<!ELEMENT MaximumSize (#PCDATA)> + +<!-- A boolean flag indicating if attempts to access the pool will block when +MaximumSize instances are active. The default is false. + + Used in: container-pool-conf +--> +<!ELEMENT strictMaximumSize (#PCDATA)> + +<!-- The time in milliseconds to wait for the strictMaximumSize semaphore. The +default is Long.MAX_VALUE or essentially enternity. + + Used in: container-pool-conf +--> +<!ELEMENT strictTimeout (#PCDATA)> + +<!-- + Can be true or false. + Used in SingletonStatelessSessionInstancePool to synchronize access to the SLSB instance. + + Used in: container-pool-conf +--> +<!ELEMENT Synchronized (#PCDATA)> + +<!-- + The number of millis to keep an unused object in the pool. Currently unused by + JBoss EJB Pools. + + Used in: invoker-proxy-conf for JMSContainerInvoker +--> +<!ELEMENT KeepAliveMillis (#PCDATA)> + +<!-- + This option is only used for entity container configurations. + + The commit-option element tells the container which option to use for transactions. + Its value must be A, B C, or D. + + - option A: the entiry instance has exclusive access to the database. The instance + stays ready after a transaction. + - option B: the entity instance does not have exclusive access to the database. + The state is loaded before the next transaction. + - option C: same as B, except the container does not keep the instance after commit: + a passivate is immediately performed after the commit. + + - option D: a lazy update. default is every 30 secs. + can be updated with <optiond-refresh-rate> + + See ejb1.1 specification for details (p118). + + Used in: container-configuration +--> +<!ELEMENT commit-option (#PCDATA)> + +<!-- + This element is used to specify the refresh rate of commit option d +--> +<!ELEMENT optiond-refresh-rate (#PCDATA)> + +<!-- +ior-security-config element describes the security configuration information for the IOR. +--> +<!ELEMENT ior-security-config ( transport-config? , as-context?, sas-context? )> + +<!-- +transport-config is the root element for security between the end points +--> +<!ELEMENT transport-config ( integrity, confidentiality, + establish-trust-in-target, establish-trust-in-client, detect-misordering?, + detect-replay?)> + +<!-- +integrity element indicates if the server (target) supports integrity protected messages. +The valid values are NONE, SUPPORTED or REQUIRED +--> +<!ELEMENT integrity ( #PCDATA)> + +<!-- +confidentiality element indicates if the server (target) supports privacy protected +messages. The values are NONE, SUPPORTED or REQUIRED +--> +<!ELEMENT confidentiality ( #PCDATA)> + +<!-- +establish-trust-in-target element indicates if the target is capable of authenticating to a client. +The values are NONE or SUPPORTED. +--> +<!ELEMENT establish-trust-in-target ( #PCDATA)> + +<!-- +establish-trust-in-client element indicates if the target is capable of authenticating a client. The +values are NONE, SUPPORTED or REQUIRED. +--> +<!ELEMENT establish-trust-in-client ( #PCDATA)> + +<!-- +The optional detect-misordering indicates if the server (target) supports +detection of message sequence errors. The values are NONE, SUPPORTED or REQUIRED. +--> +<!ELEMENT detect-misordering ( #PCDATA)> + +<!-- +The optional detect-replay indicates if the server (target) supports detection +of message replay attempts. The values are NONE, SUPPORTED or REQUIRED. +--> +<!ELEMENT detect-replay ( #PCDATA)> + +<!-- +as-context (CSIv2 authentication service) is the element describing the authentication +mechanism that will be used to authenticate the client. If specified it will be the +username-password mechanism. +--> +<!ELEMENT as-context ( auth-method, realm, required )> + +<!-- +required element specifies if the authentication method specified is required +to be used for client authentication. If so the EstablishTrustInClient bit +will be set in the target_requires field of the AS_Context. The element value +is either true or false. +--> +<!ELEMENT required ( #PCDATA )> + +<!-- +auth-method element describes the authentication method. The only supported value +for as-context is USERNAME_PASSWORD + +For port-component, the auth-method element is used to configure the +authentication mechanism for the web service. As a prerequisite to gaining +access to any web service which are protected by an authorization +constraint, a user must have authenticated using the configured +mechanism. Legal values for this element are "BASIC", or "CLIENT-CERT". + +Used in: as-context, port-component + +--> +<!ELEMENT auth-method ( #PCDATA )> + +<!-- +realm element describes the realm in which the user is authenticated. Must be +a valid realm that is registered in server configuration. +--> +<!ELEMENT realm ( #PCDATA )> + +<!-- +sas-context (related to CSIv2 security attribute service) element describes +the sas-context fields. +--> +<!ELEMENT sas-context ( caller-propagation )> + +<!-- +caller-propagation element indicates if the target will accept propagated caller identities +The values are NONE or SUPPORTED. +--> +<!ELEMENT caller-propagation ( #PCDATA) > + +<!-- The port-component element specifies a mapping from a webservice +port-component whose service-impl-bean/ejb-link value maps to an ejb. + +Used in: session +--> +<!ELEMENT port-component (port-component-name, port-component-uri?, auth-method?, + transport-guarantee?) > + +<!-- Maps to the port-component-name in the webservices.xml descriptor. + +Used in: port-component +--> +<!ELEMENT port-component-name (#PCDATA) > + +<!-- Relative path that is appended to the <context-root> element to form fully qualified +endpoint address for a web service endpoint. + +For backwards compatibility, it may also be the absolute path starting with web context root +to form fully qualified endpoint address for a web service endpoint. In this case, the port component uri +must contain at least two token seperated by '/'. The first token is the web context root, +which must be identical among all port component uris in a given deployment. + +Used in: port-component +--> +<!ELEMENT port-component-uri (#PCDATA) > + +<!-- +The transport-guarantee element specifies that the communication +between client and server should be NONE, INTEGRAL, or +CONFIDENTIAL. NONE means that the application does not require any +transport guarantees. A value of INTEGRAL means that the application +requires that the data sent between the client and server be sent in +such a way that it can't be changed in transit. CONFIDENTIAL means +that the application requires that the data be transmitted in a +fashion that prevents other entities from observing the contents of +the transmission. In most cases, the presence of the INTEGRAL or +CONFIDENTIAL flag will indicate that the use of SSL is required. + +Used in: port-component +--> +<!ELEMENT transport-guarantee (#PCDATA)> + +<!-- +Activation config + +used in message-driven and proxy-factory-config +--> +<!ELEMENT activation-config ( activation-config-property* )> + +<!-- +Activation config properties + +used in activation-config +--> +<!ELEMENT activation-config-property ( activation-config-property-name, + activation-config-property-value )> +<!-- +Activation config property name + +used in activation-config-property +--> +<!ELEMENT activation-config-property-name ( #PCDATA )> + +<!-- +Activation config property value + +used in activation-config-property +--> +<!ELEMENT activation-config-property-value ( #PCDATA )> + Added: trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/service-ref_5_0.dtd =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/service-ref_5_0.dtd (rev 0) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.core/dtd/service-ref_5_0.dtd 2009-01-10 18:43:00 UTC (rev 12974) @@ -0,0 +1,159 @@ +<?xml version='1.0' encoding='UTF-8'?> + +<!-- + $Id: jboss-client_5_0.dtd 58121 2006-11-04 19:57:58Z thomas.diesler(a)jboss.com $ + + <!DOCTYPE jboss-web PUBLIC + "-//JBoss//DTD Web Service Reference 5.0//EN" + "http://www.jboss.org/j2ee/dtd/service-ref_5_0.dtd"> +--> + +<!-- + WebServiceRef customization +--> + +<!-- + Runtime settings for a web service reference. In the simplest case, + there is no runtime information required for a service ref. Runtime info + is only needed in the following cases : + + * to define the port that should be used to resolve a container-managed port + * to define default Stub property settings for Stub objects + * to define the URL of a final WSDL document to be used + + Example: + + <service-ref> + <service-ref-name>OrganizationService</service-ref-name> + <wsdl-override>file:/wsdlRepository/organization-service.wsdl</wsdl-override> + </service-ref> + + <service-ref> + <service-ref-name>OrganizationService</service-ref-name> + <config-name>Secure Client Config</config-name> + <config-file>META-INF/jbossws-client-config.xml</config-file> + <handler-chain>META-INF/jbossws-client-handlers.xml</handler-chain> + </service-ref> + + <service-ref> + <service-ref-name>SecureService</service-ref-name> + <service-impl-class>org.jboss.tests.ws.jaxws.webserviceref.SecureEndpointService</service-impl-class> + <service-qname>{http://org.jboss.ws/wsref}SecureEndpointService</service-qname> + <port-component-ref> + <service-endpoint-interface>org.jboss.tests.ws.jaxws.webserviceref.SecureEndpoint</service-endpoint-interface> + <port-qname>{http://org.jboss.ws/wsref}SecureEndpointPort</port-qname> + <stub-property> + <name>javax.xml.ws.security.auth.username</name> + <value>kermit</value> + </stub-property> + <stub-property> + <name>javax.xml.ws.security.auth.password</name> + <value>thefrog</value> + </stub-property> + </port-component-ref> + </service-ref> +--> +<!ELEMENT service-ref (service-ref-name, service-impl-class?, service-qname?, config-name?, config-file?, handler-chain?, port-component-ref*, wsdl-override?)> + +<!-- + The service-ref-name element gives the ENC relative name. + Overrides @WebServiceRef.name +--> +<!ELEMENT service-ref-name (#PCDATA)> + +<!-- + Name of the JAXWS service implementation class. + Overrides @WebServiceRef.value +--> +<!ELEMENT service-impl-class (#PCDATA)> + +<!-- + The service-qname element declares the specific WSDL service element. + Specify the qualified service name in the form defined by QName.valueOf() + + Example: + <service-qname>{http://somensURI}SomeService</service-qname> +--> +<!ELEMENT service-qname (#PCDATA)> + +<!-- + The optional handler-chain element is a URL or resource name to a handler chain configuration. + See: @HandlerChain.file +--> +<!ELEMENT handler-chain (#PCDATA)> + +<!-- + Information for a port within a service-ref. + + Either service-endpoint-interface or wsdl-port or both + (service-endpoint-interface and wsdl-port) should be specified. + + If both are specified, wsdl-port represents the + port the container should choose for container-managed port selection. + + The same wsdl-port value must not appear in + more than one port-component-ref entry within the same service-ref. + + If a particular service-endpoint-interface is using container-managed port + selection, it must not appear in more than one port-component-ref entry + within the same service-ref. +--> +<!ELEMENT port-component-ref (service-endpoint-interface?, port-qname?, config-name?, config-file?, stub-property*)> + +<!-- + Fully qualified name of service endpoint interface +--> +<!ELEMENT service-endpoint-interface (#PCDATA)> + +<!-- + Port used in port-component-ref. + Specify the qualified port name in the form defined by QName.valueOf() + + Example: + <port-qname>{http://somensURI}SomeService</port-qname> +--> +<!ELEMENT port-qname (#PCDATA)> + +<!-- + The optional config-name element gives the client configuration name that must be present in + the configuration given by element config-file. Ports that match this port info will be + configured with this config name. + + The default is: Standard Client +--> +<!ELEMENT config-name (#PCDATA)> + +<!-- + The optional config-file element is a URL or resource name for the client configuration. + Ports that match this port info will be configured with this config file. + + The default is: META-INF/standard-jbossws-client-config.xml +--> +<!ELEMENT config-file (#PCDATA)> + +<!-- + Property values that should be set on a stub before it's returned to + to the web service client. The property names can be any properties supported + by the StubExt or Stub implementation. + + See javadoc for org.jboss.ws.core.StubExt, javax.xml.rpc.Stub +--> +<!ELEMENT stub-property (prop-name, prop-value)> + +<!-- + This text nodes holds a name string. +--> +<!ELEMENT prop-name (#PCDATA)> + +<!-- + This text nodes holds a value string. +--> +<!ELEMENT prop-value (#PCDATA)> + +<!-- + The wsdl-override element the actual wsdl docuement the web service client + uses to connect to the remote service. + + Overrides @WebServiceRef.wsdlLocation +--> +<!ELEMENT wsdl-override (#PCDATA)> Modified: trunk/as/plugins/org.jboss.ide.eclipse.as.core/plugin.xml =================================================================== --- trunk/as/plugins/org.jboss.ide.eclipse.as.core/plugin.xml 2009-01-10 18:10:44 UTC (rev 12973) +++ trunk/as/plugins/org.jboss.ide.eclipse.as.core/plugin.xml 2009-01-10 18:43:00 UTC (rev 12974) @@ -550,6 +550,38 @@ uri="dtd/service-ref_4_2.dtd" webURL="http://www.jboss.org/j2ee/dtd/service-ref_4_2.dtd"> </public> + + <public + publicId="-//JBoss//DTD Java EE Application 5.0//EN" + uri="dtd/jboss-app_5_0.dtd" + webURL="http://www.jboss.org/j2ee/dtd/jboss-app_5_0.dtd"> + </public> + <public + publicId="-//JBoss//DTD JBOSS 5.0//EN" + uri="dtd/jboss_5_0.dtd" + webURL="http://www.jboss.org/j2ee/dtd/jboss_5_0.dtd"> + </public> + <public + publicId="-//JBoss//DTD Web Application 5.0//EN" + uri="dtd/jboss-web_5_0.dtd" + webURL="http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd"> + </public> + <public + publicId="-//JBoss//DTD JBOSS JCA Config 5.0//EN" + uri="dtd/jboss-ds_5_0.dtd" + webURL="http://www.jboss.org/j2ee/dtd/jboss-ds_5_0.dtd"> + </public> + <public + publicId="-//JBoss//DTD MBean Service 5.0//EN" + uri="dtd/jboss-service_5_0.dtd" + webURL="http://www.jboss.org/j2ee/dtd/jboss-service_5_0.dtd"> + </public> + <public + publicId="-//JBoss//DTD Web Service Reference 5.0//EN" + uri="dtd/service-ref_5_0.dtd" + webURL="http://www.jboss.org/j2ee/dtd/service-ref_5_0.dtd"> + </public> + </catalogContribution> </extension>