[jboss-svn-commits] JBL Code SVN: r12361 - in labs/jbosslabs/trunk/stats-server: binaries and 120 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Wed Jun 6 12:55:53 EDT 2007
Author: wrzep
Date: 2007-06-06 12:55:52 -0400 (Wed, 06 Jun 2007)
New Revision: 12361
Added:
labs/jbosslabs/trunk/stats-server/binaries/
labs/jbosslabs/trunk/stats-server/binaries/as/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/JBossORG-EULA.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/classpath.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_hpux.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_redhat.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_suse.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/probe.bat
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/probe.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.bat
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.conf
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.bat
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.bat
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsconsume.bat
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsconsume.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsprovide.bat
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsprovide.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsrunclient.bat
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsrunclient.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wstools.bat
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wstools.sh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/activation.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/antlr.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/auth.conf
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/avalon-framework.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/commons-codec.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/commons-httpclient.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/commons-logging.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/concurrent.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/ejb3-persistence.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/getopt.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/hibernate-annotations.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/hibernate-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jacorb.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/javassist.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jaxb-api.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jaxb-impl.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jaxb-xjc.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-annotations-ejb3.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-aop-jdk50-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-aspect-jdk50-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-common-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-deployment.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-ejb3-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-ejb3x.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-iiop-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-j2ee.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-jaxrpc.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-jaxws.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-jsr77-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-remoting.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-saaj.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-serialization.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-srp-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-system-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-transaction-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-xml-binding.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossall-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbosscx-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossha-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossjmx-ant.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossmq-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbosssx-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossws-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossws-wsconsume-impl.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jmx-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jmx-invoker-adaptor-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jnp-client.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/log4j.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/logkit.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/mail.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/scout.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/servlet-api.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/stax-api.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/trove.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/wsdl4j.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/wstx.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/xmlsec.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/copyright.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/README-DTD.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/XMLSchema.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application-client_1_3.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application_1_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application_1_3.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/connector_1_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/datatypes.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/ejb-jar.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/ejb-jar_2_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws_2_4.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws_3_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_3_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_3_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_4_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_4_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_3_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_4_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_4_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-ds_1_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-ds_1_5.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_3_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_4_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_4_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-subscription.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_3_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_3_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_4_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_4_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_2_4.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_3_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_3_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_4_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_4_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_1.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_3_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_3_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_4_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_4_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/security_config.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/service-ref_4_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/service-ref_4_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-app_2_2.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-app_2_3.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-facesconfig_1_0.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-facesconfig_1_1.dtd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/binding-manager/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/binding-manager/sample-bindings.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/asapxcess-jb3.2-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/cicsr9s-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-400-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-jcc-xa-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-xa-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/derby-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/facets-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/fastobjects-jboss32-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/firebird-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/generic-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hajndi-jms-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hsqldb-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hsqldb-encrypted-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/informix-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/informix-xa-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jdatastore-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jms-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jsql-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/lido-versant-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mimer-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mimer-xa-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/msaccess-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mssql-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mssql-xa-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mysql-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/oracle-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/oracle-xa-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/pointbase-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/pointbase-xa-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/postgres-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/progress-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sapdb-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sapr3-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/solid-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sybase-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/as400-jdbc2-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/conf/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/conf/jbossmq-state.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/db2-jdbc2-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/derby-jdbc2-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/file-state-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/mssql-jdbc2-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/mysql-jdbc2-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/null-persistence-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/oil-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/oracle-jdbc2-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/postgres-jdbc2-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/rmi-il-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/ssl-uil2-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/build.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/cluster-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/jboss-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/sybase-jdbc2-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/uil-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/ejb-management.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/deploy/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/deploy/default-ds-monitor-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/deploy/jvm-monitor-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/lib/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/lib/logging-monitor.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/readme.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/META-INF/MANIFEST.MF
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/META-INF/jboss-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/org/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/org/jboss/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/org/jboss/jmx/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/org/jboss/jmx/examples/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/org/jboss/jmx/examples/persistence/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/org/jboss/jmx/examples/persistence/PersistentServiceExample.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/org/jboss/jmx/examples/persistence/PersistentServiceExampleMBean.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/netboot/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/netboot/netboot.war
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/build.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/deployment-service.sar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/readme.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/schema/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/schema/jboss-template-config.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/VM_global_library.vm
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/jms-queue/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/jms-queue/template-config.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/jms-queue/vm/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/jms-queue/vm/jms-queue.xml.vm
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/local-tx-datasource/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/local-tx-datasource/template-config.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/local-tx-datasource/vm/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/local-tx-datasource/vm/local-tx-datasource.vm
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/no-tx-datasource/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/no-tx-datasource/template-config.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/no-tx-datasource/vm/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/no-tx-datasource/vm/no-tx-datasource.vm
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/xa-datasource/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/xa-datasource/template-config.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/xa-datasource/vm/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/xa-datasource/vm/xa-datasource.vm
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/derby-plugin.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/entity-resolver-manager/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/entity-resolver-manager/xmlresolver-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/jboss-bindings.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/antlr.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/apache-1.1.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/apache-2.0.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/bsd.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/cddl.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/cpl-1.0.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/dom4j.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/hsqldb.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/ironsmith.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/jaxen.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/juddi.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/lgpl.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/license-info.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/oswego.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/thirdparty-licenses.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/xdoclet.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/README-SCHEMA.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application-client_1_4.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application-client_5.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application_1_4.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application_5.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/bean-deployer_1_0.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/connector_1_5.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/ejb-jar_2_1.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/ejb-jar_3_0.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_1_4.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_jaxrpc_mapping_1_1.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_web_services_1_1.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_web_services_client_1_1.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/java-properties_1_0.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_5.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_web_services_1_2.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_web_services_client_1_2.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jbxb_1_0.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jndi-binding-service_1_0.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jsp_2_0.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jsp_2_1.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/orm_1_0.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/persistence_1_0.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/security-config_4_0.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/security-config_4_1.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/user-roles_1_0.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-app_2_4.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-app_2_5.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-facesconfig_1_2.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-jsptaglibrary_2_0.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/xml.xsd
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/tests/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/tests/TESTS-TestSuites.txt
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/jar-versions.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lgpl.html
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/commons-codec.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/commons-httpclient.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/commons-logging.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/concurrent.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/endorsed/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/endorsed/serializer.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/endorsed/xalan.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/endorsed/xercesImpl.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/getopt.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-common.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-jmx.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-system.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-xml-binding.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/log4j-boot.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/readme.html
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/readme_j2ee.html
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-log4j.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-minimal.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jbossjta-properties.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jndi.properties
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/login-config.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jbossws-roles.properties
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jbossws-users.properties
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jmx-console-roles.properties
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jmx-console-users.properties
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/standardjboss.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/standardjbosscmp-jdbc.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/AttributePersistenceService-xmbean.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/ClientUserTransaction-xmbean.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/JNDIView-xmbean.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/Log4jService-xmbean.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/NamingBean-xmbean.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/NamingService-xmbean.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/TransactionManagerService-xmbean.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.JARDeployer-xmbean.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.MainDeployer-xmbean.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.SARDeployer-xmbean.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/bsh-deployer.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/cache-invalidation-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/client-deployer-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/ear-deployer.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/ejb-deployer.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/hsqldb-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/META-INF/jboss-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/InvokerServlet$GetCredentialAction.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/InvokerServlet$GetPrincipalAction.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/InvokerServlet.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/NamingFactoryServlet.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/ReadOnlyAccessFilter.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/jboss-web.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/web.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/META-INF/jboss-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/base-aop.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aspect-library-jdk50.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/trove.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/META-INF/jboss-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-bean-deployer.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-container.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-dependency.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-microcontainer.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-ha-local-jdbc.rar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-ha-xa-jdbc.rar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-local-jdbc.rar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/META-INF/jboss-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/META-INF/webserver-xmbean.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/WEB-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/WEB-INF/web.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/favicon.ico
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/index.html
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/jboss.css
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/logo.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/manager/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/manager/xform.xsl
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/conf/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/conf/web.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/context.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jasper-jdt.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jbossweb-extras.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jbossweb-service.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jbossweb.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jsf-libs/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jsf-libs/jboss-faces.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jsf-libs/jsf-api.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jsf-libs/jsf-impl.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jstl.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/server.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-xa-jdbc.rar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossjca-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/MANIFEST.MF
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/jboss-service-no-ejb3.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/jboss-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxrpc-client-config.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxrpc-endpoint-config.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-client-config.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-endpoint-config.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jaxb-api.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jaxb-impl.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jboss-jaxws.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws-context.war
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws-core.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws-jboss42-integration.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws.beans/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/policy.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/stax-api.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/wsdl4j.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/xmlsec.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/hsqldb-jdbc-state-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/hsqldb-jdbc2-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-destinations-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/META-INF/MANIFEST.MF
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/META-INF/jboss-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/META-INF/MANIFEST.MF
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/classes/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/classes/org/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/classes/org/jboss/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/classes/org/jboss/mq/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/classes/org/jboss/mq/il/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/classes/org/jboss/mq/il/http/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/classes/org/jboss/mq/il/http/servlet/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/classes/org/jboss/mq/il/http/servlet/HTTPServerILServlet.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/jboss-web.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/web.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jms-ds.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jms-ra.rar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jvm-il-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/uil2-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/META-INF/MANIFEST.MF
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/AddressPort.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/AttrResultInfo.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/OpResultInfo.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/Server.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/html/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/html/ClusteredConsoleServlet.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/html/HtmlAdaptorServlet.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/html/JMXOpsAccessControlFilter.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/model/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/model/DomainData.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/model/MBeanData.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/jboss-web.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/web.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/checkJNDI.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/bootstrap.html
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/clusterView.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/index.html
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/displayMBeans.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/displayOpResult.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/images/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/images/logo.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/index.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/inspectMBean.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/jboss.css
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/style_master.css
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-invoker-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jsr88-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/mail-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/META-INF/MANIFEST.MF
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/META-INF/jboss-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/console-mgr-classes.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/jcommon.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/jfreechart.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPBinding.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPClassMetaData.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorChain.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorConstructorCallerChain.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorMetaData.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorMethodCallerChain.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPDefaultMetaData.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPFieldChain.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPFieldMetaData.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPIntroductionPointcut.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMetaData.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodChain.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodConstructorCallerChain.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodMetaData.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodMethodCallerChain.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EJB.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EJBModule.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EntityEjb.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/J2EEApp.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/JNDIView.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/META-INF/MANIFEST.MF
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/MdbEjb.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Queue.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/ServerInfo.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Servlet.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/StatefulEjb.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/StatelessEjb.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/SysProperties.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Topic.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/TopicNavigation.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/TopicSubscriptions.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/Classloaders.bsh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/J2EEFolder.bsh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/JNDIView.bsh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/SystemFolder.bsh
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-roles.properties
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-users.properties
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/jboss-web.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/tlds/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/tlds/webconsole.tld
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/web.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WebModule.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/applet.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/applet.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createSnapshot.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createStringThresholdMonitor.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createStringThresholdMonitorSummary.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createThresholdMonitor.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createThresholdMonitorSummary.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/css/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/css/dtree.css
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/css/jboss.css
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/dtree.js
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/EspressoMaker.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/bean.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/beans.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/card.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/container.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/database.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/elements32.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/flash.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/jboss.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/jndiview.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/logo.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/otherimages.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/recycle.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/rubiks.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/server.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/service.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/serviceset.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/servinghand.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/settings32.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/smallnet.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/spirale.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/spirale32.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/starfolder.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/base.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/cd.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/empty.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/folder.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/folderopen.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/globe.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/imgfolder.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/join.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/joinbottom.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/line.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/minus.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/minusbottom.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/musicfolder.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/nolines_minus.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/nolines_plus.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/page.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/plus.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/plusbottom.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/question.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/trash.gif
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/index.html
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/listActiveAlarmTable.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/listMonitors.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageSnapshot.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageStringThresholdMonitor.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageThresholdMonitor.jsp
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/xform.xsl
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/monitoring-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/properties-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/quartz-ra.rar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/schedule-manager-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/scheduler-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/sqlexception-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/META-INF/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/META-INF/jboss-service.xml
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/hilo/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/hilo/HiLoKeyGenerator.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/hilo/HiLoKeyGeneratorFactory.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/hilo/HiLoKeyGeneratorFactoryMBean.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGenerator.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGeneratorFactory.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGeneratorFactoryService.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGeneratorFactoryServiceMBean.class
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/activation.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/antlr.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/autonumber-plugin.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bcel.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bindingservice-plugin.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bsf.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bsh-deployer.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bsh.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/cglib.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-codec.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-collections.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-httpclient.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-logging.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/dom4j.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/ejb3-persistence.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/el-api.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hibernate-annotations.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hibernate-entitymanager.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hibernate3.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hsqldb-plugin.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hsqldb.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/javassist.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jaxen.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-cache-jdk50.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-common-jdbc-wrapper.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-ejb3x.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-hibernate.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-j2ee.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jaxrpc.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jca.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jsr77.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jsr88.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-management.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-monitoring.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-remoting-int.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-remoting.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-saaj.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-serialization.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-srp.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-transaction.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-vfs.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossjta-integration.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossjta.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossmq.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbosssx.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossts-common.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossws-integration.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jmx-adaptor-plugin.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jnpserver.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/joesnmp.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jpl-pattern.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jpl-util.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jsp-api.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/log4j-snmp-appender.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/log4j.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/mail-plugin.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/mail.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/properties-plugin.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/quartz.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/scheduler-plugin-example.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/scheduler-plugin.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/servlet-api.jar
labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/xmlentitymgr.jar
Log:
JBLAB-868
AS for kosmos server, 4.2.0.GA without ejb3
-Pawel
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/JBossORG-EULA.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/JBossORG-EULA.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/JBossORG-EULA.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,107 @@
+LICENSE AGREEMENT
+JBOSS(r)
+
+This License Agreement governs the use of the Software Packages and any updates to the Software
+Packages, regardless of the delivery mechanism. Each Software Package is a collective work
+under U.S. Copyright Law. Subject to the following terms, Red Hat, Inc. ("Red Hat") grants to
+the user ("Client") a license to the applicable collective work(s) pursuant to the
+GNU Lesser General Public License v. 2.1 except for the following Software Packages:
+(a) JBoss Portal Forums and JBoss Transactions JTS, each of which is licensed pursuant to the
+GNU General Public License v.2;
+
+(b) JBoss Rules, which is licensed pursuant to the Apache License v.2.0;
+
+(c) an optional download for JBoss Cache for the Berkeley DB for Java database, which is licensed under the
+(open source) Sleepycat License (if Client does not wish to use the open source version of this database,
+it may purchase a license from Sleepycat Software);
+
+and (d) the BPEL extension for JBoss jBPM, which is licensed under the Common Public License v.1,
+and, pursuant to the OASIS BPEL4WS standard, requires parties wishing to redistribute to enter various
+royalty-free patent licenses.
+
+Each of the foregoing licenses is available at http://www.opensource.org/licenses/index.php.
+
+1. The Software. "Software Packages" refer to the various software modules that are created and made available
+for distribution by the JBoss.org open source community at http://www.jboss.org. Each of the Software Packages
+may be comprised of hundreds of software components. The end user license agreement for each component is located in
+the component's source code. With the exception of certain image files identified in Section 2 below,
+the license terms for the components permit Client to copy, modify, and redistribute the component,
+in both source code and binary code forms. This agreement does not limit Client's rights under,
+or grant Client rights that supersede, the license terms of any particular component.
+
+2. Intellectual Property Rights. The Software Packages are owned by Red Hat and others and are protected under copyright
+and other laws. Title to the Software Packages and any component, or to any copy, modification, or merged portion shall
+remain with the aforementioned, subject to the applicable license. The "JBoss" trademark, "Red Hat" trademark, the
+individual Software Package trademarks, and the "Shadowman" logo are registered trademarks of Red Hat and its affiliates
+in the U.S. and other countries. This agreement permits Client to distribute unmodified copies of the Software Packages
+using the Red Hat trademarks that Red Hat has inserted in the Software Packages on the condition that Client follows Red Hat's
+trademark guidelines for those trademarks located at http://www.redhat.com/about/corporate/trademark/. Client must abide by
+these trademark guidelines when distributing the Software Packages, regardless of whether the Software Packages have been modified.
+If Client modifies the Software Packages, then Client must replace all Red Hat trademarks and logos identified at
+http://www.jboss.com/company/logos, unless a separate agreement with Red Hat is executed or other permission granted.
+Merely deleting the files containing the Red Hat trademarks may corrupt the Software Packages.
+
+3. Limited Warranty. Except as specifically stated in this Paragraph 3 or a license for a particular
+component, to the maximum extent permitted under applicable law, the Software Packages and the
+components are provided and licensed "as is" without warranty of any kind, expressed or implied,
+including the implied warranties of merchantability, non-infringement or fitness for a particular purpose.
+Red Hat warrants that the media on which Software Packages may be furnished will be free from defects in
+materials and manufacture under normal use for a period of 30 days from the date of delivery to Client.
+Red Hat does not warrant that the functions contained in the Software Packages will meet Client's requirements
+or that the operation of the Software Packages will be entirely error free or appear precisely as described
+in the accompanying documentation. This warranty extends only to the party that purchases the Services
+pertaining to the Software Packages from Red Hat or a Red Hat authorized distributor.
+
+4. Limitation of Remedies and Liability. To the maximum extent permitted by applicable law, the remedies
+described below are accepted by Client as its only remedies. Red Hat's entire liability, and Client's
+exclusive remedies, shall be: If the Software media is defective, Client may return it within 30 days of
+delivery along with a copy of Client's payment receipt and Red Hat, at its option, will replace it or
+refund the money paid by Client for the Software. To the maximum extent permitted by applicable law,
+Red Hat or any Red Hat authorized dealer will not be liable to Client for any incidental or consequential
+damages, including lost profits or lost savings arising out of the use or inability to use the Software,
+even if Red Hat or such dealer has been advised of the possibility of such damages. In no event shall
+Red Hat's liability under this agreement exceed the amount that Client paid to Red Hat under this
+Agreement during the twelve months preceding the action.
+
+5. Export Control. As required by U.S. law, Client represents and warrants that it:
+(a) understands that the Software Packages are subject to export controls under the
+U.S. Commerce Department's Export Administration Regulations ("EAR");
+
+(b) is not located in a prohibited destination country under the EAR or U.S. sanctions regulations
+(currently Cuba, Iran, Iraq, Libya, North Korea, Sudan and Syria);
+
+(c) will not export, re-export, or transfer the Software Packages to any prohibited destination, entity,
+or individual without the necessary export license(s) or authorizations(s) from the U.S. Government;
+
+(d) will not use or transfer the Software Packages for use in any sensitive nuclear, chemical or
+biological weapons, or missile technology end-uses unless authorized by the U.S. Government by
+regulation or specific license;
+
+(e) understands and agrees that if it is in the United States and exports or transfers the Software
+Packages to eligible end users, it will, as required by EAR Section 740.17(e), submit semi-annual
+reports to the Commerce Department's Bureau of Industry & Security (BIS), which include the name and
+address (including country) of each transferee;
+
+and (f) understands that countries other than the United States may restrict the import, use, or
+export of encryption products and that it shall be solely responsible for compliance with any such
+import, use, or export restrictions.
+
+6. Third Party Programs. Red Hat may distribute third party software programs with the Software Packages
+that are not part of the Software Packages and which Client must install separately. These third party
+programs are subject to their own license terms. The license terms either accompany the programs or
+can be viewed at http://www.redhat.com/licenses/. If Client does not agree to abide by the applicable
+license terms for such programs, then Client may not install them. If Client wishes to install the programs
+on more than one system or transfer the programs to another party, then Client must contact the licensor
+of the programs.
+
+7. General. If any provision of this agreement is held to be unenforceable, that shall not affect the
+enforceability of the remaining provisions. This License Agreement shall be governed by the laws of the
+State of North Carolina and of the United States, without regard to any conflict of laws provisions,
+except that the United Nations Convention on the International Sale of Goods shall not apply.
+
+Copyright 2006 Red Hat, Inc. All rights reserved.
+"JBoss" and the JBoss logo are registered trademarks of Red Hat, Inc.
+All other trademarks are the property of their respective owners.
+
+ Page 1 of 1 18 October 2006
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/classpath.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/classpath.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/classpath.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,193 @@
+#!/bin/sh
+### ====================================================================== ###
+## ##
+## A tool to determine JBoss classpaths. ##
+## ##
+### ====================================================================== ###
+
+### $Id: classpath.sh 7809 2002-05-22 02:39:56Z user57 $ ###
+
+DIRNAME=`dirname $0`
+PROGNAME=`basename $0`
+CAT="cat"
+
+#
+# Helper to complain.
+#
+warn() {
+ echo "${PROGNAME}: $*"
+}
+
+#
+# Helper to puke.
+#
+die() {
+ warn $*
+ exit 1
+}
+
+# OS specific support (must be 'true' or 'false').
+cygwin=false;
+darwin=false;
+case "`uname`" in
+ CYGWIN*)
+ cygwin=true
+ ;;
+
+ Darwin*)
+ darwin=true
+ ;;
+esac
+
+#
+# Print the command line help message.
+#
+printHelpMessage() {
+ $CAT <<EOF
+usage: $PROGNAME [options] <classpath>
+
+options:
+ -h, --help Print this help message.
+ -- Stop processing options.
+ -r, --relative Use relative paths.
+
+classpath:
+ -c, --client Client classpath (client/*).
+ -s, --server Server classpath (lib/*).
+ -b, --both Both the client and server classpaths.
+EOF
+}
+
+RELATIVE=false
+
+#
+# Process command line options.
+#
+processCommandLine() {
+ while [ "x$1" != "x" ]; do
+ case "$1" in
+ --help|-h)
+ printHelpMessage
+ exit 1
+ ;;
+
+ --relative|-r)
+ RELATIVE=true
+ ;;
+
+ --)
+ shift
+ if [ "x$argv" = "x" ]; then
+ argv="$1"
+ else
+ argv="$argv $1"
+ fi
+ break
+ ;;
+
+ *)
+ if [ "x$argv" = "x" ]; then
+ argv="$1"
+ else
+ argv="$argv $1"
+ fi
+ ;;
+ esac
+ shift
+ done
+}
+
+if [ -n "$CLASSPATH" ] ; then
+ LOCALCLASSPATH=$CLASSPATH
+fi
+
+#
+# Print the class path for the given type.
+#
+printClassPath() {
+
+#
+# jason: should be fixed to only include proper classpath bits
+#
+
+ case "$1" in
+ -c|--client)
+ DIRLIBS="`ls $JBOSS_HOME/client/*`:$JBOSS_HOME/client"
+ ;;
+
+ -s|--server)
+ DIRLIBS=`ls $JBOSS_HOME/lib/*`
+ ;;
+
+ -b|--both)
+ DIRLIBS="`ls $JBOSS_HOME/client/*`:$JBOSS_HOME/client"
+ DIRLIBS="${DIRLIBS}:`ls $JBOSS_HOME/lib/*`"
+ ;;
+
+ *)
+ printHelpMessage
+ exit 0
+ ;;
+ esac
+
+ for i in ${DIRLIBS}; do
+ if [ "$i" != "${DIRLIBS}" ] ; then
+ if [ -z "$LOCALCLASSPATH" ] ; then
+ LOCALCLASSPATH=$i
+ else
+ LOCALCLASSPATH="$i":$LOCALCLASSPATH
+ fi
+ fi
+ done
+
+ # For Cygwin, switch paths to Windows format before running java
+ if $cygwin; then
+ LOCALCLASSPATH=`cygpath --path --windows "$LOCALCLASSPATH"`
+ fi
+
+ echo $LOCALCLASSPATH
+}
+
+#
+# Main entry-point.
+#
+main() {
+ argv=""
+
+ # process the command line
+ processCommandLine "$@"
+
+ # For Cygwin, ensure paths are in UNIX format before anything is touched
+ if $cygwin ; then
+ [ -n "$JBOSS_HOME" ] &&
+ JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
+ [ -n "$JAVA_HOME" ] &&
+ JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
+ [ -n "$JAVAC_JAR" ] &&
+ JAVAC_JAR=`cygpath --unix "$JAVAC_JAR"`
+ fi
+
+ # Setup JBOSS_HOME
+ if [ "x$JBOSS_HOME" = "x" ]; then
+ if $RELATIVE ; then
+ JBOSS_HOME="$DIRNAME/.."
+ else
+ # get the full path (without any relative bits)
+ JBOSS_HOME=`cd $DIRNAME/..; pwd`
+ fi
+ fi
+
+ if [ "x$argv" = "x" ]; then
+ printHelpMessage
+ exit 0
+ fi
+
+ printClassPath $argv
+}
+
+# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
+
+#
+# Boot-strap
+#
+main "$@"
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/classpath.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_hpux.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_hpux.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_hpux.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,257 @@
+#!/bin/sh
+#
+# $Id: jboss_init_hpux.sh 57105 2006-09-23 14:09:27Z dimitris at jboss.org $
+#
+# JBoss Control Script for HP-UX
+#
+# description: JBoss Applicaton Server / EJB Container
+#
+# Run this script as the root user. This script will start
+# as many instances of JBoss as there are array entries in a
+# startup configuration file under /etc/rc.config.d/ as
+# defined below. If no configuration file exists, the script
+# will still attempt to start at least one server using default
+# values.
+#
+# Installation Instructions:
+# 1. Copy <jboss-home>/bin/jboss_init_hpux.sh to/sbin/init.d/jboss
+# 2. Create softlinks to the file from the various startup and shutdown
+# directories:
+# ln -s /sbin/init.d/jboss /sbin/rc2.d/K001jboss
+# ln -s /sbin/init.d/jboss /sbin/rc3.d/S999jboss
+# 3. Create /etc/rc.config.d/jboss with the variables defined below. For
+# example if you have two servers at /opt/jboss1 and /opt/jboss2 that run
+# as users jboss1 and jboss2 using the default instances, then you would
+# create the following configuration entries:
+#############
+# JBOSS_HOME[0]=/opt/jboss1
+# JBOSS_USER[0]=jboss1
+# SERVER_NAME[0]=default
+# JBOSS_START[0]=1
+## default console logging (you can also just omit the next line)
+# JBOSS_CONSOLE[0]=""
+#############
+# JBOSS_HOME[1]=/opt/jboss2
+# JBOSS_USER[1]=jboss2
+# SERVER_NAME[1]=default
+# JBOSS_START[1]=1
+## No Console logging
+# JBOSS_CONSOLE[1]=/dev/null
+#
+
+##################################################################
+#
+# This script will start as many instances of JBoss as there are
+# consecutive array entries for the variables defined below.
+#
+# There may be a unique jboss server instance for each $JBOSS_HOME[i]
+# and $SERVER_NAME[i] combination.
+#
+# The following variables should be defined in /etc/rc.config.d/jboss.
+# If they are not, the variables are defaulted below:
+#
+# JBOSS_HOME[i] - root directory for jboss installation, like
+# /opt/jboss-<version>.
+# The default for the 1st instance is /opt/jboss: JBOSS_HOME[0]=/opt/jboss.
+# No default for any other instance.
+#
+# SERVER_NAME[i] - server instance name. Normally "all", "default", or
+# "minimal". Maps to server instance at $JBOSS_HOME/server/$SERVER_NAME
+# The default value is "default".
+#
+# JBOSS_START[i] - set to "0" to force JBOSS to not start when this script
+# is run. Usefull when this script is run automatically at system
+# startup time. Default is "1" to startup.
+#
+# JBOSS_USER[i] - it is username by which the jboss application server
+# is started. The default user is jboss.
+#
+# JBOSS_CONSOLE[i] - file where jboss console logging will be written
+# Use "/dev/null" if console logging is not desired.
+# default is /var/opt/jboss/jboss_<user>_<instance>.log
+#
+# JAVA_HOME should also be defined in the target users environment, such
+# as is the case when it is exported from ~/.profile.
+#
+# NOTE: The notation for array subscript [0] is optional. You can refer to
+# JBOSS_HOME[0] as JBOSS_HOME.
+#
+# read config variables from files in /etc/rc.config.d
+# by convention the config values should be in a file /etc/rc.config.d,
+# such as /etc/rc.config.d/jboss. If these variables are not defined
+# in a configuration file in rc.config.d, we will attempt to deal with it by
+# setting defaults in the program
+
+if [ -f /etc/rc.config ]
+then
+ . /etc/rc.config
+else
+ print "ERROR: /etc/rc.config default file MISSING" 1>&2
+fi
+umask 022
+
+#
+# Make sure variables are defined at least for the first instance of the
+# array. Note that $SERVER_NAME is the same as ${SERVER_NAME[0]}
+
+JBOSS_HOME=${JBOSS_HOME:-"/opt/jboss"}
+
+PATH=/sbin:/usr/sbin:/usr/bin:$PATH
+export PATH
+
+#Usage: isJBossRunning <jbossHome> <jbossUserId> <instance>
+# sets non zero return code if Jboss is not running
+# sets global isJBossRunningPid with 1st process id if it is running
+isJBossRunning()
+{
+ typeset JBossHome=$2 JBossUserId=$1 instance=$3 junk
+ ((isJBossRunningPid=0))
+ # pipeline reads 1st jboss pid if it is running for user, jboss home, and instance
+ ps -xu $JBossUserId |
+ grep "$JBossHome.*org.jboss.Main.*\-c[ \t]*$instance" | grep -v "grep" |
+ read isJBossRunningPid junk
+}
+
+#USAGE: isUserOK
+# prints any problems on standard error and returns with a non-zero status
+# returns a 0 status if all is OK
+isUserOK()
+{
+ # check if the user exists
+ id ${JBOSS_USER[i]} >/dev/null 2>&1
+ if (($?!=0)); then
+ echo "ERROR: The user ${JBOSS_USER[i]} does not exist." 1>&2
+ return 1
+ fi
+
+ # check if the user has write permission on the jboss instance directory
+ su ${JBOSS_USER[i]} -c "test -w ${JBOSS_HOME[i]}/server/${SERVER_NAME[i]}" >/dev/null 2>&1
+ if (($?!=0)); then
+ echo "ERROR: The user ${JBOSS_USER[i]} does not have write access to ${JBOSS_HOME[i]}/server/${SERVER_NAME[i]}" 1>&2
+ return 2
+ fi
+
+ # user must have JAVA_HOME defined
+ su - ${JBOSS_USER[i]} -c 'whence java || [[ -d $JAVA_HOME ]]' >/dev/null 2>&1
+ if (($?!=0)); then
+ echo "ERROR: The user \"${JBOSS_USER[i]}\" does not have \$JAVA_HOME defined; either define \$JAVA_HOME for this user or ensure that a path to \"java\" exists." 1>&2
+ return 3
+ fi
+
+ # user looks good so far
+ return 0
+}
+
+# Usage: startJBoss <index>
+startJBoss()
+{
+ typeset -i i=$1
+
+ (( ${JBOSS_START[i]} != 1 )) && return 0
+
+ # make sure the console log exists with appropriate permissions for JBOSS_USER[i]
+ if [[ ! -d ${JBOSS_CONSOLE[i]%/*} ]]; then
+ mkdir -p ${JBOSS_CONSOLE[i]%/*}
+ chmod 0755 ${JBOSS_CONSOLE[i]%/*}
+ chown ${JBOSS_USER[i]} ${JBOSS_CONSOLE[i]%/*}
+ fi
+
+ # do some basic error checking
+ if [[ ! -d ${JBOSS_HOME[i]} ]]; then
+ echo "ERROR: JBOSS_HOME[$i] is not a valid directory : ${JBOSS_HOME[i]}" 1>&2
+ return 1
+ fi
+
+ isUserOK || return 2
+
+ isJBossRunning ${JBOSS_USER[i]} ${JBOSS_HOME[i]} ${SERVER_NAME[i]}
+ if (( $? == 0 )); then
+ echo "JBoss AS is already running for user ${JBOSS_USER[i]} at ${JBOSS_HOME[i]} with instance ${SERVER_NAME[i]}" 1>&2
+ return 3
+ fi
+
+ # keep last version of the console log around
+ [[ -f ${JBOSS_CONSOLE[i]} ]] && mv ${JBOSS_CONSOLE[i]} ${JBOSS_CONSOLE[i]}.old
+
+ # JBoss is not running, start it up
+ CMD_START="${JBOSS_HOME[i]}/bin/run.sh -c ${SERVER_NAME[i]}"
+ nohup su - ${JBOSS_USER[i]} -c "sh $CMD_START" >${JBOSS_CONSOLE[i]} 2>&1 &
+ echo "Starting JBoss AS for user ${JBOSS_USER[i]} at ${JBOSS_HOME[i]} with instance ${SERVER_NAME[i]}."
+
+ # wait a few seconds then check if it started ok
+ #isJBossRunning ${JBOSS_USER[i]} ${JBOSS_HOME[i]} ${SERVER_NAME[i]} || sleep 2 ||
+ #isJBossRunning ${JBOSS_USER[i]} ${JBOSS_HOME[i]} ${SERVER_NAME[i]} || sleep 3 ||
+ #echo "... server not started yet. Check the log files for errors"
+}
+
+# Usage: stopJBoss <index>
+stopJBoss()
+{
+ typeset -i i=$1
+
+ # return silently if JBoss AS is not running
+ isJBossRunning ${JBOSS_USER[i]} ${JBOSS_HOME[i]} ${SERVER_NAME[i]} || return 0
+
+ # JBoss is running and $isJBossRunningPid is set to the process id
+ # SIGTERM does a gracefull shutdown like ^C
+ echo "Stopping JBoss AS PID $isJBossRunningPid for user ${JBOSS_USER[i]} at ${JBOSS_HOME[i]} with instance ${SERVER_NAME[i]}"
+ kill -s SIGTERM $isJBossRunningPid
+
+ # wait for up to 30 seconds for the process to terminate gracefully
+ isJBossRunning ${JBOSS_USER[i]} ${JBOSS_HOME[i]} ${SERVER_NAME[i]} && printf "please wait " && sleep 5 &&
+ isJBossRunning ${JBOSS_USER[i]} ${JBOSS_HOME[i]} ${SERVER_NAME[i]} && printf "." && sleep 10 &&
+ isJBossRunning ${JBOSS_USER[i]} ${JBOSS_HOME[i]} ${SERVER_NAME[i]} && printf "." && sleep 15 &&
+ isJBossRunning ${JBOSS_USER[i]} ${JBOSS_HOME[i]} ${SERVER_NAME[i]} &&
+ echo "NOT Terminated! Wait a moment then check to see if the process has shut down gracefully, or terminate it now with\n \"kill -s SIGKILL $isJBossRunningPid\"" >&2
+}
+
+# Usage: doAll <command> <command args>
+doAll()
+{
+ typeset cmd=$1
+ typeset -i rc=0
+ shift
+
+ # loop thru the configuration file for servers to start or stop as identified by JBOSS_HOME[i] and the
+ # other parameters
+
+ ((i=0))
+ while [[ ${JBOSS_HOME[i]} != "" ]]
+ do
+
+ # set defaults for any missing values
+ SERVER_NAME[$i]=${SERVER_NAME[i]:-"default"}
+ JBOSS_USER[$i]=${JBOSS_USER[i]:-"jboss"}
+ JBOSS_CONSOLE[$i]=${JBOSS_CONSOLE[i]:-/var/opt/jboss/${JBOSS_USER[i]}/jboss_${SERVER_NAME[i]}.log}
+ JBOSS_START[$i]=${JBOSS_START[i]:-1}
+
+ $cmd $i $*
+ (($? != 0)) && rc=$?
+ ((i=i+1))
+ done
+ return $rc
+}
+
+case "$1" in
+ start_msg)
+ echo "Starting JBoss"
+ ;;
+ start)
+ doAll startJBoss
+ ;;
+ stop_msg)
+ echo "Stopping JBoss"
+ ;;
+ stop)
+ doAll stopJBoss
+ ;;
+ restart)
+ $0 stop
+ $0 start
+ ;;
+ *)
+ echo "usage: $0 (start|stop|restart|help)" 1>&2
+ exit 1
+esac
+
+exit $?
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_hpux.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_redhat.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_redhat.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_redhat.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,98 @@
+#!/bin/sh
+#
+# $Id: jboss_init_redhat.sh 60992 2007-02-28 11:33:27Z dimitris at jboss.org $
+#
+# JBoss Control Script
+#
+# To use this script run it as root - it will switch to the specified user
+#
+# Here is a little (and extremely primitive) startup/shutdown script
+# for RedHat systems. It assumes that JBoss lives in /usr/local/jboss,
+# it's run by user 'jboss' and JDK binaries are in /usr/local/jdk/bin.
+# All this can be changed in the script itself.
+#
+# Either modify this script for your requirements or just ensure that
+# the following variables are set correctly before calling the script.
+
+#define where jboss is - this is the directory containing directories log, bin, conf etc
+JBOSS_HOME=${JBOSS_HOME:-"/usr/local/jboss"}
+
+#define the user under which jboss will run, or use 'RUNASIS' to run as the current user
+JBOSS_USER=${JBOSS_USER:-"jboss"}
+
+#make sure java is in your path
+JAVAPTH=${JAVAPTH:-"/usr/local/jdk/bin"}
+
+#configuration to use, usually one of 'minimal', 'default', 'all'
+JBOSS_CONF=${JBOSS_CONF:-"default"}
+
+#if JBOSS_HOST specified, use -b to bind jboss services to that address
+JBOSS_BIND_ADDR=${JBOSS_HOST:+"-b $JBOSS_HOST"}
+
+#define the classpath for the shutdown class
+JBOSSCP=${JBOSSCP:-"$JBOSS_HOME/bin/shutdown.jar:$JBOSS_HOME/client/jnet.jar"}
+
+#define the script to use to start jboss
+JBOSSSH=${JBOSSSH:-"$JBOSS_HOME/bin/run.sh -c $JBOSS_CONF $JBOSS_BIND_ADDR"}
+
+if [ "$JBOSS_USER" = "RUNASIS" ]; then
+ SUBIT=""
+else
+ SUBIT="su - $JBOSS_USER -c "
+fi
+
+if [ -n "$JBOSS_CONSOLE" -a ! -d "$JBOSS_CONSOLE" ]; then
+ # ensure the file exists
+ touch $JBOSS_CONSOLE
+ if [ ! -z "$SUBIT" ]; then
+ chown $JBOSS_USER $JBOSS_CONSOLE
+ fi
+fi
+
+if [ -n "$JBOSS_CONSOLE" -a ! -f "$JBOSS_CONSOLE" ]; then
+ echo "WARNING: location for saving console log invalid: $JBOSS_CONSOLE"
+ echo "WARNING: ignoring it and using /dev/null"
+ JBOSS_CONSOLE="/dev/null"
+fi
+
+#define what will be done with the console log
+JBOSS_CONSOLE=${JBOSS_CONSOLE:-"/dev/null"}
+
+JBOSS_CMD_START="cd $JBOSS_HOME/bin; $JBOSSSH"
+JBOSS_CMD_STOP=${JBOSS_CMD_STOP:-"java -classpath $JBOSSCP org.jboss.Shutdown --shutdown"}
+
+if [ -z "`echo $PATH | grep $JAVAPTH`" ]; then
+ export PATH=$PATH:$JAVAPTH
+fi
+
+if [ ! -d "$JBOSS_HOME" ]; then
+ echo JBOSS_HOME does not exist as a valid directory : $JBOSS_HOME
+ exit 1
+fi
+
+echo JBOSS_CMD_START = $JBOSS_CMD_START
+
+case "$1" in
+start)
+ cd $JBOSS_HOME/bin
+ if [ -z "$SUBIT" ]; then
+ eval $JBOSS_CMD_START >${JBOSS_CONSOLE} 2>&1 &
+ else
+ $SUBIT "$JBOSS_CMD_START >${JBOSS_CONSOLE} 2>&1 &"
+ fi
+ ;;
+stop)
+ if [ -z "$SUBIT" ]; then
+ $JBOSS_CMD_STOP
+ else
+ $SUBIT "$JBOSS_CMD_STOP"
+ fi
+ ;;
+restart)
+ $0 stop
+ $0 start
+ ;;
+*)
+ echo "usage: $0 (start|stop|restart|help)"
+esac
+
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_redhat.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_suse.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_suse.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_suse.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,133 @@
+#!/bin/sh
+#
+# JBoss Control Script
+#
+# To use this script
+# run it as root - it will switch to the specified user
+# It loses all console output - use the log.
+#
+# Here is a little (and extremely primitive)
+# startup/shutdown script for SuSE systems. It assumes
+# that JBoss lives in /usr/local/jboss, it's run by user
+# 'jboss' and JDK binaries are in /usr/local/jdk/bin. All
+# this can be changed in the script itself.
+#
+# Either amend this script for your requirements
+# or just ensure that the following variables are set correctly
+# before calling the script.
+#
+### BEGIN INIT INFO
+# Provides: jboss
+# Default-Start: 3 5
+# Default-Stop: 0 1 2 6
+# Description: Start the JBoss application server.
+### END INIT INFO
+
+#define where jboss is - this is the directory containing directories log, bin, conf etc
+JBOSS_HOME=${JBOSS_HOME:-"/opt/jboss"}
+
+#make java is on your path
+JAVAPTH=${JAVAPTH:-"/usr/java/j2sdk1.4.1/bin"}
+
+#define the classpath for the shutdown class
+JBOSSCP=${JBOSSCP:-"$JBOSS_HOME/bin/shutdown.jar:$JBOSS_HOME/client/jnet.jar"}
+
+#define the script to use to start jboss
+JBOSSSH=${JBOSSSH:-"$JBOSS_HOME/bin/run.sh -c default"}
+
+# Shell functions sourced from /etc/rc.status:
+# rc_check check and set local and overall rc status
+# rc_status check and set local and overall rc status
+# rc_status -v ditto but be verbose in local rc status
+# rc_status -v -r ditto and clear the local rc status
+# rc_failed set local and overall rc status to failed
+# rc_reset clear local rc status (overall remains)
+# rc_exit exit appropriate to overall rc status
+. /etc/rc.status
+
+# First reset status of this service
+rc_reset
+
+# Return values acc. to LSB for all commands but status:
+# 0 - success
+# 1 - misc error
+# 2 - invalid or excess args
+# 3 - unimplemented feature (e.g. reload)
+# 4 - insufficient privilege
+# 5 - program not installed
+# 6 - program not configured
+#
+# Note that starting an already running service, stopping
+# or restarting a not-running service as well as the restart
+# with force-reload (in case signalling is not supported) are
+# considered a success.
+
+if [ -n "$JBOSS_CONSOLE" -a ! -d "$JBOSS_CONSOLE" ]; then
+ # ensure the file exists
+ touch $JBOSS_CONSOLE
+fi
+
+if [ -n "$JBOSS_CONSOLE" -a ! -f "$JBOSS_CONSOLE" ]; then
+ echo "WARNING: location for saving console log invalid: $JBOSS_CONSOLE"
+ echo "WARNING: ignoring it and using /dev/null"
+ JBOSS_CONSOLE="/dev/null"
+fi
+
+#define what will be done with the console log
+JBOSS_CONSOLE=${JBOSS_CONSOLE:-"/opt/jboss/log/jboss.log"}
+
+#define the user under which jboss will run, or use RUNASIS to run as the current user
+JBOSSUS=${JBOSSUS:-"jboss"}
+
+CMD_START="cd $JBOSS_HOME/bin; $JBOSSSH"
+CMD_STOP="java -classpath $JBOSSCP org.jboss.Shutdown --shutdown"
+
+if [ "$JBOSSUS" = "RUNASIS" ]; then
+ SUBIT=""
+else
+ SUBIT="su - $JBOSSUS -c "
+fi
+
+if [ -z "`echo $PATH | grep $JAVAPTH`" ]; then
+ export PATH=$PATH:$JAVAPTH
+fi
+
+if [ ! -d "$JBOSS_HOME" ]; then
+ echo JBOSS_HOME does not exist as a valid directory : $JBOSS_HOME
+ exit 1
+fi
+
+case "$1" in
+start)
+ echo -n "Starting JBoss application server: "
+ cd $JBOSS_HOME/bin
+ if [ -z "$SUBIT" ]; then
+ eval $CMD_START >${JBOSS_CONSOLE} 2>&1 &
+ else
+ $SUBIT "$CMD_START >${JBOSS_CONSOLE} 2>&1 &"
+ fi
+
+ # Remember status and be verbose
+ rc_status -v
+ ;;
+stop)
+ echo -n "Shutting down JBoss application server: "
+ if [ -z "$SUBIT" ]; then
+ $CMD_STOP
+ else
+ $SUBIT "$CMD_STOP"
+ fi
+
+ # Remember status and be verbose
+ rc_status -v
+ ;;
+restart)
+ $0 stop
+ $0 start
+
+ # Remember status and be quiet
+ rc_status
+ ;;
+*)
+ echo "usage: $0 (start|stop|restart|help)"
+esac
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/jboss_init_suse.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/probe.bat
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/probe.bat (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/probe.bat 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,13 @@
+ at echo off
+rem -------------------------------------------------------------------------
+rem JGroups Cluster Discovery Script for Win32
+rem -------------------------------------------------------------------------
+
+REM Discovers all UDP-based members running on a certain mcast address (use -help for help)
+REM Probe [-help] [-addr <addr>] [-port <port>] [-ttl <ttl>] [-timeout <timeout>]
+
+set CLASSPATH=..\lib\commons-logging.jar;..\server\all\lib\jgroups.jar
+
+set CP=%CLASSPATH%
+
+java -cp %CP% org.jgroups.tests.Probe %*
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/probe.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/probe.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/probe.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,27 @@
+#!/bin/sh
+### ====================================================================== ###
+## ##
+## JGroups Cluster Discovery Script ##
+## ##
+### ====================================================================== ###
+
+# Discovers all UDP-based members running on a certain mcast address (use -help for help)
+# Probe [-help] [-addr <addr>] [-port <port>] [-ttl <ttl>] [-timeout <timeout>]
+
+CLASSPATH=.:../lib/commons-logging.jar:../server/all/lib/jgroups.jar:$CLASSPATH
+
+# OS specific support (must be 'true' or 'false').
+cygwin=false;
+case "`uname`" in
+ CYGWIN*)
+ cygwin=true
+ ;;
+esac
+
+if [ $cygwin = "true" ]; then
+ CP=`cygpath -wp $CLASSPATH`
+else
+ CP=$CLASSPATH
+fi
+
+java -cp $CP org.jgroups.tests.Probe $*
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/probe.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.bat
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.bat (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.bat 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,120 @@
+ at echo off
+rem -------------------------------------------------------------------------
+rem JBoss Bootstrap Script for Win32
+rem -------------------------------------------------------------------------
+
+rem $Id: run.bat 60996 2007-02-28 13:44:01Z dimitris at jboss.org $
+
+ at if not "%ECHO%" == "" echo %ECHO%
+ at if "%OS%" == "Windows_NT" setlocal
+
+set DIRNAME=.\
+if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
+set PROGNAME=run.bat
+if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
+
+pushd %DIRNAME%..
+set JBOSS_HOME=%CD%
+popd
+
+REM Add bin/native to the PATH if present
+if exist "%JBOSS_HOME%\bin\native" set PATH=%JBOSS_HOME%\bin\native;%PATH%
+if exist "%JBOSS_HOME%\bin\native" set JAVA_OPTS=%JAVA_OPTS% -Djava.library.path=%JBOSS_HOME%\bin\native
+
+rem Read all command line arguments
+
+REM
+REM The %ARGS% env variable commented out in favor of using %* to include
+REM all args in java command line. See bug #840239. [jpl]
+REM
+REM set ARGS=
+REM :loop
+REM if [%1] == [] goto endloop
+REM set ARGS=%ARGS% %1
+REM shift
+REM goto loop
+REM :endloop
+
+rem Find run.jar, or we can't continue
+
+set RUNJAR=%JBOSS_HOME%\bin\run.jar
+if exist "%RUNJAR%" goto FOUND_RUN_JAR
+echo Could not locate %RUNJAR%. Please check that you are in the
+echo bin directory when running this script.
+goto END
+
+:FOUND_RUN_JAR
+
+if not "%JAVA_HOME%" == "" goto ADD_TOOLS
+
+set JAVA=java
+
+echo JAVA_HOME is not set. Unexpected results may occur.
+echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
+goto SKIP_TOOLS
+
+:ADD_TOOLS
+
+set JAVA=%JAVA_HOME%\bin\java
+
+rem A full JDK with toos.jar is not required anymore since jboss web packages
+rem the eclipse jdt compiler and javassist has its own internal compiler.
+if not exist "%JAVA_HOME%\lib\tools.jar" goto SKIP_TOOLS
+
+rem If exists, point to the JDK javac compiler in case the user wants to
+rem later override the eclipse jdt compiler for compiling JSP pages.
+set JAVAC_JAR=%JAVA_HOME%\lib\tools.jar
+
+:SKIP_TOOLS
+
+rem If JBOSS_CLASSPATH or JAVAC_JAR is empty, don't include it, as this will
+rem result in including the local directory in the classpath, which makes
+rem error tracking harder.
+if not "%JAVAC_JAR%" == "" set RUNJAR=%JAVAC_JAR%;%RUNJAR%
+if "%JBOSS_CLASSPATH%" == "" set RUN_CLASSPATH=%RUNJAR%
+if "%RUN_CLASSPATH%" == "" set RUN_CLASSPATH=%JBOSS_CLASSPATH%;%RUNJAR%
+
+set JBOSS_CLASSPATH=%RUN_CLASSPATH%
+
+rem Setup JBoss specific properties
+set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME%
+
+rem Add -server to the JVM options, if supported
+"%JAVA%" -version 2>&1 | findstr /I hotspot > nul
+if not errorlevel == 1 (set JAVA_OPTS=%JAVA_OPTS% -server)
+
+rem JVM memory allocation pool parameters. Modify as appropriate.
+set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m
+
+rem With Sun JVMs reduce the RMI GCs to once per hour
+set JAVA_OPTS=%JAVA_OPTS% -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
+
+rem JPDA options. Uncomment and modify as appropriate to enable remote debugging.
+rem set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%
+
+rem Setup the java endorsed dirs
+set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
+
+echo ===============================================================================
+echo.
+echo JBoss Bootstrap Environment
+echo.
+echo JBOSS_HOME: %JBOSS_HOME%
+echo.
+echo JAVA: %JAVA%
+echo.
+echo JAVA_OPTS: %JAVA_OPTS%
+echo.
+echo CLASSPATH: %JBOSS_CLASSPATH%
+echo.
+echo ===============================================================================
+echo.
+
+:RESTART
+"%JAVA%" %JAVA_OPTS% "-Djava.endorsed.dirs=%JBOSS_ENDORSED_DIRS%" -classpath "%JBOSS_CLASSPATH%" org.jboss.Main %*
+if ERRORLEVEL 10 goto RESTART
+
+:END
+if "%NOPAUSE%" == "" pause
+
+:END_NO_PAUSE
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.conf
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.conf (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.conf 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,50 @@
+## -*- shell-script -*- ######################################################
+## ##
+## JBoss Bootstrap Script Configuration ##
+## ##
+##############################################################################
+
+### $Id: run.conf 62747 2007-05-02 17:43:36Z dimitris at jboss.org $
+
+#
+# This file is optional; it may be removed if not needed.
+#
+
+#
+# Specify the maximum file descriptor limit, use "max" or "maximum" to use
+# the default, as queried by the system.
+#
+# Defaults to "maximum"
+#
+#MAX_FD="maximum"
+
+#
+# Specify the profiler configuration file to load.
+#
+# Default is to not load profiler configuration file.
+#
+#PROFILER=""
+
+#
+# Specify the location of the Java home directory. If set then $JAVA will
+# be defined to $JAVA_HOME/bin/java, else $JAVA will be "java".
+#
+#JAVA_HOME="/opt/java/jdk"
+
+#
+# Specify the exact Java VM executable to use.
+#
+#JAVA=""
+
+#
+# Specify options to pass to the Java VM.
+#
+if [ "x$JAVA_OPTS" = "x" ]; then
+ JAVA_OPTS="-Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
+fi
+
+# Sample JPDA settings for remote socket debuging
+#JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"
+
+# Sample JPDA settings for shared memory debugging
+#JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_shmem,server=y,suspend=n,address=jboss"
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,247 @@
+#!/bin/sh
+### ====================================================================== ###
+## ##
+## JBoss Bootstrap Script ##
+## ##
+### ====================================================================== ###
+
+### $Id: run.sh 62745 2007-05-02 17:40:51Z dimitris at jboss.org $ ###
+
+DIRNAME=`dirname $0`
+PROGNAME=`basename $0`
+GREP="grep"
+
+# Use the maximum available, or set MAX_FD != -1 to use that
+MAX_FD="maximum"
+
+#
+# Helper to complain.
+#
+warn() {
+ echo "${PROGNAME}: $*"
+}
+
+#
+# Helper to puke.
+#
+die() {
+ warn $*
+ exit 1
+}
+
+# OS specific support (must be 'true' or 'false').
+cygwin=false;
+darwin=false;
+linux=false;
+case "`uname`" in
+ CYGWIN*)
+ cygwin=true
+ ;;
+
+ Darwin*)
+ darwin=true
+ ;;
+
+ Linux)
+ linux=true
+ ;;
+esac
+
+# Read an optional running configuration file
+if [ "x$RUN_CONF" = "x" ]; then
+ RUN_CONF="$DIRNAME/run.conf"
+fi
+if [ -r "$RUN_CONF" ]; then
+ . "$RUN_CONF"
+fi
+
+# Force IPv4 on Linux systems since IPv6 doesn't work correctly with jdk5 and lower
+if [ "$linux" = "true" ]; then
+ JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true"
+fi
+
+# For Cygwin, ensure paths are in UNIX format before anything is touched
+if $cygwin ; then
+ [ -n "$JBOSS_HOME" ] &&
+ JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
+ [ -n "$JAVA_HOME" ] &&
+ JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
+ [ -n "$JAVAC_JAR" ] &&
+ JAVAC_JAR=`cygpath --unix "$JAVAC_JAR"`
+fi
+
+# Setup JBOSS_HOME
+if [ "x$JBOSS_HOME" = "x" ]; then
+ # get the full path (without any relative bits)
+ JBOSS_HOME=`cd $DIRNAME/..; pwd`
+fi
+export JBOSS_HOME
+
+# Increase the maximum file descriptors if we can
+if [ "$cygwin" = "false" ]; then
+ MAX_FD_LIMIT=`ulimit -H -n`
+ if [ $? -eq 0 ]; then
+ if [ "$MAX_FD" = "maximum" -o "$MAX_FD" = "max" ]; then
+ # use the system max
+ MAX_FD="$MAX_FD_LIMIT"
+ fi
+
+ ulimit -n $MAX_FD
+ if [ $? -ne 0 ]; then
+ warn "Could not set maximum file descriptor limit: $MAX_FD"
+ fi
+ else
+ warn "Could not query system maximum file descriptor limit: $MAX_FD_LIMIT"
+ fi
+fi
+
+# Setup the JVM
+if [ "x$JAVA" = "x" ]; then
+ if [ "x$JAVA_HOME" != "x" ]; then
+ JAVA="$JAVA_HOME/bin/java"
+ else
+ JAVA="java"
+ fi
+fi
+
+# Setup the classpath
+runjar="$JBOSS_HOME/bin/run.jar"
+if [ ! -f "$runjar" ]; then
+ die "Missing required file: $runjar"
+fi
+JBOSS_BOOT_CLASSPATH="$runjar"
+
+# Tomcat uses the JDT Compiler
+# Only include tools.jar if someone wants to use the JDK instead.
+# compatible distribution which JAVA_HOME points to
+if [ "x$JAVAC_JAR" = "x" ]; then
+ JAVAC_JAR_FILE="$JAVA_HOME/lib/tools.jar"
+else
+ JAVAC_JAR_FILE="$JAVAC_JAR"
+fi
+if [ ! -f "$JAVAC_JAR_FILE" ]; then
+ # MacOSX does not have a seperate tools.jar
+ if [ "$darwin" != "true" -a "x$JAVAC_JAR" != "x" ]; then
+ warn "Missing file: JAVAC_JAR=$JAVAC_JAR"
+ warn "Unexpected results may occur."
+ fi
+ JAVAC_JAR_FILE=
+fi
+
+if [ "x$JBOSS_CLASSPATH" = "x" ]; then
+ JBOSS_CLASSPATH="$JBOSS_BOOT_CLASSPATH"
+else
+ JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_BOOT_CLASSPATH"
+fi
+if [ "x$JAVAC_JAR_FILE" != "x" ]; then
+ JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JAVAC_JAR_FILE"
+fi
+
+# If -server not set in JAVA_OPTS, set it, if supported
+SERVER_SET=`echo $JAVA_OPTS | $GREP "\-server"`
+if [ "x$SERVER_SET" = "x" ]; then
+
+ # Check for SUN(tm) JVM w/ HotSpot support
+ if [ "x$HAS_HOTSPOT" = "x" ]; then
+ HAS_HOTSPOT=`"$JAVA" -version 2>&1 | $GREP -i HotSpot`
+ fi
+
+ # Enable -server if we have Hotspot, unless we can't
+ if [ "x$HAS_HOTSPOT" != "x" ]; then
+ # MacOS does not support -server flag
+ if [ "$darwin" != "true" ]; then
+ JAVA_OPTS="-server $JAVA_OPTS"
+ fi
+ fi
+fi
+
+# Setup JBosst Native library path
+JBOSS_NATIVE_DIR="$JBOSS_HOME/bin/native"
+if [ -d "$JBOSS_NATIVE_DIR" ]; then
+ if $cygwin ; then
+ export PATH="$JBOSS_NATIVE_DIR:$PATH"
+ JBOSS_NATIVE_DIR=`cygpath --dos "$JBOSS_NATIVE_DIR"`
+ fi
+ if [ "x$LD_LIBRARY_PATH" = "x" ]; then
+ LD_LIBRARY_PATH="$JBOSS_NATIVE_DIR"
+ else
+ LD_LIBRARY_PATH="$JBOSS_NATIVE_DIR:$LD_LIBRARY_PATH"
+ fi
+ export LD_LIBRARY_PATH
+ if [ "x$JAVA_OPTS" = "x" ]; then
+ JAVA_OPTS="-Djava.library.path=$JBOSS_NATIVE_DIR"
+ else
+ JAVA_OPTS="$JAVA_OPTS -Djava.library.path=$JBOSS_NATIVE_DIR"
+ fi
+fi
+
+# Setup JBoss sepecific properties
+JAVA_OPTS="-Dprogram.name=$PROGNAME $JAVA_OPTS"
+
+# Setup the java endorsed dirs
+JBOSS_ENDORSED_DIRS="$JBOSS_HOME/lib/endorsed"
+
+# For Cygwin, switch paths to Windows format before running java
+if $cygwin; then
+ JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
+ JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
+ JBOSS_CLASSPATH=`cygpath --path --windows "$JBOSS_CLASSPATH"`
+ JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"`
+fi
+
+# Display our environment
+echo "========================================================================="
+echo ""
+echo " JBoss Bootstrap Environment"
+echo ""
+echo " JBOSS_HOME: $JBOSS_HOME"
+echo ""
+echo " JAVA: $JAVA"
+echo ""
+echo " JAVA_OPTS: $JAVA_OPTS"
+echo ""
+echo " CLASSPATH: $JBOSS_CLASSPATH"
+echo ""
+echo "========================================================================="
+echo ""
+
+while true; do
+ if [ "x$LAUNCH_JBOSS_IN_BACKGROUND" = "x" ]; then
+ # Execute the JVM in the foreground
+ "$JAVA" $JAVA_OPTS \
+ -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \
+ -classpath "$JBOSS_CLASSPATH" \
+ org.jboss.Main "$@"
+ JBOSS_STATUS=$?
+ else
+ # Execute the JVM in the background
+ "$JAVA" $JAVA_OPTS \
+ -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \
+ -classpath "$JBOSS_CLASSPATH" \
+ org.jboss.Main "$@" &
+ JBOSS_PID=$!
+ # Trap common signals and relay them to the jboss process
+ trap "kill -HUP $JBOSS_PID" HUP
+ trap "kill -TERM $JBOSS_PID" INT
+ trap "kill -QUIT $JBOSS_PID" QUIT
+ trap "kill -PIPE $JBOSS_PID" PIPE
+ trap "kill -TERM $JBOSS_PID" TERM
+ # Wait until the background process exits
+ WAIT_STATUS=0
+ while [ "$WAIT_STATUS" -ne 127 ]; do
+ JBOSS_STATUS=$WAIT_STATUS
+ wait $JBOSS_PID 2>/dev/null
+ WAIT_STATUS=$?
+ done
+ fi
+ # If restart doesn't work, check you are running JBossAS 4.0.4+
+ # http://jira.jboss.com/jira/browse/JBAS-2483
+ # or the following if you're running Red Hat 7.0
+ # http://developer.java.sun.com/developer/bugParade/bugs/4465334.html
+ if [ $JBOSS_STATUS -eq 10 ]; then
+ echo "Restarting JBoss..."
+ else
+ exit $JBOSS_STATUS
+ fi
+done
+
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/run.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.bat
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.bat (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.bat 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,66 @@
+ at echo off
+rem -------------------------------------------------------------------------
+rem JBoss JVM Launcher
+rem -------------------------------------------------------------------------
+
+rem $Id: shutdown.bat 22783 2004-08-07 19:39:38Z starksm $
+
+if not "%ECHO%" == "" echo %ECHO%
+if "%OS%" == "Windows_NT" setlocal
+
+set MAIN_JAR_NAME=shutdown.jar
+set MAIN_CLASS=org.jboss.Shutdown
+
+set DIRNAME=.\
+if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
+set PROGNAME=run.bat
+if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
+
+rem Read all command line arguments
+
+set ARGS=
+:loop
+if [%1] == [] goto end
+ set ARGS=%ARGS% %1
+ shift
+ goto loop
+:end
+
+rem Find MAIN_JAR, or we can't continue
+
+set MAIN_JAR=%DIRNAME%\%MAIN_JAR_NAME%
+if exist "%MAIN_JAR%" goto FOUND_MAIN_JAR
+echo Could not locate %MAIN_JAR%. Please check that you are in the
+echo bin directory when running this script.
+goto END
+
+:FOUND_MAIN_JAR
+
+if not "%JAVA_HOME%" == "" goto HAVE_JAVA_HOME
+
+set JAVA=java
+
+echo JAVA_HOME is not set. Unexpected results may occur.
+echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
+goto SKIP_SET_JAVA_HOME
+
+:HAVE_JAVA_HOME
+
+set JAVA=%JAVA_HOME%\bin\java
+
+:SKIP_SET_JAVA_HOME
+
+set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;%MAIN_JAR%;%DIRNAME%/../client/jbossall-client.jar
+
+rem Setup JBoss sepecific properties
+set JAVA_OPTS=%JAVA_OPTS% -Djboss.boot.loader.name=%PROGNAME%
+
+rem JPDA options. Uncomment and modify as appropriate to enable remote debugging.
+rem set JAVA_OPTS=-classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%
+
+"%JAVA%" %JAVA_OPTS% -classpath "%JBOSS_CLASSPATH%" %MAIN_CLASS% %ARGS%
+
+:END
+if "%NOPAUSE%" == "" pause
+
+:END_NO_PAUSE
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,73 @@
+#!/bin/sh
+### ====================================================================== ###
+## ##
+## JBoss Shutdown Script ##
+## ##
+### ====================================================================== ###
+
+### $Id: shutdown.sh 62718 2007-05-02 09:06:09Z dimitris at jboss.org $ ###
+
+DIRNAME=`dirname $0`
+PROGNAME=`basename $0`
+GREP="grep"
+
+#
+# Helper to complain.
+#
+die() {
+ echo "${PROGNAME}: $*"
+ exit 1
+}
+
+# OS specific support (must be 'true' or 'false').
+cygwin=false;
+case "`uname`" in
+ CYGWIN*)
+ cygwin=true
+ ;;
+esac
+
+# For Cygwin, ensure paths are in UNIX format before anything is touched
+if $cygwin ; then
+ [ -n "$JBOSS_HOME" ] &&
+ JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
+ [ -n "$JAVA_HOME" ] &&
+ JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
+fi
+
+# Setup JBOSS_HOME
+if [ "x$JBOSS_HOME" = "x" ]; then
+ JBOSS_HOME=`cd $DIRNAME/..; pwd`
+fi
+export JBOSS_HOME
+
+# Setup the JVM
+if [ "x$JAVA" = "x" ]; then
+ if [ "x$JAVA_HOME" != "x" ]; then
+ JAVA="$JAVA_HOME/bin/java"
+ else
+ JAVA="java"
+ fi
+fi
+
+# Setup the classpath
+JBOSS_BOOT_CLASSPATH="$JBOSS_HOME/bin/shutdown.jar:$JBOSS_HOME/client/jbossall-client.jar"
+
+if [ "x$JBOSS_CLASSPATH" = "x" ]; then
+ JBOSS_CLASSPATH="$JBOSS_BOOT_CLASSPATH"
+else
+ JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_BOOT_CLASSPATH"
+fi
+
+# For Cygwin, switch paths to Windows format before running java
+if $cygwin; then
+ JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
+ JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
+ JBOSS_CLASSPATH=`cygpath --path --windows "$JBOSS_CLASSPATH"`
+fi
+
+# Execute the JVM
+exec "$JAVA" \
+ $JAVA_OPTS \
+ -classpath $JBOSS_CLASSPATH \
+ org.jboss.Shutdown "$@"
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/shutdown.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.bat
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.bat (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.bat 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,71 @@
+ at echo off
+rem -------------------------------------------------------------------------
+rem JBoss JVM Launcher
+rem -------------------------------------------------------------------------
+
+rem $Id: twiddle.bat 62209 2007-04-10 12:41:38Z dimitris at jboss.org $
+
+if not "%ECHO%" == "" echo %ECHO%
+if "%OS%" == "Windows_NT" setlocal
+
+set MAIN_JAR_NAME=twiddle.jar
+set MAIN_CLASS=org.jboss.console.twiddle.Twiddle
+
+set DIRNAME=.\
+if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
+set PROGNAME=run.bat
+if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
+
+rem Read all command line arguments
+
+set ARGS=
+:loop
+if [%1] == [] goto end
+ set ARGS=%ARGS% %1
+ shift
+ goto loop
+:end
+
+rem Find MAIN_JAR, or we can't continue
+
+set MAIN_JAR=%DIRNAME%\%MAIN_JAR_NAME%
+if exist "%MAIN_JAR%" goto FOUND_MAIN_JAR
+echo Could not locate %MAIN_JAR%. Please check that you are in the
+echo bin directory when running this script.
+goto END
+
+:FOUND_MAIN_JAR
+
+if not "%JAVA_HOME%" == "" goto HAVE_JAVA_HOME
+
+set JAVA=java
+
+echo JAVA_HOME is not set. Unexpected results may occur.
+echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
+goto SKIP_SET_JAVA_HOME
+
+:HAVE_JAVA_HOME
+
+set JAVA=%JAVA_HOME%\bin\java
+
+:SKIP_SET_JAVA_HOME
+
+rem only include jbossall-client.jar in classpath, if
+rem JBOSS_CLASSPATH was not yet set
+if not "%JBOSS_CLASSPATH%" == "" GOTO HAVE_JB_CP
+set JBOSS_CLASSPATH=%DIRNAME%\..\client\jbossall-client.jar
+set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;%DIRNAME%\..\client\getopt.jar
+set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;%DIRNAME%\..\client\log4j.jar
+set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;%DIRNAME%\..\lib\jboss-jmx.jar
+:HAVE_JB_CP
+
+set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;%MAIN_JAR%
+
+rem Setup JBoss sepecific properties
+set JBOSS_HOME=%DIRNAME%\..
+set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
+set JAVA_OPTS=%JAVA_OPTS% -Djboss.boot.loader.name=%PROGNAME%
+
+"%JAVA%" %JAVA_OPTS% "-Djava.endorsed.dirs=%JBOSS_ENDORSED_DIRS%" -classpath "%JBOSS_CLASSPATH%" %MAIN_CLASS% %ARGS%
+
+:END
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,81 @@
+#!/bin/sh
+### ====================================================================== ###
+## ##
+## JBoss Shutdown Script ##
+## ##
+### ====================================================================== ###
+
+### $Id: twiddle.sh 57032 2006-09-20 22:03:16Z dimitris at jboss.org $ ###
+
+DIRNAME=`dirname $0`
+PROGNAME=`basename $0`
+GREP="grep"
+
+#
+# Helper to complain.
+#
+die() {
+ echo "${PROGNAME}: $*"
+ exit 1
+}
+
+# OS specific support (must be 'true' or 'false').
+cygwin=false;
+case "`uname`" in
+ CYGWIN*)
+ cygwin=true
+ ;;
+esac
+
+# For Cygwin, ensure paths are in UNIX format before anything is touched
+if $cygwin ; then
+ [ -n "$JBOSS_HOME" ] &&
+ JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
+ [ -n "$JAVA_HOME" ] &&
+ JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
+fi
+
+# Setup JBOSS_HOME
+if [ "x$JBOSS_HOME" = "x" ]; then
+ JBOSS_HOME=`cd $DIRNAME/..; pwd`
+fi
+export JBOSS_HOME
+
+# Setup the JVM
+if [ "x$JAVA_HOME" != "x" ]; then
+ JAVA=$JAVA_HOME/bin/java
+else
+ JAVA="java"
+fi
+
+# Setup the classpath
+JBOSS_BOOT_CLASSPATH="$JBOSS_HOME/bin/twiddle.jar"
+
+if [ "x$JBOSS_CLASSPATH" = "x" ]; then
+ JBOSS_CLASSPATH="$JBOSS_BOOT_CLASSPATH"
+ JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_HOME/client/jbossall-client.jar"
+ JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_HOME/client/getopt.jar"
+ JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_HOME/client/log4j.jar"
+ JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_HOME/lib/jboss-jmx.jar"
+else
+ JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_BOOT_CLASSPATH"
+fi
+
+# Setup the java endorsed dirs
+JBOSS_ENDORSED_DIRS="$JBOSS_HOME/lib/endorsed"
+
+# For Cygwin, switch paths to Windows format before running java
+if $cygwin; then
+ JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
+ JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
+ JBOSS_CLASSPATH=`cygpath --path --windows "$JBOSS_CLASSPATH"`
+ JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"`
+fi
+
+# Execute the JVM
+exec "$JAVA" \
+ $JAVA_OPTS \
+ -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \
+ -Dprogram.name="$PROGNAME" \
+ -classpath $JBOSS_CLASSPATH \
+ org.jboss.console.twiddle.Twiddle "$@"
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/twiddle.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsconsume.bat
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsconsume.bat (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsconsume.bat 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,53 @@
+ at echo off
+
+rem $Id: wsgen.bat 2158 2007-01-27 06:20:59Z jason.greene at jboss.com $
+
+ at if not "%ECHO%" == "" echo %ECHO%
+ at if "%OS%" == "Windows_NT" setlocal
+
+set DIRNAME=.\
+if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
+set PROGNAME=run.bat
+if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
+
+rem Read all command line arguments
+
+REM
+REM The %ARGS% env variable commented out in favor of using %* to include
+REM all args in java command line. See bug #840239. [jpl]
+REM
+REM set ARGS=
+REM :loop
+REM if [%1] == [] goto endloop
+REM set ARGS=%ARGS% %1
+REM shift
+REM goto loop
+REM :endloop
+
+set JAVA=%JAVA_HOME%\bin\java
+set JBOSS_HOME=%DIRNAME%\..
+rem Setup the java endorsed dirs
+set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
+
+rem Setup the wstools classpath
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JAVA_HOME%/lib/tools.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jboss-xml-binding.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/wstx.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/activation.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/javassist.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/getopt.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxb-api.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/stax-api.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxb-impl.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jaxb-xjc.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-wsconsume-impl.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossall-client.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jboss-saaj.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jboss-jaxrpc.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jboss-jaxws.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/jbossws-client.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/log4j.jar
+set WSCONSUME_CLASSPATH=%WSCONSUME_CLASSPATH%;%JBOSS_HOME%/client/mail.jar
+
+rem Execute the JVM
+"%JAVA%" %JAVA_OPTS% -Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" -Dlog4j.configuration=wstools-log4j.xml -classpath "%WSCONSUME_CLASSPATH%" org.jboss.ws.tools.jaxws.command.wsconsume %*
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsconsume.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsconsume.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsconsume.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,82 @@
+#!/bin/sh
+
+# $Id: wsgen.sh 2158 2007-01-27 06:20:59Z jason.greene at jboss.com $
+
+DIRNAME=`dirname $0`
+PROGNAME=`basename $0`
+
+# OS specific support (must be 'true' or 'false').
+cygwin=false;
+case "`uname`" in
+ CYGWIN*)
+ cygwin=true
+ ;;
+esac
+
+# For Cygwin, ensure paths are in UNIX format before anything is touched
+if $cygwin ; then
+ [ -n "$JBOSS_HOME" ] &&
+ JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
+ [ -n "$JAVA_HOME" ] &&
+ JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
+fi
+
+# Setup JBOSS_HOME
+if [ "x$JBOSS_HOME" = "x" ]; then
+ # get the full path (without any relative bits)
+ JBOSS_HOME=`cd $DIRNAME/..; pwd`
+fi
+export JBOSS_HOME
+
+# Setup the JVM
+if [ "x$JAVA" = "x" ]; then
+ if [ "x$JAVA_HOME" != "x" ]; then
+ JAVA="$JAVA_HOME/bin/java"
+ else
+ JAVA="java"
+ fi
+fi
+
+#JPDA options. Uncomment and modify as appropriate to enable remote debugging .
+#JAVA_OPTS="-classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n $JAVA_OPTS"
+
+# Setup JBoss sepecific properties
+JAVA_OPTS="$JAVA_OPTS"
+
+# Setup the java endorsed dirs
+JBOSS_ENDORSED_DIRS="$JBOSS_HOME/lib/endorsed"
+
+# Setup the wstools classpath
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JAVA_HOME/lib/tools.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/jboss-xml-binding.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/wstx.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/jbossws-wsconsume-impl.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/activation.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/getopt.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/javassist.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/jaxb-api.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/stax-api.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/jaxb-impl.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/jaxb-xjc.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/jbossall-client.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/jbossws-client.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/jboss-jaxws.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/jboss-jaxrpc.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/jboss-saaj.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/log4j.jar"
+WSCONSUME_CLASSPATH="$WSCONSUME_CLASSPATH:$JBOSS_HOME/client/mail.jar"
+
+# For Cygwin, switch paths to Windows format before running java
+if $cygwin; then
+ JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
+ JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
+ WSCONSUME_CLASSPATH=`cygpath --path --windows "$WSCONSUME_CLASSPATH"`
+ JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"`
+fi
+
+# Execute the JVM
+"$JAVA" $JAVA_OPTS \
+ -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \
+ -Dlog4j.configuration=wstools-log4j.xml \
+ -classpath "$WSCONSUME_CLASSPATH" \
+ org.jboss.ws.tools.jaxws.command.wsconsume "$@"
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsconsume.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsprovide.bat
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsprovide.bat (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsprovide.bat 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,48 @@
+ at echo off
+
+rem $Id: wsprovide.bat 2464 2007-02-23 21:51:05Z jason.greene at jboss.com $
+
+ at if not "%ECHO%" == "" echo %ECHO%
+ at if "%OS%" == "Windows_NT" setlocal
+
+set DIRNAME=.\
+if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
+set PROGNAME=run.bat
+if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
+
+rem Read all command line arguments
+
+REM
+REM The %ARGS% env variable commented out in favor of using %* to include
+REM all args in java command line. See bug #840239. [jpl]
+REM
+REM set ARGS=
+REM :loop
+REM if [%1] == [] goto endloop
+REM set ARGS=%ARGS% %1
+REM shift
+REM goto loop
+REM :endloop
+
+set JAVA=%JAVA_HOME%\bin\java
+set JBOSS_HOME=%DIRNAME%\..
+rem Setup the java endorsed dirs
+set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
+
+rem Setup the wstools classpath
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jboss-xml-binding.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/activation.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/javassist.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/getopt.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jaxb-api.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jaxb-impl.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jbossall-client.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jbossws-client.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jboss-jaxws.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jboss-jaxrpc.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/jboss-saaj.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/log4j.jar
+set WSPROVIDE_CLASSPATH=%WSPROVIDE_CLASSPATH%;%JBOSS_HOME%/client/mail.jar
+
+rem Execute the JVM
+"%JAVA%" %JAVA_OPTS% -Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" -Dlog4j.configuration=wstools-log4j.xml -classpath "%WSPROVIDE_CLASSPATH%" org.jboss.ws.tools.jaxws.command.wsprovide %*
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsprovide.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsprovide.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsprovide.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,77 @@
+#!/bin/sh
+
+# $Id: wsprovide.sh 2361 2007-02-14 14:52:02Z jason.greene at jboss.com $
+
+DIRNAME=`dirname $0`
+PROGNAME=`basename $0`
+
+# OS specific support (must be 'true' or 'false').
+cygwin=false;
+case "`uname`" in
+ CYGWIN*)
+ cygwin=true
+ ;;
+esac
+
+# For Cygwin, ensure paths are in UNIX format before anything is touched
+if $cygwin ; then
+ [ -n "$JBOSS_HOME" ] &&
+ JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
+ [ -n "$JAVA_HOME" ] &&
+ JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
+fi
+
+# Setup JBOSS_HOME
+if [ "x$JBOSS_HOME" = "x" ]; then
+ # get the full path (without any relative bits)
+ JBOSS_HOME=`cd $DIRNAME/..; pwd`
+fi
+export JBOSS_HOME
+
+# Setup the JVM
+if [ "x$JAVA" = "x" ]; then
+ if [ "x$JAVA_HOME" != "x" ]; then
+ JAVA="$JAVA_HOME/bin/java"
+ else
+ JAVA="java"
+ fi
+fi
+
+#JPDA options. Uncomment and modify as appropriate to enable remote debugging .
+#JAVA_OPTS="-classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n $JAVA_OPTS"
+
+# Setup JBoss sepecific properties
+JAVA_OPTS="$JAVA_OPTS"
+
+# Setup the java endorsed dirs
+JBOSS_ENDORSED_DIRS="$JBOSS_HOME/lib/endorsed"
+
+# Setup the wstools classpath
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jboss-xml-binding.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/activation.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/getopt.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/javassist.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jaxb-api.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jaxb-impl.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jbossall-client.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jbossws-client.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jboss-jaxws.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jboss-jaxrpc.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/jboss-saaj.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/log4j.jar"
+WSPROVIDE_CLASSPATH="$WSPROVIDE_CLASSPATH:$JBOSS_HOME/client/mail.jar"
+
+# For Cygwin, switch paths to Windows format before running java
+if $cygwin; then
+ JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
+ JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
+ WSPROVIDE_CLASSPATH=`cygpath --path --windows "$WSPROVIDE_CLASSPATH"`
+ JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"`
+fi
+
+# Execute the JVM
+"$JAVA" $JAVA_OPTS \
+ -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \
+ -Dlog4j.configuration=wstools-log4j.xml \
+ -classpath "$WSPROVIDE_CLASSPATH" \
+ org.jboss.ws.tools.jaxws.command.wsprovide "$@"
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsprovide.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsrunclient.bat
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsrunclient.bat (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsrunclient.bat 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,61 @@
+ at echo off
+
+rem $Id: wsprovide.bat 2325 2007-02-09 22:14:15Z jason.greene at jboss.com $
+
+ at if not "%ECHO%" == "" echo %ECHO%
+ at if "%OS%" == "Windows_NT" setlocal
+
+set DIRNAME=.\
+if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
+set PROGNAME=run.bat
+if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
+
+
+if not [%1] == [] goto start
+ echo %PROGNAME% is a command line tool that invokes a JBossWS JAX-WS Web Service client.
+ echo It builds the correct classpath and endorsed libs for you. Feel free to use
+ echo the code for this script to make your own shell scripts. It is open source
+ echo after all.
+ echo.
+ echo usage: %PROGNAME% [-classpath ^<additional class path^>] ^<java-main-class^> [arguments...]
+ goto EOF
+:start
+set ARGS=
+:loop
+if [%1] == [] goto endloop
+ if not %1 == -classpath goto argset
+ set WSRUNCLIENT_CLASSPATH=%2
+ shift
+ shift
+ goto loop
+ :argset
+ set ARGS=%ARGS% %1
+ shift
+ goto loop
+:endloop
+
+set JAVA=%JAVA_HOME%\bin\java
+set JBOSS_HOME=%DIRNAME%\..
+rem Setup the java endorsed dirs
+set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
+
+rem Setup the wstools classpath
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jboss-xml-binding.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/activation.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/javassist.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/getopt.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jaxb-api.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jaxb-impl.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jbossall-client.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/stax-api.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/wstx.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jboss-j2ee.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jboss-saaj.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jboss-jaxws.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jboss-jaxrpc.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/jbossws-client.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/log4j.jar
+set WSRUNCLIENT_CLASSPATH=%WSRUNCLIENT_CLASSPATH%;%JBOSS_HOME%/client/mail.jar
+rem Execute the JVM
+"%JAVA%" %JAVA_OPTS% -Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" -Dlog4j.configuration=wstools-log4j.xml -classpath "%WSRUNCLIENT_CLASSPATH%" %ARGS%
+:EOF
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsrunclient.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsrunclient.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsrunclient.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,99 @@
+#!/bin/sh
+
+# $Id: wsprovide 2325 2007-02-09 22:14:15Z jason.greene at jboss.com $
+DIRNAME=`dirname $0`
+PROGNAME=`basename $0`
+
+if [ $# -eq 0 ]; then
+ echo "$PROGNAME is a command line tool that invokes a JBossWS JAX-WS Web Service client."
+ echo "It builds the correct classpath and endorsed libs for you. Feel free to use"
+ echo "the code for this script to make your own shell scripts. It is open source"
+ echo "after all."
+ echo
+ echo "usage: $PROGNAME [-classpath <additional class path>] <java-main-class> [arguments...]"
+ exit 1;
+fi
+
+# OS specific support (must be 'true' or 'false').
+cygwin=false;
+case "`uname`" in
+ CYGWIN*)
+ cygwin=true
+ ;;
+esac
+
+# For Cygwin, ensure paths are in UNIX format before anything is touched
+if $cygwin ; then
+ [ -n "$JBOSS_HOME" ] &&
+ JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
+ [ -n "$JAVA_HOME" ] &&
+ JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
+fi
+
+# Setup JBOSS_HOME
+if [ "x$JBOSS_HOME" = "x" ]; then
+ # get the full path (without any relative bits)
+ JBOSS_HOME=`cd $DIRNAME/..; pwd`
+fi
+export JBOSS_HOME
+
+# Setup the JVM
+if [ "x$JAVA" = "x" ]; then
+ if [ "x$JAVA_HOME" != "x" ]; then
+ JAVA="$JAVA_HOME/bin/java"
+ else
+ JAVA="java"
+ fi
+fi
+
+#JPDA options. Uncomment and modify as appropriate to enable remote debugging .
+#JAVA_OPTS="-classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n $JAVA_OPTS"
+
+# Setup JBoss sepecific properties
+JAVA_OPTS="$JAVA_OPTS"
+
+# Setup the java endorsed dirs
+JBOSS_ENDORSED_DIRS="$JBOSS_HOME/lib/endorsed"
+
+# Setup the wstools classpath
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jboss-xml-binding.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/activation.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/getopt.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/javassist.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jaxb-api.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jaxb-impl.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jaxb-xjc.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jbossall-client.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jboss-j2ee.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jboss-ejb3x.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jbossws-client.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jboss-jaxws.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jboss-jaxrpc.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/jboss-saaj.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/log4j.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/mail.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/stax-api.jar"
+WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$JBOSS_HOME/client/wstx.jar"
+
+while [ $# -ge 1 ]; do
+ case $1 in
+ "-classpath") WSRUNCLIENT_CLASSPATH="$WSRUNCLIENT_CLASSPATH:$2"; shift;;
+ *) args="$args \"$1\"";;
+ esac
+ shift
+done
+
+# For Cygwin, switch paths to Windows format before running java
+if $cygwin; then
+ JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
+ JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
+ WSRUNCLIENT_CLASSPATH=`cygpath --path --windows "$WSRUNCLIENT_CLASSPATH"`
+ JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"`
+fi
+
+# Execute the JVM
+eval "$JAVA" $JAVA_OPTS \
+ -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \
+ -Dlog4j.configuration=wstools-log4j.xml \
+ -classpath "$WSRUNCLIENT_CLASSPATH" \
+ "$args"
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wsrunclient.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wstools.bat
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wstools.bat (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wstools.bat 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,62 @@
+ at echo off
+
+rem $Id: wstools.bat 2156 2007-01-27 05:59:35Z jason.greene at jboss.com $
+
+ at if not "%ECHO%" == "" echo %ECHO%
+ at if "%OS%" == "Windows_NT" setlocal
+
+set DIRNAME=.\
+if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
+set PROGNAME=run.bat
+if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
+
+rem Read all command line arguments
+
+REM
+REM The %ARGS% env variable commented out in favor of using %* to include
+REM all args in java command line. See bug #840239. [jpl]
+REM
+REM set ARGS=
+REM :loop
+REM if [%1] == [] goto endloop
+REM set ARGS=%ARGS% %1
+REM shift
+REM goto loop
+REM :endloop
+
+set JAVA=%JAVA_HOME%\bin\java
+set JBOSS_HOME=%DIRNAME%\..
+rem Setup the java endorsed dirs
+set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
+
+rem Setup the wstools classpath
+set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/jboss-xml-binding.jar
+set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/activation.jar
+set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/javassist.jar
+set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/jbossall-client.jar
+set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/jbossretro-rt.jar
+set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/jboss-backport-concurrent.jar
+set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/jbossws-client.jar
+set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/jbossws14-client.jar
+set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/log4j.jar
+set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/mail.jar
+
+rem Display our environment
+echo ========================================================================="
+echo .
+echo WSTools Environment
+echo .
+echo JBOSS_HOME: %JBOSS_HOME%
+echo .
+echo JAVA: %JAVA%
+echo .
+echo JAVA_OPTS: %JAVA_OPTS%
+echo .
+rem echo CLASSPATH: %WSTOOLS_CLASSPATH%
+rem echo .
+echo ========================================================================="
+echo .
+
+rem Execute the JVM
+"%JAVA%" %JAVA_OPTS% -Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" -Dlog4j.configuration=wstools-log4j.xml -classpath "%WSTOOLS_CLASSPATH%" org.jboss.ws.tools.WSTools %*
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wstools.sh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wstools.sh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wstools.sh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,90 @@
+#!/bin/sh
+
+# $Id: wstools.sh 2157 2007-01-27 06:03:58Z jason.greene at jboss.com $
+
+DIRNAME=`dirname $0`
+PROGNAME=`basename $0`
+
+# OS specific support (must be 'true' or 'false').
+cygwin=false;
+case "`uname`" in
+ CYGWIN*)
+ cygwin=true
+ ;;
+esac
+
+# For Cygwin, ensure paths are in UNIX format before anything is touched
+if $cygwin ; then
+ [ -n "$JBOSS_HOME" ] &&
+ JBOSS_HOME=`cygpath --unix "$JBOSS_HOME"`
+ [ -n "$JAVA_HOME" ] &&
+ JAVA_HOME=`cygpath --unix "$JAVA_HOME"`
+fi
+
+# Setup JBOSS_HOME
+if [ "x$JBOSS_HOME" = "x" ]; then
+ # get the full path (without any relative bits)
+ JBOSS_HOME=`cd $DIRNAME/..; pwd`
+fi
+export JBOSS_HOME
+
+# Setup the JVM
+if [ "x$JAVA" = "x" ]; then
+ if [ "x$JAVA_HOME" != "x" ]; then
+ JAVA="$JAVA_HOME/bin/java"
+ else
+ JAVA="java"
+ fi
+fi
+
+#JPDA options. Uncomment and modify as appropriate to enable remote debugging .
+#JAVA_OPTS="-classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n $JAVA_OPTS"
+
+# Setup JBoss sepecific properties
+JAVA_OPTS="$JAVA_OPTS"
+
+# Setup the java endorsed dirs
+JBOSS_ENDORSED_DIRS="$JBOSS_HOME/lib/endorsed"
+
+# Setup the wstools classpath
+WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jboss-xml-binding.jar"
+WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/activation.jar"
+WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/javassist.jar"
+WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jbossall-client.jar"
+WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jbossretro-rt.jar"
+WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jboss-backport-concurrent.jar"
+WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jbossws14-client.jar"
+WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jbossws-client.jar"
+WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/log4j.jar"
+WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/mail.jar"
+
+# For Cygwin, switch paths to Windows format before running java
+if $cygwin; then
+ JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
+ JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
+ WSTOOLS_CLASSPATH=`cygpath --path --windows "$WSTOOLS_CLASSPATH"`
+ JBOSS_ENDORSED_DIRS=`cygpath --path --windows "$JBOSS_ENDORSED_DIRS"`
+fi
+
+# Display our environment
+echo "========================================================================="
+echo ""
+echo " WSTools Environment"
+echo ""
+echo " JBOSS_HOME: $JBOSS_HOME"
+echo ""
+echo " JAVA: $JAVA"
+echo ""
+echo " JAVA_OPTS: $JAVA_OPTS"
+echo ""
+#echo " CLASSPATH: $WSTOOLS_CLASSPATH"
+#echo ""
+echo "========================================================================="
+echo ""
+
+# Execute the JVM
+"$JAVA" $JAVA_OPTS \
+ -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" \
+ -Dlog4j.configuration=wstools-log4j.xml \
+ -classpath "$WSTOOLS_CLASSPATH" \
+ org.jboss.ws.tools.WSTools "$@"
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/bin/wstools.sh
___________________________________________________________________
Name: svn:executable
+ *
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/activation.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/activation.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/antlr.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/antlr.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/auth.conf
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/auth.conf (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/auth.conf 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,25 @@
+srp-client {
+ // Example client auth.conf for using the SRPLoginModule
+ org.jboss.security.srp.jaas.SRPLoginModule required
+ password-stacking="useFirstPass"
+ principalClassName="org.jboss.security.SimplePrincipal"
+ srpServerJndiName="SRPServerInterface"
+ debug=true
+ ;
+
+ // jBoss LoginModule
+ org.jboss.security.ClientLoginModule required
+ password-stacking="useFirstPass"
+ ;
+
+ // Put your login modules that need jBoss here
+};
+
+other {
+ // jBoss LoginModule
+ org.jboss.security.ClientLoginModule required
+ ;
+
+ // Put your login modules that need jBoss here
+};
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/avalon-framework.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/avalon-framework.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/commons-codec.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/commons-codec.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/commons-httpclient.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/commons-httpclient.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/commons-logging.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/commons-logging.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/concurrent.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/concurrent.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/ejb3-persistence.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/ejb3-persistence.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/getopt.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/getopt.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/hibernate-annotations.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/hibernate-annotations.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/hibernate-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/hibernate-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jacorb.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jacorb.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/javassist.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/javassist.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jaxb-api.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jaxb-api.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jaxb-impl.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jaxb-impl.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jaxb-xjc.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jaxb-xjc.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-annotations-ejb3.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-annotations-ejb3.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-aop-jdk50-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-aop-jdk50-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-aspect-jdk50-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-aspect-jdk50-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-common-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-common-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-deployment.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-deployment.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-ejb3-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-ejb3-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-ejb3x.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-ejb3x.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-iiop-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-iiop-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-j2ee.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-j2ee.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-jaxrpc.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-jaxrpc.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-jaxws.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-jaxws.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-jsr77-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-jsr77-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-remoting.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-remoting.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-saaj.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-saaj.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-serialization.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-serialization.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-srp-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-srp-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-system-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-system-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-transaction-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-transaction-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-xml-binding.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jboss-xml-binding.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossall-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossall-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbosscx-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbosscx-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossha-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossha-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossjmx-ant.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossjmx-ant.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossmq-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossmq-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbosssx-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbosssx-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossws-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossws-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossws-wsconsume-impl.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jbossws-wsconsume-impl.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jmx-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jmx-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jmx-invoker-adaptor-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jmx-invoker-adaptor-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jnp-client.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/jnp-client.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/log4j.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/log4j.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/logkit.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/logkit.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/mail.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/mail.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/scout.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/scout.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/servlet-api.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/servlet-api.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/stax-api.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/stax-api.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/trove.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/trove.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/wsdl4j.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/wsdl4j.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/wstx.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/wstx.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/xmlsec.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/client/xmlsec.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/copyright.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/copyright.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/copyright.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,158 @@
+The JBoss(R)* app server is Copyright 2000-2006, Red Hat Middleware LLC
+and individual contributors, and is licensed under the GNU LGPL.
+
+A summary of the individual contributors is given below.
+Any omission should be sent to scott.stark at jboss.org.
+
+CVS Login(s) Name
+-------------------------------------------------------------------------------
+adrian,ejort Adrian Brock
+aloubyansky,loubyansky Alex Loubyansky
+asaldhana,osdchicago Anil Saldhana
+csuconic,clebert Clebert Suconic
+kkhan,kabkhan Kabir Khan
+ovidiu,ovidiuf Ovidiu Feodorov
+starksm,stark Scott M Stark
+tdiesler Thomas Diesler
+timfox Tim Fox
+bstansberry Brian Stansberry
+jgreene,nihility Jason Greene
+rloehr Ruel Loehr
+reverbel Francisco Reverbel
+dimitris,andd Dimitris Andreadis
+alesj Ales Justin
+bdecoste Bill DeCoste
+bill,patriot1burke Bill Burke
+telrod Tom Elrod
+schrouf Ulf Schroeter
+rrajasekaran Rajesh Rajasekaran
+genman Elias Ross
+clin Chi Lin
+ssilvert Stan Silvert
+peterj Peter Johnson
+rcampbell,recampbell Ryan Cambell
+acoliver,acoliver2 Andy Oliver
+walkerrl49 Bob Walker
+bwang,bwang00 Ben Wang
+pilhuhn Heiko W. Rupp
+jerrygauth Jerry Gauthier
+ltexier Luc Texier
+jchang Jack Chang
+nrichards,orb Norman Richards
+remm Remy Maucherat
+nrocher,noelrocher Noel Rocher
+ccrouch Charles Crouch
+sacha,slaboure Sacha Labourey
+bela,belaan Bela Ban
+jmoran Jim Moran
+gavin,oneovthafew Gavin King
+msurtani Manik Surtani
+sebersole,steveebersole Steve Ebersole
+smarlow Scott Marlow
+hbarlas Haroon Barlas
+rawb Robert Stryker
+flaviarnn Flavia Rainone
+cazzius Claudio Vesco
+russo,royrusso Roy Russo
+theute Thomas Heute
+mnf999,fleury Marc Fleury
+aveitas Algirdas Veitas
+deb Deborah Hooker
+karan_malhi Karan Singh
+pharaohh Les A. Hazlewood
+ricardoarguello Ricardo Arguello
+rauschuber Chris Rauschuber
+jhaynie Jeff Haynie
+vietj,cooperfbi Julien Viet
+richarzk Klaus Richarz
+chussenet Claude Hussenet
+aclute Andrew Clute
+juntao Juntao Yuan
+kevconner Kevin Conner
+mlavergn Marc Lavergne
+triathlon98 Joachim Van der Auwera
+ivelin Ivelin Atanasoff Ivanov
+kimptoc,kimptonc Chris Kimpton
+marshall_law,mculpepper Marshall Culpepper
+tpeuss Thomas Peuss
+essington Jason Essington
+posselt Dietmar Posselt
+juhalindfors,juha Juha Lindfors
+lqd Christian Riege
+scoy Stephen Coy
+cgjung Christoph Georg Jung
+rnjn5 Neil Dattani
+luke_t,negaton Luke Taylor
+sreich Stefan Reich
+thomasra Thomas Roka-Aardal
+mikefinn Mike Finn
+d_jencks David Jencks
+jules_gosnell Jules Gosnell
+dsundstrom Dain Sundstrom
+gregwilkins Greg Wilkins
+janb Jan Bartel
+eli201 Eli Tilevich
+harald_gliebe Harald Gliebe
+mnewcomb Michael Newcomb
+andygodwin Andy Godwin
+chirino,hiram Hiram Chirino
+user57 Jason Dillon
+nphelps Nathan W. Phelps
+sasp Spyridon Samothrakis
+igorfie Igor Fedorenko
+jboynes Jeremy Boynes
+kbirch Kevin Birch
+yanikc Yanik Crepeau
+alindsey Aaron Lindsey
+mclaugs Scott McLaughlin
+austinchau Austin Chau
+binaryfeed Jeffrey Wescott
+pra Peter Antman
+jcooley James Cooley
+gropi Tobias Frech
+mattmunz Matthew Munz
+stormy_sky,schaefera Andreas Schaefer
+peter_f Peter Fagerlund
+sparre,osh Ole Husgaard
+bartmann Michael Bartmann
+lsanders Larry Sanderson
+thesitesman Seth Sites
+azakkerman Anatoly Akkerman
+sgturner Greg Turner
+fbrier Frederick N. Brier
+biorn_steedom,simone Simone Bordet
+yarrumretep Peter M. Murray
+peterbraswell Peter Braswell
+jwalters Jay Walters
+danch Dan Christopherson
+fhanik Filip Hanik
+squirest Trevor Squires
+olegnitz,oleg Oleg Nitz
+neales Neale Swinnerton
+mikesr Mike Swainston-Rainford
+dbudworth David Budworth
+weave Brian Weaver
+vharcq Vincent Harcq
+dmaplesden David Maplesden
+boissier Guillaume Boissiere
+plevart Peter Levart
+thedug Doug Ferguson
+lepe,lennart Lennart Petersson
+charles_chan Charles Chan
+pkendall Paul Kendall
+vlada Vladimir Blagojevic
+rickardoberg,oberg Rickard Öberg
+jayeshpk Jayesh Parayali
+deerwood Georg Rehfeld
+tobyallsopp,allsopp Toby Allsopp
+kvvinaymenon KV Vinay Menon
+docodan Daniel OConnor
+stacycurl Stacy Curl
+phox Fulco Muriglio
+dmcnair Dewayne McNair
+vladimir Vladimir Ivanovic
+joel Joel Phillips
+
+-------------------------------------------------------------------------------
+* JBoss is a registered trademark of Red Hat Middleware LLC.
+
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/README-DTD.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/README-DTD.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/README-DTD.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,15 @@
+# $Id: README-DTD.txt 60564 2007-02-15 11:12:12Z dimitris at jboss.org $
+The following files contained within this folder are covered by license terms
+documented in docs/licenses/sun-specs.txt of the distribution.
+
+application_1_2.dtd
+application_1_3.dtd
+application-client_1_3.dtd
+connector_1_0.dtd
+ejb-jar.dtd
+ejb-jar_2_0.dtd
+web-app_2_2.dtd
+web-app_2_3.dtd
+
+More details on using these J2EE Schemas are available at:
+java.sun.com/xml/ns/j2ee/#usage
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/XMLSchema.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/XMLSchema.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/XMLSchema.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,402 @@
+<!-- DTD for XML Schemas: Part 1: Structures
+ Public Identifier: "-//W3C//DTD XMLSCHEMA 200102//EN"
+ Official Location: http://www.w3.org/2001/XMLSchema.dtd -->
+<!-- $Id: XMLSchema.dtd 20476 2004-04-17 13:29:24Z tdiesler $ -->
+<!-- Note this DTD is NOT normative, or even definitive. --> <!--d-->
+<!-- prose copy in the structures REC is the definitive version --> <!--d-->
+<!-- (which shouldn't differ from this one except for this --> <!--d-->
+<!-- comment and entity expansions, but just in case) --> <!--d-->
+<!-- With the exception of cases with multiple namespace
+ prefixes for the XML Schema namespace, any XML document which is
+ not valid per this DTD given redefinitions in its internal subset of the
+ 'p' and 's' parameter entities below appropriate to its namespace
+ declaration of the XML Schema namespace is almost certainly not
+ a valid schema. -->
+
+<!-- The simpleType element and its constituent parts
+ are defined in XML Schema: Part 2: Datatypes -->
+<!ENTITY % xs-datatypes PUBLIC 'datatypes' 'datatypes.dtd' >
+
+<!ENTITY % p 'xs:'> <!-- can be overriden in the internal subset of a
+ schema document to establish a different
+ namespace prefix -->
+<!ENTITY % s ':xs'> <!-- if %p is defined (e.g. as foo:) then you must
+ also define %s as the suffix for the appropriate
+ namespace declaration (e.g. :foo) -->
+<!ENTITY % nds 'xmlns%s;'>
+
+<!-- Define all the element names, with optional prefix -->
+<!ENTITY % schema "%p;schema">
+<!ENTITY % complexType "%p;complexType">
+<!ENTITY % complexContent "%p;complexContent">
+<!ENTITY % simpleContent "%p;simpleContent">
+<!ENTITY % extension "%p;extension">
+<!ENTITY % element "%p;element">
+<!ENTITY % unique "%p;unique">
+<!ENTITY % key "%p;key">
+<!ENTITY % keyref "%p;keyref">
+<!ENTITY % selector "%p;selector">
+<!ENTITY % field "%p;field">
+<!ENTITY % group "%p;group">
+<!ENTITY % all "%p;all">
+<!ENTITY % choice "%p;choice">
+<!ENTITY % sequence "%p;sequence">
+<!ENTITY % any "%p;any">
+<!ENTITY % anyAttribute "%p;anyAttribute">
+<!ENTITY % attribute "%p;attribute">
+<!ENTITY % attributeGroup "%p;attributeGroup">
+<!ENTITY % include "%p;include">
+<!ENTITY % import "%p;import">
+<!ENTITY % redefine "%p;redefine">
+<!ENTITY % notation "%p;notation">
+
+<!-- annotation elements -->
+<!ENTITY % annotation "%p;annotation">
+<!ENTITY % appinfo "%p;appinfo">
+<!ENTITY % documentation "%p;documentation">
+
+<!-- Customisation entities for the ATTLIST of each element type.
+ Define one of these if your schema takes advantage of the
+ anyAttribute='##other' in the schema for schemas -->
+
+<!ENTITY % schemaAttrs ''>
+<!ENTITY % complexTypeAttrs ''>
+<!ENTITY % complexContentAttrs ''>
+<!ENTITY % simpleContentAttrs ''>
+<!ENTITY % extensionAttrs ''>
+<!ENTITY % elementAttrs ''>
+<!ENTITY % groupAttrs ''>
+<!ENTITY % allAttrs ''>
+<!ENTITY % choiceAttrs ''>
+<!ENTITY % sequenceAttrs ''>
+<!ENTITY % anyAttrs ''>
+<!ENTITY % anyAttributeAttrs ''>
+<!ENTITY % attributeAttrs ''>
+<!ENTITY % attributeGroupAttrs ''>
+<!ENTITY % uniqueAttrs ''>
+<!ENTITY % keyAttrs ''>
+<!ENTITY % keyrefAttrs ''>
+<!ENTITY % selectorAttrs ''>
+<!ENTITY % fieldAttrs ''>
+<!ENTITY % includeAttrs ''>
+<!ENTITY % importAttrs ''>
+<!ENTITY % redefineAttrs ''>
+<!ENTITY % notationAttrs ''>
+<!ENTITY % annotationAttrs ''>
+<!ENTITY % appinfoAttrs ''>
+<!ENTITY % documentationAttrs ''>
+
+<!ENTITY % complexDerivationSet "CDATA">
+ <!-- #all or space-separated list drawn from derivationChoice -->
+<!ENTITY % blockSet "CDATA">
+ <!-- #all or space-separated list drawn from
+ derivationChoice + 'substitution' -->
+
+<!ENTITY % mgs '%all; | %choice; | %sequence;'>
+<!ENTITY % cs '%choice; | %sequence;'>
+<!ENTITY % formValues '(qualified|unqualified)'>
+
+
+<!ENTITY % attrDecls '((%attribute;| %attributeGroup;)*,(%anyAttribute;)?)'>
+
+<!ENTITY % particleAndAttrs '((%mgs; | %group;)?, %attrDecls;)'>
+
+<!-- This is used in part2 -->
+<!ENTITY % restriction1 '((%mgs; | %group;)?)'>
+
+%xs-datatypes;
+
+<!-- the duplication below is to produce an unambiguous content model
+ which allows annotation everywhere -->
+<!ELEMENT %schema; ((%include; | %import; | %redefine; | %annotation;)*,
+ ((%simpleType; | %complexType;
+ | %element; | %attribute;
+ | %attributeGroup; | %group;
+ | %notation; ),
+ (%annotation;)*)* )>
+<!ATTLIST %schema;
+ targetNamespace %URIref; #IMPLIED
+ version CDATA #IMPLIED
+ %nds; %URIref; #FIXED 'http://www.w3.org/2001/XMLSchema'
+ xmlns CDATA #IMPLIED
+ finalDefault %complexDerivationSet; ''
+ blockDefault %blockSet; ''
+ id ID #IMPLIED
+ elementFormDefault %formValues; 'unqualified'
+ attributeFormDefault %formValues; 'unqualified'
+ xml:lang CDATA #IMPLIED
+ %schemaAttrs;>
+<!-- Note the xmlns declaration is NOT in the Schema for Schemas,
+ because at the Infoset level where schemas operate,
+ xmlns(:prefix) is NOT an attribute! -->
+<!-- The declaration of xmlns is a convenience for schema authors -->
+
+<!-- The id attribute here and below is for use in external references
+ from non-schemas using simple fragment identifiers.
+ It is NOT used for schema-to-schema reference, internal or
+ external. -->
+
+<!-- a type is a named content type specification which allows attribute
+ declarations-->
+<!-- -->
+
+<!ELEMENT %complexType; ((%annotation;)?,
+ (%simpleContent;|%complexContent;|
+ %particleAndAttrs;))>
+
+<!ATTLIST %complexType;
+ name %NCName; #IMPLIED
+ id ID #IMPLIED
+ abstract %boolean; #IMPLIED
+ final %complexDerivationSet; #IMPLIED
+ block %complexDerivationSet; #IMPLIED
+ mixed (true|false) 'false'
+ %complexTypeAttrs;>
+
+<!-- particleAndAttrs is shorthand for a root type -->
+<!-- mixed is disallowed if simpleContent, overriden if complexContent
+ has one too. -->
+
+<!-- If anyAttribute appears in one or more referenced attributeGroups
+ and/or explicitly, the intersection of the permissions is used -->
+
+<!ELEMENT %complexContent; ((%annotation;)?, (%restriction;|%extension;))>
+<!ATTLIST %complexContent;
+ mixed (true|false) #IMPLIED
+ id ID #IMPLIED
+ %complexContentAttrs;>
+
+<!-- restriction should use the branch defined above, not the simple
+ one from part2; extension should use the full model -->
+
+<!ELEMENT %simpleContent; ((%annotation;)?, (%restriction;|%extension;))>
+<!ATTLIST %simpleContent;
+ id ID #IMPLIED
+ %simpleContentAttrs;>
+
+<!-- restriction should use the simple branch from part2, not the
+ one defined above; extension should have no particle -->
+
+<!ELEMENT %extension; ((%annotation;)?, (%particleAndAttrs;))>
+<!ATTLIST %extension;
+ base %QName; #REQUIRED
+ id ID #IMPLIED
+ %extensionAttrs;>
+
+<!-- an element is declared by either:
+ a name and a type (either nested or referenced via the type attribute)
+ or a ref to an existing element declaration -->
+
+<!ELEMENT %element; ((%annotation;)?, (%complexType;| %simpleType;)?,
+ (%unique; | %key; | %keyref;)*)>
+<!-- simpleType or complexType only if no type|ref attribute -->
+<!-- ref not allowed at top level -->
+<!ATTLIST %element;
+ name %NCName; #IMPLIED
+ id ID #IMPLIED
+ ref %QName; #IMPLIED
+ type %QName; #IMPLIED
+ minOccurs %nonNegativeInteger; #IMPLIED
+ maxOccurs CDATA #IMPLIED
+ nillable %boolean; #IMPLIED
+ substitutionGroup %QName; #IMPLIED
+ abstract %boolean; #IMPLIED
+ final %complexDerivationSet; #IMPLIED
+ block %blockSet; #IMPLIED
+ default CDATA #IMPLIED
+ fixed CDATA #IMPLIED
+ form %formValues; #IMPLIED
+ %elementAttrs;>
+<!-- type and ref are mutually exclusive.
+ name and ref are mutually exclusive, one is required -->
+<!-- In the absence of type AND ref, type defaults to type of
+ substitutionGroup, if any, else the ur-type, i.e. unconstrained -->
+<!-- default and fixed are mutually exclusive -->
+
+<!ELEMENT %group; ((%annotation;)?,(%mgs;)?)>
+<!ATTLIST %group;
+ name %NCName; #IMPLIED
+ ref %QName; #IMPLIED
+ minOccurs %nonNegativeInteger; #IMPLIED
+ maxOccurs CDATA #IMPLIED
+ id ID #IMPLIED
+ %groupAttrs;>
+
+<!ELEMENT %all; ((%annotation;)?, (%element;)*)>
+<!ATTLIST %all;
+ minOccurs (1) #IMPLIED
+ maxOccurs (1) #IMPLIED
+ id ID #IMPLIED
+ %allAttrs;>
+
+<!ELEMENT %choice; ((%annotation;)?, (%element;| %group;| %cs; | %any;)*)>
+<!ATTLIST %choice;
+ minOccurs %nonNegativeInteger; #IMPLIED
+ maxOccurs CDATA #IMPLIED
+ id ID #IMPLIED
+ %choiceAttrs;>
+
+<!ELEMENT %sequence; ((%annotation;)?, (%element;| %group;| %cs; | %any;)*)>
+<!ATTLIST %sequence;
+ minOccurs %nonNegativeInteger; #IMPLIED
+ maxOccurs CDATA #IMPLIED
+ id ID #IMPLIED
+ %sequenceAttrs;>
+
+<!-- an anonymous grouping in a model, or
+ a top-level named group definition, or a reference to same -->
+
+<!-- Note that if order is 'all', group is not allowed inside.
+ If order is 'all' THIS group must be alone (or referenced alone) at
+ the top level of a content model -->
+<!-- If order is 'all', minOccurs==maxOccurs==1 on element/any inside -->
+<!-- Should allow minOccurs=0 inside order='all' . . . -->
+
+<!ELEMENT %any; (%annotation;)?>
+<!ATTLIST %any;
+ namespace CDATA '##any'
+ processContents (skip|lax|strict) 'strict'
+ minOccurs %nonNegativeInteger; '1'
+ maxOccurs CDATA '1'
+ id ID #IMPLIED
+ %anyAttrs;>
+
+<!-- namespace is interpreted as follows:
+ ##any - - any non-conflicting WFXML at all
+
+ ##other - - any non-conflicting WFXML from namespace other
+ than targetNamespace
+
+ ##local - - any unqualified non-conflicting WFXML/attribute
+ one or - - any non-conflicting WFXML from
+ more URI the listed namespaces
+ references
+
+ ##targetNamespace ##local may appear in the above list,
+ with the obvious meaning -->
+
+<!ELEMENT %anyAttribute; (%annotation;)?>
+<!ATTLIST %anyAttribute;
+ namespace CDATA '##any'
+ processContents (skip|lax|strict) 'strict'
+ id ID #IMPLIED
+ %anyAttributeAttrs;>
+<!-- namespace is interpreted as for 'any' above -->
+
+<!-- simpleType only if no type|ref attribute -->
+<!-- ref not allowed at top level, name iff at top level -->
+<!ELEMENT %attribute; ((%annotation;)?, (%simpleType;)?)>
+<!ATTLIST %attribute;
+ name %NCName; #IMPLIED
+ id ID #IMPLIED
+ ref %QName; #IMPLIED
+ type %QName; #IMPLIED
+ use (prohibited|optional|required) #IMPLIED
+ default CDATA #IMPLIED
+ fixed CDATA #IMPLIED
+ form %formValues; #IMPLIED
+ %attributeAttrs;>
+<!-- type and ref are mutually exclusive.
+ name and ref are mutually exclusive, one is required -->
+<!-- default for use is optional when nested, none otherwise -->
+<!-- default and fixed are mutually exclusive -->
+<!-- type attr and simpleType content are mutually exclusive -->
+
+<!-- an attributeGroup is a named collection of attribute decls, or a
+ reference thereto -->
+<!ELEMENT %attributeGroup; ((%annotation;)?,
+ (%attribute; | %attributeGroup;)*,
+ (%anyAttribute;)?) >
+<!ATTLIST %attributeGroup;
+ name %NCName; #IMPLIED
+ id ID #IMPLIED
+ ref %QName; #IMPLIED
+ %attributeGroupAttrs;>
+
+<!-- ref iff no content, no name. ref iff not top level -->
+
+<!-- better reference mechanisms -->
+<!ELEMENT %unique; ((%annotation;)?, %selector;, (%field;)+)>
+<!ATTLIST %unique;
+ name %NCName; #REQUIRED
+ id ID #IMPLIED
+ %uniqueAttrs;>
+
+<!ELEMENT %key; ((%annotation;)?, %selector;, (%field;)+)>
+<!ATTLIST %key;
+ name %NCName; #REQUIRED
+ id ID #IMPLIED
+ %keyAttrs;>
+
+<!ELEMENT %keyref; ((%annotation;)?, %selector;, (%field;)+)>
+<!ATTLIST %keyref;
+ name %NCName; #REQUIRED
+ refer %QName; #REQUIRED
+ id ID #IMPLIED
+ %keyrefAttrs;>
+
+<!ELEMENT %selector; ((%annotation;)?)>
+<!ATTLIST %selector;
+ xpath %XPathExpr; #REQUIRED
+ id ID #IMPLIED
+ %selectorAttrs;>
+<!ELEMENT %field; ((%annotation;)?)>
+<!ATTLIST %field;
+ xpath %XPathExpr; #REQUIRED
+ id ID #IMPLIED
+ %fieldAttrs;>
+
+<!-- Schema combination mechanisms -->
+<!ELEMENT %include; (%annotation;)?>
+<!ATTLIST %include;
+ schemaLocation %URIref; #REQUIRED
+ id ID #IMPLIED
+ %includeAttrs;>
+
+<!ELEMENT %import; (%annotation;)?>
+<!ATTLIST %import;
+ namespace %URIref; #IMPLIED
+ schemaLocation %URIref; #IMPLIED
+ id ID #IMPLIED
+ %importAttrs;>
+
+<!ELEMENT %redefine; (%annotation; | %simpleType; | %complexType; |
+ %attributeGroup; | %group;)*>
+<!ATTLIST %redefine;
+ schemaLocation %URIref; #REQUIRED
+ id ID #IMPLIED
+ %redefineAttrs;>
+
+<!ELEMENT %notation; (%annotation;)?>
+<!ATTLIST %notation;
+ name %NCName; #REQUIRED
+ id ID #IMPLIED
+ public CDATA #REQUIRED
+ system %URIref; #IMPLIED
+ %notationAttrs;>
+
+<!-- Annotation is either application information or documentation -->
+<!-- By having these here they are available for datatypes as well
+ as all the structures elements -->
+
+<!ELEMENT %annotation; (%appinfo; | %documentation;)*>
+<!ATTLIST %annotation; %annotationAttrs;>
+
+<!-- User must define annotation elements in internal subset for this
+ to work -->
+<!ELEMENT %appinfo; ANY> <!-- too restrictive -->
+<!ATTLIST %appinfo;
+ source %URIref; #IMPLIED
+ id ID #IMPLIED
+ %appinfoAttrs;>
+<!ELEMENT %documentation; ANY> <!-- too restrictive -->
+<!ATTLIST %documentation;
+ source %URIref; #IMPLIED
+ id ID #IMPLIED
+ xml:lang CDATA #IMPLIED
+ %documentationAttrs;>
+
+<!NOTATION XMLSchemaStructures PUBLIC
+ 'structures' 'http://www.w3.org/2001/XMLSchema.xsd' >
+<!NOTATION XML PUBLIC
+ 'REC-xml-1998-0210' 'http://www.w3.org/TR/1998/REC-xml-19980210' >
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application-client_1_3.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application-client_1_3.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application-client_1_3.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,506 @@
+<!--
+Copyright (c) 2000 Sun Microsystems, Inc.,
+901 San Antonio Road,
+Palo Alto, California 94303, U.S.A.
+All rights reserved.
+
+Sun Microsystems, Inc. has intellectual property rights relating to
+technology embodied in the product that is described in this document.
+In particular, and without limitation, these intellectual property
+rights may include one or more of the U.S. patents listed at
+http://www.sun.com/patents and one or more additional patents or
+pending patent applications in the U.S. and in other countries.
+
+This document and the product to which it pertains are distributed
+under licenses restricting their use, copying, distribution, and
+decompilation. This document may be reproduced and distributed but may
+not be changed without prior written authorization of Sun and its
+licensors, if any.
+
+Third-party software, including font technology, is copyrighted and
+licensed from Sun suppliers.
+
+Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail and and
+Enterprise JavaBeans are trademarks or registered trademarks of Sun
+Microsystems, Inc. in the U.S. and other countries.
+
+Federal Acquisitions: Commercial Software - Government Users Subject to
+Standard License Terms and Conditions.
+
+DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
+CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
+WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
+NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
+DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
+
+
+_________________________________________________________________________
+
+Copyright (c) 2000 Sun Microsystems, Inc.,
+901 San Antonio Road,
+Palo Alto, California 94303, E'tats-Unis.
+Tous droits re'serve's.
+
+Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
+relatants a` la technologie incorpore'e dans le produit qui est de'crit
+dans ce document. En particulier, et sans la limitation, ces droits de
+proprie'te' intellectuels peuvent inclure un ou plus des brevets
+ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
+brevets plus supple'mentaires ou les applications de brevet en attente
+dans les E'tats-Unis et dans les autres pays.
+
+Ce produit ou document est prote'ge' par un copyright et distribue'
+avec des licences qui en restreignent l'utilisation, la copie, la
+distribution, et la de'compilation. Ce documention associe n peut
+e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
+l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
+licence, le cas e'che'ant.
+
+Le logiciel de'tenu par des tiers, et qui comprend la technologie
+relative aux polices de caracte`res, est prote'ge' par un copyright et
+licencie' par des fournisseurs de Sun.
+
+Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail et and
+Enterprise JavaBeans sont des marques de fabrique ou des marques
+de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
+pays.
+
+LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
+DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
+EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
+NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
+L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
+CONTREFAC,ON.
+-->
+
+<!--
+This is the XML DTD for the J2EE 1.3 application client deployment
+descriptor. All J2EE 1.3 application client deployment descriptors
+must include a DOCTYPE of the following form:
+
+ <!DOCTYPE application-client PUBLIC
+ "-//Sun Microsystems, Inc.//DTD J2EE Application Client 1.3//EN"
+ "http://java.sun.com/dtd/application-client_1_3.dtd">
+
+-->
+
+<!--
+The following conventions apply to all J2EE deployment descriptor
+elements unless indicated otherwise.
+
+- In elements that contain PCDATA, leading and trailing whitespace
+ in the data may be ignored.
+
+- In elements whose value is an "enumerated type", the value is
+ case sensitive.
+
+- In elements that specify a pathname to a file within the same
+ JAR file, relative filenames (i.e., those not starting with "/")
+ are considered relative to the root of the JAR file's namespace.
+ Absolute filenames (i.e., those starting with "/") also specify
+ names in the root of the JAR file's namespace. In general, relative
+ names are preferred. The exception is .war files where absolute
+ names are preferred for consistency with the servlet API.
+-->
+
+
+<!--
+The application-client element is the root element of an application
+client deployment descriptor. The application client deployment
+descriptor describes the EJB components and external resources
+referenced by the application client.
+-->
+<!ELEMENT application-client (icon?, display-name, description?,
+ env-entry*, ejb-ref*, resource-ref*, resource-env-ref*,
+ callback-handler?)>
+
+<!--
+The callback-handler element names a class provided by the
+application. The class must have a no args constructor and must
+implement the javax.security.auth.callback.CallbackHandler interface.
+The class will be instantiated by the application client container and
+used by the container to collect authentication information from the
+user.
+
+Used in: application-client
+-->
+<!ELEMENT callback-handler (#PCDATA)>
+
+<!--
+The description element is used to provide text describing the parent
+element. The description element should include any information that
+the application client jar file producer wants to provide to the consumer of
+the application client jar file (i.e., to the Deployer). Typically, the tools
+used by the application client jar file consumer will display the description
+when processing the parent element that contains the description.
+
+Used in: application-client, ejb-ref, env-entry, resource-env-ref,
+resource-ref
+-->
+<!ELEMENT description (#PCDATA)>
+
+<!--
+The display-name element contains a short name that is intended to be
+displayed by tools. The display name need not be unique.
+
+Used in: application-client
+
+Example:
+
+<display-name>Employee Self Service</display-name>
+-->
+<!ELEMENT display-name (#PCDATA)>
+
+<!--
+The ejb-link element is used in the ejb-ref element
+to specify that an EJB reference is linked to an
+enterprise bean.
+
+The name in the ejb-link element is composed of a
+path name specifying the ejb-jar containing the referenced enterprise
+bean with the ejb-name of the target bean appended and separated from
+the path name by "#". The path name is relative to the jar file
+containing the application client that is referencing the enterprise bean.
+This allows multiple enterprise beans with the same ejb-name to be
+uniquely identified.
+
+Used in: ejb-ref
+
+Examples:
+
+ <ejb-link>EmployeeRecord</ejb-link>
+
+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
+
+-->
+<!ELEMENT ejb-link (#PCDATA)>
+
+<!--
+The ejb-ref element is used for the declaration of a reference to
+an enterprise bean's home. The declaration consists of:
+
+ - an optional description
+ - the EJB reference name used in the code of
+ the application client that's referencing the enterprise bean
+ - the expected type of the referenced enterprise bean
+ - the expected home and remote interfaces of the referenced
+ enterprise bean
+ - optional ejb-link information, used to specify the referenced
+ enterprise bean
+
+Used in: application-client
+-->
+<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type,
+ home, remote, ejb-link?)>
+
+<!--
+The ejb-ref-name element contains the name of an EJB reference. The
+EJB reference is an entry in the application client's environment and is
+relative to the java:comp/env context. The name must be unique
+within the application client.
+
+It is recommended that name is prefixed with "ejb/".
+
+Used in: ejb-ref
+
+Example:
+
+<ejb-ref-name>ejb/Payroll</ejb-ref-name>
+-->
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+<!--
+The ejb-ref-type element contains the expected type of the
+referenced enterprise bean.
+
+The ejb-ref-type element must be one of the following:
+
+ <ejb-ref-type>Entity</ejb-ref-type>
+ <ejb-ref-type>Session</ejb-ref-type>
+
+Used in: ejb-ref
+-->
+<!ELEMENT ejb-ref-type (#PCDATA)>
+
+<!--
+The env-entry element contains the declaration of an application client's
+environment entry. The declaration consists of an optional
+description, the name of the environment entry, and an optional
+value. If a value is not specified, one must be supplied
+during deployment.
+
+Used in: application-client
+-->
+<!ELEMENT env-entry (description?, env-entry-name, env-entry-type,
+ env-entry-value?)>
+
+<!--
+The env-entry-name element contains the name of an application client's
+environment entry. The name is a JNDI name relative to the
+java:comp/env context. The name must be unique within an application client.
+
+Used in: env-entry
+
+Example:
+
+<env-entry-name>minAmount</env-entry-name>
+-->
+<!ELEMENT env-entry-name (#PCDATA)>
+
+<!--
+The env-entry-type element contains the fully-qualified Java type of
+the environment entry value that is expected by the application client's
+code.
+
+The following are the legal values of env-entry-type:
+
+ java.lang.Boolean
+ java.lang.Byte
+ java.lang.Character
+ java.lang.String
+ java.lang.Short
+ java.lang.Integer
+ java.lang.Long
+ java.lang.Float
+ java.lang.Double
+
+
+Used in: env-entry
+
+Example:
+
+<env-entry-type>java.lang.Boolean</env-entry-type>
+-->
+<!ELEMENT env-entry-type (#PCDATA)>
+
+<!--
+The env-entry-value element contains the value of an application client's
+environment entry. The value must be a String that is valid for the
+constructor of the specified type that takes a single String
+parameter, or for java.lang.Character, a single character.
+
+Used in: env-entry
+
+Example:
+
+<env-entry-value>100.00</env-entry-value>
+-->
+<!ELEMENT env-entry-value (#PCDATA)>
+
+<!--
+The home element contains the fully-qualified name of the enterprise
+bean's home interface.
+
+Used in: ejb-ref
+
+Example:
+
+<home>com.aardvark.payroll.PayrollHome</home>
+-->
+<!ELEMENT home (#PCDATA)>
+
+<!--
+The icon element contains small-icon and large-icon elements that
+specify the file names for small and a large GIF or JPEG icon images
+used to represent the parent element in a GUI tool.
+
+Used in: application-client
+-->
+<!ELEMENT icon (small-icon?, large-icon?)>
+
+<!--
+The large-icon element contains the name of a file
+containing a large (32 x 32) icon image. The file
+name is a relative path within the application client's
+jar file.
+
+The image may be either in the JPEG or GIF format.
+The icon can be used by tools.
+
+Used in: icon
+
+Example:
+
+<large-icon>employee-service-icon32x32.jpg</large-icon>
+-->
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+The remote element contains the fully-qualified name of the enterprise
+bean's remote interface.
+
+Used in: ejb-ref
+
+Example:
+
+<remote>com.wombat.empl.EmployeeService</remote>
+-->
+<!ELEMENT remote (#PCDATA)>
+
+<!--
+The res-auth element specifies whether the application client code signs
+on programmatically to the resource manager, or whether the Container
+will sign on to the resource manager on behalf of the application client. In the
+latter case, the Container uses information that is supplied by the
+Deployer.
+
+The value of this element must be one of the two following:
+
+ <res-auth>Application</res-auth>
+ <res-auth>Container</res-auth>
+
+Used in: resource-ref
+-->
+<!ELEMENT res-auth (#PCDATA)>
+
+<!--
+The res-ref-name element specifies the name of a resource manager
+connection factory reference. The name is a JNDI name relative to the
+java:comp/env context. The name must be unique within an application client.
+
+Used in: resource-ref
+-->
+<!ELEMENT res-ref-name (#PCDATA)>
+
+<!--
+The res-sharing-scope element specifies whether connections obtained
+through the given resource manager connection factory reference can be
+shared. The value of this element, if specified, must be one of the
+two following:
+
+ <res-sharing-scope>Shareable</res-sharing-scope>
+ <res-sharing-scope>Unshareable</res-sharing-scope>
+
+The default value is Shareable.
+
+Used in: resource-ref
+-->
+<!ELEMENT res-sharing-scope (#PCDATA)>
+
+<!--
+The res-type element specifies the type of the data source. The type
+is specified by the fully qualified Java language class or interface
+expected to be implemented by the data source.
+
+Used in: resource-ref
+-->
+<!ELEMENT res-type (#PCDATA)>
+
+<!--
+The resource-env-ref element contains a declaration of an application client's
+reference to an administered object associated with a resource
+in the application client's environment. It consists of an optional
+description, the resource environment reference name, and an
+indication of the resource environment reference type expected by
+the application client code.
+
+Used in: application-client
+
+Example:
+
+<resource-env-ref>
+ <resource-env-ref-name>jms/StockQueue</resource-env-ref-name>
+ <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
+</resource-env-ref>
+-->
+<!ELEMENT resource-env-ref (description?, resource-env-ref-name,
+ resource-env-ref-type)>
+
+<!--
+The resource-env-ref-name element specifies the name of a resource
+environment reference; its value is the environment entry name used in
+the application client code. The name is a JNDI name relative to the
+java:comp/env context and must be unique within an application client.
+
+Used in: resource-env-ref
+-->
+<!ELEMENT resource-env-ref-name (#PCDATA)>
+
+<!--
+The resource-env-ref-type element specifies the type of a resource
+environment reference. It is the fully qualified name of a Java
+language class or interface.
+
+Used in: resource-env-ref
+-->
+<!ELEMENT resource-env-ref-type (#PCDATA)>
+
+<!--
+The resource-ref element contains a declaration of an application client's
+reference to an external resource. It consists of an optional
+description, the resource manager connection factory reference name,
+the indication of the resource manager connection factory type
+expected by the application client code, the type of authentication
+(Application or Container), and an optional specification of the
+shareability of connections obtained from the resource (Shareable or
+Unshareable).
+
+Used in: application-client
+
+Example:
+
+ <resource-ref>
+ <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
+ <res-type>javax.sql.DataSource</res-type>
+ <res-auth>Container</res-auth>
+ <res-sharing-scope>Shareable</res-sharing-scope>
+ </resource-ref>
+-->
+<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth,
+ res-sharing-scope?)>
+
+<!--
+The small-icon element contains the name of a file
+containing a small (16 x 16) icon image. The file
+name is a relative path within the application client's
+jar file.
+
+The image may be either in the JPEG or GIF format.
+The icon can be used by tools.
+
+Used in: icon
+
+Example:
+
+<small-icon>employee-service-icon16x16.jpg</small-icon>
+-->
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+The ID mechanism is to allow tools that produce additional deployment
+information (i.e., information beyond the standard deployment
+descriptor information) to store the non-standard information in a
+separate file, and easily refer from these tool-specific files to the
+information in the standard deployment descriptor.
+
+Tools are not allowed to add the non-standard information into the
+standard deployment descriptor.
+-->
+
+<!ATTLIST application-client id ID #IMPLIED>
+<!ATTLIST callback-handler id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST ejb-link id ID #IMPLIED>
+<!ATTLIST ejb-ref id ID #IMPLIED>
+<!ATTLIST ejb-ref-name id ID #IMPLIED>
+<!ATTLIST ejb-ref-type id ID #IMPLIED>
+<!ATTLIST env-entry id ID #IMPLIED>
+<!ATTLIST env-entry-name id ID #IMPLIED>
+<!ATTLIST env-entry-type id ID #IMPLIED>
+<!ATTLIST env-entry-value id ID #IMPLIED>
+<!ATTLIST home id ID #IMPLIED>
+<!ATTLIST icon id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST remote id ID #IMPLIED>
+<!ATTLIST res-auth id ID #IMPLIED>
+<!ATTLIST res-ref-name id ID #IMPLIED>
+<!ATTLIST res-sharing-scope id ID #IMPLIED>
+<!ATTLIST res-type id ID #IMPLIED>
+<!ATTLIST resource-env-ref id ID #IMPLIED>
+<!ATTLIST resource-env-ref-name id ID #IMPLIED>
+<!ATTLIST resource-env-ref-type id ID #IMPLIED>
+<!ATTLIST resource-ref id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application_1_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application_1_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application_1_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,197 @@
+<!--
+Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road,
+Palo Alto, CA 94303, U.S.A. All rights reserved.
+
+This product or document is protected by copyright and distributed
+under licenses restricting its use, copying, distribution, and
+decompilation. No part of this product or documentation may be
+reproduced in any form by any means without prior written authorization
+of Sun and its licensors, if any.
+
+Third party software, including font technology, is copyrighted and
+licensed from Sun suppliers.
+
+Sun, Sun Microsystems, the Sun Logo, Solaris, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans,
+are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S.
+and other countries.
+
+All SPARC trademarks are used under license and are trademarks
+or registered trademarks of SPARC International, Inc.
+in the U.S. and other countries. Products bearing SPARC
+trademarks are based upon an architecture developed by Sun Microsystems, Inc.
+
+PostScript is a registered trademark of Adobe Systems, Inc.
+
+
+Federal Acquisitions: Commercial Software - Government Users Subject to
+Standard License Terms and Conditions.
+
+
+
+DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
+CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
+IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
+PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT
+TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY
+INVALID.
+
+_________________________________________________________________________
+Copyright 1999 Sun Microsystems, Inc.,
+901 San Antonio Road, Palo Alto, CA 94303, Etats-Unis.
+Tous droits re'serve's.
+
+
+Ce produit ou document est prote'ge' par un copyright et distribue' avec
+des licences qui en restreignent l'utilisation, la copie, la distribution,
+et la de'compilation. Aucune partie de ce produit ou de sa documentation
+associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen
+que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses
+bailleurs de licence, s'il y en a.
+
+Le logiciel de'tenu par des tiers, et qui comprend la technologie
+relative aux polices de caracte`res, est prote'ge' par un copyright
+et licencie' par des fournisseurs de Sun.
+
+Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans,
+sont des marques de fabrique ou des marques de'pose'es de Sun
+Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
+
+Toutes les marques SPARC sont utilise'es sous licence et sont
+des marques de fabrique ou des marques de'pose'es de SPARC
+International, Inc. aux Etats-Unis et dans
+d'autres pays. Les produits portant les marques SPARC sont
+base's sur une architecture de'veloppe'e par Sun Microsystems, Inc.
+
+Postcript est une marque enregistre'e d'Adobe Systems Inc.
+
+LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS,
+DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES,
+DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT
+TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE
+A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.
+-->
+
+<!--
+The alt-dd element specifies an optional URI to the post-assembly version of the
+deployment descriptor file for a particular J2EE module. The URI must specify
+the full pathname of the deployment descriptor file relative to the
+application's root directory. If alt-dd is not specified, the deployer must read
+the deployment descriptor from the default location and file name required by
+the respective component specification.
+-->
+<!ELEMENT alt-dd (#PCDATA)>
+
+<!--
+The application element is the root element of a J2EE application deployment
+descriptor.
+-->
+<!ELEMENT application (icon?, display-name, description?, module+,
+security-role*)>
+
+<!--
+The context-root element specifies the context root of a web application
+-->
+<!ELEMENT context-root (#PCDATA)>
+
+<!--
+The description element provides a human readable description of the
+application. The description element should include any information that the
+application assembler wants to provide the deployer.
+-->
+<!ELEMENT description (#PCDATA)>
+
+<!--
+The display-name element specifies an application name.
+The application name is assigned to the application by the application assembler
+and is used to identify the application to the deployer at deployment time.
+-->
+<!ELEMENT display-name (#PCDATA)>
+
+<!--
+The ejb element specifies the URI of a ejb-jar, relative to the top level of the
+application package.
+-->
+<!ELEMENT ejb (#PCDATA)>
+
+<!--
+The icon element contains a small-icon and large-icon element which specify the
+URIs for a small and a large GIF or JPEG icon image to represent the application
+in a GUI.
+-->
+<!ELEMENT icon (small-icon?, large-icon?)>
+
+<!--
+The java element specifies the URI of a java application client module, relative
+to the top level of the application package.
+-->
+<!ELEMENT java (#PCDATA)>
+
+<!--
+The large-icon element specifies the URI for a large GIF or JPEG icon image to
+represent the application in a GUI.
+-->
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+The module element represents a single J2EE module and contains an ejb, java, or
+web element, which indicates the module type and contains a path to the module
+file, and an optional alt-dd element, which specifies an optional URI to the
+post-assembly version of the deployment descriptor.
+The application deployment descriptor must have one module element for each J2EE
+module in the application package.
+-->
+<!ELEMENT module ((ejb | java | web), alt-dd?)>
+
+<!--
+The role-name element contains the name of a security role.
+-->
+<!ELEMENT role-name (#PCDATA)>
+
+<!--
+The security-role element contains the definition of a security role which is
+global to the application. The definition consists of a description of the
+security role, and the security role name. The descriptions at this level
+override those in the component level security-role definitions and must be the
+descriptions tool display to the deployer.
+-->
+<!ELEMENT security-role (description?, role-name)>
+
+<!--
+The small-icon element specifies the URI for a small GIF or JPEG icon image to
+represent the application in a GUI.
+-->
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+The web element contains the web-uri and context-root of a web application
+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.
+-->
+<!ELEMENT web-uri (#PCDATA)>
+
+<!--
+The ID mechanism is to allow tools to easily make tool-specific references to
+the elements of the deployment descriptor.
+ -->
+<!ATTLIST alt-dd id ID #IMPLIED>
+<!ATTLIST application id ID #IMPLIED>
+<!ATTLIST context-root id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST ejb id ID #IMPLIED>
+<!ATTLIST icon id ID #IMPLIED>
+<!ATTLIST java id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST module id ID #IMPLIED>
+<!ATTLIST role-name id ID #IMPLIED>
+<!ATTLIST security-role id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
+<!ATTLIST web id ID #IMPLIED>
+<!ATTLIST web-uri id ID #IMPLIED>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application_1_3.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application_1_3.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/application_1_3.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,312 @@
+<!--
+Copyright (c) 2000 Sun Microsystems, Inc.,
+901 San Antonio Road,
+Palo Alto, California 94303, U.S.A.
+All rights reserved.
+
+Sun Microsystems, Inc. has intellectual property rights relating to
+technology embodied in the product that is described in this document.
+In particular, and without limitation, these intellectual property
+rights may include one or more of the U.S. patents listed at
+http://www.sun.com/patents and one or more additional patents or
+pending patent applications in the U.S. and in other countries.
+
+This document and the product to which it pertains are distributed
+under licenses restricting their use, copying, distribution, and
+decompilation. This document may be reproduced and distributed but may
+not be changed without prior written authorization of Sun and its
+licensors, if any.
+
+Third-party software, including font technology, is copyrighted and
+licensed from Sun suppliers.
+
+Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail and and
+Enterprise JavaBeans are trademarks or registered trademarks of Sun
+Microsystems, Inc. in the U.S. and other countries.
+
+Federal Acquisitions: Commercial Software - Government Users Subject to
+Standard License Terms and Conditions.
+
+DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
+CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
+WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
+NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
+DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
+
+
+_________________________________________________________________________
+
+Copyright (c) 2000 Sun Microsystems, Inc.,
+901 San Antonio Road,
+Palo Alto, California 94303, E'tats-Unis.
+Tous droits re'serve's.
+
+Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
+relatants a` la technologie incorpore'e dans le produit qui est de'crit
+dans ce document. En particulier, et sans la limitation, ces droits de
+proprie'te' intellectuels peuvent inclure un ou plus des brevets
+ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
+brevets plus supple'mentaires ou les applications de brevet en attente
+dans les E'tats-Unis et dans les autres pays.
+
+Ce produit ou document est prote'ge' par un copyright et distribue'
+avec des licences qui en restreignent l'utilisation, la copie, la
+distribution, et la de'compilation. Ce documention associe n peut
+e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
+l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
+licence, le cas e'che'ant.
+
+Le logiciel de'tenu par des tiers, et qui comprend la technologie
+relative aux polices de caracte`res, est prote'ge' par un copyright et
+licencie' par des fournisseurs de Sun.
+
+Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail et and
+Enterprise JavaBeans sont des marques de fabrique ou des marques
+de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
+pays.
+
+LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
+DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
+EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
+NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
+L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
+CONTREFAC,ON.
+-->
+
+<!--
+This is the XML DTD for the J2EE 1.3 application deployment
+descriptor. All J2EE 1.3 application deployment descriptors
+must include a DOCTYPE of the following form:
+
+ <!DOCTYPE application PUBLIC
+ "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
+ "http://java.sun.com/dtd/application_1_3.dtd">
+
+-->
+
+<!--
+The following conventions apply to all J2EE deployment descriptor
+elements unless indicated otherwise.
+
+- In elements that contain PCDATA, leading and trailing whitespace
+ in the data may be ignored.
+
+- In elements whose value is an "enumerated type", the value is
+ case sensitive.
+
+- In elements that specify a pathname to a file within the same
+ JAR file, relative filenames (i.e., those not starting with "/")
+ are considered relative to the root of the JAR file's namespace.
+ Absolute filenames (i.e., those starting with "/") also specify
+ names in the root of the JAR file's namespace. In general, relative
+ names are preferred. The exception is .war files where absolute
+ names are preferred for consistency with the servlet API.
+-->
+
+
+<!--
+The application element is the root element of a J2EE application
+deployment descriptor.
+-->
+<!ELEMENT application (icon?, display-name, description?, module+,
+ security-role*)>
+
+<!--
+The alt-dd element specifies an optional URI to the post-assembly
+version of the deployment descriptor file for a particular J2EE module.
+The URI must specify the full pathname of the deployment descriptor
+file relative to the application's root directory. If alt-dd is not
+specified, the deployer must read the deployment descriptor from the
+default location and file name required by the respective component
+specification.
+
+Used in: module
+-->
+<!ELEMENT alt-dd (#PCDATA)>
+
+<!--
+The connector element specifies the URI of a resource adapter archive
+file, relative to the top level of the application package.
+
+Used in: module
+-->
+<!ELEMENT connector (#PCDATA)>
+
+<!--
+The context-root element specifies the context root of a web
+application.
+
+Used in: web
+-->
+<!ELEMENT context-root (#PCDATA)>
+
+<!--
+The description element is used to provide text describing the parent
+element. The description element should include any information that
+the application ear file producer wants to provide to the consumer of
+the application ear file (i.e., to the Deployer). Typically, the tools
+used by the application ear file consumer will display the description
+when processing the parent element that contains the description.
+
+Used in: application, security-role
+-->
+<!ELEMENT description (#PCDATA)>
+
+<!--
+The display-name element contains a short name that is intended to be
+displayed by tools. The display name need not be unique.
+
+Used in: application
+
+Example:
+
+<display-name>Employee Self Service</display-name>
+-->
+<!ELEMENT display-name (#PCDATA)>
+
+<!--
+The ejb element specifies the URI of an ejb-jar, relative to the top
+level of the application package.
+
+Used in: module
+-->
+<!ELEMENT ejb (#PCDATA)>
+
+<!--
+The icon element contains small-icon and large-icon elements that
+specify the file names for small and a large GIF or JPEG icon images
+used to represent the parent element in a GUI tool.
+
+Used in: application
+-->
+<!ELEMENT icon (small-icon?, large-icon?)>
+
+<!--
+The java element specifies the URI of a java application client module,
+relative to the top level of the application package.
+
+Used in: module
+-->
+<!ELEMENT java (#PCDATA)>
+
+<!--
+The large-icon element contains the name of a file
+containing a large (32 x 32) icon image. The file
+name is a relative path within the application's
+ear file.
+
+The image may be either in the JPEG or GIF format.
+The icon can be used by tools.
+
+Used in: icon
+
+Example:
+
+<large-icon>employee-service-icon32x32.jpg</large-icon>
+-->
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+The module element represents a single J2EE module and contains a
+connector, ejb, java, or web element, which indicates the module type
+and contains a path to the module file, and an optional alt-dd element,
+which specifies an optional URI to the post-assembly version of the
+deployment descriptor.
+
+The application deployment descriptor must have one module element for
+each J2EE module in the application package.
+
+Used in: application
+-->
+<!ELEMENT module ((connector | ejb | java | web), alt-dd?)>
+
+<!--
+The role-name element contains the name of a security role.
+
+The name must conform to the lexical rules for an NMTOKEN.
+
+Used in: security-role
+-->
+<!ELEMENT role-name (#PCDATA)>
+
+<!--
+The security-role element contains the definition of a security
+role. The definition consists of an optional description of the
+security role, and the security role name.
+
+Used in: application
+
+Example:
+
+ <security-role>
+ <description>
+ This role includes all employees who are authorized
+ to access the employee service application.
+ </description>
+ <role-name>employee</role-name>
+ </security-role>
+-->
+<!ELEMENT security-role (description?, role-name)>
+
+<!--
+The small-icon element contains the name of a file
+containing a small (16 x 16) icon image. The file
+name is a relative path within the application's
+ear file.
+
+The image may be either in the JPEG or GIF format.
+The icon can be used by tools.
+
+Used in: icon
+
+Example:
+
+<small-icon>employee-service-icon16x16.jpg</small-icon>
+-->
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+The web element contains the web-uri and context-root of a web
+application module.
+
+Used in: 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 ID mechanism is to allow tools that produce additional deployment
+information (i.e., information beyond the standard deployment
+descriptor information) to store the non-standard information in a
+separate file, and easily refer from these tool-specific files to the
+information in the standard deployment descriptor.
+
+Tools are not allowed to add the non-standard information into the
+standard deployment descriptor.
+-->
+
+<!ATTLIST alt-dd id ID #IMPLIED>
+<!ATTLIST application id ID #IMPLIED>
+<!ATTLIST connector id ID #IMPLIED>
+<!ATTLIST context-root id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST ejb id ID #IMPLIED>
+<!ATTLIST icon id ID #IMPLIED>
+<!ATTLIST java id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST module id ID #IMPLIED>
+<!ATTLIST role-name id ID #IMPLIED>
+<!ATTLIST security-role id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
+<!ATTLIST web id ID #IMPLIED>
+<!ATTLIST web-uri id ID #IMPLIED>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/connector_1_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/connector_1_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/connector_1_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,468 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!--
+LONG NOTICE:
+
+English:
+Copyright © 2000 Sun Microsystems, Inc., 901 San Antonio Road, Palo
+Alto, California 94303, U.S.A. All rights reserved.
+
+Sun Microsystems, Inc. has intellectual property rights relating to
+technology embodied in the product that is described in this document.
+In particular, and without limitation, these intellectual property
+rights may include one or more of the U.S. patents listed at
+http://www.sun.com/patents and one or more additional patents or pending
+patent applications in the U.S. and in other countries.
+
+This document and the product to which it pertains are distributed under
+licenses restricting their use, copying, distribution, and
+decompilation. This Product or document may be reproduced but may not be
+changed without prior written authorization of Sun and its licensors, if
+any.
+
+Third-party software, including font technology, is copyrighted and
+licensed from Sun suppliers.
+
+Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail and and
+Enterprise JavaBeans are trademarks or registered trademarks of Sun
+Microsystems, Inc. in the U.S. and other countries.
+
+
+
+Federal Acquisitions: Commercial Software - Government Users Subject to
+Standard License Terms and Conditions.
+
+DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
+REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
+MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
+NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
+DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
+
+French:
+Copyright © 2000 Sun Microsystems, Inc., 901 San Antonio Road, Palo
+Alto, California 94303, États-Unis. Tous droits réservés.
+
+Sun Microsystems, Inc. a les droits de propriété intellectuels
+relatants à la technologie incorporée dans le produit qui est
+décrit dans ce document. En particulier, et sans la limitation, ces
+droits de propriété intellectuels peuvent inclure un ou plus des
+brevets américains énumérés à http://www.sun.com/patents
+et un ou les brevets plus supplémentaires ou les applications de
+brevet en attente dans les États - Unis et dans les autres pays.
+
+Ce produit ou document est protégé par un copyright et
+distribué avec des licences qui en restreignent l'utilisation, la
+copie, la distribution, et la décompilation. Ce produit sa
+documention associe n peut être reproduite, par quelque moyen que ce
+soit, sans l'autorisation préalable et écrite de Sun et de ses
+bailleurs de licence, le cas échéant.
+
+Le logiciel détenu par des tiers, et qui comprend la technologie
+relative aux polices de caractères, est protégé par un
+copyright et licencié par des fournisseurs de Sun.
+
+Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail et and
+Enterprise JavaBeans sont des marques de fabrique ou des marques
+déposées de Sun Microsystems, Inc. aux États-Unis et dans
+d'autres pays.
+
+
+
+LA DOCUMENTATION EST FOURNIE "EN L'ÉTAT" ET TOUTES AUTRES CONDITIONS,
+DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
+EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
+NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
+L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
+CONTREFAÇON.
+-->
+
+<!--
+XML DTD for Resource Adapter deployment Descriptor 1.0
+-->
+
+<!--
+The connector element is the root element of the deployment descriptor
+for the resource adapter. This element includes general information - vendor
+name, version, specification version supported, icon - about the
+resource adapter module. It also includes information specific to the
+implementation of the resource adapter library as specified through
+the element resourceadapter.
+-->
+<!ELEMENT connector (display-name, description?, icon?, vendor-name,
+spec-version, eis-type, version, license?, resourceadapter)>
+
+<!--
+The element resourceadapter specifies information about the resource
+adapter. The information includes fully-qualified names of
+class/interfaces required as part of the connector architecture
+specified contracts, level of transaction support provided,
+configurable properties for ManagedConnectionFactory instances,
+one or more authentication mechanisms supported and additional
+required security permissions.
+
+If there is no authentication-mechanism specified as part of resource adapter
+element then the resource adapter does not support any standard
+security authentication mechanisms as part of security contract.
+The application server ignores the security part of the system
+contracts in this case.
+-->
+
+<!ELEMENT resourceadapter (
+managedconnectionfactory-class, connectionfactory-interface,
+connectionfactory-impl-class, connection-interface,
+connection-impl-class, transaction-support, config-property*,
+authentication-mechanism*, reauthentication-support, security-permission*
+)>
+
+<!--
+The element authentication-mechanism specifies an authentication mechanism
+supported by the resource adapter. Note that this support is for
+the resource adapter and not for the underlying EIS instance. The
+optional description specifies any resource adapter specific requirement
+for the support of security contract and authentication mechanism.
+
+Note that BasicPassword mech-type should support the
+javax.resource.spi.security.PasswordCredential interface. The Kerbv5
+mech-type should support the javax.resource.spi.security.Generic-
+Credential interface.
+-->
+<!ELEMENT authentication-mechanism (description?, authentication-mechanism-type, credential-interface)>
+
+<!--
+The element credential-interface specifies the interface that the
+resource adapter implementation supports for the representation
+of the credentials. This element should be used by application server
+to find out the Credential interface it should use as part of the
+security contract.
+
+The possible values are:
+ <credential-interface>javax.resource.spi.security.PasswordCredential
+ </credential-interface>
+ <credential-interface>javax.resource.spi.security.GenericCredential
+ </credential-interface>
+-->
+<!ELEMENT credential-interface (#PCDATA)>
+
+<!--
+The element authentication-mechanism-type specifies type of an authentication
+mechanism.
+
+The example values are:
+ <authentication-mechanism-type>BasicPassword</authentication-mechanism-type>
+ <authentication-mechanism-type>Kerbv5</authentication-mechanism-type>
+
+Any additional security mechanisms are outside the scope of the
+Connector architecture specification.
+-->
+<!ELEMENT authentication-mechanism-type (#PCDATA)>
+
+<!--
+The element connectionfactory-interface specifies the fully-qualified
+name of the ConnectionFactory interface supported by the resource
+adapter.
+
+Example: <connectionfactory-interface>com.wombat.ConnectionFactory
+ </connectionfactory-interface>
+OR
+<connectionfactory-interface>javax.resource.cci.ConnectionFactory
+ </connectionfactory-interface>
+-->
+<!ELEMENT connectionfactory-interface (#PCDATA)>
+
+<!--
+The element connectionfactory-impl-class specifies the fully-qualified
+name of the ConnectionFactory class that implements resource adapter
+specific ConnectionFactory interface.
+
+Example: <connectionfactory-impl-class>com.wombat.ConnectionFactoryImpl
+ </connectionfactory-impl-class>
+-->
+<!ELEMENT connectionfactory-impl-class (#PCDATA)>
+
+<!--
+The element connection-interface specifies the fully-qualified
+name of the Connection interface supported by the resource
+adapter.
+
+Example: <connection-interface>javax.resource.cci.Connection
+ </connection-interface>
+-->
+<!ELEMENT connection-interface (#PCDATA)>
+
+<!--
+The element connection-impl-class specifies the fully-qualified
+name of the Connection class that implements resource adapter
+specific Connection interface.
+
+Example: <connection-impl-class>com.wombat.ConnectionImpl
+ </connection-impl-class>
+-->
+<!ELEMENT connection-impl-class (#PCDATA)>
+
+<!--
+The element config-entry contains a declaration of a single
+configuration property for a ManagedConnectionFactory instance.
+
+Each ManagedConnectionFactory instance creates connections to a
+specific EIS instance based on the properties configured on the
+ManagedConnectionFactory instance. The configurable properties are
+specified only once in the deployment descriptor, even though a
+resource adapter can be used to configure multiple ManagedConnnection-
+Factory instances (that create connections to different instances of
+the same EIS).
+
+The declaration consists of an optional description, name, type
+and an optional value of the configuration property. If the resource
+adapter provider does not specify a value than the deployer is
+responsible for providing a valid value for a configuration property.
+
+Any bounds or well-defined values of properties should be described
+in the description element.
+-->
+<!ELEMENT config-property (description?, config-property-name,
+config-property-type, config-property-value?)>
+
+<!--
+The element config-property-name contains the name of a configuration
+property.
+
+Example: <config-property-name>ServerName</config-property-name>
+
+The connector architecture defines a set of well-defined properties
+all of type java.lang.String. These are as follows:
+ <config-property-name>ServerName</config-property-name>
+ <config-property-name>PortNumber</config-property-name>
+ <config-property-name>UserName</config-property-name>
+ <config-property-name>Password</config-property-name>
+ <config-property-name>ConnectionURL</config-property-name>
+
+A resource adapter provider can extend this property set to include
+properties specific to the resource adapter and its underlying EIS.
+-->
+<!ELEMENT config-property-name (#PCDATA)>
+
+<!--
+The element config-property-type contains the fully qualified Java
+type of a configuration property as required by ManagedConnection-
+Factory instance.
+
+The following are the legal values of config-property-type:
+ java.lang.Boolean, java.lang.String, java.lang.Integer,
+ java.lang.Double, java.lang.Byte, java.lang.Short,
+ java.lang.Long, java.lang.Float, java.lang.Character
+
+Example: <config-property-type>java.lang.String</config-property-type>
+-->
+<!ELEMENT config-property-type (#PCDATA)>
+
+
+<!--
+The element config-property-value contains the value of a configuration
+entry.
+
+Example: <config-property-value>WombatServer</config-property-value>
+-->
+<!ELEMENT config-property-value (#PCDATA)>
+
+
+<!--
+The element display-name contains a short name for the resource adapter
+that is intended to be displayed by the tools
+-->
+<!ELEMENT display-name (#PCDATA)>
+
+<!--
+The element description is used by resource adapter provider to provide
+text describing the parent element. The description element should include
+any information that the resource provider wants to provide to the
+deployer. Typically tools used by the consumer of resource adapter
+module will display the description when processing the parent element
+-->
+<!ELEMENT description (#PCDATA)>
+
+<!--
+The element eis-type contains information about the type of the
+EIS. For example, the type of an EIS can be product name of EIS
+independent of any version info.
+
+This helps in identifying EIS instances that can be used with
+this resource adapter.
+-->
+<!ELEMENT eis-type (#PCDATA)>
+
+<!--
+The icon element contains a small icon and large icon element
+which specify the URIs for a small and a large GIF or JPEG icon
+image to represent the application in GUI.
+-->
+<!ELEMENT icon (small-icon?, large-icon?)>
+
+<!--
+The large-icon element contains the name of a file containing an icon
+for the resource adapter module. The file name is relative path within
+the resource adapter module. This file must be either in JPEG or GIF
+format. The icon is used by tools to display information about the
+resource adapter module.
+
+Example:
+<large-icon>lib/images/wombatadapter_large.jpg</large-icon>
+-->
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+The small-icon element contains the name of a file containing an icon
+for the resource adapter module. The file name is relative path within
+the resource adapter module. This file must be either in JPEG or GIF
+format. The icon is used by tools to display information about the
+resource adapter module.
+
+Example:
+<small-icon>lib/images/wombatadapter_small.jpg</small-icon>
+-->
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+The element managedconnectionfactory-class specifies the fully qualified
+name of the Java class that implements the javax.resource.spi.Managed-
+ConnectionFactory interface. This Java class is provided as part of
+resource adapter's implementation of connector architecture specified
+contracts.
+
+Example:
+ <managedconnectionfactory-class>com.wombat.ManagedConnectionFactoryImpl
+ </managedconnectionfactory-class>
+-->
+<!ELEMENT managedconnectionfactory-class (#PCDATA)>
+
+<!--
+The element reauthentication-support specifies whether the resource
+adapter implementation supports re-authentication of existing Managed-
+Connection instance. Note that this information is for the resource
+adapter implementation and not for the underlying EIS instance.
+
+This element must be one of the following:
+ <reauthentication-support>true</reauthentication-support>
+ <reauthentication-support>false</reauthentication-support>
+-->
+<!ELEMENT reauthentication-support (#PCDATA)>
+
+<!--
+The element license specifies licensing requirements for the resource
+adapter module. This element specifies whether a license is required
+to deploy and use this resource adapter, and an optional description
+of the licensing terms (examples: duration of license, number of
+connection restrictions).
+-->
+<!ELEMENT license (description?, license-required)>
+
+<!--
+The element license-required specifies whether a license is required
+to deploy and use the resource adapter. This element must be one of
+the following:
+
+ <license-required>true</license-required>
+ <license-required>false</license-required>
+-->
+<!ELEMENT license-required (#PCDATA)>
+
+<!--
+The element spec-version specifies the version of the connector
+architecture specification that is supported by this resource
+adapter. This information enables deployer to configure the resource
+adapter to support deployment and runtime requirements of the
+corresponding connector architecture specification.
+
+Example:
+ <spec-version>1.0</spec-version>
+-->
+<!ELEMENT spec-version (#PCDATA)>
+
+
+<!--
+The element security permission specifies a security permission that
+is required by the resource adapter code.
+
+The security permission listed in the deployment descriptor are ones
+that are different from those required by the default permission set
+as specified in the connector specification. The optional description
+can mention specific reason that resource adapter requires a given
+security permission.
+-->
+<!ELEMENT security-permission (description?, security-permission-spec)>
+
+<!--
+The element permission-spec specifies a security permission based
+on the Security policy file syntax [reference: Java 2, Security
+architecture specification]
+
+http://java.sun.com/products/jdk/1.3/docs/guide/security/PolicyFiles.html#FileSyntax
+-->
+<!ELEMENT security-permission-spec (#PCDATA)>
+
+<!--
+The transaction-support element specifies the level of transaction
+support provided by the resource adapter.
+The value of transaction-support must be one of the following:
+ <transaction-support>NoTransaction</transaction-support>
+ <transaction-support>LocalTransaction</transaction-support>
+ <transaction-support>XATransaction</transaction-support>
+-->
+<!ELEMENT transaction-support (#PCDATA)>
+
+<!--
+The element vendor-name specifies the name of resource adapter provider
+vendor.
+Example:
+ <vendor-name>Wombat Corp.</vendor-name>
+-->
+<!ELEMENT vendor-name (#PCDATA)>
+
+<!--
+The element version specifies a string-based version of the
+resource adapter from the resource adapter provider.
+
+Example:
+ <version>1.0</version>
+-->
+<!ELEMENT version (#PCDATA)>
+
+<!--
+The ID mechanism is to allow tools that produce additional deployment
+information (beyond the standard deployment descriptor) to store the
+non-standard information in a separate file and to refer to standard
+deployment descriptor from these non-standard tools specific file.
+
+The connector specification does not allow the tools to add the non-
+standard information into the standard deployment descriptor.
+-->
+
+<!ATTLIST authentication-mechanism id ID #IMPLIED>
+<!ATTLIST authentication-mechanism-type id ID #IMPLIED>
+<!ATTLIST config-property id ID #IMPLIED>
+<!ATTLIST config-property-name id ID #IMPLIED>
+<!ATTLIST config-property-value id ID #IMPLIED>
+<!ATTLIST config-property-type id ID #IMPLIED>
+<!ATTLIST connector id ID #IMPLIED>
+<!ATTLIST connectionfactory-interface id ID #IMPLIED>
+<!ATTLIST connectionfactory-impl-class id ID #IMPLIED>
+<!ATTLIST connection-interface id ID #IMPLIED>
+<!ATTLIST connection-impl-class id ID #IMPLIED>
+<!ATTLIST credential-interface id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST eis-type id ID #IMPLIED>
+<!ATTLIST icon id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST license id ID #IMPLIED>
+<!ATTLIST license-required id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
+<!ATTLIST managedconnectionfactory-class id ID #IMPLIED>
+<!ATTLIST reauthentication-support id ID #IMPLIED>
+<!ATTLIST resourceadapter id ID #IMPLIED>
+<!ATTLIST security-permission id ID #IMPLIED>
+<!ATTLIST security-permission-spec id ID #IMPLIED>
+<!ATTLIST spec-version id ID #IMPLIED>
+<!ATTLIST transaction-support id ID #IMPLIED>
+<!ATTLIST vendor-name id ID #IMPLIED>
+<!ATTLIST version id ID #IMPLIED>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/datatypes.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/datatypes.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/datatypes.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,203 @@
+<!--
+ DTD for XML Schemas: Part 2: Datatypes
+ $Id: datatypes.dtd 20476 2004-04-17 13:29:24Z tdiesler $
+ Note this DTD is NOT normative, or even definitive. - - the
+ prose copy in the datatypes REC is the definitive version
+ (which shouldn't differ from this one except for this comment
+ and entity expansions, but just in case)
+ -->
+
+<!--
+ This DTD cannot be used on its own, it is intended
+ only for incorporation in XMLSchema.dtd, q.v.
+ -->
+
+<!-- Define all the element names, with optional prefix -->
+<!ENTITY % simpleType "%p;simpleType">
+<!ENTITY % restriction "%p;restriction">
+<!ENTITY % list "%p;list">
+<!ENTITY % union "%p;union">
+<!ENTITY % maxExclusive "%p;maxExclusive">
+<!ENTITY % minExclusive "%p;minExclusive">
+<!ENTITY % maxInclusive "%p;maxInclusive">
+<!ENTITY % minInclusive "%p;minInclusive">
+<!ENTITY % totalDigits "%p;totalDigits">
+<!ENTITY % fractionDigits "%p;fractionDigits">
+<!ENTITY % length "%p;length">
+<!ENTITY % minLength "%p;minLength">
+<!ENTITY % maxLength "%p;maxLength">
+<!ENTITY % enumeration "%p;enumeration">
+<!ENTITY % whiteSpace "%p;whiteSpace">
+<!ENTITY % pattern "%p;pattern">
+
+<!--
+ Customisation entities for the ATTLIST of each element
+ type. Define one of these if your schema takes advantage
+ of the anyAttribute='##other' in the schema for schemas
+ -->
+
+<!ENTITY % simpleTypeAttrs "">
+<!ENTITY % restrictionAttrs "">
+<!ENTITY % listAttrs "">
+<!ENTITY % unionAttrs "">
+<!ENTITY % maxExclusiveAttrs "">
+<!ENTITY % minExclusiveAttrs "">
+<!ENTITY % maxInclusiveAttrs "">
+<!ENTITY % minInclusiveAttrs "">
+<!ENTITY % totalDigitsAttrs "">
+<!ENTITY % fractionDigitsAttrs "">
+<!ENTITY % lengthAttrs "">
+<!ENTITY % minLengthAttrs "">
+<!ENTITY % maxLengthAttrs "">
+<!ENTITY % enumerationAttrs "">
+<!ENTITY % whiteSpaceAttrs "">
+<!ENTITY % patternAttrs "">
+
+<!-- Define some entities for informative use as attribute
+ types -->
+<!ENTITY % URIref "CDATA">
+<!ENTITY % XPathExpr "CDATA">
+<!ENTITY % QName "NMTOKEN">
+<!ENTITY % QNames "NMTOKENS">
+<!ENTITY % NCName "NMTOKEN">
+<!ENTITY % nonNegativeInteger "NMTOKEN">
+<!ENTITY % boolean "(true|false)">
+<!ENTITY % simpleDerivationSet "CDATA">
+<!--
+ #all or space-separated list drawn from derivationChoice
+ -->
+
+<!--
+ Note that the use of 'facet' below is less restrictive
+ than is really intended: There should in fact be no
+ more than one of each of minInclusive, minExclusive,
+ maxInclusive, maxExclusive, totalDigits, fractionDigits,
+ length, maxLength, minLength within datatype,
+ and the min- and max- variants of Inclusive and Exclusive
+ are mutually exclusive. On the other hand, pattern and
+ enumeration may repeat.
+ -->
+<!ENTITY % minBound "(%minInclusive; | %minExclusive;)">
+<!ENTITY % maxBound "(%maxInclusive; | %maxExclusive;)">
+<!ENTITY % bounds "%minBound; | %maxBound;">
+<!ENTITY % numeric "%totalDigits; | %fractionDigits;">
+<!ENTITY % ordered "%bounds; | %numeric;">
+<!ENTITY % unordered
+ "%pattern; | %enumeration; | %whiteSpace; | %length; |
+ %maxLength; | %minLength;">
+<!ENTITY % facet "%ordered; | %unordered;">
+<!ENTITY % facetAttr
+ "value CDATA #REQUIRED
+ id ID #IMPLIED">
+<!ENTITY % fixedAttr "fixed %boolean; #IMPLIED">
+<!ENTITY % facetModel "(%annotation;)?">
+<!ELEMENT %simpleType;
+ ((%annotation;)?, (%restriction; | %list; | %union;))>
+<!ATTLIST %simpleType;
+ name %NCName; #IMPLIED
+ final %simpleDerivationSet; #IMPLIED
+ id ID #IMPLIED
+ %simpleTypeAttrs;>
+<!-- name is required at top level -->
+<!ELEMENT %restriction; ((%annotation;)?,
+ (%restriction1; |
+ ((%simpleType;)?,(%facet;)*)),
+ (%attrDecls;))>
+<!ATTLIST %restriction;
+ base %QName; #IMPLIED
+ id ID #IMPLIED
+ %restrictionAttrs;>
+<!--
+ base and simpleType child are mutually exclusive,
+ one is required.
+
+ restriction is shared between simpleType and
+ simpleContent and complexContent (in XMLSchema.xsd).
+ restriction1 is for the latter cases, when this
+ is restricting a complex type, as is attrDecls.
+ -->
+<!ELEMENT %list; ((%annotation;)?,(%simpleType;)?)>
+<!ATTLIST %list;
+ itemType %QName; #IMPLIED
+ id ID #IMPLIED
+ %listAttrs;>
+<!--
+ itemType and simpleType child are mutually exclusive,
+ one is required
+ -->
+<!ELEMENT %union; ((%annotation;)?,(%simpleType;)*)>
+<!ATTLIST %union;
+ id ID #IMPLIED
+ memberTypes %QNames; #IMPLIED
+ %unionAttrs;>
+<!--
+ At least one item in memberTypes or one simpleType
+ child is required
+ -->
+
+<!ELEMENT %maxExclusive; %facetModel;>
+<!ATTLIST %maxExclusive;
+ %facetAttr;
+ %fixedAttr;
+ %maxExclusiveAttrs;>
+<!ELEMENT %minExclusive; %facetModel;>
+<!ATTLIST %minExclusive;
+ %facetAttr;
+ %fixedAttr;
+ %minExclusiveAttrs;>
+
+<!ELEMENT %maxInclusive; %facetModel;>
+<!ATTLIST %maxInclusive;
+ %facetAttr;
+ %fixedAttr;
+ %maxInclusiveAttrs;>
+<!ELEMENT %minInclusive; %facetModel;>
+<!ATTLIST %minInclusive;
+ %facetAttr;
+ %fixedAttr;
+ %minInclusiveAttrs;>
+
+<!ELEMENT %totalDigits; %facetModel;>
+<!ATTLIST %totalDigits;
+ %facetAttr;
+ %fixedAttr;
+ %totalDigitsAttrs;>
+<!ELEMENT %fractionDigits; %facetModel;>
+<!ATTLIST %fractionDigits;
+ %facetAttr;
+ %fixedAttr;
+ %fractionDigitsAttrs;>
+
+<!ELEMENT %length; %facetModel;>
+<!ATTLIST %length;
+ %facetAttr;
+ %fixedAttr;
+ %lengthAttrs;>
+<!ELEMENT %minLength; %facetModel;>
+<!ATTLIST %minLength;
+ %facetAttr;
+ %fixedAttr;
+ %minLengthAttrs;>
+<!ELEMENT %maxLength; %facetModel;>
+<!ATTLIST %maxLength;
+ %facetAttr;
+ %fixedAttr;
+ %maxLengthAttrs;>
+
+<!-- This one can be repeated -->
+<!ELEMENT %enumeration; %facetModel;>
+<!ATTLIST %enumeration;
+ %facetAttr;
+ %enumerationAttrs;>
+
+<!ELEMENT %whiteSpace; %facetModel;>
+<!ATTLIST %whiteSpace;
+ %facetAttr;
+ %fixedAttr;
+ %whiteSpaceAttrs;>
+
+<!-- This one can be repeated -->
+<!ELEMENT %pattern; %facetModel;>
+<!ATTLIST %pattern;
+ %facetAttr;
+ %patternAttrs;>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/ejb-jar.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/ejb-jar.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/ejb-jar.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,894 @@
+<!--
+Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road,
+Palo Alto, CA 94303, U.S.A. All rights reserved.
+
+This product or document is protected by copyright and distributed
+under licenses restricting its use, copying, distribution, and
+decompilation. No part of this product or documentation may be
+reproduced in any form by any means without prior written authorization
+of Sun and its licensors, if any.
+
+Third party software, including font technology, is copyrighted and
+licensed from Sun suppliers.
+
+Sun, Sun Microsystems, the Sun Logo, Solaris, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans,
+are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S.
+and other countries.
+
+All SPARC trademarks are used under license and are trademarks
+or registered trademarks of SPARC International, Inc.
+in the U.S. and other countries. Products bearing SPARC
+trademarks are based upon an architecture developed by Sun Microsystems, Inc.
+
+PostScript is a registered trademark of Adobe Systems, Inc.
+
+
+Federal Acquisitions: Commercial Software - Government Users Subject to
+Standard License Terms and Conditions.
+
+
+
+DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
+CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
+IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
+PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT
+TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY
+INVALID.
+
+_________________________________________________________________________
+Copyright 1999 Sun Microsystems, Inc.,
+901 San Antonio Road, Palo Alto, CA 94303, Etats-Unis.
+Tous droits re'serve's.
+
+
+Ce produit ou document est prote'ge' par un copyright et distribue' avec
+des licences qui en restreignent l'utilisation, la copie, la distribution,
+et la de'compilation. Aucune partie de ce produit ou de sa documentation
+associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen
+que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses
+bailleurs de licence, s'il y en a.
+
+Le logiciel de'tenu par des tiers, et qui comprend la technologie
+relative aux polices de caracte`res, est prote'ge' par un copyright
+et licencie' par des fournisseurs de Sun.
+
+Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans,
+sont des marques de fabrique ou des marques de'pose'es de Sun
+Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
+
+Toutes les marques SPARC sont utilise'es sous licence et sont
+des marques de fabrique ou des marques de'pose'es de SPARC
+International, Inc. aux Etats-Unis et dans
+d'autres pays. Les produits portant les marques SPARC sont
+base's sur une architecture de'veloppe'e par Sun Microsystems, Inc.
+
+Postcript est une marque enregistre'e d'Adobe Systems Inc.
+
+LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS,
+DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES,
+DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT
+TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE
+A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.
+-->
+
+
+<!--
+This is the XML DTD for the EJB 1.1 deployment descriptor.
+-->
+
+
+<!--
+The assembly-descriptor element contains application-assembly information.
+
+The application-assembly information consists of the following parts:
+the definition of security roles, the definition of method permissions,
+and the definition of transaction attributes for enterprise beans with
+container-managed transaction demarcation.
+
+All the parts are optional in the sense that they are omitted if the
+lists represented by them are empty.
+
+Providing an assembly-descriptor in the deployment descriptor is
+optional for the ejb-jar file producer.
+
+Used in: ejb-jar
+-->
+<!ELEMENT assembly-descriptor (security-role*, method-permission*,
+ container-transaction*)>
+
+<!--
+The cmp-field element describes a container-managed field. The field
+element includes an optional description of the field, and the name of
+the field.
+
+Used in: entity
+-->
+<!ELEMENT cmp-field (description?, field-name)>
+
+<!--
+The container-transaction element specifies how the container must
+manage transaction scopes for the enterprise bean's method invocations.
+The element consists of an optional description, a list of method
+elements, and a transaction attribute.The transaction attribute is to
+be applied to all the specified methods.
+
+Used in: assembly-descriptor
+-->
+<!ELEMENT container-transaction (description?, method+,
+ trans-attribute)>
+
+<!--
+The description element is used by the ejb-jar file producer to provide
+text describing the parent element.
+
+The description element should include any information that the ejb-jar
+file producer wants to provide to the consumer of the ejb-jar file
+(i.e. to the Deployer). Typically, the tools used by the ejb-jar file
+consumer will display the description when processing the parent
+element.
+
+Used in: cmp-field, container-transaction, ejb-jar, entity, env-entry,
+ejb-ref, method, method-permission, resource-ref, security-role,
+security-role-ref, and session.
+-->
+<!ELEMENT description (#PCDATA)>
+
+<!--
+The display-name element contains a short name that is intended to be
+display by tools.
+
+Used in: ejb-jar, session, and entity
+
+Example:
+ <display-name>Employee Self Service</display-name>
+-->
+<!ELEMENT display-name (#PCDATA)>
+
+<!--
+The ejb-class element contains the fully-qualified name of the
+enterprise bean's class.
+
+Used in: entity and session
+
+Example:
+ <ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
+-->
+<!ELEMENT ejb-class (#PCDATA)>
+
+<!--
+The optional ejb-client-jar element specifies a JAR file that contains
+the class files necessary for a client program to access the enterprise
+beans in the ejb-jar file. The Deployer should make the ejb-client JAR
+file accessible to the client's class-loader.
+
+Used in: ejb-jar
+
+Example:
+ <ejb-client-jar>employee_service_client.jar</ejb-client-jar>
+-->
+<!ELEMENT ejb-client-jar (#PCDATA)>
+
+<!--
+The ejb-jar element is the root element of the EJB deployment
+descriptor. It contains an optional description of the ejb-jar file,
+optional display name, optional small icon file name, optional large
+icon file name, mandatory structural information about all included
+enterprise beans, optional application-assembly descriptor, and an
+optional name of an ejb-client-jar file for the ejb-jar.
+-->
+<!ELEMENT ejb-jar (description?, display-name?, small-icon?,
+ large-icon?, enterprise-beans, assembly-descriptor?,
+ ejb-client-jar?)>
+
+<!--
+The ejb-link element is used in the ejb-ref element to specify that an
+EJB reference is linked to another enterprise bean in the ejb-jar
+file.
+
+The value of the ejb-link element must be the ejb-name of an enterprise
+bean in the same ejb-jar file, or in another ejb-jar file in the same
+J2EE application unit.
+
+Used in: ejb-ref
+
+Example:
+ <ejb-link>EmployeeRecord</ejb-link>
+-->
+<!ELEMENT ejb-link (#PCDATA)>
+
+<!--
+The ejb-name element specifies an enterprise bean's name. This name is
+assigned by the ejb-jar file producer to name the enterprise bean in
+the ejb-jar file's deployment descriptor. The name must be unique among
+the names of the enterprise beans in the same ejb-jar file.
+
+The enterprise bean code does not depend on the name; therefore the
+name can be changed during the application-assembly process without
+breaking the enterprise bean's function.
+
+There is no architected relationship between the ejb-name in the
+deployment descriptor and the JNDI name that the Deployer will assign
+to the enterprise bean's home.
+
+The name must conform to the lexical rules for an NMTOKEN.
+
+Used in: entity, method, and session
+
+Example:
+ <ejb-name>EmployeeService</ejb-name>
+-->
+<!ELEMENT ejb-name (#PCDATA)>
+
+<!--
+The ejb-ref element is used for the declaration of a reference to
+another enterprise bean's home. The declaration consists of an optional
+description; the EJB reference name used in the code of the referencing
+enterprise bean; the expected type of the referenced enterprise bean;
+the expected home and remote interfaces of the referenced enterprise
+bean; and an optional ejb-link information.
+
+The optional ejb-link element is used to specify the referenced
+enterprise bean. It is used typically in ejb-jar files that contain an
+assembled application.
+
+Used in: entity and session
+-->
+<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type, home,
+ remote, ejb-link?)>
+
+<!--
+The ejb-ref-name element contains the name of an EJB reference. The EJB
+reference is an entry in the enterprise bean's environment.
+
+It is recommended that name is prefixed with "ejb/".
+
+Used in: ejb-ref
+
+Example:
+ <ejb-ref-name>ejb/Payroll</ejb-ref-name>
+-->
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+<!--
+The ejb-ref-type element contains the expected type of the referenced
+enterprise bean.
+
+The ejb-ref-type element must be one of the following:
+ <ejb-ref-type>Entity</ejb-ref-type>
+ <ejb-ref-type>Session</ejb-ref-type>
+
+Used in: ejb-ref
+-->
+<!ELEMENT ejb-ref-type (#PCDATA)>
+
+<!--
+The enterprise-beans element contains the declarations of one or more
+enterprise beans.
+-->
+<!ELEMENT enterprise-beans (session | entity)+>
+
+<!--
+The entity element declares an entity bean. The declaration consists
+of: an optional description; optional display name; optional small icon
+file name; optional large icon file name; a name assigned to the
+enterprise bean in the deployment descriptor; the names of the entity
+bean's home and remote interfaces; the entity bean's implementation
+class; the entity bean's persistence management type; the entity bean's
+primary key class name; an indication of the entity bean's reentrancy;
+an optional list of container-managed fields; an optional specification
+of the primary key field; an optional declaration of the bean's
+environment entries; an optional declaration of the bean's EJB
+references; an optional declaration of the security role references;
+and an optional declaration of the bean's resource manager connection
+factory references.
+
+The optional primkey-field may be present in the descriptor if the
+entity's persistency-type is Container.
+
+The other elements that are optional are "optional" in the sense that
+they are omitted if the lists represented by them are empty.
+
+At least one cmp-field element must be present in the descriptor if the
+entity's persistency-type is Container, and none must not be present if
+the entity's persistence-type is Bean.
+
+Used in: enterprise-beans
+-->
+<!ELEMENT entity (description?, display-name?, small-icon?,
+ large-icon?, ejb-name, home, remote, ejb-class,
+ persistence-type, prim-key-class, reentrant,
+ cmp-field*, primkey-field?, env-entry*,
+ ejb-ref*, security-role-ref*, resource-ref*)>
+
+<!--
+The env-entry element contains the declaration of an enterprise bean's
+environment entries. The declaration consists of an optional
+description, the name of the environment entry, and an optional value.
+
+Used in: entity and session
+-->
+<!ELEMENT env-entry (description?, env-entry-name, env-entry-type,
+ env-entry-value?)>
+
+<!--
+The env-entry-name element contains the name of an enterprise bean's
+environment entry.
+
+Used in: env-entry
+
+Example:
+ <env-entry-name>minAmount</env-entry-name>
+-->
+<!ELEMENT env-entry-name (#PCDATA)>
+
+<!--
+The env-entry-type element contains the fully-qualified Java type of
+the environment entry value that is expected by the enterprise bean's
+code.
+
+The following are the legal values of env-entry-type:
+java.lang.Boolean, java.lang.String, java.lang.Integer,
+java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, and
+java.lang.Float.
+
+Used in: env-entry
+
+Example:
+ <env-entry-type>java.lang.Boolean</env-entry-type>
+-->
+<!ELEMENT env-entry-type (#PCDATA)>
+
+<!--
+The env-entry-value element contains the value of an enterprise bean's
+environment entry.
+
+Used in: env-entry
+
+Example:
+ <env-entry-value>100.00</env-entry-value>
+-->
+<!ELEMENT env-entry-value (#PCDATA)>
+
+<!--
+The field-name element specifies the name of a container managed field.
+The name must be a public field of the enterprise bean class or one of
+its superclasses.
+
+Used in: cmp-field
+
+Example:
+ <field-name>firstName</field-Name>
+-->
+<!ELEMENT field-name (#PCDATA)>
+
+<!--
+The home element contains the fully-qualified name of the enterprise
+bean's home interface.
+
+Used in: ejb-ref, entity, and session
+
+Example:
+ <home>com.aardvark.payroll.PayrollHome</home>
+-->
+<!ELEMENT home (#PCDATA)>
+
+<!--
+The large-icon element contains the name of a file containing a large
+(32 x 32) icon image. The file name is relative path within the ejb-jar
+file.
+
+The image must be either in the JPEG or GIF format, and the file name
+must end with the suffix ".jpg" or ".gif" respectively. The icon can
+be used by tools.
+
+Example:
+ <large-icon>employee-service-icon32x32.jpg</large-icon>
+-->
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+The method element is used to denote a method of an enterprise bean's
+home or remote interface, or a set of methods. The ejb-name element
+must be the name of one of the enterprise beans in declared in the
+deployment descriptor; the optional method-intf element allows to
+distinguish between a method with the same signature that is defined in
+both the home and remote interface; the method-name element specifies
+the method name; and the optional method-params elements identify a
+single method among multiple methods with an overloaded method name.
+
+There are three possible styles of the method element syntax:
+
+1. <method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>*</method-name>
+ </method>
+
+ This style is used to refer to all the methods of the specified
+ enterprise bean's home and remote interfaces.
+
+2. <method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>METHOD</method-name>
+ </method>>
+
+ This style is used to refer to the specified method of the
+ specified enterprise bean. If there are multiple methods with
+ the same overloaded name, the element of this style refers to
+ all the methods with the overloaded name.
+
+
+
+
+
+3. <method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>METHOD</method-name>
+ <method-params>
+ <method-param>PARAM-1</method-param>
+ <method-param>PARAM-2</method-param>
+ ...
+ <method-param>PARAM-n</method-param>
+ </method-params>
+ <method>
+
+ This style is used to refer to a single method within a set of
+ methods with an overloaded name. PARAM-1 through PARAM-n are the
+ fully-qualified Java types of the method's input parameters (if
+ the method has no input arguments, the method-params element
+ contains no method-param elements). Arrays are specified by the
+ array element's type, followed by one or more pair of square
+ brackets (e.g. int[][]).
+
+
+Used in: method-permission and container-transaction
+
+Examples:
+
+ Style 1: The following method element refers to all the methods of
+ the EmployeeService bean's home and remote interfaces:
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>*</method-name>
+ </method>
+
+ Style 2: The following method element refers to all the create
+ methods of the EmployeeService bean's home interface:
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>create</method-name>
+ </method>
+
+ Style 3: The following method element refers to the
+ create(String firstName, String LastName) method of the
+ EmployeeService bean's home interface.
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+ </method>
+
+
+ The following example illustrates a Style 3 element with
+ more complex parameter types. The method
+ foobar(char s, int i, int[] iar, mypackage.MyClass mycl,
+ mypackage.MyClass[][] myclaar)
+ would be specified as:
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>foobar</method-name>
+ <method-params>
+ <method-param>char</method-param>
+ <method-param>int</method-param>
+ <method-param>int[]</method-param>
+ <method-param>mypackage.MyClass</method-param>
+ <method-param>mypackage.MyClass[][]</method-param>
+ </method-params>
+ </method>
+
+ The optional method-intf element can be used when it becomes
+ necessary to differentiate between a method defined in the home
+ interface and a method with the same name and signature that is
+ defined in the remote interface.
+
+ For example, the method element
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>Remote</method-intf>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+ </method>
+
+ can be used to differentiate the create(String, String) method
+ defined in the remote interface from the create(String, String)
+ method defined in the home interface, which would be defined as
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>Home</method-intf>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+ </method>
+
+-->
+<!ELEMENT method (description?, ejb-name, method-intf?, method-name,
+ method-params?)>
+
+<!--
+The method-intf element allows a method element to differentiate
+between the methods with the same name and signature that are defined
+in both the remote and home interfaces.
+
+The method-intf element must be one of the following:
+ <method-intf>Home</method-intf>
+ <method-intf>Remote</method-intf>
+
+Used in: method
+-->
+<!ELEMENT method-intf (#PCDATA)>
+
+<!--
+The method-name element contains a name of an enterprise bean method,
+or the asterisk (*) character. The asterisk is used when the element
+denotes all the methods of an enterprise bean's remote and home
+interfaces.
+
+Used in: method
+-->
+<!ELEMENT method-name (#PCDATA)>
+
+<!--
+The method-param element contains the fully-qualified Java type name of
+a method parameter.
+
+Used in: method-params
+-->
+<!ELEMENT method-param (#PCDATA)>
+
+<!--
+The method-params element contains a list of the fully-qualified Java
+type names of the method parameters.
+
+Used in: method
+-->
+<!ELEMENT method-params (method-param*)>
+
+<!--
+The method-permission element specifies that one or more security roles
+are allowed to invoke one or more enterprise bean methods. The
+method-permission element consists of an optional description, a list
+of security role names, and a list of method elements.
+
+The security roles used in the method-permission element must be
+defined in the security-role element of the deployment descriptor, and
+the methods must be methods defined in the enterprise bean's remote
+and/or home interfaces.
+
+Used in: assembly-descriptor
+-->
+<!ELEMENT method-permission (description?, role-name+, method+)>
+
+<!--
+The persistence-type element specifies an entity bean's persistence
+management type.
+
+The persistence-type element must be one of the two following:
+ <persistence-type>Bean</persistence-type>
+ <persistence-type>Container</persistence-type>
+
+Used in: entity
+-->
+<!ELEMENT persistence-type (#PCDATA)>
+
+<!--
+The prim-key-class element contains the fully-qualified name of an
+entity bean's primary key class.
+
+If the definition of the primary key class is deferred to deployment
+time, the prim-key-class element should specify java.lang.Object.
+
+Used in: entity
+
+Examples:
+ <prim-key-class>java.lang.String</prim-key-class>
+ <prim-key-class>com.wombat.empl.EmployeeID</prim-key-class>
+ <prim-key-class>java.lang.Object</prim-key-class>
+
+-->
+<!ELEMENT prim-key-class (#PCDATA)>
+
+<!--
+The primkey-field element is used to specify the name of the primary
+key field for an entity with container-managed persistence.
+
+The primkey-field must be one of the fields declared in the cmp-field
+element, and the type of the field must be the same as the primary key
+type.
+
+The primkey-field element is not used if the primary key maps to
+multiple container-managed fields (i.e. the key is a compound key). In
+this case, the fields of the primary key class must be public, and
+their names must correspond to the field names of the entity bean class
+that comprise the key.
+
+Used in: entity
+
+Example:
+ <primkey-field>EmployeeId</primkey-field>
+-->
+<!ELEMENT primkey-field (#PCDATA)>
+
+<!--
+The reentrant element specifies whether an entity bean is reentrant or not.
+
+The reentrant element must be one of the two following:
+ <reentrant>True</reentrant>
+ <reentrant>False</reentrant>
+
+Used in: entity
+-->
+<!ELEMENT reentrant (#PCDATA)>
+
+<!--
+The remote element contains the fully-qualified name of the enterprise
+bean's remote interface.
+
+Used in: ejb-ref, entity, and session
+
+Example:
+ <remote>com.wombat.empl.EmployeeService</remote>
+-->
+<!ELEMENT remote (#PCDATA)>
+
+<!--
+The res-auth element specifies whether the enterprise bean code signs
+on programmatically to the resource manager, or whether the Container
+will sign on to the resource manager on behalf of the bean. In the
+latter case, the Container uses information that is supplied by the
+Deployer.
+
+The value of this element must be one of the two following:
+ <res-auth>Application</res-auth>
+ <res-auth>Container</res-auth>
+-->
+<!ELEMENT res-auth (#PCDATA)>
+
+<!--
+The res-ref-name element specifies the name of a resource manager
+connection factory reference.
+
+Used in: resource-ref
+-->
+<!ELEMENT res-ref-name (#PCDATA)>
+
+<!--
+The res-type element specifies the type of the data source. The type is
+specified by the Java interface (or class) expected to be implemented
+by the data source.
+
+Used in: resource-ref
+-->
+<!ELEMENT res-type (#PCDATA)>
+
+<!--
+The resource-ref element contains a declaration of enterprise bean's
+reference to an external resource. It consists of an optional
+description, the resource manager connection factory reference name,
+the indication of the resource manager connection factory type expected
+by the enterprise bean code, and the type of authentication (bean or
+container).
+
+Used in: entity and session
+
+Example:
+ <resource-ref>
+ <res-ref-name>EmployeeAppDB</res-ref-name>
+ <res-type>javax.sql.DataSource</res-type>
+ <res-auth>Container</res-auth>
+ </resource-ref>
+-->
+<!ELEMENT resource-ref (description?, res-ref-name, res-type,
+ res-auth)>
+
+<!--
+The role-link element is used to link a security role reference to a
+defined security role. The role-link element must contain the name of
+one of the security roles defined in the security-role elements.
+
+Used in: security-role-ref
+-->
+<!ELEMENT role-link (#PCDATA)>
+
+<!--
+The role-name element contains the name of a security role.
+
+The name must conform to the lexical rules for an NMTOKEN.
+
+Used in: method-permission, security-role, and security-role-ref
+-->
+<!ELEMENT role-name (#PCDATA)>
+
+<!--
+The security-role element contains the definition of a security role.
+The definition consists of an optional description of the security
+role, and the security role name.
+
+Used in: assembly-descriptor
+
+Example:
+ <security-role>
+ <description>
+ This role includes all employees who
+ are authorized to access the employee
+ service application.
+ </description>
+ <role-name>employee</role-name>
+ </security-role>
+-->
+<!ELEMENT security-role (description?, role-name)>
+
+<!--
+The security-role-ref element contains the declaration of a security
+role reference in the enterprise bean's code. The declaration consists
+of an optional description, the security role name used in the code,
+and an optional link to a defined security role.
+
+The value of the role-name element must be the String used as the
+parameter to the EJBContext.isCallerInRole(String roleName) method.
+
+The value of the role-link element must be the name of one of the
+security roles defined in the security-role elements.
+
+Used in: entity and session
+
+-->
+<!ELEMENT security-role-ref (description?, role-name, role-link?)>
+
+<!--
+The session-type element describes whether the session bean is a
+stateful session, or stateless session.
+
+The session-type element must be one of the two following:
+ <session-type>Stateful</session-type>
+ <session-type>Stateless</session-type>
+-->
+<!ELEMENT session-type (#PCDATA)>
+
+<!--
+The session element declares an session bean. The declaration consists
+of: an optional description; optional display name; optional small icon
+file name; optional large icon file name; a name assigned to the
+enterprise bean in the deployment description; the names of the session
+bean's home and remote interfaces; the session bean's implementation
+class; the session bean's state management type; the session bean's
+transaction management type; an optional declaration of the bean's
+environment entries; an optional declaration of the bean's EJB
+references; an optional declaration of the security role references;
+and an optional declaration of the bean's resource manager connection
+factory references.
+
+The elements that are optional are "optional" in the sense that they
+are omitted when if lists represented by them are empty.
+
+Used in: enterprise-beans
+-->
+<!ELEMENT session (description?, display-name?, small-icon?,
+ large-icon?, ejb-name, home, remote, ejb-class,
+ session-type, transaction-type, env-entry*,
+ ejb-ref*, security-role-ref*, resource-ref*)>
+
+<!--
+The small-icon element contains the name of a file containing a small
+(16 x 16) icon image. The file name is relative path within the ejb-jar
+file.
+
+The image must be either in the JPEG or GIF format, and the file name
+must end with the suffix ".jpg" or ".gif" respectively.
+
+The icon can be used by tools.
+
+Example:
+ <small-icon>employee-service-icon16x16.jpg</small-icon>
+-->
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+The transaction-type element specifies an enterprise bean's transaction
+management type.
+
+The transaction-type element must be one of the two following:
+ <transaction-type>Bean</transaction-type>
+ <transaction-type>Container</transaction-type>
+
+Used in: session
+-->
+<!ELEMENT transaction-type (#PCDATA)>
+
+<!--
+The trans-attribute element specifies how the container must manage the
+transaction boundaries when delegating a method invocation to an
+enterprise bean's business method.
+
+The value of trans-attribute must be one of the following:
+ <trans-attribute>NotSupported</trans-attribute>
+ <trans-attribute>Supports</trans-attribute>
+ <trans-attribute>Required</trans-attribute>
+ <trans-attribute>RequiresNew</trans-attribute>
+ <trans-attribute>Mandatory</trans-attribute>
+ <trans-attribute>Never</trans-attribute>
+
+Used in: container-transaction
+-->
+<!ELEMENT trans-attribute (#PCDATA)>
+
+<!--
+The ID mechanism is to allow tools that produce additional deployment
+information (i.e information beyond the standard EJB deployment
+descriptor information) to store the non-standard information in a
+separate file, and easily refer from these tools-specific files to the
+information in the standard deployment descriptor.
+
+The EJB architecture does not allow the tools to add the non-standard
+information into the EJB deployment descriptor.
+-->
+<!ATTLIST assembly-descriptor id ID #IMPLIED>
+<!ATTLIST cmp-field id ID #IMPLIED>
+<!ATTLIST container-transaction id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST ejb-class id ID #IMPLIED>
+<!ATTLIST ejb-client-jar id ID #IMPLIED>
+<!ATTLIST ejb-jar id ID #IMPLIED>
+<!ATTLIST ejb-link id ID #IMPLIED>
+<!ATTLIST ejb-name id ID #IMPLIED>
+<!ATTLIST ejb-ref id ID #IMPLIED>
+<!ATTLIST ejb-ref-name id ID #IMPLIED>
+<!ATTLIST ejb-ref-type id ID #IMPLIED>
+<!ATTLIST enterprise-beans id ID #IMPLIED>
+<!ATTLIST entity id ID #IMPLIED>
+<!ATTLIST env-entry id ID #IMPLIED>
+<!ATTLIST env-entry-name id ID #IMPLIED>
+<!ATTLIST env-entry-type id ID #IMPLIED>
+<!ATTLIST env-entry-value id ID #IMPLIED>
+<!ATTLIST field-name id ID #IMPLIED>
+<!ATTLIST home id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST method id ID #IMPLIED>
+<!ATTLIST method-intf id ID #IMPLIED>
+<!ATTLIST method-name id ID #IMPLIED>
+<!ATTLIST method-param id ID #IMPLIED>
+<!ATTLIST method-params id ID #IMPLIED>
+<!ATTLIST method-permission id ID #IMPLIED>
+<!ATTLIST persistence-type id ID #IMPLIED>
+<!ATTLIST prim-key-class id ID #IMPLIED>
+<!ATTLIST primkey-field id ID #IMPLIED>
+<!ATTLIST reentrant id ID #IMPLIED>
+<!ATTLIST remote id ID #IMPLIED>
+<!ATTLIST res-auth id ID #IMPLIED>
+<!ATTLIST res-ref-name id ID #IMPLIED>
+<!ATTLIST res-type id ID #IMPLIED>
+<!ATTLIST resource-ref id ID #IMPLIED>
+<!ATTLIST role-link id ID #IMPLIED>
+<!ATTLIST role-name id ID #IMPLIED>
+<!ATTLIST security-role id ID #IMPLIED>
+<!ATTLIST security-role-ref id ID #IMPLIED>
+<!ATTLIST session-type id ID #IMPLIED>
+<!ATTLIST session id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
+<!ATTLIST transaction-type id ID #IMPLIED>
+<!ATTLIST trans-attribute id ID #IMPLIED>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/ejb-jar_2_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/ejb-jar_2_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/ejb-jar_2_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1660 @@
+<!--
+Copyright 2000-2001 Sun Microsystems, Inc. 901 San Antonio Road,
+Palo Alto, CA 94303, U.S.A. All rights reserved.
+
+This product or document is protected by copyright and distributed
+under licenses restricting its use, copying, distribution, and
+decompilation. No part of this product or documentation may be
+reproduced in any form by any means without prior written authorization
+of Sun and its licensors, if any.
+
+Third party software, including font technology, is copyrighted and
+licensed from Sun suppliers.
+
+Sun, Sun Microsystems, the Sun Logo, Solaris, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans,
+are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S.
+and other countries.
+
+All SPARC trademarks are used under license and are trademarks
+or registered trademarks of SPARC International, Inc.
+in the U.S. and other countries. Products bearing SPARC
+trademarks are based upon an architecture developed by Sun Microsystems, Inc.
+
+PostScript is a registered trademark of Adobe Systems, Inc.
+
+Federal Acquisitions: Commercial Software - Government Users Subject to
+Standard License Terms and Conditions.
+
+DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
+CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
+IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
+PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT
+TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY
+INVALID.
+
+_________________________________________________________________________
+
+Copyright 2000-2001 Sun Microsystems, Inc.,
+901 San Antonio Road, Palo Alto, CA 94303, Etats-Unis.
+Tous droits re'serve's.
+
+
+Ce produit ou document est prote'ge' par un copyright et distribue' avec
+des licences qui en restreignent l'utilisation, la copie, la distribution,
+et la de'compilation. Aucune partie de ce produit ou de sa documentation
+associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen
+que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses
+bailleurs de licence, s'il y en a.
+
+Le logiciel de'tenu par des tiers, et qui comprend la technologie
+relative aux polices de caracte`res, est prote'ge' par un copyright
+et licencie' par des fournisseurs de Sun.
+
+Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans,
+sont des marques de fabrique ou des marques de'pose'es de Sun
+Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
+
+Toutes les marques SPARC sont utilise'es sous licence et sont
+des marques de fabrique ou des marques de'pose'es de SPARC
+International, Inc. aux Etats-Unis et dans
+d'autres pays. Les produits portant les marques SPARC sont
+base's sur une architecture de'veloppe'e par Sun Microsystems, Inc.
+
+Postcript est une marque enregistre'e d'Adobe Systems Inc.
+
+LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS,
+DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES,
+DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT
+TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE
+A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.
+-->
+
+<!--
+This is the XML DTD for the EJB 2.0 deployment descriptor.
+All EJB 2.0 deployment descriptors must include a DOCTYPE
+of the following form:
+
+ <!DOCTYPE ejb-jar PUBLIC
+ "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
+ "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
+
+-->
+
+<!--
+The following conventions apply to all J2EE deployment descriptor
+elements unless indicated otherwise.
+
+- In elements that contain PCDATA, leading and trailing whitespace
+ in the data may be ignored.
+
+- In elements whose value is an "enumerated type", the value is
+ case sensitive.
+
+- In elements that specify a pathname to a file within the same
+ JAR file, relative filenames (i.e., those not starting with "/")
+ are considered relative to the root of the JAR file's namespace.
+ Absolute filenames (i.e., those starting with "/") also specify
+ names in the root of the JAR file's namespace. In general, relative
+ names are preferred. The exception is .war files where absolute
+ names are preferred for consistency with the servlet API.
+-->
+
+
+<!--
+The ejb-jar element is the root element of the EJB deployment
+descriptor. It contains
+
+ - an optional description of the ejb-jar file
+ - an optional display name
+ - an optional small icon file name
+ - an optional large icon file name
+ - mandatory structural information about all included
+ enterprise beans
+ - a descriptor for container managed relationships, if any
+ - an optional application-assembly descriptor
+ - an optional name of an ejb-client-jar file for the ejb-jar.
+-->
+<!ELEMENT ejb-jar (description?, display-name?, small-icon?,
+large-icon?, enterprise-beans, relationships?, assembly-descriptor?,
+ejb-client-jar?)>
+
+<!--
+The abstract-schema-name element specifies the name of the abstract
+schema type of an entity bean with cmp-version 2.x. It is used in EJB
+QL queries.
+
+For example, the abstract-schema-name for an entity bean whose local
+interface is com.acme.commerce.Order might be Order.
+
+Used in: entity
+-->
+<!ELEMENT abstract-schema-name (#PCDATA)>
+
+<!--
+
+The acknowledge-mode element specifies whether JMS AUTO_ACKNOWLEDGE or
+DUPS_OK_ACKNOWLEDGE message acknowledgment semantics should be used
+for the onMessage message of a message-driven bean that uses bean
+managed transaction demarcation.
+
+The acknowledge-mode element must be one of the two following:
+
+ <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
+ <acknowledge-mode>Dups-ok-acknowledge</acknowledgemode>
+
+Used in: message-driven
+-->
+<!ELEMENT acknowledge-mode (#PCDATA)>
+
+<!--
+The assembly-descriptor element contains application-assembly information.
+
+The application-assembly information consists of the following parts:
+the definition of security roles, the definition of method
+permissions, the definition of transaction attributes for
+enterprise beans with container-managed transaction demarcation and
+a list of methods to be excluded from deployment.
+
+All the parts are optional in the sense that they are omitted if the
+lists represented by them are empty.
+
+Providing an assembly-descriptor in the deployment descriptor is
+optional for the ejb-jar file producer.
+
+Used in: ejb-jar
+-->
+<!ELEMENT assembly-descriptor (security-role*, method-permission*,
+container-transaction*, exclude-list?)>
+
+<!--
+The cascade-delete element specifies that, within a particular
+relationship, the lifetime of one or more entity beans is dependent
+upon the lifetime of another entity bean. The cascade-delete element
+can only be specified for an ejb-relationship-role element contained
+in an ejb-relation element in which the other ejb-relationship-role
+element specifies a multiplicity of One.
+
+Used in: ejb-relationship-role
+-->
+<!ELEMENT cascade-delete EMPTY>
+
+<!--
+The cmp-field element describes a container-managed field. The
+field element includes an optional description of the field, and the
+name of the field.
+
+Used in: entity
+-->
+<!ELEMENT cmp-field (description?, field-name)>
+
+<!--
+The cmp-version element specifies the version of an entity bean
+with container-managed persistence.
+
+The cmp-version element must be one of the two following:
+
+ <cmp-version>1.x</cmp-version>
+ <cmp-version>2.x</cmp-version>
+
+The default value of the cmp-version element is 2.x.
+
+Used in: entity
+-->
+<!ELEMENT cmp-version (#PCDATA)>
+
+<!--
+
+The cmr-field element describes the bean provider's view of a
+relationship. It consists of an optional description, and the name and
+the class type of a field in the source of a role of a
+relationship. The cmr-field-name element corresponds to the name used
+for the get and set accessor methods for the relationship. The
+cmr-field-type element is used only for collection-valued
+cmr-fields. It specifies the type of the collection that is used.
+
+Used in: ejb-relationship-role
+-->
+<!ELEMENT cmr-field (description?, cmr-field-name, cmr-field-type?)>
+
+<!--
+The cmr-field-name element specifies the name of a logical
+relationship field in the entity bean class. The name of the cmr-field
+must begin with a lowercase letter. This field is accessed by methods
+whose names consists of the name of the field specified by
+cmr-field-name in which the first letter is uppercased, prefixed by
+"get" or "set".
+
+Used in: cmr-field
+-->
+<!ELEMENT cmr-field-name (#PCDATA)>
+
+<!--
+The cmr-field-type element specifies the class of a
+collection-valued logical relationship field in the entity bean
+class. The value of the cmr-field-type element must be either:
+java.util.Collection or java.util.Set.
+
+Used in: cmr-field
+-->
+<!ELEMENT cmr-field-type (#PCDATA)>
+
+<!--
+The container-transaction element specifies how the container
+must manage transaction scopes for the enterprise bean's method
+invocations. The element consists of an optional description, a list
+of method elements, and a transaction attribute. The transaction
+attribute is to be applied to all the specified methods.
+
+Used in: assembly-descriptor
+-->
+<!ELEMENT container-transaction (description?, method+, trans-attribute)>
+
+<!--
+The description element is used to provide text describing the parent
+element. The description element should include any information that
+the enterprise bean ejb-jar file producer wants to provide to the consumer of
+the enterprise bean ejb-jar file (i.e., to the Deployer). Typically, the tools
+used by the enterprise bean ejb-jar file consumer will display the description
+when processing the parent element that contains the description.
+
+Used in: cmp-field, cmr-field, container-transaction, ejb-jar,
+ejb-local-ref, ejb-ref, ejb-relation, ejb-relationship-role, entity,
+env-entry, exclude-list, message-driven, method, method-permission,
+query, relationship-role-source, relationships, resource-env-ref,
+resource-ref, run-as, security-identity, security-role,
+security-role-ref, session
+-->
+<!ELEMENT description (#PCDATA)>
+
+<!--
+The destination-type element specifies the type of the JMS
+destination. The type is specified by the Java interface expected to
+be implemented by the destination.
+
+The destination-type element must be one of the two following:
+
+<destination-type>javax.jms.Queue</destination-type>
+<destination-type>javax.jms.Topic</destination-type>
+
+Used in: message-driven-destination
+-->
+<!ELEMENT destination-type (#PCDATA)>
+
+<!--
+The display-name element contains a short name that is intended to be
+displayed by tools. The display name need not be unique.
+
+Used in: ejb-jar, entity, message-driven, session
+
+Example:
+
+<display-name>Employee Self Service</display-name>
+-->
+<!ELEMENT display-name (#PCDATA)>
+
+<!--
+The ejb-class element contains the fully-qualified name of the
+enterprise bean's class.
+
+Used in: entity, message-driven, session
+
+Example:
+
+<ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
+-->
+<!ELEMENT ejb-class (#PCDATA)>
+
+<!--
+The optional ejb-client-jar element specifies a JAR file that contains
+the class files necessary for a client program to access the
+enterprise beans in the ejb-jar file.
+
+Used in: ejb-jar
+
+Example:
+
+<ejb-client-jar>employee_service_client.jar</ejb-client-jar>
+-->
+<!ELEMENT ejb-client-jar (#PCDATA)>
+
+<!--
+The ejb-link element is used in the ejb-ref or ejb-local-ref
+elements to specify that an EJB reference is linked to an
+enterprise bean.
+
+The value of the ejb-link element must be the ejb-name of an
+enterprise bean in the same ejb-jar file or in another ejb-jar
+file in the same J2EE application unit.
+
+Alternatively, the name in the ejb-link element may be composed of a
+path name specifying the ejb-jar containing the referenced enterprise
+bean with the ejb-name of the target bean appended and separated from
+the path name by "#". The path name is relative to the ejb-jar file
+containing the enterprise bean that is referencing the enterprise bean.
+This allows multiple enterprise beans with the same ejb-name to be
+uniquely identified.
+
+Used in: ejb-local-ref, ejb-ref
+
+Examples:
+
+ <ejb-link>EmployeeRecord</ejb-link>
+
+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
+
+-->
+<!ELEMENT ejb-link (#PCDATA)>
+
+<!--
+The ejb-local-ref element is used for the declaration of a reference to
+an enterprise bean's local home. The declaration consists of:
+
+ - an optional description
+ - the EJB reference name used in the code of the enterprise bean
+ that's referencing the enterprise bean
+ - the expected type of the referenced enterprise bean
+ - the expected local home and local interfaces of the referenced
+ enterprise bean
+ - optional ejb-link information, used to specify the referenced
+ enterprise bean
+
+Used in: entity, message-driven, session
+-->
+<!ELEMENT ejb-local-ref (description?, ejb-ref-name, ejb-ref-type,
+ local-home, local, ejb-link?)>
+
+<!--
+The ejb-name element specifies an enterprise bean's name. This name is
+assigned by the ejb-jar file producer to name the enterprise bean in
+the ejb-jar file's deployment descriptor. The name must be unique
+among the names of the enterprise beans in the same ejb-jar file.
+
+There is no architected relationship between the ejb-name in the
+deployment descriptor and the JNDI name that the Deployer will assign
+to the enterprise bean's home.
+
+The name for an entity bean with cmp-version 2.x must conform to the
+lexical rules for an NMTOKEN. The name for an entity bean with
+cmp-version 2.x must not be a reserved literal in EJB QL.
+
+Used in: entity, message-driven, method, relationship-role-source,
+session
+
+Example:
+
+<ejb-name>EmployeeService</ejb-name>
+-->
+<!ELEMENT ejb-name (#PCDATA)>
+
+<!--
+The ejb-ql element contains the EJB QL query string that defines
+a finder or select query. This element is defined within the scope of
+a query element whose contents specify the finder or the select method
+that uses the query. The content must be a valid EJB QL query string
+for the entity bean for which the query is specified.
+
+The ejb-ql element must be specified for all queries that are
+expressible in EJB QL.
+
+Used in: query
+
+Example:
+<query>
+ <query-method>
+ <method-name>ejbSelectPendingLineitems</method-name>
+ <method-params/>
+ </query-method>
+ <ejb-ql>SELECT ENTITY(l) FROM LineItems l WHERE l.shipped <> TRUE
+ </ejb-ql>
+</query>
+
+-->
+<!ELEMENT ejb-ql (#PCDATA)>
+
+<!--
+The ejb-ref element is used for the declaration of a reference to
+an enterprise bean's home. The declaration consists of:
+
+ - an optional description
+ - the EJB reference name used in the code of
+ the enterprise bean that's referencing the enterprise bean
+ - the expected type of the referenced enterprise bean
+ - the expected home and remote interfaces of the referenced
+ enterprise bean
+ - optional ejb-link information, used to specify the referenced
+ enterprise bean
+
+Used in: entity, message-driven, session
+-->
+<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type,
+ home, remote, ejb-link?)>
+
+<!--
+The ejb-ref-name element contains the name of an EJB reference. The
+EJB reference is an entry in the enterprise bean's environment and is
+relative to the java:comp/env context. The name must be unique
+within the enterprise bean.
+
+It is recommended that name is prefixed with "ejb/".
+
+Used in: ejb-local-ref, ejb-ref
+
+Example:
+
+<ejb-ref-name>ejb/Payroll</ejb-ref-name>
+-->
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+<!--
+The ejb-ref-type element contains the expected type of the
+referenced enterprise bean.
+
+The ejb-ref-type element must be one of the following:
+
+ <ejb-ref-type>Entity</ejb-ref-type>
+ <ejb-ref-type>Session</ejb-ref-type>
+
+Used in: ejb-local-ref, ejb-ref
+-->
+<!ELEMENT ejb-ref-type (#PCDATA)>
+
+<!--
+
+The ejb-relation element describes a relationship between two
+entity beans with container managed persistence. An ejb-relation
+element contains a description; an optional ejb-relation-name element;
+and exactly two relationship role declarations, defined by the
+ejb-relationship-role elements. The name of the relationship, if
+specified, is unique within the ejb-jar file.
+
+Used in: relationships
+-->
+<!ELEMENT ejb-relation (description?, ejb-relation-name?, ejb-relationship-role,
+ejb-relationship-role)>
+
+<!--
+The ejb-relation-name element provides a unique name for a relationship.
+
+Used in: ejb-relation
+-->
+<!ELEMENT ejb-relation-name (#PCDATA)>
+
+<!--
+The ejb-relationship-role element describes a role within a
+relationship. There are two roles in each relationship.
+
+The ejb-relationship-role element contains an optional description; an
+optional name for the relationship role; a specification of the
+multiplicity of the role; an optional specification of cascade-delete
+functionality for the role; the role source; and a declaration of the
+cmr-field, if any, by means of which the other side of the
+relationship is accessed from the perspective of the role source.
+
+The multiplicity and role-source element are mandatory.
+
+The relationship-role-source element designates an entity bean by
+means of an ejb-name element. For bidirectional relationships, both
+roles of a relationship must declare a relationship-role-source
+element that specifies a cmr-field in terms of which the relationship
+is accessed. The lack of a cmr-field element in an
+ejb-relationship-role specifies that the relationship is
+unidirectional in navigability and the entity bean that participates
+in the relationship is "not aware" of the relationship.
+
+Used in: ejb-relation
+
+Example:
+
+<ejb-relation>
+ <ejb-relation-name>Product-LineItem</ejb-relation-name>
+ <ejb-relationship-role>
+ <ejb-relationship-role-name>product-has-lineitems
+ </ejb-relationship-role-name>
+ <multiplicity>One</multiplicity>
+ <relationship-role-source>
+ <ejb-name>ProductEJB</ejb-name>
+ </relationship-role-source>
+ </ejb-relationship-role>
+...
+-->
+<!ELEMENT ejb-relationship-role (description?, ejb-relationship-role-name?,
+multiplicity, cascade-delete?, relationship-role-source, cmr-field?)>
+
+<!--
+The ejb-relationship-role-name element defines a name for a role that
+is unique within an ejb-relation. Different relationships can use the
+same name for a role.
+
+Used in: ejb-relationship-role
+-->
+<!ELEMENT ejb-relationship-role-name (#PCDATA)>
+
+<!--
+The enterprise-beans element contains the declarations of one or more
+enterprise beans.
+-->
+<!ELEMENT enterprise-beans (session | entity | message-driven)+>
+
+<!--
+The entity element declares an entity bean. The declaration
+consists of:
+
+ - an optional description
+ - an optional display name
+ - an optional small icon file name
+ - an optional large icon file name
+ - a unique name assigned to the enterprise bean
+ in the deployment descriptor
+ - the names of the entity bean's home and component interfaces, if any
+ - the names of the entity bean's local home and local
+ interface, if any
+ - the entity bean's implementation class
+ - the entity bean's persistence management type
+ - the entity bean's primary key class name
+ - an indication of the entity bean's reentrancy
+ - an optional specification of the entity bean's cmp-version
+ - an optional specification of the entity bean's abstract
+ schema name
+ - an optional list of container-managed fields
+ - an optional specification of the primary key field
+ - an optional declaration of the bean's environment entries
+ - an optional declaration of the bean's EJB references
+ - an optional declaration of the bean's local EJB references
+ - an optional declaration of the security role references
+ - an optional declaration of the security identity
+ to be used for the execution of the bean's methods
+ - an optional declaration of the bean's resource manager
+ connection factory references
+ - an optional declaration of the bean's
+ resource environment references
+ - an optional set of query declarations
+ for finder and select methods for an entity
+ bean with cmp-version 2.x.
+
+The optional abstract-schema-name element must be specified for an
+entity bean with container managed persistence and cmp-version 2.x.
+
+The optional primkey-field may be present in the descriptor if the
+entity's persistence-type is Container.
+
+The optional cmp-version element may be present in the descriptor if
+the entity's persistence-type is Container. If the persistence-type is
+Container and the cmp-version element is not specified, its value
+defaults to 2.x.
+
+The optional home and remote elements must be specified if the entity
+bean cmp-version is 1.x.
+
+The optional local-home and local elements must be specified if the
+entity bean has a local home and local interface.
+
+Either both the local-home and the local elements or both the
+home and the remote elements must be specified.
+
+The optional query elements must be present if the persistence-type is
+Container and the cmp-version is 2.x and query methods other than
+findByPrimaryKey have been defined for the entity bean.
+
+The other elements that are optional are "optional" in the sense that
+they are omitted if the lists represented by them are empty.
+
+At least one cmp-field element must be present in the descriptor if
+the entity's persistence-type is Container and the cmp-version is 1.x,
+and none must not be present if the entity's persistence-type is Bean.
+
+Used in: enterprise-beans
+
+-->
+<!ELEMENT entity (description?, display-name?, small-icon?,
+ large-icon?, ejb-name, home?, remote?, local-home?,
+ local?, ejb-class, persistence-type, prim-key-class,
+ reentrant, cmp-version?, abstract-schema-name?,
+ cmp-field*, primkey-field?, env-entry*, ejb-ref*,
+ ejb-local-ref*, security-role-ref*, security-identity?,
+ resource-ref*, resource-env-ref*, query*)>
+
+<!--
+The env-entry element contains the declaration of an enterprise bean's
+environment entry. The declaration consists of an optional
+description, the name of the environment entry, and an optional
+value. If a value is not specified, one must be supplied
+during deployment.
+
+Used in: entity, message-driven, session
+-->
+<!ELEMENT env-entry (description?, env-entry-name, env-entry-type,
+ env-entry-value?)>
+
+<!--
+The env-entry-name element contains the name of an enterprise bean's
+environment entry. The name is a JNDI name relative to the
+java:comp/env context. The name must be unique within an enterprise bean.
+
+Used in: env-entry
+
+Example:
+
+<env-entry-name>minAmount</env-entry-name>
+-->
+<!ELEMENT env-entry-name (#PCDATA)>
+
+<!--
+The env-entry-type element contains the fully-qualified Java type of
+the environment entry value that is expected by the enterprise bean's
+code.
+
+The following are the legal values of env-entry-type:
+
+ java.lang.Boolean
+ java.lang.Byte
+ java.lang.Character
+ java.lang.String
+ java.lang.Short
+ java.lang.Integer
+ java.lang.Long
+ java.lang.Float
+ java.lang.Double
+
+
+Used in: env-entry
+
+Example:
+
+<env-entry-type>java.lang.Boolean</env-entry-type>
+-->
+<!ELEMENT env-entry-type (#PCDATA)>
+
+<!--
+The env-entry-value element contains the value of an enterprise bean's
+environment entry. The value must be a String that is valid for the
+constructor of the specified type that takes a single String
+parameter, or for java.lang.Character, a single character.
+
+Used in: env-entry
+
+Example:
+
+<env-entry-value>100.00</env-entry-value>
+-->
+<!ELEMENT env-entry-value (#PCDATA)>
+
+<!--
+The exclude list element defines a set of methods which the Assembler marks to
+be uncallable. It contains one or more methods.
+
+If the method permission relation contains methods that are in the
+exclude list, the Deployer must consider those methods to be
+uncallable.
+
+Used in: assembly-descriptor
+-->
+<!ELEMENT exclude-list (description?, method+)>
+
+<!--
+The field-name element specifies the name of a container managed
+field. The name must be a public field of the enterprise bean class or
+one of its superclasses.
+
+The name of the cmp-field of an entity bean with cmp-version 2.x must
+begin with a lowercase letter. This field is accessed by methods whose
+names consists of the name of the field specified by field-name in
+which the first letter is uppercased, prefixed by "get" or "set".
+
+Used in: cmp-field
+
+Example:
+
+
+ <field-name>firstName</field-Name>
+
+-->
+<!ELEMENT field-name (#PCDATA)>
+
+<!--
+The home element contains the fully-qualified name of the enterprise
+bean's home interface.
+
+Used in: ejb-ref, entity, session
+
+Example:
+
+<home>com.aardvark.payroll.PayrollHome</home>
+-->
+<!ELEMENT home (#PCDATA)>
+
+<!--
+The large-icon element contains the name of a file
+containing a large (32 x 32) icon image. The file
+name is a relative path within the enterprise bean's
+ejb-jar file.
+
+The image may be either in the JPEG or GIF format.
+The icon can be used by tools.
+
+Used in: ejb-jar, entity, message-driven, session
+
+Example:
+
+<large-icon>employee-service-icon32x32.jpg</large-icon>
+-->
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+
+The local element contains the fully-qualified name of the
+enterprise bean's local interface.
+
+Used in: ejb-local-ref, entity, session
+
+-->
+<!ELEMENT local (#PCDATA)>
+
+<!--
+
+The local-home element contains the fully-qualified name of the
+enterprise bean's local home interface.
+
+Used in: ejb-local-ref, entity, session
+-->
+<!ELEMENT local-home (#PCDATA)>
+
+<!--
+
+The message-driven element declares a message-driven bean. The
+declaration consists of:
+
+ - an optional description
+ - an optional display name
+ - an optional small icon file name
+ - an optional large icon file name
+ - a name assigned to the enterprise bean in
+ the deployment descriptor
+ - the message-driven bean's implementation class
+ - the message-driven bean's transaction management type
+ - an optional declaration of the message-driven bean's
+ message selector
+ - an optional declaration of the
+ acknowledgment mode for the message-driven bean
+ if bean-managed transaction demarcation is used
+ - an optional declaration of the
+ intended destination type of the message-driven bean
+ - an optional declaration of the bean's environment entries
+ - an optional declaration of the bean's EJB references
+ - an optional declaration of the bean's local EJB references
+ - an optional declaration of the security
+ identity to be used for the execution of the bean's methods
+ - an optional declaration of the bean's resource manager
+ connection factory references
+ - an optional declaration of the bean's resource
+ environment references.
+
+Used in: enterprise-beans
+-->
+<!ELEMENT message-driven (description?, display-name?, small-icon?,
+ large-icon?, ejb-name, ejb-class, transaction-type,
+ message-selector?, acknowledge-mode?,
+ message-driven-destination?, env-entry*, ejb-ref*,
+ ejb-local-ref*, security-identity?, resource-ref*,
+ resource-env-ref*)>
+
+<!--
+The message-driven-destination element provides advice to the Deployer
+as to whether a message-driven bean is intended for a Queue or a
+Topic. The declaration consists of: the type of the message-driven
+bean's intended destination and an optional declaration of whether a
+durable or non-durable subscription should be used if the
+destination-type is javax.jms.Topic.
+
+Used in: message-driven
+-->
+<!ELEMENT message-driven-destination (destination-type,
+subscription-durability?)>
+
+<!--
+The message-selector element is used to specify the JMS message
+selector to be used in determining which messages a message-driven
+bean is to receive.
+
+Example:
+<message-selector>JMSType = `car' AND color = `blue' AND weight > 2500
+</message-selector>
+
+Used in: message-driven
+-->
+<!ELEMENT message-selector (#PCDATA)>
+
+<!--
+
+The method element is used to denote a method of an enterprise
+bean's home or component interface, or, in the case of a message-driven
+bean, the bean's onMessage method, or a set of methods. The ejb-name
+element must be the name of one of the enterprise beans declared in
+the deployment descriptor; the optional method-intf element allows to
+distinguish between a method with the same signature that is multiply
+defined across in both the home and component interfaces; the
+method-name element specifies the method name; and the optional
+method-params elements identify a single method among multiple methods
+with an overloaded method name.
+
+There are three possible styles of the method element syntax:
+
+1.
+<method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>*</method-name>
+</method>
+
+ This style is used to refer to all the methods of the specified
+ enterprise bean's home and component interfaces.
+
+2.
+<method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>METHOD</method-name>
+</method>>
+
+ This style is used to refer to the specified method of the
+ specified enterprise bean. If there are multiple methods with
+ the same overloaded name, the element of this style refers to
+ all the methods with the overloaded name.
+
+
+3.
+<method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>METHOD</method-name>
+ <method-params>
+ <method-param>PARAM-1</method-param>
+ <method-param>PARAM-2</method-param>
+ ...
+ <method-param>PARAM-n</method-param>
+ </method-params>
+<method>
+
+
+ This style is used to refer to a single method within a set of
+ methods with an overloaded name. PARAM-1 through PARAM-n are the
+ fully-qualified Java types of the method's input parameters (if
+ the method has no input arguments, the method-params element
+ contains no method-param elements). Arrays are specified by the
+ array element's type, followed by one or more pair of square
+ brackets (e.g. int[][]).
+
+
+Used in: container-transaction, exclude-list, method-permission
+
+Examples:
+
+Style 1: The following method element refers to all the methods of
+the EmployeeService bean's home and component interfaces:
+
+<method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>*</method-name>
+</method>
+
+Style 2: The following method element refers to all the create
+methods of the EmployeeService bean's home interface(s).
+
+<method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>create</method-name>
+</method>
+
+
+Style 3: The following method element refers to the
+create(String firstName, String LastName) method of the
+EmployeeService bean's home interface(s).
+
+<method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+</method>
+
+
+The following example illustrates a Style 3 element with
+more complex parameter types. The method
+foobar(char s, int i, int[] iar, mypackage.MyClass mycl,
+mypackage.MyClass[][] myclaar) would be specified as:
+
+<method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>foobar</method-name>
+ <method-params>
+ <method-param>char</method-param>
+ <method-param>int</method-param>
+ <method-param>int[]</method-param>
+ <method-param>mypackage.MyClass</method-param>
+ <method-param>mypackage.MyClass[][]</method-param>
+ </method-params>
+</method>
+
+
+The optional method-intf element can be used when it becomes necessary
+to differentiate between a method that is multiply defined across the
+enterprise bean's home and component interfaces with the same name and
+signature.
+
+
+For example, the method element
+
+<method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>Remote</method-intf>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+</method>
+
+
+can be used to differentiate the create(String, String) method defined
+in the remote interface from the create(String, String) method defined
+in the remote home interface, which would be defined as
+
+
+<method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>Home</method-intf>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+</method>
+
+and the create method that is defined in the local home interface
+which would be defined as
+
+<method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>LocalHome</method-intf>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+</method>
+
+
+The method-intf element can be used with all three Styles of the
+method element usage. For example, the following method element
+example could be used to refer to all the methods of the
+EmployeeService bean's remote home interface.
+
+
+<method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>Home</method-intf>
+ <method-name>*</method-name>
+</method>
+
+-->
+<!ELEMENT method (description?, ejb-name, method-intf?, method-name,
+method-params?)>
+
+<!--
+
+The method-intf element allows a method element to differentiate
+between the methods with the same name and signature that are multiply
+defined across the component and home interfaces (e.g, in both an
+enterprise bean's remote and local interfaces; in both an enterprise bean's
+home and remote interfaces, etc.)
+
+The method-intf element must be one of the following:
+
+ <method-intf>Home</method-intf>
+ <method-intf>Remote</method-intf>
+ <method-intf>LocalHome</method-intf>
+ <method-intf>Local</method-intf>
+
+Used in: method, query-method
+-->
+<!ELEMENT method-intf (#PCDATA)>
+
+<!--
+The method-name element contains a name of an enterprise bean method
+or the asterisk (*) character. The asterisk is used when the element
+denotes all the methods of an enterprise bean's component and home
+interfaces.
+
+Used in: method, query-method
+-->
+<!ELEMENT method-name (#PCDATA)>
+
+<!--
+The method-param element contains the fully-qualified Java type name
+of a method parameter.
+
+Used in: method-params
+-->
+<!ELEMENT method-param (#PCDATA)>
+
+<!--
+The method-params element contains a list of the fully-qualified Java
+type names of the method parameters.
+
+Used in: method, query-method
+-->
+<!ELEMENT method-params (method-param*)>
+
+<!--
+
+The method-permission element specifies that one or more security
+roles are allowed to invoke one or more enterprise bean methods. The
+method-permission element consists of an optional description, a list
+of security role names or an indicator to state that the method is
+unchecked for authorization, and a list of method elements.
+
+The security roles used in the method-permission element must be
+defined in the security-role element of the deployment descriptor, and
+the methods must be methods defined in the enterprise bean's component
+and/or home interfaces.
+
+
+Used in: assembly-descriptor
+-->
+<!ELEMENT method-permission (description?, (role-name+|unchecked), method+)>
+
+<!--
+The multiplicity element describes the multiplicity of the role that
+participates in a relation.
+
+The multiplicity element must be one of the two following:
+
+ <multiplicity>One</multiplicity>
+ <multiplicity>Many</multiplicity>
+
+Used in: ejb-relationship-role
+-->
+<!ELEMENT multiplicity (#PCDATA)>
+
+<!--
+The persistence-type element specifies an entity bean's persistence
+management type.
+
+The persistence-type element must be one of the two following:
+
+ <persistence-type>Bean</persistence-type>
+ <persistence-type>Container</persistence-type>
+
+Used in: entity
+-->
+<!ELEMENT persistence-type (#PCDATA)>
+
+<!--
+The prim-key-class element contains the fully-qualified name of an
+entity bean's primary key class.
+
+If the definition of the primary key class is deferred to deployment
+time, the prim-key-class element should specify java.lang.Object.
+
+Used in: entity
+
+Examples:
+
+ <prim-key-class>java.lang.String</prim-key-class>
+
+ <prim-key-class>com.wombat.empl.EmployeeID</prim-key-class>
+
+ <prim-key-class>java.lang.Object</prim-key-class>
+
+-->
+<!ELEMENT prim-key-class (#PCDATA)>
+
+<!--
+The primkey-field element is used to specify the name of the primary
+key field for an entity with container-managed persistence.
+
+The primkey-field must be one of the fields declared in the cmp-field
+element, and the type of the field must be the same as the primary key
+type.
+
+The primkey-field element is not used if the primary key maps to
+multiple container-managed fields (i.e. the key is a compound key). In
+this case, the fields of the primary key class must be public, and
+their names must correspond to the field names of the entity bean
+class that comprise the key.
+
+Used in: entity
+
+Example:
+
+ <primkey-field>EmployeeId</primkey-field>
+
+-->
+<!ELEMENT primkey-field (#PCDATA)>
+
+<!--
+The query element is used to specify a finder or select query. It
+contains
+ - an optional description of the query
+ - the specification of the finder or select
+ method it is used by
+ - an optional indicator which specifies how the abstract
+ schema type instance(s) must be mapped when results are
+ returned.
+ - the EJB QL query string that defines the query.
+
+Queries that are expressible in EJB QL must use the ejb-ql element to
+specify the query. If a query is not expressible in EJB QL, the
+description element should be used to describe the semantics of the
+query and the ejb-ql element should be empty.
+
+The result-type-mapping is an optional element. It can only be present
+when the query-method describes an ejbSelect query. The default value
+for the result-type-mapping element is "Local".
+
+
+Used in: entity
+-->
+<!ELEMENT query (description?, query-method, result-type-mapping?, ejb-ql)>
+
+<!--
+The query-method element is used to specify the method for a finder or
+select query.
+
+The method-name element specifies the name of a finder or select
+method in the entity bean's implementation class.
+
+Each method-param must be defined for a query-method using the
+method-params element.
+
+Used in: query
+
+Example:
+
+<query>
+ <description>Method finds large orders</description>
+ <query-method>
+ <method-name>findLargeOrders</method-name>
+ <method-params></method-params>
+ </query-method>
+ <ejb-ql>SELECT ENTITY(o) FROM Order o WHERE o.amount > 1000</ejb-ql>
+</query>
+
+-->
+<!ELEMENT query-method (method-name, method-intf?, method-params)>
+
+<!--
+The reentrant element specifies whether an entity bean is reentrant or
+not.
+
+The reentrant element must be one of the two following:
+
+ <reentrant>True</reentrant>
+ <reentrant>False</reentrant>
+
+Used in: entity
+-->
+<!ELEMENT reentrant (#PCDATA)>
+
+<!--
+
+The relationship-role-source element designates the source of a role
+that participates in a relationship. A relationship-role-source
+element uniquely identifies an entity bean.
+
+Used in: ejb-relationship-role
+-->
+<!ELEMENT relationship-role-source (description?, ejb-name)>
+
+<!--
+The relationships element describes the relationships in which
+entity beans with container managed persistence participate. The
+relationships element contains an optional description; and a list of
+ejb-relation elements, which specify the container managed
+relationships.
+
+
+Used in: ejb-jar
+-->
+<!ELEMENT relationships (description?, ejb-relation+)>
+
+<!--
+The remote element contains the fully-qualified name of the enterprise
+bean's remote interface.
+
+Used in: ejb-ref, entity, session
+
+Example:
+
+<remote>com.wombat.empl.EmployeeService</remote>
+-->
+<!ELEMENT remote (#PCDATA)>
+
+<!--
+The res-auth element specifies whether the enterprise bean code signs
+on programmatically to the resource manager, or whether the Container
+will sign on to the resource manager on behalf of the enterprise bean. In the
+latter case, the Container uses information that is supplied by the
+Deployer.
+
+The value of this element must be one of the two following:
+
+ <res-auth>Application</res-auth>
+ <res-auth>Container</res-auth>
+
+Used in: resource-ref
+-->
+<!ELEMENT res-auth (#PCDATA)>
+
+<!--
+The res-ref-name element specifies the name of a resource manager
+connection factory reference. The name is a JNDI name relative to the
+java:comp/env context. The name must be unique within an enterprise bean.
+
+Used in: resource-ref
+-->
+<!ELEMENT res-ref-name (#PCDATA)>
+
+<!--
+The res-sharing-scope element specifies whether connections obtained
+through the given resource manager connection factory reference can be
+shared. The value of this element, if specified, must be one of the
+two following:
+
+ <res-sharing-scope>Shareable</res-sharing-scope>
+ <res-sharing-scope>Unshareable</res-sharing-scope>
+
+The default value is Shareable.
+
+Used in: resource-ref
+-->
+<!ELEMENT res-sharing-scope (#PCDATA)>
+
+<!--
+The res-type element specifies the type of the data source. The type
+is specified by the fully qualified Java language class or interface
+expected to be implemented by the data source.
+
+Used in: resource-ref
+-->
+<!ELEMENT res-type (#PCDATA)>
+
+<!--
+The resource-env-ref element contains a declaration of an enterprise bean's
+reference to an administered object associated with a resource
+in the enterprise bean's environment. It consists of an optional
+description, the resource environment reference name, and an
+indication of the resource environment reference type expected by
+the enterprise bean code.
+
+Used in: entity, message-driven, session
+
+Example:
+
+<resource-env-ref>
+ <resource-env-ref-name>jms/StockQueue</resource-env-ref-name>
+ <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
+</resource-env-ref>
+-->
+<!ELEMENT resource-env-ref (description?, resource-env-ref-name,
+ resource-env-ref-type)>
+
+<!--
+The resource-env-ref-name element specifies the name of a resource
+environment reference; its value is the environment entry name used in
+the enterprise bean code. The name is a JNDI name relative to the
+java:comp/env context and must be unique within an enterprise bean.
+
+Used in: resource-env-ref
+-->
+<!ELEMENT resource-env-ref-name (#PCDATA)>
+
+<!--
+The resource-env-ref-type element specifies the type of a resource
+environment reference. It is the fully qualified name of a Java
+language class or interface.
+
+Used in: resource-env-ref
+-->
+<!ELEMENT resource-env-ref-type (#PCDATA)>
+
+<!--
+The resource-ref element contains a declaration of an enterprise bean's
+reference to an external resource. It consists of an optional
+description, the resource manager connection factory reference name,
+the indication of the resource manager connection factory type
+expected by the enterprise bean code, the type of authentication
+(Application or Container), and an optional specification of the
+shareability of connections obtained from the resource (Shareable or
+Unshareable).
+
+Used in: entity, message-driven, session
+
+Example:
+
+ <resource-ref>
+ <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
+ <res-type>javax.sql.DataSource</res-type>
+ <res-auth>Container</res-auth>
+ <res-sharing-scope>Shareable</res-sharing-scope>
+ </resource-ref>
+-->
+<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth,
+ res-sharing-scope?)>
+
+<!--
+
+The result-type-mapping element designates the mapping of the return
+value(s) of an select query.
+
+When the result type of a select query is an abstract schema type, the
+value of this element determines whether the select
+query returns remote or local entity objects.
+
+The result-type-mapping element must have one of the following:
+
+ <result-type-mapping>Local</result-type-mapping>
+ <result-type-mapping>Remote</result-type-mapping>
+
+Used in: query
+-->
+<!ELEMENT result-type-mapping (#PCDATA)>
+
+<!--
+The role-link element is a reference to a defined security role. The
+role-link element must contain the name of one of the security roles
+defined in the security-role elements.
+
+Used in: security-role-ref
+-->
+<!ELEMENT role-link (#PCDATA)>
+
+<!--
+The role-name element contains the name of a security role.
+
+The name must conform to the lexical rules for an NMTOKEN.
+
+Used in: method-permission, run-as, security-role, security-role-ref
+-->
+<!ELEMENT role-name (#PCDATA)>
+
+<!--
+The run-as element specifies the run-as identity to be used for the
+execution of the enterprise bean. It contains an optional description, and
+the name of a security role.
+
+Used in: security-identity
+-->
+<!ELEMENT run-as (description?, role-name)>
+
+<!--
+
+The security-identity element specifies whether the caller's
+security identity is to be used for the execution of the methods of
+the enterprise bean or whether a specific run-as identity is to be
+used. It contains an optional description and a specification of the
+security identity to be used.
+
+Used in: entity, message-driven, session
+-->
+<!ELEMENT security-identity (description?, (use-caller-identity|run-as))>
+
+<!--
+The security-role element contains the definition of a security
+role. The definition consists of an optional description of the
+security role, and the security role name.
+
+Used in: assembly-descriptor
+
+Example:
+
+ <security-role>
+ <description>
+ This role includes all employees who are authorized
+ to access the employee service application.
+ </description>
+ <role-name>employee</role-name>
+ </security-role>
+-->
+<!ELEMENT security-role (description?, role-name)>
+
+<!--
+The security-role-ref element contains the declaration of a security
+role reference in the enterprise bean's code. The declaration consists
+of an optional description, the security role name used in the code,
+and an optional link to a security role. If the security role is not
+specified, the Deployer must choose an appropriate security role.
+
+The value of the role-name element must be the String used as the
+parameter to the EJBContext.isCallerInRole(String roleName) method
+or the HttpServletRequest.isUserInRole(String role) method.
+
+Used in: entity, session
+
+-->
+<!ELEMENT security-role-ref (description?, role-name, role-link?)>
+
+<!--
+The session element declares an session bean. The declaration consists
+of:
+ - an optional description
+ - an optional display name
+ - an optional small icon file name
+ - an optional large icon file name
+ - a name assigned to the enterprise bean
+ in the deployment description
+ - the names of the session bean's remote home and
+ remote interfaces, if any
+ - the names of the session bean's local home and
+ local interfaces, if any
+ - the session bean's implementation class
+ - the session bean's state management type
+ - the session bean's transaction management type
+ - an optional declaration of the bean's environment entries
+ - an optional declaration of the bean's EJB references
+ - an optional declaration of the bean's local EJB references
+ - an optional declaration of the security role references
+ - an optional declaration of the security identity to be
+ used for the execution of the bean's methods
+ - an optional declaration of the bean's resource manager
+ connection factory references
+ - an optional declaration of the bean's resource environment
+ references.
+
+The elements that are optional are "optional" in the sense that they
+are omitted when if lists represented by them are empty.
+
+Either both the local-home and the local elements or both the
+home and the remote elements must be specified for the session bean.
+
+Used in: enterprise-beans
+-->
+<!ELEMENT session (description?, display-name?, small-icon?,
+large-icon?, ejb-name, home?, remote?, local-home? , local?,
+ejb-class, session-type, transaction-type, env-entry*, ejb-ref*,
+ejb-local-ref*, security-role-ref*, security-identity?, resource-ref*,
+resource-env-ref*)>
+
+<!--
+The session-type element describes whether the session bean is a
+stateful session or stateless session.
+
+The session-type element must be one of the two following:
+
+ <session-type>Stateful</session-type>
+ <session-type>Stateless</session-type>
+-->
+<!ELEMENT session-type (#PCDATA)>
+
+<!--
+The small-icon element contains the name of a file
+containing a small (16 x 16) icon image. The file
+name is a relative path within the enterprise bean's
+ejb-jar file.
+
+The image may be either in the JPEG or GIF format.
+The icon can be used by tools.
+
+Used in: ejb-jar, entity, message-driven, session
+
+Example:
+
+<small-icon>employee-service-icon16x16.jpg</small-icon>
+-->
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+The subscription-durability element specifies whether a JMS topic
+subscription is intended to be durable or nondurable.
+
+The subscription-durability element must be one of the two following:
+
+ <subscription-durability>Durable</subscription-durability>
+ <subscription-durability>NonDurable</subscription-durability>
+
+Used in: message-driven-destination
+-->
+<!ELEMENT subscription-durability (#PCDATA)>
+
+<!--
+The trans-attribute element specifies how the container must manage
+the transaction boundaries when delegating a method invocation to an
+enterprise bean's business method.
+
+The value of trans-attribute must be one of the following:
+
+
+ <trans-attribute>NotSupported</trans-attribute>
+ <trans-attribute>Supports</trans-attribute>
+ <trans-attribute>Required</trans-attribute>
+ <trans-attribute>RequiresNew</trans-attribute>
+ <trans-attribute>Mandatory</trans-attribute>
+ <trans-attribute>Never</trans-attribute>
+
+Used in: container-transaction
+-->
+<!ELEMENT trans-attribute (#PCDATA)>
+
+<!--
+The transaction-type element specifies an enterprise bean's
+transaction management type.
+
+The transaction-type element must be one of the two following:
+
+ <transaction-type>Bean</transaction-type>
+ <transaction-type>Container</transaction-type>
+
+Used in: message-driven, session
+-->
+<!ELEMENT transaction-type (#PCDATA)>
+
+<!--
+The unchecked element specifies that a method is not checked for authorization
+by the container prior to invocation of the method.
+
+Used in: method-permission
+-->
+<!ELEMENT unchecked EMPTY>
+
+<!--
+
+The use-caller-identity element specifies that the caller's security
+identity be used as the security identity for the execution of the
+enterprise bean's methods.
+
+Used in: security-identity
+-->
+<!ELEMENT use-caller-identity EMPTY>
+
+<!--
+The ID mechanism is to allow tools that produce additional deployment
+information (i.e., information beyond the standard deployment
+descriptor information) to store the non-standard information in a
+separate file, and easily refer from these tool-specific files to the
+information in the standard deployment descriptor.
+
+Tools are not allowed to add the non-standard information into the
+standard deployment descriptor.
+-->
+
+<!ATTLIST abstract-schema-name id ID #IMPLIED>
+<!ATTLIST acknowledge-mode id ID #IMPLIED>
+<!ATTLIST assembly-descriptor id ID #IMPLIED>
+<!ATTLIST cascade-delete id ID #IMPLIED>
+<!ATTLIST cmp-field id ID #IMPLIED>
+<!ATTLIST cmp-version id ID #IMPLIED>
+<!ATTLIST cmr-field id ID #IMPLIED>
+<!ATTLIST cmr-field-name id ID #IMPLIED>
+<!ATTLIST cmr-field-type id ID #IMPLIED>
+<!ATTLIST container-transaction id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST destination-type id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST ejb-class id ID #IMPLIED>
+<!ATTLIST ejb-client-jar id ID #IMPLIED>
+<!ATTLIST ejb-jar id ID #IMPLIED>
+<!ATTLIST ejb-link id ID #IMPLIED>
+<!ATTLIST ejb-local-ref id ID #IMPLIED>
+<!ATTLIST ejb-name id ID #IMPLIED>
+<!ATTLIST ejb-ql id ID #IMPLIED>
+<!ATTLIST ejb-ref id ID #IMPLIED>
+<!ATTLIST ejb-ref-name id ID #IMPLIED>
+<!ATTLIST ejb-ref-type id ID #IMPLIED>
+<!ATTLIST ejb-relation id ID #IMPLIED>
+<!ATTLIST ejb-relation-name id ID #IMPLIED>
+<!ATTLIST ejb-relationship-role id ID #IMPLIED>
+<!ATTLIST ejb-relationship-role-name id ID #IMPLIED>
+<!ATTLIST enterprise-beans id ID #IMPLIED>
+<!ATTLIST entity id ID #IMPLIED>
+<!ATTLIST env-entry id ID #IMPLIED>
+<!ATTLIST env-entry-name id ID #IMPLIED>
+<!ATTLIST env-entry-type id ID #IMPLIED>
+<!ATTLIST env-entry-value id ID #IMPLIED>
+<!ATTLIST exclude-list id ID #IMPLIED>
+<!ATTLIST field-name id ID #IMPLIED>
+<!ATTLIST home id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST local id ID #IMPLIED>
+<!ATTLIST local-home id ID #IMPLIED>
+<!ATTLIST message-driven id ID #IMPLIED>
+<!ATTLIST message-driven-destination id ID #IMPLIED>
+<!ATTLIST message-selector id ID #IMPLIED>
+<!ATTLIST method id ID #IMPLIED>
+<!ATTLIST method-intf id ID #IMPLIED>
+<!ATTLIST method-name id ID #IMPLIED>
+<!ATTLIST method-param id ID #IMPLIED>
+<!ATTLIST method-params id ID #IMPLIED>
+<!ATTLIST method-permission id ID #IMPLIED>
+<!ATTLIST multiplicity id ID #IMPLIED>
+<!ATTLIST persistence-type id ID #IMPLIED>
+<!ATTLIST prim-key-class id ID #IMPLIED>
+<!ATTLIST primkey-field id ID #IMPLIED>
+<!ATTLIST query id ID #IMPLIED>
+<!ATTLIST query-method id ID #IMPLIED>
+<!ATTLIST reentrant id ID #IMPLIED>
+<!ATTLIST relationship-role-source id ID #IMPLIED>
+<!ATTLIST relationships id ID #IMPLIED>
+<!ATTLIST remote id ID #IMPLIED>
+<!ATTLIST res-auth id ID #IMPLIED>
+<!ATTLIST res-ref-name id ID #IMPLIED>
+<!ATTLIST res-sharing-scope id ID #IMPLIED>
+<!ATTLIST res-type id ID #IMPLIED>
+<!ATTLIST resource-env-ref id ID #IMPLIED>
+<!ATTLIST resource-env-ref-name id ID #IMPLIED>
+<!ATTLIST resource-env-ref-type id ID #IMPLIED>
+<!ATTLIST resource-ref id ID #IMPLIED>
+<!ATTLIST result-type-mapping id ID #IMPLIED>
+<!ATTLIST role-link id ID #IMPLIED>
+<!ATTLIST role-name id ID #IMPLIED>
+<!ATTLIST run-as id ID #IMPLIED>
+<!ATTLIST security-identity id ID #IMPLIED>
+<!ATTLIST security-role id ID #IMPLIED>
+<!ATTLIST security-role-ref id ID #IMPLIED>
+<!ATTLIST session id ID #IMPLIED>
+<!ATTLIST session-type id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
+<!ATTLIST subscription-durability id ID #IMPLIED>
+<!ATTLIST trans-attribute id ID #IMPLIED>
+<!ATTLIST transaction-type id ID #IMPLIED>
+<!ATTLIST unchecked id ID #IMPLIED>
+<!ATTLIST use-caller-identity id ID #IMPLIED>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,25 @@
+<!--
+This is the XML DTD for the JAWS deployment descriptor.
+-->
+
+<!ELEMENT jaws (datasource,type-mapping,enterprise-beans)>
+
+<!ELEMENT datasource (#PCDATA)>
+
+<!ELEMENT type-mapping (#PCDATA)>
+
+<!ELEMENT enterprise-beans (entity*)>
+
+<!ELEMENT entity (ejb-name,datasource?,cmp-field*,finder*)>
+
+<!ELEMENT ejb-name (#PCDATA)>
+
+<!ELEMENT datasource (#PCDATA)>
+
+<!ELEMENT finder (name,query,order?)>
+
+<!ELEMENT name (#PCDATA)>
+
+<!ELEMENT query (#PCDATA)>
+
+<!ELEMENT order (#PCDATA)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws_2_4.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws_2_4.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws_2_4.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,122 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+This is the XML DTD for the JAWS deployment descriptor.
+ <!DOCTYPE jaws PUBLIC
+ "-//JBoss//DTD JAWS 2.4//EN"
+ "http://www.jboss.org/j2ee/dtd/jaws_2_4.dtd">
+-->
+<!-- The jaws element is always the root (document) node of the jaws.xml
+ deployment descriptor or the standardjaws.xml defaults document. All elements
+ are declared as optional - if not given in jaws.xml, defaults will be read
+ from standardjaws.xml -->
+<!ELEMENT jaws (datasource? , type-mapping? , debug? , default-entity? , enterprise-beans? , type-mappings?)>
+
+<!-- the datasource element is used to indicate to JAWS which datasource
+ should be used for persistence of the CMP entities in this ejb-jar. It
+ should be the datasource named as it appears in jboss' global naming
+ context. The default is java:/DefaultDS
+
+ Beans are also allowed to specify datasources at bean level and will override this datasource if specified.
+
+Used in: jaws, entity
+ -->
+<!ELEMENT datasource (#PCDATA)>
+
+<!-- the type-mapping element is used to indicate to JAWS which set of mappings
+ from java types to jdbc and SQL types to be used for CMP beans in this jar.
+ type-mappings are defined withing the type-mappings element with a type-mapping
+ element that carries a separate meaning: This DTD wil not parse! -->
+<!ELEMENT type-mapping (#PCDATA)>
+
+<!ELEMENT debug (#PCDATA)>
+
+<!ELEMENT default-entity (create-table , remove-table , tuned-updates , read-only , pk-constraint? , select-for-update? , time-out)>
+
+<!ELEMENT create-table (#PCDATA)>
+
+<!ELEMENT remove-table (#PCDATA)>
+
+<!ELEMENT tuned-updates (#PCDATA)>
+
+<!ELEMENT read-only (#PCDATA)>
+
+<!ELEMENT pk-constraint (#PCDATA)>
+
+<!ELEMENT select-for-update (#PCDATA)>
+
+<!ELEMENT time-out (#PCDATA)>
+
+<!-- the enterpris-beans tag contains overridden attribute mappings for any
+ CMP bean in this ejb-jar that requires non-default column mapping behavior -->
+<!ELEMENT enterprise-beans (entity*)>
+
+<!-- the entity element defines a non-default column mapping for a CMP entity
+ bean in this ejb-jar. This includes query specifications for any finders that
+ either do not correspond to a single cmp-field or that require a specific
+ ordering. it must contain an ejb-name element, can contain 0 or more cmp-field
+ elements and my contain 0 or more finder elements.
+ Other options include:
+ read-ahead: When a finder is called, load all data for all entities.
+ read-only: Do not persist any changes to the bean's state.
+ table-name: Name of the corresponding table.
+ tuned-updates: emit 'update' SQL statements that update only changed fields.
+ create-table: On deploy, create the table if it doesn't exist.
+ remove-table: On undeploy, drop the table from the database (with _all_ _data_!!!
+ select-for-update: On loading the bean, use the 'select ... for update' syntax,
+ locking the row.
+ pk-constraint: If create-table is on, create it with a primary key.
+ time-out: For read-only only, re-load entity after time-out
+-->
+<!ELEMENT entity (ejb-name , datasource? , cmp-field* , finder* , read-ahead? , read-only? , table-name? , tuned-updates? , create-table? , remove-table? , select-for-update? , time-out? , pk-constraint?)>
+
+<!-- ejb-name within an entity element must contain the ejb-name as specified
+ in ejb-jar.xml. -->
+<!ELEMENT ejb-name (#PCDATA)>
+
+<!ELEMENT cmp-field (field-name , column-name , (jdbc-type , sql-type)?)>
+
+<!ELEMENT field-name (#PCDATA)>
+
+<!ELEMENT column-name (#PCDATA)>
+
+<!-- the finder element overrides JAWS default behavior for a finder, or
+ specifies JAWS behavior for finders requiring multi-column where clauses or
+ a specific ordering. it must contain name and query elements and my contain
+ 1 order element.
+ After JBoss version 2.3, it may contain a read-ahead element indicating whether
+ or not all data for the entities selected should be loaded immediatly. Note
+ that JAWS/JBoss cannot guarentee serializable transactions with the read-ahead
+ option!-->
+<!ELEMENT finder (name , query , order? , read-ahead?)>
+
+<!-- the name within a finder element must contain the name of the finder
+ method from the bean's home interface -->
+<!ELEMENT name (#PCDATA)>
+
+<!-- the query element must contain the where clause that will select the
+ proper rows to be returned by the finder. If this query begins with an
+ inner join clause, it may specify multiple tables. -->
+<!ELEMENT query (#PCDATA)>
+
+<!-- the order element should contain a SQL order by clause (without the
+ initial 'order by' verb!) that should be used to order the results of the
+ query for the finder -->
+<!ELEMENT order (#PCDATA)>
+
+<!ELEMENT read-ahead (#PCDATA)>
+
+<!ELEMENT table-name (#PCDATA)>
+
+<!ELEMENT type-mappings (type-mapping-definition*)>
+
+<!ELEMENT type-mapping-definition (name , mapping*)>
+
+<!ELEMENT mapping (java-type , jdbc-type , sql-type)>
+
+<!ELEMENT java-type (#PCDATA)>
+
+<!ELEMENT jdbc-type (#PCDATA)>
+
+<!ELEMENT sql-type (#PCDATA)>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws_3_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws_3_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jaws_3_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,121 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+This is the XML DTD for the JAWS deployment descriptor.
+ <!DOCTYPE jaws PUBLIC
+ "-//JBoss//DTD JAWS 3.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jaws_3_0.dtd">
+-->
+<!-- The jaws element is always the root (document) node of the jaws.xml
+ deployment descriptor or the standardjaws.xml defaults document. All elements
+ are declared as optional - if not given in jaws.xml, defaults will be read
+ from standardjaws.xml -->
+<!ELEMENT jaws (datasource? , type-mapping? , default-entity? , enterprise-beans? , type-mappings?)>
+
+<!-- the datasource element is used to indicate to JAWS which datasource
+ should be used for persistence of the CMP entities in this ejb-jar. It
+ should be the datasource named as it appears in jboss' global naming
+ context. The default is java:/DefaultDS
+
+ Beans are also allowed to specify datasources at bean level and will override this datasource if specified.
+
+Used in: jaws, entity
+ -->
+<!ELEMENT datasource (#PCDATA)>
+
+<!-- the type-mapping element is used to indicate to JAWS which set of mappings
+ from java types to jdbc and SQL types to be used for CMP beans in this jar.
+ type-mappings are defined withing the type-mappings element with a type-mapping
+ element that carries a separate meaning: This DTD wil not parse! -->
+<!ELEMENT type-mapping (#PCDATA)>
+
+<!ELEMENT default-entity (create-table , remove-table , tuned-updates , read-only , pk-constraint? , row-locking? , time-out)>
+
+<!ELEMENT create-table (#PCDATA)>
+
+<!ELEMENT remove-table (#PCDATA)>
+
+<!ELEMENT tuned-updates (#PCDATA)>
+
+<!ELEMENT read-only (#PCDATA)>
+
+<!ELEMENT pk-constraint (#PCDATA)>
+
+<!ELEMENT row-locking (#PCDATA)>
+
+<!ELEMENT time-out (#PCDATA)>
+
+<!-- the enterpris-beans tag contains overridden attribute mappings for any
+ CMP bean in this ejb-jar that requires non-default column mapping behavior -->
+<!ELEMENT enterprise-beans (entity*)>
+
+<!-- the entity element defines a non-default column mapping for a CMP entity
+ bean in this ejb-jar. This includes query specifications for any finders that
+ either do not correspond to a single cmp-field or that require a specific
+ ordering. it must contain an ejb-name element, can contain 0 or more cmp-field
+ elements and my contain 0 or more finder elements.
+ Other options include:
+ read-ahead: When a finder is called, load all data for all entities.
+ read-only: Do not persist any changes to the bean's state.
+ table-name: Name of the corresponding table.
+ tuned-updates: emit 'update' SQL statements that update only changed fields.
+ create-table: On deploy, create the table if it doesn't exist.
+ remove-table: On undeploy, drop the table from the database (with _all_ _data_!!!
+ row-locking: On loading the bean, row lock it
+ pk-constraint: If create-table is on, create it with a primary key.
+ time-out: For read-only only, re-load entity after time-out
+-->
+<!ELEMENT entity (ejb-name , datasource? , cmp-field* , finder* , read-ahead? , read-only? , table-name? , tuned-updates? , create-table? , remove-table? , row-locking? , time-out? , pk-constraint?)>
+
+<!-- ejb-name within an entity element must contain the ejb-name as specified
+ in ejb-jar.xml. -->
+<!ELEMENT ejb-name (#PCDATA)>
+
+<!ELEMENT cmp-field (field-name , column-name , (jdbc-type , sql-type)? , nullable?)>
+
+<!ELEMENT field-name (#PCDATA)>
+
+<!ELEMENT column-name (#PCDATA)>
+
+<!ELEMENT nullable (#PCDATA)>
+
+<!-- the finder element overrides JAWS default behavior for a finder, or
+ specifies JAWS behavior for finders requiring multi-column where clauses or
+ a specific ordering. it must contain name and query elements and my contain
+ 1 order element.
+ After JBoss version 2.3, it may contain a read-ahead element indicating whether
+ or not all data for the entities selected should be loaded immediatly. Note
+ that JAWS/JBoss cannot guarentee serializable transactions with the read-ahead
+ option!-->
+<!ELEMENT finder (name , query , order? , read-ahead?)>
+
+<!-- the name within a finder element must contain the name of the finder
+ method from the bean's home interface -->
+<!ELEMENT name (#PCDATA)>
+
+<!-- the query element must contain the where clause that will select the
+ proper rows to be returned by the finder. If this query begins with an
+ inner join clause, it may specify multiple tables. -->
+<!ELEMENT query (#PCDATA)>
+
+<!-- the order element should contain a SQL order by clause (without the
+ initial 'order by' verb!) that should be used to order the results of the
+ query for the finder -->
+<!ELEMENT order (#PCDATA)>
+
+<!ELEMENT read-ahead (#PCDATA)>
+
+<!ELEMENT table-name (#PCDATA)>
+
+<!ELEMENT type-mappings (type-mapping-definition*)>
+
+<!ELEMENT type-mapping-definition (name , mapping*)>
+
+<!ELEMENT mapping (java-type , jdbc-type , sql-type)>
+
+<!ELEMENT java-type (#PCDATA)>
+
+<!ELEMENT jdbc-type (#PCDATA)>
+
+<!ELEMENT sql-type (#PCDATA)>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_3_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_3_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_3_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,41 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss specific elements for ears.
+$Id: jboss-app_3_0.dtd 20476 2004-04-17 13:29:24Z tdiesler $
+
+DOCTYPE jboss-app
+ PUBLIC "-//JBoss//DTD J2EE Application 1.3//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-app_3_0.dtd"
+-->
+
+<!-- The jboss-app element is the root element.
+-->
+<!ELEMENT jboss-app (loader-repository?, module*)>
+
+<!-- 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.
+
+ Example:
+ <loader-repository>jboss.test:loader=cts-cmp2v1-sar.ear</loader-repository>
+-->
+<!ELEMENT loader-repository (#PCDATA)>
+<!-- The loaderRepositoryClass attribute gives the classname loader-repository
+implementation.
+-->
+<!ATTLIST loader-repository loaderRepositoryClass CDATA #IMPLIED>
+
+<!-- The module element is used to specify a jboss specific module archive.
+-->
+<!ELEMENT module (service)>
+
+<!-- The service element specifies a service archive (SAR) to deploy.
+
+Example:
+ <module>
+ <service>external.sar</service>
+ </module>
+-->
+<!ELEMENT service (#PCDATA)>
+
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_3_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_3_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_3_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,76 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss 3.2.x specific elements for ears.
+$Id: jboss-app_3_2.dtd 22964 2004-08-14 00:35:40Z starksm $
+
+DOCTYPE jboss-app
+ PUBLIC "-//JBoss//DTD J2EE Application 1.3V2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-app_3_2.dtd"
+-->
+
+<!-- The jboss-app element is the root element.
+-->
+<!ELEMENT jboss-app (loader-repository?, jmx-name?, module*)>
+
+<!-- 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)>
+
+<!-- The module element is used to specify a jboss specific module archive.
+-->
+<!ELEMENT module (service | har)>
+
+<!-- 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)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_4_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_4_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_4_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,145 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss 4.x specific elements for ears.
+$Id: jboss-app_4_0.dtd 56293 2006-08-26 12:42:15Z vicky.kak at jboss.com $
+
+DOCTYPE jboss-app
+ PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd"
+-->
+
+<!-- The jboss-app element is the root element.
+-->
+<!ELEMENT jboss-app (module-order?,security-domain?, unauthenticated-principal?,
+ loader-repository?, jmx-name?, module*, security-role*)>
+
+<!--
+ 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)>
+
+<!-- The module element is used to specify a jboss specific module archive.
+-->
+<!ELEMENT module (service | har)>
+<!-- Allow the module to have a unique id -->
+<!ATTLIST module id ID #IMPLIED>
+
+<!-- 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 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)>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_4_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_4_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-app_4_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,188 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss 4.2.x specific elements for ears.
+$Id: jboss-app_4_0.dtd 56293 2006-08-26 12:42:15Z vicky.kak at jboss.com $
+
+DOCTYPE jboss-app
+ PUBLIC "-//JBoss//DTD J2EE Application 4.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-app_4_2.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*)>
+
+<!--
+ 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)>
+
+<!-- Allow the module to have a unique id -->
+<!ATTLIST module id ID #IMPLIED>
+
+<!-- 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)>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_3_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_3_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_3_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,105 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss specific elements used to deploy an application client.
+This version applies to the JBoss 3.2.x releases and the
+j2ee-1.3 application-client_1_3.dtd.
+
+$Id: jboss-client_3_2.dtd 20476 2004-04-17 13:29:24Z tdiesler $
+
+ <!DOCTYPE jboss-client PUBLIC
+ "-//JBoss//DTD Application Client 3.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-client_3_2.dtd">
+-->
+
+<!-- The jboss-client element is the root element.
+-->
+<!ELEMENT jboss-client (jndi-name, ejb-ref*, resource-ref*, resource-env-ref*)>
+
+<!-- The required jndi-name element specifies the JNDI name of a deployed
+object. It is used in two different contexts:
+
+1. In jboss-client to specify the location in JNDI on the server side which
+contains the ObjectFactory which handles the java:comp/env enterprise naming
+context (ENC) on the client. The application client code maps its ENC to the
+approriate client jar deployment jboss-client/jndi-name value by specifying this
+location via the j2ee.clientName IntialContext environment property, or as a
+system property. The prototype code for creating the client side InitialContext
+is:
+
+ Properties env = new Properties();
+ env.setProperty(Context.INITIAL_CONTEXT_FACTORY,
+ "org.jnp.interfaces.NamingContextFactory");
+ env.setProperty(Context.URL_PKG_PREFIXES, "org.jboss.naming.client");
+ env.setProperty(Context.PROVIDER_URL, "jnp://somehost:1099");
+ env.setProperty("j2ee.clientName", "test-client");
+ InitialContext ctx = new InitialContext(env);
+ Context enc = (Context) ctx.lookup("java:comp/env");
+
+2. In resource-ref, resource-env-ref, ejb-ref to specify the the actual server
+side binding location of the target the client ENC binding will link to via a
+JNDI LinkRef.
+
+Used in: jboss-client, resource-ref, resource-env-ref, ejb-ref
+-->
+<!ELEMENT jndi-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-ref-name element gives the ENC relative name used
+in the client code.
+
+Used in: ejb-ref
+-->
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+<!--The resource-ref element maps from the client 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 application-client.xml
+res-ref-name element to which this mapping applies.
+-->
+<!ELEMENT res-ref-name (#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 application-client.xml
+resource-env-ref-name element to which this mapping applies.
+-->
+<!ELEMENT resource-env-ref-name (#PCDATA)>
+
+<!-- The res-url element value is a URL string.
+
+ Used in: resource-ref
+-->
+<!ELEMENT res-url (#PCDATA)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_4_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_4_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_4_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,128 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss specific elements used to deploy an application client.
+This version applies to the JBoss 4.x releases and the
+j2ee-1.4 application-client_1_4.xsd.
+
+$Id: jboss-client_4_0.dtd 61966 2007-04-01 17:05:37Z dimitris at jboss.org $
+
+ <!DOCTYPE jboss-client PUBLIC
+ "-//JBoss//DTD Application Client 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-client_4_0.dtd">
+-->
+
+<!ENTITY % service-ref PUBLIC
+ "-//JBoss//DTD Web Service Reference 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/service-ref_4_0.dtd">
+
+%service-ref;
+
+
+<!-- The jboss-client element is the root element.
+-->
+<!ELEMENT jboss-client (jndi-name, ejb-ref*, service-ref*, resource-ref*,
+ resource-env-ref*)>
+
+<!-- The required jndi-name element specifies the JNDI name of a deployed
+object. It is used in two different contexts:
+
+1. In jboss-client to specify the location in JNDI on the server side which
+contains the ObjectFactory which handles the java:comp/env enterprise naming
+context (ENC) on the client. The application client code maps its ENC to the
+approriate client jar deployment jboss-client/jndi-name value by specifying this
+location via the j2ee.clientName IntialContext environment property, or as a
+system property. The prototype code for creating the client side InitialContext
+is:
+
+ Properties env = new Properties();
+ env.setProperty(Context.INITIAL_CONTEXT_FACTORY,
+ "org.jnp.interfaces.NamingContextFactory");
+ env.setProperty(Context.URL_PKG_PREFIXES, "org.jboss.naming.client");
+ env.setProperty(Context.PROVIDER_URL, "jnp://somehost:1099");
+ env.setProperty("j2ee.clientName", "test-client");
+ InitialContext ctx = new InitialContext(env);
+ Context enc = (Context) ctx.lookup("java:comp/env");
+
+2. In resource-ref, resource-env-ref, ejb-ref to specify the the actual server
+side binding location of the target the client ENC binding will link to via a
+JNDI LinkRef.
+
+Used in: jboss-client, resource-ref, resource-env-ref, ejb-ref
+-->
+<!ELEMENT jndi-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-ref-name element gives the ENC relative name used
+in the client code.
+
+Used in: ejb-ref
+-->
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+<!--The resource-ref element maps from the client 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>url/XYZHome</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 application-client.xml
+res-ref-name element to which this mapping applies.
+-->
+<!ELEMENT res-ref-name (#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 application-client.xml
+resource-env-ref-name element to which this mapping applies.
+-->
+<!ELEMENT resource-env-ref-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)>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_4_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_4_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-client_4_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,128 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss specific elements used to deploy an application client.
+This version applies to the JBoss 4.2 releases and the
+j2ee-1.4 application-client_1_4.xsd.
+
+$Id: jboss-client_4_0.dtd 60135 2007-01-31 13:17:30Z thomas.diesler at jboss.com $
+
+ <!DOCTYPE jboss-client PUBLIC
+ "-//JBoss//DTD Application Client 4.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-client_4_2.dtd">
+-->
+
+<!ENTITY % service-ref PUBLIC
+ "-//JBoss//DTD Web Service Reference 4.2//EN"
+ "http://www.jboss.org/j2ee/dtd/service-ref_4_2.dtd">
+
+%service-ref;
+
+
+<!-- The jboss-client element is the root element.
+-->
+<!ELEMENT jboss-client (jndi-name, ejb-ref*, service-ref*, resource-ref*,
+ resource-env-ref*)>
+
+<!-- The required jndi-name element specifies the JNDI name of a deployed
+object. It is used in two different contexts:
+
+1. In jboss-client to specify the location in JNDI on the server side which
+contains the ObjectFactory which handles the java:comp/env enterprise naming
+context (ENC) on the client. The application client code maps its ENC to the
+approriate client jar deployment jboss-client/jndi-name value by specifying this
+location via the j2ee.clientName IntialContext environment property, or as a
+system property. The prototype code for creating the client side InitialContext
+is:
+
+ Properties env = new Properties();
+ env.setProperty(Context.INITIAL_CONTEXT_FACTORY,
+ "org.jnp.interfaces.NamingContextFactory");
+ env.setProperty(Context.URL_PKG_PREFIXES, "org.jboss.naming.client");
+ env.setProperty(Context.PROVIDER_URL, "jnp://somehost:1099");
+ env.setProperty("j2ee.clientName", "test-client");
+ InitialContext ctx = new InitialContext(env);
+ Context enc = (Context) ctx.lookup("java:comp/env");
+
+2. In resource-ref, resource-env-ref, ejb-ref to specify the the actual server
+side binding location of the target the client ENC binding will link to via a
+JNDI LinkRef.
+
+Used in: jboss-client, resource-ref, resource-env-ref, ejb-ref
+-->
+<!ELEMENT jndi-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-ref-name element gives the ENC relative name used
+in the client code.
+
+Used in: ejb-ref
+-->
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+<!--The resource-ref element maps from the client 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>url/XYZHome</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 application-client.xml
+res-ref-name element to which this mapping applies.
+-->
+<!ELEMENT res-ref-name (#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 application-client.xml
+resource-env-ref-name element to which this mapping applies.
+-->
+<!ELEMENT resource-env-ref-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)>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-ds_1_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-ds_1_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-ds_1_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,345 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- dtd for jboss 3.2/jca 1.0 datasource configurations (*-ds.xml), transformed
+by ConnectionFactoryTemplate.xsl
+
+DOCTYPE datasources
+ PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-ds_1_0.dtd"
+
+DOCTYPE connection-factories
+ PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-ds_1_0.dtd"
+
+$Id: jboss-ds_1_0.dtd 23958 2004-09-21 21:09:11Z starksm $
+-->
+
+<!--
+The datasources element is the root of the jdbc datasource configuration
+-->
+<!ELEMENT datasources (mbean | local-tx-datasource | xa-datasource | no-tx-datasource)*>
+
+<!-- Specify a jca-jdbc non-XADatasource (local) wrapper, using no transactions
+-->
+<!ELEMENT no-tx-datasource (jndi-name , connection-url , 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? , idle-timeout-minutes? ,
+new-connection-sql, check-valid-connection-sql, valid-connection-checker-class-name,
+exception-sorter-class-name, track-statements, prepared-statement-cache-size , depends*)>
+
+<!-- Specify a jca-jdbc non-XADatasource (local) wrapper, using local
+transactions
+-->
+<!ELEMENT local-tx-datasource (jndi-name , connection-url , 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? ,
+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? , set-tx-query-timeout , depends*)>
+
+<!-- Specify a jca-jdbc XADatasource wrapper
+-->
+<!ELEMENT xa-datasource (jndi-name , track-connection-by-tx , xa-datasource-class ,
+xa-datasource-property* , 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? ,
+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? , set-tx-query-timeout , depends*)>
+
+<!-- The JNDI name under which the DataSource wrapper will be bound. Note that
+this name is relative to the "java:/" prefix. The full JNDI name of the
+DataSource will be "java:/" + jndi-name. DataSource wrappers are bound under
+the "java:/" prefix since they are not usable outside of the server VM.
+Ex:
+<jndi-name>DefaultDS</jndi-name>
+-->
+<!ELEMENT jndi-name (#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)>
+
+<!-- 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/>
+-->
+<!ELEMENT track-connection-by-tx 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)>
+
+<!-- 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 (#PCDATA)>
+
+<!-- The number of prepared statements per connection in an LRU cache
+-->
+<!ELEMENT prepared-statement-cache-size (#PCDATA)>
+
+<!-- Whether to set the query timeout based upon the time left until the transaction timeout
+ e.g.
+ <set-tx-query-timeout/>
+-->
+<!ELEMENT set-tx-query-timeout EMPTY>
+
+<!-- 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 (mbean | tx-connection-factory | no-tx-connection-factory)*>
+
+<!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? , adapter-display-name? , config-property* ,
+(application-managed-security | security-domain | security-domain-and-application)? ,
+min-pool-size? , max-pool-size? , blocking-timeout-millis? , idle-timeout-minutes? ,
+no-tx-separate-pools? , 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 , adapter-display-name? , config-property* ,
+(application-managed-security | security-domain | security-domain-and-application)? ,
+min-pool-size? , max-pool-size? , blocking-timeout-millis? , idle-timeout-minutes? , depends*)>
+
+<!-- The display name to associate with the connection manager mbean.
+-->
+<!ELEMENT adapter-display-name (#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>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-ds_1_5.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-ds_1_5.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-ds_1_5.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,446 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--dtd for jboss 4.0/jca 1.5 datasource configurations (*-ds.xml), transformed
+by ConnectionFactoryTemplate.xsl
+
+DOCTYPE datasources
+ PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd"
+
+DOCTYPE connection-factories
+ PUBLIC "-//JBoss//DTD JBOSS JCA Config 1.5//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd"
+
+$Id: jboss-ds_1_5.dtd 59775 2007-01-18 14:29:40Z weston.price at jboss.com $
+-->
+
+<!--
+The datasources element is the root of the jdbc datasource configuration
+-->
+<!ELEMENT datasources (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 , 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-minutes?,
+idle-timeout-minutes? , validate-on-match?, new-connection-sql?, check-valid-connection-sql?, valid-connection-checker-class-name?,
+exception-sorter-class-name?, track-statements?, prefill?,
+prepared-statement-cache-size?, share-prepared-statements? , set-tx-query-timeout?, query-timeout?,
+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 , 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-minutes?,
+idle-timeout-minutes? , validate-on-match?, no-tx-separate-pools? , new-connection-sql? , check-valid-connection-sql? ,
+valid-connection-checker-class-name? , exception-sorter-class-name? , track-statements? , prefill?,
+prepared-statement-cache-size?, share-prepared-statements? , set-tx-query-timeout?, query-timeout?,
+metadata?, type-mapping?, depends*)>
+
+<!-- Specify a jca-jdbc XADatasource wrapper
+-->
+<!ELEMENT xa-datasource (jndi-name , use-java-context?, track-connection-by-tx , xa-datasource-class ,
+xa-datasource-property* , 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-minutes?,
+idle-timeout-minutes? , 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? , track-statements? , prefill?,
+prepared-statement-cache-size?, share-prepared-statements? , set-tx-query-timeout?, query-timeout?,
+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 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/>
+-->
+<!ELEMENT track-connection-by-tx 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)>
+
+<!-- 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) >
+
+<!-- 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)>
+
+<!-- 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 (mbean | tx-connection-factory | no-tx-connection-factory)*>
+
+<!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? , idle-timeout-minutes? ,
+no-tx-separate-pools?, 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? , idle-timeout-minutes? ,
+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)>
+
+<!-- EXPERIMENTAL: this is a copy of local-tx-datasource + url-delimeter
+-->
+<!ELEMENT ha-local-tx-datasource (jndi-name, use-java-context?, connection-url, url-delimetir,
+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? , background-validation?, background-validation-minutes?,
+no-tx-separate-pools? , new-connection-sql? , check-valid-connection-sql? , validate-on-match?,
+valid-connection-checker-class-name? , exception-sorter-class-name? , track-statements? , prefill?,
+prepared-statement-cache-size?, share-prepared-statements? , set-tx-query-timeout?, query-timeout?,
+metadata?, type-mapping?, depends*)>
+
+<!-- Specify a jca-jdbc XADatasource wrapper
+-->
+<!ELEMENT ha-xa-datasource (jndi-name , use-java-context?, track-connection-by-tx , xa-datasource-class ,
+xa-datasource-property* , url-property, url-delimetir, 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? , background-validation?, background-validation-minutes?,
+no-tx-separate-pools? , xa-resource-timeout? , validate-on-match?,
+new-connection-sql? , check-valid-connection-sql? ,
+valid-connection-checker-class-name? , exception-sorter-class-name? , track-statements? , prefill?,
+prepared-statement-cache-size?, share-prepared-statements? , set-tx-query-timeout?, query-timeout?,
+type-mapping?, depends*)>
+
+<!-- Specifies the delimeter for URLs in connection-url for ha datasources
+-->
+<!ELEMENT url-delimeter (#PCDATA)>
+
+<!-- For HA XA datasource specifies the name of an xa-datasource-property that contains a list of URLs
+-->
+<!ELEMENT url-property (#PCDATA)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_3_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_3_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_3_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,260 @@
+<?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_3_2.dtd 32781 2005-06-23 21:46:30Z dimitris $
+
+DOCTYPE server
+ PUBLIC "-//JBoss//DTD MBean Service 3.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-service_3_2.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>
+-->
+<!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 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 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 mbean 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: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_4_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_4_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_4_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,287 @@
+<?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 33900 2005-07-25 04:26:25Z starksm $
+
+DOCTYPE server
+ PUBLIC "-//JBoss//DTD MBean Service 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-service_4_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>
+-->
+<!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 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: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_4_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_4_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-service_4_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,287 @@
+<?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 33900 2005-07-25 04:26:25Z starksm $
+
+DOCTYPE server
+ PUBLIC "-//JBoss//DTD MBean Service 4.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-service_4_2.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>
+-->
+<!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 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: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-subscription.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-subscription.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-subscription.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,136 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+ DTD used to configure JMX notification listening subscriptions:
+ which JMX Notifications to intercept from which MBeans.
+
+ MBeans that implement org.jboss.system.ListenerServiceMBean
+ have the SubscriptionList attribute, whose value must conform
+ to this DTD.
+
+ For example:
+
+ <server>
+ <mbean code="jboss.example.NotificationMonitor"
+ name="jboss.monitor:name=NotificationMonitor">
+
+ <attribute name="SubscriptionList">
+ <subscription-list>
+ <mbean name="*:service=invoker,*" handback="anObject"/>
+ <mbean name="jboss.monitor:*">
+ <notification type="JBOSS_MONITOR_NOTIFICATION"/>
+ </mbean>
+ <mbean name="JMImplementation:type=MBeanServerDelegate">
+ <notification type="JMX.mbean.registered"/>
+ [...]
+ </mbean
+ [...]
+ </subscription-list>
+ </attribute>
+ [ ... your-other-mbean-attributes ...]
+ </mbean>
+ </server>
+
+ The filter mechanism has been extended to support specification
+ of arbitrary filters, using filter factory plugins, so now we can have:
+
+ <attribute name="SubscriptionList">
+ <subscription-list>
+ <mbean name="jboss.system:*">
+ <filter factory="NotificationFilterSupportFactory">
+ <enable type="org.jboss.system.ServiceMBean.start"/>
+ <enable type="org.jboss.system.ServiceMBean.stop"/>
+ </filter>
+ </mbean>
+ <mbean name="jboss.monitor:service=MemoryMonitor">
+ <filter factory="AttributeChangeNotificationFilterFactory">
+ <enable attribute-name="State"/>
+ </filter>
+ </mbean>
+ <mbean name="JMImplementation:type=MBeanServerDelegate">
+ <filter factory="MBeanServerNotificationFilterFactory">
+ <enable type="JMX.mbean"/>
+ <enable object-name="jboss:type=Service,name=SystemProperties"/>
+ </filter>
+ </mbean>
+ </subscription-list>
+ </attribute>
+
+ $Id: jboss-subscription.dtd 29474 2005-03-14 19:41:52Z andd $
+
+ Author: <a href="mailto:dimitris at jboss.org">Dimitris Andreadis</a>
+-->
+
+<!-- The subscription-list encapsulates the set of MBeans/JMX-Notifications
+that should be monitored (subscribed for). At the first level it contains
+a series of zero or more MBean subscription specifications.
+-->
+<!ELEMENT subscription-list (mbean*)>
+
+<!-- The mbean element is used to identify one or more (in case of a pattern
+specification) mbeans that should be monitored. The mbean may contain an
+optional filter element, or instead, zero or more notification elements.
+If no filter or notification element(s) is specified, all JMX Notification
+types will be monitored. Otherwise, a filter will be installed to monitor
+a subset of the emitted Notifications.
+-->
+<!ELEMENT mbean (filter? | notification*)>
+
+<!-- The name attribute in the mbean specification is required to match one
+or more MBeans. For example:
+
+ <mbean name="*:*"/> - matches all MBeans in the server
+ <mbean name="jboss:*"/> - matches all MBeans in domain jboss
+ <mbean name="jboss:service=invoker,*"/> - matches all MBeans in domain jboss
+ whose service=invoker
+ <mbean name="jboss:service=invoker,type=local"/>
+ - matches this particular MBean
+-->
+<!ATTLIST mbean name CDATA #REQUIRED>
+
+<!-- When making a notification subscription an optional handback string
+maybe specified. All incoming notifications that occur due to this particular
+mbean subscription will carry the handback object.
+-->
+<!ATTLIST mbean handback CDATA #IMPLIED>
+
+<!-- Specification of a notification filter to apply to the subscription.
+The content of this element will vary according to the chosen
+NotificationFilterFactory implementation. For example,
+MBeanServerNotificationFilterFactory supports the following config:
+
+ <mbean name="JMImplementation:type=MBeanServerDelegate">
+ <filter factory="MBeanServerNotificationFilterFactory">
+ <enable type="JMX.mbean"/>
+ <enable object-name="jboss:type=Service,name=SystemProperties"/>
+ ...
+ </filter>
+ </mbean>
+-->
+<!ELEMENT filter ANY>
+
+<!-- The name of a class implementing org.jboss.system.NotificationFilterFactory
+interface. It will be used to construct the filter that will be applied
+to the enclosing subscription. Three filter factories corresponding to the
+"standard" jmx notification filters are already implemented:
+
+ org.jboss.system.filterfactory.AttributeChangeNotificationFilterFactory
+ org.jboss.system.filterfactory.MBeanServerNotificationFilterFactory
+ org.jboss.system.filterfactory.NotificationFilterSupportFactory
+
+As a convenience, you don't need to specify the full package name for
+the pre-packaged factories.
+-->
+<!ATTLIST filter factory CDATA #REQUIRED>
+
+<!-- Specification of a particular JMX notification type to be monitored.
+-->
+<!ELEMENT notification EMPTY>
+
+<!-- The notification type is used as a prefix in the installed notification
+type filter. For example:
+
+ <notification type="JMX.mbean"/> - matches both JMX.mbean.registered &
+ JMX.mbean.unregistered
+-->
+<!ATTLIST notification type CDATA #REQUIRED>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,46 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss specific elements used to integrate the servlet 2.2 web.xml
+elements into a JBoss deployment. This version applies to the JBoss 2.4 and
+earlier series. See the jboss-web_3_0.dtd for changes available only in 3.x.
+
+DOCTYPE jboss-web
+ PUBLIC "-//JBoss//DTD Web Application 2.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-web.dtd"
+-->
+<!-- The jboss-web element is the root element.
+-->
+<!ELEMENT jboss-web (security-domain?, resource-ref* , ejb-ref*)>
+
+<!-- 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 EJBSecurityManager and RealmMapping for
+the domain.
+-->
+<!ELEMENT security-domain (#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-ref-name element gives the ENC relative name used
+in the web-app.xml ejb-ref-name element.
+-->
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+<!-- The jndi-name element specifies the JNDI name of the deployed
+EJB home interface to which the servlet ENC binding will link to.
+-->
+<!ELEMENT jndi-name (#PCDATA)>
+
+<!ELEMENT resource-ref (res-ref-name , jndi-name)>
+
+<!ELEMENT res-ref-name (#PCDATA)>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_3_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_3_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_3_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,105 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss specific elements used to integrate the servlet 2.3 web.xml
+elements into a JBoss deployment. This version applies to the JBoss 3.x
+releases.
+
+DOCTYPE jboss-web
+ PUBLIC "-//JBoss//DTD Web Application 2.3//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-web_3_0.dtd"
+-->
+
+<!-- The jboss-web element is the root element.
+-->
+<!ELEMENT jboss-web (security-domain?, context-root?, virtual-host?,
+resource-env-ref*, resource-ref* , ejb-ref*)>
+
+<!-- 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)>
+
+<!-- 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 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 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-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
+-->
+<!ELEMENT jndi-name (#PCDATA)>
+
+<!-- The res-url element value is url a URL string.
+
+ Used in: resource-ref
+-->
+<!ELEMENT res-url (#PCDATA)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_3_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_3_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_3_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,287 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss specific elements used to integrate the servlet 2.3 web.xml
+elements into a JBoss deployment. This version applies to the JBoss 3.2.x
+releases.
+
+DOCTYPE jboss-web
+ PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd"
+-->
+
+<!-- The jboss-web element is the root element.
+-->
+<!ELEMENT jboss-web (class-loading?, security-domain?, context-root?,
+ virtual-host*, use-session-cookies?, replication-config?, resource-env-ref*,
+ resource-ref* , ejb-ref* , ejb-local-ref*, depends*)>
+
+<!-- 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)>
+
+<!-- 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 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
+-->
+<!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 url a URL string.
+
+ Used in: resource-ref
+-->
+<!ELEMENT res-url (#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 wether this context uses session cookies
+ or not.
+
+Example:
+ <use-session-cookies>true</use-session-cookies>
+-->
+<!ELEMENT use-session-cookies (#PCDATA)>
+
+<!--
+ HTTP Session clustering configuration (optional tags)
+-->
+<!ELEMENT replication-config (replication-trigger?, replication-type?, replication-granularity?)>
+
+<!--
+ Clustering only: Determines when the container should consider that a session
+ must be replicated accross the cluster.
+ Possible values are:
+ 1 - "ACCESS"
+ 2 - "SET_AND_GET"
+ 3 - "SET_AND_NON_PRIMITIVE_GET" (default value)
+ 4 - "SET"
+
+ The first option is conservative but not optimal (performance-wise): it will replicate the
+ session after each http request since the access time stamp is updated.
+
+ The second option is less restrictive but still not optimal since it will replicate even
+ if its content has not been modified but simply accessed (through get attribute operation).
+ There is no deterministic way to know if the content of an attribute is not itself modified.
+ Consequently, by default, no hypothesis can be done. It is up to the developer to tell us
+ if we can trust this policy.
+
+ The third option is conservative but will only replicate if a non-primitive Object has been
+ accessed (Integer, Long, String, etc. which are immutables). It is the default value.
+
+ The fourth option considers that the developer will explicitely call setAttribute on the
+ session if it has to be replicated.
+
+Examples:
+ <replication-trigger>ACCESS</replication-trigger>
+ or
+ <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)>
+
+<!--
+ Deprecated since 3.2.6! The mode is configured cluster-wide in tc5-cluster-service.xml
+ (through the CacheMode attribute).
+
+ Clustering only: Determines how the container will replicate your sessions.
+ Possible values are:
+ 1 - "SYNC" (default)
+ 2 - "ASYNC"
+
+ The first option will make sure that the session is actually copied to other nodes of the cluster
+ before finishing returning the HTTP request. The session removal and expiration are
+ an exception to this rule.
+
+ The second option will asynchronously replicate sessions to the other nodes. This is more
+ efficient (better scalability and performance) but in case of failover you cannot be sure the
+ session has actually arrive on the other node(s).
+
+Examples:
+ <replication-type>SYNC</replication-type>
+ or
+ <replication-type>ASYNC</replication-type>
+-->
+<!ELEMENT replication-type (#PCDATA)>
+
+<!--
+ Clustering only: Determines the session replication granularity level.
+ Possible values are:
+ 1 - "SESSION" (default)
+ 2 - "ATTRIBUTE"
+ 3 - "FIELD" (not yet supported)
+
+ 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.
+
+Examples:
+ <replication-granularity>SESSION</replication-granularity>
+ or
+ <replication-granularity>ATTRIBUTE</replication-granularity>
+-->
+<!ELEMENT replication-granularity (#PCDATA)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_4_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_4_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_4_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,456 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss specific elements used to integrate the servlet 2.4 web.xml
+elements into a JBoss deployment. This version applies to the JBoss 4.0.x
+releases.
+
+$Id: jboss-web_4_0.dtd 61966 2007-04-01 17:05:37Z dimitris at jboss.org $
+
+ <!DOCTYPE jboss-web PUBLIC
+ "-//JBoss//DTD Web Application 2.4//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">
+-->
+
+<!ENTITY % service-ref PUBLIC
+ "-//JBoss//DTD Web Service Reference 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/service-ref_4_0.dtd">
+
+%service-ref;
+
+
+<!-- The jboss-web element is the root element.
+-->
+<!ELEMENT jboss-web (class-loading?, security-domain?, context-root?,
+ virtual-host*, use-session-cookies?, replication-config?, resource-env-ref*,
+ resource-ref*, security-role*, ejb-ref*, ejb-local-ref*,
+ message-destination-ref*, message-destination*,
+ webservice-description*, service-ref*, depends*, servlet*, authenticators*)>
+
+<!-- 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)>
+
+<!-- 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 wether this context uses session cookies
+ or not.
+
+Example:
+ <use-session-cookies>true</use-session-cookies>
+-->
+<!ELEMENT use-session-cookies (#PCDATA)>
+
+
+<!--
+ HTTP Session clustering configuration (optional tags)
+-->
+<!ELEMENT replication-config (replication-trigger?, replication-granularity, replication-field-batch-mode?)>
+
+<!--
+ Clustering only: Determines when the container should consider that a session
+ must be replicated accross the cluster.
+ Possible values are:
+ 1 - "SET_AND_GET"
+ 2 - "SET_AND_NON_PRIMITIVE_GET" (default value)
+ 3 - "SET"
+
+ The first option is conservative but not optimal (performance-wise): it will replicate the
+ session even if its content has not been modified but simply accessed. There is no deterministic
+ way to know if the content of an attribute is not itself modified. Consequently, by default, no
+ hypothesis can be done. It is up to the developer to tell us if we can trust this policy.
+
+ The second option is conservative but will only replicate if a non-primitive Object has been
+ accessed (Integer, Long, String, etc. which are immutables). It is the default value.
+
+ The third option considers that the developer will explicitely call setAttribute on the session
+ if it has to be replicated.
+
+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.
+
+Examples:
+ <replication-granularity>SESSION</replication-granularity>
+ or
+ <replication-granularity>ATTRIBUTE</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 (true|false)>
+
+<!--
+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 )>
+
+<!--
+ Customize the tomcat authenticators at the context or web-app level.
+ These are keyed in by http-auth method specified in login-config in web.xml
+
+ <authenticators>
+ <authenticator>
+ <key>BASIC</key>
+ <value>org.apache.catalina.authenticator.BasicAuthenticator</value>
+ </authenticator>
+ <authenticator>
+ <key>CLIENT-CERT</key>
+ <value>org.apache.catalina.authenticator.SSLAuthenticator</value>
+ </authenticator>
+ <authenticator>
+ <key>DIGEST</key>
+ <value>org.apache.catalina.authenticator.DigestAuthenticator</value>
+ </authenticator>
+ <authenticator>
+ <key>FORM</key>
+ <value>org.apache.catalina.authenticator.FormAuthenticator</value>
+ </authenticator>
+ <authenticator>
+ <key>NONE</key>
+ <value>org.apache.catalina.authenticator.NonLoginAuthenticator</value>
+ </authenticator>
+ </authenticators>
+-->
+
+<!ELEMENT authenticators (authenticator+)>
+<!ELEMENT authenticator ( key, value )>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_4_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_4_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss-web_4_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,431 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- The JBoss specific elements used to integrate the servlet 2.4 web.xml
+elements into a JBoss deployment. This version applies to the JBoss 4.2.x
+releases.
+
+$Id: jboss-web_4_0.dtd 60134 2007-01-31 13:14:47Z thomas.diesler at jboss.com $
+
+ <!DOCTYPE jboss-web PUBLIC
+ "-//JBoss//DTD Web Application 4.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-web_4_2.dtd">
+-->
+
+<!ENTITY % service-ref PUBLIC
+ "-//JBoss//DTD Web Service Reference 4.2//EN"
+ "http://www.jboss.org/j2ee/dtd/service-ref_4_2.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*,
+ resource-ref*, security-role*, ejb-ref*, ejb-local-ref*,
+ message-destination-ref*, message-destination*,
+ webservice-description*, service-ref*, depends*, servlet*)>
+
+<!-- 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 wether this context uses session cookies
+ or not.
+
+Example:
+ <use-session-cookies>true</use-session-cookies>
+-->
+<!ELEMENT use-session-cookies (#PCDATA)>
+
+
+<!--
+ HTTP Session clustering configuration (optional tags)
+-->
+<!ELEMENT replication-config (replication-trigger?, replication-granularity, replication-field-batch-mode?)>
+
+<!--
+ Clustering only: Determines when the container should consider that a session
+ must be replicated accross the cluster.
+ Possible values are:
+ 1 - "SET_AND_GET"
+ 2 - "SET_AND_NON_PRIMITIVE_GET" (default value)
+ 3 - "SET"
+
+ The first option is conservative but not optimal (performance-wise): it will replicate the
+ session even if its content has not been modified but simply accessed. There is no deterministic
+ way to know if the content of an attribute is not itself modified. Consequently, by default, no
+ hypothesis can be done. It is up to the developer to tell us if we can trust this policy.
+
+ The second option is conservative but will only replicate if a non-primitive Object has been
+ accessed (Integer, Long, String, etc. which are immutables). It is the default value.
+
+ The third option considers that the developer will explicitely call setAttribute on the session
+ if it has to be replicated.
+
+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.
+
+Examples:
+ <replication-granularity>SESSION</replication-granularity>
+ or
+ <replication-granularity>ATTRIBUTE</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 (true|false)>
+
+<!--
+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: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,728 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+This is the XML DTD for the JBoss 2.2 EJB deployment descriptor.
+The DOCTYPE is:
+ <!DOCTYPE jboss PUBLIC
+ "-//JBoss//DTD JBOSS//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss.dtd">
+
+Overview of the architecture of jboss.xml
+
+<jboss>
+
+ <secure />
+ <security-domain />
+
+ <enterprise-beans>
+
+ <entity>
+ <ejb-name />
+ <jndi-name />
+ <resource-ref>
+ <res-ref-name />
+ <resource-name />
+ </resource-ref>
+ </entity>
+
+ <session>
+ <ejb-name />
+ <jndi-name />
+ <resource-ref>
+ <res-ref-name />
+ <resource-name />
+ </resource-ref>
+ </session>
+
+ </enterprise-beans>
+
+ <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 />
+ <container-invoker />
+ <container-interceptors />
+ <instance-pool />
+ <instance-cache />
+ <persistence-manager />
+ <transaction-manager />
+ <container-invoker-conf />
+ <container-cache-conf />
+ <container-pool-conf />
+ <commit-option />
+ <role-mapping-manager/>
+ <authentication-module/>
+ </container-configuration>
+
+ </container-configurations>
+
+</jboss>
+-->
+<!--
+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 (secure? , security-domain?, enterprise-beans? , resource-managers? , container-configurations?)>
+
+<!--
+ The secure element tells the container to enforce ejb1.1 restrictions
+ It must be one of the following :
+ <secure>true</secure>
+ <secure>false</secure>
+
+ Used in: jboss
+ -->
+<!ELEMENT secure (#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 EJBSecurityManager and RealmMapping for
+the domain. One can still override these interfaces at the container
+level using the authentication-module and role-mapping-manager elements.
+-->
+<!ELEMENT security-domain (#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)+>
+
+<!--
+ 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? , home-invoker? , bean-invoker? , configuration-name? , security-proxy?, ejb-ref* , resource-ref*)>
+
+<!--
+ 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-invoker? , bean-invoker? , configuration-name?, security-proxy?, ejb-ref* , resource-ref*)>
+
+<!--
+ 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 and session
+ -->
+<!ELEMENT ejb-name (#PCDATA)>
+
+<!--
+ The jndi-name element gives the actual jndi name under which the bean will
+ be deployed. It is provided by the deployer. If not, jboss will assume
+ "jndi-name" = "ejb-name"
+
+ Used in: entity and session
+ -->
+<!ELEMENT jndi-name (#PCDATA)>
+
+<!--
+ The home-invoker and bean-invoker elements defines the Invoker MBean to use
+ for Home Proxies and Bean Proxies.
+
+ Used in: entity and session
+ -->
+<!ELEMENT home-invoker (#PCDATA)>
+<!ELEMENT bean-invoker (#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 none is provided, jboss will automatically use the
+ right standard configuration, see container-configurations.
+
+ Used in: entity and session
+ -->
+<!ELEMENT configuration-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 and session
+-->
+<!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
+ -->
+<!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 jndi-name element gives the deployed name of the reference. The
+ general form is
+ <jndi-name>t3://otherserver/application/beanB</jndi-name>
+
+ Used in: ejb-ref
+
+ (It's commented out here because it appears above and you
+ can't declare an element more than once per DTD)
+ -->
+<!-- <!ELEMENT jndi-name (#PCDATA)> -->
+<!--
+ The resource-ref element gives a mapping between the "code name"
+ of a resource (res-ref-name, provided by the Bean Developper) 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: session, entity
+ -->
+<!ELEMENT resource-ref (res-ref-name , resource-name)>
+
+<!--
+ The res-ref-name element gives the "code name" of a resource. It is
+ provided by the Bean Developper. 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 Developper 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-class attribute is used to indicate which implementation
+ class should be used for the specified resource manager.
+ -->
+<!ATTLIST resource-manager res-class CDATA #REQUIRED>
+
+<!--
+ 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 is the "runtime jndi name" as a url of the resource.
+ It is provided by the Deployer. See resource-managers.
+
+ Used in: resource-manager
+ -->
+<!ELEMENT res-url (#PCDATA)>
+
+<!--
+ The container-configurations element declares the different possible
+ container configurations that the beans can use. standardjboss.xml
+ provides 4 standard configurations with the following container-names:
+ - Standard CMP EntityBean
+ - Standard BMP EntityBean
+ - Standard Stateless SessionBean
+ - Standard Stateful SessionBean
+
+ These 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, container-invoker,
+container-interceptors?, instance-pool?, instance-cache? , persistence-manager? ,
+transaction-manager? , container-invoker-conf? , container-cache-conf? , container-pool-conf?,
+commit-option? , (role-mapping-manager, authentication-module?)?)>
+
+<!--
+ The configuration-class attribute is used to indicate the
+ implementation class that will be loaded for this configuration.
+ This usually indicates what type of bean the configuration
+ applies to.
+ -->
+<!ATTLIST container-configuration configuration-class 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 container-invoker element gives the class name of the container
+ invoker jboss must use for in this configuration. This class must
+ implement the org.jboss.ejb.ContainerInvoker interface. The default is
+ org.jboss.ejb.plugins.jrmp13.server.JRMPContainerInvoker, it may be
+ changed to org.jboss.ejb.plugins.jrmp12.server.JRMPContainerInvoker if
+ no 1.3 VM is available
+
+ Used in: container-configuration
+ -->
+<!ELEMENT container-invoker (#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 interceptor element specifies an instance of org.jboss.ejb.Interceptor
+that is to be added to the container interceptor stack.
+
+Used in: container-interceptors
+-->
+<!ELEMENT interceptor (#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 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 transaction-manager element gives the class name of the transaction
+ manager jboss must use for in this configuration. This class must implement
+ the javax.transaction.TransactionManager interface. The default is
+ org.jboss.tm.TxManager.
+
+ Used in: container-configuration
+ -->
+<!ELEMENT transaction-manager (#PCDATA)>
+
+<!--
+ The container-invoker-conf element holds configuration data for the
+ container invoker.
+ jboss does not read directly the subtree for this element: instead,
+ it is passed to the container invoker instance (if it implements
+ org.jboss.metadata.XmlLoadable) for it to load its parameters.
+
+ The Optimized tag described here only relates to the default container
+ invoker, JRMPContainerInvoker.
+
+ Used in: container-configuration
+ -->
+<!ELEMENT container-invoker-conf (Optimized , RMIObjectPort, RMIClientSocketFactory?, RMIServerSocketFactory?)>
+
+<!--
+ This element is only valid if the container invoker is
+ JRMPContainerInvoker.
+
+ The Optimized element tells if the container invoker to bypass RMI layers
+ when the client is local (same VM as the server). This optimizes RMI calls.
+ Its value must be true or false.
+
+ Used in: container-invoker-conf for JRMPContainerInvoker
+ -->
+<!ELEMENT Optimized (#PCDATA)>
+
+<!--
+ The RMIObjectPort element indicates what port the RMI objects
+ created by this container should listen on. Any number of objects
+ in the same VM can use the same port. However, objects in
+ different VMs cannot use the same port. You may set this value
+ to 0 to use anyonmous ports (that is, each object just picks a
+ free port to use). If you want to run jBoss more than once on
+ the same machine, you must either create separate configurations
+ with separate ports, or set all the configurations to use
+ anonymous port. The standard jBoss setting is "4444".
+
+ Its value must an integer (0, or a valid port number). Note that
+ normal user on a UNIX system cannot access privileged ports (<1024)
+
+ Used in: container-invoker-conf for JRMPContainerInvoker
+ -->
+<!ELEMENT RMIObjectPort (#PCDATA)>
+
+<!--
+ The RMIClientSocketFactory element indicates the use of a custom
+ socket factory that should be used by RMI objects created by
+ this container. The combination of socket factory type and port
+ must be unique but more than one container can use the same
+ socket factory, port combination.
+
+ Its value must be the fully qualified name of the class that
+ implements the java.rmi.server.RMIClientSocketFactory interface,
+ and the class must be available to the JBoss class loader.
+ If this element is not specified the default VM client socket
+ factory will be used.
+
+ Used in: container-invoker-conf for JRMPContainerInvoker
+ -->
+<!ELEMENT RMIClientSocketFactory (#PCDATA)>
+
+<!--
+ The RMIServerSocketFactory element indicates the use of a custom
+ socket factory that should be used by RMI objects created by
+ this container. The combination of socket factory type and port
+ must be unique but more than one container can use the same
+ socket factory, port combination.
+
+ Its value must be the fully qualified name of the class that
+ implements the java.rmi.server.RMIServerSocketFactory interface,
+ and the class must be available to the JBoss class loader.
+ If this element is not specified the default VM server socket
+ factory will be used.
+
+ Used in: container-invoker-conf for JRMPContainerInvoker
+ -->
+<!ELEMENT RMIServerSocketFactory (#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.
+
+ The default instance caches, NoPassivationEntityInstanceCache and
+ NoPassivationStatefulSessionInstanceCache, have no configuration
+ available.
+
+ Used in: container-configuration
+ -->
+<!ELEMENT container-cache-conf (cache-policy? , cache-policy-conf?)>
+
+<!--
+ 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.
+
+ Used in: container-cache-conf (when cache-policy is the LRU cache)
+ -->
+<!ELEMENT cache-policy-conf (min-capacity , max-capacity , overager-period , resizer-period , max-bean-age , max-cache-miss-period , min-cache-miss-period , cache-load-factor)>
+
+<!--
+ 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 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)>
+
+<!--
+ 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 (MaximumSize , feeder-policy , feeder-policy-conf)>
+
+<!--
+ The capacity of the Pool. The pool feeder will feed the pool with new
+ instances, the pool size being limited by this value. For pools where
+ reclaim is possible, the pool will also be feed 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.
+
+ Used in: container-pool-conf
+ -->
+<!ELEMENT MaximumSize (#PCDATA)>
+
+<!--
+ This element is only valid if the instance pool is a subclass of
+ AbstractInstancePool.
+
+ The feeder-policy element gives the Class that implements InstancePoolFeeder
+ and is responsible to feed the pool with new instances of bean.
+ If not present, no thread are started and the pool will have a size of 1.
+
+ TimedInstancePoolFeeder is the first implementation available.
+
+ Used in: container-pool-conf for AbstractInstancePool subclasses
+ -->
+<!ELEMENT feeder-policy (#PCDATA)>
+
+<!--
+ This element describes properties that the InstancePoolFeeder implementation
+ will read to configure itself (XmlLoadable).
+
+ Note: the 3 attributes are hardcoded here for TimedInstancePoolFeeder.
+
+ Used in: container-pool-conf for InstancePoolFeeder implementations
+ -->
+<!ELEMENT feeder-policy-conf (increment , period)>
+
+<!--
+ The pool feeder will feed the pool with this number of new instances at
+ a regular period.
+
+ Used in: feeder-policy-conf
+ -->
+<!ELEMENT increment (#PCDATA)>
+
+<!--
+ The interval of time (in milliseconds) the pool feeder look if the pool
+ has come to its maximum size (capacity) and if not, will feed it with
+ a particular number of new instances (increment).
+
+ Used in: feeder-policy-conf
+ -->
+<!ELEMENT period (#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 or C.
+
+ - 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.
+
+ See ejb1.1 specification for details (p118).
+
+ Used in: container-configuration
+ -->
+<!ELEMENT commit-option (#PCDATA)>
+
+<!--
+ The role-mapping-manager element specifies the JNDI name of the
+ org.jboss.security.RealmMapping implementation that is to be used by the
+ container SecurityInterceptor.
+
+ Used in: container-configuration
+ -->
+<!ELEMENT role-mapping-manager (#PCDATA)>
+
+<!--
+ The authentication-module element specifies the JNDI name of the
+ org.jboss.security.EJBSecurityManager implementation that is to be used
+ by the container SecurityInterceptor.
+
+ Used in: container-configuration
+ -->
+<!ELEMENT authentication-module (#PCDATA)>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_2_4.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_2_4.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_2_4.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,857 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+This is the XML DTD for the JBoss 2.4 EJB deployment descriptor.
+The DOCTYPE is:
+ <!DOCTYPE jboss PUBLIC
+ "-//JBoss//DTD JBOSS 2.4//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_2_4.dtd">
+
+$Id: jboss_2_4.dtd 23138 2004-08-22 08:08:27Z pilhuhn $
+$Revision: 23138 $
+
+Overview of the architecture of jboss.xml
+
+<jboss>
+
+ <enforce-ejb-restrictions />
+ <security-domain />
+ <unauthenticated-principal />
+
+ <enterprise-beans>
+
+ <entity>
+ <ejb-name />
+ <jndi-name />
+ <resource-ref>
+ <res-ref-name />
+ <resource-name />
+ </resource-ref>
+ <clustered />
+ </entity>
+
+ <session>
+ <ejb-name />
+ <jndi-name />
+ <resource-ref>
+ <res-ref-name />
+ <resource-name />
+ </resource-ref>
+ <clustered />
+ </session>
+
+ </enterprise-beans>
+
+ <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 />
+ <container-invoker />
+ <container-interceptors />
+ <instance-pool />
+ <instance-cache />
+ <persistence-manager />
+ <transaction-manager />
+ <locking-policy />
+ <container-invoker-conf />
+ <container-cache-conf />
+ <container-pool-conf />
+ <commit-option />
+ <optiond-refresh-rate />
+ <security-domain/>
+ </container-configuration>
+
+ </container-configurations>
+
+</jboss>
+-->
+<!--
+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 (enforce-ejb-restrictions? , security-domain? , unauthenticated-principal? , enterprise-beans? , resource-managers? , container-configurations?)>
+
+<!--
+ 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 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 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? , configuration-name? , security-proxy? , ejb-ref* , resource-ref* , resource-env-ref* , clustered? , cluster-config? )>
+
+<!--
+ 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? , configuration-name? , security-proxy? , ejb-ref* , resource-ref* , resource-env-ref* , clustered? , cluster-config? )>
+
+<!--
+ 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 , destination-jndi-name , configuration-name? , security-proxy? , ejb-ref* , resource-ref* , resource-env-ref*)>
+
+<!--
+ 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. It is provided by the deployer. If not, jboss will assume
+ "jndi-name" = "ejb-name"
+
+ Used in: entity and session
+ -->
+<!ELEMENT jndi-name (#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 none is provided, jboss will automatically use the
+ right standard configuration, see container-configurations.
+
+ Used in: entity, session, and message-driven
+ -->
+<!ELEMENT configuration-name (#PCDATA)>
+
+<!ELEMENT destination-jndi-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 jndi-name element gives the deployed name of the reference. The
+ general form is
+ <jndi-name>t3://otherserver/application/beanB</jndi-name>
+
+ Used in: ejb-ref
+
+ (It's commented out here because it appears above and you
+ can't declare an element more than once per DTD)
+ -->
+<!-- <!ELEMENT jndi-name (#PCDATA)> -->
+<!--
+ The resource-env-ref element gives a mapping between the "code name"
+ of a env resource (res-ref-name, provided by the Bean Developper) 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 Developper. See resource-managers for the actual
+
+ Used in: resource-env-ref
+ -->
+<!ELEMENT resource-env-ref-name (#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
+ -->
+<!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 "/HASessionState/" by the container to get
+ the actual JNDI name of the HAPartition. If not, jboss will assume partition-name = "DefaultPartition".
+
+ Used in: entity and session (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.
+ If not, jboss will assume home-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin".
+
+ Used in: entity and session (in clustered-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 the bean proxy.
+ If not, jboss will assume :
+ - for EB and SFSB : bean-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin"
+ - for SLSB : bean-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin"
+
+ Used in: entity and session (in clustered-config element)
+ -->
+<!ELEMENT bean-load-balance-policy (#PCDATA)>
+
+<!--
+ The session-state-manager-jndi-name element indicates the name of the HASessionState to be used
+ by the container as a backend for state session management in the cluster.
+ This *is* a JNDI name (not like the partition-name element).
+ If not, jboss will assume partition-name = "/HASessionState/Default".
+
+ Used in: session (in clustered-config element)
+ -->
+<!ELEMENT session-state-manager-jndi-name (#PCDATA)>
+
+<!--
+ The jndi-name element gives the deployed name of the reference. The
+ general form is
+ <jndi-name>t3://otherserver/application/beanB</jndi-name>
+
+ Used in: ejb-ref
+
+ (It's commented out here because it appears above and you
+ can't declare an element more than once per DTD)
+ -->
+<!-- <!ELEMENT jndi-name (#PCDATA)> -->
+<!--
+ The resource-ref element gives a mapping between the "code name"
+ of a resource (res-ref-name, provided by the Bean Developper) 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 Developper. 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 Developper 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 is the "runtime jndi name" as a url of the resource.
+ It is provided by the Deployer. See resource-managers.
+
+ Used in: resource-manager
+ -->
+<!ELEMENT res-url (#PCDATA)>
+
+<!--
+ The container-configurations element declares the different possible
+ container configurations that the beans can use. standardjboss.xml
+ provides 4 standard configurations with the following container-names:
+ - Standard CMP EntityBean
+ - Standard BMP EntityBean
+ - Standard Stateless SessionBean
+ - Standard Stateful SessionBean
+
+ These 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? , container-invoker? , container-interceptors? , instance-pool? , instance-cache? , persistence-manager? , transaction-manager? , locking-policy? , container-invoker-conf? , container-cache-conf? , container-pool-conf? , commit-option? , optiond-refresh-rate? , (security-domain | (role-mapping-manager , authentication-module))?)>
+
+<!--
+ The configuration-class attribute is used to indicate the
+ implementation class that will be loaded for this configuration.
+ This usually indicates what type of bean the configuration
+ applies to.
+ -->
+<!ATTLIST container-configuration configuration-class 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 container-invoker element gives the class name of the container
+ invoker jboss must use for in this configuration. This class must
+ implement the org.jboss.ejb.ContainerInvoker interface. The default is
+ org.jboss.ejb.plugins.jrmp13.server.JRMPContainerInvoker, it may be
+ changed to org.jboss.ejb.plugins.jrmp12.server.JRMPContainerInvoker if
+ no 1.3 VM is available
+
+ Used in: container-configuration
+ -->
+<!ELEMENT container-invoker (#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 interceptor element specifies an instance of org.jboss.ejb.Interceptor
+that is to be added to the container interceptor stack.
+
+Used in: container-interceptors
+-->
+<!ELEMENT interceptor (#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 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 transaction-manager (#PCDATA)>
+
+<!--
+ The transaction-manager element gives the class name of the transaction
+ manager jboss must use for in this configuration. This class must implement
+ the javax.transaction.TransactionManager interface. The default is
+ org.jboss.tm.TxManager.
+
+ Used in: container-configuration
+ -->
+<!ELEMENT locking-policy (#PCDATA)>
+
+<!--
+ The container-invoker-conf element holds configuration data for the
+ container invoker.
+ jboss does not read directly the subtree for this element: instead,
+ it is passed to the container invoker instance (if it implements
+ org.jboss.metadata.XmlLoadable) for it to load its parameters.
+
+ The Optimized tag described here only relates to the default container
+ invoker, JRMPContainerInvoker.
+
+ Used in: container-configuration
+ -->
+<!ELEMENT container-invoker-conf (JMSProviderAdapterJNDI? , ServerSessionPoolFactoryJNDI? , MaximumSize? , MaxMessages? , RMIObjectPort? , Optimized , RMIClientSocketFactory? , RMIServerSocketFactory? , RMIServerSocketAddr?)>
+
+<!--
+ This element is only valid if the container invoker is
+ JRMPContainerInvoker.
+
+ The Optimized element tells if the container invoker to bypass RMI layers
+ when the client is local (same VM as the server). This optimizes RMI calls.
+ Its value must be true or false.
+
+ Used in: container-invoker-conf for JRMPContainerInvoker
+ -->
+<!ELEMENT Optimized (#PCDATA)>
+
+<!--
+ The RMIObjectPort element indicates what port the RMI objects
+ created by this container should listen on. Any number of objects
+ in the same VM can use the same port. However, objects in
+ different VMs cannot use the same port. You may set this value
+ to 0 to use anyonmous ports (that is, each object just picks a
+ free port to use). If you want to run jBoss more than once on
+ the same machine, you must either create separate configurations
+ with separate ports, or set all the configurations to use
+ anonymous port. The standard jBoss setting is "4444".
+
+ Its value must an integer (0, or a valid port number). Note that
+ normal user on a UNIX system cannot access privileged ports (<1024)
+
+ Used in: container-invoker-conf for JRMPContainerInvoker
+ -->
+<!ELEMENT RMIObjectPort (#PCDATA)>
+
+<!--
+ The RMIClientSocketFactory element indicates the use of a custom
+ socket factory that should be used by RMI objects created by
+ this container. The combination of socket factory type and port
+ must be unique but more than one container can use the same
+ socket factory, port combination.
+
+ Its value must be the fully qualified name of the class that
+ implements the java.rmi.server.RMIClientSocketFactory interface,
+ and the class must be available to the JBoss class loader.
+ If this element is not specified the default VM client socket
+ factory will be used.
+
+ Used in: container-invoker-conf for JRMPContainerInvoker
+ -->
+<!ELEMENT RMIClientSocketFactory (#PCDATA)>
+
+<!--
+ The RMIServerSocketFactory element indicates the use of a custom
+ socket factory that should be used by RMI objects created by
+ this container. The combination of socket factory type and port
+ must be unique but more than one container can use the same
+ socket factory, port combination.
+
+ Its value must be the fully qualified name of the class that
+ implements the java.rmi.server.RMIServerSocketFactory interface,
+ and the class must be available to the JBoss class loader.
+ If this element is not specified the default VM server socket
+ factory will be used.
+
+ Used in: container-invoker-conf for JRMPContainerInvoker
+ -->
+<!ELEMENT RMIServerSocketFactory (#PCDATA)>
+
+<!--
+ The RMIServerSocketAddr element specifies the address on which the
+ RMI objects should be bound.
+
+ Its value is the interface address as a dot decimal IP address or
+ hostname.
+
+ Used in: container-invoker-conf for JRMPContainerInvoker
+ -->
+<!ELEMENT RMIServerSocketAddr (#PCDATA)>
+
+<!ELEMENT JMSProviderAdapterJNDI (#PCDATA)>
+
+<!ELEMENT ServerSessionPoolFactoryJNDI (#PCDATA)>
+
+<!ELEMENT MaxMessages (#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?)>
+
+<!--
+ 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)>
+
+<!--
+ 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)>
+
+<!--
+ 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 MaximumSize
+ configuration.
+
+ Used in: container-configuration
+ -->
+<!ELEMENT container-pool-conf ((MaximumSize , MinimumSize) | Synchronized)>
+
+<!--
+ This element is only valid if the instance pool is a subclass of
+ AbstractInstancePool.
+
+ The MaximumSize element gives the maximum number of instance to
+ keep in the pool. Its value must be an integer.
+
+ Used in: container-pool-conf for AbstractInstancePool subclasses
+ -->
+<!ELEMENT MaximumSize (#PCDATA)>
+
+<!--
+ This element is only valid if the instance pool is a subclass of
+ AbstractInstancePool.
+
+ The MinimumSize element gives the minimum number of instance to
+ keep in the pool. Its value must be an integer.
+
+ Used in: container-pool-conf for AbstractInstancePool subclasses
+ -->
+<!ELEMENT MinimumSize (#PCDATA)>
+
+<!--
+ This element is only valid if the instance pool is
+StatelessSessionInstancePool.
+
+ The Synchronized element instructs the the pool to synchronize
+calls to the Session bean.
+ Its value must be true or false.
+
+ Used in: container-pool-conf for StatelessSessionInstancePool
+ -->
+<!ELEMENT Synchronized (#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)>
+
+<!--
+ The role-mapping-manager element specifies the JNDI name of the
+ org.jboss.security.RealmMapping implementation that is to be used by the
+ container SecurityInterceptor. Its use is deprecated in favor of the
+ security-domain element.
+
+ Used in: container-configuration
+ -->
+<!ELEMENT role-mapping-manager (#PCDATA)>
+
+<!--
+ The authentication-module element specifies the JNDI name of the
+ org.jboss.security.EJBSecurityManager implementation that is to be used
+ by the container SecurityInterceptor. Its use is deprecated in favor of
+ the security-domain element.
+
+ Used in: container-configuration
+ -->
+<!ELEMENT authentication-module (#PCDATA)>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_3_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_3_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_3_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,975 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--Generated by XML Authority-->
+
+<!--
+This is the XML DTD for the JBoss 3.0 EJB deployment descriptor.
+The DOCTYPE is:
+ <!DOCTYPE jboss PUBLIC
+ "-//JBoss//DTD JBOSS 3.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
+
+$Id: jboss_3_0.dtd 23138 2004-08-22 08:08:27Z pilhuhn $
+$Revision: 23138 $
+
+Overview of the architecture of jboss.xml
+
+<jboss>
+
+ <enforce-ejb-restrictions />
+ <security-domain />
+ <unauthenticated-principal />
+
+ <enterprise-beans>
+
+ <entity>
+ <ejb-name />
+ <jndi-name />
+ <local-jndi-name />
+ <read-only>
+ <home-invoker>
+ <bean-invoker>
+ <configuration-name>
+ <security-proxy>
+ <ejb-ref>
+ <resource-ref>
+ <res-ref-name />
+ <resource-name />
+ </resource-ref>
+ <resource-env-ref>
+ <clustered />
+ <cluster-config>
+ </entity>
+
+ <session>
+ <ejb-name />
+ <jndi-name />
+ <local-jndi-name />
+ <home-invoker>
+ <bean-invoker>
+ <configuration-name>
+ <security-proxy>
+ <ejb-ref>
+ <resource-ref>
+ <res-ref-name />
+ <resource-name />
+ </resource-ref>
+ <resource-env-ref>
+ <clustered />
+ <cluster-config>
+ </session>
+
+ <message-driven>
+ <ejb-name>
+ <destination-jndi-name>
+ <mdb-user>
+ <mdb-passwd>
+ <mdb-client-id>
+ <mdb-subscription-id>
+ <configuration-name>
+ <security-proxy>
+ <ejb-ref>
+ <resource-ref>
+ <resource-env-ref>
+ </message-driven>
+
+ </enterprise-beans>
+
+ <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 />
+ <container-invoker />
+ <container-interceptors />
+ <client-interceptors />
+ <instance-pool />
+ <instance-cache />
+ <persistence-manager />
+ <transaction-manager />
+ <web-class-loader />
+ <locking-policy />
+ <container-invoker-conf />
+ <container-cache-conf />
+ <container-pool-conf />
+ <commit-option />
+ <optiond-refresh-rate />
+ <security-domain/>
+ </container-configuration>
+
+ </container-configurations>
+
+</jboss>
+-->
+<!--
+ 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 (enforce-ejb-restrictions? , security-domain? ,
+ unauthenticated-principal? , enterprise-beans? , resource-managers? ,
+ container-configurations?)>
+
+<!--
+ 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 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 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? , read-only? , home-invoker? , bean-invoker? ,
+configuration-name? , security-proxy? , ejb-ref* , resource-ref* , resource-env-ref* ,
+clustered? , cluster-config?, method-attributes?, depends*)>
+
+<!--
+ 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? , local-jndi-name? , home-invoker? , bean-invoker? ,
+configuration-name? , security-proxy? , ejb-ref* , resource-ref* , resource-env-ref* ,
+clustered? , cluster-config?, method-attributes?, depends*)>
+
+<!--
+ 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 , destination-jndi-name , mdb-user? , mdb-passwd? , mdb-client-id?,
+mdb-subscription-id? , configuration-name? , security-proxy? , ejb-ref* , resource-ref* ,
+resource-env-ref*, depends*)>
+
+<!--
+ 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, resource-ref, resource-env-ref 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)>
+
+<!--
+ The JNDI name under with the local home interface should be bound
+
+ Used in: entity and session
+-->
+<!ELEMENT local-jndi-name (#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, method-attributes
+-->
+<!ELEMENT read-only (#PCDATA)>
+
+<!--
+ The home-invoker and bean-invoker elements define the Invoker MBean to use
+ for Home Proxies and Bean Proxies. When specified at the container configuration
+ level this specifies the default invoker for all beans using the container
+ configuration.
+
+ Used in: container-configuration, entity and session
+-->
+<!ELEMENT home-invoker (#PCDATA)>
+
+<!ELEMENT bean-invoker (#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)>
+
+<!ELEMENT destination-jndi-name (#PCDATA)>
+
+<!ELEMENT mdb-user (#PCDATA)>
+
+<!ELEMENT mdb-passwd (#PCDATA)>
+
+<!ELEMENT mdb-client-id (#PCDATA)>
+
+<!ELEMENT mdb-subscription-id (#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 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 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
+-->
+<!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 "/HASessionState/" by the container to get
+ the actual JNDI name of the HAPartition. If not, jboss will assume partition-name = "DefaultPartition".
+
+ Used in: entity and session (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.
+ If not, jboss will assume home-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin".
+
+ Used in: entity and session (in clustered-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 the bean proxy.
+ If not, jboss will assume :
+ - for EB and SFSB : bean-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin"
+ - for SLSB : bean-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin"
+
+ Used in: entity and session (in clustered-config element)
+-->
+<!ELEMENT bean-load-balance-policy (#PCDATA)>
+
+<!--
+ The session-state-manager-jndi-name element indicates the name of the HASessionState to be used
+ by the container as a backend for state session management in the cluster.
+ This *is* a JNDI name (not like the partition-name element).
+ If not, jboss will assume partition-name = "/HASessionState/Default".
+
+ Used in: session (in clustered-config element)
+-->
+<!ELEMENT session-state-manager-jndi-name (#PCDATA)>
+
+<!-- The method-attributes element allows for the specification of non-standard
+attributes for the named method(s).
+
+Used in: session and entity
+-->
+<!ELEMENT method-attributes (method-name, read-only?)>
+
+<!-- Specifies a method name or method name pattern
+
+Used in: session and entity
+-->
+<!ELEMENT method-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 is the "runtime jndi name" as a url of the resource.
+ It is provided by the Deployer. See resource-managers.
+
+ Used in: resource-manager
+-->
+<!ELEMENT res-url (#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
+ - jdk 1.2.2 CMP EntityBean
+ - Standard Stateless SessionBean
+ - Clustered Stateless SessionBean
+ - IIOP Stateless SessionBean
+ - jdk 1.2.2 Stateless SessionBean
+ - Standard Stateful SessionBean
+ - Clustered Stateful SessionBean
+ - IIOP Stateful SessionBean
+ - jdk 1.2.2 Stateful SessionBean
+ - Standard BMP EntityBean
+ - Clustered BMP EntityBean
+ - IIOP BMP EntityBean
+ - jdk 1.2.2 BMP EntityBean
+ - Standard message Driven Bean
+
+ The standard configurations will automatically be used if no custom
+ configuration is specified.
+
+ The jdk 1.2.2 configurations are defined for backwards compatability.
+
+ 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? , container-invoker?,
+home-invoker?, bean-invoker?, container-interceptors? , client-interceptors? , instance-pool? ,
+instance-cache? , persistence-manager? , transaction-manager? , web-class-loader? , locking-policy? ,
+container-invoker-conf? , container-cache-conf? , container-pool-conf? , commit-option? ,
+optiond-refresh-rate? , security-domain?, cluster-config?)>
+
+<!-- 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 container-invoker element gives the class name of the container
+ invoker jboss must use for in this configuration. This class must
+ implement the org.jboss.ejb.ContainerInvoker interface. The default is
+ org.jboss.proxy.ejb.ProxyFactory for entity and session beans and
+ org.jboss.ejb.plugins.jms.JMSContainerInvoker for message driven beans.
+ Containers supporting clustering use org.jboss.proxy.ejb.ProxyFactoryHA.
+
+ Used in: container-configuration
+-->
+<!ELEMENT container-invoker (#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: container-configuration
+-->
+<!ELEMENT client-interceptors (home , bean)>
+
+<!--
+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 interceptor element specifies an instance of org.jboss.ejb.Interceptor
+ that is to be added to the container interceptor stack.
+
+ Used in: container-interceptors
+-->
+<!ELEMENT interceptor (#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 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 transaction-manager element gives the class name of the transaction
+ manager jboss must use for in this configuration. This class must implement
+ the javax.transaction.TransactionManager interface. The default is
+ org.jboss.tm.TxManager.
+
+ Used in: container-configuration
+-->
+<!ELEMENT transaction-manager (#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
+-->
+<!ELEMENT web-class-loader (#PCDATA)>
+
+<!--
+ The container-invoker-conf element holds configuration data for the
+ container invoker.
+ jboss does not read directly the subtree for this element: instead,
+ it is passed to the container invoker instance (if it implements
+ org.jboss.metadata.XmlLoadable) for it to load its parameters.
+
+ The Optimized tag described here only relates to the default container
+ invokers, ProxyFactory, ProxyFactoryHA and JMSContainerInvoker.
+
+ Used in: container-configuration
+-->
+<!ELEMENT container-invoker-conf (JMSProviderAdapterJNDI? , ServerSessionPoolFactoryJNDI? , MaximumSize? , MaxMessages? , MDBConfig?)>
+
+<!--
+ Used in: container-invoker-conf for JMSContainerInvoker
+-->
+<!ELEMENT JMSProviderAdapterJNDI (#PCDATA)>
+
+<!--
+ Used in: container-invoker-conf for JMSContainerInvoker
+-->
+<!ELEMENT ServerSessionPoolFactoryJNDI (#PCDATA)>
+
+<!--
+ Used in: container-invoker-conf for JMSContainerInvoker
+-->
+<!ELEMENT MaxMessages (#PCDATA)>
+
+<!--
+ Used in: container-invoker-conf for JMSContainerInvoker
+-->
+<!ELEMENT MDBConfig (ReconnectIntervalSec , DLQConfig?)>
+
+<!--
+ Used in: MDBConfig
+-->
+<!ELEMENT ReconnectIntervalSec (#PCDATA)>
+
+<!--
+ Used in: MDBConfig
+-->
+<!ELEMENT DLQConfig (DestinationQueue , MaxTimesRedelivered , TimeToLive)>
+
+<!--
+ Used in: DLQConfig
+-->
+<!ELEMENT DestinationQueue (#PCDATA)>
+
+<!--
+ Used in: DLQConfig
+-->
+<!ELEMENT MaxTimesRedelivered (#PCDATA)>
+
+<!--
+ Used in: DLQConfig
+-->
+<!ELEMENT TimeToLive (#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?)>
+
+<!--
+ 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)>
+
+<!--
+ 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)>
+
+<!--
+ 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 (MaximumSize , feeder-policy , feeder-policy-conf)>
+
+<!--
+ The capacity of the Pool. The pool feeder will feed the pool with new
+ instances, the pool size being limited by this value. For pools where
+ reclaim is possible, the pool will also be feed 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.
+
+ Used in: container-pool-conf
+-->
+<!ELEMENT MaximumSize (#PCDATA)>
+
+<!--
+ This element is only valid if the instance pool is a subclass of
+ AbstractInstancePool.
+
+ The feeder-policy element gives the Class that implements InstancePoolFeeder
+ and is responsible to feed the pool with new instances of bean.
+ If not present, no thread are started and the pool will have a size of 1.
+
+ TimedInstancePoolFeeder is the first implementation available.
+
+ Used in: container-pool-conf for AbstractInstancePool subclasses
+-->
+<!ELEMENT feeder-policy (#PCDATA)>
+
+<!--
+ This element describes properties that the InstancePoolFeeder implementation
+ will read to configure itself (XmlLoadable).
+
+ Note: the 3 attributes are hardcoded here for TimedInstancePoolFeeder.
+
+ Used in: container-pool-conf for InstancePoolFeeder implementations
+-->
+<!ELEMENT feeder-policy-conf (increment , period)>
+
+<!--
+ The pool feeder will feed the pool with this number of new instances at
+ a regular period.
+
+ Used in: feeder-policy-conf
+-->
+<!ELEMENT increment (#PCDATA)>
+
+<!--
+ The interval of time (in milliseconds) the pool feeder look if the pool
+ has come to its maximum size (capacity) and if not, will feed it with
+ a particular number of new instances (increment).
+
+ Used in: feeder-policy-conf
+-->
+<!ELEMENT period (#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)>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_3_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_3_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_3_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1227 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+$Id: jboss_3_2.dtd 60564 2007-02-15 11:12:12Z dimitris at jboss.org $
+
+This is the XML DTD for the JBoss 3.2 EJB deployment descriptor.
+The DOCTYPE is:
+
+ <!DOCTYPE jboss PUBLIC
+ "-//JBoss//DTD JBOSS 3.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_3_2.dtd">
+
+Overview of the architecture of jboss.xml
+
+<jboss>
+
+ <enforce-ejb-restrictions />
+ <security-domain />
+ <unauthenticated-principal />
+
+ <enterprise-beans>
+
+ <entity>
+ <ejb-name />
+ <jndi-name />
+ <local-jndi-name />
+ <call-by-value/>
+ <read-only>
+ <configuration-name>
+ <security-proxy>
+ <ejb-ref>
+ <ejb-local-ref>
+ <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>
+ <resource-ref>
+ <res-ref-name />
+ <resource-name />
+ </resource-ref>
+ <resource-env-ref>
+ <clustered />
+ <cluster-config>
+ </session>
+
+ <message-driven>
+ <ejb-name>
+ <destination-jndi-name>
+ <mdb-user>
+ <mdb-passwd>
+ <mdb-client-id>
+ <mdb-subscription-id>
+ <configuration-name>
+ <security-proxy>
+ <ejb-ref>
+ <resource-ref>
+ <resource-env-ref>
+ </message-driven>
+
+ </enterprise-beans>
+
+ <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>
+-->
+
+<!--
+ 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?, unauthenticated-principal? , exception-on-rollback?, enterprise-beans?,
+ 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 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? , web-class-loader? ,
+JMSProviderAdapterJNDI? , ServerSessionPoolFactoryJNDI? , MinimumSize? , MaximumSize? ,
+KeepAliveMillis? , MaxMessages? , MDBConfig? , poa? , register-ejbs-in-jnp-context? ,
+jnp-context?)>
+
+<!--
+ 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)>
+<!--
+ 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)>
+
+<!--
+ 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?, configuration-name? , invoker-bindings?, security-proxy? ,
+ ejb-ref* , ejb-local-ref* , resource-ref* ,
+ resource-env-ref* , method-attributes? , clustered? , cluster-config?,
+ cache-invalidation? , cache-invalidation-config?, depends*)>
+
+<!--
+ 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? , local-jndi-name?, call-by-value?,
+ exception-on-rollback?, configuration-name?, invoker-bindings?, security-proxy? ,
+ ejb-ref* , ejb-local-ref* , resource-ref* , resource-env-ref* , clustered? ,
+ cluster-config?, method-attributes?, depends*)>
+
+<!--
+ 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 , destination-jndi-name , local-jndi-name?,
+ mdb-user?, mdb-passwd? , mdb-client-id? , mdb-subscription-id? ,
+ exception-on-rollback?, configuration-name? , invoker-bindings?,
+ security-proxy? , ejb-ref* , ejb-local-ref* , resource-ref* , resource-env-ref*, depends*)>
+
+<!--
+ 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 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)>
+
+<!--
+ 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 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 jndi name of the queue/topic to receive messages from -->
+<!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 optional subscription name for topic delivery -->
+<!ELEMENT mdb-subscription-id (#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 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 "/HASessionState/" by the container to get
+ the actual JNDI name of the HAPartition. If not, jboss will assume partition-name = "DefaultPartition".
+
+ Used in: entity and session (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.
+ If not, jboss will assume home-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin".
+
+ Used in: entity and session (in clustered-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 the bean proxy.
+ If not, jboss will assume :
+ - for EB and SFSB : bean-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin"
+ - for SLSB : bean-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin"
+
+ Used in: entity and session (in clustered-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 state session management in the cluster.
+ This *is* a JNDI name (not like the partition-name element).
+ If not, jboss will assume partition-name = "/HASessionState/Default".
+
+ Used in: session (in clustered-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 is the "runtime jndi name" as a url of the resource.
+ It is provided by the Deployer. See resource-managers.
+
+ Used in: resource-manager
+-->
+<!ELEMENT res-url (#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 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
+-->
+<!ELEMENT interceptor (#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?)>
+
+<!-- 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)>
+
+<!--
+ 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)>
+
+<!-- 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)>
+
+<!--
+ 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)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_4_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_4_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_4_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1692 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+$Id: jboss_4_0.dtd 61966 2007-04-01 17:05:37Z dimitris at jboss.org $
+
+This is the XML DTD for the JBoss 4.0 EJB deployment descriptor.
+The DOCTYPE is:
+
+ <!DOCTYPE jboss PUBLIC
+ "-//JBoss//DTD JBOSS 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_4_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 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/service-ref_4_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*, security-identity? ,
+ resource-ref* , resource-env-ref*, message-destination-ref* , 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? , local-jndi-name?, call-by-value?,
+ exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?,
+ security-proxy? , ejb-ref* , ejb-local-ref* , service-ref*, security-identity? ,
+ resource-ref* , resource-env-ref*, message-destination-ref* , 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*, security-identity?, resource-ref*,
+ resource-env-ref*, message-destination-ref*, 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)>
+
+<!--
+ 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 "/HASessionState/" by the container to get
+ the actual JNDI name of the HAPartition. If not, jboss will assume partition-name = "DefaultPartition".
+
+ Used in: entity and session (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.
+ If not, jboss will assume home-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin".
+
+ Used in: entity and session (in clustered-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 the bean proxy.
+ If not, jboss will assume :
+ - for EB and SFSB : bean-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin"
+ - for SLSB : bean-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin"
+
+ Used in: entity and session (in clustered-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 state session management in the cluster.
+ This *is* a JNDI name (not like the partition-name element).
+ If not, jboss will assume partition-name = "/HASessionState/Default".
+
+ Used in: session (in clustered-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?)>
+
+<!-- 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)>
+
+<!--
+ 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: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_4_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_4_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_4_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1702 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+$Id: jboss_4_0.dtd 60157 2007-02-01 11:06:42Z thomas.diesler at jboss.com $
+
+This is the XML DTD for the JBoss 4.2 EJB deployment descriptor.
+The DOCTYPE is:
+
+ <!DOCTYPE jboss PUBLIC
+ "-//JBoss//DTD JBOSS 4.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_4_2.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>
+ <secure-wsdl-access>
+ </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 4.2//EN"
+ "http://www.jboss.org/j2ee/dtd/service-ref_4_2.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*, security-identity? ,
+ resource-ref* , resource-env-ref*, message-destination-ref* , 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? , local-jndi-name?, call-by-value?,
+ exception-on-rollback?, timer-persistence?, configuration-name?, invoker-bindings?,
+ security-proxy? , ejb-ref* , ejb-local-ref* , service-ref*, security-identity? ,
+ resource-ref* , resource-env-ref*, message-destination-ref* , 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*, security-identity?, resource-ref*,
+ resource-env-ref*, message-destination-ref*, 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)>
+
+<!--
+ 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 "/HASessionState/" by the container to get
+ the actual JNDI name of the HAPartition. If not, jboss will assume partition-name = "DefaultPartition".
+
+ Used in: entity and session (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.
+ If not, jboss will assume home-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin".
+
+ Used in: entity and session (in clustered-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 the bean proxy.
+ If not, jboss will assume :
+ - for EB and SFSB : bean-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin"
+ - for SLSB : bean-load-balance-policy = "org.jboss.ha.framework.interfaces.RoundRobin"
+
+ Used in: entity and session (in clustered-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 state session management in the cluster.
+ This *is* a JNDI name (not like the partition-name element).
+ If not, jboss will assume partition-name = "/HASessionState/Default".
+
+ Used in: session (in clustered-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?)>
+
+<!-- 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)>
+
+<!--
+ 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?, secure-wsdl-access?) >
+
+<!-- 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)>
+
+<!--
+A secure endpoint does not by default publish it's wsdl on an unsecure transport.
+You can override this behaviour by explicitly setting the secureWSDLAccess flag to false.
+
+Used in: port-component
+-->
+<!ELEMENT secure-wsdl-access (#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: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,243 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- $Id: jboss_xmbean_1_0.dtd 23740 2004-09-15 22:16:49Z andd $ -->
+
+<!-- This is the XML DTD for the JBoss MX 1.0 XMBean deployment descriptor.
+Author: Juha Lindfors
+Author: David Jencks
+Author: Matt Munz
+
+The DOCTYPE is:
+ <!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_0.dtd">
+-->
+<!--
+ The mbean element is the root element of the document containing the
+ required elements for describing the management interface of one
+ MBean (constructors, attributes, operations and notifications). It
+ also includes an optional description element that can be used to
+ describe the purpose of the MBean and attributes for persistence
+ policy and attribute caching.
+-->
+<!ELEMENT mbean (description? , descriptors? , class , constructor*,
+ attribute* , operation* , notification*)>
+
+<!-- The class element specifies the fully qualifed name of the model MBean
+implementation class. This class will be exposed as a ModelMBean by the
+JMX implementation.
+-->
+<!ELEMENT class (#PCDATA)>
+
+<!--
+ The constructor element describes the constructors of an MBean
+ that are exposed to the management application. The optional
+ description element can be used to to describe the use of the
+ constructor.
+-->
+<!ELEMENT constructor (description? , name , parameter* , descriptors?)>
+
+<!--
+ The attribute element describes the management attributes of an
+ MBean. The name element contains the attribute's name and the type
+ element contains a fully qualified class name of the attribute's
+ type.
+-->
+<!ELEMENT attribute (description? , name , type , descriptors?)>
+
+<!-- The access attribute defines the read/write access modes of an attribute -->
+<!ATTLIST attribute access (read-only | write-only | read-write ) "read-write">
+
+<!-- The getMethod attribute defines the name of the method which reads
+the named attribute. This must be specified if the managed attribute should
+be obtained from the mbean instance. -->
+<!ATTLIST attribute getMethod CDATA #IMPLIED>
+
+<!-- The setMethod attribute defines the name of the method which writes
+the named attribute. This must be specified if the managed attribute should
+be obtained from the mbean instance. -->
+<!ATTLIST attribute setMethod CDATA #IMPLIED>
+
+<!--
+ The operation element describes a management operation of an MBean.
+ The name element contains the operation's name and the parameter
+ elements describe the operation's signature. The return-type element
+ must contain a fully qualified class name of the return type from
+ this operation.
+
+ If return-type is not specified, void is assumed.
+-->
+<!ELEMENT operation (description? , name , parameter* , return-type? , descriptors?)>
+
+<!-- The impact attribute defines the impact of executing the operation and must be one of:
+ ACTION, The operation changes the state of the MBean component (write operation).
+ INFO, The operation should not alter the state of the MBean component (read operation).
+ ACTION_INFO, The operation behaves like a read/write operation.
+-->
+<!ATTLIST operation impact (ACTION | INFO | ACTION_INFO ) "ACTION_INFO">
+
+<!-- The descriptors element contains all the descriptors for a containing element, as subelements.
+The descriptors suggested in the jmx spec have predefined elements, whereas custom descriptors have
+a generic element.
+-->
+<!ELEMENT descriptors (interceptors? , persistence? , currencyTimeLimit? , state-action-on-update? ,
+display-name? , default? , value? , persistence-manager? , descriptor*)>
+
+<!-- The interceptors element specifies a customized stack of interceptors
+that will be used in place of the default stack. Currently this is only
+used when specified at the mbean level, but it could define a custom attribute
+or operation level interceptor stack in the future.
+-->
+<!ELEMENT interceptors (interceptor+)>
+
+<!-- The interceptor element specifies a custom interceptor stack to insert
+ahead of the standard ModelBean consisting of:
+ org.jboss.mx.interceptor.PersistenceInterceptor
+ org.jboss.mx.interceptor.MBeanAttributeInterceptor
+ org.jboss.mx.interceptor.ObjectReferenceInterceptor
+
+Each interceptor must implement the org.jboss.mx.interceptor.Interceptor
+interface, and must have either a no-arg constructor, or a constructor
+that accepts a javax.management.modelmbean.ModelMBeanInfo.
+-->
+<!ELEMENT interceptor ANY>
+
+<!ATTLIST interceptor code CDATA #REQUIRED >
+<!-- The persistence element contains descriptors for the persistPolicy,
+persistPeriod, persistLocation, and persistName properties suggested by the spec.
+-->
+<!ELEMENT persistence EMPTY>
+
+<!-- The persistPolicy defines how attributes should be persisted and must be one of:
+ Never, attribute values are transient values that are never persisted
+ OnUpdate, attribute values are persisted whenever they are updated
+ OnTimer, attribute values are persisted based on the time given by the persistPeriod.
+ NoMoreOftenThan, attribute values are persisted when updated unless but no more
+ oten than the persistPeriod.
+-->
+<!ATTLIST persistence persistPolicy (Never | OnUpdate | NoMoreOftenThan | OnTimer ) #IMPLIED>
+
+<!-- The persistPeriod attribute gives the update frequency in milliseconds if
+the perisitPolicy attribute is NoMoreOftenThan or OnTimer.
+-->
+<!ATTLIST persistence persistPeriod CDATA #IMPLIED>
+
+<!-- The persistLocation attribute specifies the location of the persistence
+store. Its form depends on the JMX implementation. Currently this should refer
+to a directory into which the attributes will be serialized.
+-->
+<!ATTLIST persistence persistLocation CDATA #IMPLIED>
+
+<!-- The persistName attribute can be used in conjunction with the
+persistLocation attribute to further qualify the persistent store location. For
+a directory persistLocation the persistName specifies the file to which the
+attributes are stored within the directory.
+-->
+<!ATTLIST persistence persistName CDATA #IMPLIED>
+
+<!-- The currencyTimeLimit element specifies the time in seconds that a cached
+value of an attribute remains valid.
+-->
+<!ELEMENT currencyTimeLimit EMPTY>
+
+<!-- The value attribute gives the currencyTimeLimit in seconds. A 0 value
+indicates that an attribute value should always be retrieved from the mbean and
+never cached. A -1 value indicates that a cache value is always valid.
+-->
+<!ATTLIST currencyTimeLimit value CDATA #IMPLIED>
+
+<!-- The state-action-on-update element specifies the what happens to an mbean
+when one of its attributes is updated. The action is given by the value attribute.
+-->
+<!ELEMENT state-action-on-update EMPTY>
+
+<!-- The value value attribute defines what happens to the mbean lifecycle
+state when one of its attributes is update. It must be one of:
+ keep-running,
+ restart,
+ reconfigure,
+ reinstantiate
+-->
+<!ATTLIST state-action-on-update value (keep-running | restart | reconfigure | reinstantiate ) #IMPLIED>
+
+<!-- The displayName element specifies the human friendly name of an item
+ -->
+<!ELEMENT display-name EMPTY>
+
+<!-- The value attribute gives the string representation of the displayName
+ -->
+<!ATTLIST display-name value CDATA #IMPLIED>
+
+<!-- The persistence-manager element give the name of a class to use as the
+persistence manager.
+ -->
+<!ELEMENT persistence-manager EMPTY>
+
+<!-- The value attribute specifies the class name that supplies the
+org.jboss.mx.persistence.PersistenceManager interface implementation.
+ -->
+<!ATTLIST persistence-manager value CDATA #IMPLIED>
+
+<!-- The default element specifes a default value to use when a field has not
+been set.
+-->
+<!ELEMENT default EMPTY>
+
+<!-- The value attribute gives the default value representation
+-->
+<!ATTLIST default value CDATA #REQUIRED>
+
+<!-- The value element specifies a management attribute's current value
+-->
+<!ELEMENT value EMPTY>
+
+<!-- The value (initial) value for attribute -->
+<!ATTLIST value value CDATA #REQUIRED>
+
+<!-- The descriptor element
+-->
+<!ELEMENT descriptor EMPTY>
+
+<!-- The name attribute specifies the type of the descriptor.
+ -->
+<!ATTLIST descriptor name CDATA #REQUIRED>
+<!-- The value attribute specifies the descriptor value.
+-->
+<!ATTLIST descriptor value CDATA #REQUIRED>
+
+<!-- The notification element describes a management notification. The name
+ element contains the fully qualified name of the notification class and
+ the notification-type element contains the dot-separated notification
+ type string.
+-->
+<!ELEMENT notification (description? , name , notification-type+ , descriptors?)>
+
+<!-- The parameter element specifies an operation parameter
+-->
+<!ELEMENT parameter (description? , name , type)>
+
+<!-- The name element is used to define the fundamental name of a component, such as the
+mbean JMX name, the name of an attribute, constructor, operation, notification, etc. This is a
+case-sensitive code centric name. For notifications the name if the class name of the event
+object, javax.management.Notification or a subclass.
+-->
+<!ELEMENT name (#PCDATA)>
+
+<!-- The description element provides human readable descriptive text for constructors,
+attributes, operations, paramters, notifications, etc.
+-->
+<!ELEMENT description (#PCDATA)>
+
+<!-- The type element specifies a fully qualified name of a Java type.
+-->
+<!ELEMENT type (#PCDATA)>
+
+<!-- The return-type element specifies the return type of an operation. If not given or empty
+it is assumed to be the void type.
+-->
+<!ELEMENT return-type (#PCDATA)>
+
+<!-- The notification-type element speicifies the types of notifications that may be sent. These are
+the value that will be seen as the the javax.management.Notification.type attribute.
+-->
+<!ELEMENT notification-type (#PCDATA)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_1.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_1.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_1.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,333 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- $Id: jboss_xmbean_1_1.dtd 39447 2006-01-03 17:46:05Z dimitris $ -->
+
+<!-- This is the XML DTD for the JBoss MX 1.0 XMBean deployment descriptor.
+Author: Juha Lindfors
+Author: David Jencks
+Author: Matt Munz
+Author: Heiko W. Rupp
+Author: Dimitris Andreadis
+The DOCTYPE is:
+ <!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.1//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_1.dtd">
+-->
+<!--
+ The mbean element is the root element of the document containing the
+ required elements for describing the management interface of one
+ MBean (constructors, attributes, operations and notifications). It
+ also includes an optional description element that can be used to
+ describe the purpose of the MBean and attributes for persistence
+ policy and attribute caching.
+-->
+<!ELEMENT mbean (description? , descriptors? , class , constructor*,
+ attribute* , operation* , notification*)>
+
+<!-- The class element specifies the fully qualifed name of the model MBean
+implementation class. This class will be exposed as a ModelMBean by the
+JMX implementation.
+-->
+<!ELEMENT class (#PCDATA)>
+
+<!--
+ The constructor element describes the constructors of an MBean
+ that are exposed to the management application. The optional
+ description element can be used to to describe the use of the
+ constructor.
+-->
+<!ELEMENT constructor (description? , name , parameter* , descriptors?)>
+
+<!--
+ The attribute element describes the management attributes of an
+ MBean. The name element contains the attribute's name and the type
+ element contains a fully qualified class name of the attribute's
+ type.
+-->
+<!ELEMENT attribute (description? , name , type , descriptors?)>
+
+<!-- The access attribute defines the read/write access modes of an attribute -->
+<!ATTLIST attribute access (read-only | write-only | read-write ) "read-write">
+
+<!-- The getMethod attribute defines the name of the method which reads
+the named attribute. This must be specified if the managed attribute should
+be obtained from the mbean instance. -->
+<!ATTLIST attribute getMethod CDATA #IMPLIED>
+
+<!-- The setMethod attribute defines the name of the method which writes
+the named attribute. This must be specified if the managed attribute should
+be obtained from the mbean instance. -->
+<!ATTLIST attribute setMethod CDATA #IMPLIED>
+
+<!--
+ The operation element describes a management operation of an MBean.
+ The name element contains the operation's name and the parameter
+ elements describe the operation's signature. The return-type element
+ must contain a fully qualified class name of the return type from
+ this operation.
+
+ If return-type is not specified, void is assumed.
+-->
+<!ELEMENT operation (description? , name , parameter* , return-type? , descriptors?)>
+
+<!-- The impact attribute defines the impact of executing the operation and must be one of:
+ ACTION, The operation changes the state of the MBean component (write operation).
+ INFO, The operation should not alter the state of the MBean component (read operation).
+ ACTION_INFO, The operation behaves like a read/write operation.
+-->
+<!ATTLIST operation impact (ACTION | INFO | ACTION_INFO ) "ACTION_INFO">
+
+<!-- The descriptors element contains all the descriptors for a containing element, as subelements.
+The descriptors suggested in the jmx spec have predefined elements, whereas custom descriptors have
+a generic element.
+-->
+<!ELEMENT descriptors (interceptors? , persistence? , currencyTimeLimit? ,
+display-name? , default? , value? , persistence-manager? , descriptor* , injection*)>
+
+<!-- The interceptors element specifies a customized stack of interceptors
+that will be used in place of the default stack. Currently this is only
+used when specified at the mbean level, but it could define a custom attribute
+or operation level interceptor stack in the future.
+-->
+<!ELEMENT interceptors (interceptor+)>
+
+<!-- The interceptor element specifies a custom interceptor stack to insert
+ahead of the standard ModelBean consisting of:
+ org.jboss.mx.interceptor.PersistenceInterceptor
+ org.jboss.mx.interceptor.MBeanAttributeInterceptor
+ org.jboss.mx.interceptor.ObjectReferenceInterceptor
+
+Each interceptor must implement the org.jboss.mx.interceptor.Interceptor
+interface, and must have either a no-arg constructor, or a constructor
+that accepts a javax.management.modelmbean.ModelMBeanInfo.
+-->
+<!ELEMENT interceptor ANY>
+
+<!ATTLIST interceptor code CDATA #REQUIRED >
+<!-- The persistence element contains descriptors for the persistPolicy,
+persistPeriod, persistLocation, and persistName properties suggested by the spec.
+-->
+<!ELEMENT persistence EMPTY>
+
+<!-- The persistPolicy defines how attributes should be persisted and must be one of:
+ Never, attribute values are transient values that are never persisted
+ OnUpdate, attribute values are persisted whenever they are updated
+ OnTimer, attribute values are persisted based on the time given by the persistPeriod.
+ NoMoreOftenThan, attribute values are persisted when updated unless but no more
+ oten than the persistPeriod.
+-->
+<!ATTLIST persistence persistPolicy (Never | OnUpdate | NoMoreOftenThan | OnTimer ) #IMPLIED>
+
+<!-- The persistPeriod attribute gives the update frequency in milliseconds if
+the perisitPolicy attribute is NoMoreOftenThan or OnTimer.
+-->
+<!ATTLIST persistence persistPeriod CDATA #IMPLIED>
+
+<!-- The persistLocation attribute specifies the location of the persistence
+store. Its form depends on the JMX implementation. Currently this should refer
+to a directory into which the attributes will be serialized.
+-->
+<!ATTLIST persistence persistLocation CDATA #IMPLIED>
+
+<!-- The persistName attribute can be used in conjunction with the
+persistLocation attribute to further qualify the persistent store location. For
+a directory persistLocation the persistName specifies the file to which the
+attributes are stored within the directory.
+-->
+<!ATTLIST persistence persistName CDATA #IMPLIED>
+
+<!-- The currencyTimeLimit element specifies the time in seconds that a cached
+value of an attribute remains valid.
+-->
+<!ELEMENT currencyTimeLimit EMPTY>
+
+<!-- The value attribute gives the currencyTimeLimit in seconds. A 0 value
+indicates that an attribute value should always be retrieved from the mbean and
+never cached. A -1 value indicates that a cache value is always valid.
+-->
+<!ATTLIST currencyTimeLimit value CDATA #IMPLIED>
+
+<!-- The displayName element specifies the human friendly name of an item
+ -->
+<!ELEMENT display-name EMPTY>
+
+<!-- The value attribute gives the string representation of the displayName
+ -->
+<!ATTLIST display-name value CDATA #IMPLIED>
+
+<!-- The persistence-manager element give the name of a class to use as the
+persistence manager.
+ -->
+<!ELEMENT persistence-manager EMPTY>
+
+<!-- The value attribute specifies the class name that supplies the
+org.jboss.mx.persistence.PersistenceManager interface implementation.
+ -->
+<!ATTLIST persistence-manager value CDATA #IMPLIED>
+
+<!-- The default element specifes a default value to use when a field has not
+been set.
+-->
+<!ELEMENT default EMPTY>
+
+<!-- The value attribute gives the default value representation
+-->
+<!ATTLIST default value CDATA #REQUIRED>
+
+<!-- The value element specifies a management attribute's current value
+-->
+<!ELEMENT value EMPTY>
+
+<!-- The value (initial) value for attribute -->
+<!ATTLIST value value CDATA #REQUIRED>
+
+<!-- The descriptor element
+-->
+<!ELEMENT descriptor EMPTY>
+
+<!-- The name attribute specifies the type of the descriptor.
+ -->
+<!ATTLIST descriptor name CDATA #REQUIRED>
+<!-- The value attribute specifies the descriptor value.
+-->
+<!ATTLIST descriptor value CDATA #REQUIRED>
+
+<!-- The notification element describes a management notification. The name
+ element contains the fully qualified name of the notification class and
+ the notification-type element contains the dot-separated notification
+ type string.
+-->
+<!ELEMENT notification (description? , name , notification-type+ , descriptors?)>
+
+<!-- The parameter element specifies an operation parameter
+-->
+<!ELEMENT parameter (description? , name , type)>
+
+<!-- The name element is used to define the fundamental name of a component, such as the
+mbean JMX name, the name of an attribute, constructor, operation, notification, etc. This is a
+case-sensitive code centric name. For notifications the name if the class name of the event
+object, javax.management.Notification or a subclass.
+-->
+<!ELEMENT name (#PCDATA)>
+
+<!-- The description element provides human readable descriptive text for constructors,
+attributes, operations, paramters, notifications, etc.
+-->
+<!ELEMENT description (#PCDATA)>
+
+<!-- The type element specifies a fully qualified name of a Java type.
+-->
+<!ELEMENT type (#PCDATA)>
+
+<!-- The return-type element specifies the return type of an operation. If not given or empty
+it is assumed to be the void type.
+-->
+<!ELEMENT return-type (#PCDATA)>
+
+<!-- The notification-type element speicifies the types of notifications that may be sent. These are
+the value that will be seen as the the javax.management.Notification.type attribute.
+-->
+<!ELEMENT notification-type (#PCDATA)>
+
+<!--
+ The injection element describes an injection point for receiving information
+ from the jmx microkernel. Each injection point specifies the type and
+ the resource setter method to use to inject the information into the
+ resource.
+-->
+<!ELEMENT injection EMPTY>
+
+<!--
+ The injection id attribute specifies the injection point type. The current
+ injection point types are:
+
+ MBeanServerType - the MBeanServer the XMBean is registered with. This requires
+ a setter with an x(javax.management.MBeanServer) signature.
+ MBeanInfoType - the XMBean ModelMBeanInfo metadata. This requires
+ a setter with an x(javax.management.MBeanInfo) signature.
+ ObjectNameType - the ObjectName the XMBean is registered under. This requires
+ a setter with an x(javax.management.ObjectName) signature.
+-->
+<!ATTLIST injection id (MBeanServerType | MBeanInfoType | ObjectNameType) #REQUIRED>
+
+<!--
+ The injection setMethod attribute gives the name of the method used to set
+ the injection value on the resource.
+-->
+<!ATTLIST injection setMethod CDATA #IMPLIED>
+
+<!--
+ provide entities for default MBean Operations
+ and the three default MBean attributes
+-->
+<!ENTITY defaultOperations '
+<operation>
+ <description>Standard MBean lifecycle method</description>
+ <name>create</name>
+</operation>
+<operation>
+ <description>The start lifecycle operation</description>
+ <name>start</name>
+</operation>
+<operation>
+ <description>The stop lifecycle operation</description>
+ <name>stop</name>
+</operation>
+<operation>
+ <description>The destroy lifecycle operation</description>
+ <name>destroy</name>
+</operation>
+<operation>
+ <description>The detyped lifecycle operation (for internal use only)</description>
+ <name>jbossInternalLifecycle</name>
+ <parameter>
+ <description>The lifecycle operation</description>
+ <name>method</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+</operation>
+'>
+
+<!ENTITY defaultAttributes '
+<attribute access="read-only" getMethod="getName">
+ <description>The class name of the MBean</description>
+ <name>Name</name>
+ <type>java.lang.String</type>
+</attribute>
+<attribute access="read-only" getMethod="getState">
+ <description>The status of the MBean</description>
+ <name>State</name>
+ <type>int</type>
+</attribute>
+<attribute access="read-only" getMethod="getStateString">
+ <description>The status of the MBean in text form</description>
+ <name>StateString</name>
+ <type>java.lang.String</type>
+</attribute>
+'>
+
+<!--
+ Methods to expose the Interceptable interface. Used in conjunction
+ with org.jboss.mx.interceptor.DynamicInterceptor
+-->
+<!ENTITY interceptable '
+<operation>
+ <description>Add dynamically an operation interceptor</description>
+ <name>addOperationInterceptor</name>
+ <parameter>
+ <description>The Interceptor</description>
+ <name>interceptor</name>
+ <type>org.jboss.mx.interceptor.Interceptor</type>
+ </parameter>
+</operation>
+<operation>
+ <description>Remove dynamically an operation interceptor</description>
+ <name>removeOperationInterceptor</name>
+ <parameter>
+ <description>The Interceptor</description>
+ <name>interceptor</name>
+ <type>org.jboss.mx.interceptor.Interceptor</type>
+ </parameter>
+</operation>
+'>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jboss_xmbean_1_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,441 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!-- $Id: jboss_xmbean_1_2.dtd 39447 2006-01-03 17:46:05Z dimitris $ -->
+
+<!-- This is the XML DTD for the JBoss MX 1.2 XMBean deployment descriptor.
+Author: Juha Lindfors
+Author: David Jencks
+Author: Matt Munz
+Author: Heiko W. Rupp
+Author: Dimitris Andreadis
+The DOCTYPE is:
+ <!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_2.dtd">
+-->
+<!--
+ The mbean element is the root element of the document containing the
+ required elements for describing the management interface of one
+ MBean (constructors, attributes, operations and notifications). It
+ also includes an optional description element that can be used to
+ describe the purpose of the MBean and attributes for persistence
+ policy and attribute caching.
+-->
+<!ELEMENT mbean (description? , descriptors? , class , constructor*,
+ attribute* , operation* , notification*)>
+
+<!-- The class element specifies the fully qualifed name of the model MBean
+implementation class. This class will be exposed as a ModelMBean by the
+JMX implementation.
+-->
+<!ELEMENT class (#PCDATA)>
+
+<!--
+ The constructor element describes the constructors of an MBean
+ that are exposed to the management application. The optional
+ description element can be used to to describe the use of the
+ constructor.
+-->
+<!ELEMENT constructor (description? , name , parameter* , descriptors?)>
+
+<!--
+ The attribute element describes the management attributes of an
+ MBean. The name element contains the attribute's name and the type
+ element contains a fully qualified class name of the attribute's
+ type.
+-->
+<!ELEMENT attribute (description? , name , type , descriptors?)>
+
+<!-- The access attribute defines the read/write access modes of an attribute -->
+<!ATTLIST attribute access (read-only | write-only | read-write ) "read-write">
+
+<!-- The getMethod attribute defines the name of the method which reads
+the named attribute. This must be specified if the managed attribute should
+be obtained from the mbean instance. -->
+<!ATTLIST attribute getMethod CDATA #IMPLIED>
+
+<!-- The setMethod attribute defines the name of the method which writes
+the named attribute. This must be specified if the managed attribute should
+be obtained from the mbean instance. -->
+<!ATTLIST attribute setMethod CDATA #IMPLIED>
+
+<!--
+ The operation element describes a management operation of an MBean.
+ The name element contains the operation's name and the parameter
+ elements describe the operation's signature. The return-type element
+ must contain a fully qualified class name of the return type from
+ this operation.
+
+ If return-type is not specified, void is assumed.
+-->
+<!ELEMENT operation (description? , name , parameter* , return-type? , descriptors?)>
+
+<!-- The impact attribute defines the impact of executing the operation and must be one of:
+ ACTION, The operation changes the state of the MBean component (write operation).
+ INFO, The operation should not alter the state of the MBean component (read operation).
+ ACTION_INFO, The operation behaves like a read/write operation.
+-->
+<!ATTLIST operation impact (ACTION | INFO | ACTION_INFO ) "ACTION_INFO">
+
+<!-- The descriptors element contains all the descriptors for a containing element, as subelements.
+The descriptors suggested in the jmx spec have predefined elements, whereas custom descriptors have
+a generic element.
+-->
+<!ELEMENT descriptors (interceptors? , persistence? , currencyTimeLimit? ,
+display-name? , default? , value? , persistence-manager? , descriptor* , injection*)>
+
+<!-- The interceptors element specifies a customized stack of interceptors
+that will be used in place of the default stack. Currently this is only
+used when specified at the mbean level, but it could define a custom attribute
+or operation level interceptor stack in the future.
+-->
+<!ELEMENT interceptors (interceptor+)>
+
+<!-- The interceptor element specifies a custom interceptor stack to insert
+ahead of the standard ModelBean consisting of:
+ org.jboss.mx.interceptor.PersistenceInterceptor
+ org.jboss.mx.interceptor.MBeanAttributeInterceptor
+ org.jboss.mx.interceptor.ObjectReferenceInterceptor
+
+Each interceptor must implement the org.jboss.mx.interceptor.Interceptor
+interface, and must have either a no-arg constructor, or a constructor
+that accepts a javax.management.modelmbean.ModelMBeanInfo.
+-->
+<!ELEMENT interceptor ANY>
+
+<!ATTLIST interceptor code CDATA #REQUIRED >
+<!-- The persistence element contains descriptors for the persistPolicy,
+persistPeriod, persistLocation, and persistName properties suggested by the spec.
+-->
+<!ELEMENT persistence EMPTY>
+
+<!-- The persistPolicy defines how attributes should be persisted and must be one of:
+ Never, attribute values are transient values that are never persisted
+ OnUpdate, attribute values are persisted whenever they are updated
+ OnTimer, attribute values are persisted based on the time given by the persistPeriod.
+ NoMoreOftenThan, attribute values are persisted when updated unless but no more
+ oten than the persistPeriod.
+-->
+<!ATTLIST persistence persistPolicy (Never | OnUpdate | NoMoreOftenThan | OnTimer ) #IMPLIED>
+
+<!-- The persistPeriod attribute gives the update frequency in milliseconds if
+the perisitPolicy attribute is NoMoreOftenThan or OnTimer.
+-->
+<!ATTLIST persistence persistPeriod CDATA #IMPLIED>
+
+<!-- The persistLocation attribute specifies the location of the persistence
+store. Its form depends on the JMX implementation. Currently this should refer
+to a directory into which the attributes will be serialized.
+-->
+<!ATTLIST persistence persistLocation CDATA #IMPLIED>
+
+<!-- The persistName attribute can be used in conjunction with the
+persistLocation attribute to further qualify the persistent store location. For
+a directory persistLocation the persistName specifies the file to which the
+attributes are stored within the directory.
+-->
+<!ATTLIST persistence persistName CDATA #IMPLIED>
+
+<!-- The currencyTimeLimit element specifies the time in seconds that a cached
+value of an attribute remains valid.
+-->
+<!ELEMENT currencyTimeLimit EMPTY>
+
+<!-- The value attribute gives the currencyTimeLimit in seconds. A 0 value
+indicates that an attribute value should always be retrieved from the mbean and
+never cached. A -1 value indicates that a cache value is always valid.
+-->
+<!ATTLIST currencyTimeLimit value CDATA #IMPLIED>
+
+<!-- The displayName element specifies the human friendly name of an item
+ -->
+<!ELEMENT display-name EMPTY>
+
+<!-- The value attribute gives the string representation of the displayName
+ -->
+<!ATTLIST display-name value CDATA #IMPLIED>
+
+<!-- The persistence-manager element give the name of a class to use as the
+persistence manager.
+ -->
+<!ELEMENT persistence-manager EMPTY>
+
+<!-- The value attribute specifies the class name that supplies the
+org.jboss.mx.persistence.PersistenceManager interface implementation.
+ -->
+<!ATTLIST persistence-manager value CDATA #IMPLIED>
+
+<!-- The default element specifes a default value to use when a field has not
+been set. Typically the value of the element is the string representation of the
+attribute, but it can be an arbitrary xml fragment.
+-->
+<!ELEMENT default ANY>
+
+<!-- The value attribute gives the default value representation.
+Alternatively a sub-element may be used, in which case 'trim' and
+'replace' apply also.
+-->
+<!ATTLIST default value CDATA #IMPLIED>
+
+<!-- The optional replace attribute indicates whether references of the form ${x}
+in the element content should be replaced with the corresponding System.getProperty(x) value.
+-->
+<!ATTLIST default replace (true | false) 'true'>
+
+<!-- The optional trim attribute specifies whether the
+element content should be trimmed of whitespace.
+-->
+<!ATTLIST default trim (true | false) 'true'>
+
+<!-- The value element specifies a management attribute's current value
+Typically the value of the element is the string representation of the
+attribute, but it can be an arbitrary xml fragment.
+-->
+<!ELEMENT value ANY>
+
+<!-- The value (initial) value for attribute. Alternatively a sub-element may be used,
+in which case 'trim' and 'replace' apply also.
+-->
+<!ATTLIST value value CDATA #IMPLIED>
+
+<!-- The optional replace attribute indicates whether references of the form ${x}
+in the element content should be replaced with the corresponding System.getProperty(x) value.
+-->
+<!ATTLIST value replace (true | false) 'true'>
+
+<!-- The optional trim attribute specifies whether the
+element content should be trimmed of whitespace.
+-->
+<!ATTLIST value trim (true | false) 'true'>
+
+<!-- The descriptor element
+-->
+<!ELEMENT descriptor EMPTY>
+
+<!-- The name attribute specifies the type of the descriptor.
+ -->
+<!ATTLIST descriptor name CDATA #REQUIRED>
+<!-- The value attribute specifies the descriptor value.
+-->
+<!ATTLIST descriptor value CDATA #REQUIRED>
+
+<!-- The notification element describes a management notification. The name
+ element contains the fully qualified name of the notification class and
+ the notification-type element contains the dot-separated notification
+ type string.
+-->
+<!ELEMENT notification (description? , name , notification-type+ , descriptors?)>
+
+<!-- The parameter element specifies an operation parameter
+-->
+<!ELEMENT parameter (description? , name , type)>
+
+<!-- The name element is used to define the fundamental name of a component, such as the
+mbean JMX name, the name of an attribute, constructor, operation, notification, etc. This is a
+case-sensitive code centric name. For notifications the name if the class name of the event
+object, javax.management.Notification or a subclass.
+-->
+<!ELEMENT name (#PCDATA)>
+
+<!-- The description element provides human readable descriptive text for constructors,
+attributes, operations, paramters, notifications, etc.
+-->
+<!ELEMENT description (#PCDATA)>
+
+<!-- The type element specifies a fully qualified name of a Java type.
+-->
+<!ELEMENT type (#PCDATA)>
+
+<!-- The return-type element specifies the return type of an operation. If not given or empty
+it is assumed to be the void type.
+-->
+<!ELEMENT return-type (#PCDATA)>
+
+<!-- The notification-type element speicifies the types of notifications that may be sent. These are
+the value that will be seen as the the javax.management.Notification.type attribute.
+-->
+<!ELEMENT notification-type (#PCDATA)>
+
+<!--
+ The injection element describes an injection point for receiving information
+ from the jmx microkernel. Each injection point specifies the type and
+ the resource setter method to use to inject the information into the
+ resource.
+-->
+<!ELEMENT injection EMPTY>
+
+<!--
+ The injection id attribute specifies the injection point type. The current
+ injection point types are:
+
+ MBeanServerType - the MBeanServer the XMBean is registered with. This requires
+ a setter with an x(javax.management.MBeanServer) signature.
+ MBeanInfoType - the XMBean ModelMBeanInfo metadata. This requires
+ a setter with an x(javax.management.MBeanInfo) signature.
+ ObjectNameType - the ObjectName the XMBean is registered under. This requires
+ a setter with an x(javax.management.ObjectName) signature.
+-->
+<!ATTLIST injection id (MBeanServerType | MBeanInfoType | ObjectNameType) #REQUIRED>
+
+<!--
+ The injection setMethod attribute gives the name of the method used to set
+ the injection value on the resource.
+-->
+<!ATTLIST injection setMethod CDATA #IMPLIED>
+
+<!--
+ provide entities for default MBean Operations
+ and the three default MBean attributes
+-->
+<!ENTITY defaultOperations '
+<operation>
+ <description>Standard MBean lifecycle method</description>
+ <name>create</name>
+</operation>
+<operation>
+ <description>The start lifecycle operation</description>
+ <name>start</name>
+</operation>
+<operation>
+ <description>The stop lifecycle operation</description>
+ <name>stop</name>
+</operation>
+<operation>
+ <description>The destroy lifecycle operation</description>
+ <name>destroy</name>
+</operation>
+<operation>
+ <description>The detyped lifecycle operation (for internal use only)</description>
+ <name>jbossInternalLifecycle</name>
+ <parameter>
+ <description>The lifecycle operation</description>
+ <name>method</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+</operation>
+'>
+
+<!ENTITY defaultAttributes '
+<attribute access="read-only" getMethod="getName">
+ <description>The class name of the MBean</description>
+ <name>Name</name>
+ <type>java.lang.String</type>
+</attribute>
+<attribute access="read-only" getMethod="getState">
+ <description>The status of the MBean</description>
+ <name>State</name>
+ <type>int</type>
+</attribute>
+<attribute access="read-only" getMethod="getStateString">
+ <description>The status of the MBean in text form</description>
+ <name>StateString</name>
+ <type>java.lang.String</type>
+</attribute>
+'>
+
+<!--
+ Common SubDeployer attributes
+-->
+<!ENTITY deployerAttributes '
+<attribute access="read-only" getMethod="getServiceName">
+ <description>The JMX ObjectName of the service that provides the SubDeployer</description>
+ <name>ServiceName</name>
+ <type>javax.management.ObjectName</type>
+</attribute>
+<attribute access="read-only" getMethod="getSuffixes">
+ <description>An array of suffixes of interest to this subdeployer</description>
+ <name>Suffixes</name>
+ <type>[Ljava.lang.String;</type>
+</attribute>
+<attribute access="read-only" getMethod="getRelativeOrder">
+ <description>The relative order of the specified suffixes</description>
+ <name>RelativeOrder</name>
+ <type>int</type>
+</attribute>
+'>
+
+<!--
+ Common SubDeployer operations
+-->
+<!ENTITY deployerOperations '
+<operation>
+ <description>This method is called by MainDeployer to determine if subdeployer can handle a deployment</description>
+ <name>accepts</name>
+ <parameter>
+ <name>di</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ <return-type>boolean</return-type>
+</operation>
+<operation>
+ <description>The init method lets the deployer set a few properties of the DeploymentInfo, such as the watch url</description>
+ <name>init</name>
+ <parameter>
+ <name>di</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ <return-type>void</return-type>
+</operation>
+<operation>
+ <description>Set up the components of the deployment that do not refer to other components</description>
+ <name>create</name>
+ <parameter>
+ <name>di</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ <return-type>void</return-type>
+</operation>
+<operation>
+ <description>The start method starts all the mbeans in this DeploymentInfo</description>
+ <name>start</name>
+ <parameter>
+ <name>di</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ <return-type>void</return-type>
+</operation>
+<operation>
+ <description>The stop method invokes stop on the mbeans associated with the deployment in reverse order relative to start</description>
+ <name>stop</name>
+ <parameter>
+ <name>di</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ <return-type>void</return-type>
+</operation>
+<operation>
+ <description>The destroy method invokes destroy on the mbeans associated with the deployment in reverse order relative to create</description>
+ <name>destroy</name>
+ <parameter>
+ <name>di</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ <return-type>void</return-type>
+</operation>
+'>
+
+<!--
+ Methods to expose the Interceptable interface. Used in conjunction
+ with org.jboss.mx.interceptor.DynamicInterceptor
+-->
+<!ENTITY interceptable '
+<operation>
+ <description>Add dynamically an operation interceptor</description>
+ <name>addOperationInterceptor</name>
+ <parameter>
+ <description>The Interceptor</description>
+ <name>interceptor</name>
+ <type>org.jboss.mx.interceptor.Interceptor</type>
+ </parameter>
+</operation>
+<operation>
+ <description>Remove dynamically an operation interceptor</description>
+ <name>removeOperationInterceptor</name>
+ <parameter>
+ <description>The Interceptor</description>
+ <name>interceptor</name>
+ <type>org.jboss.mx.interceptor.Interceptor</type>
+ </parameter>
+</operation>
+'>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_3_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_3_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_3_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,608 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+This is the XML DTD for the jbosscmp-jdbc deployment descriptor.
+ <!DOCTYPE jbosscmp-jdbc PUBLIC
+ "-//JBoss//DTD JBOSSCMP-JDBC 3.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_3_0.dtd">
+-->
+
+<!--
+The root element of JBossCMP-JDBC configuration files.
+-->
+<!ELEMENT jbosscmp-jdbc (defaults?, enterprise-beans?, relationships?,
+ dependent-value-classes?, type-mappings?)>
+
+<!--
+The optional defaults elements contains the default values for
+entities, and relationships.
+-->
+<!ELEMENT defaults ((datasource, datasource-mapping)?, create-table?,
+ remove-table?, read-only?, read-time-out?, row-locking?,
+ pk-constraint?, fk-constraint?, preferred-relation-mapping?,
+ read-ahead?, list-cache-max?, fetch-size?)>
+
+
+<!--
+The optional datasource element contains the jndi-name used to lookup
+the datasource. All database connections used by an entity or relation table are obtained from the datasource.
+-->
+<!ELEMENT datasource (#PCDATA)>
+
+
+<!--
+The optional datasource-mapping element contains the name of the type mapping
+that will be used for this datasource.
+-->
+<!ELEMENT datasource-mapping (#PCDATA)>
+
+
+<!--
+Should the persistence manager attempt to create tables if they are
+not present?
+
+The create-table element must be one of the two following:
+ <create-table>true</create-table>
+ <create-table>false</create-table>
+-->
+<!ELEMENT create-table (#PCDATA)>
+
+
+<!--
+Should the persistence manager attempt to remove tables during shutdown?
+
+The remove-table element must be one of the two following:
+ <remove-table>true</remove-table>
+ <remove-table>false</remove-table>
+-->
+<!ELEMENT remove-table (#PCDATA)>
+
+
+<!--
+Is the entity or cmp-field read-only?
+
+The read-only element must be one of the two following:
+ <read-only>true</read-only>
+ <read-only>false</read-only>
+-->
+<!ELEMENT read-only (#PCDATA)>
+
+
+<!--
+Specifies the ammount of time that a read-only field is considered
+valid (milliseconds).
+-->
+<!ELEMENT read-time-out (#PCDATA)>
+
+
+<!--
+Should select statements the SELECT ... FOR UPDATE syntax?
+
+The row-locking element must be one of the two following:
+ <row-locking>true</row-locking>
+ <row-locking>false</row-locking>
+-->
+<!ELEMENT row-locking (#PCDATA)>
+
+
+<!--
+Should a foreign key constraint be added for this relationship role?
+
+The fk-constraint element must be one of the two following:
+ <fk-constraint>true</fk-constraint>
+ <fk-constraint>false</fk-constraint>
+-->
+<!ELEMENT fk-constraint (#PCDATA)>
+
+
+<!--
+Should a primary key constraint be added when creating tables?
+
+The pk-constraint element must be one of the two following:
+ <pk-constraint>true</pk-constraint>
+ <pk-constraint>false</pk-constraint>
+-->
+<!ELEMENT pk-constraint (#PCDATA)>
+
+
+<!--
+Specifies the preferred mapping style for relationships.
+
+The preferred-relation-mapping element must be one of the two following:
+ <preferred-relation-mapping>foreign-key</preferred-relation-mapping>
+ <preferred-relation-mapping>relation-table</preferred-relation-mapping>
+-->
+<!ELEMENT preferred-relation-mapping (#PCDATA)>
+
+<!--
+Specifies the read ahead strategy.
+
+ <read-ahead>
+ <strategy>on-load</strategy>
+ <page-size>255</page-size>
+ <eager-load-group>*</eager-load-group>
+ </read-ahead>
+-->
+<!ELEMENT read-ahead (strategy, page-size?, eager-load-group?)>
+
+<!--
+Specifies the strategy used to read-ahead data in queries.
+
+The strategy element must be one of the two following:
+ <strategy>none</strategy>
+ <strategy>on-load</strategy>
+ <strategy>on-find</strategy>
+-->
+<!ELEMENT strategy (#PCDATA)>
+
+
+<!--
+Specifies the number of entities that will be read in a single
+read-ahead load query.
+-->
+<!ELEMENT page-size (#PCDATA)>
+
+
+<!--
+Specifies the number of simultaneous queries that can be tracked by
+the cache for an entity.
+-->
+<!ELEMENT list-cache-max (#PCDATA)>
+
+
+<!--
+Specifies the number of entities to read in one round-trip to
+the underlying datastore.
+-->
+<!ELEMENT fetch-size (#PCDATA)>
+
+
+<!--
+The enterprise-beans element contains the entity elements that will
+be configured.
+-->
+<!ELEMENT enterprise-beans (entity+)>
+
+
+<!--
+The entity element contains the configuration of an entity
+-->
+<!ELEMENT entity (ejb-name, (datasource, datasource-mapping)?, create-table?,
+ remove-table?, read-only?, read-time-out?, row-locking?,
+ pk-constraint?, read-ahead?, list-cache-max?, fetch-size?, table-name?,
+ cmp-field*, load-groups?, eager-load-group?, lazy-load-groups?,
+ query*)>
+
+<!--
+Name of the entity being configured. This must match an entity declared
+in the ejb-jar.xml file.
+-->
+<!ELEMENT ejb-name (#PCDATA)>
+
+
+<!--
+This is the name of the table that will hold data for this entity.
+Each entity instance will be stored in one row of this table.
+-->
+<!ELEMENT table-name (#PCDATA)>
+
+
+<!--
+The cmp-field element contains the configuration of a cmp-field.
+-->
+<!ELEMENT cmp-field (field-name, read-only?, read-time-out?,
+ column-name?, not-null?, ((jdbc-type, sql-type) | (property+))? )>
+
+
+<!--
+Name of the cmp-field being configured. This must match a cmp-field
+declared for this entity in the ejb-jar.xml file.
+-->
+<!ELEMENT field-name (#PCDATA)>
+
+
+<!--
+The name of the column that will hold the data for this field.
+-->
+<!ELEMENT column-name (#PCDATA)>
+
+
+<!--
+If present the field will not allow a field value.
+-->
+<!ELEMENT not-null EMPTY>
+
+
+<!--
+This is the JDBC type that is used when setting parameters in a JDBC
+PreparedStatement or loading data from a JDBC ResultSet for this
+cmp-field. The valid types are defined in java.sql.Types.
+-->
+<!ELEMENT jdbc-type (#PCDATA)>
+
+
+<!--
+This is the SQL type that is used in create table statements for
+this field. Valid sql-types are only limited by your database vendor.
+-->
+<!ELEMENT sql-type (#PCDATA)>
+
+
+<!--
+The property element contains the configuration of a dependent
+value class property of a cmp-field that is the type of a dependent
+value class.
+-->
+<!ELEMENT property (property-name, column-name?, not-null?,
+ (jdbc-type, sql-type)?)>
+
+
+<!--
+Name of the property being configured. In a dependent-value-class
+element this must match a JavaBean property of the class. In a
+cmp-field element this must match a flattened propety of the
+dependent-value-class field type.
+-->
+<!ELEMENT property-name (#PCDATA)>
+
+<!--
+Contains the named load groups.
+-->
+<!ELEMENT load-groups (load-group+)>
+
+
+<!--
+A named group of fields that will be loaded together.
+-->
+<!ELEMENT load-group (description?, load-group-name, field-name+)>
+
+<!--
+Contains the name of a load group.
+-->
+<!ELEMENT load-group-name (#PCDATA)>
+
+
+<!--
+Contains the name of the load group that will eager loaded for this entity.
+-->
+<!ELEMENT eager-load-group (#PCDATA)>
+
+
+<!--
+Contains the names of the groups that will be lazy loaded together.
+-->
+<!ELEMENT lazy-load-groups (load-group-name+)>
+
+
+<!--
+Descriptive text.
+-->
+<!ELEMENT description (#PCDATA)>
+
+
+<!--
+The query element contains the configuration of a query.
+-->
+<!ELEMENT query (description?, query-method,
+ (jboss-ql | dynamic-ql | declared-sql)?, read-ahead?)>
+
+
+<!--
+The query method that being configured. This must match a
+query-method declared for this entity in the ejb-jar.xml file.
+-->
+<!ELEMENT query-method (method-name, method-params)>
+
+
+<!--
+The name of the query method that is being configured.
+-->
+<!ELEMENT method-name (#PCDATA)>
+
+
+<!--
+The method-parameters contains the parameters of the method that is
+being configured. Method parameters must be in the same order as the
+method and have the same type.
+-->
+<!ELEMENT method-params (method-param*)>
+
+
+<!--
+The java class of one parameter for a query.
+
+An example follows:
+ <method-param>java.lang.String</method-param>
+-->
+<!ELEMENT method-param (#PCDATA)>
+
+
+<!--
+JBossQL query. JBossQL is a superset of EJB-QL.
+-->
+<!ELEMENT jboss-ql (#PCDATA)>
+
+
+<!--
+Dynamic JBossQL query. The JBossQL is passed to the query and compiled
+on the fly.
+-->
+<!ELEMENT dynamic-ql EMPTY>
+
+
+<!--
+Explicitly declared sql fragments.
+-->
+<!ELEMENT declared-sql (select?, from?, where?, order?, other?)>
+
+
+<!--
+Delcares what is to be selected. A finder may only have the distinct element.
+-->
+<!ELEMENT select (distinct?, (ejb-name, field-name?)?, alias?)>
+
+
+<!--
+Delared additional SQl to append to the generated from clause.
+
+Example: <from>, FullAddressEJB as a</from>
+-->
+<!ELEMENT from (#PCDATA)>
+
+<!--
+If the empty distinct element is present, the SELECT DISTINCT
+syntax will be used. This syntax is used by default for ejbSelect
+methods that return a java.util.Set.
+-->
+<!ELEMENT distinct EMPTY>
+
+
+<!--
+Declares the where clause for the query.
+
+Example: <where>TITLE={0} OR ARTIST={0} OR TYPE={0} OR NOTES={0}</where>
+-->
+<!ELEMENT where (#PCDATA)>
+
+
+<!--
+Declares the order clause for the query.
+
+Example: <order>TITLE</order>
+-->
+<!ELEMENT order (#PCDATA)>
+
+
+<!--
+Declares the other sql that is appended to the end of a query.
+
+Example: <other>LIMIT 100 OFFSET 200</other>
+-->
+<!ELEMENT other (#PCDATA)>
+
+<!--
+Declare the alias to use for the main select table.
+
+Example: <alias>my_table</alias>
+-->
+<!ELEMENT alias (#PCDATA)>
+
+
+<!--
+The relationships element contains the ejb-relation elements that will
+be configured.
+-->
+<!ELEMENT relationships (ejb-relation+)>
+
+
+<!--
+The ejb-relation element contains the configuration of an
+ejb-relation.
+-->
+<!ELEMENT ejb-relation (ejb-relation-name, read-only?, read-time-out?,
+ (foreign-key-mapping | relation-table-mapping)?,
+ (ejb-relationship-role, ejb-relationship-role)?)>
+
+
+<!--
+Name of the ejb-relation being configured. This must match an
+ejb-relation declared in the ejb-jar.xml file.
+-->
+<!ELEMENT ejb-relation-name (#PCDATA)>
+
+
+<!--
+Specifies that the ejb-relation should be mapped with foreign-keys.
+This mapping is not available for many-to-many relationships.
+-->
+<!ELEMENT foreign-key-mapping EMPTY>
+
+
+<!--
+Specifies that the ejb-relation should be mapped with a relation-table.
+-->
+<!ELEMENT relation-table-mapping (table-name?,
+ (datasource, datasource-mapping)?, create-table?, remove-table?,
+ row-locking?, pk-constraint?)>
+
+
+<!--
+The ejb-rejationship-role element contains the configuration of an
+ejb-relationship-role.
+-->
+<!ELEMENT ejb-relationship-role (ejb-relationship-role-name,
+ fk-constraint?, key-fields?, read-ahead?)>
+
+
+<!--
+Name of the ejb-relationship-role being configured. This must match
+an ejb-relationship-role declared for this ejb-relation in the
+ejb-jar.xml file.
+-->
+<!ELEMENT ejb-relationship-role-name (#PCDATA)>
+
+
+<!--
+Contains the key fields. The interperation of the key fields depends
+on the mapping style of the relationship.
+-->
+<!ELEMENT key-fields (key-field*)>
+
+<!--
+The key-field element declared the configuration of a key field.
+The field-name element must match the field-name of one of the
+primary key fields of the this entity.
+-->
+<!ELEMENT key-field (field-name,
+ ((column-name, (jdbc-type, sql-type)?) | (property*))
+ )>
+
+
+<!--
+Contains the known dependent value classes.
+-->
+<!ELEMENT dependent-value-classes (dependent-value-class*)>
+
+
+<!--
+The dependent-value-class element contains the configuration of a
+dependent value class.
+-->
+<!ELEMENT dependent-value-class (description?, class, property+)>
+
+
+<!--
+Name of the java class to which the dependent value class configuration
+applies.
+-->
+<!ELEMENT class (#PCDATA)>
+
+
+<!--
+The type-mappings element contains the java to sql mappings.
+-->
+<!ELEMENT type-mappings (type-mapping+)>
+
+<!--
+The type-mapping element contains a named java to sql mapping.
+This includes both type mapping and function mapping.
+-->
+<!ELEMENT type-mapping (name, row-locking-template, pk-constraint-template,
+ fk-constraint-template, alias-header-prefix, alias-header-suffix,
+ alias-max-length, subquery-supported, true-mapping, false-mapping,
+ function-mapping*, mapping+)>
+
+<!--
+Name of the type-mapping.
+-->
+<!ELEMENT name (#PCDATA)>
+
+<!--
+This is the template used to create a row lock on the selected rows. The
+arguments supplied are as follows:
+
+1. Select clause
+2. From clasue; the order of the tables is currently not guarenteed
+3. Where clause
+
+If row locking is not supported in select statement this element should be
+empty. The most common form of row locking is select for update as in the
+example that follows:
+
+SELECT ?1 FROM ?2 WHERE ?3 FOR UPDATE
+-->
+<!ELEMENT row-locking-template (#PCDATA)>
+
+<!--
+This is the template used to create a primary key constraint in the create
+table statement. The arguments supplied are as follows:
+
+1. Primary key constraint name; which is always pk_{table-name}
+2. Comma sepperated list of primary key column names
+
+If a primary key constraint clause is not supported in a create table statement
+this element should be empty. The most common form of a primary key constraint
+follows:
+
+CONSTRAINT ?1 PRIMARY KEY (?2)
+-->
+<!ELEMENT pk-constraint-template (#PCDATA)>
+
+<!--
+This is the template used to create a foreign key constraint in sepperate
+statement. The arguments supplied are as follows:
+
+1. Table name
+2. Foreign key constraint name; which is always fk_{table-name}_{cmr-field-name}
+3. Comma sepperated list of foreign key column names
+4. References table name
+5. Comma sepperated list of the referenced primary key column names
+
+If the datasource does not support foreign key constraints this element should
+be empty. The most common form of a foreign key constraint follows:
+
+ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)
+-->
+<!ELEMENT fk-constraint-template (#PCDATA)>
+
+<!--
+An alias header is prepended to a generated table alias by the EJB-QL compiler
+to prevent name collisions. An alias header is constructed as folows:
+
+alias-header-prefix + int_counter + alias-header-suffix
+-->
+<!ELEMENT alias-header-prefix (#PCDATA)>
+<!ELEMENT alias-header-suffix (#PCDATA)>
+<!ELEMENT alias-max-length (#PCDATA)>
+
+<!--
+Does this type-mapping support subqueries. Some EJB-QL opperators are mapped
+to exists subqueries. If subquery is false the EJB-QL compiler will use a
+left join and is null.
+
+The subquery-supported element must be one of the two following:
+ <create-table>true</create-table>
+ <create-table>false</create-table>
+-->
+<!ELEMENT subquery-supported (#PCDATA)>
+
+<!--
+The true and false mappings are the mappings for true and false in EJB-QL
+queries.
+-->
+<!ELEMENT true-mapping (#PCDATA)>
+<!ELEMENT false-mapping (#PCDATA)>
+
+<!--
+Specifies the mapping from a java type to a jdbc and a sql type.
+-->
+<!ELEMENT mapping (java-type, jdbc-type, sql-type)>
+
+<!--
+Specifies the java class type to be mapped.
+-->
+<!ELEMENT java-type (#PCDATA)>
+
+<!--
+Specifies the mapping from an EJB-QL function to a sql function.
+-->
+<!ELEMENT function-mapping (function-name, function-sql)>
+
+<!--
+The name of the function to be mapped.
+-->
+<!ELEMENT function-name (#PCDATA)>
+
+<!--
+The sql to which the function is mapped. The sql can contain
+parameters specified with a question mark followed by the base one
+parameter number. For example, function mapping for concat in Oracle
+follows:
+
+<function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+</function-mapping>
+-->
+<!ELEMENT function-sql (#PCDATA)>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_3_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_3_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_3_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,960 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+This is the XML DTD for the jbosscmp-jdbc deployment descriptor.
+ <!DOCTYPE jbosscmp-jdbc PUBLIC
+ "-//JBoss//DTD JBOSSCMP-JDBC 3.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_3_2.dtd">
+-->
+
+<!--
+The root element of JBossCMP-JDBC configuration files.
+-->
+<!ELEMENT jbosscmp-jdbc (defaults?, enterprise-beans?, relationships?,
+ dependent-value-classes?, type-mappings?, entity-commands?,
+ user-type-mappings? , reserved-words?)>
+
+<!--
+The optional defaults elements contains the default values for
+entities, and relationships.
+-->
+<!ELEMENT defaults ((datasource, datasource-mapping)?, create-table?,
+ alter-table?, remove-table?, post-table-create?, read-only?, read-time-out?,
+ row-locking?, pk-constraint?, fk-constraint?,
+ preferred-relation-mapping?, read-ahead?, list-cache-max?, clean-read-ahead-on-load?,
+ fetch-size?, unknown-pk?, entity-command?, ql-compiler?, throw-runtime-exceptions?)>
+
+<!--
+The optional datasource element contains the jndi-name used to lookup
+the datasource. All database connections used by an entity or relation table are obtained from the datasource.
+-->
+<!ELEMENT datasource (#PCDATA)>
+
+
+<!--
+The optional datasource-mapping element contains the name of the type mapping
+that will be used for this datasource.
+-->
+<!ELEMENT datasource-mapping (#PCDATA)>
+
+
+<!--
+Should the persistence manager attempt to create tables if they are
+not present?
+
+The create-table element must be one of the two following:
+ <create-table>true</create-table>
+ <create-table>false</create-table>
+-->
+<!ELEMENT create-table (#PCDATA)>
+
+
+<!--
+Should the persistence manager attempt to remove tables during shutdown?
+
+The remove-table element must be one of the two following:
+ <remove-table>true</remove-table>
+ <remove-table>false</remove-table>
+-->
+<!ELEMENT remove-table (#PCDATA)>
+
+<!--
+Should the persistence manager attempt to update the table structure at deployment
+
+The remove-table element must be one of the two following:
+ <alter-table>true</alter-table>
+ <alter-table>false</alter-table>
+-->
+<!ELEMENT alter-table (#PCDATA)>
+
+
+<!--
+Execute arbitrary SQL code directly after the database table is created.
+This command is only executed if create-table is true and the table
+did not previously exist.
+-->
+<!ELEMENT post-table-create (sql-statement+)>
+
+<!--
+The SQL Statement to be executed. Note that this is not translated
+into database specific SQL, but passed literally to the database.
+-->
+<!ELEMENT sql-statement (#PCDATA)>
+
+<!--
+Is the entity or cmp-field read-only?
+
+The read-only element must be one of the two following:
+ <read-only>true</read-only>
+ <read-only>false</read-only>
+-->
+<!ELEMENT read-only (#PCDATA)>
+
+
+<!--
+Specifies the ammount of time that a read-only field is considered
+valid (milliseconds).
+-->
+<!ELEMENT read-time-out (#PCDATA)>
+
+
+<!--
+Should select statements the SELECT ... FOR UPDATE syntax?
+
+The row-locking element must be one of the two following:
+ <row-locking>true</row-locking>
+ <row-locking>false</row-locking>
+-->
+<!ELEMENT row-locking (#PCDATA)>
+
+
+<!--
+Should a foreign key constraint be added for this relationship role?
+
+The fk-constraint element must be one of the two following:
+ <fk-constraint>true</fk-constraint>
+ <fk-constraint>false</fk-constraint>
+-->
+<!ELEMENT fk-constraint (#PCDATA)>
+
+
+<!--
+Should a primary key constraint be added when creating tables?
+
+The pk-constraint element must be one of the two following:
+ <pk-constraint>true</pk-constraint>
+ <pk-constraint>false</pk-constraint>
+-->
+<!ELEMENT pk-constraint (#PCDATA)>
+
+
+<!--
+Specifies the preferred mapping style for relationships.
+
+The preferred-relation-mapping element must be one of the two following:
+ <preferred-relation-mapping>foreign-key</preferred-relation-mapping>
+ <preferred-relation-mapping>relation-table</preferred-relation-mapping>
+-->
+<!ELEMENT preferred-relation-mapping (#PCDATA)>
+
+<!--
+Specifies the read ahead strategy.
+
+ <read-ahead>
+ <strategy>on-load</strategy>
+ <page-size>255</page-size>
+ <eager-load-group>*</eager-load-group>
+ </read-ahead>
+-->
+<!ELEMENT read-ahead (strategy, page-size?, eager-load-group?, left-join*)>
+
+<!--
+Specifies the strategy used to read-ahead data in queries.
+
+The strategy element must be one of the two following:
+ <strategy>none</strategy>
+ <strategy>on-load</strategy>
+ <strategy>on-find</strategy>
+-->
+<!ELEMENT strategy (#PCDATA)>
+
+
+<!--
+Specifies the number of entities that will be read in a single
+read-ahead load query.
+-->
+<!ELEMENT page-size (#PCDATA)>
+
+
+<!--
+Specifies a related entity that will be fetched on-find with LEFT JOIN.
+
+ <read-ahead>
+ <strategy>on-find</strategy>
+ <eager-load-group>report</eager-load-group>
+ <left-join cmr-field="lineItems"/>
+ <left-join cmr-field="product" eager-load-group="short"/>
+ </left-join>
+ <left-join cmr-field="customer" eager-load-group="basic"/>
+ </read-ahead>
+-->
+<!ELEMENT left-join (left-join*)>
+
+<!--
+The CMR field name to LEFT JOIN.
+-->
+<!ATTLIST left-join cmr-field CDATA #REQUIRED>
+
+<!--
+The eager load group of the related entity.
+-->
+<!ATTLIST left-join eager-load-group CDATA #IMPLIED>
+
+
+<!--
+Specifies whether the read-ahead cache should be cleaned after the instance was loaded.
+Allowed values are true and false.
+Since 3.2.5RC1. Previously, read-ahead cache was cleaned after loading.
+-->
+<!ELEMENT clean-read-ahead-on-load (#PCDATA)>
+
+
+<!--
+Specifies the number of simultaneous queries that can be tracked by
+the cache for an entity.
+-->
+<!ELEMENT list-cache-max (#PCDATA)>
+
+
+<!--
+Specifies the number of entities to read in one round-trip to
+the underlying datastore.
+-->
+<!ELEMENT fetch-size (#PCDATA)>
+
+
+<!--
+Should runtime exceptions be thrown when unexpected exception occurs ?
+
+The throw-runtime-exceptions element must be one of the two following:
+ <throw-runtime-exceptions>true</throw-runtime-exceptions>
+ <throw-runtime-exceptions>false</throw-runtime-exceptions>
+-->
+<!ELEMENT throw-runtime-exceptions (#PCDATA)>
+
+
+<!--
+The enterprise-beans element contains the entity elements that will
+be configured.
+-->
+<!ELEMENT enterprise-beans (entity+)>
+
+
+<!--
+The entity element contains the configuration of an entity
+-->
+<!ELEMENT entity (ejb-name, (datasource, datasource-mapping)?, create-table?,
+ remove-table?, post-table-create?, read-only?, read-time-out?,
+ row-locking?, pk-constraint?, read-ahead?, list-cache-max?, clean-read-ahead-on-load?,
+ fetch-size?, table-name?, cmp-field*, load-groups?, eager-load-group?,
+ lazy-load-groups?, query*, unknown-pk?, entity-command?,
+ optimistic-locking?, audit?)>
+
+<!--
+Name of the entity being configured. This must match an entity declared
+in the ejb-jar.xml file.
+-->
+<!ELEMENT ejb-name (#PCDATA)>
+
+
+<!--
+This is the name of the table that will hold data for this entity.
+Each entity instance will be stored in one row of this table.
+-->
+<!ELEMENT table-name (#PCDATA)>
+
+
+<!--
+The cmp-field element contains the configuration of a cmp-field.
+-->
+<!ELEMENT cmp-field (field-name, read-only?, read-time-out?,
+ column-name?, not-null?, ((jdbc-type, sql-type) | (property+))?,
+ auto-increment?, dbindex?, check-dirty-after-get?, state-factory? )>
+
+
+<!--
+Name of the cmp-field being configured. This must match a cmp-field
+declared for this entity in the ejb-jar.xml file.
+-->
+<!ELEMENT field-name (#PCDATA)>
+
+
+<!--
+The name of the column that will hold the data for this field.
+-->
+<!ELEMENT column-name (#PCDATA)>
+
+
+<!--
+If present the field will not allow a field value.
+-->
+<!ELEMENT not-null EMPTY>
+
+<!--
+If present, the server will try to create an index on the column
+in the database called <fieldname>_index
+-->
+<!ELEMENT dbindex EMPTY>
+
+
+<!--
+This is the JDBC type that is used when setting parameters in a JDBC
+PreparedStatement or loading data from a JDBC ResultSet for this
+cmp-field. The valid types are defined in java.sql.Types.
+-->
+<!ELEMENT jdbc-type (#PCDATA)>
+
+
+<!--
+This is the SQL type that is used in create table statements for
+this field. Valid sql-types are only limited by your database vendor.
+-->
+<!ELEMENT sql-type (#PCDATA)>
+
+
+<!--
+The property element contains the configuration of a dependent
+value class property of a cmp-field that is the type of a dependent
+value class.
+-->
+<!ELEMENT property (property-name, column-name?, not-null?,
+ (jdbc-type, sql-type)?)>
+
+
+<!--
+Name of the property being configured. In a dependent-value-class
+element this must match a JavaBean property of the class. In a
+cmp-field element this must match a flattened propety of the
+dependent-value-class field type.
+-->
+<!ELEMENT property-name (#PCDATA)>
+
+
+<!--
+Can be true or false.
+If true, the field will be checked for dirty state at synchronization time.
+By default, all fields except for the fields of primitive and their wrapper types
+are checked for dirty state after get.
+-->
+<!ELEMENT check-dirty-after-get (#PCDATA)>
+
+<!--
+Fully qualified class name of the implementation of
+ org.jboss.ejb.plugins.cmp.jdbc.CMPFieldStateFactory.
+-->
+<!ELEMENT state-factory (#PCDATA)>
+
+<!--
+Contains the named load groups.
+-->
+<!ELEMENT load-groups (load-group+)>
+
+
+<!--
+A named group of fields that will be loaded together.
+-->
+<!ELEMENT load-group (description?, load-group-name, field-name+)>
+
+<!--
+Contains the name of a load group.
+-->
+<!ELEMENT load-group-name (#PCDATA)>
+
+
+<!--
+Contains the name of the load group that will eager loaded for this entity.
+-->
+<!ELEMENT eager-load-group (#PCDATA)>
+
+
+<!--
+Contains the names of the groups that will be lazy loaded together.
+-->
+<!ELEMENT lazy-load-groups (load-group-name+)>
+
+
+<!--
+Descriptive text.
+-->
+<!ELEMENT description (#PCDATA)>
+
+
+<!--
+The query element contains the configuration of a query.
+-->
+<!ELEMENT query (description?, query-method,
+ (jboss-ql | dynamic-ql | declared-sql)?, read-ahead?, ql-compiler?, lazy-resultset-loading?)>
+
+
+<!--
+The query method that being configured. This must match a
+query-method declared for this entity in the ejb-jar.xml file.
+-->
+<!ELEMENT query-method (method-name, method-params)>
+
+
+<!--
+The name of the query method that is being configured.
+-->
+<!ELEMENT method-name (#PCDATA)>
+
+
+<!--
+The method-parameters contains the parameters of the method that is
+being configured. Method parameters must be in the same order as the
+method and have the same type.
+-->
+<!ELEMENT method-params (method-param*)>
+
+
+<!--
+The java class of one parameter for a query.
+
+An example follows:
+ <method-param>java.lang.String</method-param>
+-->
+<!ELEMENT method-param (#PCDATA)>
+
+
+<!--
+JBossQL query. JBossQL is a superset of EJB-QL.
+-->
+<!ELEMENT jboss-ql (#PCDATA)>
+
+
+<!--
+Dynamic JBossQL query. The JBossQL is passed to the query and compiled
+on the fly.
+-->
+<!ELEMENT dynamic-ql EMPTY>
+
+
+<!--
+Explicitly declared sql fragments.
+-->
+<!ELEMENT declared-sql (select?, from?, where?, order?, other?)>
+
+
+<!--
+Delcares what is to be selected. A finder may only have the distinct element.
+-->
+<!ELEMENT select (distinct?, (ejb-name, field-name?)?, alias?, additional-columns?)>
+
+
+<!--
+Delared additional SQl to append to the generated from clause.
+
+Example: <from>, FullAddressEJB as a</from>
+-->
+<!ELEMENT from (#PCDATA)>
+
+<!--
+If the empty distinct element is present, the SELECT DISTINCT
+syntax will be used. This syntax is used by default for ejbSelect
+methods that return a java.util.Set.
+-->
+<!ELEMENT distinct EMPTY>
+
+
+<!--
+Declares the where clause for the query.
+
+Example: <where>TITLE={0} OR ARTIST={0} OR TYPE={0} OR NOTES={0}</where>
+-->
+<!ELEMENT where (#PCDATA)>
+
+
+<!--
+Declares the order clause for the query.
+
+Example: <order>TITLE</order>
+-->
+<!ELEMENT order (#PCDATA)>
+
+
+<!--
+Declares the other sql that is appended to the end of a query.
+
+Example: <other>LIMIT 100 OFFSET 200</other>
+-->
+<!ELEMENT other (#PCDATA)>
+
+<!--
+Declare the alias to use for the main select table.
+
+Example: <alias>my_table</alias>
+-->
+<!ELEMENT alias (#PCDATA)>
+
+
+<!--
+Declares other columns to be selected to satisfy ordering
+by arbitrary columns with ejbFinders or to facilitate aggregate
+functions in ejbSelects.
+
+Example: <additional-columns>, join-table1.column1,
+ join-table2.column2</additional-columns>
+-->
+<!ELEMENT additional-columns (#PCDATA)>
+
+
+<!--
+Fully qualified name of QL compiler implementation class.
+-->
+<!ELEMENT ql-compiler (#PCDATA)>
+
+
+<!--
+The relationships element contains the ejb-relation elements that will
+be configured.
+-->
+<!ELEMENT relationships (ejb-relation+)>
+
+
+<!--
+The ejb-relation element contains the configuration of an
+ejb-relation.
+-->
+<!ELEMENT ejb-relation (ejb-relation-name, read-only?, read-time-out?,
+ (foreign-key-mapping | relation-table-mapping)?,
+ (ejb-relationship-role, ejb-relationship-role)?)>
+
+
+<!--
+Name of the ejb-relation being configured. This must match an
+ejb-relation declared in the ejb-jar.xml file.
+-->
+<!ELEMENT ejb-relation-name (#PCDATA)>
+
+
+<!--
+Specifies that the ejb-relation should be mapped with foreign-keys.
+This mapping is not available for many-to-many relationships.
+-->
+<!ELEMENT foreign-key-mapping EMPTY>
+
+
+<!--
+Specifies that the ejb-relation should be mapped with a relation-table.
+-->
+<!ELEMENT relation-table-mapping (table-name?,
+ (datasource, datasource-mapping)?, create-table?, remove-table?,
+ post-table-create?,
+ row-locking?, pk-constraint?)>
+
+
+<!--
+The ejb-rejationship-role element contains the configuration of an
+ejb-relationship-role.
+-->
+<!ELEMENT ejb-relationship-role (ejb-relationship-role-name,
+ fk-constraint?, key-fields?, read-ahead?, batch-cascade-delete?)>
+
+<!--
+The batch-cascade-delete element specifies that, this side of the relationship
+should be batch deleted with one SQL statement of the form
+DELETE FROM <related-table> WHERE <foreign-key> = ?
+The presense of cascade-delete element in ejb-jar.xml for the matching
+ejb-relationship-role is mandatory.
+-->
+<!ELEMENT batch-cascade-delete EMPTY>
+
+
+<!--
+Name of the ejb-relationship-role being configured. This must match
+an ejb-relationship-role declared for this ejb-relation in the
+ejb-jar.xml file.
+-->
+<!ELEMENT ejb-relationship-role-name (#PCDATA)>
+
+
+<!--
+Contains the key fields. The interperation of the key fields depends
+on the mapping style of the relationship.
+-->
+<!ELEMENT key-fields (key-field*)>
+
+<!--
+The key-field element declared the configuration of a key field.
+The field-name element must match the field-name of one of the
+primary key fields of the this entity.
+-->
+<!ELEMENT key-field (field-name,
+ ((column-name, (jdbc-type, sql-type)?) | (property*)),
+ dbindex?)>
+
+
+<!--
+Contains the known dependent value classes.
+-->
+<!ELEMENT dependent-value-classes (dependent-value-class*)>
+
+
+<!--
+The dependent-value-class element contains the configuration of a
+dependent value class.
+-->
+<!ELEMENT dependent-value-class (description?, class, property+)>
+
+
+<!--
+Name of the java class to which the dependent value class configuration
+applies.
+-->
+<!ELEMENT class (#PCDATA)>
+
+
+<!--
+The type-mappings element contains the java to sql mappings.
+-->
+<!ELEMENT type-mappings (type-mapping+)>
+
+<!--
+The type-mapping element contains a named java to sql mapping.
+This includes both type mapping and function mapping.
+-->
+<!ELEMENT type-mapping (name, row-locking-template, pk-constraint-template,
+ fk-constraint-template, auto-increment-template?,
+ add-column-template?, alter-column-template?, drop-column-template?,
+ alias-header-prefix,
+ alias-header-suffix, alias-max-length, subquery-supported,
+ true-mapping, false-mapping, max-keys-in-delete?,
+ function-mapping*, mapping+)>
+
+<!--
+Name of the type-mapping.
+-->
+<!ELEMENT name (#PCDATA)>
+
+<!--
+This is the template used to create a row lock on the selected rows. The
+arguments supplied are as follows:
+
+1. Select clause
+2. From clasue; the order of the tables is currently not guarenteed
+3. Where clause
+
+If row locking is not supported in select statement this element should be
+empty. The most common form of row locking is select for update as in the
+example that follows:
+
+SELECT ?1 FROM ?2 WHERE ?3 FOR UPDATE
+-->
+<!ELEMENT row-locking-template (#PCDATA)>
+
+<!--
+This is the template used to create a primary key constraint in the create
+table statement. The arguments supplied are as follows:
+
+1. Primary key constraint name; which is always pk_{table-name}
+2. Comma sepperated list of primary key column names
+
+If a primary key constraint clause is not supported in a create table statement
+this element should be empty. The most common form of a primary key constraint
+follows:
+
+CONSTRAINT ?1 PRIMARY KEY (?2)
+-->
+<!ELEMENT pk-constraint-template (#PCDATA)>
+
+<!--
+This is the template used to create a foreign key constraint in sepperate
+statement. The arguments supplied are as follows:
+
+1. Table name
+2. Foreign key constraint name; which is always fk_{table-name}_{cmr-field-name}
+3. Comma sepperated list of foreign key column names
+4. References table name
+5. Comma sepperated list of the referenced primary key column names
+
+If the datasource does not support foreign key constraints this element should
+be empty. The most common form of a foreign key constraint follows:
+
+ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)
+-->
+<!ELEMENT fk-constraint-template (#PCDATA)>
+
+<!--
+This element is used to define auto-increment template for a column
+-->
+<!ELEMENT auto-increment-template (#PCDATA)>
+
+<!--
+Template to add a column to the database.
+Arguments are as follows :
+
+1. Table name
+2. Column new
+3. Column type
+
+Default value is
+
+ALTER TABLE ?1 ADD ?2 ?3
+-->
+<!ELEMENT add-column-template (#PCDATA)>
+
+<!--
+Template to alter a column to the database.
+Arguments are as follows :
+
+1. Table name
+2. Column new
+3. Column type
+
+Default value is
+
+ALTER TABLE ?1 ALTER ?2 TYPE ?3
+-->
+<!ELEMENT alter-column-template (#PCDATA)>
+
+<!--
+Template to drop a column to the database.
+Arguments are as follows :
+
+1. Table name
+2. Column new
+
+Default value is
+
+ALTER TABLE ?1 DROP ?2
+-->
+<!ELEMENT drop-column-template (#PCDATA)>
+
+<!--
+An alias header is prepended to a generated table alias by the EJB-QL compiler
+to prevent name collisions. An alias header is constructed as folows:
+
+alias-header-prefix + int_counter + alias-header-suffix
+-->
+<!ELEMENT alias-header-prefix (#PCDATA)>
+<!ELEMENT alias-header-suffix (#PCDATA)>
+<!ELEMENT alias-max-length (#PCDATA)>
+
+<!--
+Does this type-mapping support subqueries. Some EJB-QL opperators are mapped
+to exists subqueries. If subquery is false the EJB-QL compiler will use a
+left join and is null.
+
+The subquery-supported element must be one of the two following:
+ <create-table>true</create-table>
+ <create-table>false</create-table>
+-->
+<!ELEMENT subquery-supported (#PCDATA)>
+
+<!--
+The true and false mappings are the mappings for true and false in EJB-QL
+queries.
+-->
+<!ELEMENT true-mapping (#PCDATA)>
+<!ELEMENT false-mapping (#PCDATA)>
+
+<!--
+The maximum number of key pairs that can appear in a single DELETE statement for relation table
+-->
+<!ELEMENT max-keys-in-delete (#PCDATA)>
+
+<!--
+Specifies the mapping from a java type to a jdbc and a sql type.
+-->
+<!ELEMENT mapping (java-type, jdbc-type, sql-type, param-setter?, result-reader?)>
+
+<!--
+Specifies the java class type to be mapped.
+-->
+<!ELEMENT java-type (#PCDATA)>
+
+<!--
+Fully qualified name of the JDBCParameterSetter implementation.
+-->
+<!ELEMENT param-setter (#PCDATA)>
+
+<!--
+Fully qualified name of the JDBCResultSetReader implementation.
+-->
+<!ELEMENT result-reader (#PCDATA)>
+
+<!--
+Specifies the mapping from an EJB-QL function to a sql function.
+-->
+<!ELEMENT function-mapping (function-name, function-sql)>
+
+<!--
+The name of the function to be mapped.
+-->
+<!ELEMENT function-name (#PCDATA)>
+
+<!--
+The sql to which the function is mapped. The sql can contain
+parameters specified with a question mark followed by the base one
+parameter number. For example, function mapping for concat in Oracle
+follows:
+
+<function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+</function-mapping>
+-->
+<!ELEMENT function-sql (#PCDATA)>
+
+<!--
+Unknown primary key configuration
+-->
+<!ELEMENT unknown-pk (key-generator-factory?, unknown-pk-class, field-name?,
+ read-only?, read-time-out?,
+ column-name?, (jdbc-type, sql-type)?, auto-increment? )>
+
+<!--
+The unknown primary key class.
+-->
+<!ELEMENT unknown-pk-class (#PCDATA)>
+
+<!--
+If present the field will auto-incremented by the database
+-->
+<!ELEMENT auto-increment EMPTY>
+
+<!--
+This element declares available for entity commands
+-->
+<!ELEMENT entity-commands (entity-command*)>
+
+<!--
+This element represents an entity command
+-->
+<!ELEMENT entity-command (attribute*)>
+
+<!--
+This attribute specifies the command name
+-->
+<!ATTLIST entity-command name CDATA #REQUIRED>
+
+<!--
+This attribute specifies the command class
+-->
+<!ATTLIST entity-command class CDATA #IMPLIED>
+
+<!--
+The attribute for create-method.
+-->
+<!ELEMENT attribute (#PCDATA)>
+
+<!--
+The name of the attribute
+-->
+<!ATTLIST attribute name CDATA #REQUIRED>
+
+<!--
+Optimistic locking configuration
+-->
+<!ELEMENT optimistic-locking (
+ group-name |
+ modified-strategy |
+ read-strategy |
+ ((version-column | timestamp-column | (key-generator-factory, field-type)),
+ field-name?, column-name?, (jdbc-type, sql-type)?)
+)>
+
+<!--
+Optimistic locking field group name.
+This name must match one of the entity's load-group-name.
+The fields in this group will be used for optimistic locking.
+-->
+<!ELEMENT group-name (#PCDATA)>
+
+<!--
+Optimistic locking modified strategy.
+This means the fields that were modified during transaction
+will be used for optimistic locking
+-->
+<!ELEMENT modified-strategy EMPTY>
+
+<!--
+Optimistic locking read strategy.
+This strategy implies that the fields that were read/changed
+in the transaction will be used for optimistic locking
+-->
+<!ELEMENT read-strategy EMPTY>
+
+<!--
+Optimistic locking version column strategy.
+Setting this element will add to entity bean additional version field
+of type java.lang.Long that will be used for optimistic locking.
+Each update of the entity will increase the value of this field.
+-->
+<!ELEMENT version-column EMPTY>
+
+<!--
+Optimistic locking timestamp column strategy.
+Setting this element will add to entity bean additional field of type
+java.util.Date that will be used for optimistic locking.
+Each update of the entity will set the value of this field to the current
+time.
+-->
+<!ELEMENT timestamp-column EMPTY>
+
+<!--
+Optimistic locking field type.
+The type for locking field in optimistic locking.
+-->
+<!ELEMENT field-type (#PCDATA)>
+
+<!--
+Key generator factory JNDI name.
+This element specifies the JNDI name of key generator factory that is
+used to obtain key generator for locking column used in optimistic locking.
+-->
+<!ELEMENT key-generator-factory (#PCDATA)>
+
+<!--
+Audit fields, choose the audit fields
+The created by and updated by require a caller principal
+The fields can also be cmp fields, use the same field-name
+-->
+<!ELEMENT audit (created-by?, created-time?, updated-by?, updated-time?)>
+
+<!--
+Created by principal, default is audit_created_by
+-->
+<!ELEMENT created-by (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+Created time, default is audit_created_time
+-->
+<!ELEMENT created-time (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+Updated by principal, default is audit_updated_by
+-->
+<!ELEMENT updated-by (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+Updated time, default is audit_updated_time
+-->
+<!ELEMENT updated-time (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+ Container for user-type-mapping elements
+-->
+<!ELEMENT user-type-mappings (user-type-mapping+)>
+
+<!--
+ Defines a mapping of a user type to a column providing a mapper class.
+ Mapper is like a mediator: when storing, it takes an instance of the user
+ type and translates it to a column value; when loading, it takes a column
+ value and translates it to an instance of the user type.
+-->
+<!ELEMENT user-type-mapping (java-type, mapped-type, mapper, check-dirty-after-get?, state-factory?)>
+
+<!--
+ The type a java-type in user-type-mapping is mapped to.
+-->
+<!ELEMENT mapped-type (#PCDATA)>
+
+<!--
+ Mapper class for user-type-mapping.
+-->
+<!ELEMENT mapper (#PCDATA)>
+
+<!--
+ Provide reserved words that should be escaped when generating tables
+-->
+<!ELEMENT reserved-words (word+)>
+<!ELEMENT word (#PCDATA)>
+
+<!--
+Is relevant only for multi-object queries. Allowed values are true and false.
+If true, ResultSet will be read on demand, i.e. when user iterates through the collection.
+If false, user is given completely initialized result, i.e. when user got the result
+ResultSet is read till the end and closed.
+-->
+<!ELEMENT lazy-resultset-loading (#PCDATA)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_4_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_4_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_4_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,960 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+This is the XML DTD for the jbosscmp-jdbc deployment descriptor.
+ <!DOCTYPE jbosscmp-jdbc PUBLIC
+ "-//JBoss//DTD JBOSSCMP-JDBC 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_4_0.dtd">
+-->
+
+<!--
+The root element of JBossCMP-JDBC configuration files.
+-->
+<!ELEMENT jbosscmp-jdbc (defaults?, enterprise-beans?, relationships?,
+ dependent-value-classes?, type-mappings?, entity-commands?,
+ user-type-mappings? , reserved-words?)>
+
+<!--
+The optional defaults elements contains the default values for
+entities, and relationships.
+-->
+<!ELEMENT defaults (datasource?, datasource-mapping?, create-table?,
+ alter-table?, remove-table?, post-table-create?, read-only?, read-time-out?,
+ row-locking?, pk-constraint?, fk-constraint?,
+ preferred-relation-mapping?, read-ahead?, list-cache-max?, clean-read-ahead-on-load?,
+ fetch-size?, unknown-pk?, entity-command?, ql-compiler?, throw-runtime-exceptions?)>
+
+<!--
+The optional datasource element contains the jndi-name used to lookup
+the datasource. All database connections used by an entity or relation table are obtained from the datasource.
+-->
+<!ELEMENT datasource (#PCDATA)>
+
+
+<!--
+The optional datasource-mapping element contains the name of the type mapping
+that will be used for this datasource.
+-->
+<!ELEMENT datasource-mapping (#PCDATA)>
+
+
+<!--
+Should the persistence manager attempt to create tables if they are
+not present?
+
+The create-table element must be one of the two following:
+ <create-table>true</create-table>
+ <create-table>false</create-table>
+-->
+<!ELEMENT create-table (#PCDATA)>
+
+
+<!--
+Should the persistence manager attempt to remove tables during shutdown?
+
+The remove-table element must be one of the two following:
+ <remove-table>true</remove-table>
+ <remove-table>false</remove-table>
+-->
+<!ELEMENT remove-table (#PCDATA)>
+
+<!--
+Should the persistence manager attempt to update the table structure at deployment
+
+The remove-table element must be one of the two following:
+ <alter-table>true</alter-table>
+ <alter-table>false</alter-table>
+-->
+<!ELEMENT alter-table (#PCDATA)>
+
+
+<!--
+Execute arbitrary SQL code directly after the database table is created.
+This command is only executed if create-table is true and the table
+did not previously exist.
+-->
+<!ELEMENT post-table-create (sql-statement+)>
+
+<!--
+The SQL Statement to be executed. Note that this is not translated
+into database specific SQL, but passed literally to the database.
+-->
+<!ELEMENT sql-statement (#PCDATA)>
+
+<!--
+Is the entity or cmp-field read-only?
+
+The read-only element must be one of the two following:
+ <read-only>true</read-only>
+ <read-only>false</read-only>
+-->
+<!ELEMENT read-only (#PCDATA)>
+
+
+<!--
+Specifies the ammount of time that a read-only field is considered
+valid (milliseconds).
+-->
+<!ELEMENT read-time-out (#PCDATA)>
+
+
+<!--
+Should select statements the SELECT ... FOR UPDATE syntax?
+
+The row-locking element must be one of the two following:
+ <row-locking>true</row-locking>
+ <row-locking>false</row-locking>
+-->
+<!ELEMENT row-locking (#PCDATA)>
+
+
+<!--
+Should a foreign key constraint be added for this relationship role?
+
+The fk-constraint element must be one of the two following:
+ <fk-constraint>true</fk-constraint>
+ <fk-constraint>false</fk-constraint>
+-->
+<!ELEMENT fk-constraint (#PCDATA)>
+
+
+<!--
+Should a primary key constraint be added when creating tables?
+
+The pk-constraint element must be one of the two following:
+ <pk-constraint>true</pk-constraint>
+ <pk-constraint>false</pk-constraint>
+-->
+<!ELEMENT pk-constraint (#PCDATA)>
+
+
+<!--
+Specifies the preferred mapping style for relationships.
+
+The preferred-relation-mapping element must be one of the two following:
+ <preferred-relation-mapping>foreign-key</preferred-relation-mapping>
+ <preferred-relation-mapping>relation-table</preferred-relation-mapping>
+-->
+<!ELEMENT preferred-relation-mapping (#PCDATA)>
+
+<!--
+Specifies the read ahead strategy.
+
+ <read-ahead>
+ <strategy>on-load</strategy>
+ <page-size>255</page-size>
+ <eager-load-group>*</eager-load-group>
+ </read-ahead>
+-->
+<!ELEMENT read-ahead (strategy, page-size?, eager-load-group?, left-join*)>
+
+<!--
+Specifies the strategy used to read-ahead data in queries.
+
+The strategy element must be one of the two following:
+ <strategy>none</strategy>
+ <strategy>on-load</strategy>
+ <strategy>on-find</strategy>
+-->
+<!ELEMENT strategy (#PCDATA)>
+
+
+<!--
+Specifies the number of entities that will be read in a single
+read-ahead load query.
+-->
+<!ELEMENT page-size (#PCDATA)>
+
+
+<!--
+Specifies a related entity that will be fetched on-find with LEFT JOIN.
+
+ <read-ahead>
+ <strategy>on-find</strategy>
+ <eager-load-group>report</eager-load-group>
+ <left-join cmr-field="lineItems"/>
+ <left-join cmr-field="product" eager-load-group="short"/>
+ </left-join>
+ <left-join cmr-field="customer" eager-load-group="basic"/>
+ </read-ahead>
+-->
+<!ELEMENT left-join (left-join*)>
+
+<!--
+The CMR field name to LEFT JOIN.
+-->
+<!ATTLIST left-join cmr-field CDATA #REQUIRED>
+
+<!--
+The eager load group of the related entity.
+-->
+<!ATTLIST left-join eager-load-group CDATA #IMPLIED>
+
+
+<!--
+Specifies whether the read-ahead cache should be cleaned after the instance was loaded.
+Allowed values are true and false.
+Since 3.2.5RC1. Previously, read-ahead cache was cleaned after loading.
+-->
+<!ELEMENT clean-read-ahead-on-load (#PCDATA)>
+
+
+<!--
+Specifies the number of simultaneous queries that can be tracked by
+the cache for an entity.
+-->
+<!ELEMENT list-cache-max (#PCDATA)>
+
+
+<!--
+Specifies the number of entities to read in one round-trip to
+the underlying datastore.
+-->
+<!ELEMENT fetch-size (#PCDATA)>
+
+
+<!--
+Should runtime exceptions be thrown when unexpected exception occurs ?
+
+The throw-runtime-exceptions element must be one of the two following:
+ <throw-runtime-exceptions>true</throw-runtime-exceptions>
+ <throw-runtime-exceptions>false</throw-runtime-exceptions>
+-->
+<!ELEMENT throw-runtime-exceptions (#PCDATA)>
+
+
+<!--
+The enterprise-beans element contains the entity elements that will
+be configured.
+-->
+<!ELEMENT enterprise-beans (entity+)>
+
+
+<!--
+The entity element contains the configuration of an entity
+-->
+<!ELEMENT entity (ejb-name, datasource?, datasource-mapping?, create-table?,
+ remove-table?, post-table-create?, read-only?, read-time-out?,
+ row-locking?, pk-constraint?, read-ahead?, list-cache-max?, clean-read-ahead-on-load?,
+ fetch-size?, table-name?, cmp-field*, load-groups?, eager-load-group?,
+ lazy-load-groups?, query*, unknown-pk?, entity-command?,
+ optimistic-locking?, audit?)>
+
+<!--
+Name of the entity being configured. This must match an entity declared
+in the ejb-jar.xml file.
+-->
+<!ELEMENT ejb-name (#PCDATA)>
+
+
+<!--
+This is the name of the table that will hold data for this entity.
+Each entity instance will be stored in one row of this table.
+-->
+<!ELEMENT table-name (#PCDATA)>
+
+
+<!--
+The cmp-field element contains the configuration of a cmp-field.
+-->
+<!ELEMENT cmp-field (field-name, read-only?, read-time-out?,
+ column-name?, not-null?, ((jdbc-type, sql-type) | (property+))?,
+ auto-increment?, dbindex?, check-dirty-after-get?, state-factory? )>
+
+
+<!--
+Name of the cmp-field being configured. This must match a cmp-field
+declared for this entity in the ejb-jar.xml file.
+-->
+<!ELEMENT field-name (#PCDATA)>
+
+
+<!--
+The name of the column that will hold the data for this field.
+-->
+<!ELEMENT column-name (#PCDATA)>
+
+
+<!--
+If present the field will not allow a field value.
+-->
+<!ELEMENT not-null EMPTY>
+
+<!--
+If present, the server will try to create an index on the column
+in the database called <fieldname>_index
+-->
+<!ELEMENT dbindex EMPTY>
+
+
+<!--
+This is the JDBC type that is used when setting parameters in a JDBC
+PreparedStatement or loading data from a JDBC ResultSet for this
+cmp-field. The valid types are defined in java.sql.Types.
+-->
+<!ELEMENT jdbc-type (#PCDATA)>
+
+
+<!--
+This is the SQL type that is used in create table statements for
+this field. Valid sql-types are only limited by your database vendor.
+-->
+<!ELEMENT sql-type (#PCDATA)>
+
+
+<!--
+The property element contains the configuration of a dependent
+value class property of a cmp-field that is the type of a dependent
+value class.
+-->
+<!ELEMENT property (property-name, column-name?, not-null?,
+ (jdbc-type, sql-type)?)>
+
+
+<!--
+Name of the property being configured. In a dependent-value-class
+element this must match a JavaBean property of the class. In a
+cmp-field element this must match a flattened propety of the
+dependent-value-class field type.
+-->
+<!ELEMENT property-name (#PCDATA)>
+
+
+<!--
+Can be true or false.
+If true, the field will be checked for dirty state at synchronization time.
+By default, all fields except for the fields of primitive and their wrapper types
+are checked for dirty state after get.
+-->
+<!ELEMENT check-dirty-after-get (#PCDATA)>
+
+<!--
+Fully qualified class name of the implementation of
+ org.jboss.ejb.plugins.cmp.jdbc.CMPFieldStateFactory.
+-->
+<!ELEMENT state-factory (#PCDATA)>
+
+<!--
+Contains the named load groups.
+-->
+<!ELEMENT load-groups (load-group+)>
+
+
+<!--
+A named group of fields that will be loaded together.
+-->
+<!ELEMENT load-group (description?, load-group-name, field-name+)>
+
+<!--
+Contains the name of a load group.
+-->
+<!ELEMENT load-group-name (#PCDATA)>
+
+
+<!--
+Contains the name of the load group that will eager loaded for this entity.
+-->
+<!ELEMENT eager-load-group (#PCDATA)>
+
+
+<!--
+Contains the names of the groups that will be lazy loaded together.
+-->
+<!ELEMENT lazy-load-groups (load-group-name+)>
+
+
+<!--
+Descriptive text.
+-->
+<!ELEMENT description (#PCDATA)>
+
+
+<!--
+The query element contains the configuration of a query.
+-->
+<!ELEMENT query (description?, query-method,
+ (jboss-ql | dynamic-ql | declared-sql)?, read-ahead?, ql-compiler?, lazy-resultset-loading?)>
+
+
+<!--
+The query method that being configured. This must match a
+query-method declared for this entity in the ejb-jar.xml file.
+-->
+<!ELEMENT query-method (method-name, method-params)>
+
+
+<!--
+The name of the query method that is being configured.
+-->
+<!ELEMENT method-name (#PCDATA)>
+
+
+<!--
+The method-parameters contains the parameters of the method that is
+being configured. Method parameters must be in the same order as the
+method and have the same type.
+-->
+<!ELEMENT method-params (method-param*)>
+
+
+<!--
+The java class of one parameter for a query.
+
+An example follows:
+ <method-param>java.lang.String</method-param>
+-->
+<!ELEMENT method-param (#PCDATA)>
+
+
+<!--
+JBossQL query. JBossQL is a superset of EJB-QL.
+-->
+<!ELEMENT jboss-ql (#PCDATA)>
+
+
+<!--
+Dynamic JBossQL query. The JBossQL is passed to the query and compiled
+on the fly.
+-->
+<!ELEMENT dynamic-ql EMPTY>
+
+
+<!--
+Explicitly declared sql fragments.
+-->
+<!ELEMENT declared-sql (select?, from?, where?, order?, other?)>
+
+
+<!--
+Delcares what is to be selected. A finder may only have the distinct element.
+-->
+<!ELEMENT select (distinct?, (ejb-name, field-name?)?, alias?, additional-columns?)>
+
+
+<!--
+Delared additional SQl to append to the generated from clause.
+
+Example: <from>, FullAddressEJB as a</from>
+-->
+<!ELEMENT from (#PCDATA)>
+
+<!--
+If the empty distinct element is present, the SELECT DISTINCT
+syntax will be used. This syntax is used by default for ejbSelect
+methods that return a java.util.Set.
+-->
+<!ELEMENT distinct EMPTY>
+
+
+<!--
+Declares the where clause for the query.
+
+Example: <where>TITLE={0} OR ARTIST={0} OR TYPE={0} OR NOTES={0}</where>
+-->
+<!ELEMENT where (#PCDATA)>
+
+
+<!--
+Declares the order clause for the query.
+
+Example: <order>TITLE</order>
+-->
+<!ELEMENT order (#PCDATA)>
+
+
+<!--
+Declares the other sql that is appended to the end of a query.
+
+Example: <other>LIMIT 100 OFFSET 200</other>
+-->
+<!ELEMENT other (#PCDATA)>
+
+<!--
+Declare the alias to use for the main select table.
+
+Example: <alias>my_table</alias>
+-->
+<!ELEMENT alias (#PCDATA)>
+
+
+<!--
+Declares other columns to be selected to satisfy ordering
+by arbitrary columns with ejbFinders or to facilitate aggregate
+functions in ejbSelects.
+
+Example: <additional-columns>, join-table1.column1,
+ join-table2.column2</additional-columns>
+-->
+<!ELEMENT additional-columns (#PCDATA)>
+
+
+<!--
+Fully qualified name of QL compiler implementation class.
+-->
+<!ELEMENT ql-compiler (#PCDATA)>
+
+
+<!--
+The relationships element contains the ejb-relation elements that will
+be configured.
+-->
+<!ELEMENT relationships (ejb-relation+)>
+
+
+<!--
+The ejb-relation element contains the configuration of an
+ejb-relation.
+-->
+<!ELEMENT ejb-relation (ejb-relation-name, read-only?, read-time-out?,
+ (foreign-key-mapping | relation-table-mapping)?,
+ (ejb-relationship-role, ejb-relationship-role)?)>
+
+
+<!--
+Name of the ejb-relation being configured. This must match an
+ejb-relation declared in the ejb-jar.xml file.
+-->
+<!ELEMENT ejb-relation-name (#PCDATA)>
+
+
+<!--
+Specifies that the ejb-relation should be mapped with foreign-keys.
+This mapping is not available for many-to-many relationships.
+-->
+<!ELEMENT foreign-key-mapping EMPTY>
+
+
+<!--
+Specifies that the ejb-relation should be mapped with a relation-table.
+-->
+<!ELEMENT relation-table-mapping (table-name?,
+ (datasource, datasource-mapping)?, create-table?, remove-table?,
+ post-table-create?,
+ row-locking?, pk-constraint?)>
+
+
+<!--
+The ejb-rejationship-role element contains the configuration of an
+ejb-relationship-role.
+-->
+<!ELEMENT ejb-relationship-role (ejb-relationship-role-name,
+ fk-constraint?, key-fields?, read-ahead?, batch-cascade-delete?)>
+
+<!--
+The batch-cascade-delete element specifies that, this side of the relationship
+should be batch deleted with one SQL statement of the form
+DELETE FROM <related-table> WHERE <foreign-key> = ?
+The presense of cascade-delete element in ejb-jar.xml for the matching
+ejb-relationship-role is mandatory.
+-->
+<!ELEMENT batch-cascade-delete EMPTY>
+
+
+<!--
+Name of the ejb-relationship-role being configured. This must match
+an ejb-relationship-role declared for this ejb-relation in the
+ejb-jar.xml file.
+-->
+<!ELEMENT ejb-relationship-role-name (#PCDATA)>
+
+
+<!--
+Contains the key fields. The interperation of the key fields depends
+on the mapping style of the relationship.
+-->
+<!ELEMENT key-fields (key-field*)>
+
+<!--
+The key-field element declared the configuration of a key field.
+The field-name element must match the field-name of one of the
+primary key fields of the this entity.
+-->
+<!ELEMENT key-field (field-name,
+ ((column-name, (jdbc-type, sql-type)?) | (property*)),
+ dbindex?)>
+
+
+<!--
+Contains the known dependent value classes.
+-->
+<!ELEMENT dependent-value-classes (dependent-value-class*)>
+
+
+<!--
+The dependent-value-class element contains the configuration of a
+dependent value class.
+-->
+<!ELEMENT dependent-value-class (description?, class, property+)>
+
+
+<!--
+Name of the java class to which the dependent value class configuration
+applies.
+-->
+<!ELEMENT class (#PCDATA)>
+
+
+<!--
+The type-mappings element contains the java to sql mappings.
+-->
+<!ELEMENT type-mappings (type-mapping+)>
+
+<!--
+The type-mapping element contains a named java to sql mapping.
+This includes both type mapping and function mapping.
+-->
+<!ELEMENT type-mapping (name, row-locking-template, pk-constraint-template,
+ fk-constraint-template, auto-increment-template?,
+ add-column-template?, alter-column-template?, drop-column-template?,
+ alias-header-prefix,
+ alias-header-suffix, alias-max-length, subquery-supported,
+ true-mapping, false-mapping, max-keys-in-delete?,
+ function-mapping*, mapping+)>
+
+<!--
+Name of the type-mapping.
+-->
+<!ELEMENT name (#PCDATA)>
+
+<!--
+This is the template used to create a row lock on the selected rows. The
+arguments supplied are as follows:
+
+1. Select clause
+2. From clasue; the order of the tables is currently not guarenteed
+3. Where clause
+
+If row locking is not supported in select statement this element should be
+empty. The most common form of row locking is select for update as in the
+example that follows:
+
+SELECT ?1 FROM ?2 WHERE ?3 FOR UPDATE
+-->
+<!ELEMENT row-locking-template (#PCDATA)>
+
+<!--
+This is the template used to create a primary key constraint in the create
+table statement. The arguments supplied are as follows:
+
+1. Primary key constraint name; which is always pk_{table-name}
+2. Comma sepperated list of primary key column names
+
+If a primary key constraint clause is not supported in a create table statement
+this element should be empty. The most common form of a primary key constraint
+follows:
+
+CONSTRAINT ?1 PRIMARY KEY (?2)
+-->
+<!ELEMENT pk-constraint-template (#PCDATA)>
+
+<!--
+This is the template used to create a foreign key constraint in sepperate
+statement. The arguments supplied are as follows:
+
+1. Table name
+2. Foreign key constraint name; which is always fk_{table-name}_{cmr-field-name}
+3. Comma sepperated list of foreign key column names
+4. References table name
+5. Comma sepperated list of the referenced primary key column names
+
+If the datasource does not support foreign key constraints this element should
+be empty. The most common form of a foreign key constraint follows:
+
+ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)
+-->
+<!ELEMENT fk-constraint-template (#PCDATA)>
+
+<!--
+This element is used to define auto-increment template for a column
+-->
+<!ELEMENT auto-increment-template (#PCDATA)>
+
+<!--
+Template to add a column to the database.
+Arguments are as follows :
+
+1. Table name
+2. Column new
+3. Column type
+
+Default value is
+
+ALTER TABLE ?1 ADD ?2 ?3
+-->
+<!ELEMENT add-column-template (#PCDATA)>
+
+<!--
+Template to alter a column to the database.
+Arguments are as follows :
+
+1. Table name
+2. Column new
+3. Column type
+
+Default value is
+
+ALTER TABLE ?1 ALTER ?2 TYPE ?3
+-->
+<!ELEMENT alter-column-template (#PCDATA)>
+
+<!--
+Template to drop a column to the database.
+Arguments are as follows :
+
+1. Table name
+2. Column new
+
+Default value is
+
+ALTER TABLE ?1 DROP ?2
+-->
+<!ELEMENT drop-column-template (#PCDATA)>
+
+<!--
+An alias header is prepended to a generated table alias by the EJB-QL compiler
+to prevent name collisions. An alias header is constructed as folows:
+
+alias-header-prefix + int_counter + alias-header-suffix
+-->
+<!ELEMENT alias-header-prefix (#PCDATA)>
+<!ELEMENT alias-header-suffix (#PCDATA)>
+<!ELEMENT alias-max-length (#PCDATA)>
+
+<!--
+Does this type-mapping support subqueries. Some EJB-QL opperators are mapped
+to exists subqueries. If subquery is false the EJB-QL compiler will use a
+left join and is null.
+
+The subquery-supported element must be one of the two following:
+ <create-table>true</create-table>
+ <create-table>false</create-table>
+-->
+<!ELEMENT subquery-supported (#PCDATA)>
+
+<!--
+The true and false mappings are the mappings for true and false in EJB-QL
+queries.
+-->
+<!ELEMENT true-mapping (#PCDATA)>
+<!ELEMENT false-mapping (#PCDATA)>
+
+<!--
+The maximum number of key pairs that can appear in a single DELETE statement for relation table
+-->
+<!ELEMENT max-keys-in-delete (#PCDATA)>
+
+<!--
+Specifies the mapping from a java type to a jdbc and a sql type.
+-->
+<!ELEMENT mapping (java-type, jdbc-type, sql-type, param-setter?, result-reader?)>
+
+<!--
+Specifies the java class type to be mapped.
+-->
+<!ELEMENT java-type (#PCDATA)>
+
+<!--
+Fully qualified name of the JDBCParameterSetter implementation.
+-->
+<!ELEMENT param-setter (#PCDATA)>
+
+<!--
+Fully qualified name of the JDBCResultSetReader implementation.
+-->
+<!ELEMENT result-reader (#PCDATA)>
+
+<!--
+Specifies the mapping from an EJB-QL function to a sql function.
+-->
+<!ELEMENT function-mapping (function-name, function-sql)>
+
+<!--
+The name of the function to be mapped.
+-->
+<!ELEMENT function-name (#PCDATA)>
+
+<!--
+The sql to which the function is mapped. The sql can contain
+parameters specified with a question mark followed by the base one
+parameter number. For example, function mapping for concat in Oracle
+follows:
+
+<function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+</function-mapping>
+-->
+<!ELEMENT function-sql (#PCDATA)>
+
+<!--
+Unknown primary key configuration
+-->
+<!ELEMENT unknown-pk (key-generator-factory?, unknown-pk-class, field-name?,
+ read-only?, read-time-out?,
+ column-name?, (jdbc-type, sql-type)?, auto-increment? )>
+
+<!--
+The unknown primary key class.
+-->
+<!ELEMENT unknown-pk-class (#PCDATA)>
+
+<!--
+If present the field will auto-incremented by the database
+-->
+<!ELEMENT auto-increment EMPTY>
+
+<!--
+This element declares available for entity commands
+-->
+<!ELEMENT entity-commands (entity-command*)>
+
+<!--
+This element represents an entity command
+-->
+<!ELEMENT entity-command (attribute*)>
+
+<!--
+This attribute specifies the command name
+-->
+<!ATTLIST entity-command name CDATA #REQUIRED>
+
+<!--
+This attribute specifies the command class
+-->
+<!ATTLIST entity-command class CDATA #IMPLIED>
+
+<!--
+The attribute for create-method.
+-->
+<!ELEMENT attribute (#PCDATA)>
+
+<!--
+The name of the attribute
+-->
+<!ATTLIST attribute name CDATA #REQUIRED>
+
+<!--
+Optimistic locking configuration
+-->
+<!ELEMENT optimistic-locking (
+ group-name |
+ modified-strategy |
+ read-strategy |
+ ((version-column | timestamp-column | (key-generator-factory, field-type)),
+ field-name?, column-name?, (jdbc-type, sql-type)?)
+)>
+
+<!--
+Optimistic locking field group name.
+This name must match one of the entity's load-group-name.
+The fields in this group will be used for optimistic locking.
+-->
+<!ELEMENT group-name (#PCDATA)>
+
+<!--
+Optimistic locking modified strategy.
+This means the fields that were modified during transaction
+will be used for optimistic locking
+-->
+<!ELEMENT modified-strategy EMPTY>
+
+<!--
+Optimistic locking read strategy.
+This strategy implies that the fields that were read/changed
+in the transaction will be used for optimistic locking
+-->
+<!ELEMENT read-strategy EMPTY>
+
+<!--
+Optimistic locking version column strategy.
+Setting this element will add to entity bean additional version field
+of type java.lang.Long that will be used for optimistic locking.
+Each update of the entity will increase the value of this field.
+-->
+<!ELEMENT version-column EMPTY>
+
+<!--
+Optimistic locking timestamp column strategy.
+Setting this element will add to entity bean additional field of type
+java.util.Date that will be used for optimistic locking.
+Each update of the entity will set the value of this field to the current
+time.
+-->
+<!ELEMENT timestamp-column EMPTY>
+
+<!--
+Optimistic locking field type.
+The type for locking field in optimistic locking.
+-->
+<!ELEMENT field-type (#PCDATA)>
+
+<!--
+Key generator factory JNDI name.
+This element specifies the JNDI name of key generator factory that is
+used to obtain key generator for locking column used in optimistic locking.
+-->
+<!ELEMENT key-generator-factory (#PCDATA)>
+
+<!--
+Audit fields, choose the audit fields
+The created by and updated by require a caller principal
+The fields can also be cmp fields, use the same field-name
+-->
+<!ELEMENT audit (created-by?, created-time?, updated-by?, updated-time?)>
+
+<!--
+Created by principal, default is audit_created_by
+-->
+<!ELEMENT created-by (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+Created time, default is audit_created_time
+-->
+<!ELEMENT created-time (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+Updated by principal, default is audit_updated_by
+-->
+<!ELEMENT updated-by (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+Updated time, default is audit_updated_time
+-->
+<!ELEMENT updated-time (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+ Container for user-type-mapping elements
+-->
+<!ELEMENT user-type-mappings (user-type-mapping+)>
+
+<!--
+ Defines a mapping of a user type to a column providing a mapper class.
+ Mapper is like a mediator: when storing, it takes an instance of the user
+ type and translates it to a column value; when loading, it takes a column
+ value and translates it to an instance of the user type.
+-->
+<!ELEMENT user-type-mapping (java-type, mapped-type, mapper, check-dirty-after-get?, state-factory?)>
+
+<!--
+ The type a java-type in user-type-mapping is mapped to.
+-->
+<!ELEMENT mapped-type (#PCDATA)>
+
+<!--
+ Mapper class for user-type-mapping.
+-->
+<!ELEMENT mapper (#PCDATA)>
+
+<!--
+ Provide reserved words that should be escaped when generating tables
+-->
+<!ELEMENT reserved-words (word+)>
+<!ELEMENT word (#PCDATA)>
+
+<!--
+Is relevant only for multi-object queries. Allowed values are true and false.
+If true, ResultSet will be read on demand, i.e. when user iterates through the collection.
+If false, user is given completely initialized result, i.e. when user got the result
+ResultSet is read till the end and closed.
+-->
+<!ELEMENT lazy-resultset-loading (#PCDATA)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_4_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_4_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/jbosscmp-jdbc_4_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,960 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--
+This is the XML DTD for the jbosscmp-jdbc deployment descriptor.
+ <!DOCTYPE jbosscmp-jdbc PUBLIC
+ "-//JBoss//DTD JBOSSCMP-JDBC 4.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_4_2.dtd">
+-->
+
+<!--
+The root element of JBossCMP-JDBC configuration files.
+-->
+<!ELEMENT jbosscmp-jdbc (defaults?, enterprise-beans?, relationships?,
+ dependent-value-classes?, type-mappings?, entity-commands?,
+ user-type-mappings? , reserved-words?)>
+
+<!--
+The optional defaults elements contains the default values for
+entities, and relationships.
+-->
+<!ELEMENT defaults (datasource?, datasource-mapping?, create-table?,
+ alter-table?, remove-table?, post-table-create?, read-only?, read-time-out?,
+ row-locking?, pk-constraint?, fk-constraint?,
+ preferred-relation-mapping?, read-ahead?, list-cache-max?, clean-read-ahead-on-load?,
+ fetch-size?, unknown-pk?, entity-command?, ql-compiler?, throw-runtime-exceptions?)>
+
+<!--
+The optional datasource element contains the jndi-name used to lookup
+the datasource. All database connections used by an entity or relation table are obtained from the datasource.
+-->
+<!ELEMENT datasource (#PCDATA)>
+
+
+<!--
+The optional datasource-mapping element contains the name of the type mapping
+that will be used for this datasource.
+-->
+<!ELEMENT datasource-mapping (#PCDATA)>
+
+
+<!--
+Should the persistence manager attempt to create tables if they are
+not present?
+
+The create-table element must be one of the two following:
+ <create-table>true</create-table>
+ <create-table>false</create-table>
+-->
+<!ELEMENT create-table (#PCDATA)>
+
+
+<!--
+Should the persistence manager attempt to remove tables during shutdown?
+
+The remove-table element must be one of the two following:
+ <remove-table>true</remove-table>
+ <remove-table>false</remove-table>
+-->
+<!ELEMENT remove-table (#PCDATA)>
+
+<!--
+Should the persistence manager attempt to update the table structure at deployment
+
+The remove-table element must be one of the two following:
+ <alter-table>true</alter-table>
+ <alter-table>false</alter-table>
+-->
+<!ELEMENT alter-table (#PCDATA)>
+
+
+<!--
+Execute arbitrary SQL code directly after the database table is created.
+This command is only executed if create-table is true and the table
+did not previously exist.
+-->
+<!ELEMENT post-table-create (sql-statement+)>
+
+<!--
+The SQL Statement to be executed. Note that this is not translated
+into database specific SQL, but passed literally to the database.
+-->
+<!ELEMENT sql-statement (#PCDATA)>
+
+<!--
+Is the entity or cmp-field read-only?
+
+The read-only element must be one of the two following:
+ <read-only>true</read-only>
+ <read-only>false</read-only>
+-->
+<!ELEMENT read-only (#PCDATA)>
+
+
+<!--
+Specifies the ammount of time that a read-only field is considered
+valid (milliseconds).
+-->
+<!ELEMENT read-time-out (#PCDATA)>
+
+
+<!--
+Should select statements the SELECT ... FOR UPDATE syntax?
+
+The row-locking element must be one of the two following:
+ <row-locking>true</row-locking>
+ <row-locking>false</row-locking>
+-->
+<!ELEMENT row-locking (#PCDATA)>
+
+
+<!--
+Should a foreign key constraint be added for this relationship role?
+
+The fk-constraint element must be one of the two following:
+ <fk-constraint>true</fk-constraint>
+ <fk-constraint>false</fk-constraint>
+-->
+<!ELEMENT fk-constraint (#PCDATA)>
+
+
+<!--
+Should a primary key constraint be added when creating tables?
+
+The pk-constraint element must be one of the two following:
+ <pk-constraint>true</pk-constraint>
+ <pk-constraint>false</pk-constraint>
+-->
+<!ELEMENT pk-constraint (#PCDATA)>
+
+
+<!--
+Specifies the preferred mapping style for relationships.
+
+The preferred-relation-mapping element must be one of the two following:
+ <preferred-relation-mapping>foreign-key</preferred-relation-mapping>
+ <preferred-relation-mapping>relation-table</preferred-relation-mapping>
+-->
+<!ELEMENT preferred-relation-mapping (#PCDATA)>
+
+<!--
+Specifies the read ahead strategy.
+
+ <read-ahead>
+ <strategy>on-load</strategy>
+ <page-size>255</page-size>
+ <eager-load-group>*</eager-load-group>
+ </read-ahead>
+-->
+<!ELEMENT read-ahead (strategy, page-size?, eager-load-group?, left-join*)>
+
+<!--
+Specifies the strategy used to read-ahead data in queries.
+
+The strategy element must be one of the two following:
+ <strategy>none</strategy>
+ <strategy>on-load</strategy>
+ <strategy>on-find</strategy>
+-->
+<!ELEMENT strategy (#PCDATA)>
+
+
+<!--
+Specifies the number of entities that will be read in a single
+read-ahead load query.
+-->
+<!ELEMENT page-size (#PCDATA)>
+
+
+<!--
+Specifies a related entity that will be fetched on-find with LEFT JOIN.
+
+ <read-ahead>
+ <strategy>on-find</strategy>
+ <eager-load-group>report</eager-load-group>
+ <left-join cmr-field="lineItems"/>
+ <left-join cmr-field="product" eager-load-group="short"/>
+ </left-join>
+ <left-join cmr-field="customer" eager-load-group="basic"/>
+ </read-ahead>
+-->
+<!ELEMENT left-join (left-join*)>
+
+<!--
+The CMR field name to LEFT JOIN.
+-->
+<!ATTLIST left-join cmr-field CDATA #REQUIRED>
+
+<!--
+The eager load group of the related entity.
+-->
+<!ATTLIST left-join eager-load-group CDATA #IMPLIED>
+
+
+<!--
+Specifies whether the read-ahead cache should be cleaned after the instance was loaded.
+Allowed values are true and false.
+Since 3.2.5RC1. Previously, read-ahead cache was cleaned after loading.
+-->
+<!ELEMENT clean-read-ahead-on-load (#PCDATA)>
+
+
+<!--
+Specifies the number of simultaneous queries that can be tracked by
+the cache for an entity.
+-->
+<!ELEMENT list-cache-max (#PCDATA)>
+
+
+<!--
+Specifies the number of entities to read in one round-trip to
+the underlying datastore.
+-->
+<!ELEMENT fetch-size (#PCDATA)>
+
+
+<!--
+Should runtime exceptions be thrown when unexpected exception occurs ?
+
+The throw-runtime-exceptions element must be one of the two following:
+ <throw-runtime-exceptions>true</throw-runtime-exceptions>
+ <throw-runtime-exceptions>false</throw-runtime-exceptions>
+-->
+<!ELEMENT throw-runtime-exceptions (#PCDATA)>
+
+
+<!--
+The enterprise-beans element contains the entity elements that will
+be configured.
+-->
+<!ELEMENT enterprise-beans (entity+)>
+
+
+<!--
+The entity element contains the configuration of an entity
+-->
+<!ELEMENT entity (ejb-name, datasource?, datasource-mapping?, create-table?,
+ remove-table?, post-table-create?, read-only?, read-time-out?,
+ row-locking?, pk-constraint?, read-ahead?, list-cache-max?, clean-read-ahead-on-load?,
+ fetch-size?, table-name?, cmp-field*, load-groups?, eager-load-group?,
+ lazy-load-groups?, query*, unknown-pk?, entity-command?,
+ optimistic-locking?, audit?)>
+
+<!--
+Name of the entity being configured. This must match an entity declared
+in the ejb-jar.xml file.
+-->
+<!ELEMENT ejb-name (#PCDATA)>
+
+
+<!--
+This is the name of the table that will hold data for this entity.
+Each entity instance will be stored in one row of this table.
+-->
+<!ELEMENT table-name (#PCDATA)>
+
+
+<!--
+The cmp-field element contains the configuration of a cmp-field.
+-->
+<!ELEMENT cmp-field (field-name, read-only?, read-time-out?,
+ column-name?, not-null?, ((jdbc-type, sql-type) | (property+))?,
+ auto-increment?, dbindex?, check-dirty-after-get?, state-factory? )>
+
+
+<!--
+Name of the cmp-field being configured. This must match a cmp-field
+declared for this entity in the ejb-jar.xml file.
+-->
+<!ELEMENT field-name (#PCDATA)>
+
+
+<!--
+The name of the column that will hold the data for this field.
+-->
+<!ELEMENT column-name (#PCDATA)>
+
+
+<!--
+If present the field will not allow a field value.
+-->
+<!ELEMENT not-null EMPTY>
+
+<!--
+If present, the server will try to create an index on the column
+in the database called <fieldname>_index
+-->
+<!ELEMENT dbindex EMPTY>
+
+
+<!--
+This is the JDBC type that is used when setting parameters in a JDBC
+PreparedStatement or loading data from a JDBC ResultSet for this
+cmp-field. The valid types are defined in java.sql.Types.
+-->
+<!ELEMENT jdbc-type (#PCDATA)>
+
+
+<!--
+This is the SQL type that is used in create table statements for
+this field. Valid sql-types are only limited by your database vendor.
+-->
+<!ELEMENT sql-type (#PCDATA)>
+
+
+<!--
+The property element contains the configuration of a dependent
+value class property of a cmp-field that is the type of a dependent
+value class.
+-->
+<!ELEMENT property (property-name, column-name?, not-null?,
+ (jdbc-type, sql-type)?)>
+
+
+<!--
+Name of the property being configured. In a dependent-value-class
+element this must match a JavaBean property of the class. In a
+cmp-field element this must match a flattened propety of the
+dependent-value-class field type.
+-->
+<!ELEMENT property-name (#PCDATA)>
+
+
+<!--
+Can be true or false.
+If true, the field will be checked for dirty state at synchronization time.
+By default, all fields except for the fields of primitive and their wrapper types
+are checked for dirty state after get.
+-->
+<!ELEMENT check-dirty-after-get (#PCDATA)>
+
+<!--
+Fully qualified class name of the implementation of
+ org.jboss.ejb.plugins.cmp.jdbc.CMPFieldStateFactory.
+-->
+<!ELEMENT state-factory (#PCDATA)>
+
+<!--
+Contains the named load groups.
+-->
+<!ELEMENT load-groups (load-group+)>
+
+
+<!--
+A named group of fields that will be loaded together.
+-->
+<!ELEMENT load-group (description?, load-group-name, field-name+)>
+
+<!--
+Contains the name of a load group.
+-->
+<!ELEMENT load-group-name (#PCDATA)>
+
+
+<!--
+Contains the name of the load group that will eager loaded for this entity.
+-->
+<!ELEMENT eager-load-group (#PCDATA)>
+
+
+<!--
+Contains the names of the groups that will be lazy loaded together.
+-->
+<!ELEMENT lazy-load-groups (load-group-name+)>
+
+
+<!--
+Descriptive text.
+-->
+<!ELEMENT description (#PCDATA)>
+
+
+<!--
+The query element contains the configuration of a query.
+-->
+<!ELEMENT query (description?, query-method,
+ (jboss-ql | dynamic-ql | declared-sql)?, read-ahead?, ql-compiler?, lazy-resultset-loading?)>
+
+
+<!--
+The query method that being configured. This must match a
+query-method declared for this entity in the ejb-jar.xml file.
+-->
+<!ELEMENT query-method (method-name, method-params)>
+
+
+<!--
+The name of the query method that is being configured.
+-->
+<!ELEMENT method-name (#PCDATA)>
+
+
+<!--
+The method-parameters contains the parameters of the method that is
+being configured. Method parameters must be in the same order as the
+method and have the same type.
+-->
+<!ELEMENT method-params (method-param*)>
+
+
+<!--
+The java class of one parameter for a query.
+
+An example follows:
+ <method-param>java.lang.String</method-param>
+-->
+<!ELEMENT method-param (#PCDATA)>
+
+
+<!--
+JBossQL query. JBossQL is a superset of EJB-QL.
+-->
+<!ELEMENT jboss-ql (#PCDATA)>
+
+
+<!--
+Dynamic JBossQL query. The JBossQL is passed to the query and compiled
+on the fly.
+-->
+<!ELEMENT dynamic-ql EMPTY>
+
+
+<!--
+Explicitly declared sql fragments.
+-->
+<!ELEMENT declared-sql (select?, from?, where?, order?, other?)>
+
+
+<!--
+Delcares what is to be selected. A finder may only have the distinct element.
+-->
+<!ELEMENT select (distinct?, (ejb-name, field-name?)?, alias?, additional-columns?)>
+
+
+<!--
+Delared additional SQl to append to the generated from clause.
+
+Example: <from>, FullAddressEJB as a</from>
+-->
+<!ELEMENT from (#PCDATA)>
+
+<!--
+If the empty distinct element is present, the SELECT DISTINCT
+syntax will be used. This syntax is used by default for ejbSelect
+methods that return a java.util.Set.
+-->
+<!ELEMENT distinct EMPTY>
+
+
+<!--
+Declares the where clause for the query.
+
+Example: <where>TITLE={0} OR ARTIST={0} OR TYPE={0} OR NOTES={0}</where>
+-->
+<!ELEMENT where (#PCDATA)>
+
+
+<!--
+Declares the order clause for the query.
+
+Example: <order>TITLE</order>
+-->
+<!ELEMENT order (#PCDATA)>
+
+
+<!--
+Declares the other sql that is appended to the end of a query.
+
+Example: <other>LIMIT 100 OFFSET 200</other>
+-->
+<!ELEMENT other (#PCDATA)>
+
+<!--
+Declare the alias to use for the main select table.
+
+Example: <alias>my_table</alias>
+-->
+<!ELEMENT alias (#PCDATA)>
+
+
+<!--
+Declares other columns to be selected to satisfy ordering
+by arbitrary columns with ejbFinders or to facilitate aggregate
+functions in ejbSelects.
+
+Example: <additional-columns>, join-table1.column1,
+ join-table2.column2</additional-columns>
+-->
+<!ELEMENT additional-columns (#PCDATA)>
+
+
+<!--
+Fully qualified name of QL compiler implementation class.
+-->
+<!ELEMENT ql-compiler (#PCDATA)>
+
+
+<!--
+The relationships element contains the ejb-relation elements that will
+be configured.
+-->
+<!ELEMENT relationships (ejb-relation+)>
+
+
+<!--
+The ejb-relation element contains the configuration of an
+ejb-relation.
+-->
+<!ELEMENT ejb-relation (ejb-relation-name, read-only?, read-time-out?,
+ (foreign-key-mapping | relation-table-mapping)?,
+ (ejb-relationship-role, ejb-relationship-role)?)>
+
+
+<!--
+Name of the ejb-relation being configured. This must match an
+ejb-relation declared in the ejb-jar.xml file.
+-->
+<!ELEMENT ejb-relation-name (#PCDATA)>
+
+
+<!--
+Specifies that the ejb-relation should be mapped with foreign-keys.
+This mapping is not available for many-to-many relationships.
+-->
+<!ELEMENT foreign-key-mapping EMPTY>
+
+
+<!--
+Specifies that the ejb-relation should be mapped with a relation-table.
+-->
+<!ELEMENT relation-table-mapping (table-name?,
+ (datasource, datasource-mapping)?, create-table?, remove-table?,
+ post-table-create?,
+ row-locking?, pk-constraint?)>
+
+
+<!--
+The ejb-rejationship-role element contains the configuration of an
+ejb-relationship-role.
+-->
+<!ELEMENT ejb-relationship-role (ejb-relationship-role-name,
+ fk-constraint?, key-fields?, read-ahead?, batch-cascade-delete?)>
+
+<!--
+The batch-cascade-delete element specifies that, this side of the relationship
+should be batch deleted with one SQL statement of the form
+DELETE FROM <related-table> WHERE <foreign-key> = ?
+The presense of cascade-delete element in ejb-jar.xml for the matching
+ejb-relationship-role is mandatory.
+-->
+<!ELEMENT batch-cascade-delete EMPTY>
+
+
+<!--
+Name of the ejb-relationship-role being configured. This must match
+an ejb-relationship-role declared for this ejb-relation in the
+ejb-jar.xml file.
+-->
+<!ELEMENT ejb-relationship-role-name (#PCDATA)>
+
+
+<!--
+Contains the key fields. The interperation of the key fields depends
+on the mapping style of the relationship.
+-->
+<!ELEMENT key-fields (key-field*)>
+
+<!--
+The key-field element declared the configuration of a key field.
+The field-name element must match the field-name of one of the
+primary key fields of the this entity.
+-->
+<!ELEMENT key-field (field-name,
+ ((column-name, (jdbc-type, sql-type)?) | (property*)),
+ dbindex?)>
+
+
+<!--
+Contains the known dependent value classes.
+-->
+<!ELEMENT dependent-value-classes (dependent-value-class*)>
+
+
+<!--
+The dependent-value-class element contains the configuration of a
+dependent value class.
+-->
+<!ELEMENT dependent-value-class (description?, class, property+)>
+
+
+<!--
+Name of the java class to which the dependent value class configuration
+applies.
+-->
+<!ELEMENT class (#PCDATA)>
+
+
+<!--
+The type-mappings element contains the java to sql mappings.
+-->
+<!ELEMENT type-mappings (type-mapping+)>
+
+<!--
+The type-mapping element contains a named java to sql mapping.
+This includes both type mapping and function mapping.
+-->
+<!ELEMENT type-mapping (name, row-locking-template, pk-constraint-template,
+ fk-constraint-template, auto-increment-template?,
+ add-column-template?, alter-column-template?, drop-column-template?,
+ alias-header-prefix,
+ alias-header-suffix, alias-max-length, subquery-supported,
+ true-mapping, false-mapping, max-keys-in-delete?,
+ function-mapping*, mapping+)>
+
+<!--
+Name of the type-mapping.
+-->
+<!ELEMENT name (#PCDATA)>
+
+<!--
+This is the template used to create a row lock on the selected rows. The
+arguments supplied are as follows:
+
+1. Select clause
+2. From clasue; the order of the tables is currently not guarenteed
+3. Where clause
+
+If row locking is not supported in select statement this element should be
+empty. The most common form of row locking is select for update as in the
+example that follows:
+
+SELECT ?1 FROM ?2 WHERE ?3 FOR UPDATE
+-->
+<!ELEMENT row-locking-template (#PCDATA)>
+
+<!--
+This is the template used to create a primary key constraint in the create
+table statement. The arguments supplied are as follows:
+
+1. Primary key constraint name; which is always pk_{table-name}
+2. Comma sepperated list of primary key column names
+
+If a primary key constraint clause is not supported in a create table statement
+this element should be empty. The most common form of a primary key constraint
+follows:
+
+CONSTRAINT ?1 PRIMARY KEY (?2)
+-->
+<!ELEMENT pk-constraint-template (#PCDATA)>
+
+<!--
+This is the template used to create a foreign key constraint in sepperate
+statement. The arguments supplied are as follows:
+
+1. Table name
+2. Foreign key constraint name; which is always fk_{table-name}_{cmr-field-name}
+3. Comma sepperated list of foreign key column names
+4. References table name
+5. Comma sepperated list of the referenced primary key column names
+
+If the datasource does not support foreign key constraints this element should
+be empty. The most common form of a foreign key constraint follows:
+
+ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)
+-->
+<!ELEMENT fk-constraint-template (#PCDATA)>
+
+<!--
+This element is used to define auto-increment template for a column
+-->
+<!ELEMENT auto-increment-template (#PCDATA)>
+
+<!--
+Template to add a column to the database.
+Arguments are as follows :
+
+1. Table name
+2. Column new
+3. Column type
+
+Default value is
+
+ALTER TABLE ?1 ADD ?2 ?3
+-->
+<!ELEMENT add-column-template (#PCDATA)>
+
+<!--
+Template to alter a column to the database.
+Arguments are as follows :
+
+1. Table name
+2. Column new
+3. Column type
+
+Default value is
+
+ALTER TABLE ?1 ALTER ?2 TYPE ?3
+-->
+<!ELEMENT alter-column-template (#PCDATA)>
+
+<!--
+Template to drop a column to the database.
+Arguments are as follows :
+
+1. Table name
+2. Column new
+
+Default value is
+
+ALTER TABLE ?1 DROP ?2
+-->
+<!ELEMENT drop-column-template (#PCDATA)>
+
+<!--
+An alias header is prepended to a generated table alias by the EJB-QL compiler
+to prevent name collisions. An alias header is constructed as folows:
+
+alias-header-prefix + int_counter + alias-header-suffix
+-->
+<!ELEMENT alias-header-prefix (#PCDATA)>
+<!ELEMENT alias-header-suffix (#PCDATA)>
+<!ELEMENT alias-max-length (#PCDATA)>
+
+<!--
+Does this type-mapping support subqueries. Some EJB-QL opperators are mapped
+to exists subqueries. If subquery is false the EJB-QL compiler will use a
+left join and is null.
+
+The subquery-supported element must be one of the two following:
+ <create-table>true</create-table>
+ <create-table>false</create-table>
+-->
+<!ELEMENT subquery-supported (#PCDATA)>
+
+<!--
+The true and false mappings are the mappings for true and false in EJB-QL
+queries.
+-->
+<!ELEMENT true-mapping (#PCDATA)>
+<!ELEMENT false-mapping (#PCDATA)>
+
+<!--
+The maximum number of key pairs that can appear in a single DELETE statement for relation table
+-->
+<!ELEMENT max-keys-in-delete (#PCDATA)>
+
+<!--
+Specifies the mapping from a java type to a jdbc and a sql type.
+-->
+<!ELEMENT mapping (java-type, jdbc-type, sql-type, param-setter?, result-reader?)>
+
+<!--
+Specifies the java class type to be mapped.
+-->
+<!ELEMENT java-type (#PCDATA)>
+
+<!--
+Fully qualified name of the JDBCParameterSetter implementation.
+-->
+<!ELEMENT param-setter (#PCDATA)>
+
+<!--
+Fully qualified name of the JDBCResultSetReader implementation.
+-->
+<!ELEMENT result-reader (#PCDATA)>
+
+<!--
+Specifies the mapping from an EJB-QL function to a sql function.
+-->
+<!ELEMENT function-mapping (function-name, function-sql)>
+
+<!--
+The name of the function to be mapped.
+-->
+<!ELEMENT function-name (#PCDATA)>
+
+<!--
+The sql to which the function is mapped. The sql can contain
+parameters specified with a question mark followed by the base one
+parameter number. For example, function mapping for concat in Oracle
+follows:
+
+<function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+</function-mapping>
+-->
+<!ELEMENT function-sql (#PCDATA)>
+
+<!--
+Unknown primary key configuration
+-->
+<!ELEMENT unknown-pk (key-generator-factory?, unknown-pk-class, field-name?,
+ read-only?, read-time-out?,
+ column-name?, (jdbc-type, sql-type)?, auto-increment? )>
+
+<!--
+The unknown primary key class.
+-->
+<!ELEMENT unknown-pk-class (#PCDATA)>
+
+<!--
+If present the field will auto-incremented by the database
+-->
+<!ELEMENT auto-increment EMPTY>
+
+<!--
+This element declares available for entity commands
+-->
+<!ELEMENT entity-commands (entity-command*)>
+
+<!--
+This element represents an entity command
+-->
+<!ELEMENT entity-command (attribute*)>
+
+<!--
+This attribute specifies the command name
+-->
+<!ATTLIST entity-command name CDATA #REQUIRED>
+
+<!--
+This attribute specifies the command class
+-->
+<!ATTLIST entity-command class CDATA #IMPLIED>
+
+<!--
+The attribute for create-method.
+-->
+<!ELEMENT attribute (#PCDATA)>
+
+<!--
+The name of the attribute
+-->
+<!ATTLIST attribute name CDATA #REQUIRED>
+
+<!--
+Optimistic locking configuration
+-->
+<!ELEMENT optimistic-locking (
+ group-name |
+ modified-strategy |
+ read-strategy |
+ ((version-column | timestamp-column | (key-generator-factory, field-type)),
+ field-name?, column-name?, (jdbc-type, sql-type)?)
+)>
+
+<!--
+Optimistic locking field group name.
+This name must match one of the entity's load-group-name.
+The fields in this group will be used for optimistic locking.
+-->
+<!ELEMENT group-name (#PCDATA)>
+
+<!--
+Optimistic locking modified strategy.
+This means the fields that were modified during transaction
+will be used for optimistic locking
+-->
+<!ELEMENT modified-strategy EMPTY>
+
+<!--
+Optimistic locking read strategy.
+This strategy implies that the fields that were read/changed
+in the transaction will be used for optimistic locking
+-->
+<!ELEMENT read-strategy EMPTY>
+
+<!--
+Optimistic locking version column strategy.
+Setting this element will add to entity bean additional version field
+of type java.lang.Long that will be used for optimistic locking.
+Each update of the entity will increase the value of this field.
+-->
+<!ELEMENT version-column EMPTY>
+
+<!--
+Optimistic locking timestamp column strategy.
+Setting this element will add to entity bean additional field of type
+java.util.Date that will be used for optimistic locking.
+Each update of the entity will set the value of this field to the current
+time.
+-->
+<!ELEMENT timestamp-column EMPTY>
+
+<!--
+Optimistic locking field type.
+The type for locking field in optimistic locking.
+-->
+<!ELEMENT field-type (#PCDATA)>
+
+<!--
+Key generator factory JNDI name.
+This element specifies the JNDI name of key generator factory that is
+used to obtain key generator for locking column used in optimistic locking.
+-->
+<!ELEMENT key-generator-factory (#PCDATA)>
+
+<!--
+Audit fields, choose the audit fields
+The created by and updated by require a caller principal
+The fields can also be cmp fields, use the same field-name
+-->
+<!ELEMENT audit (created-by?, created-time?, updated-by?, updated-time?)>
+
+<!--
+Created by principal, default is audit_created_by
+-->
+<!ELEMENT created-by (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+Created time, default is audit_created_time
+-->
+<!ELEMENT created-time (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+Updated by principal, default is audit_updated_by
+-->
+<!ELEMENT updated-by (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+Updated time, default is audit_updated_time
+-->
+<!ELEMENT updated-time (field-name?, column-name?, (jdbc-type, sql-type)?)>
+
+<!--
+ Container for user-type-mapping elements
+-->
+<!ELEMENT user-type-mappings (user-type-mapping+)>
+
+<!--
+ Defines a mapping of a user type to a column providing a mapper class.
+ Mapper is like a mediator: when storing, it takes an instance of the user
+ type and translates it to a column value; when loading, it takes a column
+ value and translates it to an instance of the user type.
+-->
+<!ELEMENT user-type-mapping (java-type, mapped-type, mapper, check-dirty-after-get?, state-factory?)>
+
+<!--
+ The type a java-type in user-type-mapping is mapped to.
+-->
+<!ELEMENT mapped-type (#PCDATA)>
+
+<!--
+ Mapper class for user-type-mapping.
+-->
+<!ELEMENT mapper (#PCDATA)>
+
+<!--
+ Provide reserved words that should be escaped when generating tables
+-->
+<!ELEMENT reserved-words (word+)>
+<!ELEMENT word (#PCDATA)>
+
+<!--
+Is relevant only for multi-object queries. Allowed values are true and false.
+If true, ResultSet will be read on demand, i.e. when user iterates through the collection.
+If false, user is given completely initialized result, i.e. when user got the result
+ResultSet is read till the end and closed.
+-->
+<!ELEMENT lazy-resultset-loading (#PCDATA)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/security_config.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/security_config.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/security_config.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,100 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!--Generated by XML Authority-->
+
+<!-- This is the XML DTD for the JBoss 3.0 security policy configuration.
+The DOCTYPE is:
+ <!DOCTYPE policy PUBLIC
+ "-//JBoss//DTD JBOSS Security Config 3.0//EN"
+ "http://www.jboss.org/j2ee/dtd/security_config.dtd">
+
+$Id: security_config.dtd 20476 2004-04-17 13:29:24Z tdiesler $
+$Revision: 20476 $
+
+The outline of the application-policy is:
+<policy>
+ <application-policy name="security-domain-name">
+ <authentication>
+ <login-module code="login.module1.class.name" flag="control_flag">
+ <module-option name = "option1-name">option1-value</module-option>
+ <module-option name = "option2-name">option2-value</module-option>
+ ...
+ </login-module>
+
+ <login-module code="login.module2.class.name" flag="control_flag">
+ ...
+ </login-module>
+ ...
+ </authentication>
+ </application-policy>
+</policy>
+-->
+<!-- The root element of the security policy configuration -->
+<!ELEMENT policy (application-policy+)>
+
+<!-- An application-policy defines the security configuration for an application domain. Currently
+this consists of only the login module configurations specified in the authentication -->
+<!ELEMENT application-policy (authentication)>
+
+<!-- The application-policy name attribute gives the name of the security domain.
+-->
+<!ATTLIST application-policy name CDATA #REQUIRED>
+
+<!-- The authentication element contains the login module stack configuration. Each
+login module configuration is specified using a login-module element.
+-->
+<!ELEMENT authentication (login-module+)>
+
+<!-- The login-module element defines a JAAS login module configuration entry. Each
+entry must have a code and flag attribute along with zero or more login module options
+specified via the module-option element.
+-->
+<!ELEMENT login-module (module-option*)>
+
+<!-- The flag attribute controls how a login module participates in the overall authentication proceedure.
+Required - The LoginModule is required to succeed.
+ If it succeeds or fails, authentication still continues
+ to proceed down the LoginModule list.
+
+Requisite - The LoginModule is required to succeed.
+ If it succeeds, authentication continues down the
+ LoginModule list. If it fails,
+ control immediately returns to the application
+ (authentication does not proceed down the
+ LoginModule list).
+
+Sufficient - The LoginModule is not required to
+ succeed. If it does succeed, control immediately
+ returns to the application (authentication does not
+ proceed down the LoginModule list).
+ If it fails, authentication continues down the
+ LoginModule list.
+
+Optional - The LoginModule is not required to
+ succeed. If it succeeds or fails,
+ authentication still continues to proceed down the
+ LoginModule list.
+
+The overall authentication succeeds only if all required and requisite LoginModules succeed. If a sufficient
+LoginModule is configured and succeeds, then only the required and requisite LoginModules prior to that
+sufficient LoginModule need to have succeeded for the overall authentication to succeed. If no required or
+requisite LoginModules are configured for an application, then at least one sufficient or optional LoginModule
+must succeed.
+-->
+<!ATTLIST login-module flag (required | requisite | sufficient | optional ) #REQUIRED>
+
+<!-- The code attribute gives the fully qualifed class name of the javax.security.auth.spi.LoginModule
+interface implementation for the login module.
+-->
+<!ATTLIST login-module code CDATA #REQUIRED>
+
+<!-- A module option defines a name, value pair of strings that are passed to a LoginModule when it
+is initialized during the login proceedure. The name attribute defines the option name while the
+element value is the option string value.
+-->
+<!ELEMENT module-option (#PCDATA)>
+
+<!-- The name attribute specifies the name of the login module option.
+-->
+<!ATTLIST module-option name CDATA #REQUIRED>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/service-ref_4_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/service-ref_4_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/service-ref_4_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,90 @@
+<?xml version='1.0' encoding='UTF-8'?>
+
+<!--
+ $Id: jboss-client_5_0.dtd 58121 2006-11-04 19:57:58Z thomas.diesler at jboss.com $
+
+ <!DOCTYPE jboss-web PUBLIC
+ "-//JBoss//DTD Web Service Reference 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/service-ref_4_0.dtd">
+-->
+
+<!--
+ The service-ref element provides jboss specific deployment values to
+ the web service reference in application-client.xml.
+
+ 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>
+ <port-component-ref>
+ <service-endpoint-interface>com.dot.SEI</service-endpoint-interface>
+ <call-property>
+ <prop-name>X</prop-name>
+ <prop-value>Y</prop-value>
+ </call-property>
+ </port-component-ref>
+ </service-ref>
+-->
+<!ELEMENT service-ref (service-ref-name, config-name?, config-file?, port-component-ref*, wsdl-override?, call-property*)>
+
+<!-- The service-ref-name element gives the ENC relative name used
+in the ejb-jar.xml service-ref-name element.
+
+Used in: service-ref
+-->
+<!ELEMENT service-ref-name (#PCDATA)>
+
+<!-- The optional config-name element gives the client configuration name that must be present in
+the configuration given by element config-file.
+
+The default is: Standard Client
+
+Used in: service-ref
+-->
+<!ELEMENT config-name (#PCDATA)>
+
+<!-- The optional config-file element gives the to a URL or resource name for the client configuration.
+The default is: META-INF/standard-jbossws-client-config.xml
+
+Used in: service-ref
+-->
+<!ELEMENT config-file (#PCDATA)>
+
+<!-- The port-component-ref element provides additional information about
+the standard j2ee service-reference/port-component-ref. Currently this includes
+properties that should be associated with the call/stub for the port.
+
+Used in: service-ref
+-->
+<!ELEMENT port-component-ref (service-endpoint-interface?, call-property*)>
+
+<!-- The wsdl-override element the actual wsdl docuement the web service client
+uses to connect to the remote service. It overrides the value of wsdl-file in ejb-jar.xml.
+
+Used in: service-ref
+-->
+<!ELEMENT wsdl-override (#PCDATA)>
+
+<!-- Fully qualified name of service endpoint interface
+-->
+<!ELEMENT service-endpoint-interface ( #PCDATA )>
+
+<!-- Arbitrary jaxrpc property values that should be set on a Call object
+before it's returned to the web service client. The valid properties can be any
+properties supported by the jaxrpc Call implementation.
+-->
+<!ELEMENT call-property ( prop-name, prop-value )>
+
+<!-- The string value of a property name
+-->
+<!ELEMENT prop-name (#PCDATA)>
+
+<!-- The string value of a property value
+-->
+<!ELEMENT prop-value (#PCDATA)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/service-ref_4_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/service-ref_4_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/service-ref_4_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,90 @@
+<?xml version='1.0' encoding='UTF-8'?>
+
+<!--
+ $Id: jboss-web_4_0.dtd 60134 2007-01-31 13:14:47Z thomas.diesler at jboss.com $
+
+ <!DOCTYPE jboss-web PUBLIC
+ "-//JBoss//DTD Web Service Reference 4.2//EN"
+ "http://www.jboss.org/j2ee/dtd/service-ref_4_2.dtd">
+-->
+
+<!--
+ The service-ref element provides jboss specific deployment values to
+ the web service reference in application-client.xml.
+
+ 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>
+ <port-component-ref>
+ <service-endpoint-interface>com.dot.SEI</service-endpoint-interface>
+ <call-property>
+ <prop-name>X</prop-name>
+ <prop-value>Y</prop-value>
+ </call-property>
+ </port-component-ref>
+ </service-ref>
+-->
+<!ELEMENT service-ref (service-ref-name, config-name?, config-file?, port-component-ref*, wsdl-override?, call-property*)>
+
+<!-- The service-ref-name element gives the ENC relative name used
+in the ejb-jar.xml service-ref-name element.
+
+Used in: service-ref
+-->
+<!ELEMENT service-ref-name (#PCDATA)>
+
+<!-- The optional config-name element gives the client configuration name that must be present in
+the configuration given by element config-file.
+
+The default is: Standard Client
+
+Used in: service-ref
+-->
+<!ELEMENT config-name (#PCDATA)>
+
+<!-- The optional config-file element gives the to a URL or resource name for the client configuration.
+The default is: META-INF/standard-jbossws-client-config.xml
+
+Used in: service-ref
+-->
+<!ELEMENT config-file (#PCDATA)>
+
+<!-- The port-component-ref element provides additional information about
+the standard j2ee service-reference/port-component-ref. Currently this includes
+properties that should be associated with the call/stub for the port.
+
+Used in: service-ref
+-->
+<!ELEMENT port-component-ref (service-endpoint-interface?, call-property*)>
+
+<!-- The wsdl-override element the actual wsdl docuement the web service client
+uses to connect to the remote service. It overrides the value of wsdl-file in ejb-jar.xml.
+
+Used in: service-ref
+-->
+<!ELEMENT wsdl-override (#PCDATA)>
+
+<!-- Fully qualified name of service endpoint interface
+-->
+<!ELEMENT service-endpoint-interface ( #PCDATA )>
+
+<!-- Arbitrary jaxrpc property values that should be set on a Call object
+before it's returned to the web service client. The valid properties can be any
+properties supported by the jaxrpc Call implementation.
+-->
+<!ELEMENT call-property ( prop-name, prop-value )>
+
+<!-- The string value of a property name
+-->
+<!ELEMENT prop-name (#PCDATA)>
+
+<!-- The string value of a property value
+-->
+<!ELEMENT prop-value (#PCDATA)>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-app_2_2.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-app_2_2.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-app_2_2.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,639 @@
+<!--
+Copyright 1999 Sun Microsystems, Inc. 901 San Antonio Road,
+Palo Alto, CA 94303, U.S.A. All rights reserved.
+
+This product or document is protected by copyright and distributed
+under licenses restricting its use, copying, distribution, and
+decompilation. No part of this product or documentation may be
+reproduced in any form by any means without prior written authorization
+of Sun and its licensors, if any.
+
+Third party software, including font technology, is copyrighted and
+licensed from Sun suppliers.
+
+Sun, Sun Microsystems, the Sun Logo, Solaris, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail and Enterprise JavaBeans,
+are trademarks or registered trademarks of Sun Microsystems, Inc in the U.S.
+and other countries.
+
+All SPARC trademarks are used under license and are trademarks
+or registered trademarks of SPARC International, Inc.
+in the U.S. and other countries. Products bearing SPARC
+trademarks are based upon an architecture developed by Sun Microsystems, Inc.
+
+PostScript is a registered trademark of Adobe Systems, Inc.
+
+
+Federal Acquisitions: Commercial Software - Government Users Subject to
+Standard License Terms and Conditions.
+
+
+
+DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
+CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
+IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
+PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT
+TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY
+INVALID.
+
+_________________________________________________________________________
+Copyright 1999 Sun Microsystems, Inc.,
+901 San Antonio Road, Palo Alto, CA 94303, Etats-Unis.
+Tous droits re'serve's.
+
+
+Ce produit ou document est prote'ge' par un copyright et distribue' avec
+des licences qui en restreignent l'utilisation, la copie, la distribution,
+et la de'compilation. Aucune partie de ce produit ou de sa documentation
+associe'e ne peut e^tre reproduite sous aucune forme, par quelque moyen
+que ce soit, sans l'autorisation pre'alable et e'crite de Sun et de ses
+bailleurs de licence, s'il y en a.
+
+Le logiciel de'tenu par des tiers, et qui comprend la technologie
+relative aux polices de caracte`res, est prote'ge' par un copyright
+et licencie' par des fournisseurs de Sun.
+
+Sun, Sun Microsystems, le logo Sun, Solaris, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail, et Enterprise JavaBeans,
+sont des marques de fabrique ou des marques de'pose'es de Sun
+Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
+
+Toutes les marques SPARC sont utilise'es sous licence et sont
+des marques de fabrique ou des marques de'pose'es de SPARC
+International, Inc. aux Etats-Unis et dans
+d'autres pays. Les produits portant les marques SPARC sont
+base's sur une architecture de'veloppe'e par Sun Microsystems, Inc.
+
+Postcript est une marque enregistre'e d'Adobe Systems Inc.
+
+LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS,
+DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES,
+DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT
+TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE
+A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.
+-->
+
+<!--
+The web-app element is the root of the deployment descriptor for
+a web application
+-->
+
+<!ELEMENT web-app (icon?, display-name?, description?, distributable?,
+context-param*, servlet*, servlet-mapping*, session-config?,
+mime-mapping*, welcome-file-list?, error-page*, taglib*,
+resource-ref*, security-constraint*, login-config?, security-role*,
+env-entry*, ejb-ref*)>
+
+<!--
+The icon element contains a small-icon and a large-icon element
+which specify the location within the web application for a small and
+large image used to represent the web application in a GUI tool. At a
+minimum, tools must accept GIF and JPEG format images.
+-->
+
+<!ELEMENT icon (small-icon?, large-icon?)>
+
+<!--
+The small-icon element contains the location within the web
+application of a file containing a small (16x16 pixel) icon image.
+-->
+
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+The large-icon element contains the location within the web
+application of a file containing a large (32x32 pixel) icon image.
+-->
+
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+The display-name element contains a short name that is intended
+to be displayed by GUI tools
+-->
+
+<!ELEMENT display-name (#PCDATA)>
+
+<!--
+The description element is used to provide descriptive text about
+the parent element.
+-->
+
+<!ELEMENT description (#PCDATA)>
+
+<!--
+The distributable element, by its presence in a web application
+deployment descriptor, indicates that this web application is
+programmed appropriately to be deployed into a distributed servlet
+container
+-->
+
+<!ELEMENT distributable EMPTY>
+
+<!--
+The context-param element contains the declaration of a web
+application's servlet context initialization parameters.
+-->
+
+<!ELEMENT context-param (param-name, param-value, description?)>
+
+<!--
+The param-name element contains the name of a parameter.
+-->
+
+<!ELEMENT param-name (#PCDATA)>
+
+<!--
+The param-value element contains the value of a parameter.
+-->
+
+<!ELEMENT param-value (#PCDATA)>
+
+<!--
+The servlet element contains the declarative data of a
+servlet. If a jsp-file is specified and the load-on-startup element is
+present, then the JSP should be precompiled and loaded.
+-->
+
+<!ELEMENT servlet (icon?, servlet-name, display-name?, description?,
+(servlet-class|jsp-file), init-param*, load-on-startup?, security-role-ref*)>
+
+<!--
+The servlet-name element contains the canonical name of the
+servlet.
+-->
+
+<!ELEMENT servlet-name (#PCDATA)>
+
+<!--
+The servlet-class element contains the fully qualified class name
+of the servlet.
+-->
+
+<!ELEMENT servlet-class (#PCDATA)>
+
+<!--
+The jsp-file element contains the full path to a JSP file within
+the web application.
+-->
+
+<!ELEMENT jsp-file (#PCDATA)>
+
+<!--
+The init-param element contains a name/value pair as an
+initialization param of the servlet
+-->
+
+<!ELEMENT init-param (param-name, param-value, description?)>
+
+<!--
+The load-on-startup element indicates that this servlet should be
+loaded on the startup of the web application. The optional contents of
+these element must be a positive integer indicating the order in which
+the servlet should be loaded. Lower integers are loaded before higher
+integers. If no value is specified, or if the value specified is not a
+positive integer, the container is free to load it at any time in the
+startup sequence.
+-->
+
+<!ELEMENT load-on-startup (#PCDATA)>
+
+<!--
+The servlet-mapping element defines a mapping between a servlet
+and a url pattern
+-->
+
+<!ELEMENT servlet-mapping (servlet-name, url-pattern)>
+
+<!--
+The url-pattern element contains the url pattern of the
+mapping. Must follow the rules specified in Section 10 of the Servlet
+API Specification.
+-->
+
+<!ELEMENT url-pattern (#PCDATA)>
+
+<!--
+The session-config element defines the session parameters for
+this web application.
+-->
+
+<!ELEMENT session-config (session-timeout?)>
+
+<!--
+The session-timeout element defines the default session timeout
+interval for all sessions created in this web application. The
+specified timeout must be expressed in a whole number of minutes.
+-->
+
+<!ELEMENT session-timeout (#PCDATA)>
+
+<!--
+The mime-mapping element defines a mapping between an extension
+and a mime type.
+-->
+
+<!ELEMENT mime-mapping (extension, mime-type)>
+
+<!--
+The extension element contains a string describing an
+extension. example: "txt"
+-->
+
+<!ELEMENT extension (#PCDATA)>
+
+<!--
+The mime-type element contains a defined mime type. example:
+"text/plain"
+-->
+
+<!ELEMENT mime-type (#PCDATA)>
+
+<!--
+The welcome-file-list contains an ordered list of welcome files
+elements.
+-->
+
+<!ELEMENT welcome-file-list (welcome-file+)>
+
+<!--
+The welcome-file element contains file name to use as a default
+welcome file, such as index.html
+-->
+
+<!ELEMENT welcome-file (#PCDATA)>
+
+<!--
+The taglib element is used to describe a JSP tag library.
+-->
+
+<!ELEMENT taglib (taglib-uri, taglib-location)>
+
+<!--
+The taglib-uri element describes a URI, relative to the location
+of the web.xml document, identifying a Tag Library used in the Web
+Application.
+-->
+
+<!ELEMENT taglib-uri (#PCDATA)>
+
+<!--
+the taglib-location element contains the location (as a resource
+relative to the root of the web application) where to find the Tag
+Libary Description file for the tag library.
+-->
+
+<!ELEMENT taglib-location (#PCDATA)>
+
+<!--
+The error-page element contains a mapping between an error code
+or exception type to the path of a resource in the web application
+-->
+
+<!ELEMENT error-page ((error-code | exception-type), location)>
+
+<!--
+The error-code contains an HTTP error code, ex: 404
+-->
+
+<!ELEMENT error-code (#PCDATA)>
+
+<!--
+The exception type contains a fully qualified class name of a
+Java exception type.
+-->
+
+<!ELEMENT exception-type (#PCDATA)>
+
+<!--
+The location element contains the location of the resource in the
+web application
+-->
+
+<!ELEMENT location (#PCDATA)>
+
+<!--
+The resource-ref element contains a declaration of a Web
+Application's reference to an external resource.
+-->
+
+<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth)>
+
+<!--
+The res-ref-name element specifies the name of the resource
+factory reference name.
+-->
+
+<!ELEMENT res-ref-name (#PCDATA)>
+
+<!--
+The res-type element specifies the (Java class) type of the data
+source.
+-->
+
+<!ELEMENT res-type (#PCDATA)>
+
+<!--
+The res-auth element indicates whether the application component
+code performs resource signon programmatically or whether the
+container signs onto the resource based on the principle mapping
+information supplied by the deployer. Must be CONTAINER or SERVLET
+-->
+
+<!ELEMENT res-auth (#PCDATA)>
+
+<!--
+The security-constraint element is used to associate security
+constraints with one or more web resource collections
+-->
+
+<!ELEMENT security-constraint (web-resource-collection+,
+auth-constraint?, user-data-constraint?)>
+
+<!--
+The web-resource-collection element is used to identify a subset
+of the resources and HTTP methods on those resources within a web
+application to which a security constraint applies. If no HTTP methods
+are specified, then the security constraint applies to all HTTP
+methods.
+-->
+
+<!ELEMENT web-resource-collection (web-resource-name, description?,
+url-pattern*, http-method*)>
+
+<!--
+The web-resource-name contains the name of this web resource
+collection
+-->
+
+<!ELEMENT web-resource-name (#PCDATA)>
+
+<!--
+The http-method contains an HTTP method (GET | POST |...)
+-->
+
+<!ELEMENT http-method (#PCDATA)>
+
+<!--
+The user-data-constraint element is used to indicate how data
+communicated between the client and container should be protected
+-->
+
+<!ELEMENT user-data-constraint (description?, transport-guarantee)>
+
+<!--
+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.
+-->
+
+<!ELEMENT transport-guarantee (#PCDATA)>
+
+<!--
+The auth-constraint element indicates the user roles that should
+be permitted access to this resource collection. The role used here
+must appear in a security-role-ref element.
+-->
+
+<!ELEMENT auth-constraint (description?, role-name*)>
+
+<!--
+The role-name element contains the name of a security role.
+-->
+
+<!ELEMENT role-name (#PCDATA)>
+
+<!--
+The login-config element is used to configure the authentication
+method that should be used, the realm name that should be used for
+this application, and the attributes that are needed by the form login
+mechanism.
+-->
+
+<!ELEMENT login-config (auth-method?, realm-name?, form-login-config?)>
+
+<!--
+The realm name element specifies the realm name to use in HTTP
+Basic authorization
+-->
+
+<!ELEMENT realm-name (#PCDATA)>
+
+<!--
+The form-login-config element specifies the login and error pages
+that should be used in form based login. If form based authentication
+is not used, these elements are ignored.
+-->
+
+<!ELEMENT form-login-config (form-login-page, form-error-page)>
+
+<!--
+The form-login-page element defines the location in the web app
+where the page that can be used for login can be found
+-->
+
+<!ELEMENT form-login-page (#PCDATA)>
+
+<!--
+The form-error-page element defines the location in the web app
+where the error page that is displayed when login is not successful
+can be found
+-->
+
+<!ELEMENT form-error-page (#PCDATA)>
+
+<!--
+The auth-method element is used to configure the authentication
+mechanism for the web application. As a prerequisite to gaining access
+to any web resources which are protected by an authorization
+constraint, a user must have authenticated using the configured
+mechanism. Legal values for this element are "BASIC", "DIGEST",
+"FORM", or "CLIENT-CERT".
+-->
+
+<!ELEMENT auth-method (#PCDATA)>
+
+<!--
+The security-role element contains the declaration of a security
+role which is used in the security-constraints placed on the web
+application.
+-->
+
+<!ELEMENT security-role (description?, role-name)>
+
+<!--
+The role-name element contains the name of a role. This element
+must contain a non-empty string.
+-->
+
+<!ELEMENT security-role-ref (description?, role-name, role-link)>
+
+<!--
+The role-link element is used to link a security role reference
+to a defined security role. The role-link element must contain the
+name of one of the security roles defined in the security-role
+elements.
+-->
+
+<!ELEMENT role-link (#PCDATA)>
+
+<!--
+The env-entry element contains the declaration of an
+application's environment entry. This element is required to be
+honored on in J2EE compliant servlet containers.
+-->
+
+<!ELEMENT env-entry (description?, env-entry-name, env-entry-value?,
+env-entry-type)>
+
+<!--
+The env-entry-name contains the name of an application's
+environment entry
+-->
+
+<!ELEMENT env-entry-name (#PCDATA)>
+
+<!--
+The env-entry-value element contains the value of an
+application's environment entry
+-->
+
+<!ELEMENT env-entry-value (#PCDATA)>
+
+<!--
+The env-entry-type element contains the fully qualified Java type
+of the environment entry value that is expected by the application
+code. The following are the legal values of env-entry-type:
+java.lang.Boolean, java.lang.String, java.lang.Integer,
+java.lang.Double, java.lang.Float.
+-->
+
+<!ELEMENT env-entry-type (#PCDATA)>
+
+<!--
+The ejb-ref element is used to declare a reference to an
+enterprise bean.
+-->
+
+<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type, home, remote,
+ejb-link?)>
+
+<!--
+The ejb-ref-name element contains the name of an EJB
+reference. This is the JNDI name that the servlet code uses to get a
+reference to the enterprise bean.
+-->
+
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+<!--
+The ejb-ref-type element contains the expected java class type of
+the referenced EJB.
+-->
+
+<!ELEMENT ejb-ref-type (#PCDATA)>
+
+<!--
+The ejb-home element contains the fully qualified name of the
+EJB's home interface
+-->
+
+<!ELEMENT home (#PCDATA)>
+
+<!--
+The ejb-remote element contains the fully qualified name of the
+EJB's remote interface
+-->
+
+<!ELEMENT remote (#PCDATA)>
+
+<!--
+The ejb-link element is used in the ejb-ref element to specify
+that an EJB reference is linked to an EJB in an encompassing Java2
+Enterprise Edition (J2EE) application package. The value of the
+ejb-link element must be the ejb-name of and EJB in the J2EE
+application package.
+-->
+
+<!ELEMENT ejb-link (#PCDATA)>
+
+<!--
+The ID mechanism is to allow tools to easily make tool-specific
+references to the elements of the deployment descriptor. This allows
+tools that produce additional deployment information (i.e information
+beyond the standard deployment descriptor information) to store the
+non-standard information in a separate file, and easily refer from
+these tools-specific files to the information in the standard web-app
+deployment descriptor.
+-->
+
+<!ATTLIST web-app id ID #IMPLIED>
+<!ATTLIST icon id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST distributable id ID #IMPLIED>
+<!ATTLIST context-param id ID #IMPLIED>
+<!ATTLIST param-name id ID #IMPLIED>
+<!ATTLIST param-value id ID #IMPLIED>
+<!ATTLIST servlet id ID #IMPLIED>
+<!ATTLIST servlet-name id ID #IMPLIED>
+<!ATTLIST servlet-class id ID #IMPLIED>
+<!ATTLIST jsp-file id ID #IMPLIED>
+<!ATTLIST init-param id ID #IMPLIED>
+<!ATTLIST load-on-startup id ID #IMPLIED>
+<!ATTLIST servlet-mapping id ID #IMPLIED>
+<!ATTLIST url-pattern id ID #IMPLIED>
+<!ATTLIST session-config id ID #IMPLIED>
+<!ATTLIST session-timeout id ID #IMPLIED>
+<!ATTLIST mime-mapping id ID #IMPLIED>
+<!ATTLIST extension id ID #IMPLIED>
+<!ATTLIST mime-type id ID #IMPLIED>
+<!ATTLIST welcome-file-list id ID #IMPLIED>
+<!ATTLIST welcome-file id ID #IMPLIED>
+<!ATTLIST taglib id ID #IMPLIED>
+<!ATTLIST taglib-uri id ID #IMPLIED>
+<!ATTLIST taglib-location id ID #IMPLIED>
+<!ATTLIST error-page id ID #IMPLIED>
+<!ATTLIST error-code id ID #IMPLIED>
+<!ATTLIST exception-type id ID #IMPLIED>
+<!ATTLIST location id ID #IMPLIED>
+<!ATTLIST resource-ref id ID #IMPLIED>
+<!ATTLIST res-ref-name id ID #IMPLIED>
+<!ATTLIST res-type id ID #IMPLIED>
+<!ATTLIST res-auth id ID #IMPLIED>
+<!ATTLIST security-constraint id ID #IMPLIED>
+<!ATTLIST web-resource-collection id ID #IMPLIED>
+<!ATTLIST web-resource-name id ID #IMPLIED>
+<!ATTLIST http-method id ID #IMPLIED>
+<!ATTLIST user-data-constraint id ID #IMPLIED>
+<!ATTLIST transport-guarantee id ID #IMPLIED>
+<!ATTLIST auth-constraint id ID #IMPLIED>
+<!ATTLIST role-name id ID #IMPLIED>
+<!ATTLIST login-config id ID #IMPLIED>
+<!ATTLIST realm-name id ID #IMPLIED>
+<!ATTLIST form-login-config id ID #IMPLIED>
+<!ATTLIST form-login-page id ID #IMPLIED>
+<!ATTLIST form-error-page id ID #IMPLIED>
+<!ATTLIST auth-method id ID #IMPLIED>
+<!ATTLIST security-role id ID #IMPLIED>
+<!ATTLIST security-role-ref id ID #IMPLIED>
+<!ATTLIST role-link id ID #IMPLIED>
+<!ATTLIST env-entry id ID #IMPLIED>
+<!ATTLIST env-entry-name id ID #IMPLIED>
+<!ATTLIST env-entry-value id ID #IMPLIED>
+<!ATTLIST env-entry-type id ID #IMPLIED>
+<!ATTLIST ejb-ref id ID #IMPLIED>
+<!ATTLIST ejb-ref-name id ID #IMPLIED>
+<!ATTLIST ejb-ref-type id ID #IMPLIED>
+<!ATTLIST home id ID #IMPLIED>
+<!ATTLIST remote id ID #IMPLIED>
+<!ATTLIST ejb-link id ID #IMPLIED>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-app_2_3.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-app_2_3.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-app_2_3.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1063 @@
+<!--
+Copyright (c) 2000 Sun Microsystems, Inc.,
+901 San Antonio Road,
+Palo Alto, California 94303, U.S.A.
+All rights reserved.
+
+Sun Microsystems, Inc. has intellectual property rights relating to
+technology embodied in the product that is described in this document.
+In particular, and without limitation, these intellectual property
+rights may include one or more of the U.S. patents listed at
+http://www.sun.com/patents and one or more additional patents or
+pending patent applications in the U.S. and in other countries.
+
+This document and the product to which it pertains are distributed
+under licenses restricting their use, copying, distribution, and
+decompilation. This document may be reproduced and distributed but may
+not be changed without prior written authorization of Sun and its
+licensors, if any.
+
+Third-party software, including font technology, is copyrighted and
+licensed from Sun suppliers.
+
+Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail and and
+Enterprise JavaBeans are trademarks or registered trademarks of Sun
+Microsystems, Inc. in the U.S. and other countries.
+
+Federal Acquisitions: Commercial Software - Government Users Subject to
+Standard License Terms and Conditions.
+
+DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
+CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
+WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
+NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
+DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
+
+
+_________________________________________________________________________
+
+Copyright (c) 2000 Sun Microsystems, Inc.,
+901 San Antonio Road,
+Palo Alto, California 94303, E'tats-Unis.
+Tous droits re'serve's.
+
+Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
+relatants a` la technologie incorpore'e dans le produit qui est de'crit
+dans ce document. En particulier, et sans la limitation, ces droits de
+proprie'te' intellectuels peuvent inclure un ou plus des brevets
+ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
+brevets plus supple'mentaires ou les applications de brevet en attente
+dans les E'tats-Unis et dans les autres pays.
+
+Ce produit ou document est prote'ge' par un copyright et distribue'
+avec des licences qui en restreignent l'utilisation, la copie, la
+distribution, et la de'compilation. Ce documention associe n peut
+e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
+l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
+licence, le cas e'che'ant.
+
+Le logiciel de'tenu par des tiers, et qui comprend la technologie
+relative aux polices de caracte`res, est prote'ge' par un copyright et
+licencie' par des fournisseurs de Sun.
+
+Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
+Naming and Directory Interface, JDBC, JDK, JavaMail et and
+Enterprise JavaBeans sont des marques de fabrique ou des marques
+de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
+pays.
+
+LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
+DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
+EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
+NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
+L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
+CONTREFAC,ON.
+-->
+
+<!--
+This is the XML DTD for the Servlet 2.3 deployment descriptor.
+All Servlet 2.3 deployment descriptors must include a DOCTYPE
+of the following form:
+
+ <!DOCTYPE web-app PUBLIC
+ "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
+ "http://java.sun.com/dtd/web-app_2_3.dtd">
+
+-->
+
+<!--
+The following conventions apply to all J2EE deployment descriptor
+elements unless indicated otherwise.
+
+- In elements that contain PCDATA, leading and trailing whitespace
+ in the data may be ignored.
+
+- In elements whose value is an "enumerated type", the value is
+ case sensitive.
+
+- In elements that specify a pathname to a file within the same
+ JAR file, relative filenames (i.e., those not starting with "/")
+ are considered relative to the root of the JAR file's namespace.
+ Absolute filenames (i.e., those starting with "/") also specify
+ names in the root of the JAR file's namespace. In general, relative
+ names are preferred. The exception is .war files where absolute
+ names are preferred for consistency with the servlet API.
+-->
+
+
+<!--
+The web-app element is the root of the deployment descriptor for
+a web application.
+-->
+<!ELEMENT web-app (icon?, display-name?, description?, distributable?,
+context-param*, filter*, filter-mapping*, listener*, servlet*,
+servlet-mapping*, session-config?, mime-mapping*, welcome-file-list?,
+error-page*, taglib*, resource-env-ref*, resource-ref*, security-constraint*,
+login-config?, security-role*, env-entry*, ejb-ref*, ejb-local-ref*)>
+
+<!--
+The auth-constraint element indicates the user roles that should
+be permitted access to this resource collection. The role-name
+used here must either correspond to the role-name of one of the
+security-role elements defined for this web application, or be
+the specially reserved role-name "*" that is a compact syntax for
+indicating all roles in the web application. If both "*" and
+rolenames appear, the container interprets this as all roles.
+If no roles are defined, no user is allowed access to the portion of
+the web application described by the containing security-constraint.
+The container matches role names case sensitively when determining
+access.
+
+
+Used in: security-constraint
+-->
+<!ELEMENT auth-constraint (description?, role-name*)>
+
+<!--
+The auth-method element is used to configure the authentication
+mechanism for the web application. As a prerequisite to gaining access to any web resources which are protected by an authorization
+constraint, a user must have authenticated using the configured
+mechanism. Legal values for this element are "BASIC", "DIGEST",
+"FORM", or "CLIENT-CERT".
+
+Used in: login-config
+-->
+<!ELEMENT auth-method (#PCDATA)>
+
+<!--
+The context-param element contains the declaration of a web
+application's servlet context initialization parameters.
+
+Used in: web-app
+-->
+<!ELEMENT context-param (param-name, param-value, description?)>
+
+<!--
+The description element is used to provide text describing the parent
+element. The description element should include any information that
+the web application war file producer wants to provide to the consumer of
+the web application war file (i.e., to the Deployer). Typically, the tools
+used by the web application war file consumer will display the description
+when processing the parent element that contains the description.
+
+Used in: auth-constraint, context-param, ejb-local-ref, ejb-ref,
+env-entry, filter, init-param, resource-env-ref, resource-ref, run-as,
+security-role, security-role-ref, servlet, user-data-constraint,
+web-app, web-resource-collection
+-->
+<!ELEMENT description (#PCDATA)>
+
+<!--
+The display-name element contains a short name that is intended to be
+displayed by tools. The display name need not be unique.
+
+Used in: filter, security-constraint, servlet, web-app
+
+Example:
+
+<display-name>Employee Self Service</display-name>
+-->
+<!ELEMENT display-name (#PCDATA)>
+
+<!--
+The distributable element, by its presence in a web application
+deployment descriptor, indicates that this web application is
+programmed appropriately to be deployed into a distributed servlet
+container
+
+Used in: web-app
+-->
+<!ELEMENT distributable EMPTY>
+
+<!--
+The ejb-link element is used in the ejb-ref or ejb-local-ref
+elements to specify that an EJB reference is linked to an
+enterprise bean.
+
+The name in the ejb-link element is composed of a
+path name specifying the ejb-jar containing the referenced enterprise
+bean with the ejb-name of the target bean appended and separated from
+the path name by "#". The path name is relative to the war file
+containing the web application that is referencing the enterprise bean.
+This allows multiple enterprise beans with the same ejb-name to be
+uniquely identified.
+
+Used in: ejb-local-ref, ejb-ref
+
+Examples:
+
+ <ejb-link>EmployeeRecord</ejb-link>
+
+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
+
+-->
+<!ELEMENT ejb-link (#PCDATA)>
+
+<!--
+The ejb-local-ref element is used for the declaration of a reference to
+an enterprise bean's local home. The declaration consists of:
+
+ - an optional description
+ - the EJB reference name used in the code of the web application
+ that's referencing the enterprise bean
+ - the expected type of the referenced enterprise bean
+ - the expected local home and local interfaces of the referenced
+ enterprise bean
+ - optional ejb-link information, used to specify the referenced
+ enterprise bean
+
+Used in: web-app
+-->
+<!ELEMENT ejb-local-ref (description?, ejb-ref-name, ejb-ref-type,
+ local-home, local, ejb-link?)>
+
+<!--
+The ejb-ref element is used for the declaration of a reference to
+an enterprise bean's home. The declaration consists of:
+
+ - an optional description
+ - the EJB reference name used in the code of
+ the web application that's referencing the enterprise bean
+ - the expected type of the referenced enterprise bean
+ - the expected home and remote interfaces of the referenced
+ enterprise bean
+ - optional ejb-link information, used to specify the referenced
+ enterprise bean
+
+Used in: web-app
+-->
+<!ELEMENT ejb-ref (description?, ejb-ref-name, ejb-ref-type,
+ home, remote, ejb-link?)>
+
+<!--
+The ejb-ref-name element contains the name of an EJB reference. The
+EJB reference is an entry in the web application's environment and is
+relative to the java:comp/env context. The name must be unique
+within the web application.
+
+It is recommended that name is prefixed with "ejb/".
+
+Used in: ejb-local-ref, ejb-ref
+
+Example:
+
+<ejb-ref-name>ejb/Payroll</ejb-ref-name>
+-->
+<!ELEMENT ejb-ref-name (#PCDATA)>
+
+<!--
+The ejb-ref-type element contains the expected type of the
+referenced enterprise bean.
+
+The ejb-ref-type element must be one of the following:
+
+ <ejb-ref-type>Entity</ejb-ref-type>
+ <ejb-ref-type>Session</ejb-ref-type>
+
+Used in: ejb-local-ref, ejb-ref
+-->
+<!ELEMENT ejb-ref-type (#PCDATA)>
+
+<!--
+The env-entry element contains the declaration of a web application's
+environment entry. The declaration consists of an optional
+description, the name of the environment entry, and an optional
+value. If a value is not specified, one must be supplied
+during deployment.
+-->
+<!ELEMENT env-entry (description?, env-entry-name, env-entry-value?,
+env-entry-type)>
+
+<!--
+The env-entry-name element contains the name of a web applications's
+environment entry. The name is a JNDI name relative to the
+java:comp/env context. The name must be unique within a web application.
+
+Example:
+
+<env-entry-name>minAmount</env-entry-name>
+
+Used in: env-entry
+-->
+<!ELEMENT env-entry-name (#PCDATA)>
+
+<!--
+The env-entry-type element contains the fully-qualified Java type of
+the environment entry value that is expected by the web application's
+code.
+
+The following are the legal values of env-entry-type:
+
+ java.lang.Boolean
+ java.lang.Byte
+ java.lang.Character
+ java.lang.String
+ java.lang.Short
+ java.lang.Integer
+ java.lang.Long
+ java.lang.Float
+ java.lang.Double
+
+Used in: env-entry
+-->
+<!ELEMENT env-entry-type (#PCDATA)>
+
+<!--
+The env-entry-value element contains the value of a web application's
+environment entry. The value must be a String that is valid for the
+constructor of the specified type that takes a single String
+parameter, or for java.lang.Character, a single character.
+
+Example:
+
+<env-entry-value>100.00</env-entry-value>
+
+Used in: env-entry
+-->
+<!ELEMENT env-entry-value (#PCDATA)>
+
+<!--
+The error-code contains an HTTP error code, ex: 404
+
+Used in: error-page
+-->
+<!ELEMENT error-code (#PCDATA)>
+
+<!--
+The error-page element contains a mapping between an error code
+or exception type to the path of a resource in the web application
+
+Used in: web-app
+-->
+<!ELEMENT error-page ((error-code | exception-type), location)>
+
+<!--
+The exception type contains a fully qualified class name of a
+Java exception type.
+
+Used in: error-page
+-->
+<!ELEMENT exception-type (#PCDATA)>
+
+<!--
+The extension element contains a string describing an
+extension. example: "txt"
+
+Used in: mime-mapping
+-->
+<!ELEMENT extension (#PCDATA)>
+
+<!--
+Declares a filter in the web application. The filter is mapped to
+either a servlet or a URL pattern in the filter-mapping element, using
+the filter-name value to reference. Filters can access the
+initialization parameters declared in the deployment descriptor at
+runtime via the FilterConfig interface.
+
+Used in: web-app
+-->
+<!ELEMENT filter (icon?, filter-name, display-name?, description?,
+filter-class, init-param*)>
+
+<!--
+The fully qualified classname of the filter.
+
+Used in: filter
+-->
+<!ELEMENT filter-class (#PCDATA)>
+
+<!--
+Declaration of the filter mappings in this web application. The
+container uses the filter-mapping declarations to decide which filters
+to apply to a request, and in what order. The container matches the
+request URI to a Servlet in the normal way. To determine which filters
+to apply it matches filter-mapping declarations either on servlet-name,
+or on url-pattern for each filter-mapping element, depending on which
+style is used. The order in which filters are invoked is the order in
+which filter-mapping declarations that match a request URI for a
+servlet appear in the list of filter-mapping elements.The filter-name
+value must be the value of the <filter-name> sub-elements of one of the
+<filter> declarations in the deployment descriptor.
+
+Used in: web-app
+-->
+<!ELEMENT filter-mapping (filter-name, (url-pattern | servlet-name))>
+
+<!--
+The logical name of the filter. This name is used to map the filter.
+Each filter name is unique within the web application.
+
+Used in: filter, filter-mapping
+-->
+<!ELEMENT filter-name (#PCDATA)>
+
+<!--
+The form-error-page element defines the location in the web app
+where the error page that is displayed when login is not successful
+can be found. The path begins with a leading / and is interpreted
+relative to the root of the WAR.
+
+Used in: form-login-config
+-->
+<!ELEMENT form-error-page (#PCDATA)>
+
+<!--
+The form-login-config element specifies the login and error pages
+that should be used in form based login. If form based authentication
+is not used, these elements are ignored.
+
+Used in: login-config
+-->
+<!ELEMENT form-login-config (form-login-page, form-error-page)>
+
+<!--
+The form-login-page element defines the location in the web app
+where the page that can be used for login can be found. The path
+begins with a leading / and is interpreted relative to the root of the WAR.
+
+Used in: form-login-config
+-->
+<!ELEMENT form-login-page (#PCDATA)>
+
+<!--
+The home element contains the fully-qualified name of the enterprise
+bean's home interface.
+
+Used in: ejb-ref
+
+Example:
+
+<home>com.aardvark.payroll.PayrollHome</home>
+-->
+<!ELEMENT home (#PCDATA)>
+
+<!--
+The http-method contains an HTTP method (GET | POST |...).
+
+Used in: web-resource-collection
+-->
+<!ELEMENT http-method (#PCDATA)>
+
+<!--
+The icon element contains small-icon and large-icon elements that
+specify the file names for small and a large GIF or JPEG icon images
+used to represent the parent element in a GUI tool.
+
+Used in: filter, servlet, web-app
+-->
+<!ELEMENT icon (small-icon?, large-icon?)>
+
+<!--
+The init-param element contains a name/value pair as an
+initialization param of the servlet
+
+Used in: filter, servlet
+-->
+<!ELEMENT init-param (param-name, param-value, description?)>
+
+<!--
+The jsp-file element contains the full path to a JSP file within
+the web application beginning with a `/'.
+
+Used in: servlet
+-->
+<!ELEMENT jsp-file (#PCDATA)>
+
+<!--
+The large-icon element contains the name of a file
+containing a large (32 x 32) icon image. The file
+name is a relative path within the web application's
+war file.
+
+The image may be either in the JPEG or GIF format.
+The icon can be used by tools.
+
+Used in: icon
+
+Example:
+
+<large-icon>employee-service-icon32x32.jpg</large-icon>
+-->
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+The listener element indicates the deployment properties for a web
+application listener bean.
+
+Used in: web-app
+-->
+<!ELEMENT listener (listener-class)>
+
+<!--
+The listener-class element declares a class in the application must be
+registered as a web application listener bean. The value is the fully qualified classname of the listener class.
+
+
+Used in: listener
+-->
+<!ELEMENT listener-class (#PCDATA)>
+
+<!--
+The load-on-startup element indicates that this servlet should be
+loaded (instantiated and have its init() called) on the startup
+of the web application. The optional contents of
+these element must be an integer indicating the order in which
+the servlet should be loaded. If the value is a negative integer,
+or the element is not present, the container is free to load the
+servlet whenever it chooses. If the value is a positive integer
+or 0, the container must load and initialize the servlet as the
+application is deployed. The container must guarantee that
+servlets marked with lower integers are loaded before servlets
+marked with higher integers. The container may choose the order
+of loading of servlets with the same load-on-start-up value.
+
+Used in: servlet
+-->
+<!ELEMENT load-on-startup (#PCDATA)>
+
+<!--
+
+The local element contains the fully-qualified name of the
+enterprise bean's local interface.
+
+Used in: ejb-local-ref
+
+-->
+<!ELEMENT local (#PCDATA)>
+
+<!--
+
+The local-home element contains the fully-qualified name of the
+enterprise bean's local home interface.
+
+Used in: ejb-local-ref
+-->
+<!ELEMENT local-home (#PCDATA)>
+
+<!--
+The location element contains the location of the resource in the web
+application relative to the root of the web application. The value of
+the location must have a leading `/'.
+
+Used in: error-page
+-->
+<!ELEMENT location (#PCDATA)>
+
+<!--
+The login-config element is used to configure the authentication
+method that should be used, the realm name that should be used for
+this application, and the attributes that are needed by the form login
+mechanism.
+
+Used in: web-app
+-->
+<!ELEMENT login-config (auth-method?, realm-name?, form-login-config?)>
+
+<!--
+The mime-mapping element defines a mapping between an extension
+and a mime type.
+
+Used in: web-app
+-->
+<!ELEMENT mime-mapping (extension, mime-type)>
+
+<!--
+The mime-type element contains a defined mime type. example:
+"text/plain"
+
+Used in: mime-mapping
+-->
+<!ELEMENT mime-type (#PCDATA)>
+
+<!--
+The param-name element contains the name of a parameter. Each parameter
+name must be unique in the web application.
+
+
+Used in: context-param, init-param
+-->
+<!ELEMENT param-name (#PCDATA)>
+
+<!--
+The param-value element contains the value of a parameter.
+
+Used in: context-param, init-param
+-->
+<!ELEMENT param-value (#PCDATA)>
+
+<!--
+The realm name element specifies the realm name to use in HTTP
+Basic authorization.
+
+Used in: login-config
+-->
+<!ELEMENT realm-name (#PCDATA)>
+
+<!--
+The remote element contains the fully-qualified name of the enterprise
+bean's remote interface.
+
+Used in: ejb-ref
+
+Example:
+
+<remote>com.wombat.empl.EmployeeService</remote>
+-->
+<!ELEMENT remote (#PCDATA)>
+
+<!--
+The res-auth element specifies whether the web application code signs
+on programmatically to the resource manager, or whether the Container
+will sign on to the resource manager on behalf of the web application. In the
+latter case, the Container uses information that is supplied by the
+Deployer.
+
+The value of this element must be one of the two following:
+
+ <res-auth>Application</res-auth>
+ <res-auth>Container</res-auth>
+
+Used in: resource-ref
+-->
+<!ELEMENT res-auth (#PCDATA)>
+
+<!--
+The res-ref-name element specifies the name of a resource manager
+connection factory reference. The name is a JNDI name relative to the
+java:comp/env context. The name must be unique within a web application.
+
+Used in: resource-ref
+-->
+<!ELEMENT res-ref-name (#PCDATA)>
+
+<!--
+The res-sharing-scope element specifies whether connections obtained
+through the given resource manager connection factory reference can be
+shared. The value of this element, if specified, must be one of the
+two following:
+
+ <res-sharing-scope>Shareable</res-sharing-scope>
+ <res-sharing-scope>Unshareable</res-sharing-scope>
+
+The default value is Shareable.
+
+Used in: resource-ref
+-->
+<!ELEMENT res-sharing-scope (#PCDATA)>
+
+<!--
+The res-type element specifies the type of the data source. The type
+is specified by the fully qualified Java language class or interface
+expected to be implemented by the data source.
+
+Used in: resource-ref
+-->
+<!ELEMENT res-type (#PCDATA)>
+
+<!--
+The resource-env-ref element contains a declaration of a web application's
+reference to an administered object associated with a resource
+in the web application's environment. It consists of an optional
+description, the resource environment reference name, and an
+indication of the resource environment reference type expected by
+the web application code.
+
+Used in: web-app
+
+Example:
+
+<resource-env-ref>
+ <resource-env-ref-name>jms/StockQueue</resource-env-ref-name>
+ <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
+</resource-env-ref>
+-->
+<!ELEMENT resource-env-ref (description?, resource-env-ref-name,
+ resource-env-ref-type)>
+
+<!--
+The resource-env-ref-name element specifies the name of a resource
+environment reference; its value is the environment entry name used in
+the web application code. The name is a JNDI name relative to the
+java:comp/env context and must be unique within a web application.
+
+Used in: resource-env-ref
+-->
+<!ELEMENT resource-env-ref-name (#PCDATA)>
+
+<!--
+The resource-env-ref-type element specifies the type of a resource
+environment reference. It is the fully qualified name of a Java
+language class or interface.
+
+Used in: resource-env-ref
+-->
+<!ELEMENT resource-env-ref-type (#PCDATA)>
+
+<!--
+The resource-ref element contains a declaration of a web application's
+reference to an external resource. It consists of an optional
+description, the resource manager connection factory reference name,
+the indication of the resource manager connection factory type
+expected by the web application code, the type of authentication
+(Application or Container), and an optional specification of the
+shareability of connections obtained from the resource (Shareable or
+Unshareable).
+
+Used in: web-app
+
+Example:
+
+ <resource-ref>
+ <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
+ <res-type>javax.sql.DataSource</res-type>
+ <res-auth>Container</res-auth>
+ <res-sharing-scope>Shareable</res-sharing-scope>
+ </resource-ref>
+-->
+<!ELEMENT resource-ref (description?, res-ref-name, res-type, res-auth,
+ res-sharing-scope?)>
+
+<!--
+The role-link element is a reference to a defined security role. The
+role-link element must contain the name of one of the security roles
+defined in the security-role elements.
+
+Used in: security-role-ref
+-->
+<!ELEMENT role-link (#PCDATA)>
+
+<!--
+The role-name element contains the name of a security role.
+
+The name must conform to the lexical rules for an NMTOKEN.
+
+Used in: auth-constraint, run-as, security-role, security-role-ref
+-->
+<!ELEMENT role-name (#PCDATA)>
+
+<!--
+The run-as element specifies the run-as identity to be used for the
+execution of the web application. It contains an optional description, and
+the name of a security role.
+
+Used in: servlet
+-->
+<!ELEMENT run-as (description?, role-name)>
+
+<!--
+The security-constraint element is used to associate security
+constraints with one or more web resource collections
+
+Used in: web-app
+-->
+<!ELEMENT security-constraint (display-name?, web-resource-collection+,
+auth-constraint?, user-data-constraint?)>
+
+<!--
+The security-role element contains the definition of a security
+role. The definition consists of an optional description of the
+security role, and the security role name.
+
+Used in: web-app
+
+Example:
+
+ <security-role>
+ <description>
+ This role includes all employees who are authorized
+ to access the employee service application.
+ </description>
+ <role-name>employee</role-name>
+ </security-role>
+-->
+<!ELEMENT security-role (description?, role-name)>
+
+<!--
+The security-role-ref element contains the declaration of a security
+role reference in the web application's code. The declaration consists
+of an optional description, the security role name used in the code,
+and an optional link to a security role. If the security role is not
+specified, the Deployer must choose an appropriate security role.
+
+The value of the role-name element must be the String used as the
+parameter to the EJBContext.isCallerInRole(String roleName) method
+or the HttpServletRequest.isUserInRole(String role) method.
+
+Used in: servlet
+
+-->
+<!ELEMENT security-role-ref (description?, role-name, role-link?)>
+
+<!--
+The servlet element contains the declarative data of a
+servlet. If a jsp-file is specified and the load-on-startup element is
+present, then the JSP should be precompiled and loaded.
+
+Used in: web-app
+-->
+<!ELEMENT servlet (icon?, servlet-name, display-name?, description?,
+(servlet-class|jsp-file), init-param*, load-on-startup?, run-as?, security-role-ref*)>
+
+<!--
+The servlet-class element contains the fully qualified class name
+of the servlet.
+
+Used in: servlet
+-->
+<!ELEMENT servlet-class (#PCDATA)>
+
+<!--
+The servlet-mapping element defines a mapping between a servlet
+and a url pattern
+
+Used in: web-app
+-->
+<!ELEMENT servlet-mapping (servlet-name, url-pattern)>
+
+<!--
+The servlet-name element contains the canonical name of the
+servlet. Each servlet name is unique within the web application.
+
+Used in: filter-mapping, servlet, servlet-mapping
+-->
+<!ELEMENT servlet-name (#PCDATA)>
+
+<!--
+The session-config element defines the session parameters for
+this web application.
+
+Used in: web-app
+-->
+<!ELEMENT session-config (session-timeout?)>
+
+<!--
+The session-timeout element defines the default session timeout
+interval for all sessions created in this web application. The
+specified timeout must be expressed in a whole number of minutes.
+If the timeout is 0 or less, the container ensures the default
+behaviour of sessions is never to time out.
+
+Used in: session-config
+-->
+<!ELEMENT session-timeout (#PCDATA)>
+
+<!--
+The small-icon element contains the name of a file
+containing a small (16 x 16) icon image. The file
+name is a relative path within the web application's
+war file.
+
+The image may be either in the JPEG or GIF format.
+The icon can be used by tools.
+
+Used in: icon
+
+Example:
+
+<small-icon>employee-service-icon16x16.jpg</small-icon>
+-->
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+The taglib element is used to describe a JSP tag library.
+
+Used in: web-app
+-->
+<!ELEMENT taglib (taglib-uri, taglib-location)>
+
+<!--
+the taglib-location element contains the location (as a resource
+relative to the root of the web application) where to find the Tag
+Libary Description file for the tag library.
+
+Used in: taglib
+-->
+<!ELEMENT taglib-location (#PCDATA)>
+
+<!--
+The taglib-uri element describes a URI, relative to the location
+of the web.xml document, identifying a Tag Library used in the Web
+Application.
+
+Used in: taglib
+-->
+<!ELEMENT taglib-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: user-data-constraint
+-->
+<!ELEMENT transport-guarantee (#PCDATA)>
+
+<!--
+The url-pattern element contains the url pattern of the mapping. Must
+follow the rules specified in Section 11.2 of the Servlet API
+Specification.
+
+Used in: filter-mapping, servlet-mapping, web-resource-collection
+-->
+<!ELEMENT url-pattern (#PCDATA)>
+
+<!--
+The user-data-constraint element is used to indicate how data
+communicated between the client and container should be protected.
+
+Used in: security-constraint
+-->
+<!ELEMENT user-data-constraint (description?, transport-guarantee)>
+
+<!--
+The web-resource-collection element is used to identify a subset
+of the resources and HTTP methods on those resources within a web
+application to which a security constraint applies. If no HTTP methods
+are specified, then the security constraint applies to all HTTP
+methods.
+
+Used in: security-constraint
+-->
+<!ELEMENT web-resource-collection (web-resource-name, description?,
+url-pattern*, http-method*)>
+
+<!--
+The web-resource-name contains the name of this web resource
+collection.
+
+Used in: web-resource-collection
+-->
+<!ELEMENT web-resource-name (#PCDATA)>
+
+<!--
+The welcome-file element contains file name to use as a default
+welcome file, such as index.html
+
+Used in: welcome-file-list
+-->
+<!ELEMENT welcome-file (#PCDATA)>
+
+<!--
+The welcome-file-list contains an ordered list of welcome files
+elements.
+
+Used in: web-app
+-->
+<!ELEMENT welcome-file-list (welcome-file+)>
+
+<!--
+The ID mechanism is to allow tools that produce additional deployment
+information (i.e., information beyond the standard deployment
+descriptor information) to store the non-standard information in a
+separate file, and easily refer from these tool-specific files to the
+information in the standard deployment descriptor.
+
+Tools are not allowed to add the non-standard information into the
+standard deployment descriptor.
+-->
+
+<!ATTLIST auth-constraint id ID #IMPLIED>
+<!ATTLIST auth-method id ID #IMPLIED>
+<!ATTLIST context-param id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST distributable id ID #IMPLIED>
+<!ATTLIST ejb-link id ID #IMPLIED>
+<!ATTLIST ejb-local-ref id ID #IMPLIED>
+<!ATTLIST ejb-ref id ID #IMPLIED>
+<!ATTLIST ejb-ref-name id ID #IMPLIED>
+<!ATTLIST ejb-ref-type id ID #IMPLIED>
+<!ATTLIST env-entry id ID #IMPLIED>
+<!ATTLIST env-entry-name id ID #IMPLIED>
+<!ATTLIST env-entry-type id ID #IMPLIED>
+<!ATTLIST env-entry-value id ID #IMPLIED>
+<!ATTLIST error-code id ID #IMPLIED>
+<!ATTLIST error-page id ID #IMPLIED>
+<!ATTLIST exception-type id ID #IMPLIED>
+<!ATTLIST extension id ID #IMPLIED>
+<!ATTLIST filter id ID #IMPLIED>
+<!ATTLIST filter-class id ID #IMPLIED>
+<!ATTLIST filter-mapping id ID #IMPLIED>
+<!ATTLIST filter-name id ID #IMPLIED>
+<!ATTLIST form-error-page id ID #IMPLIED>
+<!ATTLIST form-login-config id ID #IMPLIED>
+<!ATTLIST form-login-page id ID #IMPLIED>
+<!ATTLIST home id ID #IMPLIED>
+<!ATTLIST http-method id ID #IMPLIED>
+<!ATTLIST icon id ID #IMPLIED>
+<!ATTLIST init-param id ID #IMPLIED>
+<!ATTLIST jsp-file id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST listener id ID #IMPLIED>
+<!ATTLIST listener-class id ID #IMPLIED>
+<!ATTLIST load-on-startup id ID #IMPLIED>
+<!ATTLIST local id ID #IMPLIED>
+<!ATTLIST local-home id ID #IMPLIED>
+<!ATTLIST location id ID #IMPLIED>
+<!ATTLIST login-config id ID #IMPLIED>
+<!ATTLIST mime-mapping id ID #IMPLIED>
+<!ATTLIST mime-type id ID #IMPLIED>
+<!ATTLIST param-name id ID #IMPLIED>
+<!ATTLIST param-value id ID #IMPLIED>
+<!ATTLIST realm-name id ID #IMPLIED>
+<!ATTLIST remote id ID #IMPLIED>
+<!ATTLIST res-auth id ID #IMPLIED>
+<!ATTLIST res-ref-name id ID #IMPLIED>
+<!ATTLIST res-sharing-scope id ID #IMPLIED>
+<!ATTLIST res-type id ID #IMPLIED>
+<!ATTLIST resource-env-ref id ID #IMPLIED>
+<!ATTLIST resource-env-ref-name id ID #IMPLIED>
+<!ATTLIST resource-env-ref-type id ID #IMPLIED>
+<!ATTLIST resource-ref id ID #IMPLIED>
+<!ATTLIST role-link id ID #IMPLIED>
+<!ATTLIST role-name id ID #IMPLIED>
+<!ATTLIST run-as id ID #IMPLIED>
+<!ATTLIST security-constraint id ID #IMPLIED>
+<!ATTLIST security-role id ID #IMPLIED>
+<!ATTLIST security-role-ref id ID #IMPLIED>
+<!ATTLIST servlet id ID #IMPLIED>
+<!ATTLIST servlet-class id ID #IMPLIED>
+<!ATTLIST servlet-mapping id ID #IMPLIED>
+<!ATTLIST servlet-name id ID #IMPLIED>
+<!ATTLIST session-config id ID #IMPLIED>
+<!ATTLIST session-timeout id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
+<!ATTLIST taglib id ID #IMPLIED>
+<!ATTLIST taglib-location id ID #IMPLIED>
+<!ATTLIST taglib-uri id ID #IMPLIED>
+<!ATTLIST transport-guarantee id ID #IMPLIED>
+<!ATTLIST url-pattern id ID #IMPLIED>
+<!ATTLIST user-data-constraint id ID #IMPLIED>
+<!ATTLIST web-app id ID #IMPLIED>
+<!ATTLIST web-resource-collection id ID #IMPLIED>
+<!ATTLIST web-resource-name id ID #IMPLIED>
+<!ATTLIST welcome-file id ID #IMPLIED>
+<!ATTLIST welcome-file-list id ID #IMPLIED>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-facesconfig_1_0.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-facesconfig_1_0.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-facesconfig_1_0.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,874 @@
+<!--
+ DTD for the JavaServer Faces Application Configuration File (Version 1.0)
+
+ To support validation of your configuration file(s), include the following
+ DOCTYPE element at the beginning (after the "xml" declaration):
+
+ <!DOCTYPE faces-config PUBLIC
+ "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN"
+ "http://java.sun.com/dtd/web-facesconfig_1_0.dtd">
+
+ $Id: web-facesconfig_1_0.dtd,v 1.33 2006/03/27 17:36:05 rogerk Exp $
+
+-->
+
+
+<!-- ==================== Defined Types =================================== -->
+
+
+<!--
+ An "Action" is a String that represents a method binding
+ expression that points at a method with no arguments that returns a
+ String. It must be bracketed with "#{}", for example,
+ "#{cardemo.buyCar}".
+-->
+<!ENTITY % Action "CDATA">
+
+
+<!--
+ A "ClassName" is the fully qualified name of a Java class that is
+ instantiated to provide the functionality of the enclosing element.
+-->
+<!ENTITY % ClassName "CDATA">
+
+
+<!--
+ An "Identifier" is a string of characters that conforms to the variable
+ naming conventions of the Java programming language (JLS Section ?.?.?).
+-->
+<!ENTITY % Identifier "CDATA">
+
+
+<!--
+ A "JavaType" is either the fully qualified name of a Java class that is
+ instantiated to provide the functionality of the enclosing element, or
+ the name of a Java primitive type (such as int or char). The class name
+ or primitive type may optionally be followed by "[]" to indicate that
+ the underlying data must be an array, rather than a scalar variable.
+-->
+<!ENTITY % JavaType "CDATA">
+
+
+<!--
+ A "Language" is a lower case two-letter code for a language as defined
+ by ISL-639.
+-->
+<!ENTITY % Language "CDATA">
+
+
+<!--
+ A "ResourcePath" is the relative or absolute path to a resource file
+ (such as a logo image).
+-->
+<!ENTITY % ResourcePath "CDATA">
+
+
+<!--
+ A "Scope" is the well-known name of a scope in which managed beans may
+ optionally be defined to be created in.
+-->
+<!ENTITY % Scope "(request|session|application)">
+
+
+
+<!--
+ A "ScopeOrNone" element defines the legal values for the
+ <managed-bean-scope> element's body content, which includes
+ all of the scopes respresented by the "Scope" type, plus the
+ "none" value indicating that a created bean should not be
+ stored into any scope.
+-->
+<!ENTITY % ScopeOrNone "(request|session|application|none)">
+
+
+<!--
+ A "ViewIdPattern" is a pattern for matching view identifiers in
+ order to determine whether a particular navigation rule should be
+ fired. It must contain one of the following values:
+
+ - The exact match for a view identifier that is recognized
+ by the the ViewHandler implementation being used (such as
+ "/index.jsp" if you are using the default ViewHandler).
+
+ - A proper prefix of a view identifier, plus a trailing "*"
+ character. This pattern indicates that all view identifiers that
+ match the portion of the pattern up to the asterisk will match the
+ surrounding rule. When more than one match exists, the match with
+ the longest pattern is selected.
+
+ - An "*" character, which means that this pattern applies to all
+ view identifiers.
+-->
+<!ENTITY % ViewIdPattern "CDATA">
+
+
+<!-- ==================== Top Level Elements ============================== -->
+
+
+<!--
+ The "faces-config" element is the root of the configuration information
+ hierarchy, and contains nested elements for all of the other configuration
+ settings.
+-->
+<!ELEMENT faces-config ((application|factory|component|converter|managed-bean|navigation-rule|referenced-bean|render-kit|lifecycle|validator)*)>
+<!ATTLIST faces-config
+ xmlns CDATA #FIXED "http://java.sun.com/JSF/Configuration">
+
+
+
+<!-- ==================== Definition Elements ============================= -->
+
+
+<!--
+ The "application" element provides a mechanism to define the various
+ per-application-singleton implementation artifacts for a particular web
+ application that is utilizing JavaServer Faces. For nested elements
+ that are not specified, the JSF implementation must provide a suitable
+ default.
+-->
+<!ELEMENT application ((action-listener|default-render-kit-id|message-bundle|navigation-handler|view-handler|state-manager|property-resolver|variable-resolver|locale-config)*)>
+
+
+<!--
+ The "factory" element provides a mechanism to define the various
+ Factories that comprise parts of the implementation of JavaServer
+ Faces. For nested elements that are not specified, the JSF
+ implementation must provide a suitable default.
+-->
+<!ELEMENT factory ((application-factory|faces-context-factory|lifecycle-factory|render-kit-factory)*)>
+
+
+<!--
+ The "attribute" element represents a named, typed, value associated with
+ the parent UIComponent via the generic attributes mechanism.
+
+ Attribute names must be unique within the scope of the parent (or related)
+ component.
+-->
+<!ELEMENT attribute (description*, display-name*, icon*, attribute-name, attribute-class, default-value?, suggested-value?, attribute-extension*)>
+
+<!--
+ Extension element for attribute. May contain implementation
+ specific content.
+-->
+<!ELEMENT attribute-extension ANY>
+
+
+<!--
+ The "component" element represents a concrete UIComponent implementation
+ class that should be registered under the specified type identifier,
+ along with its associated properties and attributes. Component types must
+ be unique within the entire web application.
+
+ Nested "attribute" elements identify generic attributes that are recognized
+ by the implementation logic of this component. Nested "property" elements
+ identify JavaBeans properties of the component class that may be exposed
+ for manipulation via tools.
+-->
+<!ELEMENT component (description*, display-name*, icon*, component-type, component-class, attribute*, property*, component-extension*)>
+
+<!--
+ Extension element for component. May contain implementation
+ specific content.
+-->
+<!ELEMENT component-extension ANY>
+
+
+
+<!--
+ The "converter" element represents a concrete Converter implementation
+ class that should be registered under the specified converter identifier.
+ Converter identifiers must be unique within the entire web application.
+
+ Nested "attribute" elements identify generic attributes that may be
+ configured on the corresponding UIComponent in order to affect the
+ operation of the Converter. Nested "property" elements identify JavaBeans
+ properties of the Converter implementation class that may be configured
+ to affect the operation of the Converter.
+-->
+<!ELEMENT converter (description*, display-name*, icon*, (converter-id | converter-for-class), converter-class, attribute*, property*)>
+
+
+<!--
+ The "icon" element contains "small-icon" and "large-icon" elements that
+ specify the resoruce paths for small and large GIF or JPG icon images
+ used to represent the parent element in a GUI tool.
+-->
+<!ELEMENT icon (small-icon?, large-icon?)>
+<!ATTLIST icon xml:lang %Language; #IMPLIED>
+
+<!--
+ The "lifecycle" element provides a mechanism to specify
+ modifications to the behaviour of the default Lifecycle
+ implementation for this web application.
+-->
+<!ELEMENT lifecycle (phase-listener*)>
+
+<!--
+ The "locale-config" element allows the app developer to declare the
+ supported locales for this application.
+-->
+<!ELEMENT locale-config (default-locale?, supported-locale*)>
+
+<!--
+ The "managed-bean" element represents a JavaBean, of a particular class,
+ that will be dynamically instantiated at runtime (by the default
+ VariableResolver implementation) if it is referenced as the first element
+ of a value binding expression, and no corresponding bean can be
+ identified in any scope. In addition to the creation of the managed bean,
+ and the optional storing of it into the specified scope, the nested
+ managed-property elements can be used to initialize the contents of
+ settable JavaBeans properties of the created instance.
+-->
+<!ELEMENT managed-bean (description*, display-name*, icon*, managed-bean-name, managed-bean-class, managed-bean-scope, (managed-property* | map-entries | list-entries))>
+
+
+<!--
+ The "managed-property" element represents an individual property of a
+ managed bean that will be configured to the specified value (or value set)
+ if the corresponding managed bean is automatically created.
+-->
+<!ELEMENT managed-property (description*, display-name*, icon*, property-name, property-class?, (map-entries|null-value|value|list-entries))>
+
+
+<!--
+ The "map-entry" element reprsents a single key-entry pair that
+ will be added to the computed value of a managed property of type
+ java.util.Map.
+-->
+<!ELEMENT map-entry (key, (null-value|value))>
+
+
+<!--
+ The "map-entries' element represents a set of key-entry pairs that
+ will be added to the computed value of a managed property of type
+ java.util.Map. In addition, the Java class types of the key and entry
+ values may be optionally declared.
+-->
+<!ELEMENT map-entries (key-class?, value-class?, map-entry*)>
+
+
+<!--
+ The base name of a resource bundle representing the message resources
+ for this application. See the JavaDocs for the "java.util.ResourceBundle"
+ class for more information on the syntax of resource bundle names.
+-->
+
+<!ELEMENT message-bundle (#PCDATA)>
+
+
+<!--
+ The "navigation-case" element describes a particular combination of
+ conditions that must match for this case to be executed, and the
+ view id of the component tree that should be selected next.
+-->
+<!ELEMENT navigation-case (description*, display-name*, icon*, from-action?, from-outcome?, to-view-id, redirect?)>
+
+
+<!--
+ The "navigation-rule" element represents an individual decision rule
+ that will be utilized by the default NavigationHandler
+ implementation to make decisions on what view should be displayed
+ next, based on the view id being processed.
+-->
+<!ELEMENT navigation-rule (description*, display-name*, icon*, from-view-id?, navigation-case*)>
+
+
+<!--
+ The "property" element represents a JavaBean property of the Java class
+ represented by our parent element.
+
+ Property names must be unique within the scope of the Java class
+ that is represented by the parent element, and must correspond to
+ property names that will be recognized when performing introspection
+ against that class via java.beans.Introspector.
+-->
+<!ELEMENT property (description*, display-name*, icon*, property-name, property-class, default-value?, suggested-value?, property-extension*)>
+
+<!--
+ Extension element for property. May contain implementation
+ specific content.
+-->
+<!ELEMENT property-extension ANY>
+
+<!--
+ The "referenced-bean" element represents at design time the promise
+ that a Java object of the specified type will exist at runtime in some
+ scope, under the specified key. This can be used by design time tools
+ to construct user interface dialogs based on the properties of the
+ specified class. The presence or absence of a referenced bean
+ element has no impact on the JavaServer Faces runtime environment
+ inside a web application.
+-->
+<!ELEMENT referenced-bean (description*, display-name*, icon*, referenced-bean-name, referenced-bean-class)>
+
+
+<!--
+ The "render-kit" element represents a concrete RenderKit implementation
+ that should be registered under the specified render-kit-id. If no
+ render-kit-id is specified, the identifier of the default RenderKit
+ (RenderKitFactory.DEFAULT_RENDER_KIT) is assumed.
+-->
+<!ELEMENT render-kit (description*, display-name*, icon*, render-kit-id?, render-kit-class?, renderer*)>
+
+
+<!--
+ The "renderer" element represents a concrete Renderer implementation
+ class that should be registered under the specified component family
+ and renderer type identifiers, in the RenderKit associated with the
+ parent "render-kit" element. Combinations of component family and renderer
+ type must be unique within the RenderKit associated with the parent
+ "render-kit" element.
+
+ Nested "attribute" elements identify generic component attributes that
+ are recognized by this renderer.
+-->
+<!ELEMENT renderer (description*, display-name*, icon*, component-family, renderer-type, renderer-class, attribute*, renderer-extension*)>
+
+<!--
+ Extension element for renderer. May contain implementation
+ specific content.
+-->
+<!ELEMENT renderer-extension ANY>
+
+<!--
+ The "validator" element represents a concrete Validator implementation
+ class that should be registered under the specified validator identifier.
+ Validator identifiers must be unique within the entire web application.
+
+ Nested "attribute" elements identify generic attributes that may be
+ configured on the corresponding UIComponent in order to affect the
+ operation of the Validator. Nested "property" elements identify JavaBeans
+ properties of the Validator implementation class that may be configured
+ to affect the operation of the Validator.
+-->
+<!ELEMENT validator (description*, display-name*, icon*, validator-id, validator-class, attribute*, property*)>
+
+
+<!--
+ The "list-entries" element represents a set of initialization
+ elements for a managed property that is a java.util.List or an
+ array. In the former case, the "value-class" element can optionally
+ be used to declare the Java type to which each value should be
+ converted before adding it to the Collection.
+-->
+<!ELEMENT list-entries (value-class?, (null-value|value)*)>
+
+
+<!-- ==================== Subordinate Elements ============================ -->
+
+
+<!--
+ The "action-listener" element contains the fully qualified class name
+ of the concrete ActionListener implementation class that will be called
+ during the Invoke Application phase of the request processing lifecycle.
+ It must be of type "ClassName".
+-->
+<!ELEMENT action-listener (#PCDATA)>
+
+<!--
+ The "application-factory" element contains the fully qualified class
+ name of the concrete ApplicationFactory implementation class that
+ will be called when FactoryFinder.getFactory(APPLICATION_FACTORY) is
+ called. It must be of type "ClassName".
+-->
+<!ELEMENT application-factory (#PCDATA)>
+
+<!--
+ The "attribute-class" element represents the Java type of the value
+ associated with this attribute name. It must be of type "ClassName".
+-->
+<!ELEMENT attribute-class (#PCDATA)>
+
+
+<!--
+ The "attribute-name" element represents the name under which the
+ corresponding value will be stored, in the generic attributes of the
+ UIComponent we are related to.
+-->
+<!ELEMENT attribute-name (#PCDATA)>
+
+
+<!--
+ The "component-class" element represents the fully qualified class name
+ of a concrete UIComponent implementation class. It must be of
+ type "ClassName".
+-->
+<!ELEMENT component-class (#PCDATA)>
+
+
+<!--
+ The "component-family" element represents the component family for
+ which the Renderer represented by the parent "renderer" element will be
+ used.
+-->
+<!ELEMENT component-family (#PCDATA)>
+
+<!--
+ The "component-type" element represents the name under which the
+ corresponding UIComponent class should be registered.
+-->
+<!ELEMENT component-type (#PCDATA)>
+
+
+<!--
+ The "converter-class" element represents the fully qualified class name
+ of a concrete Converter implementation class. It must be of
+ type "ClassName".
+-->
+<!ELEMENT converter-class (#PCDATA)>
+
+
+<!--
+ The "converter-for-class" element represents the fully qualified class name
+ for which a Converter class will be registered. It must be of
+ type "ClassName".
+-->
+<!ELEMENT converter-for-class (#PCDATA)>
+
+
+<!--
+ The "converter-id" element represents the identifier under which the
+ corresponding Converter class should be registered.
+-->
+<!ELEMENT converter-id (#PCDATA)>
+
+<!--
+ The "default-render-kit-id" element allows the application to define
+ a renderkit to be used other than the standard one.
+-->
+<!ELEMENT default-render-kit-id (#PCDATA)>
+
+<!--
+ The "default-locale" element declares the default locale for this
+ application instance. It must be specified as
+ :language:[_:country:[_:variant:]] without the colons, for example
+ "ja_JP_SJIS". The separators between the segments may be '-' or
+ '_'.
+-->
+<!ELEMENT default-locale (#PCDATA)>
+
+<!--
+ The "default-value" contains the value for the property or attribute
+ in which this element resides. This value differs from the
+ "suggested-value" in that the property or attribute must take the
+ value, whereas in "suggested-value" taking the value is optional.
+-->
+<!ELEMENT default-value (#PCDATA)>
+
+<!--
+ The "description" element contains a textual description of the element
+ it is nested in, optionally flagged with a language code using the
+ "xml:lang" attribute.
+-->
+<!ELEMENT description ANY>
+<!ATTLIST description xml:lang %Language; #IMPLIED>
+
+
+<!--
+ The "display-name" element is a short descriptive name describing the
+ entity associated with the element it is nested in, intended to be
+ displayed by tools, and optionally flagged with a language code using
+ the "xml:lang" attribute.
+-->
+<!ELEMENT display-name (#PCDATA)>
+<!ATTLIST display-name xml:lang %Language; #IMPLIED>
+
+<!--
+ The "faces-context-factory" element contains the fully qualified
+ class name of the concrete FacesContextFactory implementation class
+ that will be called when
+ FactoryFinder.getFactory(FACES_CONTEXT_FACTORY) is called. It must
+ be of type "ClassName".
+-->
+<!ELEMENT faces-context-factory (#PCDATA)>
+
+<!--
+ The "from-action" element contains an action reference expression
+ that must have been executed (by the default ActionListener for handling
+ application level events) in order to select this navigation rule. If
+ not specified, this rule will be relevant no matter which action reference
+ was executed (or if no action reference was executed).
+
+ This value must be of type "Action".
+-->
+<!ELEMENT from-action (#PCDATA)>
+
+
+<!--
+ The "from-outcome" element contains a logical outcome string returned
+ by the execution of an application action method selected via an
+ "actionRef" property (or a literal value specified by an "action"
+ property) of a UICommand component. If specified, this rule will be
+ relevant only if the outcome value matches this element's value. If
+ not specified, this rule will be relevant no matter what the outcome
+ value was.
+-->
+<!ELEMENT from-outcome (#PCDATA)>
+
+
+<!--
+ The "from-view-id" element contains the view identifier of the view
+ for which the containing navigation rule is relevant. If no
+ "from-view" element is specified, this rule applies to navigation
+ decisions on all views. If this element is not specified, a value
+ of "*" is assumed, meaning that this navigation rule applies to all
+ views.
+
+ This value must be of type "ViewIdPattern".
+-->
+<!ELEMENT from-view-id (#PCDATA)>
+
+
+<!--
+ The "key" element is the String representation of a map key that
+ will be stored in a managed property of type java.util.Map.
+-->
+<!ELEMENT key (#PCDATA)>
+
+
+<!--
+ The "key-class" element defines the Java type to which each "key"
+ element in a set of "map-entry" elements will be converted to. It
+ must be of type "ClassName". If omitted, "java.lang.String"
+ is assumed.
+-->
+<!ELEMENT key-class (#PCDATA)>
+
+
+<!--
+ The "large-icon" element contains the resource path to a large (32x32)
+ icon image. The image may be in either GIF or JPG format.
+-->
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+ The "lifecycle-factory" element contains the fully qualified class name
+ of the concrete LifecycleFactory implementation class that will be called
+ when FactoryFinder.getFactory(LIFECYCLE_FACTORY) is called. It must be
+ of type "ClassName".
+-->
+<!ELEMENT lifecycle-factory (#PCDATA)>
+
+<!--
+ The "managed-bean-class" element represents the fully qualified class
+ name of the Java class that will be used to instantiate a new instance
+ if creation of the specified managed bean is requested. It must be of
+ type "ClassName".
+
+ The specified class must conform to standard JavaBeans conventions.
+ In particular, it must have a public zero-arguments constructor, and
+ zero or more public property setters.
+-->
+<!ELEMENT managed-bean-class (#PCDATA)>
+
+
+<!--
+ The "managed-bean-name" element represents the attribute name under
+ which a managed bean will be searched for, as well as stored (unless
+ the "managed-bean-scope" value is "none"). It must be of type
+ "Identifier".
+-->
+<!ELEMENT managed-bean-name (#PCDATA)>
+
+
+<!--
+ The "managed-bean-scope" element represents the scope into which a newly
+ created instance of the specified managed bean will be stored (unless
+ the value is "none"). It must be of type "ScopeOrNone".
+-->
+<!ELEMENT managed-bean-scope (#PCDATA)>
+
+<!--
+ The "navigation-handler" element contains the fully qualified class name
+ of the concrete NavigationHandler implementation class that will be called
+ during the Invoke Application phase of the request processing lifecycle,
+ if the default ActionListener (provided by the JSF implementation) is used.
+ It must be of type "ClassName".
+-->
+<!ELEMENT navigation-handler (#PCDATA)>
+
+<!--
+The "phase-listener" element contains the fully qualified class
+name of the concrete PhaseListener implementation class that will be
+registered on the Lifecycle. It must be of type "ClassName".
+-->
+<!ELEMENT phase-listener (#PCDATA)>
+
+<!--
+ The "redirect" element indicates that navigation to the specified
+ "to-view-id" should be accomplished by performing an HTTP redirect
+ rather than the usual ViewHandler mechanisms.
+-->
+<!ELEMENT redirect EMPTY>
+
+<!--
+ The "suggested-value" contains the value for the property or
+ attribute in which this element resides. This value is advisory
+ only and is intended for tools to use when populating pallettes.
+-->
+<!ELEMENT suggested-value (#PCDATA)>
+
+
+<!--
+
+ The "view-handler" element contains the fully qualified class name
+ of the concrete ViewHandler implementation class that will be called
+ during the Restore View and Render Response phases of the request
+ processing lifecycle. The faces implementation must provide a
+ default implementation of this class
+-->
+<!ELEMENT view-handler (#PCDATA)>
+
+<!--
+
+ The "state-manager" element contains the fully qualified class name
+ of the concrete StateManager implementation class that will be called
+ during the Restore View and Render Response phases of the request
+ processing lifecycle. The faces implementation must provide a
+ default implementation of this class
+-->
+<!ELEMENT state-manager (#PCDATA)>
+
+<!--
+ The "null-value" element indicates that the managed property in which we
+ are nested will be explicitly set to null if our managed bean is
+ automatically created. This is different from omitting the managed
+ property element entirely, which will cause no property setter to be
+ called for this property.
+
+ The "null-value" element can only be used when the associated
+ "property-class" identifies a Java class, not a Java primitive.
+-->
+<!ELEMENT null-value EMPTY>
+
+
+<!--
+ The "property-class" element represents the Java type of the value
+ associated with this property name. It must be of type "JavaType".
+ If not specified, it can be inferred from existing classes; however,
+ this element should be specified if the configuration file is going
+ to be the source for generating the corresponding classes.
+-->
+<!ELEMENT property-class (#PCDATA)>
+
+
+<!--
+ The "property-name" element represents the JavaBeans property name
+ under which the corresponding value may be stored.
+-->
+<!ELEMENT property-name (#PCDATA)>
+
+
+<!--
+ The "property-resolver" element contains the fully qualified class name
+ of the concrete PropertyResolver implementation class that will be used
+ during the processing of value binding expressions.
+ It must be of type "ClassName".
+-->
+<!ELEMENT property-resolver (#PCDATA)>
+
+
+<!--
+ The "referenced-bean-class" element represents the fully qualified class
+ name of the Java class (either abstract or concrete) or Java interface
+ implemented by the corresponding referenced bean. It must be of type
+ "ClassName".
+-->
+<!ELEMENT referenced-bean-class (#PCDATA)>
+
+
+<!--
+ The "referenced-bean-name" element represents the attribute name under
+ which the corresponding referenced bean may be assumed to be stored,
+ in one of the scopes defined by the "Scope" type. It must be of type
+ "Identifier".
+-->
+<!ELEMENT referenced-bean-name (#PCDATA)>
+
+
+<!--
+ The "render-kit-id" element represents an identifier for the
+ RenderKit represented by the parent "render-kit" element.
+-->
+<!ELEMENT render-kit-id (#PCDATA)>
+
+
+<!--
+ The "render-kit-class" element represents the fully qualified class name
+ of a concrete RenderKit implementation class. It must be of
+ type "ClassName".
+-->
+<!ELEMENT render-kit-class (#PCDATA)>
+
+
+<!--
+ The "renderer-class" element represents the fully qualified class name
+ of a concrete Renderer implementation class. It must be of
+ type "ClassName".
+-->
+<!ELEMENT renderer-class (#PCDATA)>
+
+<!--
+ The "render-kit-factory" element contains the fully qualified class name
+ of the concrete RenderKitFactory implementation class that will be called
+ when FactoryFinder.getFactory(RENDER_KIT_FACTORY) is called. It must be
+ of type "ClassName".
+-->
+<!ELEMENT render-kit-factory (#PCDATA)>
+
+<!--
+ The "renderer-type" element represents a renderer type identifier for the
+ Renderer represented by the parent "renderer" element.
+-->
+<!ELEMENT renderer-type (#PCDATA)>
+
+<!--
+ The "small-icon" element contains the resource path to a large (16x16)
+ icon image. The image may be in either GIF or JPG format.
+-->
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+ The "supported-locale" element allows authors to declare which
+ locales are supported in this application instance.
+
+ It must be specified as :language:[_:country:[_:variant:]] without
+ the colons, for example "ja_JP_SJIS". The separators between the
+ segments may be '-' or '_'.
+-->
+<!ELEMENT supported-locale (#PCDATA)>
+
+<!--
+ The "to-view" element contains the view identifier of the next view
+ that should be displayed if this navigation rule is matched. It
+ must be of type "ViewId".
+-->
+<!ELEMENT to-view-id (#PCDATA)>
+
+
+<!--
+ The "validator-class" element represents the fully qualified class name
+ of a concrete Validator implementation class. It must be of
+ type "ClassName".
+-->
+<!ELEMENT validator-class (#PCDATA)>
+
+
+<!--
+ The "validator-id" element represents the identifier under which the
+ corresponding Validator class should be registered.
+-->
+<!ELEMENT validator-id (#PCDATA)>
+
+
+<!--
+ The "value" element is the String representation of a literal
+ value to which a scalar managed property will be set, or a value
+ binding expression ("#{...}") that will be used to calculate the
+ required value. It will be converted as specified for the actual
+ property type.
+-->
+<!ELEMENT value (#PCDATA)>
+
+
+<!--
+ The "value-class" element defines the Java type to which each
+ "value" element's value will be converted to, prior to adding it to
+ the "list-entries" list for a managed property that is a
+ java.util.List, or a "map-entries" map for a managed property that
+ is a java.util.Map. It must be of type "ClassName". If omitted,
+ "java.lang.String" is assumed.
+-->
+<!ELEMENT value-class (#PCDATA)>
+
+<!--
+ The "variable-resolver" element contains the fully qualified class name
+ of the concrete VariableResolver implementation class that will be used
+ during the processing of value binding expressions.
+ It must be of type "ClassName".
+-->
+<!ELEMENT variable-resolver (#PCDATA)>
+
+
+<!-- ============================ Identifier Attributes ==================== -->
+
+
+<!ATTLIST action-listener id ID #IMPLIED>
+<!ATTLIST application id ID #IMPLIED>
+<!ATTLIST application-factory id ID #IMPLIED>
+<!ATTLIST attribute id ID #IMPLIED>
+<!ATTLIST attribute-class id ID #IMPLIED>
+<!ATTLIST attribute-extension id ID #IMPLIED>
+<!ATTLIST attribute-name id ID #IMPLIED>
+<!ATTLIST component id ID #IMPLIED>
+<!ATTLIST component-class id ID #IMPLIED>
+<!ATTLIST component-extension id ID #IMPLIED>
+<!ATTLIST component-family id ID #IMPLIED>
+<!ATTLIST component-type id ID #IMPLIED>
+<!ATTLIST converter id ID #IMPLIED>
+<!ATTLIST converter-class id ID #IMPLIED>
+<!ATTLIST converter-for-class id ID #IMPLIED>
+<!ATTLIST converter-id id ID #IMPLIED>
+<!ATTLIST default-locale id ID #IMPLIED>
+<!ATTLIST default-render-kit-id id ID #IMPLIED>
+<!ATTLIST default-value id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST faces-config id ID #IMPLIED>
+<!ATTLIST faces-context-factory id ID #IMPLIED>
+<!ATTLIST factory id ID #IMPLIED>
+<!ATTLIST from-action id ID #IMPLIED>
+<!ATTLIST from-outcome id ID #IMPLIED>
+<!ATTLIST from-view-id id ID #IMPLIED>
+<!ATTLIST icon id ID #IMPLIED>
+<!ATTLIST key id ID #IMPLIED>
+<!ATTLIST key-class id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST lifecycle id ID #IMPLIED>
+<!ATTLIST lifecycle-factory id ID #IMPLIED>
+<!ATTLIST list-entries id ID #IMPLIED>
+<!ATTLIST locale-config id ID #IMPLIED>
+<!ATTLIST managed-bean id ID #IMPLIED>
+<!ATTLIST managed-bean-class id ID #IMPLIED>
+<!ATTLIST managed-bean-name id ID #IMPLIED>
+<!ATTLIST managed-bean-scope id ID #IMPLIED>
+<!ATTLIST managed-property id ID #IMPLIED>
+<!ATTLIST map-entries id ID #IMPLIED>
+<!ATTLIST map-entry id ID #IMPLIED>
+<!ATTLIST message-bundle id ID #IMPLIED>
+<!ATTLIST navigation-case id ID #IMPLIED>
+<!ATTLIST navigation-handler id ID #IMPLIED>
+<!ATTLIST navigation-rule id ID #IMPLIED>
+<!ATTLIST null-value id ID #IMPLIED>
+<!ATTLIST phase-listener id ID #IMPLIED>
+<!ATTLIST property id ID #IMPLIED>
+<!ATTLIST property-class id ID #IMPLIED>
+<!ATTLIST property-extension id ID #IMPLIED>
+<!ATTLIST property-name id ID #IMPLIED>
+<!ATTLIST property-resolver id ID #IMPLIED>
+<!ATTLIST redirect id ID #IMPLIED>
+<!ATTLIST referenced-bean id ID #IMPLIED>
+<!ATTLIST referenced-bean-class id ID #IMPLIED>
+<!ATTLIST referenced-bean-name id ID #IMPLIED>
+<!ATTLIST render-kit id ID #IMPLIED>
+<!ATTLIST render-kit-class id ID #IMPLIED>
+<!ATTLIST render-kit-factory id ID #IMPLIED>
+<!ATTLIST render-kit-id id ID #IMPLIED>
+<!ATTLIST renderer id ID #IMPLIED>
+<!ATTLIST renderer-class id ID #IMPLIED>
+<!ATTLIST renderer-extension id ID #IMPLIED>
+<!ATTLIST renderer-type id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
+<!ATTLIST state-manager id ID #IMPLIED>
+<!ATTLIST suggested-value id ID #IMPLIED>
+<!ATTLIST supported-locale id ID #IMPLIED>
+<!ATTLIST to-view-id id ID #IMPLIED>
+<!ATTLIST validator id ID #IMPLIED>
+<!ATTLIST validator-class id ID #IMPLIED>
+<!ATTLIST validator-id id ID #IMPLIED>
+<!ATTLIST value id ID #IMPLIED>
+<!ATTLIST value-class id ID #IMPLIED>
+<!ATTLIST variable-resolver id ID #IMPLIED>
+<!ATTLIST view-handler id ID #IMPLIED>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-facesconfig_1_1.dtd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-facesconfig_1_1.dtd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/dtd/web-facesconfig_1_1.dtd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,895 @@
+<!--
+ DTD for the JavaServer Faces Application Configuration File (Version 1.1)
+
+ To support validation of your configuration file(s), include the following
+ DOCTYPE element at the beginning (after the "xml" declaration):
+
+ <!DOCTYPE faces-config PUBLIC
+ "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
+ "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
+
+ $Id: web-facesconfig_1_1.dtd,v 1.5 2006/03/27 17:36:06 rogerk Exp $
+
+-->
+
+
+<!-- ==================== Defined Types =================================== -->
+
+
+<!--
+ An "Action" is a String that represents a method binding
+ expression that points at a method with no arguments that returns a
+ String. It must be bracketed with "#{}", for example,
+ "#{cardemo.buyCar}".
+-->
+<!ENTITY % Action "CDATA">
+
+
+<!--
+ A "ClassName" is the fully qualified name of a Java class that is
+ instantiated to provide the functionality of the enclosing element.
+-->
+<!ENTITY % ClassName "CDATA">
+
+
+<!--
+ An "Identifier" is a string of characters that conforms to the variable
+ naming conventions of the Java programming language (JLS Section ?.?.?).
+-->
+<!ENTITY % Identifier "CDATA">
+
+
+<!--
+ A "JavaType" is either the fully qualified name of a Java class that is
+ instantiated to provide the functionality of the enclosing element, or
+ the name of a Java primitive type (such as int or char). The class name
+ or primitive type may optionally be followed by "[]" to indicate that
+ the underlying data must be an array, rather than a scalar variable.
+-->
+<!ENTITY % JavaType "CDATA">
+
+
+<!--
+ A "Language" is a lower case two-letter code for a language as defined
+ by ISL-639.
+-->
+<!ENTITY % Language "CDATA">
+
+
+<!--
+ A "ResourcePath" is the relative or absolute path to a resource file
+ (such as a logo image).
+-->
+<!ENTITY % ResourcePath "CDATA">
+
+
+<!--
+ A "Scope" is the well-known name of a scope in which managed beans may
+ optionally be defined to be created in.
+-->
+<!ENTITY % Scope "(request|session|application)">
+
+
+
+<!--
+ A "ScopeOrNone" element defines the legal values for the
+ <managed-bean-scope> element's body content, which includes
+ all of the scopes respresented by the "Scope" type, plus the
+ "none" value indicating that a created bean should not be
+ stored into any scope.
+-->
+<!ENTITY % ScopeOrNone "(request|session|application|none)">
+
+
+<!--
+ A "ViewIdPattern" is a pattern for matching view identifiers in
+ order to determine whether a particular navigation rule should be
+ fired. It must contain one of the following values:
+
+ - The exact match for a view identifier that is recognized
+ by the the ViewHandler implementation being used (such as
+ "/index.jsp" if you are using the default ViewHandler).
+
+ - A proper prefix of a view identifier, plus a trailing "*"
+ character. This pattern indicates that all view identifiers that
+ match the portion of the pattern up to the asterisk will match the
+ surrounding rule. When more than one match exists, the match with
+ the longest pattern is selected.
+
+ - An "*" character, which means that this pattern applies to all
+ view identifiers.
+-->
+<!ENTITY % ViewIdPattern "CDATA">
+
+
+<!-- ==================== Top Level Elements ============================== -->
+
+
+<!--
+ The "faces-config" element is the root of the configuration information
+ hierarchy, and contains nested elements for all of the other configuration
+ settings.
+-->
+<!ELEMENT faces-config ((application|factory|component|converter|managed-bean|navigation-rule|referenced-bean|render-kit|lifecycle|validator)*)>
+<!ATTLIST faces-config
+ xmlns CDATA #FIXED "http://java.sun.com/JSF/Configuration">
+
+
+
+<!-- ==================== Definition Elements ============================= -->
+
+
+<!--
+ The "application" element provides a mechanism to define the various
+ per-application-singleton implementation artifacts for a particular web
+ application that is utilizing JavaServer Faces. For nested elements
+ that are not specified, the JSF implementation must provide a suitable
+ default.
+-->
+<!ELEMENT application ((action-listener|default-render-kit-id|message-bundle|navigation-handler|view-handler|state-manager|property-resolver|variable-resolver|locale-config)*)>
+
+
+<!--
+ The "factory" element provides a mechanism to define the various
+ Factories that comprise parts of the implementation of JavaServer
+ Faces. For nested elements that are not specified, the JSF
+ implementation must provide a suitable default.
+-->
+<!ELEMENT factory ((application-factory|faces-context-factory|lifecycle-factory|render-kit-factory)*)>
+
+
+<!--
+ The "attribute" element represents a named, typed, value associated with
+ the parent UIComponent via the generic attributes mechanism.
+
+ Attribute names must be unique within the scope of the parent (or related)
+ component.
+-->
+<!ELEMENT attribute (description*, display-name*, icon*, attribute-name, attribute-class, default-value?, suggested-value?, attribute-extension*)>
+
+<!--
+ Extension element for attribute. May contain implementation
+ specific content.
+-->
+<!ELEMENT attribute-extension ANY>
+
+
+<!--
+ The "component" element represents a concrete UIComponent implementation
+ class that should be registered under the specified type identifier,
+ along with its associated properties and attributes. Component types must
+ be unique within the entire web application.
+
+ Nested "attribute" elements identify generic attributes that are recognized
+ by the implementation logic of this component. Nested "property" elements
+ identify JavaBeans properties of the component class that may be exposed
+ for manipulation via tools.
+-->
+<!ELEMENT component (description*, display-name*, icon*, component-type, component-class, facet*, attribute*, property*, component-extension*)>
+
+<!--
+ Extension element for component. May contain implementation
+ specific content.
+-->
+<!ELEMENT component-extension ANY>
+
+<!--
+ Define the name and other design-time information for a facet that is
+ associated with a renderer or a component.
+-->
+
+<!ELEMENT facet (description*, display-name*, icon*, facet-name, facet-extension*)>
+
+<!--
+ Extension element for facet. May contain implementation
+ specific content.
+-->
+<!ELEMENT facet-extension ANY>
+
+<!--
+ The "facet-name" element represents the facet name under which a
+ UIComponent will be added to its parent. It must be of type
+ "Identifier".
+-->
+<!ELEMENT facet-name (#PCDATA)>
+
+<!--
+ The "converter" element represents a concrete Converter implementation
+ class that should be registered under the specified converter identifier.
+ Converter identifiers must be unique within the entire web application.
+
+ Nested "attribute" elements identify generic attributes that may be
+ configured on the corresponding UIComponent in order to affect the
+ operation of the Converter. Nested "property" elements identify JavaBeans
+ properties of the Converter implementation class that may be configured
+ to affect the operation of the Converter.
+-->
+<!ELEMENT converter (description*, display-name*, icon*, (converter-id | converter-for-class), converter-class, attribute*, property*)>
+
+
+<!--
+ The "icon" element contains "small-icon" and "large-icon" elements that
+ specify the resoruce paths for small and large GIF or JPG icon images
+ used to represent the parent element in a GUI tool.
+-->
+<!ELEMENT icon (small-icon?, large-icon?)>
+<!ATTLIST icon xml:lang %Language; #IMPLIED>
+
+<!--
+ The "lifecycle" element provides a mechanism to specify
+ modifications to the behaviour of the default Lifecycle
+ implementation for this web application.
+-->
+<!ELEMENT lifecycle (phase-listener*)>
+
+<!--
+ The "locale-config" element allows the app developer to declare the
+ supported locales for this application.
+-->
+<!ELEMENT locale-config (default-locale?, supported-locale*)>
+
+<!--
+ The "managed-bean" element represents a JavaBean, of a particular class,
+ that will be dynamically instantiated at runtime (by the default
+ VariableResolver implementation) if it is referenced as the first element
+ of a value binding expression, and no corresponding bean can be
+ identified in any scope. In addition to the creation of the managed bean,
+ and the optional storing of it into the specified scope, the nested
+ managed-property elements can be used to initialize the contents of
+ settable JavaBeans properties of the created instance.
+-->
+<!ELEMENT managed-bean (description*, display-name*, icon*, managed-bean-name, managed-bean-class, managed-bean-scope, (managed-property* | map-entries | list-entries))>
+
+
+<!--
+ The "managed-property" element represents an individual property of a
+ managed bean that will be configured to the specified value (or value set)
+ if the corresponding managed bean is automatically created.
+-->
+<!ELEMENT managed-property (description*, display-name*, icon*, property-name, property-class?, (map-entries|null-value|value|list-entries))>
+
+
+<!--
+ The "map-entry" element reprsents a single key-entry pair that
+ will be added to the computed value of a managed property of type
+ java.util.Map.
+-->
+<!ELEMENT map-entry (key, (null-value|value))>
+
+
+<!--
+ The "map-entries' element represents a set of key-entry pairs that
+ will be added to the computed value of a managed property of type
+ java.util.Map. In addition, the Java class types of the key and entry
+ values may be optionally declared.
+-->
+<!ELEMENT map-entries (key-class?, value-class?, map-entry*)>
+
+
+<!--
+ The base name of a resource bundle representing the message resources
+ for this application. See the JavaDocs for the "java.util.ResourceBundle"
+ class for more information on the syntax of resource bundle names.
+-->
+
+<!ELEMENT message-bundle (#PCDATA)>
+
+
+<!--
+ The "navigation-case" element describes a particular combination of
+ conditions that must match for this case to be executed, and the
+ view id of the component tree that should be selected next.
+-->
+<!ELEMENT navigation-case (description*, display-name*, icon*, from-action?, from-outcome?, to-view-id, redirect?)>
+
+
+<!--
+ The "navigation-rule" element represents an individual decision rule
+ that will be utilized by the default NavigationHandler
+ implementation to make decisions on what view should be displayed
+ next, based on the view id being processed.
+-->
+<!ELEMENT navigation-rule (description*, display-name*, icon*, from-view-id?, navigation-case*)>
+
+
+<!--
+ The "property" element represents a JavaBean property of the Java class
+ represented by our parent element.
+
+ Property names must be unique within the scope of the Java class
+ that is represented by the parent element, and must correspond to
+ property names that will be recognized when performing introspection
+ against that class via java.beans.Introspector.
+-->
+<!ELEMENT property (description*, display-name*, icon*, property-name, property-class, default-value?, suggested-value?, property-extension*)>
+
+<!--
+ Extension element for property. May contain implementation
+ specific content.
+-->
+<!ELEMENT property-extension ANY>
+
+<!--
+ The "referenced-bean" element represents at design time the promise
+ that a Java object of the specified type will exist at runtime in some
+ scope, under the specified key. This can be used by design time tools
+ to construct user interface dialogs based on the properties of the
+ specified class. The presence or absence of a referenced bean
+ element has no impact on the JavaServer Faces runtime environment
+ inside a web application.
+-->
+<!ELEMENT referenced-bean (description*, display-name*, icon*, referenced-bean-name, referenced-bean-class)>
+
+
+<!--
+ The "render-kit" element represents a concrete RenderKit implementation
+ that should be registered under the specified render-kit-id. If no
+ render-kit-id is specified, the identifier of the default RenderKit
+ (RenderKitFactory.DEFAULT_RENDER_KIT) is assumed.
+-->
+<!ELEMENT render-kit (description*, display-name*, icon*, render-kit-id?, render-kit-class?, renderer*)>
+
+
+<!--
+ The "renderer" element represents a concrete Renderer implementation
+ class that should be registered under the specified component family
+ and renderer type identifiers, in the RenderKit associated with the
+ parent "render-kit" element. Combinations of component family and renderer
+ type must be unique within the RenderKit associated with the parent
+ "render-kit" element.
+
+ Nested "attribute" elements identify generic component attributes that
+ are recognized by this renderer.
+-->
+<!ELEMENT renderer (description*, display-name*, icon*, component-family, renderer-type, renderer-class, facet*, attribute*, renderer-extension*)>
+
+<!--
+ Extension element for renderer. May contain implementation
+ specific content.
+-->
+<!ELEMENT renderer-extension ANY>
+
+<!--
+ The "validator" element represents a concrete Validator implementation
+ class that should be registered under the specified validator identifier.
+ Validator identifiers must be unique within the entire web application.
+
+ Nested "attribute" elements identify generic attributes that may be
+ configured on the corresponding UIComponent in order to affect the
+ operation of the Validator. Nested "property" elements identify JavaBeans
+ properties of the Validator implementation class that may be configured
+ to affect the operation of the Validator.
+-->
+<!ELEMENT validator (description*, display-name*, icon*, validator-id, validator-class, attribute*, property*)>
+
+
+<!--
+ The "list-entries" element represents a set of initialization
+ elements for a managed property that is a java.util.List or an
+ array. In the former case, the "value-class" element can optionally
+ be used to declare the Java type to which each value should be
+ converted before adding it to the Collection.
+-->
+<!ELEMENT list-entries (value-class?, (null-value|value)*)>
+
+
+<!-- ==================== Subordinate Elements ============================ -->
+
+
+<!--
+ The "action-listener" element contains the fully qualified class name
+ of the concrete ActionListener implementation class that will be called
+ during the Invoke Application phase of the request processing lifecycle.
+ It must be of type "ClassName".
+-->
+<!ELEMENT action-listener (#PCDATA)>
+
+<!--
+ The "application-factory" element contains the fully qualified class
+ name of the concrete ApplicationFactory implementation class that
+ will be called when FactoryFinder.getFactory(APPLICATION_FACTORY) is
+ called. It must be of type "ClassName".
+-->
+<!ELEMENT application-factory (#PCDATA)>
+
+<!--
+ The "attribute-class" element represents the Java type of the value
+ associated with this attribute name. It must be of type "ClassName".
+-->
+<!ELEMENT attribute-class (#PCDATA)>
+
+
+<!--
+ The "attribute-name" element represents the name under which the
+ corresponding value will be stored, in the generic attributes of the
+ UIComponent we are related to.
+-->
+<!ELEMENT attribute-name (#PCDATA)>
+
+
+<!--
+ The "component-class" element represents the fully qualified class name
+ of a concrete UIComponent implementation class. It must be of
+ type "ClassName".
+-->
+<!ELEMENT component-class (#PCDATA)>
+
+
+<!--
+ The "component-family" element represents the component family for
+ which the Renderer represented by the parent "renderer" element will be
+ used.
+-->
+<!ELEMENT component-family (#PCDATA)>
+
+<!--
+ The "component-type" element represents the name under which the
+ corresponding UIComponent class should be registered.
+-->
+<!ELEMENT component-type (#PCDATA)>
+
+
+<!--
+ The "converter-class" element represents the fully qualified class name
+ of a concrete Converter implementation class. It must be of
+ type "ClassName".
+-->
+<!ELEMENT converter-class (#PCDATA)>
+
+
+<!--
+ The "converter-for-class" element represents the fully qualified class name
+ for which a Converter class will be registered. It must be of
+ type "ClassName".
+-->
+<!ELEMENT converter-for-class (#PCDATA)>
+
+
+<!--
+ The "converter-id" element represents the identifier under which the
+ corresponding Converter class should be registered.
+-->
+<!ELEMENT converter-id (#PCDATA)>
+
+<!--
+ The "default-render-kit-id" element allows the application to define
+ a renderkit to be used other than the standard one.
+-->
+<!ELEMENT default-render-kit-id (#PCDATA)>
+
+<!--
+ The "default-locale" element declares the default locale for this
+ application instance. It must be specified as
+ :language:[_:country:[_:variant:]] without the colons, for example
+ "ja_JP_SJIS". The separators between the segments may be '-' or
+ '_'.
+-->
+<!ELEMENT default-locale (#PCDATA)>
+
+<!--
+ The "default-value" contains the value for the property or attribute
+ in which this element resides. This value differs from the
+ "suggested-value" in that the property or attribute must take the
+ value, whereas in "suggested-value" taking the value is optional.
+-->
+<!ELEMENT default-value (#PCDATA)>
+
+<!--
+ The "description" element contains a textual description of the element
+ it is nested in, optionally flagged with a language code using the
+ "xml:lang" attribute.
+-->
+<!ELEMENT description ANY>
+<!ATTLIST description xml:lang %Language; #IMPLIED>
+
+
+<!--
+ The "display-name" element is a short descriptive name describing the
+ entity associated with the element it is nested in, intended to be
+ displayed by tools, and optionally flagged with a language code using
+ the "xml:lang" attribute.
+-->
+<!ELEMENT display-name (#PCDATA)>
+<!ATTLIST display-name xml:lang %Language; #IMPLIED>
+
+<!--
+ The "faces-context-factory" element contains the fully qualified
+ class name of the concrete FacesContextFactory implementation class
+ that will be called when
+ FactoryFinder.getFactory(FACES_CONTEXT_FACTORY) is called. It must
+ be of type "ClassName".
+-->
+<!ELEMENT faces-context-factory (#PCDATA)>
+
+<!--
+ The "from-action" element contains an action reference expression
+ that must have been executed (by the default ActionListener for handling
+ application level events) in order to select this navigation rule. If
+ not specified, this rule will be relevant no matter which action reference
+ was executed (or if no action reference was executed).
+
+ This value must be of type "Action".
+-->
+<!ELEMENT from-action (#PCDATA)>
+
+
+<!--
+ The "from-outcome" element contains a logical outcome string returned
+ by the execution of an application action method selected via an
+ "actionRef" property (or a literal value specified by an "action"
+ property) of a UICommand component. If specified, this rule will be
+ relevant only if the outcome value matches this element's value. If
+ not specified, this rule will be relevant no matter what the outcome
+ value was.
+-->
+<!ELEMENT from-outcome (#PCDATA)>
+
+
+<!--
+ The "from-view-id" element contains the view identifier of the view
+ for which the containing navigation rule is relevant. If no
+ "from-view" element is specified, this rule applies to navigation
+ decisions on all views. If this element is not specified, a value
+ of "*" is assumed, meaning that this navigation rule applies to all
+ views.
+
+ This value must be of type "ViewIdPattern".
+-->
+<!ELEMENT from-view-id (#PCDATA)>
+
+
+<!--
+ The "key" element is the String representation of a map key that
+ will be stored in a managed property of type java.util.Map.
+-->
+<!ELEMENT key (#PCDATA)>
+
+
+<!--
+ The "key-class" element defines the Java type to which each "key"
+ element in a set of "map-entry" elements will be converted to. It
+ must be of type "ClassName". If omitted, "java.lang.String"
+ is assumed.
+-->
+<!ELEMENT key-class (#PCDATA)>
+
+
+<!--
+ The "large-icon" element contains the resource path to a large (32x32)
+ icon image. The image may be in either GIF or JPG format.
+-->
+<!ELEMENT large-icon (#PCDATA)>
+
+<!--
+ The "lifecycle-factory" element contains the fully qualified class name
+ of the concrete LifecycleFactory implementation class that will be called
+ when FactoryFinder.getFactory(LIFECYCLE_FACTORY) is called. It must be
+ of type "ClassName".
+-->
+<!ELEMENT lifecycle-factory (#PCDATA)>
+
+<!--
+ The "managed-bean-class" element represents the fully qualified class
+ name of the Java class that will be used to instantiate a new instance
+ if creation of the specified managed bean is requested. It must be of
+ type "ClassName".
+
+ The specified class must conform to standard JavaBeans conventions.
+ In particular, it must have a public zero-arguments constructor, and
+ zero or more public property setters.
+-->
+<!ELEMENT managed-bean-class (#PCDATA)>
+
+
+<!--
+ The "managed-bean-name" element represents the attribute name under
+ which a managed bean will be searched for, as well as stored (unless
+ the "managed-bean-scope" value is "none"). It must be of type
+ "Identifier".
+-->
+<!ELEMENT managed-bean-name (#PCDATA)>
+
+
+<!--
+ The "managed-bean-scope" element represents the scope into which a newly
+ created instance of the specified managed bean will be stored (unless
+ the value is "none"). It must be of type "ScopeOrNone".
+-->
+<!ELEMENT managed-bean-scope (#PCDATA)>
+
+<!--
+ The "navigation-handler" element contains the fully qualified class name
+ of the concrete NavigationHandler implementation class that will be called
+ during the Invoke Application phase of the request processing lifecycle,
+ if the default ActionListener (provided by the JSF implementation) is used.
+ It must be of type "ClassName".
+-->
+<!ELEMENT navigation-handler (#PCDATA)>
+
+<!--
+The "phase-listener" element contains the fully qualified class
+name of the concrete PhaseListener implementation class that will be
+registered on the Lifecycle. It must be of type "ClassName".
+-->
+<!ELEMENT phase-listener (#PCDATA)>
+
+<!--
+ The "redirect" element indicates that navigation to the specified
+ "to-view-id" should be accomplished by performing an HTTP redirect
+ rather than the usual ViewHandler mechanisms.
+-->
+<!ELEMENT redirect EMPTY>
+
+<!--
+ The "suggested-value" contains the value for the property or
+ attribute in which this element resides. This value is advisory
+ only and is intended for tools to use when populating pallettes.
+-->
+<!ELEMENT suggested-value (#PCDATA)>
+
+
+<!--
+
+ The "view-handler" element contains the fully qualified class name
+ of the concrete ViewHandler implementation class that will be called
+ during the Restore View and Render Response phases of the request
+ processing lifecycle. The faces implementation must provide a
+ default implementation of this class
+-->
+<!ELEMENT view-handler (#PCDATA)>
+
+<!--
+
+ The "state-manager" element contains the fully qualified class name
+ of the concrete StateManager implementation class that will be called
+ during the Restore View and Render Response phases of the request
+ processing lifecycle. The faces implementation must provide a
+ default implementation of this class
+-->
+<!ELEMENT state-manager (#PCDATA)>
+
+<!--
+ The "null-value" element indicates that the managed property in which we
+ are nested will be explicitly set to null if our managed bean is
+ automatically created. This is different from omitting the managed
+ property element entirely, which will cause no property setter to be
+ called for this property.
+
+ The "null-value" element can only be used when the associated
+ "property-class" identifies a Java class, not a Java primitive.
+-->
+<!ELEMENT null-value EMPTY>
+
+
+<!--
+ The "property-class" element represents the Java type of the value
+ associated with this property name. It must be of type "JavaType".
+ If not specified, it can be inferred from existing classes; however,
+ this element should be specified if the configuration file is going
+ to be the source for generating the corresponding classes.
+-->
+<!ELEMENT property-class (#PCDATA)>
+
+
+<!--
+ The "property-name" element represents the JavaBeans property name
+ under which the corresponding value may be stored.
+-->
+<!ELEMENT property-name (#PCDATA)>
+
+
+<!--
+ The "property-resolver" element contains the fully qualified class name
+ of the concrete PropertyResolver implementation class that will be used
+ during the processing of value binding expressions.
+ It must be of type "ClassName".
+-->
+<!ELEMENT property-resolver (#PCDATA)>
+
+
+<!--
+ The "referenced-bean-class" element represents the fully qualified class
+ name of the Java class (either abstract or concrete) or Java interface
+ implemented by the corresponding referenced bean. It must be of type
+ "ClassName".
+-->
+<!ELEMENT referenced-bean-class (#PCDATA)>
+
+
+<!--
+ The "referenced-bean-name" element represents the attribute name under
+ which the corresponding referenced bean may be assumed to be stored,
+ in one of the scopes defined by the "Scope" type. It must be of type
+ "Identifier".
+-->
+<!ELEMENT referenced-bean-name (#PCDATA)>
+
+
+<!--
+ The "render-kit-id" element represents an identifier for the
+ RenderKit represented by the parent "render-kit" element.
+-->
+<!ELEMENT render-kit-id (#PCDATA)>
+
+
+<!--
+ The "render-kit-class" element represents the fully qualified class name
+ of a concrete RenderKit implementation class. It must be of
+ type "ClassName".
+-->
+<!ELEMENT render-kit-class (#PCDATA)>
+
+
+<!--
+ The "renderer-class" element represents the fully qualified class name
+ of a concrete Renderer implementation class. It must be of
+ type "ClassName".
+-->
+<!ELEMENT renderer-class (#PCDATA)>
+
+<!--
+ The "render-kit-factory" element contains the fully qualified class name
+ of the concrete RenderKitFactory implementation class that will be called
+ when FactoryFinder.getFactory(RENDER_KIT_FACTORY) is called. It must be
+ of type "ClassName".
+-->
+<!ELEMENT render-kit-factory (#PCDATA)>
+
+<!--
+ The "renderer-type" element represents a renderer type identifier for the
+ Renderer represented by the parent "renderer" element.
+-->
+<!ELEMENT renderer-type (#PCDATA)>
+
+<!--
+ The "small-icon" element contains the resource path to a large (16x16)
+ icon image. The image may be in either GIF or JPG format.
+-->
+<!ELEMENT small-icon (#PCDATA)>
+
+<!--
+ The "supported-locale" element allows authors to declare which
+ locales are supported in this application instance.
+
+ It must be specified as :language:[_:country:[_:variant:]] without
+ the colons, for example "ja_JP_SJIS". The separators between the
+ segments may be '-' or '_'.
+-->
+<!ELEMENT supported-locale (#PCDATA)>
+
+<!--
+ The "to-view" element contains the view identifier of the next view
+ that should be displayed if this navigation rule is matched. It
+ must be of type "ViewId".
+-->
+<!ELEMENT to-view-id (#PCDATA)>
+
+
+<!--
+ The "validator-class" element represents the fully qualified class name
+ of a concrete Validator implementation class. It must be of
+ type "ClassName".
+-->
+<!ELEMENT validator-class (#PCDATA)>
+
+
+<!--
+ The "validator-id" element represents the identifier under which the
+ corresponding Validator class should be registered.
+-->
+<!ELEMENT validator-id (#PCDATA)>
+
+
+<!--
+ The "value" element is the String representation of a literal
+ value to which a scalar managed property will be set, or a value
+ binding expression ("#{...}") that will be used to calculate the
+ required value. It will be converted as specified for the actual
+ property type.
+-->
+<!ELEMENT value (#PCDATA)>
+
+
+<!--
+ The "value-class" element defines the Java type to which each
+ "value" element's value will be converted to, prior to adding it to
+ the "list-entries" list for a managed property that is a
+ java.util.List, or a "map-entries" map for a managed property that
+ is a java.util.Map. It must be of type "ClassName". If omitted,
+ "java.lang.String" is assumed.
+-->
+<!ELEMENT value-class (#PCDATA)>
+
+<!--
+ The "variable-resolver" element contains the fully qualified class name
+ of the concrete VariableResolver implementation class that will be used
+ during the processing of value binding expressions.
+ It must be of type "ClassName".
+-->
+<!ELEMENT variable-resolver (#PCDATA)>
+
+
+<!-- ============================ Identifier Attributes ==================== -->
+
+
+<!ATTLIST action-listener id ID #IMPLIED>
+<!ATTLIST application id ID #IMPLIED>
+<!ATTLIST application-factory id ID #IMPLIED>
+<!ATTLIST attribute id ID #IMPLIED>
+<!ATTLIST attribute-class id ID #IMPLIED>
+<!ATTLIST attribute-extension id ID #IMPLIED>
+<!ATTLIST attribute-name id ID #IMPLIED>
+<!ATTLIST component id ID #IMPLIED>
+<!ATTLIST component-class id ID #IMPLIED>
+<!ATTLIST component-extension id ID #IMPLIED>
+<!ATTLIST component-family id ID #IMPLIED>
+<!ATTLIST component-type id ID #IMPLIED>
+<!ATTLIST converter id ID #IMPLIED>
+<!ATTLIST converter-class id ID #IMPLIED>
+<!ATTLIST converter-for-class id ID #IMPLIED>
+<!ATTLIST converter-id id ID #IMPLIED>
+<!ATTLIST default-locale id ID #IMPLIED>
+<!ATTLIST default-render-kit-id id ID #IMPLIED>
+<!ATTLIST default-value id ID #IMPLIED>
+<!ATTLIST description id ID #IMPLIED>
+<!ATTLIST display-name id ID #IMPLIED>
+<!ATTLIST faces-config id ID #IMPLIED>
+<!ATTLIST faces-context-factory id ID #IMPLIED>
+<!ATTLIST facet id ID #IMPLIED>
+<!ATTLIST facet-extension id ID #IMPLIED>
+<!ATTLIST facet-name id ID #IMPLIED>
+<!ATTLIST factory id ID #IMPLIED>
+<!ATTLIST from-action id ID #IMPLIED>
+<!ATTLIST from-outcome id ID #IMPLIED>
+<!ATTLIST from-view-id id ID #IMPLIED>
+<!ATTLIST icon id ID #IMPLIED>
+<!ATTLIST key id ID #IMPLIED>
+<!ATTLIST key-class id ID #IMPLIED>
+<!ATTLIST large-icon id ID #IMPLIED>
+<!ATTLIST lifecycle id ID #IMPLIED>
+<!ATTLIST lifecycle-factory id ID #IMPLIED>
+<!ATTLIST list-entries id ID #IMPLIED>
+<!ATTLIST locale-config id ID #IMPLIED>
+<!ATTLIST managed-bean id ID #IMPLIED>
+<!ATTLIST managed-bean-class id ID #IMPLIED>
+<!ATTLIST managed-bean-name id ID #IMPLIED>
+<!ATTLIST managed-bean-scope id ID #IMPLIED>
+<!ATTLIST managed-property id ID #IMPLIED>
+<!ATTLIST map-entries id ID #IMPLIED>
+<!ATTLIST map-entry id ID #IMPLIED>
+<!ATTLIST message-bundle id ID #IMPLIED>
+<!ATTLIST navigation-case id ID #IMPLIED>
+<!ATTLIST navigation-handler id ID #IMPLIED>
+<!ATTLIST navigation-rule id ID #IMPLIED>
+<!ATTLIST null-value id ID #IMPLIED>
+<!ATTLIST phase-listener id ID #IMPLIED>
+<!ATTLIST property id ID #IMPLIED>
+<!ATTLIST property-class id ID #IMPLIED>
+<!ATTLIST property-extension id ID #IMPLIED>
+<!ATTLIST property-name id ID #IMPLIED>
+<!ATTLIST property-resolver id ID #IMPLIED>
+<!ATTLIST redirect id ID #IMPLIED>
+<!ATTLIST referenced-bean id ID #IMPLIED>
+<!ATTLIST referenced-bean-class id ID #IMPLIED>
+<!ATTLIST referenced-bean-name id ID #IMPLIED>
+<!ATTLIST render-kit id ID #IMPLIED>
+<!ATTLIST render-kit-class id ID #IMPLIED>
+<!ATTLIST render-kit-factory id ID #IMPLIED>
+<!ATTLIST render-kit-id id ID #IMPLIED>
+<!ATTLIST renderer id ID #IMPLIED>
+<!ATTLIST renderer-class id ID #IMPLIED>
+<!ATTLIST renderer-extension id ID #IMPLIED>
+<!ATTLIST renderer-type id ID #IMPLIED>
+<!ATTLIST small-icon id ID #IMPLIED>
+<!ATTLIST state-manager id ID #IMPLIED>
+<!ATTLIST suggested-value id ID #IMPLIED>
+<!ATTLIST supported-locale id ID #IMPLIED>
+<!ATTLIST to-view-id id ID #IMPLIED>
+<!ATTLIST validator id ID #IMPLIED>
+<!ATTLIST validator-class id ID #IMPLIED>
+<!ATTLIST validator-id id ID #IMPLIED>
+<!ATTLIST value id ID #IMPLIED>
+<!ATTLIST value-class id ID #IMPLIED>
+<!ATTLIST variable-resolver id ID #IMPLIED>
+<!ATTLIST view-handler id ID #IMPLIED>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/binding-manager/sample-bindings.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/binding-manager/sample-bindings.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/binding-manager/sample-bindings.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1524 @@
+<!--
+ $Id: sample-bindings.xml 61991 2007-04-02 16:14:51Z bstansberry at jboss.com $
+
+ A sample configuration for the binding service which defines different
+ port configurations (ports-default, ports-01, ports-02) for running multiple
+ JBoss instances in parallel on the same machine.
+
+ The actual port configuration can be selected within the jboss-service.xml
+ file via ServiceBindingManager attribute ServerName.
+
+ The following sample e.g. selects the jboss-default port configuration
+
+ <mbean code="org.jboss.services.binding.ServiceBindingManager"
+ name="jboss.system:service=ServiceBindingManager">
+ <attribute name="ServerName">ports-default</attribute>
+ <attribute name="StoreURL">file:../server/port-bindings.xml</attribute>
+ <attribute name="StoreFactoryClassName">
+ org.jboss.services.binding.XMLServicesStoreFactory
+ </attribute>
+ </mbean>
+
+ For running a second server instance you have to change the port
+ bindings of that instance by specifing an alternative port binding
+ configuration in the jboss-service.xml of the second server, e.g.
+
+ <attribute name="ServerName">ports-01</attribute>
+
+ Additional documentation for running multiple JBoss instances on the
+ same machine can be found at http://www.jboss.com/products/jbossas/docs
+ in the offical JBoss Application Server Guide in chapter
+ "MBean Service Miscellany - Services Binding Management"
+-->
+<service-bindings>
+
+ <!-- ********************************************************** -->
+ <!-- * ports-default * -->
+ <!-- ********************************************************** -->
+ <server name="ports-default">
+
+ <!-- ********************* jboss-service.xml ****************** -->
+
+ <service-config name="jboss:service=Naming"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port" hostName="BindAddress">
+ <attribute name="RmiPort">1098</attribute>
+ </delegate-config>
+ <binding port="1099" host="${jboss.bind.address}"/>
+ </service-config>
+
+
+ <service-config name="jboss:service=WebService"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="8083"/>
+ </service-config>
+
+
+ <service-config name="jboss:service=invoker,type=jrmp"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="4444"/>
+ </service-config>
+
+ <service-config name="jboss:service=invoker,type=pooled"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="4445"/>
+ </service-config>
+
+
+ <!-- ********************* cluster-service.xml **************** -->
+
+ <service-config name="jboss:service=HAJNDI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="Port" hostName="BindAddress">
+ <attribute name="RmiPort">1101</attribute>
+ </delegate-config>
+ <binding port="1100" host="${jboss.bind.address}"/>
+ </service-config>
+
+ <service-config name="jboss:service=invoker,type=jrmpha"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="4444"/>
+ </service-config>
+
+ <service-config name="jboss:service=invoker,type=pooledha"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="4448"/>
+ </service-config>
+
+ <!-- ********************* iiop-service.xml ****************** -->
+
+ <service-config name="jboss:service=CorbaORB"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="3528"/>
+ </service-config>
+
+
+ <!-- ********************* jmx-rmi-adaptor.sar **************** -->
+
+ <service-config name="jboss.jmx:type=Connector,name=RMI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="19001"/>
+ </service-config>
+
+
+ <!-- ********************* snmp-adaptor.sar ****************** -->
+
+ <service-config name="jboss.jmx:name=SnmpAgent,service=trapd,type=logger"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="1162"/>
+ </service-config>
+
+ <service-config name="jboss.jmx:name=SnmpAgent,service=snmp,type=adaptor"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="1161"/>
+ </service-config>
+
+
+ <!-- ********************* jbossmq-service.xml **************** -->
+
+ <!-- JMS related services -->
+ <service-config name="jboss.mq:service=InvocationLayer,type=UIL2"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="8093"/>
+ </service-config>
+
+
+ <!-- ********************* jbossmq-httpil.sar **************** -->
+ <service-config name="jboss.mq:service=InvocationLayer,type=HTTP"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="URLPort"/>
+ <binding port="8080"/>
+ </service-config>
+
+ <!-- ********************* hajndi-jms-ds.xml **************** -->
+
+ <!-- The JMS provider loader -->
+ <service-config name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <!--
+ MAKE SURE java.naming.provider.url
+ PORT IS SAME AS HA-JNDI ABOVE !!!
+ -->
+ <delegate-config>
+ <attribute name="Properties"><![CDATA[
+ java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
+ java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
+ java.naming.provider.url=${jboss.bind.address:localhost}:1100
+ jnp.disableDiscovery=false
+ jnp.partitionName=${jboss.partition.name:DefaultPartition}
+ jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
+ jnp.discoveryPort=1102
+ jnp.discoveryTTL=16
+ jnp.discoveryTimeout=5000
+ jnp.maxRetries=1
+ ]]>
+ </attribute>
+ </delegate-config>
+ <!-- NOTE: YOU MUST ADD THIS ELEMENT, BUT THE VALUE DOESN'T MATTER
+ BE SURE THE CORRECT VALUE IS IN java.naming.provider.url ABOVE -->
+ <binding port="1100"/>
+ </service-config>
+
+ <!-- **************** http-invoker.sar & httpha-invoker.sar*************** -->
+ <!-- EJBInvoker -->
+ <service-config name="jboss:service=invoker,type=http"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/EJBInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8080"/>
+ </service-config>
+
+ <!-- EJB3 Remoting Connector ejb3.deployer/META-INF/jboss-service.xml -->
+
+ <service-config name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config>
+ <attribute name="InvokerLocator">socket://${jboss.bind.address}:3873</attribute>
+ </delegate-config>
+ <binding port="3873"/>
+ </service-config>
+
+ <!-- JMXInvoker -->
+ <service-config name="jboss:service=invoker,type=http,target=Naming"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/JMXInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8080"/>
+ </service-config>
+
+ <!-- readonly JMXInvoker -->
+ <service-config name="jboss:service=invoker,type=http,target=Naming,readonly=true"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/readonly/JMXInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8080"/>
+ </service-config>
+
+ <!-- **************** httpha-invoker.sar*************** -->
+ <!-- EJBInvokerHA -->
+ <service-config name="jboss:service=invoker,type=httpHA"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/EJBInvokerHAServlet</attribute>
+ </delegate-config>
+ <binding port="8080"/>
+ </service-config>
+
+ <!-- JMXInvokerHA -->
+ <service-config name="jboss:service=invoker,type=http,target=HAJNDI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/JMXInvokerHAServlet</attribute>
+ </delegate-config>
+ <binding port="8080"/>
+ </service-config>
+
+
+ <!-- ********************* jboss-ws4ee.sar **************** -->
+
+ <!-- Web Service related services -->
+ <service-config name="jboss.ws4ee:service=AxisService"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="WebServicePort" hostName="WebServiceHost"/>
+ <binding port="8080" host="${jboss.bind.address}"/>
+ </service-config>
+
+ <!-- ********************* remoting **************** -->
+
+ <!-- *** remoting connector *** -->
+ <service-config name="jboss.remoting:service=Connector,transport=socket"
+ delegateClass="org.jboss.services.binding.XSLTConfigDelegate">
+ <delegate-config>
+ <xslt-config configName="Configuration"><![CDATA[
+ <xsl:stylesheet xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="port"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match="attribute[@name='serverBindPort']">
+ <attribute type="java.lang.String" name="serverBindPort"><xsl:value-of select='$port'/></attribute>
+ </xsl:template>
+
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+ </xsl:stylesheet>
+ ]]>
+ </xslt-config>
+ </delegate-config>
+ <binding port="4446" />
+ </service-config>
+
+
+ <!-- ********************* hsqldb-ds.xml ********************** -->
+
+ <!-- Hypersonic related services when using the tcp/ip access
+ <service-config name="jboss.jca:service=ManagedConnectionFactory,name=DefaultDS"
+ delegateClass="org.jboss.services.binding.XSLTConfigDelegate"
+ >
+ <delegate-config>
+ <xslt-config configName="ManagedConnectionFactoryProperties"><![CDATA[
+<xsl:stylesheet
+ xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="host"/>
+ <xsl:param name="port"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match="config-property[@name='ConnectionURL']">
+ <config-property type="java.lang.String" name="ConnectionURL">jdbc:hsqldb:hsql://<xsl:value-of select='$host'/>:<xsl:value-of select='$port'/></config-property>
+ </xsl:template>
+
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+</xsl:stylesheet>
+]]>
+ </xslt-config>
+ </delegate-config>
+ <binding host="localhost" port="1701" />
+ </service-config>
+
+ <service-config name="jboss:service=Hypersonic"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port" />
+ <binding port="1701" />
+ </service-config>
+ -->
+
+
+ <!-- ********************* tomcat ********************** -->
+
+ <service-config name="jboss.web:service=WebServer"
+ delegateClass="org.jboss.services.binding.XSLTFileDelegate"
+ >
+ <delegate-config>
+ <xslt-config configName="ConfigFile"><![CDATA[
+ <xsl:stylesheet
+ xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="port"/>
+
+ <xsl:variable name="portAJP" select="$port - 71"/>
+ <xsl:variable name="portHttps" select="$port + 363"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match = "Connector">
+ <Connector>
+ <xsl:for-each select="@*">
+ <xsl:choose>
+ <xsl:when test="(name() = 'port' and . = '8080')">
+ <xsl:attribute name="port"><xsl:value-of select="$port" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'port' and . = '8009')">
+ <xsl:attribute name="port"><xsl:value-of select="$portAJP" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'redirectPort')">
+ <xsl:attribute name="redirectPort"><xsl:value-of select="$portHttps" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'port' and . = '8443')">
+ <xsl:attribute name="port"><xsl:value-of select="$portHttps" /></xsl:attribute>
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:attribute name="{name()}"><xsl:value-of select="." /></xsl:attribute>
+ </xsl:otherwise>
+ </xsl:choose>
+ </xsl:for-each>
+ <xsl:apply-templates/>
+ </Connector>
+ </xsl:template>
+
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+ </xsl:stylesheet>
+ ]]>
+ </xslt-config>
+ </delegate-config>
+ <binding port="8080"/>
+ </service-config>
+
+ <!-- ********************* jboss messaging ********************** -->
+
+ <service-config name="jboss.messaging:service=Connector,transport=socket"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config>
+ <attribute name="InvokerLocator">socket://${jboss.bind.address}:4457/?dataType=jms&serializationtype=jms&timeout=0&leasePeriod=20000&socket.check_connection=false&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat</attribute>
+ </delegate-config>
+ <binding port="4457"/>
+ </service-config>
+
+ </server>
+
+ <!-- ********************************************************** -->
+ <!-- * ports-01 * -->
+ <!-- ********************************************************** -->
+ <server name="ports-01">
+
+ <!-- EJB3 Remoting Connector ejb3.deployer/META-INF/jboss-service.xml -->
+
+ <service-config name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config>
+ <attribute name="InvokerLocator">socket://${jboss.bind.address}:3973</attribute>
+ </delegate-config>
+ <binding port="3973"/>
+ </service-config>
+
+ <!-- ********************* jboss-service.xml ****************** -->
+
+ <service-config name="jboss:service=Naming"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port" hostName="BindAddress">
+ <attribute name="RmiPort">1198</attribute>
+ </delegate-config>
+ <binding port="1199" host="${jboss.bind.address}"/>
+ </service-config>
+
+
+ <service-config name="jboss:service=WebService"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="8183"/>
+ </service-config>
+
+
+ <service-config name="jboss:service=invoker,type=jrmp"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="4544"/>
+ </service-config>
+
+
+ <service-config name="jboss:service=invoker,type=pooled"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="4545"/>
+ </service-config>
+
+
+ <!-- ********************* cluster-service.xml **************** -->
+
+ <service-config name="jboss:service=HAJNDI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="Port" hostName="BindAddress">
+ <attribute name="RmiPort">1201</attribute>
+ </delegate-config>
+ <binding port="1200" host="${jboss.bind.address}"/>
+ </service-config>
+
+ <service-config name="jboss:service=invoker,type=jrmpha"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="4544"/>
+ </service-config>
+
+ <service-config name="jboss:service=invoker,type=pooledha"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="4548"/>
+ </service-config>
+
+ <!-- ********************* iiop-service.xml ****************** -->
+
+ <service-config name="jboss:service=CorbaORB"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="3628"/>
+ </service-config>
+
+
+ <!-- ********************* jmx-rmi-adaptor.sar **************** -->
+
+ <service-config name="jboss.jmx:type=Connector,name=RMI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="19101"/>
+ </service-config>
+
+
+ <!-- ********************* snmp-adaptor.sar ****************** -->
+
+ <service-config name="jboss.jmx:name=SnmpAgent,service=trapd,type=logger"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="1262"/>
+ </service-config>
+
+ <service-config name="jboss.jmx:name=SnmpAgent,service=snmp,type=adaptor"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="1261"/>
+ </service-config>
+
+
+ <!-- ********************* jbossmq-service.xml **************** -->
+
+ <!-- JMS related services -->
+ <service-config name="jboss.mq:service=InvocationLayer,type=UIL2"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="8193"/>
+ </service-config>
+
+
+ <!-- ********************* jbossmq-httpil.sar **************** -->
+ <service-config name="jboss.mq:service=InvocationLayer,type=HTTP"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="URLPort"/>
+ <binding port="8180"/>
+ </service-config>
+
+ <!-- ********************* hajndi-jms-ds.xml **************** -->
+
+ <!-- The JMS provider loader -->
+ <service-config name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <!--
+ MAKE SURE java.naming.provider.url
+ PORT IS SAME AS HA-JNDI ABOVE !!!
+ -->
+ <delegate-config>
+ <attribute name="Properties"><![CDATA[
+ java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
+ java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
+ java.naming.provider.url=${jboss.bind.address:localhost}:1200
+ jnp.disableDiscovery=false
+ jnp.partitionName=${jboss.partition.name:DefaultPartition}
+ jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
+ jnp.discoveryPort=1102
+ jnp.discoveryTTL=16
+ jnp.discoveryTimeout=5000
+ jnp.maxRetries=1
+ ]]>
+ </attribute>
+ </delegate-config>
+ <!-- NOTE: YOU MUST ADD THIS ELEMENT, BUT THE VALUE DOESN'T MATTER
+ BE SURE THE CORRECT VALUE IS IN java.naming.provider.url ABOVE -->
+ <binding port="1200"/>
+ </service-config>
+
+ <!-- **************** http-invoker.sar & httpha-invoker.sar*************** -->
+ <!-- EJBInvoker -->
+ <service-config name="jboss:service=invoker,type=http"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/EJBInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8180"/>
+ </service-config>
+
+ <!-- JMXInvoker -->
+ <service-config name="jboss:service=invoker,type=http,target=Naming"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/JMXInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8180"/>
+ </service-config>
+
+ <!-- readonly JMXInvoker -->
+ <service-config name="jboss:service=invoker,type=http,target=Naming,readonly=true"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/readonly/JMXInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8180"/>
+ </service-config>
+
+ <!-- **************** httpha-invoker.sar*************** -->
+ <!-- EJBInvokerHA -->
+ <service-config name="jboss:service=invoker,type=httpHA"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/EJBInvokerHAServlet</attribute>
+ </delegate-config>
+ <binding port="8180"/>
+ </service-config>
+
+ <!-- JMXInvokerHA -->
+ <service-config name="jboss:service=invoker,type=http,target=HAJNDI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/JMXInvokerHAServlet</attribute>
+ </delegate-config>
+ <binding port="8180"/>
+ </service-config>
+
+
+
+
+ <!-- ********************* jboss-ws4ee.sar **************** -->
+
+ <!-- Web Service related services -->
+ <service-config name="jboss.ws4ee:service=AxisService"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="WebServicePort" hostName="WebServiceHost"/>
+ <binding port="8180" host="${jboss.bind.address}"/>
+ </service-config>
+
+ <!-- ********************* remoting **************** -->
+
+ <!-- *** remoting connector *** -->
+ <service-config name="jboss.remoting:service=Connector,transport=socket"
+ delegateClass="org.jboss.services.binding.XSLTConfigDelegate">
+ <delegate-config>
+ <xslt-config configName="Configuration"><![CDATA[
+ <xsl:stylesheet xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="port"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match="attribute[@name='serverBindPort']">
+ <attribute type="java.lang.String" name="serverBindPort"><xsl:value-of select='$port'/></attribute>
+ </xsl:template>
+
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+ </xsl:stylesheet>
+ ]]>
+ </xslt-config>
+ </delegate-config>
+ <binding port="5446" />
+ </service-config>
+
+ <!-- ********************* hsqldb-ds.xml ********************** -->
+
+ <!-- Hypersonic related services
+
+ Only if using TCP setup (local file setup by default)
+
+ <service-config name="jboss.jca:service=ManagedConnectionFactory,name=DefaultDS"
+ delegateClass="org.jboss.services.binding.XSLTConfigDelegate"
+ >
+ <delegate-config>
+ <xslt-config configName="ManagedConnectionFactoryProperties"><![CDATA[
+<xsl:stylesheet
+ xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="host"/>
+ <xsl:param name="port"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match="config-property[@name='ConnectionURL']">
+ <config-property type="java.lang.String" name="ConnectionURL">jdbc:hsqldb:hsql://<xsl:value-of select='$host'/>:<xsl:value-of select='$port'/></config-property>
+ </xsl:template>
+
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+</xsl:stylesheet>
+]]>
+ </xslt-config>
+ </delegate-config>
+ <binding host="localhost" port="1801" />
+ </service-config>
+
+ <service-config name="jboss:service=Hypersonic"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port" />
+ <binding port="1801" />
+ </service-config>
+
+ -->
+
+
+ <!-- ********************* tomcat ********************** -->
+
+ <service-config name="jboss.web:service=WebServer"
+ delegateClass="org.jboss.services.binding.XSLTFileDelegate"
+ >
+ <delegate-config>
+ <xslt-config configName="ConfigFile"><![CDATA[
+ <xsl:stylesheet
+ xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="port"/>
+
+ <xsl:variable name="portAJP" select="$port - 71"/>
+ <xsl:variable name="portHttps" select="$port + 363"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match = "Connector">
+ <Connector>
+ <xsl:for-each select="@*">
+ <xsl:choose>
+ <xsl:when test="(name() = 'port' and . = '8080')">
+ <xsl:attribute name="port"><xsl:value-of select="$port" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'port' and . = '8009')">
+ <xsl:attribute name="port"><xsl:value-of select="$portAJP" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'redirectPort')">
+ <xsl:attribute name="redirectPort"><xsl:value-of select="$portHttps" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'port' and . = '8443')">
+ <xsl:attribute name="port"><xsl:value-of select="$portHttps" /></xsl:attribute>
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:attribute name="{name()}"><xsl:value-of select="." /></xsl:attribute>
+ </xsl:otherwise>
+ </xsl:choose>
+ </xsl:for-each>
+ <xsl:apply-templates/>
+ </Connector>
+ </xsl:template>
+
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+ </xsl:stylesheet>
+ ]]>
+ </xslt-config>
+ </delegate-config>
+ <binding port="8180"/>
+ </service-config>
+
+ <!-- ********************* jboss messaging ********************** -->
+
+ <service-config name="jboss.messaging:service=Connector,transport=socket"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config>
+ <attribute name="InvokerLocator">socket://${jboss.bind.address}:4557/?dataType=jms&serializationtype=jms&timeout=0&leasePeriod=20000&socket.check_connection=false&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat</attribute>
+ </delegate-config>
+ <binding port="4557"/>
+ </service-config>
+
+ </server>
+
+ <!-- ********************************************************** -->
+ <!-- * ports-02 * -->
+ <!-- ********************************************************** -->
+ <server name="ports-02">
+
+ <!-- EJB3 Remoting Connector ejb3.deployer/META-INF/jboss-service.xml -->
+
+ <service-config name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config>
+ <attribute name="InvokerLocator">socket://${jboss.bind.address}:4073</attribute>
+ </delegate-config>
+ <binding port="4073"/>
+ </service-config>
+
+ <!-- ********************* jboss-service.xml ****************** -->
+
+ <service-config name="jboss:service=Naming"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port" hostName="BindAddress">
+ <attribute name="RmiPort">1298</attribute>
+ </delegate-config>
+ <binding port="1299" host="${jboss.bind.address}"/>
+ </service-config>
+
+
+ <service-config name="jboss:service=WebService"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="8283"/>
+ </service-config>
+
+
+ <service-config name="jboss:service=invoker,type=jrmp"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="4644"/>
+ </service-config>
+
+
+ <service-config name="jboss:service=invoker,type=pooled"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="4645"/>
+ </service-config>
+
+
+ <!-- ********************* cluster-service.xml **************** -->
+
+ <service-config name="jboss:service=HAJNDI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="Port" hostName="BindAddress">
+ <attribute name="RmiPort">1301</attribute>
+ </delegate-config>
+ <binding port="1300" host="${jboss.bind.address}"/>
+ </service-config>
+
+ <service-config name="jboss:service=invoker,type=jrmpha"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="4644"/>
+ </service-config>
+
+ <service-config name="jboss:service=invoker,type=pooledha"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="4648"/>
+ </service-config>
+
+ <!-- ********************* iiop-service.xml ****************** -->
+
+ <service-config name="jboss:service=CorbaORB"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="3728"/>
+ </service-config>
+
+
+ <!-- ********************* jmx-rmi-adaptor.sar **************** -->
+
+ <service-config name="jboss.jmx:type=Connector,name=RMI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="19201"/>
+ </service-config>
+
+
+ <!-- ********************* snmp-adaptor.sar ****************** -->
+
+ <service-config name="jboss.jmx:name=SnmpAgent,service=trapd,type=logger"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="1362"/>
+ </service-config>
+
+ <service-config name="jboss.jmx:name=SnmpAgent,service=snmp,type=adaptor"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="1361"/>
+ </service-config>
+
+
+ <!-- ********************* jbossmq-service.xml **************** -->
+
+ <!-- JMS related services -->
+ <service-config name="jboss.mq:service=InvocationLayer,type=UIL2"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="8293"/>
+ </service-config>
+
+
+ <!-- ********************* jbossmq-httpil.sar **************** -->
+ <service-config name="jboss.mq:service=InvocationLayer,type=HTTP"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="URLPort"/>
+ <binding port="8280"/>
+ </service-config>
+
+ <!-- ********************* hajndi-jms-ds.xml **************** -->
+
+ <!-- The JMS provider loader -->
+ <service-config name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <!--
+ MAKE SURE java.naming.provider.url
+ PORT IS SAME AS HA-JNDI ABOVE !!!
+ -->
+ <delegate-config>
+ <attribute name="Properties"><![CDATA[
+ java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
+ java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
+ java.naming.provider.url=${jboss.bind.address:localhost}:1300
+ jnp.disableDiscovery=false
+ jnp.partitionName=${jboss.partition.name:DefaultPartition}
+ jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
+ jnp.discoveryPort=1102
+ jnp.discoveryTTL=16
+ jnp.discoveryTimeout=5000
+ jnp.maxRetries=1
+ ]]>
+ </attribute>
+ </delegate-config>
+ <!-- NOTE: YOU MUST ADD THIS ELEMENT, BUT THE VALUE DOESN'T MATTER
+ BE SURE THE CORRECT VALUE IS IN java.naming.provider.url ABOVE -->
+ <binding port="1300"/>
+ </service-config>
+
+ <!-- **************** http-invoker.sar & httpha-invoker.sar*************** -->
+ <!-- EJBInvoker -->
+ <service-config name="jboss:service=invoker,type=http"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/EJBInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8280"/>
+ </service-config>
+
+ <!-- JMXInvoker -->
+ <service-config name="jboss:service=invoker,type=http,target=Naming"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/JMXInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8280"/>
+ </service-config>
+
+ <!-- readonly JMXInvoker -->
+ <service-config name="jboss:service=invoker,type=http,target=Naming,readonly=true"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/readonly/JMXInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8280"/>
+ </service-config>
+
+ <!-- **************** httpha-invoker.sar*************** -->
+ <!-- EJBInvokerHA -->
+ <service-config name="jboss:service=invoker,type=httpHA"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/EJBInvokerHAServlet</attribute>
+ </delegate-config>
+ <binding port="8280"/>
+ </service-config>
+
+ <!-- JMXInvokerHA -->
+ <service-config name="jboss:service=invoker,type=http,target=HAJNDI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/JMXInvokerHAServlet</attribute>
+ </delegate-config>
+ <binding port="8280"/>
+ </service-config>
+
+
+
+
+ <!-- ********************* jboss-ws4ee.sar **************** -->
+
+ <!-- Web Service related services -->
+ <service-config name="jboss.ws4ee:service=AxisService"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="WebServicePort" hostName="WebServiceHost"/>
+ <binding port="8280" host="${jboss.bind.address}"/>
+ </service-config>
+
+ <!-- ********************* remoting **************** -->
+
+ <!-- *** remoting connector *** -->
+ <service-config name="jboss.remoting:service=Connector,transport=socket"
+ delegateClass="org.jboss.services.binding.XSLTConfigDelegate">
+ <delegate-config>
+ <xslt-config configName="Configuration"><![CDATA[
+ <xsl:stylesheet xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="port"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match="attribute[@name='serverBindPort']">
+ <attribute type="java.lang.String" name="serverBindPort"><xsl:value-of select='$port'/></attribute>
+ </xsl:template>
+
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+ </xsl:stylesheet>
+ ]]>
+ </xslt-config>
+ </delegate-config>
+ <binding port="6446" />
+ </service-config>
+
+
+ <!-- ********************* hsqldb-ds.xml ********************** -->
+
+ <!-- Hypersonic related services
+
+ Only if using TCP setup (local file setup by default)
+
+ <service-config name="jboss.jca:service=ManagedConnectionFactory,name=DefaultDS"
+ delegateClass="org.jboss.services.binding.XSLTConfigDelegate"
+ >
+ <delegate-config>
+ <xslt-config configName="ManagedConnectionFactoryProperties"><![CDATA[
+<xsl:stylesheet
+ xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="host"/>
+ <xsl:param name="port"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match="config-property[@name='ConnectionURL']">
+ <config-property type="java.lang.String" name="ConnectionURL">jdbc:hsqldb:hsql://<xsl:value-of select='$host'/>:<xsl:value-of select='$port'/></config-property>
+ </xsl:template>
+
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+</xsl:stylesheet>
+]]>
+ </xslt-config>
+ </delegate-config>
+ <binding host="localhost" port="1901" />
+ </service-config>
+
+ <service-config name="jboss:service=Hypersonic"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port" />
+ <binding port="1901" />
+ </service-config>
+
+ -->
+
+
+ <!-- ********************* tomcat ***************** -->
+
+ <service-config name="jboss.web:service=WebServer"
+ delegateClass="org.jboss.services.binding.XSLTFileDelegate"
+ >
+ <delegate-config>
+ <xslt-config configName="ConfigFile"><![CDATA[
+ <xsl:stylesheet
+ xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="port"/>
+
+ <xsl:variable name="portAJP" select="$port - 71"/>
+ <xsl:variable name="portHttps" select="$port + 363"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match = "Connector">
+ <Connector>
+ <xsl:for-each select="@*">
+ <xsl:choose>
+ <xsl:when test="(name() = 'port' and . = '8080')">
+ <xsl:attribute name="port"><xsl:value-of select="$port" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'port' and . = '8009')">
+ <xsl:attribute name="port"><xsl:value-of select="$portAJP" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'redirectPort')">
+ <xsl:attribute name="redirectPort"><xsl:value-of select="$portHttps" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'port' and . = '8443')">
+ <xsl:attribute name="port"><xsl:value-of select="$portHttps" /></xsl:attribute>
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:attribute name="{name()}"><xsl:value-of select="." /></xsl:attribute>
+ </xsl:otherwise>
+ </xsl:choose>
+ </xsl:for-each>
+ <xsl:apply-templates/>
+ </Connector>
+ </xsl:template>
+
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+ </xsl:stylesheet>
+ ]]>
+ </xslt-config>
+ </delegate-config>
+ <binding port="8280"/>
+ </service-config>
+
+ <!-- ********************* jboss messaging ********************** -->
+
+ <service-config name="jboss.messaging:service=Connector,transport=socket"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config>
+ <attribute name="InvokerLocator">socket://${jboss.bind.address}:4657/?dataType=jms&serializationtype=jms&timeout=0&leasePeriod=20000&socket.check_connection=false&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat</attribute>
+ </delegate-config>
+ <binding port="4657"/>
+ </service-config>
+
+ </server>
+
+ <!-- ********************************************************** -->
+ <!-- * ports-03 * -->
+ <!-- ********************************************************** -->
+ <server name="ports-03">
+
+ <!-- ********************* jboss-service.xml ****************** -->
+
+ <service-config name="jboss:service=Naming"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port" hostName="BindAddress">
+ <attribute name="RmiPort">1398</attribute>
+ </delegate-config>
+ <binding port="1399" host="${jboss.bind.address}"/>
+ </service-config>
+
+
+ <service-config name="jboss:service=WebService"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="8383"/>
+ </service-config>
+
+
+ <service-config name="jboss:service=invoker,type=jrmp"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="4744"/>
+ </service-config>
+
+
+ <service-config name="jboss:service=invoker,type=pooled"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="4745"/>
+ </service-config>
+
+
+ <!-- ********************* cluster-service.xml **************** -->
+
+ <service-config name="jboss:service=HAJNDI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="Port" hostName="BindAddress">
+ <attribute name="RmiPort">1401</attribute>
+ </delegate-config>
+ <binding port="1400" host="${jboss.bind.address}"/>
+ </service-config>
+
+ <service-config name="jboss:service=invoker,type=jrmpha"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="4744"/>
+ </service-config>
+
+ <service-config name="jboss:service=invoker,type=pooledha"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="4748"/>
+ </service-config>
+
+ <!-- ********************* iiop-service.xml ****************** -->
+
+ <service-config name="jboss:service=CorbaORB"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="3828"/>
+ </service-config>
+
+
+ <!-- ********************* jmx-rmi-adaptor.sar **************** -->
+
+ <service-config name="jboss.jmx:type=Connector,name=RMI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="RMIObjectPort"/>
+ <binding port="19301"/>
+ </service-config>
+
+
+ <!-- ********************* snmp-adaptor.sar ****************** -->
+
+ <service-config name="jboss.jmx:name=SnmpAgent,service=trapd,type=logger"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="1462"/>
+ </service-config>
+
+ <service-config name="jboss.jmx:name=SnmpAgent,service=snmp,type=adaptor"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="1461"/>
+ </service-config>
+
+
+ <!-- ********************* jbossmq-service.xml **************** -->
+
+ <!-- JMS related services -->
+ <service-config name="jboss.mq:service=InvocationLayer,type=UIL2"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="8393"/>
+ </service-config>
+
+
+ <!-- ********************* jbossmq-httpil.sar **************** -->
+ <service-config name="jboss.mq:service=InvocationLayer,type=HTTP"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="URLPort"/>
+ <binding port="8380"/>
+ </service-config>
+
+ <!-- ********************* hajndi-jms-ds.xml **************** -->
+
+ <!-- The JMS provider loader -->
+ <service-config name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <!--
+ MAKE SURE java.naming.provider.url
+ PORT IS SAME AS HA-JNDI ABOVE !!!
+ -->
+ <delegate-config>
+ <attribute name="Properties"><![CDATA[
+ java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
+ java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
+ java.naming.provider.url=${jboss.bind.address:localhost}:1400
+ jnp.disableDiscovery=false
+ jnp.partitionName=${jboss.partition.name:DefaultPartition}
+ jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
+ jnp.discoveryPort=1102
+ jnp.discoveryTTL=16
+ jnp.discoveryTimeout=5000
+ jnp.maxRetries=1
+ ]]>
+ </attribute>
+ </delegate-config>
+ <!-- NOTE: YOU MUST ADD THIS ELEMENT, BUT THE VALUE DOESN'T MATTER
+ BE SURE THE CORRECT VALUE IS IN java.naming.provider.url ABOVE -->
+ <binding port="1400"/>
+ </service-config>
+
+ <!-- **************** http-invoker.sar & httpha-invoker.sar*************** -->
+ <!-- EJBInvoker -->
+ <service-config name="jboss:service=invoker,type=http"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/EJBInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8380"/>
+ </service-config>
+
+ <!-- JMXInvoker -->
+ <service-config name="jboss:service=invoker,type=http,target=Naming"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/JMXInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8380"/>
+ </service-config>
+
+ <!-- readonly JMXInvoker -->
+ <service-config name="jboss:service=invoker,type=http,target=Naming,readonly=true"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/readonly/JMXInvokerServlet</attribute>
+ </delegate-config>
+ <!--
+ MUST BE THE SAME AS
+ TOMCAT HTTP CONNECTOR BELOW !!!
+ -->
+ <binding port="8380"/>
+ </service-config>
+
+ <!-- **************** httpha-invoker.sar*************** -->
+ <!-- EJBInvokerHA -->
+ <service-config name="jboss:service=invoker,type=httpHA"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/EJBInvokerHAServlet</attribute>
+ </delegate-config>
+ <binding port="8380"/>
+ </service-config>
+
+ <!-- JMXInvokerHA -->
+ <service-config name="jboss:service=invoker,type=http,target=HAJNDI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config>
+ <attribute name="InvokerURLSuffix">:${port}/invoker/JMXInvokerHAServlet</attribute>
+ </delegate-config>
+ <binding port="8380"/>
+ </service-config>
+
+
+
+
+ <!-- ********************* jboss-ws4ee.sar **************** -->
+
+ <!-- Web Service related services -->
+ <service-config name="jboss.ws4ee:service=AxisService"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="WebServicePort" hostName="WebServiceHost"/>
+ <binding port="8380" host="${jboss.bind.address}"/>
+ </service-config>
+
+ <!-- ********************* hsqldb-ds.xml ********************** -->
+
+ <!-- Hypersonic related services
+
+ Only if using TCP setup (local file setup by default)
+
+ <service-config name="jboss.jca:service=ManagedConnectionFactory,name=DefaultDS"
+ delegateClass="org.jboss.services.binding.XSLTConfigDelegate"
+ >
+ <delegate-config>
+ <xslt-config configName="ManagedConnectionFactoryProperties"><![CDATA[
+<xsl:stylesheet
+ xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="host"/>
+ <xsl:param name="port"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match="config-property[@name='ConnectionURL']">
+ <config-property type="java.lang.String" name="ConnectionURL">jdbc:hsqldb:hsql://<xsl:value-of select='$host'/>:<xsl:value-of select='$port'/></config-property>
+ </xsl:template>
+
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+</xsl:stylesheet>
+]]>
+ </xslt-config>
+ </delegate-config>
+ <binding host="localhost" port="1901" />
+ </service-config>
+
+ <service-config name="jboss:service=Hypersonic"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port" />
+ <binding port="1901" />
+ </service-config>
+
+ -->
+
+
+ <!-- ********************* tomcat ********************** -->
+
+ <service-config name="jboss.web:service=WebServer"
+ delegateClass="org.jboss.services.binding.XSLTFileDelegate"
+ >
+ <delegate-config>
+ <xslt-config configName="ConfigFile"><![CDATA[
+ <xsl:stylesheet
+ xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="port"/>
+
+ <xsl:variable name="portAJP" select="$port - 71"/>
+ <xsl:variable name="portHttps" select="$port + 363"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match = "Connector">
+ <Connector>
+ <xsl:for-each select="@*">
+ <xsl:choose>
+ <xsl:when test="(name() = 'port' and . = '8080')">
+ <xsl:attribute name="port"><xsl:value-of select="$port" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'port' and . = '8009')">
+ <xsl:attribute name="port"><xsl:value-of select="$portAJP" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'redirectPort')">
+ <xsl:attribute name="redirectPort"><xsl:value-of select="$portHttps" /></xsl:attribute>
+ </xsl:when>
+ <xsl:when test="(name() = 'port' and . = '8443')">
+ <xsl:attribute name="port"><xsl:value-of select="$portHttps" /></xsl:attribute>
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:attribute name="{name()}"><xsl:value-of select="." /></xsl:attribute>
+ </xsl:otherwise>
+ </xsl:choose>
+ </xsl:for-each>
+ <xsl:apply-templates/>
+ </Connector>
+ </xsl:template>
+
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+ </xsl:stylesheet>
+ ]]>
+ </xslt-config>
+ </delegate-config>
+ <binding port="8380"/>
+ </service-config>
+
+ <!-- ********************* jboss messaging ********************** -->
+
+ <service-config name="jboss.messaging:service=Connector,transport=socket"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
+ <delegate-config>
+ <attribute name="InvokerLocator">socket://${jboss.bind.address}:4757/?dataType=jms&serializationtype=jms&timeout=0&leasePeriod=20000&socket.check_connection=false&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat</attribute>
+ </delegate-config>
+ <binding port="4757"/>
+ </service-config>
+
+ </server>
+
+</service-bindings>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/asapxcess-jb3.2-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/asapxcess-jb3.2-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/asapxcess-jb3.2-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- configuration for aSAPXcess SAP adapter for jboss 3.2 -->
+<!-- ==================================================================== -->
+<!-- aSAPXcess adapter configuration for SAP R3 -->
+<!-- Contact: aif_support at asapsolutions.com -->
+<!-- -->
+<!-- ==================================================================== -->
+<connection-factories>
+ <!-- mbean for adding license in the classpath. Add absolute path for the folder containing the aSAPXcessLicense.txt file
+ i.e. file:D:/aSAPXCess_Jboss3.2/properties/ for windows
+ i.e. file:/usr/home/aSAPXCess_Jboss3.2/properties/ for linux/solaris
+ -->
+ <mbean code="org.jboss.deployment.ClasspathExtension" name="jboss.aSAPXcess:service=license">
+ <attribute name="MetadataURL">file:<add_properties_folder_path_here/></attribute>
+ </mbean>
+
+ <tx-connection-factory>
+ <depends>jboss.aSAPXcess:service=license</depends>
+ <jndi-name>aSAPXcess</jndi-name>
+ <local-transaction/>
+ <adapter-display-name>aSAPXcess</adapter-display-name>
+ <config-property name="LogConfigFile" type="java.lang.String">ASAP_SAP_1_0.xml</config-property>
+ <config-property name="RootLogContext" type="java.lang.String">ASAP_SAP_1_0</config-property>
+ <config-property name="LogLevel" type="java.lang.String">WARN</config-property>
+ <config-property name="MessageBundleBase" type="java.lang.String">ASAP_SAP_1_0</config-property>
+ <config-property name="LanguageCode" type="java.lang.String">en</config-property>
+ <config-property name="CountryCode" type="java.lang.String">US</config-property>
+ <config-property name="UserName" type="java.lang.String"></config-property>
+ <config-property name="Password" type="java.lang.String"></config-property>
+ <config-property name="ClientNumber" type="java.lang.String"></config-property>
+ <config-property name="ServerName" type="java.lang.String"></config-property>
+ <config-property name="SystemNumber" type="java.lang.String"></config-property>
+ <config-property name="GatewayServerName" type="java.lang.String"></config-property>
+ <config-property name="GatewayServiceNumber" type="java.lang.String"></config-property>
+ <config-property name="SystemName" type="java.lang.String"></config-property>
+ <config-property name="MessageServerName" type="java.lang.String"></config-property>
+ <config-property name="GroupName" type="java.lang.String"></config-property>
+ <config-property name="ConnectionURL" type="java.lang.String"></config-property>
+
+ <min-pool-size>0</min-pool-size>
+ <max-pool-size>64</max-pool-size>
+
+ <blocking-timeout-millis>5000</blocking-timeout-millis>
+ <idle-timeout-minutes>15</idle-timeout-minutes>
+
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ <!-- pooling criteria. USE AT MOST ONE-->
+ <!-- If you don't use JAAS login modules or explicit login
+ getConnection(usr,pw) but rely on user/pw specified above,
+ don't specify anything here -->
+
+ <!-- If you supply the usr/pw from a JAAS login module
+ <security-domain>MySecurityDomain</security-domain>
+ -->
+ <!-- if your app supplies the usr/pw explicitly getConnection(usr, pw)
+ <application-managed-security/>
+ -->
+ </tx-connection-factory>
+</connection-factories>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/cicsr9s-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/cicsr9s-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/cicsr9s-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- CICSR9S provided by chen_comp in the forums -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: cicsr9s-ds.xml 22595 2004-08-02 19:24:08Z ejort $ -->
+
+<connection-factories>
+
+ <tx-connection-factory>
+
+ <jndi-name>ra/cicsr9s</jndi-name>
+
+ <rar-name>cicsr9s.rar</rar-name>
+ <connection-definition>javax.resource.cci.ConnectionFactory</connection-definition>
+
+ <config-property name="ConnectionURL" type="java.lang.String">tcp://arno</config-property>
+ <config-property name="PortNumber" type="java.lang.String">2006</config-property>
+ <config-property name="ServerName" type="java.lang.String">CICSR9S</config-property>
+ <config-property name="UserName" type="java.lang.String">CICSUSER</config-property>
+
+ <max-pool-size>50</max-pool-size>
+
+ </tx-connection-factory>
+
+</connection-factories>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-400-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-400-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-400-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: db2-400-ds.xml 25096 2004-10-27 18:44:58Z pilhuhn $ -->
+
+<!-- You need the jt400.jar that is delivered with IBM iSeries Access or the
+ OpenSource Project jtopen.
+
+ [systemname] Hostame of the iSeries
+ [schema] Default schema is needed so jboss could use metadat to test if the tables exists
+ -->
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>DB2-400</jndi-name>
+ <connection-url>jdbc:as400://[systemname]/[schema];extended dynamic=true;package=jbpkg;package cache=true;package library=jboss;errors=full</connection-url>
+ <driver-class>com.ibm.as400.access.AS400JDBCDriver</driver-class>
+ <user-name>[username]</user-name>
+ <password>[password]</password>
+ <min-pool-size>0</min-pool-size>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>DB2/400</type-mapping>
+ </metadata>
+
+
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: db2-ds.xml 23720 2004-09-15 14:37:40Z loubyansky $ -->
+
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>DB2DS</jndi-name>
+ <connection-url>jdbc:db2:yourdatabase</connection-url>
+ <driver-class>COM.ibm.db2.jdbc.app.DB2Driver</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+ <min-pool-size>0</min-pool-size>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>DB2</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-jcc-xa-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-jcc-xa-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-jcc-xa-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<datasources>
+ <!--
+ IBM DB2 XA driver
+ db2jcc.jar
+ -->
+
+ <xa-datasource>
+ <jndi-name>DB2XADS</jndi-name>
+
+ <xa-datasource-class>com.ibm.db2.jcc.DB2XADataSource</xa-datasource-class>
+
+ <xa-datasource-property name="DatabaseName">your_database_name</xa-datasource-property>
+ <xa-datasource-property name="User">your_user</xa-datasource-property>
+ <xa-datasource-property name="Password">your_password</xa-datasource-property>
+
+ <!-- Note, as opposed to the Type2 driver, DB2 Type 4 requires the PortNumber. By default this is 50000-->
+ <xa-datasource-property name="PortNumber">your_port_number</xa-datasource-property>
+
+ <!-- Must be set if using multiple DB2 XA resources in same transaction -->
+
+ <isSameRM-override-value>false</isSameRM-override-value>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>DB2</type-mapping>
+ </metadata>
+
+ </xa-datasource>
+
+</datasources>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-xa-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-xa-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/db2-xa-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- Thanks to Horia Muntean <horia at bvb.ro> -->
+<!-- ===================================================================== -->
+
+<!-- $Id: db2-xa-ds.xml 58886 2006-12-06 21:19:08Z weston.price at jboss.com $ -->
+
+
+<datasources>
+ <!--
+ XADatasource for DB2 V8.1 (app driver)
+ copy $db2_install_dir/java/db2java.zip into $jboss_install_dir/server/default/lib
+ -->
+
+ <xa-datasource>
+ <jndi-name>DB2XADS</jndi-name>
+
+ <xa-datasource-class>COM.ibm.db2.jdbc.DB2XADataSource</xa-datasource-class>
+ <xa-datasource-property name="DatabaseName">your_database_name</xa-datasource-property>
+ <xa-datasource-property name="User">your_user</xa-datasource-property>
+ <xa-datasource-property name="Password">your_password</xa-datasource-property>
+
+ <!-- Must be set if using multiple DB2 XA resources in same transaction -->
+
+ <isSameRM-override-value>false</isSameRM-override-value>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>DB2</type-mapping>
+ </metadata>
+ </xa-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/derby-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/derby-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/derby-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- The Derby embedded database JCA connection factory config
+$Id: derby-ds.xml 25345 2004-11-03 13:29:58Z loubyansky $ -->
+
+
+<datasources>
+ <local-tx-datasource>
+
+ <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
+ <!-- Datasources are not available outside the virtual machine -->
+ <jndi-name>DerbyDS</jndi-name>
+
+ <!-- for in-process persistent db, saved when jboss stops. The
+ org.jboss.jdbc.DerbyDatabase mbean is necessary for properly db shutdown -->
+ <connection-url>jdbc:derby:${jboss.server.data.dir}${/}derby${/}localDB;create=true</connection-url>
+
+ <!-- The driver class -->
+ <driver-class>org.apache.derby.jdbc.EmbeddedDriver</driver-class>
+
+ <!-- The login and password -->
+ <user-name>sa</user-name>
+ <password></password>
+
+ <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
+ <min-pool-size>5</min-pool-size>
+
+ <!-- The maximum connections in a pool/sub-pool -->
+ <max-pool-size>20</max-pool-size>
+
+ <!-- The time before an unused connection is destroyed -->
+ <idle-timeout-minutes>5</idle-timeout-minutes>
+
+ <!-- Whether to check all statements are closed when the connection is returned to the pool,
+ this is a debugging feature that should be turned off in production -->
+ <track-statements/>
+
+ <!-- This mbean can be used when using in process persistent derby -->
+ <depends>jboss:service=Derby</depends>
+ </local-tx-datasource>
+
+ <mbean code="org.jboss.jdbc.DerbyDatabase" name="jboss:service=Derby"/>
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/facets-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/facets-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/facets-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+ <!-- ====================================================================
+ Facets service description for JBoss 3.0
+
+ This file and the lib/facetsAdapter.rar archive should be copied to
+ the "deploy" directory of your JBoss server.
+
+ Configurable sections are
+ <config-property> elements
+ ManagedConnectionPool attributes
+ <authentication> element
+ ==================================================================== -->
+
+<connection-factories>
+
+ <tx-connection-factory>
+
+ <jndi-name>Facets</jndi-name>
+
+ <xa-transaction/>
+
+ <track-connection-by-tx/>
+
+ <attribute name="JndiName">Facets</attribute>
+
+ <adapter-display-name>GemStone_Facets</adapter-display-name>
+
+ <!--
+ <config-property name="DefaultUser" type="java.lang.String">so-and-so</config-property>
+ -->
+
+ <!--
+ <config-property name="DefaultPassword" type="java.lang.String">secret</config-property>
+ -->
+
+ <!--
+ <config-property name="SessionConfigFile" type="java.lang.String"></config-property>
+ -->
+
+ <config-property name="Verbose" type="java.lang.String"></config-property>
+
+ <config-property name="Debug" type="java.lang.String"></config-property>
+
+ </tx-connection-factory>
+
+</connection-factories>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/fastobjects-jboss32-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/fastobjects-jboss32-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/fastobjects-jboss32-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!--
+ this file contains the configuration for using
+ the FastObjects t7 resource adapter with JBoss 3.2.1,
+ note, that the MBean name for JaasSecurityManager differs between JBoss 3.0.0 and 3.0.4
+
+ make sure, that the FastObjects native libraries can be loaded (Windows:
+ runtime/bin of your FastObjects-Installation must be contained in PATH)
+ and that jdo.jar is copied into the default\lib-directory.
+
+ Place this file and the RAR-file into the default\deploy directory.
+
+-->
+
+<connection-factories>
+
+
+
+ <tx-connection-factory>
+ <jndi-name>t7Connector</jndi-name>
+
+ <local-transaction/>
+ <adapter-display-name>t7-jdo</adapter-display-name>
+
+ <config-property name="ConnectionURL" type="java.lang.String">FastObjects://localhost/myBase</config-property>
+ <config-property name="TransactionDemarcation" type="java.lang.String">ContainerManaged</config-property>
+ <config-property name="VerboseMode" type="java.lang.String">0</config-property>
+
+ <min-pool-size>5</min-pool-size>
+ <max-pool-size>50</max-pool-size>
+ <blocking-timeout-millis>5000</blocking-timeout-millis>
+ <idle-timeout-minutes>15</idle-timeout-minutes>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+
+ </tx-connection-factory>
+</connection-factories>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/firebird-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/firebird-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/firebird-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+ <!-- $Id: firebird-ds.xml 41641 2006-03-02 17:41:11Z dimitris $ -->
+
+ <!-- ==================================================================== -->
+ <!-- New ConnectionManager setup for firebird dbs using jca-jdbc xa driver-->
+ <!-- Build jmx-api (build/build.sh all) and view for config documentation -->
+ <!-- ==================================================================== -->
+
+<connection-factories>
+
+ <!--FBManager can be used to create and drop databases.
+ Drop is especially useful during testing, since it
+ assures a clean start next time. -->
+ <mbean code="org.firebirdsql.management.FBManager" name="jboss.jca:service=FirebirdManager">
+ <attribute name="FileName">${jboss.server.data.dir}${/}fbtest.gdb</attribute>
+ <attribute name="UserName">sysdba</attribute>
+ <attribute name="Password">masterkey</attribute>
+ <attribute name="CreateOnStart">true</attribute>
+ <attribute name="DropOnStop">false</attribute>
+ </mbean>
+
+ <tx-connection-factory>
+ <jndi-name>FIrebirdDS</jndi-name>
+ <xa-transaction/>
+ <track-connection-by-tx/>
+ <rar-name>firebirdsql.rar</rar-name>
+ <connection-definition>javax.sql.DataSource</connection-definition>
+ <config-property name="Database" type="java.lang.String">localhost/3050:${jboss.server.data.dir}${/}fbtest.gdb</config-property>
+ <user-name>sysdba</user-name>
+ <password>masterkey</password>
+ <!--additional properties. only use one way of setting tx isolation, please
+ <config-property name="TransactionIsolation"></config-property>
+ <config-property name="TransactionIsolationName">TRANSACTION_READ_COMMITTED</config-property>
+ <config-property name="BlobBufferLength"></config-property>
+ <config-property name="Encoding">UNICODE_FSS</config-property>
+ -->
+ <min-pool-size>0</min-pool-size>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>Firebird</type-mapping>
+ </metadata>
+ </tx-connection-factory>
+
+</connection-factories>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/generic-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/generic-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/generic-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,105 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- Generic datasource configuration showing all possibilities -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: generic-ds.xml 16783 2003-09-05 16:39:28Z patriot1burke $ -->
+
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>GenericDS</jndi-name>
+ <connection-url>[jdbc: url for use with Driver class]</connection-url>
+ <driver-class>[fully qualified class name of java.sql.Driver implementation]</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+ <!-- you can include connection properties that will get passed in
+ the DriverManager.getConnection(props) call-->
+ <!-- look at your Driver docs to see what these might be -->
+ <connection-property name="char.encoding">UTF-8</connection-property>
+ <transaction-isolation>TRANSACTION_SERIALIZABLE</transaction-isolation>
+
+ <!--pooling parameters-->
+ <min-pool-size>5</min-pool-size>
+ <max-pool-size>100</max-pool-size>
+ <blocking-timeout-millis>5000</blocking-timeout-millis>
+ <idle-timeout-minutes>15</idle-timeout-minutes>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+
+ <!-- pooling criteria. USE AT MOST ONE-->
+ <!-- If you don't use JAAS login modules or explicit login
+ getConnection(usr,pw) but rely on user/pw specified above,
+ don't specify anything here -->
+
+ <!-- If you supply the usr/pw from a JAAS login module -->
+ <security-domain>MyRealm</security-domain>
+
+ <!-- if your app supplies the usr/pw explicitly getConnection(usr, pw) -->
+ <application-managed-security/>
+
+ <!--Anonymous depends elements are copied verbatim into the ConnectionManager mbean config-->
+ <depends>myapp.service:service=DoSomethingService</depends>
+
+ </local-tx-datasource>
+
+ <!-- you can include regular mbean configurations like this one -->
+ <mbean code="org.jboss.tm.XidFactory"
+ name="jboss:service=XidFactory">
+ <attribute name="Pad">true</attribute>
+ </mbean>
+
+
+ <!-- Here's an xa example -->
+ <xa-tx-datasource>
+ <jndi-name>GenericXADS</jndi-name>
+ <xa-datasource-class>[fully qualified name of class implementing javax.sql.XADataSource goes here]</xa-datasource-class>
+ <xa-datasource-property name="SomeProperty">SomePropertyValue</xa-datasource-property>
+ <xa-datasource-property name="SomeOtherProperty">SomeOtherValue</xa-datasource-property>
+
+ <user-name>x</user-name>
+ <password>y</password>
+ <transaction-isolation>TRANSACTION_SERIALIZABLE</transaction-isolation>
+
+
+
+ <!--pooling parameters-->
+ <min-pool-size>5</min-pool-size>
+ <max-pool-size>100</max-pool-size>
+ <blocking-timeout-millis>5000</blocking-timeout-millis>
+ <idle-timeout-minutes>15</idle-timeout-minutes>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+
+ <!-- pooling criteria. USE AT MOST ONE-->
+ <!-- If you don't use JAAS login modules or explicit login
+ getConnection(usr,pw) but rely on user/pw specified above,
+ don't specify anything here -->
+
+ <!-- If you supply the usr/pw from a JAAS login module -->
+ <security-domain/>
+
+ <!-- if your app supplies the usr/pw explicitly getConnection(usr, pw) -->
+ <application-managed-security/>
+
+ </xa-tx-datasource>
+
+
+
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hajndi-jms-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hajndi-jms-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hajndi-jms-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<connection-factories>
+
+ <!-- ==================================================================== -->
+ <!-- JMS Stuff -->
+ <!-- ==================================================================== -->
+
+ <!-- The JMS provider loader -->
+ <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
+ name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider">
+ <attribute name="ProviderName">DefaultJMSProvider</attribute>
+ <attribute name="ProviderAdapterClass">
+ org.jboss.jms.jndi.JNDIProviderAdapter
+ </attribute>
+ <!-- The combined connection factory -->
+ <attribute name="FactoryRef">XAConnectionFactory</attribute>
+ <!-- The queue connection factory -->
+ <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
+ <!-- The topic factory -->
+ <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
+ <!-- Access JMS via HAJNDI -->
+ <attribute name="Properties">
+ java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
+ java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
+ java.naming.provider.url=${jboss.bind.address:localhost}:1100
+ jnp.disableDiscovery=false
+ jnp.partitionName=${jboss.partition.name:DefaultPartition}
+ jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
+ jnp.discoveryPort=1102
+ jnp.discoveryTTL=16
+ jnp.discoveryTimeout=5000
+ jnp.maxRetries=1
+ </attribute>
+ </mbean>
+
+ <!-- The server session pool for Message Driven Beans -->
+ <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
+ name="jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool">
+ <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
+ <attribute name="PoolName">StdJMSPool</attribute>
+ <attribute name="PoolFactoryClass">
+ org.jboss.jms.asf.StdServerSessionPoolFactory
+ </attribute>
+ </mbean>
+
+ <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
+ <tx-connection-factory>
+ <jndi-name>JmsXA</jndi-name>
+ <xa-transaction/>
+ <rar-name>jms-ra.rar</rar-name>
+ <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
+ <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
+ <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
+ <max-pool-size>20</max-pool-size>
+ <security-domain-and-application>JmsXARealm</security-domain-and-application>
+ </tx-connection-factory>
+
+</connection-factories>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hsqldb-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hsqldb-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hsqldb-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,113 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- The Hypersonic embedded database JCA connection factory config -->
+
+<!-- $Id: hsqldb-ds.xml 39791 2006-01-10 18:14:42Z dimitris $ -->
+
+<datasources>
+ <local-tx-datasource>
+
+ <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
+ <!-- Datasources are not available outside the virtual machine -->
+ <jndi-name>DefaultDS</jndi-name>
+
+ <!-- For server mode db, allowing other processes to use hsqldb over tcp.
+ This requires the org.jboss.jdbc.HypersonicDatabase mbean.
+ <connection-url>jdbc:hsqldb:hsql://${jboss.bind.address}:1701</connection-url>
+ -->
+ <!-- For totally in-memory db, not saved when jboss stops.
+ The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
+ <connection-url>jdbc:hsqldb:.</connection-url>
+ -->
+ <!-- For in-process persistent db, saved when jboss stops.
+ The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
+ -->
+ <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB</connection-url>
+
+ <!-- The driver class -->
+ <driver-class>org.hsqldb.jdbcDriver</driver-class>
+
+ <!-- The login and password -->
+ <user-name>sa</user-name>
+ <password></password>
+
+ <!--example of how to specify class that determines if exception means connection should be destroyed-->
+ <!--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyExceptionSorter</exception-sorter-class-name-->
+
+ <!-- this will be run before a managed connection is removed from the pool for use by a client-->
+ <!--<check-valid-connection-sql>select * from something</check-valid-connection-sql> -->
+
+ <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
+ <min-pool-size>5</min-pool-size>
+
+ <!-- The maximum connections in a pool/sub-pool -->
+ <max-pool-size>20</max-pool-size>
+
+ <!-- The time before an unused connection is destroyed -->
+ <!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout after last use -->
+ <!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads on closed connections -->
+ <idle-timeout-minutes>0</idle-timeout-minutes>
+
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ <!-- example of how to specify a class that determines a connection is valid before it is handed out from the pool
+ <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyValidConnectionChecker</valid-connection-checker-class-name>
+ -->
+
+ <!-- Whether to check all statements are closed when the connection is returned to the pool,
+ this is a debugging feature that should be turned off in production -->
+ <track-statements/>
+
+ <!-- Use the getConnection(user, pw) for logins
+ <application-managed-security/>
+ -->
+
+ <!-- Use the security domain defined in conf/login-config.xml -->
+ <security-domain>HsqlDbRealm</security-domain>
+
+ <!-- Use the security domain defined in conf/login-config.xml or the
+ getConnection(user, pw) for logins. The security domain takes precedence.
+ <security-domain-and-application>HsqlDbRealm</security-domain-and-application>
+ -->
+
+ <!-- HSQL DB benefits from prepared statement caching -->
+ <prepared-statement-cache-size>32</prepared-statement-cache-size>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>Hypersonic SQL</type-mapping>
+ </metadata>
+
+ <!-- When using in-process (standalone) mode -->
+ <depends>jboss:service=Hypersonic,database=localDB</depends>
+ <!-- Uncomment when using hsqldb in server mode
+ <depends>jboss:service=Hypersonic</depends>
+ -->
+ </local-tx-datasource>
+
+ <!-- Uncomment if you want hsqldb accessed over tcp (server mode)
+ <mbean code="org.jboss.jdbc.HypersonicDatabase"
+ name="jboss:service=Hypersonic">
+ <attribute name="Port">1701</attribute>
+ <attribute name="BindAddress">${jboss.bind.address}</attribute>
+ <attribute name="Silent">true</attribute>
+ <attribute name="Database">default</attribute>
+ <attribute name="Trace">false</attribute>
+ <attribute name="No_system_exit">true</attribute>
+ </mbean>
+ -->
+
+ <!-- For hsqldb accessed from jboss only, in-process (standalone) mode -->
+ <mbean code="org.jboss.jdbc.HypersonicDatabase"
+ name="jboss:service=Hypersonic,database=localDB">
+ <attribute name="Database">localDB</attribute>
+ <attribute name="InProcessMode">true</attribute>
+ </mbean>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hsqldb-encrypted-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hsqldb-encrypted-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/hsqldb-encrypted-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,148 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- The Hypersonic embedded database JCA connection factory config -->
+<!-- that illustrates the use of the JaasSecurityDomainIdentityLoginModule -->
+<!-- to use encrypted password in the data source configuration. -->
+
+<!-- $Id: hsqldb-encrypted-ds.xml 39791 2006-01-10 18:14:42Z dimitris $ -->
+
+<datasources>
+ <local-tx-datasource>
+
+ <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
+ <!-- Datasources are not available outside the virtual machine -->
+ <jndi-name>DefaultDS</jndi-name>
+
+ <!-- For server mode db, allowing other processes to use hsqldb over tcp.
+ This requires the org.jboss.jdbc.HypersonicDatabase mbean.
+ <connection-url>jdbc:hsqldb:hsql://${jboss.bind.address}:1701</connection-url>
+ -->
+ <!-- For totally in-memory db, not saved when jboss stops.
+ The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
+ <connection-url>jdbc:hsqldb:.</connection-url>
+ -->
+ <!-- For in-process persistent db, saved when jboss stops.
+ The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
+ -->
+ <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB</connection-url>
+
+ <!-- The driver class -->
+ <driver-class>org.hsqldb.jdbcDriver</driver-class>
+
+ <!--example of how to specify class that determines if exception means connection should be destroyed-->
+ <!--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyExceptionSorter</exception-sorter-class-name-->
+
+ <!-- this will be run before a managed connection is removed from the pool for use by a client-->
+ <!--<check-valid-connection-sql>select * from something</check-valid-connection-sql> -->
+
+ <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
+ <min-pool-size>5</min-pool-size>
+
+ <!-- The maximum connections in a pool/sub-pool -->
+ <max-pool-size>20</max-pool-size>
+
+ <!-- The time before an unused connection is destroyed -->
+ <!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout after last use -->
+ <!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads on closed connections -->
+ <idle-timeout-minutes>0</idle-timeout-minutes>
+
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ <!-- example of how to specify a class that determines a connection is valid before it is handed out from the pool
+ <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyValidConnectionChecker</valid-connection-checker-class-name>
+ -->
+
+ <!-- Whether to check all statements are closed when the connection is returned to the pool,
+ this is a debugging feature that should be turned off in production -->
+ <track-statements/>
+
+ <!-- Use the getConnection(user, pw) for logins
+ <application-managed-security/>
+ -->
+
+ <!-- Use the security domain defined in conf/login-config.xml -->
+ <security-domain>EncryptedHsqlDbRealm</security-domain>
+
+ <!-- Use the security domain defined in conf/login-config.xml or the
+ getConnection(user, pw) for logins. The security domain takes precedence.
+ <security-domain-and-application>HsqlDbRealm</security-domain-and-application>
+ -->
+
+ <!-- HSQL DB benefits from prepared statement caching -->
+ <prepared-statement-cache-size>32</prepared-statement-cache-size>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>Hypersonic SQL</type-mapping>
+ </metadata>
+
+ <!-- When using in-process (standalone) mode -->
+ <depends>jboss:service=Hypersonic,database=localDB</depends>
+ <!-- Uncomment when using hsqldb in server mode
+ <depends>jboss:service=Hypersonic</depends>
+ -->
+ </local-tx-datasource>
+
+ <!-- The JaasSecurityDomain used for encryption. Use the name
+ "jboss.security:service=JaasSecurityDomain,domain=ServerMasterPassword"
+ as the value of the JaasSecurityDomainIdentityLoginModule
+ jaasSecurityDomain login module option in the EncryptedHsqlDbRealm
+ login-config.xml section. Typically this service config should be in
+ the conf/jboss-service.xml descriptor.
+ The opaque master.password file could be created using:
+ java -cp jbosssx.jar org.jboss.security.plugins.FilePassword 12345678 17 master server.password
+
+ The corresponding login-config.xml would look like:
+ <application-policy name = "EncryptedHsqlDbRealm">
+ <authentication>
+ <login-module code = "org.jboss.resource.security.JaasSecurityDomainIdentityLoginModule"
+ flag = "required">
+ <module-option name = "username">sa</module-option>
+ <module-option name = "password">E5gtGMKcXPP</module-option>
+ <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=DefaultDS</module-option>
+ <module-option name = "jaasSecurityDomain">jboss.security:service=JaasSecurityDomain,domain=ServerMasterPassword</module-option>
+ </login-module>
+ </authentication>
+ </application-policy>
+ where the encrypted password was generated using:
+ java -cp jbosssx.jar org.jboss.security.plugins.PBEUtils abcdefgh 13 master ''
+ Encoded password: E5gtGMKcXPP
+ -->
+ <mbean code="org.jboss.security.plugins.JaasSecurityDomain"
+ name="jboss.security:service=JaasSecurityDomain,domain=ServerMasterPassword">
+ <constructor>
+ <arg type="java.lang.String" value="ServerMasterPassword"/>
+ </constructor>
+ <!-- The opaque master password file used to decrypt the encrypted
+ database password key -->
+ <attribute name="KeyStorePass">{CLASS}org.jboss.security.plugins.FilePassword:${jboss.server.home.dir}/conf/server.password</attribute>
+ <attribute name="Salt">abcdefgh</attribute>
+ <attribute name="IterationCount">13</attribute>
+ </mbean>
+
+ <!-- Uncomment if you want hsqldb accessed over tcp (server mode)
+ <mbean code="org.jboss.jdbc.HypersonicDatabase"
+ name="jboss:service=Hypersonic">
+ <attribute name="Port">1701</attribute>
+ <attribute name="BindAddress">${jboss.bind.address}</attribute>
+ <attribute name="Silent">true</attribute>
+ <attribute name="Database">default</attribute>
+ <attribute name="Trace">false</attribute>
+ <attribute name="No_system_exit">true</attribute>
+ </mbean>
+ -->
+
+ <!-- For hsqldb accessed from jboss only, in-process (standalone) mode -->
+ <mbean code="org.jboss.jdbc.HypersonicDatabase"
+ name="jboss:service=Hypersonic,database=localDB">
+ <attribute name="Database">localDB</attribute>
+ <attribute name="InProcessMode">true</attribute>
+ </mbean>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/informix-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/informix-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/informix-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: informix-ds.xml 26270 2004-12-01 11:46:00Z schrouf $ -->
+
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>InformixDS</jndi-name>
+ <connection-url>jdbc:informix-sqli://myhost.mydomain.com:1557/mydb:INFORMIXSERVER=myserver</connection-url>
+ <driver-class>com.informix.jdbc.IfxDriver</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+ <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.InformixExceptionSorter</exception-sorter-class-name>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>InformixDB</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/informix-xa-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/informix-xa-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/informix-xa-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: informix-xa-ds.xml 26270 2004-12-01 11:46:00Z schrouf $ -->
+
+
+<datasources>
+ <xa-datasource>
+ <jndi-name>InformixXADS</jndi-name>
+ <xa-datasource-class>com.informix.jdbcx.IfxXADataSource</xa-datasource-class>
+ <!-- Not supported by latter drivers
+ <xa-datasource-property name="IfxWAITTIME">10</xa-datasource-property>
+ -->
+ <xa-datasource-property name="Description">Something Descriptive</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>
+ <xa-datasource-property name="User">username</xa-datasource-property>
+ <xa-datasource-property name="Password">password</xa-datasource-property>
+ <user-name>x</user-name>
+ <password>y</password>
+ <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.InformixExceptionSorter</exception-sorter-class-name>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>InformixDB</type-mapping>
+ </metadata>
+ </xa-datasource>
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jdatastore-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jdatastore-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jdatastore-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: jdatastore-ds.xml 8941 2002-07-22 22:57:24Z d_jencks $ -->
+<!-- ==================================================================== -->
+<!-- Copy these jar's from your JBuilder6/lib to your jboss's lib -->
+<!-- dx.jar,jdsserver.jar,jds.jar -->
+<!-- Originally from Brent Thompson www.protegra.com/javagroup.html -->
+<!-- ==================================================================== -->
+
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>JDataStoreDS</jndi-name>
+ <connection-url>jdbc:borland:dslocal:/home/brent/JBuilder6/samples/JDataStore/datastores/employee.jds</connection-url>
+ <driver-class>com.borland.datastore.jdbc.DataStoreDriver</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jms-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jms-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jms-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<connection-factories>
+
+ <!-- ==================================================================== -->
+ <!-- JMS Stuff -->
+ <!-- ==================================================================== -->
+
+ <!-- The JMS provider loader -->
+ <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
+ name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
+ <attribute name="ProviderName">DefaultJMSProvider</attribute>
+ <attribute name="ProviderAdapterClass">
+ org.jboss.jms.jndi.JNDIProviderAdapter
+ </attribute>
+ <!-- The combined connection factory -->
+ <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
+ <!-- The queue connection factory -->
+ <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
+ <!-- The topic factory -->
+ <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
+ <!-- Uncomment to use HAJNDI to access JMS
+ <attribute name="Properties">
+ java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
+ java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
+ java.naming.provider.url=localhost:1100
+ </attribute>
+ -->
+ </mbean>
+
+ <!-- The server session pool for Message Driven Beans -->
+ <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
+ name="jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool">
+ <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
+ <attribute name="PoolName">StdJMSPool</attribute>
+ <attribute name="PoolFactoryClass">
+ org.jboss.jms.asf.StdServerSessionPoolFactory
+ </attribute>
+ </mbean>
+
+ <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
+ <tx-connection-factory>
+ <jndi-name>JmsXA</jndi-name>
+ <xa-transaction/>
+ <rar-name>jms-ra.rar</rar-name>
+ <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
+ <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
+ <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
+ <max-pool-size>20</max-pool-size>
+ <security-domain-and-application>JmsXARealm</security-domain-and-application>
+ </tx-connection-factory>
+
+</connection-factories>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jsql-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jsql-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/jsql-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: jsql-ds.xml 17519 2003-10-30 09:53:25Z ejort $ -->
+
+ <!-- ======================================================================-->
+ <!-- ConnectionManager setup for JSQL Microsoft SQL Server 2000 driver -->
+ <!-- ===================================================================== -->
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>JSQLDS</jndi-name>
+ <connection-url>jdbc:JSQLConnect://localhost:1433/databaseName=testdb</connection-url>
+ <driver-class>com.jnetdirect.jsql.JSQLDriver</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/lido-versant-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/lido-versant-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/lido-versant-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,98 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+ <!-- ==================================================================== -->
+ <!-- ConnectionManager setup for LiDO jdo using Versant object db.-->
+ <!-- Build jmx-api (build/build.sh all) and view for config documentation -->
+ <!-- ==================================================================== -->
+
+<service>
+
+ <!-- the enhanced classes must already be deployed before this adapter is started. Currently
+ LiDO does not work with jboss to find the metadata.jdo if it is in a jar file, so you must
+ put it on the classpath independently as a file. The license can be added similarly -->
+
+ <!-- as of LiDO build 17 it is necessary that all metadata be in one metadata.jdo file. -->
+
+ <!--Specify the metadata file name and get the metadata file on the classpath.
+ Hopefully LiDO will make this a ManagedConnectionFactory property soon.-->
+ <mbean code="org.jboss.deployment.ClasspathExtension" name="jboss.jdo.lido:service=metadata">
+ <attribute name="MetadataURL">file:/usr/java/fgm/co4copy/tracker2/domain/src/resources/</attribute>
+ </mbean>
+
+ <mbean code="org.jboss.deployment.ClasspathExtension" name="jboss.jdo.lido:service=license">
+ <attribute name="MetadataURL">file:/usr/java/lido/bin/</attribute>
+ </mbean>
+
+ <mbean code="org.jboss.resource.connectionmanager.XATxConnectionManager" name="jboss.jca:service=XaTxCM,name=LiDOVersantDS">
+
+ <!--depend on the metadata helper-->
+ <depends>jboss.jdo.lido:service=metadata</depends>
+ <depends>jboss.jdo.lido:service=license</depends>
+
+
+ <attribute name="JndiName">adap_1</attribute>
+ <depends optional-attribute-name="ManagedConnectionPool">
+ <mbean code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" name="jboss.jca:service=XaTxPool,name=LiDOVersantDS">
+
+ <depends optional-attribute-name="ManagedConnectionFactoryName">
+ <mbean code="org.jboss.resource.connectionmanager.RARDeployment" name="jboss.jca:service=XaTxDS,name=LiDOVersantDS">
+ <!--more hack-->
+ <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=LiDO</depends>
+ <attribute name="ManagedConnectionFactoryProperties">
+ <properties>
+ <config-property name="ConnectionDriverName" type="java.lang.String">versant</config-property>
+ <config-property name="ConnectionURL" type="java.lang.String">trackerdb</config-property>
+ <!--config-property name="ConnectionDriverName" type="java.lang.String">fdb</config-property>
+ <config-property name="ConnectionURL" type="java.lang.String">/usr/java/lido/samples/company_basic/fdb.properties</config-property-->
+ <config-property name="ConnectionUserName" type="java.lang.String">david</config-property>
+ <config-property name="ConnectionPassword" type="java.lang.String">david</config-property>
+ </properties>
+ </attribute>
+ </mbean>
+
+ </depends>
+ <attribute name="MinSize">0</attribute>
+ <attribute name="MaxSize">50</attribute>
+ <attribute name="BlockingTimeoutMillis">5000</attribute>
+ <attribute name="IdleTimeoutMinutes">15</attribute>
+ <!--criteria indicates if Subject (from security domain) or app supplied
+ parameters (such as from getConnection(user, pw)) are used to distinguish
+ connections in the pool. Choices are
+ ByContainerAndApplication (use both),
+ ByContainer (use Subject),
+ ByApplication (use app supplied params only),
+ ByNothing (all connections are equivalent, usually if adapter supports
+ reauthentication)-->
+ <attribute name="Criteria">ByContainer</attribute>
+ </mbean>
+ </depends>
+ <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>
+ <!-- Include a login module configuration named FirebirdDBRealm.
+ Update your login-conf.xml, here is an example for a
+ ConfiguredIdentityLoginModule:
+
+ <application-policy name = "LiDOVersantDSBRealm">
+ <authentication>
+ <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
+ <module-option name = "principal">sysdba</module-option>
+ <module-option name = "userName">sysdba</module-option>
+ <module-option name = "password">masterkey</module-option>
+ <module-option name = "managedConnectionFactoryName">jboss.jca:service=XaTxCM,name=LiDOVersantDS</module-option>
+ </login-module>
+ </authentication>
+ </application-policy>
+
+ NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
+ module-option name = "managedConnectionFactoryName"
+ must match the object name of the ConnectionManager you are configuring here.
+ -->
+ <!--comment out this line if you want component managed security or want
+ to use the default values in the ManagedConnectionFactoryProperties - ->
+ <attribute name="SecurityDomainJndiName">LiDOVersantDSRealm</attribute-->
+
+ <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager</depends>
+
+ <attribute name="TransactionManager">java:/TransactionManager</attribute>
+ </mbean>
+
+</service>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mimer-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mimer-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mimer-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: mimer-ds.xml 23720 2004-09-15 14:37:40Z loubyansky $ -->
+
+<!-- ==================================================================== -->
+<!-- ConnectionManager setup for Mimer SQL for local transactions -->
+<!-- -->
+<!-- Supplied by fredrik.alund at upright.se -->
+<!-- ==================================================================== -->
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>MimerDS</jndi-name>
+ <driver-class>com.mimer.jdbc.Driver</driver-class>
+ <connection-url>jdbc:mimer:multi1</connection-url>
+ <user-name>changeme</user-name>
+ <password>changeme</password>
+ <min-pool-size>5</min-pool-size>
+ <max-pool-size>100</max-pool-size>
+ <blocking-timeout-millis>5000</blocking-timeout-millis>
+ <idle-timeout-minutes>15</idle-timeout-minutes>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>Mimer SQL</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mimer-xa-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mimer-xa-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mimer-xa-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: mimer-xa-ds.xml 23720 2004-09-15 14:37:40Z loubyansky $ -->
+
+<!-- ==================================================================== -->
+<!-- ConnectionManager setup for Mimer SQL for distributed transactions -->
+<!-- -->
+<!-- Requires version 9 -->
+<!-- -->
+<!-- Supplied by fredrik.alund at upright.se -->
+<!-- ==================================================================== -->
+
+<datasources>
+ <xa-datasource>
+ <jndi-name>XAMimerDS</jndi-name>
+ <xa-datasource-class>com.mimer.jdbc.MimerXADataSource</xa-datasource-class>
+ <xa-datasource-property name="DatabaseName">multi1</xa-datasource-property>
+ <xa-datasource-property name="ServerName">localhost</xa-datasource-property>
+ <xa-datasource-property name="PortNumber">1360</xa-datasource-property>
+ <user-name>changeme</user-name>
+ <password>changeme</password>
+ <min-pool-size>5</min-pool-size>
+ <max-pool-size>100</max-pool-size>
+ <blocking-timeout-millis>5000</blocking-timeout-millis>
+ <idle-timeout-minutes>15</idle-timeout-minutes>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>Mimer SQL</type-mapping>
+ </metadata>
+ </xa-datasource>
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/msaccess-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/msaccess-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/msaccess-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: msaccess-ds.xml 8941 2002-07-22 22:57:24Z d_jencks $ -->
+<!-- ==================================================================== -->
+<!-- This uses the sun jdbc-odbc driver, so don't expect miracles -->
+<!-- Thanks to Alan Moor, who warns... -->
+<!-- Remember, though, never trust critical data, or data that you can't -->
+<!-- afford to lose, or data that you need quick access to, or data that -->
+<!-- needs to be secure, to Microsoft Access. -->
+<!-- ===================================================================== -->
+
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>MSAccessDS</jndi-name>
+ <!-- format of URL is "jdbc:odbc:DSNNAME" -->
+ <connection-url>jdbc:odbc:INsightDSN</connection-url>
+ <driver-class>sun.jdbc.odbc.JdbcOdbcDriver</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mssql-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mssql-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mssql-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: mssql-ds.xml 61002 2007-02-28 16:13:00Z weston.price at jboss.com $ -->
+
+ <!-- ======================================================================-->
+ <!-- New ConnectionManager setup for Microsoft SQL Server 2005 driver -->
+ <!-- Further information about the Microsoft JDBC Driver version 1.1 -->
+ <!-- can be found here: -->
+ <!-- http://msdn2.microsoft.com/en-us/library/aa496082.aspx -->
+ <!-- ===================================================================== -->
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>MSSQLDS</jndi-name>
+ <connection-url>jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=MyDatabase</connection-url>
+ <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>MS SQLSERVER2000</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mssql-xa-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mssql-xa-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mssql-xa-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: mssql-xa-ds.xml 61002 2007-02-28 16:13:00Z weston.price at jboss.com $ -->
+ <!-- ==================================================================== -->
+ <!-- ConnectionManager setup for xa Microsoft SQL Server 2005, using -->
+ <!-- Microsoft's JDBC driver. -->
+ <!-- Thanks to Benjamin Geer <benjamin.geer at misys.com> -->
+ <!-- Be sure to set the JndiName property to the name you want to look up -->
+ <!-- the datasource under and set the location of your database in -->
+ <!-- the xa-datasource-property section. -->
+ <!-- Further information about the Microsoft JDBC Driver version 1.1 -->
+ <!-- can be found here: -->
+ <!-- http://msdn2.microsoft.com/en-us/library/aa496082.aspx -->
+ <!-- ==================================================================== -->
+
+
+<datasources>
+ <xa-datasource>
+ <jndi-name>MSSQLXADS</jndi-name>
+ <track-connection-by-tx/>
+ <isSameRM-override-value>false</isSameRM-override-value>
+ <xa-datasource-class>com.microsoft.sqlserver.jdbc.SQLServerXADataSource</xa-datasource-class>
+ <xa-datasource-property name="ServerName">myserver</xa-datasource-property>
+ <xa-datasource-property name="DatabaseName">mydatabase</xa-datasource-property>
+ <xa-datasource-property name="SelectMethod">cursor</xa-datasource-property>
+<!-- not sure if these should be here-->
+ <user-name>x</user-name>
+ <password>y</password>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>MS SQLSERVER2000</type-mapping>
+ </metadata>
+ </xa-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mysql-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mysql-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/mysql-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: mysql-ds.xml 41016 2006-02-07 14:23:00Z acoliver $ -->
+<!-- Datasource config for MySQL using 3.0.9 available from:
+http://www.mysql.com/downloads/api-jdbc-stable.html
+-->
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>MySqlDS</jndi-name>
+ <connection-url>jdbc:mysql://mysql-hostname:3306/jbossdb</connection-url>
+ <driver-class>com.mysql.jdbc.Driver</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+ <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
+ <!-- should only be used on drivers after 3.22.1 with "ping" support
+ <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
+ -->
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+ <!-- sql to call on an existing pooled connection when it is obtained from pool - MySQLValidConnectionChecker is preferred for newer drivers
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>mySQL</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+</datasources>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/oracle-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/oracle-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/oracle-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: oracle-ds.xml 23720 2004-09-15 14:37:40Z loubyansky $ -->
+<!-- ==================================================================== -->
+<!-- Datasource config for Oracle originally from Steven Coy -->
+<!-- ==================================================================== -->
+
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>OracleDS</jndi-name>
+ <connection-url>jdbc:oracle:thin:@youroraclehost:1521:yoursid</connection-url>
+ <!--
+
+ Here are a couple of the possible OCI configurations.
+ For more information, see http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/java.920/a96654/toc.htm
+
+ <connection-url>jdbc:oracle:oci:@youroracle-tns-name</connection-url>
+ or
+ <connection-url>jdbc:oracle:oci:@(description=(address=(host=youroraclehost)(protocol=tcp)(port=1521))(connect_data=(SERVICE_NAME=yourservicename)))</connection-url>
+
+ Clearly, its better to have TNS set up properly.
+ -->
+ <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+ <!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool -->
+ <!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name-->
+ <!-- Checks the Oracle error codes and messages for fatal errors -->
+ <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool - the OracleValidConnectionChecker is prefered
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>Oracle9i</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/oracle-xa-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/oracle-xa-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/oracle-xa-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: oracle-xa-ds.xml 23720 2004-09-15 14:37:40Z loubyansky $ -->
+
+<!-- ===================================================================== -->
+<!-- ATTENTION: DO NOT FORGET TO SET Pad=true IN transaction-service.xml -->
+<!-- ===================================================================== -->
+
+<datasources>
+ <xa-datasource>
+ <jndi-name>XAOracleDS</jndi-name>
+ <track-connection-by-tx/>
+ <isSameRM-override-value>false</isSameRM-override-value>
+ <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
+ <xa-datasource-property name="URL">jdbc:oracle:oci8:@tc</xa-datasource-property>
+ <xa-datasource-property name="User">scott</xa-datasource-property>
+ <xa-datasource-property name="Password">tiger</xa-datasource-property>
+ <!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool -->
+ <!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name-->
+ <!-- Checks the Oracle error codes and messages for fatal errors -->
+ <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
+ <!-- Oracles XA datasource cannot reuse a connection outside a transaction once enlisted in a global transaction and vice-versa -->
+ <no-tx-separate-pools/>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>Oracle9i</type-mapping>
+ </metadata>
+ </xa-datasource>
+
+ <mbean code="org.jboss.resource.adapter.jdbc.vendor.OracleXAExceptionFormatter"
+ name="jboss.jca:service=OracleXAExceptionFormatter">
+ <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends>
+ </mbean>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/pointbase-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/pointbase-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/pointbase-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- Example of the pointbase 4.8 datasource configuration -->
+<!-- $Id: pointbase-ds.xml 23720 2004-09-15 14:37:40Z loubyansky $ -->
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>DefaultDS</jndi-name>
+ <connection-url>jdbc:pointbase:server://@pointbase.server@:@pointbase.port/pointbase.dbName@,new</connection-url>
+ <driver-class>com.pointbase.jdbc.jdbcUniversalDriver</driver-class>
+ <user-name>@pointbase.user@</user-name>
+ <password>@pointbase.passwd@</password>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>PointBase</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/pointbase-xa-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/pointbase-xa-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/pointbase-xa-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- Example of the pointbase 4.8 XA datasource configuration -->
+<!-- $Id: pointbase-xa-ds.xml 23720 2004-09-15 14:37:40Z loubyansky $ -->
+
+<datasources>
+ <xa-datasource>
+ <jndi-name>PointbaseXA</jndi-name>
+ <xa-datasource-class>com.pointbase.xa.xaDataSource</xa-datasource-class>
+ <xa-datasource-property name="ServerName">@pointbase.server@</xa-datasource-property>
+ <xa-datasource-property name="DatabaseName">9092</xa-datasource-property>
+ <user-name>@pointbase.user@</user-name>
+ <password>@pointbase.passwd@</password>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>PointBase</type-mapping>
+ </metadata>
+ </xa-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/postgres-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/postgres-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/postgres-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: postgres-ds.xml 41016 2006-02-07 14:23:00Z acoliver $ -->
+<!-- ==================================================================== -->
+<!-- Datasource config for Postgres -->
+<!-- ==================================================================== -->
+
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>PostgresDS</jndi-name>
+ <connection-url>jdbc:postgresql://[servername]:[port]/[database name]</connection-url>
+ <driver-class>org.postgresql.Driver</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+ <!-- sql to call when connection is created. Can be anything, select 1 is valid for PostgreSQL
+ <new-connection-sql>select 1</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool. Can be anything, select 1 is valid for PostgreSQL
+ <check-valid-connection-sql>select 1</check-valid-connection-sql>
+ -->
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>PostgreSQL 7.2</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/progress-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/progress-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/progress-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: progress-ds.xml 23720 2004-09-15 14:37:40Z loubyansky $ -->
+<!-- ==================================================================== -->
+<!-- Datasource config for Progress 9.1 -->
+<!-- -->
+<!-- Based on config provided by victorstar in the forums -->
+<!-- -->
+<!-- Beside adding the driver jar to server/[config]/lib you also -->
+<!-- need to add the native library to your path. -->
+<!-- e.g. JdbcProgress.dll on windows -->
+<!-- ==================================================================== -->
+
+<datasources>
+
+ <local-tx-datasource>
+ <jndi-name>ProgressDS</jndi-name>
+
+ <connection-url>jdbc:JdbcProgress:T:dbserver:3305:liveappl</connection-url>
+ <driver-class>com.progress.sql.jdbc.JdbcProgressDriver</driver-class>
+ <user-name>user</user-name>
+ <password>password</password>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>PostgreSQL 7.2</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sapdb-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sapdb-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sapdb-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- New ConnectionManager setup for Sapdb using the sapdbc driver -->
+<!-- Thanks to Kasper Nielsen <news at kav.dk> -->
+<!-- See http://www.sapdb.org/sap_db_jdbc.htm for details -->
+<!-- This is a minimal example. See the generic example for other stuff -->
+<!-- ===================================================================== -->
+
+<!-- $Id: sapdb-ds.xml 23720 2004-09-15 14:37:40Z loubyansky $ -->
+
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>SapdbDS</jndi-name>
+ <connection-url>jdbc:sapdb://127.0.0.1/DB_NAME</connection-url>
+ <driver-class>com.sap.dbtech.jdbc.DriverSapDB</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>SapDB</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sapr3-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sapr3-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sapr3-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"?>
+ <!-- ==================================================================== -->
+ <!-- ConnectionManager setup for SAP R3 -->
+ <!-- Author: David Jencks (d_jencks at users.sourceforge.net) -->
+ <!-- Author: Chris Pinfold (chrisp at yambay.com) -->
+ <!-- Author: Juraj Lenharcik (nort at nort.de) ;-) -->
+ <!-- ==================================================================== -->
+
+<connection-factories>
+ <tx-connection-factory>
+ <adapter-display-name>SAPJRA</adapter-display-name>
+ <jndi-name>eis/SAPJRA</jndi-name>
+ <config-property name="SAPClient" type="java.lang.String">150</config-property>
+ <user-name>dsgsd</user-name>
+ <password>sdgsdg</password>
+ <config-property name="Language" type="java.lang.String">DE</config-property>
+ <config-property name="ServerName" type="java.lang.String">44.44.44.44</config-property>
+ <config-property name="SystemNumber" type="java.lang.String">00</config-property>
+ <config-property name="PortNumber" type="java.lang.String">10</config-property>
+<!-- <config-property name="GatewayServerName" type="java.lang.String">a</config-property>
+ <config-property name="GatewayServiceNumber" type="java.lang.String">a</config-property>
+ <config-property name="MessageServerName" type="java.lang.String">a</config-property>
+ <config-property name="SystemName" type="java.lang.String">a</config-property>
+ <config-property name="GroupName" type="java.lang.String">a</config-property> -->
+ </tx-connection-factory>
+</connection-factories>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/solid-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/solid-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/solid-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: solid-ds.xml 23720 2004-09-15 14:37:40Z loubyansky $ -->
+<!-- ==================================================================== -->
+<!-- DataSource configuration for solid using 3.0 driver -->
+<!-- Thanks to Casey Haakenson -->
+<!-- ==================================================================== -->
+
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>SolidDS</jndi-name>
+ <!--NOTE: Solid wants the username/password in the URL, it will
+ ignore the specific arguments.-->
+ <connection-url>jdbc:solid://yourdbhost:1964/yourdbusername/yourdbpassword</connection-url>
+ <driver-class>solid.jdbc.SolidDriver</driver-class>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>SOLID</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sybase-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sybase-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jca/sybase-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss Server Configuration -->
+<!-- -->
+<!-- New ConnectionManager setup for Sybase ASE/ASA jConnect driver -->
+<!-- Thanks to Marc Zampetti <zampetti at aol.net> -->
+<!-- This is a minimal example. See the generic example for other stuff -->
+<!-- ===================================================================== -->
+
+<!-- $Id: sybase-ds.xml 23720 2004-09-15 14:37:40Z loubyansky $ -->
+
+
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>jdbc/SybaseDB</jndi-name>
+ <!-- Sybase jConnect URL for the database.
+ NOTE: The hostname and port are made up values. The optional
+ database name is provided, as well as some additinal Driver
+ parameters.
+ -->
+ <connection-url>jdbc:sybase:Tds:host.at.some.domain:5000/db_name?JCONNECT_VERSION=6</connection-url>
+ <driver-class>com.sybase.jdbc2.jdbc.SybDataSource</driver-class>
+ <user-name>x</user-name>
+ <password>y</password>
+ <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.SybaseExceptionSorter</exception-sorter-class-name>
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>Sybase</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/as400-jdbc2-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/as400-jdbc2-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/as400-jdbc2-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<server>
+
+ <!--
+ | The destination manager is the core service within JBossMQ
+ -->
+ <mbean code="org.jboss.mq.server.jmx.DestinationManager" name="jboss.mq:service=DestinationManager">
+ <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>
+ <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>
+ <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+
+ <!--
+ | The MessageCache decides where to put JBossMQ message that
+ | are sitting around waiting to be consumed by a client.
+ |
+ | The memory marks are in Megabytes. Once the JVM memory usage hits
+ | the high memory mark, the old messages in the cache will start getting
+ | stored in the DataDirectory. As memory usage gets closer to the
+ | Max memory mark, the amount of message kept in the memory cache aproaches 0.
+ -->
+ <mbean code="org.jboss.mq.server.MessageCache"
+ name="jboss.mq:service=MessageCache">
+ <attribute name="HighMemoryMark">50</attribute>
+ <attribute name="MaxMemoryMark">60</attribute>
+ <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
+ </mbean>
+
+
+ <mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
+ name="jboss.mq:service=PersistenceManager">
+ <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=DB2-400</depends>
+ <attribute name="SqlProperties">
+ BLOB_TYPE=BYTES_BLOB
+ INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
+ INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
+ SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
+ SELECT_MAX_TX = (SELECT MAX(TXID) AS TXID FROM JMS_TRANSACTIONS UNION SELECT MAX(TXID) AS TXID FROM JMS_MESSAGES)
+ DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS
+ SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
+ UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
+ UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
+ UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
+ DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXOP=? AND JMS_MESSAGES.TXID IN (SELECT TXID FROM JMS_TRANSACTIONS)
+ DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?
+ DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?
+ DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T'
+ DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION))
+ CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX JMS_MESSAGES_TXOP_TXID ON JMS_MESSAGES (TXOP, TXID)
+ CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_MESSAGES_DESTINATION ON JMS_MESSAGES (DESTINATION)
+ CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) )
+ CREATE_TABLES_ON_STARTUP = TRUE </attribute>
+ <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
+ <!--attribute name="RecoveryTimeout">0</attribute-->
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/conf/jbossmq-state.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/conf/jbossmq-state.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/conf/jbossmq-state.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<StateManager>
+ <Users>
+ <User>
+ <Name>j2ee</Name>
+ <Password>j2ee</Password>
+ </User>
+ <User>
+ <Name>john</Name>
+ <Password>needle</Password>
+ <Id>DurableSubscriberExample</Id>
+ </User>
+ <User>
+ <Name>guest</Name>
+ <Password>guest</Password>
+ </User>
+ <User>
+ <Name>nobody</Name>
+ <Password>nobody</Password>
+ </User>
+ <User>
+ <Name>dynsub</Name>
+ <Password>dynsub</Password>
+ </User>
+ </Users>
+ <Roles>
+ <Role name="guest">
+ <UserName>j2ee</UserName>
+ <UserName>guest</UserName>
+ <UserName>john</UserName>
+ </Role>
+ <Role name="subscriber">
+ <UserName>john</UserName>
+ </Role>
+ <Role name="publisher">
+ <UserName>john</UserName>
+ <UserName>dynsub</UserName>
+ </Role>
+ <Role name="durpublisher">
+ <UserName>john</UserName>
+ <UserName>dynsub</UserName>
+ </Role>
+ <Role name="noacc">
+ <UserName>nobody</UserName>
+ </Role>
+ </Roles>
+ <DurableSubscriptions>
+ </DurableSubscriptions>
+</StateManager>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/db2-jdbc2-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/db2-jdbc2-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/db2-jdbc2-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<server>
+
+ <!--
+ | The destination manager is the core service within JBossMQ
+ -->
+ <mbean code="org.jboss.mq.server.jmx.DestinationManager" name="jboss.mq:service=DestinationManager">
+ <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>
+ <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>
+ <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+
+ <!--
+ | The MessageCache decides where to put JBossMQ message that
+ | are sitting around waiting to be consumed by a client.
+ |
+ | The memory marks are in Megabytes. Once the JVM memory usage hits
+ | the high memory mark, the old messages in the cache will start getting
+ | stored in the DataDirectory. As memory usage gets closer to the
+ | Max memory mark, the amount of message kept in the memory cache aproaches 0.
+ -->
+ <mbean code="org.jboss.mq.server.MessageCache"
+ name="jboss.mq:service=MessageCache">
+ <attribute name="HighMemoryMark">50</attribute>
+ <attribute name="MaxMemoryMark">60</attribute>
+ <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
+ </mbean>
+
+
+ <mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
+ name="jboss.mq:service=PersistenceManager">
+ <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=DB2DS</depends>
+ <attribute name="SqlProperties">
+ BLOB_TYPE=BYTES_BLOB
+ INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
+ INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
+ SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
+ SELECT_MAX_TX = (SELECT MAX(TXID) AS TXID FROM JMS_TRANSACTIONS UNION SELECT MAX(TXID) AS TXID FROM JMS_MESSAGES)
+ DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS
+ SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
+ UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
+ UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
+ UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
+ DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXOP=? AND JMS_MESSAGES.TXID IN (SELECT TXID FROM JMS_TRANSACTIONS)
+ DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?
+ DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?
+ DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T'
+ DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB BLOB(1024M), PRIMARY KEY (MESSAGEID, DESTINATION))
+ CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX JMS_TXOP_TXID ON JMS_MESSAGES (TXOP, TXID)
+ CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_DESTINATION ON JMS_MESSAGES (DESTINATION)
+ CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER NOT NULL, PRIMARY KEY (TXID) )
+ CREATE_TABLES_ON_STARTUP = TRUE </attribute>
+ <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
+ <!--attribute name="RecoveryTimeout">0</attribute-->
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/derby-jdbc2-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/derby-jdbc2-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/derby-jdbc2-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: derby-jdbc2-service.xml 58302 2006-11-13 17:11:17Z adrian at jboss.org $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Persistence and caching using DERBY-DB (Synonym: IBM-Cloudscape) -->
+ <!-- See docs/examples/jms for other configurations -->
+ <!-- IMPORTANT: Remove hsqldb-jdbc2-service.xml -->
+ <!-- -->
+ <!-- Configuration supplied by Bison Schweiz AG Hendrik Schäfer -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | The destination manager is the core service within JBossMQ
+ -->
+ <mbean code="org.jboss.mq.server.jmx.DestinationManager" name="jboss.mq:service=DestinationManager">
+ <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>
+ <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>
+ <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>
+ </mbean>
+
+ <!--
+ | The MessageCache decides where to put JBossMQ message that
+ | are sitting around waiting to be consumed by a client.
+ |
+ | The memory marks are in Megabytes. Once the JVM memory usage hits
+ | the high memory mark, the old messages in the cache will start getting
+ | stored in the DataDirectory. As memory usage gets closer to the
+ | Max memory mark, the amount of message kept in the memory cache aproaches 0.
+ -->
+ <mbean code="org.jboss.mq.server.MessageCache"
+ name="jboss.mq:service=MessageCache">
+ <attribute name="HighMemoryMark">50</attribute>
+ <attribute name="MaxMemoryMark">60</attribute>
+ <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
+ </mbean>
+
+ <!-- The PersistenceManager is used to store messages to disk. -->
+ <!--
+ | The jdbc2 PersistenceManager is the new improved JDBC implementation.
+ | This implementation allows you to control how messages are stored in
+ | the database.
+ |
+ | This jdbc2 PM configuration has been tested against Derby DB
+ |
+ -->
+ <mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
+ name="jboss.mq:service=PersistenceManager">
+ <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=DerbyDS</depends>
+ <attribute name="SqlProperties">
+ BLOB_TYPE=BYTES_BLOB
+ INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
+ INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
+ SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
+ SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES
+ DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS
+ SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE_KEYS_IN_DEST = SELECT MESSAGEID FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
+ UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
+ DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE EXISTS (SELECT JMS_TRANSACTIONS.TXID FROM JMS_TRANSACTIONS \
+ WHERE JMS_TRANSACTIONS.TXID = JMS_MESSAGES.TXID) \
+ AND JMS_MESSAGES.TXOP = ?
+ DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?
+ DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?
+ DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T'
+ DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, \
+ DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \
+ MESSAGEBLOB blob(1024M), PRIMARY KEY (MESSAGEID, DESTINATION))
+ CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX JMS_MESSAGES_TXOP_TXID ON JMS_MESSAGES (TXOP, TXID)
+ CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_MESSAGES_DESTINATION ON JMS_MESSAGES (DESTINATION)
+ CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER not null, PRIMARY KEY (TXID) )
+ CREATE_TABLES_ON_STARTUP = TRUE
+ </attribute>
+ <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
+ <!--attribute name="RecoveryTimeout">0</attribute-->
+ <!-- The number of blobs to load at once during message recovery -->
+ <attribute name="RecoverMessagesChunk">0</attribute>
+ </mbean>
+
+</server>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/file-state-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/file-state-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/file-state-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: file-state-service.xml 23368 2004-09-03 15:50:38Z ejort $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- State management using the file system -->
+ <!-- -->
+ <!-- IMPORTANT OTHER CONFIGURATION INSTRUCTIONS -->
+ <!-- -->
+ <!-- 1) Remove hsqldb-jdbc-state-service.xml -->
+ <!-- 2) Replace the jbossmq configuration with the following -->
+ <!-- login module in conf/login-config.xml -->
+ <!--
+ <application-policy name = "jbossmq">
+ <authentication>
+ <login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"
+ flag = "required">
+ <module-option name = "unauthenticatedIdentity">guest</module-option>
+ <module-option name = "sm.objectname">jboss.mq:service=StateManager</module-option>
+ </login-module>
+ </authentication>
+ </application-policy>
+ -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | The StateManager is used to keep JMS persistent state data.
+ | For example: what durable subscriptions are active.
+ -->
+ <mbean code="org.jboss.mq.sm.file.DynamicStateManager"
+ name="jboss.mq:service=StateManager">
+ <!-- This file is pulled from the configuration URL of the server -->
+ <attribute name="StateFile">jbossmq-state.xml</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/mssql-jdbc2-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/mssql-jdbc2-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/mssql-jdbc2-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: mssql-jdbc2-service.xml 56265 2006-08-25 14:01:38Z luc.texier at jboss.com $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Persistence and caching using MSSQL -->
+ <!-- IMPORTANT: Remove hsqldb-jdbc2-service.xml -->
+ <!-- Provided by matty at mattygiedt.com -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | The destination manager is the core service within JBossMQ
+ -->
+ <mbean code="org.jboss.mq.server.jmx.DestinationManager" name="jboss.mq:service=DestinationManager">
+ <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>
+ <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>
+ <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>
+ </mbean>
+
+ <!--
+ | The MessageCache decides where to put JBossMQ message that
+ | are sitting around waiting to be consumed by a client.
+ |
+ | The memory marks are in Megabytes. Once the JVM memory usage hits
+ | the high memory mark, the old messages in the cache will start getting
+ | stored in the DataDirectory. As memory usage gets closer to the
+ | Max memory mark, the amount of message kept in the memory cache aproaches 0.
+ -->
+ <mbean code="org.jboss.mq.server.MessageCache"
+ name="jboss.mq:service=MessageCache">
+ <attribute name="HighMemoryMark">50</attribute>
+ <attribute name="MaxMemoryMark">60</attribute>
+ <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
+ </mbean>
+
+ <!-- The PersistenceManager is used to store messages to disk. -->
+ <!--
+ | The jdbc2 PersistenceManager is the new improved JDBC implementation.
+ | This implementation allows you to control how messages are stored in
+ | the database.
+ |
+ | This jdbc2 PM configuration has been tested against MS SQL Server 2000
+ | http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpAMSSQLDatasource
+ -->
+ <mbean code="org.jboss.mq.pm.jdbc2.MSSQLPersistenceManager"
+ name="jboss.mq:service=PersistenceManager">
+ <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=MSSQLDS</depends>
+ <attribute name="SqlProperties">
+ BLOB_TYPE=BINARYSTREAM_BLOB
+ INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
+ INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
+ SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
+ SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES
+ DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS
+ SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE_KEYS_IN_DEST = SELECT MESSAGEID FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
+ UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
+ DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXID IN (SELECT TXID FROM JMS_TRANSACTIONS) AND TXOP=?
+ DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?
+ DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?
+ DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T'
+ DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB IMAGE)
+ CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX JMS_MESSAGES_TXOP_TXID ON JMS_MESSAGES (TXOP, TXID)
+ CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_MESSAGES_DESTINATION ON JMS_MESSAGES (DESTINATION)
+ CREATE_IDX_MESSAGE_MESSAGEID_DESTINATION = CREATE UNIQUE CLUSTERED INDEX JMS_MESSAGES_IDX ON JMS_MESSAGES (MESSAGEID, DESTINATION)
+ CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) )
+ CREATE_TABLES_ON_STARTUP = TRUE
+ </attribute>
+ <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
+ <!--attribute name="RecoveryTimeout">0</attribute-->
+ <!-- The number of blobs to load at once during message recovery -->
+ <attribute name="RecoverMessagesChunk">0</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/mysql-jdbc2-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/mysql-jdbc2-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/mysql-jdbc2-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,80 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: mysql-jdbc2-service.xml 39343 2005-12-29 16:32:35Z ltexier $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Persistence and caching using MySQL -->
+ <!-- IMPORTANT: Remove hsqldb-jdbc2-service.xml -->
+ <!-- -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | The destination manager is the core service within JBossMQ
+ -->
+ <mbean code="org.jboss.mq.server.jmx.DestinationManager" name="jboss.mq:service=DestinationManager">
+ <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>
+ <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>
+ <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>
+ </mbean>
+
+ <!--
+ | The MessageCache decides where to put JBossMQ message that
+ | are sitting around waiting to be consumed by a client.
+ |
+ | The memory marks are in Megabytes. Once the JVM memory usage hits
+ | the high memory mark, the old messages in the cache will start getting
+ | stored in the DataDirectory. As memory usage gets closer to the
+ | Max memory mark, the amount of message kept in the memory cache aproaches 0.
+ -->
+ <mbean code="org.jboss.mq.server.MessageCache"
+ name="jboss.mq:service=MessageCache">
+ <attribute name="HighMemoryMark">50</attribute>
+ <attribute name="MaxMemoryMark">60</attribute>
+ <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
+ </mbean>
+
+ <!-- The PersistenceManager is used to store messages to disk. -->
+ <!--
+ | The jdbc2 PersistenceManager is the new improved JDBC implementation.
+ | This implementation allows you to control how messages are stored in
+ | the database.
+ |
+ | This jdbc2 PM configuration has was supplied by Stephane Nicoll in the forums as an example for MySQL
+ -->
+ <mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
+ name="jboss.mq:service=PersistenceManager">
+ <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=MySqlDS</depends>
+ <attribute name="SqlProperties">
+ BLOB_TYPE=BYTES_BLOB
+ INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
+ INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
+ SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
+ SELECT_MAX_TX = SELECT MAX(TXID) FROM JMS_MESSAGES
+ DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS
+ SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE_KEYS_IN_DEST = SELECT MESSAGEID FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
+ UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
+ DELETE_MARKED_MESSAGES_WITH_TX = DELETE JMS_MESSAGES FROM JMS_MESSAGES, JMS_TRANSACTIONS WHERE JMS_MESSAGES.TXID = JMS_TRANSACTIONS.TXID AND JMS_MESSAGES.TXOP=?
+ DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?
+ DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?
+ DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T'
+ DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB LONGBLOB, PRIMARY KEY (MESSAGEID, DESTINATION))
+ CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX JMS_MESSAGES_TXOP_TXID ON JMS_MESSAGES (TXOP, TXID)
+ CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_MESSAGES_DESTINATION ON JMS_MESSAGES (DESTINATION)
+ CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) )
+ CREATE_TABLES_ON_STARTUP = TRUE
+ </attribute>
+ <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
+ <!--attribute name="RecoveryTimeout">0</attribute-->
+ <!-- The number of blobs to load at once during message recovery -->
+ <attribute name="RecoverMessagesChunk">1</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/null-persistence-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/null-persistence-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/null-persistence-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: null-persistence-service.xml 29473 2005-03-14 19:18:48Z ejort $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Persistence and caching using MSSQL -->
+ <!-- IMPORTANT: Remove hsqldb-jdbc2-service.xml -->
+ <!-- Provided by matty at mattygiedt.com -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | The destination manager is the core service within JBossMQ
+ -->
+ <mbean code="org.jboss.mq.server.jmx.DestinationManager" name="jboss.mq:service=DestinationManager">
+ <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>
+ <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>
+ <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>
+
+ <!-- If using a delegate persistence manager, use the in memory cache store -->
+ <!-- for temporary queues/topics (uncomment to enable) -->
+ <!--attribute name="TemporaryInMemory">true</attribute-->
+ </mbean>
+
+ <!--
+ | The MessageCache decides where to put JBossMQ message that
+ | are sitting around waiting to be consumed by a client.
+ |
+ | The memory marks are in Megabytes. Once the JVM memory usage hits
+ | the high memory mark, the old messages in the cache will start getting
+ | stored in the DataDirectory. As memory usage gets closer to the
+ | Max memory mark, the amount of message kept in the memory cache aproaches 0.
+ -->
+ <mbean code="org.jboss.mq.server.MessageCache"
+ name="jboss.mq:service=MessageCache">
+ <attribute name="HighMemoryMark">50</attribute>
+ <attribute name="MaxMemoryMark">60</attribute>
+ <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
+ </mbean>
+
+ <!-- This PersistenceManager does not store messages to disk -->
+ <!-- All persistence requests are ignored and the cache store is in memory -->
+ <!-- -->
+ <!-- Use org.jboss.mq.pm.none.NewPersistenceManager to enable the -->
+ <!-- optimized topic persistence with or without a jdbc3 delegate -->
+ <!-- -->
+ <!-- A delegate persistence manager can be configured -->
+ <!-- The delegate will be used unless the queue/topic is configured with -->
+ <!-- <attribute name="InMemory">true</attribute> -->
+ <mbean code="org.jboss.mq.pm.none.PersistenceManager"
+ name="jboss.mq:service=PersistenceManager">
+
+ <!-- An optional delegate for real persistence of some destinations e.g. jdbc2 -->
+ <!-- depends optional-attribute-name="DelegatePM">jboss.mq:service=SomePersistenceManager</depends-->
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/oil-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/oil-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/oil-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: oil-service.xml 38188 2005-11-17 00:11:34Z adrian $ -->
+
+<server>
+
+ <!-- JBossMQ communication using the Optimizated Invocation Layer
+ The server connects back to the client on a different socket -->
+
+ <mbean code="org.jboss.mq.il.oil.OILServerILService"
+ name="jboss.mq:service=InvocationLayer,type=OIL">
+ <depends optional-attribute-name="Invoker">jboss.mq:service=Invoker</depends>
+ <attribute name="ConnectionFactoryJNDIRef">OILConnectionFactory</attribute>
+ <attribute name="XAConnectionFactoryJNDIRef">OILXAConnectionFactory</attribute>
+ <attribute name="ServerBindPort">8090</attribute>
+ <attribute name="PingPeriod">60000</attribute>
+ <attribute name="EnableTcpNoDelay">true</attribute>
+ <attribute name="BindAddress">${jboss.bind.address}</attribute>
+ <!-- Used to disconnect the client if there is no activity -->
+ <!-- Ensure this is greater than the ping period -->
+ <attribute name="ReadTimeout">70000</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/oracle-jdbc2-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/oracle-jdbc2-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/oracle-jdbc2-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: oracle-jdbc2-service.xml 57445 2006-10-05 13:20:43Z adrian at jboss.org $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Persistence and caching using Oracle -->
+ <!-- IMPORTANT: Remove hsqldb-jdbc2-service.xml -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | The destination manager is the core service within JBossMQ
+ -->
+ <mbean code="org.jboss.mq.server.jmx.DestinationManager" name="jboss.mq:service=DestinationManager">
+ <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>
+ <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>
+ <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>
+ </mbean>
+
+ <!--
+ | The MessageCache decides where to put JBossMQ message that
+ | are sitting around waiting to be consumed by a client.
+ |
+ | The memory marks are in Megabytes. Once the JVM memory usage hits
+ | the high memory mark, the old messages in the cache will start getting
+ | stored in the DataDirectory. As memory usage gets closer to the
+ | Max memory mark, the amount of message kept in the memory cache aproaches 0.
+ -->
+ <mbean code="org.jboss.mq.server.MessageCache"
+ name="jboss.mq:service=MessageCache">
+ <attribute name="HighMemoryMark">50</attribute>
+ <attribute name="MaxMemoryMark">60</attribute>
+ <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
+ </mbean>
+
+ <!-- The PersistenceManager is used to store messages to disk. -->
+ <!--
+ | The jdbc2 PersistenceManager is the new improved JDBC implementation.
+ | This implementation allows you to control how messages are stored in
+ | the database.
+ |
+ | This jdbc2 PM configuration has been tested against Oracle
+ |
+ | Use the OracleThinPeristenceManager if you have the 4K limit problem for blobs
+ | this uses the INSERT_EMPTY_BLOB and LOCK_EMPTY_BLOB before updating the row
+ | with the real blob data to workaround that limit.
+ -->
+ <!--mbean code="org.jboss.mq.pm.jdbc2.OracleThinPersistenceManager" -->
+ <mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
+ name="jboss.mq:service=PersistenceManager">
+ <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=OracleDS</depends>
+ <attribute name="SqlProperties">
+ INSERT_EMPTY_BLOB = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,EMPTY_BLOB(),?,?)
+ LOCK_EMPTY_BLOB = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID = ? AND DESTINATION = ? FOR UPDATE
+ BLOB_TYPE=BINARYSTREAM_BLOB
+ INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
+ INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
+ SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
+ SELECT_MAX_TX = SELECT MAX(TXID) FROM (SELECT MAX(TXID) AS TXID FROM JMS_TRANSACTIONS UNION SELECT MAX(TXID) AS TXID FROM JMS_MESSAGES)
+ DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS
+ SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE_KEYS_IN_DEST = SELECT MESSAGEID FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
+ UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
+ DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES MESS WHERE TXOP=? AND EXISTS (SELECT TXID FROM JMS_TRANSACTIONS TX WHERE TX.TXID = MESS.TXID)
+ DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?
+ DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?
+ DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T'
+ DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \
+ DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \
+ MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) )
+ CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX JMS_MESSAGES_TXOP_TXID ON JMS_MESSAGES (TXOP, TXID)
+ CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_MESSAGES_DESTINATION ON JMS_MESSAGES (DESTINATION)
+ CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) )
+ CREATE_TABLES_ON_STARTUP = TRUE
+ </attribute>
+ <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
+ <!--attribute name="RecoveryTimeout">0</attribute-->
+ <!-- The number of blobs to load at once during message recovery -->
+ <attribute name="RecoverMessagesChunk">0</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/postgres-jdbc2-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/postgres-jdbc2-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/postgres-jdbc2-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: postgres-jdbc2-service.xml 42419 2006-03-17 11:35:42Z adrian $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Persistence and caching using Postgres -->
+ <!-- IMPORTANT: Remove hsqldb-jdbc2-service.xml -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | The destination manager is the core service within JBossMQ
+ -->
+ <mbean code="org.jboss.mq.server.jmx.DestinationManager" name="jboss.mq:service=DestinationManager">
+ <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>
+ <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>
+ <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>
+ </mbean>
+
+ <!--
+ | The MessageCache decides where to put JBossMQ message that
+ | are sitting around waiting to be consumed by a client.
+ |
+ | The memory marks are in Megabytes. Once the JVM memory usage hits
+ | the high memory mark, the old messages in the cache will start getting
+ | stored in the DataDirectory. As memory usage gets closer to the
+ | Max memory mark, the amount of message kept in the memory cache aproaches 0.
+ -->
+ <mbean code="org.jboss.mq.server.MessageCache"
+ name="jboss.mq:service=MessageCache">
+ <attribute name="HighMemoryMark">50</attribute>
+ <attribute name="MaxMemoryMark">60</attribute>
+ <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
+ </mbean>
+
+ <!-- The PersistenceManager is used to store messages to disk. -->
+ <!--
+ | The jdbc2 PersistenceManager is the new improved JDBC implementation.
+ | This implementation allows you to control how messages are stored in
+ | the database.
+ |
+ | This jdbc2 PM configuration has was supplied by Stephane Nicoll in the forums as an example for Postgres
+ -->
+ <mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
+ name="jboss.mq:service=PersistenceManager">
+ <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=PostgresDS</depends>
+ <attribute name="SqlProperties">
+ BLOB_TYPE=BYTES_BLOB
+ INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
+ INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
+ SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
+ SELECT_MAX_TX = SELECT MAX(TXID) FROM (SELECT MAX(TXID) AS TXID FROM JMS_TRANSACTIONS UNION SELECT MAX(TXID) AS TXID FROM JMS_MESSAGES) AS TXID
+ DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS
+ SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE_KEYS_IN_DEST = SELECT MESSAGEID FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
+ UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
+ DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXID IN (SELECT TXID FROM JMS_TRANSACTIONS) AND TXOP=?
+ DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?
+ DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?
+ DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T'
+ DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB BYTEA, PRIMARY KEY (MESSAGEID, DESTINATION))
+ CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX JMS_MESSAGES_TXOP_TXID ON JMS_MESSAGES (TXOP, TXID)
+ CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_MESSAGES_DESTINATION ON JMS_MESSAGES (DESTINATION)
+ CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) )
+ CREATE_TABLES_ON_STARTUP = TRUE
+ </attribute>
+ <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
+ <!--attribute name="RecoveryTimeout">0</attribute-->
+ <!-- The number of blobs to load at once during message recovery -->
+ <attribute name="RecoverMessagesChunk">0</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/rmi-il-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/rmi-il-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/rmi-il-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: rmi-il-service.xml 30526 2005-04-19 05:00:42Z $ -->
+
+<server>
+
+ <!-- JBossMQ communication using RMI -->
+
+ <mbean code="org.jboss.mq.il.rmi.RMIServerILService"
+ name="jboss.mq:service=InvocationLayer,type=RMI">
+ <depends optional-attribute-name="Invoker">jboss.mq:service=Invoker</depends>
+ <attribute name="ConnectionFactoryJNDIRef">RMIConnectionFactory</attribute>
+ <attribute name="XAConnectionFactoryJNDIRef">RMIXAConnectionFactory</attribute>
+ <attribute name="PingPeriod">60000</attribute>
+ </mbean>
+
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/ssl-uil2-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/ssl-uil2-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/ssl-uil2-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: ssl-uil2-service.xml 33429 2005-07-11 19:59:46Z adrian $ -->
+
+<server>
+
+ <!-- An example invocation layer using ssl
+ JBossMQ using the Unified Invocation Layer
+ All communication uses one socket connection -->
+
+ <mbean code="org.jboss.mq.il.uil2.UILServerILService"
+ name="jboss.mq:service=InvocationLayer,type=SSLUIL2">
+
+ <!-- The server chain -->
+ <depends optional-attribute-name="Invoker">jboss.mq:service=Invoker</depends>
+
+ <!-- JNDI binding -->
+ <attribute name="ConnectionFactoryJNDIRef">SSLUIL2ConnectionFactory</attribute>
+
+ <!-- JNDI binding for XA -->
+ <attribute name="XAConnectionFactoryJNDIRef">SSLUIL2XAConnectionFactory</attribute>
+
+ <!-- The bind address -->
+ <attribute name="BindAddress">${jboss.bind.address}</attribute>
+
+ <!-- The bind port -->
+ <attribute name="ServerBindPort">8091</attribute>
+
+ <!-- The ping period in millis -->
+ <attribute name="PingPeriod">60000</attribute>
+
+ <!-- Whether tcp/ip does not wait for buffer fills -->
+
+ <attribute name="EnableTcpNoDelay">true</attribute>
+ <!-- Used to disconnect the client on the serverside if there is no activity -->
+ <!-- Ensure this is greater than the ping period -->
+ <attribute name="ReadTimeout">120000</attribute>
+
+ <!-- Used to disconnect the client on the clientside if there is no activity -->
+ <!-- Ensure this is greater than the ping period -->
+ <attribute name="ClientReadTimeout">300000</attribute>
+
+ <!-- The size of the buffer (in bytes) wrapping the socket -->
+ <!-- The buffer is flushed after each request -->
+ <attribute name="BufferSize">2048</attribute>
+
+ <!-- Large messages may block the ping/pong -->
+ <!-- A pong is simulated after each chunk (in bytes) for both reading and writing -->
+ <!-- It must be larger than the buffer size -->
+ <attribute name="ChunkSize">1000000</attribute>
+
+ <!-- Minimum number of threads in the internal thread pool -->
+ <attribute name="MinimumThreads">1</attribute>
+
+ <!-- Maximum number of threads in the internal thread pool -->
+ <!-- This is not strict, it represents how many threads go back into the pool -->
+ <!-- rather than are reaped immediately -->
+ <attribute name="MaximumThreads">50</attribute>
+
+ <!-- The timeout for unused threads in the internal pool in millis -->
+ <attribute name="TimeoutThreads">60000</attribute>
+
+ <!-- SSL Socket Factories -->
+ <attribute name="ClientSocketFactory">org.jboss.security.ssl.ClientSocketFactory</attribute>
+ <attribute name="ServerSocketFactory">org.jboss.security.ssl.DomainServerSocketFactory</attribute>
+
+ <!-- Security domain - see below -->
+ <attribute name="SecurityDomain">java:/jaas/SSL</attribute>
+ </mbean>
+
+ <!-- Configures the keystore on the security domain
+ This mbean is better placed in conf/jboss-service.xml where it
+ can be used by other services. But it will still work from anywhere.
+ Use keytool from the sdk to create the keystore.
+ -->
+ <mbean code="org.jboss.security.plugins.JaasSecurityDomain"
+ name="jboss.security:service=JaasSecurityDomain,domain=SSL">
+ <!-- This must correlate with the java:/jaas/SSL above -->
+ <constructor>
+ <arg type="java.lang.String" value="SSL"/>
+ </constructor>
+ <!-- The location of the keystore
+ resource: loads from the classloaders conf/ is the first classloader -->
+ <attribute name="KeyStoreURL">resource:test.keystore</attribute>
+ <attribute name="KeyStorePass">changeme</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/build.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/build.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/build.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,124 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- This is an Ant build script that creates a minimal jbossmq
+configuration based on the default configuration
+-->
+<project name="Mininal JBossMQ configuration script" default="config">
+
+ <!-- Override if the script is not run from within the
+ dist/docs/examples/jms/standalone directory.
+ -->
+ <property name="jboss.dist" value="../../../.."/>
+
+
+ <target name="common">
+
+ <!-- get rid of any existing folder -->
+ <delete dir="${jboss.dist}/server/jbossmq"/>
+
+
+ <!-- We are mainly based on the minimal configuration -->
+ <copy todir="${jboss.dist}/server/jbossmq">
+ <fileset dir="${jboss.dist}/server/minimal">
+ <exclude name="conf/jboss-service.xml"/>
+ <exclude name="lib/jboss-minimal.jar"/>
+ </fileset>
+ </copy>
+
+ <!-- We need the following from the default configuration -->
+ <copy todir="${jboss.dist}/server/jbossmq">
+ <fileset dir="${jboss.dist}/server/default">
+ <!-- configuration -->
+ <include name="conf/login-config.xml"/>
+ <include name="conf/xmdesc/*"/>
+ <!-- the main jboss jar -->
+ <include name="lib/jboss.jar"/>
+ <!-- jaas -->
+ <include name="lib/jbosssx.jar"/>
+ <!-- transactions -->
+ <include name="lib/jboss-transaction.jar"/>
+ <!-- jms interfaces -->
+ <include name="lib/jboss-j2ee.jar"/>
+ <!-- local db support -->
+ <include name="lib/jboss-common-jdbc-wrapper.jar"/>
+ <include name="lib/xalan.jar"/>
+ <include name="lib/jboss-jca.jar"/>
+ <include name="deploy/jbossjca-service.xml"/>
+ <include name="deploy/jboss-local-jdbc.rar"/>
+ <include name="conf/standardjbosscmp-jdbc.xml"/>
+ </fileset>
+ </copy>
+
+
+ <copy todir="${jboss.dist}/server/jbossmq/conf/" overwrite="true">
+ <fileset dir="${jboss.dist}/docs/examples/jms/standalone">
+ <include name="jboss-service.xml"/>
+ </fileset>
+ </copy>
+
+
+ </target>
+
+
+ <target name="config" depends="common">
+
+ <!-- We need the following from the default configuration -->
+ <copy todir="${jboss.dist}/server/jbossmq">
+ <fileset dir="${jboss.dist}/server/default">
+
+ <!-- hypersonic -->
+ <include name="lib/hsqldb*"/>
+ <include name="deploy/hsqldb-ds.xml"/>
+ <include name="deploy/jms/hsqldb-jdbc2-service.xml"/>
+ <include name="deploy/jms/hsqldb-jdbc-state-service.xml"/>
+ <!-- jbossmq -->
+ <include name="lib/jbossmq.jar"/>
+ <include name="deploy/jms/jbossmq-service.xml"/>
+ <include name="deploy/jms/jbossmq-destinations-service.xml"/>
+ <include name="deploy/jms/uil2-service.xml"/>
+ </fileset>
+ </copy>
+
+ </target>
+
+ <target name="config-all" depends="common">
+
+
+ <!-- We need the following from the all configuration -->
+ <copy todir="${jboss.dist}/server/jbossmq">
+ <fileset dir="${jboss.dist}/server/all">
+
+ <!-- hypersonic -->
+ <include name="lib/hsqldb*"/>
+ <include name="deploy/hsqldb-ds.xml"/>
+ <include name="deploy-hasingleton/jms/hsqldb-jdbc2-service.xml"/>
+ <include name="deploy-hasingleton/jms/hsqldb-jdbc-state-service.xml"/>
+ <!-- jbossmq -->
+ <include name="lib/jbossmq.jar"/>
+ <include name="deploy-hasingleton/jms/jbossmq-service.xml"/>
+ <include name="deploy-hasingleton/jms/jbossmq-destinations-service.xml"/>
+ <include name="deploy-hasingleton/jms/uil2-service.xml"/>
+ <!-- clustering -->
+ <include name="lib/jgroups.jar"/>
+ <include name="lib/jbossha.jar"/>
+ <include name="lib/commons-logging.jar"/>
+ <include name="deploy/cluster-service.xml"/>
+ <include name="deploy/deploy-hasingleton-service.xml"/>
+
+
+ </fileset>
+ </copy>
+
+
+
+ <copy todir="${jboss.dist}/server/jbossmq/deploy/" overwrite="true">
+ <fileset dir="${jboss.dist}/docs/examples/jms/standalone">
+ <include name="cluster-service.xml"/>
+ </fileset>
+ </copy>
+
+
+ </target>
+
+
+
+</project>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/cluster-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/cluster-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/cluster-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,133 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- Sample Clustering Service Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Cluster Partition: defines cluster -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.ha.framework.server.ClusterPartition"
+ name="jboss:service=${jboss.partition.name:DefaultPartition}">
+
+ <!-- Name of the partition being built -->
+ <attribute name="PartitionName">${jboss.partition.name:DefaultPartition}</attribute>
+
+ <!-- The address used to determine the node name -->
+ <attribute name="NodeAddress">${jboss.bind.address}</attribute>
+
+ <!-- Determine if deadlock detection is enabled -->
+ <attribute name="DeadlockDetection">False</attribute>
+
+ <!-- Max time (in ms) to wait for state transfer to complete. Increase for large states -->
+ <attribute name="StateTransferTimeout">30000</attribute>
+
+ <!-- The JGroups protocol configuration -->
+ <attribute name="PartitionConfig">
+ <!--
+ The default UDP stack:
+ - If you have a multihomed machine, set the UDP protocol's bind_addr attribute to the
+ appropriate NIC IP address, e.g bind_addr="192.168.0.2".
+ - On Windows machines, because of the media sense feature being broken with multicast
+ (even after disabling media sense) set the UDP protocol's loopback attribute to true
+ -->
+ <Config>
+ <UDP mcast_addr="${jboss.partition.udpGroup:228.1.2.3}" mcast_port="45566"
+ ip_ttl="8" ip_mcast="true"
+ mcast_send_buf_size="800000" mcast_recv_buf_size="150000"
+ ucast_send_buf_size="800000" ucast_recv_buf_size="150000"
+ loopback="false"/>
+ <PING timeout="2000" num_initial_members="3"
+ up_thread="true" down_thread="true"/>
+ <MERGE2 min_interval="10000" max_interval="20000"/>
+ <FD shun="true" up_thread="true" down_thread="true"
+ timeout="2500" max_tries="5"/>
+ <VERIFY_SUSPECT timeout="3000" num_msgs="3"
+ up_thread="true" down_thread="true"/>
+ <pbcast.NAKACK gc_lag="50" retransmit_timeout="300,600,1200,2400,4800"
+ max_xmit_size="8192"
+ up_thread="true" down_thread="true"/>
+ <UNICAST timeout="300,600,1200,2400,4800" window_size="100" min_threshold="10"
+ down_thread="true"/>
+ <pbcast.STABLE desired_avg_gossip="20000"
+ up_thread="true" down_thread="true"/>
+ <FRAG frag_size="8192"
+ down_thread="true" up_thread="true"/>
+ <pbcast.GMS join_timeout="5000" join_retry_timeout="2000"
+ shun="true" print_local_addr="true"/>
+ <pbcast.STATE_TRANSFER up_thread="true" down_thread="true"/>
+ </Config>
+
+ <!-- Alternate TCP stack: customize it for your environment, change bind_addr and initial_hosts -->
+ <!--
+ <Config>
+ <TCP bind_addr="thishost" start_port="7800" loopback="true"/>
+ <TCPPING initial_hosts="thishost[7800],otherhost[7800]" port_range="3" timeout="3500"
+ num_initial_members="3" up_thread="true" down_thread="true"/>
+ <MERGE2 min_interval="5000" max_interval="10000"/>
+ <FD shun="true" timeout="2500" max_tries="5" up_thread="true" down_thread="true" />
+ <VERIFY_SUSPECT timeout="1500" down_thread="false" up_thread="false" />
+ <pbcast.NAKACK down_thread="true" up_thread="true" gc_lag="100"
+ retransmit_timeout="3000"/>
+ <pbcast.STABLE desired_avg_gossip="20000" down_thread="false" up_thread="false" />
+ <pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="false"
+ print_local_addr="true" down_thread="true" up_thread="true"/>
+ <pbcast.STATE_TRANSFER up_thread="true" down_thread="true"/>
+ </Config>
+ -->
+ </attribute>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+
+
+
+ <!-- ==================================================================== -->
+ <!-- HA JNDI -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.ha.jndi.HANamingService"
+ name="jboss:service=HAJNDI">
+ <depends>jboss:service=${jboss.partition.name:DefaultPartition}</depends>
+ <!-- Name of the partition to which the service is linked -->
+ <attribute name="PartitionName">${jboss.partition.name:DefaultPartition}</attribute>
+ <!-- Bind address of bootstrap and HA-JNDI RMI endpoints -->
+ <attribute name="BindAddress">${jboss.bind.address}</attribute>
+ <!-- Port on which the HA-JNDI stub is made available -->
+ <attribute name="Port">1100</attribute>
+ <!-- RmiPort to be used by the HA-JNDI service once bound. 0 => auto. -->
+ <attribute name="RmiPort">1101</attribute>
+ <!-- Accept backlog of the bootstrap socket -->
+ <attribute name="Backlog">50</attribute>
+ <!-- The thread pool service used to control the bootstrap and
+ auto discovery lookups -->
+ <depends optional-attribute-name="LookupPool"
+ proxy-type="attribute">jboss.system:service=ThreadPool</depends>
+
+ <!-- A flag to disable the auto discovery via multicast -->
+ <attribute name="DiscoveryDisabled">false</attribute>
+ <!-- Set the auto-discovery bootstrap multicast bind address. If not
+ specified and a BindAddress is specified, the BindAddress will be used. -->
+ <attribute name="AutoDiscoveryBindAddress">${jboss.bind.address}</attribute>
+ <!-- Multicast Address and group port used for auto-discovery -->
+ <attribute name="AutoDiscoveryAddress">${jboss.partition.udpGroup:230.0.0.4}</attribute>
+ <attribute name="AutoDiscoveryGroup">1102</attribute>
+ <!-- The TTL (time-to-live) for autodiscovery IP multicast packets -->
+ <attribute name="AutoDiscoveryTTL">16</attribute>
+
+ <!-- Client socket factory to be used for client-server
+ RMI invocations during JNDI queries
+ <attribute name="ClientSocketFactory">custom</attribute>
+ -->
+ <!-- Server socket factory to be used for client-server
+ RMI invocations during JNDI queries
+ <attribute name="ServerSocketFactory">custom</attribute>
+ -->
+ </mbean>
+
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/jboss-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/jboss-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/standalone/jboss-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,376 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: jboss-service.xml 56341 2006-08-28 14:34:39Z luc.texier at jboss.com $ -->
+
+<!-- ===================================================================== -->
+<!-- JBoss Server Configuration -->
+<!-- ===================================================================== -->
+
+<server>
+
+ <!-- Load all jars from the JBOSS_DIST/server/<config>/lib directory. This
+ can be restricted to specific jars by specifying them in the archives
+ attribute.
+ -->
+ <classpath codebase="${jboss.server.lib.url:lib}" archives="*"/>
+
+
+
+ <!-- A Thread pool service -->
+ <mbean code="org.jboss.util.threadpool.BasicThreadPool"
+ name="jboss.system:service=ThreadPool">
+ <attribute name="Name">JBoss System Threads</attribute>
+ <attribute name="ThreadGroupName">System Threads</attribute>
+ <!-- How long a thread will live without any tasks in MS -->
+ <attribute name="KeepAliveTime">60000</attribute>
+ <!-- The max number of threads in the pool -->
+ <attribute name="MaximumPoolSize">10</attribute>
+ <!-- The max number of tasks before the queue is full -->
+ <attribute name="MaximumQueueSize">1000</attribute>
+ <!-- The behavior of the pool when a task is added and the queue is full.
+ abort - a RuntimeException is thrown
+ run - the calling thread executes the task
+ wait - the calling thread blocks until the queue has room
+ discard - the task is silently discarded without being run
+ discardOldest - check to see if a task is about to complete and enque
+ the new task if possible, else run the task in the calling thread
+ -->
+ <attribute name="BlockingMode">run</attribute>
+ </mbean>
+
+
+ <!-- ==================================================================== -->
+ <!-- Log4j Initialization -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.logging.Log4jService"
+ name="jboss.system:type=Log4jService,service=Logging"
+ xmbean-dd="resource:xmdesc/Log4jService-xmbean.xml">
+ <attribute name="ConfigurationURL">resource:log4j.xml</attribute>
+ <!-- Set the org.apache.log4j.helpers.LogLog.setQuiteMode. As of log4j1.2.8
+ this needs to be set to avoid a possible deadlock on exception at the
+ appender level. See bug#696819.
+ -->
+ <attribute name="Log4jQuietMode">true</attribute>
+ <!-- How frequently in seconds the ConfigurationURL is checked for changes -->
+ <attribute name="RefreshPeriod">60</attribute>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- JBoss RMI Classloader - only install when available -->
+ <!-- ==================================================================== -->
+ <mbean code="org.jboss.util.property.jmx.SystemPropertyClassValue"
+ name="jboss.rmi:type=RMIClassLoader">
+ <attribute name="Property">java.rmi.server.RMIClassLoaderSpi</attribute>
+ <attribute name="ClassName">org.jboss.system.JBossRMIClassLoader</attribute>
+ </mbean>
+
+
+ <!-- ==================================================================== -->
+ <!-- JNDI -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.naming.NamingService"
+ name="jboss:service=Naming"
+ xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
+ <!-- The call by value mode. true if all lookups are unmarshalled using
+ the caller's TCL, false if in VM lookups return the value by reference.
+ -->
+ <attribute name="CallByValue">false</attribute>
+ <!-- The listening port for the bootstrap JNP service. Set this to -1
+ to run the NamingService without the JNP invoker listening port.
+ -->
+ <attribute name="Port">1099</attribute>
+ <!-- The bootstrap JNP server bind address. This also sets the default
+ RMI service bind address. Empty == all addresses
+ -->
+ <attribute name="BindAddress">${jboss.bind.address}</attribute>
+ <!-- The port of the RMI naming service, 0 == anonymous -->
+ <attribute name="RmiPort">1098</attribute>
+ <!-- The RMI service bind address. Empty == all addresses
+ -->
+ <attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
+ <!-- The thread pool service used to control the bootstrap lookups -->
+ <depends optional-attribute-name="LookupPool"
+ proxy-type="attribute">jboss.system:service=ThreadPool</depends>
+ </mbean>
+
+ <mbean code="org.jboss.naming.JNDIView"
+ name="jboss:service=JNDIView"
+ xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Security -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.security.plugins.SecurityConfig"
+ name="jboss.security:service=SecurityConfig">
+ <attribute name="LoginConfig">jboss.security:service=XMLLoginConfig</attribute>
+ </mbean>
+ <mbean code="org.jboss.security.auth.login.XMLLoginConfig"
+ name="jboss.security:service=XMLLoginConfig">
+ <attribute name="ConfigResource">login-config.xml</attribute>
+ </mbean>
+
+ <!-- JAAS security manager and realm mapping -->
+ <mbean code="org.jboss.security.plugins.JaasSecurityManagerService"
+ name="jboss.security:service=JaasSecurityManager">
+ <!-- A flag which indicates whether the SecurityAssociation server mode
+ is set on service creation. This is true by default since the
+ SecurityAssociation should be thread local for multi-threaded server
+ operation.
+ -->
+ <attribute name="ServerMode">true</attribute>
+ <attribute name="SecurityManagerClassName">org.jboss.security.plugins.JaasSecurityManager</attribute>
+ <attribute name="DefaultUnauthenticatedPrincipal">anonymous</attribute>
+ <!-- DefaultCacheTimeout: Specifies the default timed cache policy timeout
+ in seconds.
+ If you want to disable caching of security credentials, set this to 0 to
+ force authentication to occur every time. This has no affect if the
+ AuthenticationCacheJndiName has been changed from the default value.
+ -->
+ <attribute name="DefaultCacheTimeout">1800</attribute>
+ <!-- DefaultCacheResolution: Specifies the default timed cache policy
+ resolution in seconds. This controls the interval at which the cache
+ current timestamp is updated and should be less than the DefaultCacheTimeout
+ in order for the timeout to be meaningful. This has no affect if the
+ AuthenticationCacheJndiName has been changed from the default value.
+ -->
+ <attribute name="DefaultCacheResolution">60</attribute>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Transactions -->
+ <!-- ==================================================================== -->
+ <!-- The configurable Xid factory. For use with Oracle, set pad to true -->
+ <mbean code="org.jboss.tm.XidFactory"
+ name="jboss:service=XidFactory">
+ <!--attribute name="Pad">true</attribute-->
+ </mbean>
+
+ <!--
+ | The fast in-memory transaction manager.
+ -->
+ <mbean code="org.jboss.tm.TransactionManagerService"
+ name="jboss:service=TransactionManager"
+ xmbean-dd="resource:xmdesc/TransactionManagerService-xmbean.xml">
+ <attribute name="TransactionTimeout">300</attribute>
+ <!-- set to false to disable transaction demarcation over IIOP -->
+ <attribute name="GlobalIdsEnabled">true</attribute>
+ <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
+
+ <!-- Transaction Integrity Checking -->
+ <!-- Force a rollback if another thread is associated with the transaction at commit -->
+ <!--depends optional-attribute-name="TransactionIntegrityFactory"
+ proxy-type="org.jboss.tm.integrity.TransactionIntegrityFactory">
+ <mbean code="org.jboss.tm.integrity.FailIncompleteTransaction"
+ name="jboss:service=TransactionManager,plugin=TransactionIntegrity"/>
+ </depends-->
+ </mbean>
+ <!--
+ | UserTransaction support.
+ -->
+ <mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService"
+ name="jboss:service=ClientUserTransaction"
+ xmbean-dd="resource:xmdesc/ClientUserTransaction-xmbean.xml">
+ <depends>
+ <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
+ name="jboss:service=proxyFactory,target=ClientUserTransactionFactory">
+ <attribute name="InvokerName">jboss:service=invoker,type=jrmp</attribute>
+ <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute>
+ <attribute name="JndiName">UserTransactionSessionFactory</attribute>
+ <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory</attribute>
+ <attribute name="ClientInterceptors">
+ <interceptors>
+ <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
+ <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
+ </interceptors>
+ </attribute>
+ <depends>jboss:service=invoker,type=jrmp</depends>
+ </mbean>
+ </depends>
+ <depends optional-attribute-name="TxProxyName">
+ <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
+ name="jboss:service=proxyFactory,target=ClientUserTransaction">
+ <attribute name="InvokerName">jboss:service=invoker,type=jrmp</attribute>
+ <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute>
+ <attribute name="JndiName"></attribute>
+ <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSession</attribute>
+ <attribute name="ClientInterceptors">
+ <interceptors>
+ <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
+ <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
+ </interceptors>
+ </attribute>
+ <depends>jboss:service=invoker,type=jrmp</depends>
+ </mbean>
+ </depends>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Invokers to the JMX node -->
+ <!-- ==================================================================== -->
+
+ <!-- RMI/JRMP invoker -->
+ <mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
+ name="jboss:service=invoker,type=jrmp">
+ <attribute name="RMIObjectPort">4444</attribute>
+ <attribute name="ServerAddress">${jboss.bind.address}</attribute>
+ <!--
+ <attribute name="RMIClientSocketFactory">custom</attribute>
+ <attribute name="RMIServerSocketFactory">custom</attribute>
+ <attribute name="RMIServerSocketAddr">custom</attribute>
+ <attribute name="SecurityDomain">ssl-domain-name</attribute>
+ -->
+ <depends>jboss:service=TransactionManager</depends>
+ </mbean>
+
+ <mbean code="org.jboss.invocation.local.LocalInvoker"
+ name="jboss:service=invoker,type=local">
+
+ <depends>jboss:service=TransactionManager</depends>
+ </mbean>
+
+ <mbean code="org.jboss.invocation.pooled.server.PooledInvoker"
+ name="jboss:service=invoker,type=pooled">
+ <attribute name="NumAcceptThreads">1</attribute>
+ <attribute name="MaxPoolSize">300</attribute>
+ <attribute name="ClientMaxPoolSize">300</attribute>
+ <attribute name="SocketTimeout">60000</attribute>
+ <attribute name="ServerBindAddress">${jboss.bind.address}</attribute>
+ <attribute name="ServerBindPort">4445</attribute>
+ <attribute name="ClientConnectAddress">${jboss.bind.address}</attribute>
+ <attribute name="ClientConnectPort">0</attribute>
+ <attribute name="ClientRetryCount">1</attribute>
+ <attribute name="EnableTcpNoDelay">false</attribute>
+
+ <!-- Customized socket factory attributes
+ <attribute name="ClientSocketFactoryName">custom.client.factory</attribute>
+ <attribute name="ServerSocketFactoryName">custom.server.factory</attribute>
+ <attribute name="SslDomain">java:/jaas/pooledInvoker</attribute>
+ -->
+ <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Monitoring and Management -->
+ <!-- ==================================================================== -->
+
+ <!-- Uncomment to enable JMX monitoring of the bean cache
+ <mbean code="org.jboss.monitor.BeanCacheMonitor"
+ name="jboss.monitor:name=BeanCacheMonitor"/>
+ -->
+
+ <!-- Uncomment to enable JMX monitoring of the entity bean locking
+ <mbean code="org.jboss.monitor.EntityLockMonitor"
+ name="jboss.monitor:name=EntityLockMonitor"/>
+ -->
+
+ <!-- ==================================================================== -->
+ <!-- An MBean that is a registry for JDBC type-mapping metadata -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary"
+ name="jboss.jdbc:service=metadata"/>
+
+ <!-- ==================================================================== -->
+ <!-- Deployment Scanning -->
+ <!-- ==================================================================== -->
+
+ <!-- An mbean for hot deployment/undeployment of archives.
+ -->
+ <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
+ name="jboss.deployment:type=DeploymentScanner,flavor=URL">
+
+ <!-- Uncomment (and comment/remove version below) to enable usage of the
+ DeploymentCache
+ <depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache</depends>
+ -->
+ <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>
+
+ <!-- The URLComparator can be used to specify a deployment ordering
+ for deployments found in a scanned directory. The class specified
+ must be an implementation of java.util.Comparator, it must be able
+ to compare two URL objects, and it must have a no-arg constructor.
+ Two deployment comparators are shipped with JBoss:
+ - org.jboss.deployment.DeploymentSorter
+ Sorts by file extension, as follows:
+ "sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip",
+ "*"
+ - org.jboss.deployment.scanner.PrefixDeploymentSorter
+ If the name portion of the url begins with 1 or more digits, those
+ digits are converted to an int (ignoring leading zeroes), and
+ files are deployed in that order. Files that do not start with
+ any digits will be deployed first, and they will be sorted by
+ extension as above with DeploymentSorter.
+ -->
+ <attribute name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute>
+
+ <!--
+ <attribute name="URLComparator">org.jboss.deployment.scanner.PrefixDeploymentSorter</attribute>
+ -->
+
+ <!-- The FilterInstance specifies a URLLister.URLFilter for scanned
+ directories. This DeploymentFilter is initialized with the given
+ prefixes, suffixes and matches that define which URLs should be
+ ignored.
+ -->
+ <attribute name="FilterInstance"
+ attributeClass="org.jboss.deployment.scanner.DeploymentFilter"
+ serialDataType="javaBean">
+ <!-- Files starting with theses strings are ignored -->
+ <property name="prefixes">#,%,\,,.,_$</property>
+ <!-- Files ending with theses strings are ignored -->
+ <property name="suffixes">#,$,%,~,\,v,.BAK,.bak,.old,.orig,.tmp,.rej,.sh</property>
+ <!-- Files matching with theses strings are ignored -->
+ <property name="matches">.make.state,.nse_depinfo,CVS,CVS.admin,RCS,RCSLOG,SCCS,TAGS,core,tags</property>
+ </attribute>
+
+ <!-- Frequency in milliseconds to rescan the URLs for changes -->
+ <attribute name="ScanPeriod">5000</attribute>
+
+ <!-- A flag to disable the scans -->
+ <attribute name="ScanEnabled">true</attribute>
+
+ <!-- URLs are comma separated and resolve relative to the server home URL
+ unless the given path is absolute. If the URL ends in "/" it is
+ considered a collection and scanned, otherwise it is simply deployed;
+ this follows RFC2518 convention and allows discrimination between
+ collections and directories that are simply unpacked archives.
+
+ URLs may be local (file:) or remote (http:). Scanning is supported
+ for remote URLs but unpacked deployment units are not.
+
+ Example URLs:
+ deploy/
+ scans ${jboss.server.url}/deploy/, which is local or remote
+ depending on the URL used to boot the server
+ ${jboss.server.home}/deploy/
+ scans ${jboss.server.home)/deploy, which is always local
+ file:/var/opt/myapp.ear
+ deploy myapp.ear from a local location
+ file:/var/opt/apps/
+ scans the specified directory
+ http://www.test.com/netboot/myapp.ear
+ deploys myapp.ear from a remote location
+ http://www.test.com/netboot/apps/
+ scans the specified WebDAV location
+ -->
+ <attribute name="URLs">
+ deploy/
+ </attribute>
+
+ <!-- Indicates if the scanner should recursively scan directories that
+ contain no "." in their names. This can be used to group applications
+ and services that must be deployed and that have the same
+ logical function in the same directory i.e.
+ deploy/JMX/
+ deploy/JMS/
+ ...
+ -->
+ <attribute name="RecursiveSearch">True</attribute>
+
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/sybase-jdbc2-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/sybase-jdbc2-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/sybase-jdbc2-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,85 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: sybase-jdbc2-service.xml 61575 2007-03-22 14:35:46Z adrian at jboss.org $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Persistence and caching using Sybase -->
+ <!-- Based on configuration provided by amresh.deshmukh at drkw.com -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | The destination manager is the core service within JBossMQ
+ -->
+ <mbean code="org.jboss.mq.server.jmx.DestinationManager" name="jboss.mq:service=DestinationManager">
+ <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>
+ <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>
+ <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>
+ </mbean>
+
+ <!--
+ | The MessageCache decides where to put JBossMQ message that
+ | are sitting around waiting to be consumed by a client.
+ |
+ | The memory marks are in Megabytes. Once the JVM memory usage hits
+ | the high memory mark, the old messages in the cache will start getting
+ | stored in the DataDirectory. As memory usage gets closer to the
+ | Max memory mark, the amount of message kept in the memory cache aproaches 0.
+ -->
+ <mbean code="org.jboss.mq.server.MessageCache"
+ name="jboss.mq:service=MessageCache">
+ <attribute name="HighMemoryMark">50</attribute>
+ <attribute name="MaxMemoryMark">60</attribute>
+ <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
+ </mbean>
+
+ <!--
+ | The jdbc2 PersistenceManager is the new improved JDBC implementation.
+ | This implementation allows you to control how messages are stored in
+ | the database.
+ |
+ | Take care that the selected blob column type in jms_messages can store
+ | all message data. Some databases (e.g. mySQL) offer blob types with
+ | different maximum capacity (e.g. mySQL-type BLOB=64K, LONGBLOB=2G).
+ |
+ | If you encouter problems with the configured BLOB_TYPE try a different
+ | setting. Valid settings are OBJECT_BLOB, BINARYSTREAM_BLOB and BYTES_BLOB.
+ -->
+ <mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
+ name="jboss.mq:service=PersistenceManager">
+ <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=jdbc/SybaseDB</depends>
+ <attribute name="SqlProperties">
+ BLOB_TYPE=BYTES_BLOB
+ INSERT_TX = INSERT INTO dbo.JMS_TRANSACTIONS (TXID) values(?)
+ INSERT_MESSAGE = INSERT INTO dbo.JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
+ SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM dbo.JMS_TRANSACTIONS
+ SELECT_MAX_TX = SELECT MAX(X.TXID) FROM (SELECT MAX(TXID) AS TXID FROM dbo.JMS_TRANSACTIONS UNION SELECT MAX(TXID) AS TXID FROM dbo.JMS_MESSAGES) X
+ DELETE_ALL_TX = DELETE FROM dbo.JMS_TRANSACTIONS
+ SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM dbo.JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE_KEYS_IN_DEST = SELECT MESSAGEID FROM dbo.JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM dbo.JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ MARK_MESSAGE = UPDATE dbo.JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MESSAGE = UPDATE dbo.JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MARKED_MESSAGES = UPDATE dbo.JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
+ UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE dbo.JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
+ DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM dbo.JMS_MESSAGES WHERE TXID IN (SELECT TXID FROM dbo.JMS_TRANSACTIONS) AND TXOP=?
+ DELETE_TX = DELETE FROM dbo.JMS_TRANSACTIONS WHERE TXID = ?
+ DELETE_MARKED_MESSAGES = DELETE FROM dbo.JMS_MESSAGES WHERE TXID=? AND TXOP=?
+ DELETE_TEMPORARY_MESSAGES = DELETE FROM dbo.JMS_MESSAGES WHERE TXOP='T'
+ DELETE_MESSAGE = DELETE FROM dbo.JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ CREATE_MESSAGE_TABLE = CREATE TABLE dbo.JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \
+ DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER NULL, TXOP CHAR(1) NOT NULL, \
+ MESSAGEBLOB IMAGE NOT NULL, PRIMARY KEY (MESSAGEID, DESTINATION) ) LOCK DATAROWS
+ CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX dbo.JMS_MESSAGES_TXOP_TXID ON dbo.JMS_MESSAGES (TXOP, TXID)
+ CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX dbo.JMS_MESSAGES_DESTINATION ON dbo.JMS_MESSAGES (DESTINATION)
+ CREATE_TX_TABLE = CREATE TABLE dbo.JMS_TRANSACTIONS ( TXID INTEGER NOT NULL, PRIMARY KEY (TXID) ) \
+ LOCK DATAROWS
+ CREATE_TABLES_ON_STARTUP = TRUE
+ </attribute>
+ <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
+ <!--attribute name="RecoveryTimeout">0</attribute-->
+ <!-- The number of blobs to load at once during message recovery -->
+ <attribute name="RecoverMessagesChunk">0</attribute>
+ </mbean>
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/uil-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/uil-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jms/uil-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: uil-service.xml 19392 2004-03-05 12:35:23Z ejort $ -->
+
+<server>
+
+ <!-- Deprecated use UIL2 -->
+
+ <mbean code="org.jboss.mq.il.uil.UILServerILService"
+ name="jboss.mq:service=InvocationLayer,type=UIL">
+ <depends optional-attribute-name="Invoker">jboss.mq:service=Invoker</depends>
+ <attribute name="ConnectionFactoryJNDIRef">UILConnectionFactory</attribute>
+ <attribute name="XAConnectionFactoryJNDIRef">UILXAConnectionFactory</attribute>
+ <attribute name="ServerBindPort">8091</attribute>
+ <!-- FIXME: ping disabled because of deadlock problem -->
+ <attribute name="PingPeriod">0</attribute>
+<!-- <attribute name="PingPeriod">60000</attribute> -->
+ <attribute name="EnableTcpNoDelay">true</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/ejb-management.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/ejb-management.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/deploy/default-ds-monitor-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/deploy/default-ds-monitor-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/deploy/default-ds-monitor-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE server PUBLIC
+ "-//JBoss//DTD MBean Service 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-service_4_0.dtd">
+
+<!-- $Id: default-ds-monitor-service.xml 34694 2005-08-07 12:33:37Z dimitris $ -->
+
+<!--============================================================================
+ | DefaultDS LoggingMonitor Service Configuration
+ |
+ | An example configuration of the LoggingMonitor service to monitor the JBoss
+ | default datasource.
+ |===========================================================================-->
+<server>
+
+ <mbean code="org.jboss.services.loggingmonitor.LoggingMonitor"
+ name="jboss.monitor:type=LoggingMonitor,name=DefaultDSMonitor">
+
+ <!--
+ | The name of the file to which monitoring information will be logged.
+ -->
+ <attribute name="Filename">${jboss.server.home.dir}/log/default-ds.log</attribute>
+
+ <!--
+ | Whether or not this monitor's log file should have information appended
+ | to it, if it already exists. This attribute is *not* required, and the
+ | default value is true.
+ -->
+ <attribute name="AppendToFile">false</attribute>
+
+ <!--
+ | Controls the org.apache.log4j.PatternLayout for logging entries.
+ | The default pattern is "%d %-5p [%c] %m%n".
+ <attribute name="PatternLayout">%d %-5p [%c] %m%n</attribute>
+ -->
+
+ <!--
+ | The rollover period for this monitor's log file. Valid values are
+ | MONTH, WEEK, DAY, HALFDAY, HOUR, MINUTE (case insensitive). This
+ | attributes is *not* required, and the default value is DAY.
+ -->
+ <attribute name="RolloverPeriod">DAY</attribute>
+
+ <!--
+ | The period to delay in between monitoring snapshots (in milliseconds).
+ -->
+ <attribute name="MonitorPeriod">5000</attribute>
+
+ <!--
+ | The list of objects (MBeans) and their corresponding attributes to be
+ | monitored.
+ |
+ | This parameter is specified as a XML fragment as follows:
+ |
+ | <attribute name="MonitoredObjects">
+ | <configuration>
+ | <monitoredmbean name="[object name]"
+ | logger="[logger name]">
+ | <attribute>[an attribute name]</attribute>
+ | <attribute>[an attribute name]</attribute>
+ | ...
+ | </monitoredmbean>
+ | </configuration>
+ | </attribute>
+ -->
+ <attribute name="MonitoredObjects">
+ <configuration>
+ <monitoredmbean name="jboss.jca:name=DefaultDS,service=ManagedConnectionPool"
+ logger="jca.defaultds">
+ <attribute>InUseConnectionCount</attribute>
+ <attribute>AvailableConnectionCount</attribute>
+ <attribute>ConnectionCreatedCount</attribute>
+ <attribute>ConnectionDestroyedCount</attribute>
+ <attribute>MaxConnectionsInUseCount</attribute>
+ </monitoredmbean>
+ </configuration>
+ </attribute>
+
+ <depends>jboss.jca:name=DefaultDS,service=ManagedConnectionPool</depends>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/deploy/jvm-monitor-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/deploy/jvm-monitor-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/deploy/jvm-monitor-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE server PUBLIC
+ "-//JBoss//DTD MBean Service 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-service_4_0.dtd">
+
+<!-- $Id: jvm-monitor-service.xml 34694 2005-08-07 12:33:37Z dimitris $ -->
+
+<!--============================================================================
+ | JVM LoggingMonitor Service Configuration
+ |
+ | An example configuration of the LoggingMonitor service to monitor JVM thread
+ | and heap useage information.
+ |===========================================================================-->
+<server>
+
+ <mbean code="org.jboss.services.loggingmonitor.LoggingMonitor"
+ name="jboss.monitor:type=LoggingMonitor,name=JVMMonitor">
+
+ <!--
+ | The name of the file to which monitoring information will be logged.
+ -->
+ <attribute name="Filename">${jboss.server.home.dir}/log/jvm.log</attribute>
+
+ <!--
+ | Whether or not this monitor's log file should have information appended
+ | to it, if it already exists. This attribute is *not* required, and the
+ | default value is true.
+ -->
+ <attribute name="AppendToFile">false</attribute>
+
+ <!--
+ | Controls the org.apache.log4j.PatternLayout for logging entries.
+ | The default pattern is "%d %-5p [%c] %m%n".
+ <attribute name="PatternLayout">%d %-5p [%c] %m%n</attribute>
+ -->
+
+ <!--
+ | The rollover period for this monitor's log file. Valid values are
+ | MONTH, WEEK, DAY, HALFDAY, HOUR, MINUTE (case insensitive). This
+ | attributes is *not* required, and the default value is DAY.
+ -->
+ <attribute name="RolloverPeriod">DAY</attribute>
+
+ <!--
+ | The period to delay in between monitoring snapshots (in milliseconds).
+ -->
+ <attribute name="MonitorPeriod">10000</attribute>
+
+ <!--
+ | The list of objects (MBeans) and their corresponding attributes to be
+ | monitored.
+ |
+ | This parameter is specified as a XML fragment as follows:
+ |
+ | <attribute name="MonitoredObjects">
+ | <configuration>
+ | <monitoredmbean name="[object name]"
+ | logger="[logger name]">
+ | <attribute>[an attribute name]</attribute>
+ | <attribute>[an attribute name]</attribute>
+ | ...
+ | </monitoredmbean>
+ | </configuration>
+ | </attribute>
+ -->
+ <attribute name="MonitoredObjects">
+ <configuration>
+ <monitoredmbean name="jboss.system:type=ServerInfo" logger="jvm.threads">
+ <attribute>ActiveThreadCount</attribute>
+ </monitoredmbean>
+ <monitoredmbean name="jboss.system:type=ServerInfo" logger="jvm.heap">
+ <attribute>FreeMemory</attribute>
+ <attribute>TotalMemory</attribute>
+ <attribute>MaxMemory</attribute>
+ </monitoredmbean>
+ </configuration>
+ </attribute>
+
+ <!--
+ | Since this logging monitor only depends upon the ServerInfo MBean, a
+ | non-service MBean, no dependancies can be specified.
+ -->
+ <!-- <depends>jboss.system:type=ServerInfo</depends> -->
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/lib/logging-monitor.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/lib/logging-monitor.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/readme.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/readme.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/logging-monitor/readme.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,92 @@
+JBoss LoggingMonitor Service
+----------------------------
+
+--- $Id: readme.txt 34694 2005-08-07 12:33:37Z dimitris $ ----
+
+INTRODUCTION
+
+The JBoss LoggingMonitor service is similar in purpose to the other monitoring
+services provided as a part of JBossAS. The JBoss LoggingMonitor service
+monitor's the specified attributes of a MBean periodically and logs their value
+to the filename specified. This file can then be used for debugging and/or
+charting JBoss services information based upon your specific use case(s).
+
+The JBoss LoggingMonitor service graduated succesfully from the
+"JBoss World Of MBeans", to the jboss codebase. You can read more
+about this here: http://www.jboss.org/wiki/Wiki.jsp?page=JBossWorldOfMBeans.
+
+Additional information about the service maybe found in the JBoss wiki:
+http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossLoggingMonitor
+
+Questions regarding the use of the JBoss LoggingMonitor service should be
+directed to the "Management, JMX/JBoss" user forum.
+
+INSTALLATION/USE
+
+Place the ./lib/logging-monitor.jar file in the lib directory of your JBoss server
+configuration, and hot-deploy your customized *-service.xml file to your server
+configuration's deploy directory. Multiple *-service.xml files can be deployed
+simultaneously utilizing this MBean. Examples of various *-service.xml files
+can be found in the ./deploy subdirectory.
+
+*-SERVICE.XML FILE FORMAT
+
+The JBoss LoggingMonitor service MBean's configuration file format is the same
+as most JBoss MBean services. Its DTD is specified at
+http://www.jboss.org/j2ee/dtd/jboss-service_4_0.dtd.
+
+The following is a description of the attributes and their possible values:
+
+Attribute Description
+--------- -----------
+
+Filename The name of the file to which monitoring information will be
+ logged. This attribute can not be set to null or the be
+ empty.
+
+AppendToFile Whether or not a monitor's log file should have information
+ appended to it, if it already exists. This attribute is *not*
+ required, and the default value is "true".
+
+PatternLayout Controls the org.apache.log4j.PatternLayout for logging entries.
+ The default pattern is "%d %-5p [%c] %m%n".
+
+RolloverPeriod The rollover period for the monitor's log file. Valid values
+ are MONTH, WEEK, DAY, HALFDAY, HOUR, and MINUTE (case
+ insensitive). This attribute is *not* required, and the
+ default value is DAY.
+
+MonitoredObjects The list of objects (MBeans) and their corresponding
+ attributes to be monitored.
+
+ This parameter is specified as a XML fragment as follows:
+
+ <configuration>
+ <monitoredmbean name="[object name]"
+ logger="[logger name]">
+ <attribute>[attribute name]</attribute>
+ <attribute>[attribute name]</attribute>
+ ...
+ </monitoredmbean>
+ ...
+ </configuration>
+
+ [object name] is the name of the MBean to be monitored.
+
+ [logger name] the name of the logger to be used when logging
+ attribute information.
+
+ [attribute name] the name of an attribute to be logged.
+
+ As the XML fragment indicates, any number of MBeans can be
+ monitored, and any number of attributes for a given MBean can
+ be specified.
+
+MonitorPeriod The frequency with which to log information (in milliseconds).
+ This attribute must have a non-zero, positive value.
+
+AUTHORS
+
+James Wilson, original code
+Dimitris Andreadis, integration into the jboss codebase
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/META-INF/MANIFEST.MF
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/META-INF/MANIFEST.MF (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/META-INF/MANIFEST.MF 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,13 @@
+Manifest-Version: 1.0
+Ant-Version: Apache Ant 1.6.2
+Created-By: 1.5.0_11-b03 (Sun Microsystems Inc.)
+Specification-Title: JBoss
+Specification-Version: 4.2.0.GA
+Specification-Vendor: JBoss (http://www.jboss.org/)
+Implementation-Title: JBoss [Trinity]
+Implementation-URL: http://www.jboss.org/
+Implementation-Version: 4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=20
+ 0705111440)
+Implementation-Vendor: JBoss Inc.
+Implementation-Vendor-Id: http://www.jboss.org/
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/META-INF/jboss-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/META-INF/jboss-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/META-INF/jboss-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,143 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: jboss-service.xml 23704 2004-09-14 20:29:40Z andd $ -->
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- Example Service using "external" XMBean persistence -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<server>
+ <mbean code="org.jboss.jmx.examples.persistence.PersistentServiceExample"
+ name="jboss.jmx:service=PersistentServiceExample"
+ xmbean-dd="">
+
+ <!-- Inline xmbean descriptor
+
+ This is a normal XMBean descriptor, the only different being the
+ specification of the DelegatingPersistenceManager as a persistence-manager.
+
+ This persistence manager will invoke a factory operations
+ (by default apmCreate()) on an external MBean service
+ (by default jboss:service=AttributePersistenceService),
+ in order to get a reference to an AttributePersistenceManager
+ implementation.
+
+ The actual AttributePersistenceManager implementation is instantiated
+ by the AttributePersistenceService and shared by many
+ DelegatingPersistenceManagers. By default an XMLAttributePersistenceManager
+ is instantiated, but other implementations are possible.
+
+ The external AttributePersistenceService can be use to manage at runtime
+ the AttributePersistenceManager implementation, i.e. list persisted ids,
+ remove persisted images, or specify a particular 'version-tag' for all
+ saved information.
+
+ It is important that the external AttributePersistenceService is
+ operational when the XMBean that uses it is instantiated. This will
+ normally not be a problem since the AttributePersistenceService is most
+ probably started by conf/jboss-service.xml
+ -->
+ <xmbean>
+ <description>PersistentServiceExample</description>
+ <descriptors>
+ <persistence persistPolicy="OnUpdate"/>
+ <!-- persistLocation is ignored
+
+ persistName="PersistentServiceExample"
+
+ an alternative persistent id may be specified with
+ persistName; by default the ObjectName will used -->
+
+ <!-- THIS IS IMPORTANT -->
+ <persistence-manager value="org.jboss.mx.persistence.DelegatingPersistenceManager"/>
+
+ <!-- May use a different external AttributePersistenceService; default should be ok.
+ <descriptor name="attribute-persistence-service" value="jboss:service=AttributePersistenceService"/>
+ <descriptor name="attribute-persistence-operation" value="apmCreate"/>
+ -->
+ </descriptors>
+ <class>org.jboss.jmx.examples.persistence.PersistentServiceExample</class>
+
+ <!-- Attributes -->
+
+ <attribute access="read-write" getMethod="getSomeBigDecimal" setMethod="setSomeBigDecimal">
+ <name>SomeBigDecimal</name>
+ <type>java.math.BigDecimal</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="isSomeBoolean" setMethod="setSomeBoolean">
+ <name>SomeBoolean</name>
+ <type>boolean</type>
+ </attribute>
+
+ <!-- This is an XML element -->
+ <attribute access="read-write" getMethod="getSomeElement" setMethod="setSomeElement">
+ <name>SomeElement</name>
+ <type>org.w3c.dom.Element</type>
+ </attribute>
+
+ <!-- We can specify that an attribute is never persisted
+ If we remove the "persistPolicy" - "Never" descriptor we'll
+ probably get a warning since the java.io.FileDescriptor
+ cannot be persisted. Try it! -->
+ <attribute access="read-write" getMethod="getSomeFileDescriptor" setMethod="setSomeFileDescriptor">
+ <name>SomeFileDescriptor</name>
+ <type>java.io.FileDescriptor</type>
+ <descriptors>
+ <descriptor name="persistPolicy" value="Never"/>
+ </descriptors>
+ </attribute>
+
+ <!-- primitive types (e.g. int) are boxed during persistence
+ (e.g java.lang.Integer) -->
+ <attribute access="read-write" getMethod="getSomeInt" setMethod="setSomeInt">
+ <name>SomeInt</name>
+ <type>int</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getSomeInteger" setMethod="setSomeInteger">
+ <name>SomeInteger</name>
+ <type>java.lang.Integer</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getSomeString" setMethod="setSomeString">
+ <name>SomeString</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getSomeTimestamp" setMethod="setSomeTimestamp">
+ <name>SomeTimestamp</name>
+ <type>java.sql.Timestamp</type>
+ <descriptors>
+ <descriptor name="currencyTimeLimit" value="10"/>
+ </descriptors>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getSomeNullObject" setMethod="setSomeNullObject">
+ <name>SomeNullObject</name>
+ <type>java.lang.Object</type>
+ </attribute>
+
+ <!-- Again, although the java.util.ArrayList is Serializable,
+ it cannot be persisted in this case because it contains
+ non-serializable content -->
+ <attribute access="read-write" getMethod="getSomeArrayList" setMethod="setSomeArrayList">
+ <name>SomeArrayList</name>
+ <type>java.util.ArrayList</type>
+ <descriptors>
+ <descriptor name="persistPolicy" value="Never"/>
+ </descriptors>
+ </attribute>
+
+ </xmbean>
+ <!-- XMBean Descriptor END -->
+
+ <!-- Normal Attribute Overrides Here, for Example: -->
+ <attribute name="SomeElement">
+ <some-message>Welcome to the Athens 2004, Olympic Games!</some-message>
+ </attribute>
+
+ </mbean>
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/org/jboss/jmx/examples/persistence/PersistentServiceExample.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/org/jboss/jmx/examples/persistence/PersistentServiceExample.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/org/jboss/jmx/examples/persistence/PersistentServiceExampleMBean.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/jmx/persistent-service.sar/org/jboss/jmx/examples/persistence/PersistentServiceExampleMBean.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/netboot/netboot.war
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/netboot/netboot.war
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/build.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/build.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/build.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project default="install" name="installer">
+
+ <property name="server.default" value="../../../../server/default"/>
+
+ <target name="install"
+ description="Installs the DeploymentService to the default configuration">
+
+ <copy todir="${server.default}/conf">
+ <fileset dir=".">
+ <include name="templates/**"/>
+ </fileset>
+ </copy>
+
+ <mkdir dir="${server.default}/deploy/deployment-service.sar"/>
+ <unjar src="deployment-service.sar"
+ dest="${server.default}/deploy/deployment-service.sar"/>
+
+ </target>
+
+ <target name="clean"
+ description="Cleans up the DeploymentService from the default configuration">
+
+ <delete dir="${server.default}/deploy/deployment-service.sar"/>
+ <delete dir="${server.default}/conf/templates"/>
+
+ </target>
+
+</project>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/deployment-service.sar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/deployment-service.sar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/readme.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/readme.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/readme.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,6 @@
+
+ant install - installs the DeploymentService
+ant clean - uninstalls the DeploymentService
+
+For more info, see:
+http://www.jboss.org/wiki/Wiki.jsp?page=DeploymentService
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/schema/jboss-template-config.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/schema/jboss-template-config.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/schema/jboss-template-config.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ XML Schema used by DeploymentManager
+ when loading configuration templates
+
+ $Revision: 25695 $
+
+ Authors
+ <a href="mailto:dimitris at jboss.org">Dimitris Andreadis</a>
+-->
+<xsd:schema
+ targetNamespace="http://www.jboss.org/"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ xmlns="http://www.w3.org/2001/XMLSchema">
+
+ <xsd:annotation>
+ <xsd:documentation xml:lang="en">
+ XML Schema used by DeploymentManager
+ when loading configuration templates.
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:element name="template-config">
+ <xsd:complexType>
+ <xsd:sequence>
+
+ <xsd:element name="description" type="xsd:string" minOccurs="0" maxOccurs="1"/>
+
+ <xsd:element name="property-list" minOccurs="0" maxOccurs="1">
+ <xsd:complexType>
+ <xsd:sequence>
+ <xsd:element name="property" minOccurs="1" maxOccurs="unbounded">
+ <xsd:complexType>
+ <xsd:sequence>
+ <xsd:element name="description" type="xsd:string" minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="default-value" type="xsd:string" minOccurs="0" maxOccurs="1"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="string" use="required"/>
+ <xsd:attribute name="type" type="string" use="optional" default="java.lang.String"/>
+ <xsd:attribute name="optional" type="string" use="optional"/>
+ </xsd:complexType>
+ </xsd:element>
+ </xsd:sequence>
+ </xsd:complexType>
+ </xsd:element>
+
+ <xsd:element name="template-list" minOccurs="0" maxOccurs="1">
+ <xsd:complexType>
+ <xsd:sequence>
+ <xsd:element name="template" minOccurs="1" maxOccurs="unbounded">
+ <xsd:complexType>
+ <xsd:attribute name="input" type="string" use="required"/>
+ <xsd:attribute name="output" type="string" use="required"/>
+ </xsd:complexType>
+ </xsd:element>
+ </xsd:sequence>
+ </xsd:complexType>
+ </xsd:element>
+
+ </xsd:sequence>
+ <xsd:attribute name="template" type="string" use="optional"/>
+ <xsd:attribute name="copydir" type="string" use="optional"/>
+ <xsd:attribute name="extension" type="string" use="optional"/>
+ </xsd:complexType>
+
+ </xsd:element>
+
+</xsd:schema>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/VM_global_library.vm
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/VM_global_library.vm (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/VM_global_library.vm 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,32 @@
+## ---------------------------------------------------------
+## Velocity macros to be shared by all DeploymentService
+## velocity templates.
+##
+## $Id: VM_global_library.vm 25695 2004-11-09 18:52:46Z andd $
+## ---------------------------------------------------------
+
+## --------------------------------------------------------
+## ifDefReplace
+##
+## If $substr is contained in $string then produce $replace
+##
+## $string and $substr must be Strings
+## --------------------------------------------------------
+#macro(ifDefReplace $string $substr $replace)
+#if($string.indexOf($substr) >= 0)
+$replace#end
+#end
+
+## --------------------------------------------------------
+## firstToken
+##
+## If $delim appears in $string, produce all characters
+## up to $delim, else, produce $string
+##
+## $string and $delim must be Strings
+## --------------------------------------------------------
+#macro(firstToken $string $delim)
+#if($string.indexOf($delim))
+$string.substring(0, $string.indexOf($delim))#else
+$string#end
+#end
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/jms-queue/template-config.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/jms-queue/template-config.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/jms-queue/template-config.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Example template configuration that produces a JMS-Queue
+ deployment descriptor.
+
+ Documentation for the deployment service can be found at:
+ http://www.jboss.org/wiki/Wiki.jsp?page=DeploymentService
+-->
+<template-config template="vm/jms-queue.xml.vm" extension="-service.xml">
+
+ <property-list>
+ <!-- if type not specified, java.lang.String is assumed -->
+ <!-- a value must be supplied at runtime, or an exception will be thrown -->
+ <property name="QueueName"/>
+
+ <!-- if a value is not supplied at runtime, the default will be used -->
+ <property name="DestinationManager" type="javax.management.ObjectName">
+ <default-value>jboss.mq:service=DestinationManager</default-value>
+ </property>
+
+ <!-- mark a property with optional=true so that a value is not required -->
+ <!-- any specified default will be ignored in this case -->
+ <property name="SecurityManager" type="javax.management.ObjectName" optional="true">
+ <default-value>jboss.mq:service=SecurityManager</default-value>
+ </property>
+
+ <!-- arrays and generally any valid java/user class is permitted -->
+ <property name="SecurityRoles" type="[Ljava.lang.String;" optional="true"/>
+ </property-list>
+
+</template-config>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/jms-queue/vm/jms-queue.xml.vm
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/jms-queue/vm/jms-queue.xml.vm (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/jms-queue/vm/jms-queue.xml.vm 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Automatically generated by DeploymentService
+ ===================================================================
+ QueueName - $QueueName
+ DestinationManager - $DestinationManager
+ SecurityManager - $SecurityManager
+ SecurityRoles - $SecurityRoles
+ ===================================================================
+-->
+<server>
+ <mbean code="org.jboss.mq.server.jmx.Queue"
+ name="jboss.mq.destination:service=Queue,name=$QueueName">
+
+ <depends optional-attribute-name="DestinationManager">$DestinationManager</depends>
+#if($SecurityManager)
+ <depends optional-attribute-name="SecurityManager">$SecurityManager</depends>
+#end
+#if($SecurityRoles)
+ <attribute name="SecurityConf">
+ <security>
+#foreach($role in $SecurityRoles)
+ <role name="#firstToken($role ':')" #ifDefReplace($role "read" 'read="true"') #ifDefReplace($role "write" 'write="true"') #ifDefReplace($role "create" 'create="true"')/>
+#end
+ </security>
+ </attribute>
+#end
+ </mbean>
+</server>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/local-tx-datasource/template-config.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/local-tx-datasource/template-config.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/local-tx-datasource/template-config.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,127 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Template configuration that produces a local-tx-datasource
+ deployment descriptor.
+
+ $Id: template-config.xml 29103 2005-02-24 12:22:56Z andd $
+-->
+<template-config template="vm/local-tx-datasource.vm" extension="-ds.xml">
+
+ <property-list>
+ <property name="jndi-name" type="java.lang.String">
+ <description>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.</description>
+ </property>
+
+ <property name="use-java-context" type="java.lang.Boolean" optional="true">
+ <description>Setting this to false will bind the DataSource into global jndi.</description>
+ <default-value>true</default-value>
+ </property>
+
+ <property name="connection-url" type="java.lang.String">
+ <description>The JDBC driver connection URL string.</description>
+ </property>
+
+ <property name="driver-class" type="java.lang.String">
+ <description>The fully qualifed name of the JDBC driver class.</description>
+ </property>
+
+ <property name="transaction-isolation" type="java.lang.String" optional="true">
+ <description>The java.sql.Connection transaction isolation level to use. The possible values are
+ TRANSACTION_READ_UNCOMMITTED
+ TRANSACTION_READ_COMMITTED
+ TRANSACTION_REPEATABLE_READ
+ TRANSACTION_SERIALIZABLE
+ TRANSACTION_NONE
+ </description>
+ </property>
+
+ <property name="connection-properties" type="java.util.Hashtable" optional="true">
+ <description>Allows you to pass in arbitrary connection properties (string name/value pairs) to the Driver.connect(url, props) method.</description>
+ </property>
+
+ <property name="user-name" type="java.lang.String" optional="true">
+ <description>Specifies the default username used when creating a new connection.</description>
+ </property>
+
+ <property name="password" type="java.lang.String" optional="true">
+ <description>Specifies the default password used when creating a new connection.</description>
+ </property>
+
+ <!-- The two properties that follow are related -->
+ <property name="security-config" type="java.lang.String" optional="true">
+ <description>
+ The value of this property should be one of:
+ APPLICATION-MANAGED-SECURITY - Indicates that app supplied parameters (such as from getConnection(user, pw)) are used to distinguish connections in the pool.
+ SECURITY-DOMAIN - Indicates that the Subject (from the security domain) is used to distinguish connections in the pool.
+ SECURITY-DOMAIN-AND-APPLICATION - Indicates that either app suplied parameters or the Subject are used to distinguish connections in the pool.
+ </description>
+ </property>
+
+ <property name="security-domain" type="java.lang.String" optional="true">
+ <description>When the security-config is either SECURITY-DOMAIN or SECURITY-DOMAIN-AND-APPLICATION this property should define the name of the JAAS security manager handling authentication, which correlates to the login-config.xml descriptor, application-policy/name attribute.</description>
+ </property>
+
+ <property name="min-pool-size" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ <default-value>0</default-value>
+ </property>
+
+ <property name="max-pool-size" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ <default-value>20</default-value>
+ </property>
+
+ <property name="blocking-timeout-millis" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ <default-value>30000</default-value>
+ </property>
+
+ <property name="idle-timeout-minutes" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ </property>
+
+ <property name="no-tx-separate-pools" type="java.lang.Boolean" optional="true">
+ <description>Indicates whether to use separete pools for connection retrieved in a transaction and those retrieved outside a transaction.</description>
+ <default-value>false</default-value>
+ </property>
+
+ <property name="new-connection-sql" type="java.lang.String" optional="true">
+ <description>Specify an SQL statement to execute whenever a connection is added to the connection pool.</description>
+ </property>
+
+ <property name="check-valid-connection-sql" type="java.lang.String" optional="true">
+ <description>Specify an SQL statement to check validity of a pool connection. This may be called when managed connection is taken from pool for use.</description>
+ </property>
+
+ <property name="valid-connection-checker-class-name" type="java.lang.String" optional="true">
+ <description>An org.jboss.resource.adapter.jdbc.ValidConnectionChecker that provides an SQLException isValidConnection(Connection e) method to validate if a connection is valid. An exception means the connection is destroyed. This overrides the check-valid-connection-sql when present.</description>
+ </property>
+
+ <property name="exception-sorter-class-name" type="java.lang.String" optional="true">
+ <description>An org.jboss.resource.adapter.jdbc.ExceptionSorter that provides a boolean isExceptionFatal(SQLException e) method to validate if an exception should be broadcast to all javax.resource.spi.ConnectionEventListener as a connectionErrorOccurred message.</description>
+ </property>
+
+ <property name="track-statements" type="java.lang.String" optional="true">
+ <description>Specifies 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)
+ </description>
+ <default-value>NOWARN</default-value>
+ </property>
+
+ <property name="prepared-statement-cache-size" type="java.lang.Integer" optional="true">
+ <description>The number of prepared statements per connection in an LRU cache.</description>
+ </property>
+
+ <property name="dependencies" type="[Ljavax.management.ObjectName;" optional="true">
+ <description>ObjectNames of services the connection manager depends on.</description>
+ </property>
+
+ <property name="type-mapping" type="java.lang.String" optional="true">
+ <description>Datasource/connection factory type-mapping.</description>
+ </property>
+
+ </property-list>
+
+</template-config>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/local-tx-datasource/vm/local-tx-datasource.vm
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/local-tx-datasource/vm/local-tx-datasource.vm (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/local-tx-datasource/vm/local-tx-datasource.vm 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,128 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ ===================================================================
+ Generic local-tx-datasource configuration,
+ automatically generated by DeploymentService.
+##
+## author: dimitris at jboss.org
+## version: $Revision: 29103 $
+ ===================================================================
+-->
+<datasources>
+ <local-tx-datasource>
+
+ <!-- Where to bind the datasource, under the "java:/" prefix -->
+ <jndi-name>${jndi-name}</jndi-name>
+#if($helper.isDefined(${use-java-context}))
+ <!-- Setting this to false will bind the DataSource into global jndi -->
+ <use-java-context>${use-java-context}</use-java-context>
+#end
+
+ <!-- The JDBC driver connection URL string -->
+ <connection-url>${connection-url}</connection-url>
+ <!-- The fully qualifed name of the JDBC driver class -->
+ <driver-class>${driver-class}</driver-class>
+#if(${transaction-isolation})
+ <!-- The java.sql.Connection transaction isolation level to use -->
+ <transaction-isolation>${transaction-isolation}</transaction-isolation>
+#end
+#if(${connection-properties})
+ <!-- Pass arbitrary connection properties to the Driver.connect(url, props) method -->
+#foreach($key in ${connection-properties.keySet()})
+ <connection-property name="$key">${connection-properties.get($key)}</connection-property>
+#end
+#end
+#if(${user-name})
+
+ <!-- Specifies the default username used when creating a new connection -->
+ <user-name>${user-name}</user-name>
+#end
+#if(${password})
+ <!-- Specifies the default password used when creating a new connection -->
+ <password>${password}</password>
+#end
+#if(${security-config})
+
+#if(${security-config.equalsIgnoreCase("APPLICATION-MANAGED-SECURITY")})
+ <!-- App supplied parameters (such as from getConnection(user, pw)) -->
+ <!-- are used to distinguish connections in the pool -->
+ <application-managed-security/>
+#elseif(${security-config.equalsIgnoreCase("SECURITY-DOMAIN")})
+ <!-- Indicates that the Subject (from the security domain) -->
+ <!-- is used to distinguish connections in the pool -->
+ <security-domain>${security-domain}</security-domain>
+#elseif(${security-config.equalsIgnoreCase("SECURITY-DOMAIN-AND-APPLICATION")})
+ <!-- Indicates that either app suplied parameters or the -->
+ <!-- Subject are used to distinguish connections in the pool -->
+ <security-domain-and-application>${security-domain}</security-domain-and-application>
+#end
+#end
+#if(${min-pool-size})
+
+ <!-- The minimum number of connections a pool should hold -->
+ <min-pool-size>${min-pool-size}</min-pool-size>
+#end
+#if(${max-pool-size})
+ <!-- The maximum number of connections for a pool -->
+ <max-pool-size>${max-pool-size}</max-pool-size>
+#end
+#if(${blocking-timeout-millis})
+ <!-- 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 -->
+ <blocking-timeout-millis>${blocking-timeout-millis}</blocking-timeout-millis>
+#end
+#if(${idle-timeout-minutes})
+ <!-- The maximum time in minutes a connection may be idle before being closed -->
+ <idle-timeout-minutes>${idle-timeout-minutes}</idle-timeout-minutes>
+#end
+#if(${no-tx-separate-pools})
+ <!-- use separete pools for connection retrieved in a transaction -->
+ <!-- and those retrieved outside a transaction -->
+ <no-tx-separate-pools/>
+#end
+#if(${new-connection-sql})
+
+ <!-- SQL statement to execute whenever a connection is added to the connection pool -->
+ <new-connection-sql>${new-connection-sql}</new-connection-sql>
+#end
+#if(${check-valid-connection-sql})
+ <!-- SQL statement to check validity of a pool connection -->
+ <check-valid-connection-sql>${check-valid-connection-sql}</check-valid-connection-sql>
+#end
+#if(${valid-connection-checker-class-name})
+ <!-- An org.jboss.resource.adapter.jdbc.ValidConnectionChecker -->
+ <valid-connection-checker-class-name>${valid-connection-checker-class-name}</valid-connection-checker-class-name>
+#end
+#if(${exception-sorter-class-name})
+ <!-- An org.jboss.resource.adapter.jdbc.ExceptionSorter -->
+ <exception-sorter-class-name>${exception-sorter-class-name}</exception-sorter-class-name>
+#end
+#if(${track-statements})
+ <!-- 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 -->
+ <track-statements>${track-statements.toLowerCase()}</track-statements>
+#end
+#if(${prepared-statement-cache-size})
+ <!-- The number of prepared statements per connection in an LRU cache -->
+ <prepared-statement-cache-size>${prepared-statement-cache-size}</prepared-statement-cache-size>
+#end
+#if(${dependencies})
+
+ <!-- ObjectNames of services the connection manager depends on -->
+#foreach($dependency in ${dependencies})
+ <depends>$dependency</depends>
+#end
+#end
+#if(${type-mapping})
+
+ <!-- Datasource/connection factory type-mapping -->
+ <metadata>
+ <type-mapping>${type-mapping}</type-mapping>
+ </metadata>
+#end
+
+ </local-tx-datasource>
+</datasources>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/no-tx-datasource/template-config.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/no-tx-datasource/template-config.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/no-tx-datasource/template-config.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,112 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Template configuration that produces a no-tx-datasource
+ deployment descriptor.
+
+ $Id: template-config.xml 29103 2005-02-24 12:22:56Z andd $
+-->
+<template-config template="vm/no-tx-datasource.vm" extension="-ds.xml">
+
+ <property-list>
+ <property name="jndi-name" type="java.lang.String">
+ <description>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.</description>
+ </property>
+
+ <property name="use-java-context" type="java.lang.Boolean" optional="true">
+ <description>Setting this to false will bind the DataSource into global jndi.</description>
+ <default-value>true</default-value>
+ </property>
+
+ <property name="connection-url" type="java.lang.String">
+ <description>The JDBC driver connection URL string.</description>
+ </property>
+
+ <property name="driver-class" type="java.lang.String">
+ <description>The fully qualifed name of the JDBC driver class.</description>
+ </property>
+
+ <property name="connection-properties" type="java.util.Hashtable" optional="true">
+ <description>Allows you to pass in arbitrary connection properties (string name/value pairs) to the Driver.connect(url, props) method.</description>
+ </property>
+
+ <property name="user-name" type="java.lang.String" optional="true">
+ <description>Specifies the default username used when creating a new connection.</description>
+ </property>
+
+ <property name="password" type="java.lang.String" optional="true">
+ <description>Specifies the default password used when creating a new connection.</description>
+ </property>
+
+ <!-- The two properties that follow are related -->
+ <property name="security-config" type="java.lang.String" optional="true">
+ <description>
+ The value of this property should be one of:
+ APPLICATION-MANAGED-SECURITY - Indicates that app supplied parameters (such as from getConnection(user, pw)) are used to distinguish connections in the pool.
+ SECURITY-DOMAIN - Indicates that the Subject (from the security domain) is used to distinguish connections in the pool.
+ SECURITY-DOMAIN-AND-APPLICATION - Indicates that either app suplied parameters or the Subject are used to distinguish connections in the pool.
+ </description>
+ </property>
+
+ <property name="security-domain" type="java.lang.String" optional="true">
+ <description>When the security-config is either SECURITY-DOMAIN or SECURITY-DOMAIN-AND-APPLICATION this property should define the name of the JAAS security manager handling authentication, which correlates to the login-config.xml descriptor, application-policy/name attribute.</description>
+ </property>
+
+ <property name="min-pool-size" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ <default-value>0</default-value>
+ </property>
+
+ <property name="max-pool-size" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ <default-value>20</default-value>
+ </property>
+
+ <property name="blocking-timeout-millis" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ <default-value>30000</default-value>
+ </property>
+
+ <property name="idle-timeout-minutes" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ </property>
+
+ <property name="new-connection-sql" type="java.lang.String" optional="true">
+ <description>Specify an SQL statement to execute whenever a connection is added to the connection pool.</description>
+ </property>
+
+ <property name="check-valid-connection-sql" type="java.lang.String" optional="true">
+ <description>Specify an SQL statement to check validity of a pool connection. This may be called when managed connection is taken from pool for use.</description>
+ </property>
+
+ <property name="valid-connection-checker-class-name" type="java.lang.String" optional="true">
+ <description>An org.jboss.resource.adapter.jdbc.ValidConnectionChecker that provides an SQLException isValidConnection(Connection e) method to validate if a connection is valid. An exception means the connection is destroyed. This overrides the check-valid-connection-sql when present.</description>
+ </property>
+
+ <property name="exception-sorter-class-name" type="java.lang.String" optional="true">
+ <description>An org.jboss.resource.adapter.jdbc.ExceptionSorter that provides a boolean isExceptionFatal(SQLException e) method to validate if an exception should be broadcast to all javax.resource.spi.ConnectionEventListener as a connectionErrorOccurred message.</description>
+ </property>
+
+ <property name="track-statements" type="java.lang.String" optional="true">
+ <description>Specifies 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)
+ </description>
+ <default-value>NOWARN</default-value>
+ </property>
+
+ <property name="prepared-statement-cache-size" type="java.lang.Integer" optional="true">
+ <description>The number of prepared statements per connection in an LRU cache.</description>
+ </property>
+
+ <property name="dependencies" type="[Ljavax.management.ObjectName;" optional="true">
+ <description>ObjectNames of services the connection manager depends on.</description>
+ </property>
+
+ <property name="type-mapping" type="java.lang.String" optional="true">
+ <description>Datasource/connection factory type-mapping.</description>
+ </property>
+
+ </property-list>
+
+</template-config>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/no-tx-datasource/vm/no-tx-datasource.vm
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/no-tx-datasource/vm/no-tx-datasource.vm (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/no-tx-datasource/vm/no-tx-datasource.vm 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,119 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ ===================================================================
+ Generic no-tx-datasource configuration,
+ automatically generated by DeploymentService.
+##
+## author: dimitris at jboss.org
+## version: $Revision: 29103 $
+ ===================================================================
+-->
+<datasources>
+ <no-tx-datasource>
+
+ <!-- Where to bind the datasource, under the "java:/" prefix -->
+ <jndi-name>${jndi-name}</jndi-name>
+#if($helper.isDefined(${use-java-context}))
+ <!-- Setting this to false will bind the DataSource into global jndi -->
+ <use-java-context>${use-java-context}</use-java-context>
+#end
+
+ <!-- The JDBC driver connection URL string -->
+ <connection-url>${connection-url}</connection-url>
+ <!-- The fully qualifed name of the JDBC driver class -->
+ <driver-class>${driver-class}</driver-class>
+#if(${connection-properties})
+ <!-- Pass arbitrary connection properties to the Driver.connect(url, props) method -->
+#foreach($key in ${connection-properties.keySet()})
+ <connection-property name="$key">${connection-properties.get($key)}</connection-property>
+#end
+#end
+#if(${user-name})
+
+ <!-- Specifies the default username used when creating a new connection -->
+ <user-name>${user-name}</user-name>
+#end
+#if(${password})
+ <!-- Specifies the default password used when creating a new connection -->
+ <password>${password}</password>
+#end
+#if(${security-config})
+
+#if(${security-config.equalsIgnoreCase("APPLICATION-MANAGED-SECURITY")})
+ <!-- App supplied parameters (such as from getConnection(user, pw)) -->
+ <!-- are used to distinguish connections in the pool -->
+ <application-managed-security/>
+#elseif(${security-config.equalsIgnoreCase("SECURITY-DOMAIN")})
+ <!-- Indicates that the Subject (from the security domain) -->
+ <!-- is used to distinguish connections in the pool -->
+ <security-domain>${security-domain}</security-domain>
+#elseif(${security-config.equalsIgnoreCase("SECURITY-DOMAIN-AND-APPLICATION")})
+ <!-- Indicates that either app suplied parameters or the -->
+ <!-- Subject are used to distinguish connections in the pool -->
+ <security-domain-and-application>${security-domain}</security-domain-and-application>
+#end
+#end
+#if(${min-pool-size})
+
+ <!-- The minimum number of connections a pool should hold -->
+ <min-pool-size>${min-pool-size}</min-pool-size>
+#end
+#if(${max-pool-size})
+ <!-- The maximum number of connections for a pool -->
+ <max-pool-size>${max-pool-size}</max-pool-size>
+#end
+#if(${blocking-timeout-millis})
+ <!-- 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 -->
+ <blocking-timeout-millis>${blocking-timeout-millis}</blocking-timeout-millis>
+#end
+#if(${idle-timeout-minutes})
+ <!-- The maximum time in minutes a connection may be idle before being closed -->
+ <idle-timeout-minutes>${idle-timeout-minutes}</idle-timeout-minutes>
+#end
+#if(${new-connection-sql})
+
+ <!-- SQL statement to execute whenever a connection is added to the connection pool -->
+ <new-connection-sql>${new-connection-sql}</new-connection-sql>
+#end
+#if(${check-valid-connection-sql})
+ <!-- SQL statement to check validity of a pool connection -->
+ <check-valid-connection-sql>${check-valid-connection-sql}</check-valid-connection-sql>
+#end
+#if(${valid-connection-checker-class-name})
+ <!-- An org.jboss.resource.adapter.jdbc.ValidConnectionChecker -->
+ <valid-connection-checker-class-name>${valid-connection-checker-class-name}</valid-connection-checker-class-name>
+#end
+#if(${exception-sorter-class-name})
+ <!-- An org.jboss.resource.adapter.jdbc.ExceptionSorter -->
+ <exception-sorter-class-name>${exception-sorter-class-name}</exception-sorter-class-name>
+#end
+#if(${track-statements})
+ <!-- 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 -->
+ <track-statements>${track-statements.toLowerCase()}</track-statements>
+#end
+#if(${prepared-statement-cache-size})
+ <!-- The number of prepared statements per connection in an LRU cache -->
+ <prepared-statement-cache-size>${prepared-statement-cache-size}</prepared-statement-cache-size>
+#end
+#if(${dependencies})
+
+ <!-- ObjectNames of services the connection manager depends on -->
+#foreach($dependency in ${dependencies})
+ <depends>$dependency</depends>
+#end
+#end
+#if(${type-mapping})
+
+ <!-- Datasource/connection factory type-mapping -->
+ <metadata>
+ <type-mapping>${type-mapping}</type-mapping>
+ </metadata>
+#end
+
+ </no-tx-datasource>
+</datasources>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/xa-datasource/template-config.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/xa-datasource/template-config.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/xa-datasource/template-config.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,132 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ Template configuration that produces an xa-datasource
+ deployment descriptor.
+
+ $Id: template-config.xml 29103 2005-02-24 12:22:56Z andd $
+-->
+<template-config template="vm/xa-datasource.vm" extension="-ds.xml">
+
+ <property-list>
+ <property name="jndi-name" type="java.lang.String">
+ <description>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.</description>
+ </property>
+
+ <property name="use-java-context" type="java.lang.Boolean" optional="true">
+ <description>Setting this to false will bind the DataSource into global jndi.</description>
+ <default-value>true</default-value>
+ </property>
+
+ <property name="track-connection-by-tx" type="java.lang.Boolean" optional="true">
+ <description>All work on one tx will go through one connection.</description>
+ <default-value>false</default-value>
+ </property>
+
+ <property name="xa-datasource-class" type="java.lang.String">
+ <description>The fully qualifed name of the javax.sql.XADataSource implementation class.</description>
+ </property>
+
+ <property name="xa-datasource-properties" type="java.util.Hashtable" optional="true">
+ <description>Allows you to pass in arbitrary connection properties (string name/value pairs) to the XADataSource.</description>
+ </property>
+
+ <property name="is-same-RM-override-value" type="java.lang.Boolean" optional="true">
+ <description>Allows to unconditionally set whether the javax.transaction.xa.XAResource.isSameRM(XAResource) returns true or false.</description>
+ </property>
+
+ <property name="transaction-isolation" type="java.lang.String" optional="true">
+ <description>The java.sql.Connection transaction isolation level to use. The possible values are
+ TRANSACTION_READ_UNCOMMITTED
+ TRANSACTION_READ_COMMITTED
+ TRANSACTION_REPEATABLE_READ
+ TRANSACTION_SERIALIZABLE
+ TRANSACTION_NONE
+ </description>
+ </property>
+
+ <property name="user-name" type="java.lang.String" optional="true">
+ <description>Specifies the default username used when creating a new connection.</description>
+ </property>
+
+ <property name="password" type="java.lang.String" optional="true">
+ <description>Specifies the default password used when creating a new connection.</description>
+ </property>
+
+ <!-- The two properties that follow are related -->
+ <property name="security-config" type="java.lang.String" optional="true">
+ <description>
+ The value of this property should be one of:
+ APPLICATION-MANAGED-SECURITY - Indicates that app supplied parameters (such as from getConnection(user, pw)) are used to distinguish connections in the pool.
+ SECURITY-DOMAIN - Indicates that the Subject (from the security domain) is used to distinguish connections in the pool.
+ SECURITY-DOMAIN-AND-APPLICATION - Indicates that either app suplied parameters or the Subject are used to distinguish connections in the pool.
+ </description>
+ </property>
+
+ <property name="security-domain" type="java.lang.String" optional="true">
+ <description>When the security-config is either SECURITY-DOMAIN or SECURITY-DOMAIN-AND-APPLICATION this property should define the name of the JAAS security manager handling authentication, which correlates to the login-config.xml descriptor, application-policy/name attribute.</description>
+ </property>
+
+ <property name="min-pool-size" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ <default-value>0</default-value>
+ </property>
+
+ <property name="max-pool-size" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ <default-value>20</default-value>
+ </property>
+
+ <property name="blocking-timeout-millis" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ <default-value>30000</default-value>
+ </property>
+
+ <property name="idle-timeout-minutes" type="java.lang.Integer" optional="true">
+ <description>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.</description>
+ </property>
+
+ <property name="no-tx-separate-pools" type="java.lang.Boolean" optional="true">
+ <description>Indicates whether to use separete pools for connection retrieved in a transaction and those retrieved outside a transaction.</description>
+ <default-value>false</default-value>
+ </property>
+
+ <property name="new-connection-sql" type="java.lang.String" optional="true">
+ <description>Specify an SQL statement to execute whenever a connection is added to the connection pool.</description>
+ </property>
+
+ <property name="check-valid-connection-sql" type="java.lang.String" optional="true">
+ <description>Specify an SQL statement to check validity of a pool connection. This may be called when managed connection is taken from pool for use.</description>
+ </property>
+
+ <property name="valid-connection-checker-class-name" type="java.lang.String" optional="true">
+ <description>An org.jboss.resource.adapter.jdbc.ValidConnectionChecker that provides an SQLException isValidConnection(Connection e) method to validate if a connection is valid. An exception means the connection is destroyed. This overrides the check-valid-connection-sql when present.</description>
+ </property>
+
+ <property name="exception-sorter-class-name" type="java.lang.String" optional="true">
+ <description>An org.jboss.resource.adapter.jdbc.ExceptionSorter that provides a boolean isExceptionFatal(SQLException e) method to validate if an exception should be broadcast to all javax.resource.spi.ConnectionEventListener as a connectionErrorOccurred message.</description>
+ </property>
+
+ <property name="track-statements" type="java.lang.String" optional="true">
+ <description>Specifies 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)
+ </description>
+ <default-value>NOWARN</default-value>
+ </property>
+
+ <property name="prepared-statement-cache-size" type="java.lang.Integer" optional="true">
+ <description>The number of prepared statements per connection in an LRU cache.</description>
+ </property>
+
+ <property name="dependencies" type="[Ljavax.management.ObjectName;" optional="true">
+ <description>ObjectNames of services the connection manager depends on.</description>
+ </property>
+
+ <property name="type-mapping" type="java.lang.String" optional="true">
+ <description>Datasource/connection factory type-mapping.</description>
+ </property>
+
+ </property-list>
+
+</template-config>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/xa-datasource/vm/xa-datasource.vm
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/xa-datasource/vm/xa-datasource.vm (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/deployment-service/templates/xa-datasource/vm/xa-datasource.vm 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,132 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ ===================================================================
+ Generic xa-datasource configuration,
+ automatically generated by DeploymentService.
+##
+## author: dimitris at jboss.org
+## version: $Revision: 29103 $
+ ===================================================================
+-->
+<datasources>
+ <xa-datasource>
+
+ <!-- Where to bind the datasource, under the "java:/" prefix -->
+ <jndi-name>${jndi-name}</jndi-name>
+#if($helper.isDefined(${use-java-context}))
+ <!-- Setting this to false will bind the DataSource into global jndi -->
+ <use-java-context>${use-java-context}</use-java-context>
+#end
+#if(${track-connection-by-tx})
+ <!-- All work on one tx will go through one connection -->
+ <track-connection-by-tx/>
+#end
+ <!-- The fully qualifed name of the javax.sql.XADataSource implementation class -->
+ <xa-datasource-class>${xa-datasource-class}</xa-datasource-class>
+#if(${xa-datasource-properties})
+ <!-- Pass arbitrary connection properties (string name/value pairs) to the XADataSource -->
+#foreach($key in ${xa-datasource-properties.keySet()})
+ <xa-datasource-property name="$key">${xa-datasource-properties.get($key)}</xa-datasource-property>
+#end
+#end
+#if($helper.isDefined(${is-same-RM-override-value}))
+ <!-- Force javax.transaction.xa.XAResource.isSameRM(XAResource) to return true or false -->
+ <isSameRM-override-value>${is-same-RM-override-value}</isSameRM-override-value>
+#end
+#if(${transaction-isolation})
+ <!-- The java.sql.Connection transaction isolation level to use -->
+ <transaction-isolation>${transaction-isolation}</transaction-isolation>
+#end
+#if(${user-name})
+ <!-- Specifies the default username used when creating a new connection -->
+ <user-name>${user-name}</user-name>
+#end
+#if(${password})
+ <!-- Specifies the default password used when creating a new connection -->
+ <password>${password}</password>
+#end
+#if(${security-config})
+
+#if(${security-config.equalsIgnoreCase("APPLICATION-MANAGED-SECURITY")})
+ <!-- App supplied parameters (such as from getConnection(user, pw)) -->
+ <!-- are used to distinguish connections in the pool -->
+ <application-managed-security/>
+#elseif(${security-config.equalsIgnoreCase("SECURITY-DOMAIN")})
+ <!-- Indicates that the Subject (from the security domain) -->
+ <!-- is used to distinguish connections in the pool -->
+ <security-domain>${security-domain}</security-domain>
+#elseif(${security-config.equalsIgnoreCase("SECURITY-DOMAIN-AND-APPLICATION")})
+ <!-- Indicates that either app suplied parameters or the -->
+ <!-- Subject are used to distinguish connections in the pool -->
+ <security-domain-and-application>${security-domain}</security-domain-and-application>
+#end
+#end
+#if(${min-pool-size})
+
+ <!-- The minimum number of connections a pool should hold -->
+ <min-pool-size>${min-pool-size}</min-pool-size>
+#end
+#if(${max-pool-size})
+ <!-- The maximum number of connections for a pool -->
+ <max-pool-size>${max-pool-size}</max-pool-size>
+#end
+#if(${blocking-timeout-millis})
+ <!-- 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 -->
+ <blocking-timeout-millis>${blocking-timeout-millis}</blocking-timeout-millis>
+#end
+#if(${idle-timeout-minutes})
+ <!-- The maximum time in minutes a connection may be idle before being closed -->
+ <idle-timeout-minutes>${idle-timeout-minutes}</idle-timeout-minutes>
+#end
+#if(${no-tx-separate-pools})
+ <!-- use separete pools for connection retrieved in a transaction -->
+ <!-- and those retrieved outside a transaction -->
+ <no-tx-separate-pools/>
+#end
+#if(${new-connection-sql})
+
+ <!-- SQL statement to execute whenever a connection is added to the connection pool -->
+ <new-connection-sql>${new-connection-sql}</new-connection-sql>
+#end
+#if(${check-valid-connection-sql})
+ <!-- SQL statement to check validity of a pool connection -->
+ <check-valid-connection-sql>${check-valid-connection-sql}</check-valid-connection-sql>
+#end
+#if(${valid-connection-checker-class-name})
+ <!-- An org.jboss.resource.adapter.jdbc.ValidConnectionChecker -->
+ <valid-connection-checker-class-name>${valid-connection-checker-class-name}</valid-connection-checker-class-name>
+#end
+#if(${exception-sorter-class-name})
+ <!-- An org.jboss.resource.adapter.jdbc.ExceptionSorter -->
+ <exception-sorter-class-name>${exception-sorter-class-name}</exception-sorter-class-name>
+#end
+#if(${track-statements})
+ <!-- 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 -->
+ <track-statements>${track-statements.toLowerCase()}</track-statements>
+#end
+#if(${prepared-statement-cache-size})
+ <!-- The number of prepared statements per connection in an LRU cache -->
+ <prepared-statement-cache-size>${prepared-statement-cache-size}</prepared-statement-cache-size>
+#end
+#if(${dependencies})
+
+ <!-- ObjectNames of services the connection manager depends on -->
+#foreach($dependency in ${dependencies})
+ <depends>$dependency</depends>
+#end
+#end
+#if(${type-mapping})
+
+ <!-- Datasource/connection factory type-mapping -->
+ <metadata>
+ <type-mapping>${type-mapping}</type-mapping>
+ </metadata>
+#end
+
+ </xa-datasource>
+</datasources>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/derby-plugin.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/derby-plugin.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/entity-resolver-manager/xmlresolver-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/entity-resolver-manager/xmlresolver-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/entity-resolver-manager/xmlresolver-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,12 @@
+<!-- The JBossEntityResolver mbean service which allows customization of the
+xml parser entity resolver publicID/systemID to dtd/schema file mapping.
+See, http://wiki.jboss.org/wiki/Wiki.jsp?page=XMLEntitySchemaResolution
+-->
+<server>
+ <mbean code="org.jboss.services.xml.JBossEntityResolverMgr"
+ name="jboss.xml:service=JBossEntityResolverMgr">
+ <attribute name="WarnOnNonFileURLs">true</attribute>
+ <attribute name="EntityMap">
+ </attribute>
+ </mbean>
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/jboss-bindings.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/jboss-bindings.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/examples/varia/jboss-bindings.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,187 @@
+<!DOCTYPE service-bindings [
+ <!ELEMENT service-bindings (server+)>
+
+ <!ELEMENT server (service-config+)>
+
+ <!ATTLIST server name CDATA #REQUIRED>
+
+ <!ELEMENT service-config (delegate-config? , binding+)>
+
+ <!ATTLIST service-config name CDATA #REQUIRED
+ delegateClass CDATA #IMPLIED >
+
+ <!ELEMENT binding EMPTY>
+
+ <!ATTLIST binding name CDATA #IMPLIED
+ host CDATA #IMPLIED
+ port CDATA #IMPLIED >
+ <!ELEMENT delegate-config ANY>
+ <!ATTLIST delegate-config hostName CDATA #IMPLIED
+ portName CDATA #IMPLIED >
+]>
+
+<service-bindings>
+
+ <server name="jboss_2">
+
+ <!-- ********************************************************** -->
+
+ <service-config name="jboss:service=WebService"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="28083" />
+ </service-config>
+
+ <!-- ********************************************************** -->
+
+ <service-config name="jboss:service=Naming"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port"/>
+ <binding port="21099" />
+ </service-config>
+
+ <!-- ********************************************************** -->
+
+ <service-config name="jboss:service=invoker,type=trunk"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort"/>
+ <binding port="24445" />
+ </service-config>
+
+ <!-- ********************************************************** -->
+
+ <!-- Hypersonic related services -->
+ <service-config name="jboss.jca:service=LocalTxDS,name=DefaultDS"
+ delegateClass="org.jboss.services.binding.XSLTConfigDelegate"
+ >
+ <delegate-config>
+ <attribute name="">jdbc:hsqldb:hsql://${host}:${port}</attribute>
+ <xslt-config configName="ManagedConnectionFactoryProperties"><![CDATA[
+<xsl:stylesheet
+ xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="host"/>
+ <xsl:param name="port"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match="config-property[@name='ConnectionURL']">
+ <config-property type="java.lang.String" name="ConnectionURL">jdbc:hsqldb:hsql://<xsl:value-of select='$host'/>:<xsl:value-of select='$port'/></config-property>
+ </xsl:template>
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+</xsl:stylesheet>
+]]>
+ </xslt-config>
+ </delegate-config>
+ <binding host="localhost" port="21476" />
+ </service-config>
+
+ <service-config name="jboss:service=Hypersonic"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port" />
+ <binding port="21476" />
+ </service-config>
+
+ <!-- ********************************************************** -->
+
+ <!-- JMS related services -->
+ <service-config name="jboss.mq:service=InvocationLayer,type=OIL"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort" />
+ <binding port="28090" />
+ </service-config>
+
+ <service-config name="jboss.mq:service=InvocationLayer,type=OIL2"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort" />
+ <binding port="28092" />
+ </service-config>
+
+ <service-config name="jboss.mq:service=InvocationLayer,type=UIL"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort" />
+ <binding port="28091" />
+ </service-config>
+
+ <service-config name="jboss.mq:service=InvocationLayer,type=UIL2"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="ServerBindPort" />
+ <binding port="28093" />
+ </service-config>
+
+ <!-- ********************************************************** -->
+
+ <!-- Jetty -->
+ <service-config name="jboss.web:service=WebServer"
+ delegateClass="org.jboss.services.binding.XSLTConfigDelegate"
+ >
+ <!-- This transforms the ConfigurationElement attribute document
+ -->
+ <delegate-config>
+ <xslt-config configName="ConfigurationElement"><![CDATA[
+<xsl:stylesheet
+ xmlns:xsl='http://www.w3.org/1999/XSL/Transform' version='1.0'>
+
+ <xsl:output method="xml" />
+ <xsl:param name="host"/>
+ <xsl:param name="port"/>
+
+ <xsl:template match="/">
+ <xsl:apply-templates/>
+ </xsl:template>
+
+ <xsl:template match="SystemProperty[@name='jetty.port']">
+ <SystemProperty default="{$port}" name="jetty.port" />
+ </xsl:template>
+ <xsl:template match="New[@class='org.mortbay.http.ajp.AJP13Listener']/Set[@name='Port']">
+ <Set name="Port"><xsl:value-of select="$port - 71"/></Set>
+ </xsl:template>
+ <xsl:template match="*|@*">
+ <xsl:copy>
+ <xsl:apply-templates select="@*|node()"/>
+ </xsl:copy>
+ </xsl:template>
+</xsl:stylesheet>
+]]>
+ </xslt-config>
+ </delegate-config>
+ <binding port="28080" />
+ </service-config>
+
+ <!-- ********************************************************** -->
+
+ <service-config name="jboss:service=HAJNDI"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port" />
+ <binding port="21100" />
+ </service-config>
+
+ <!-- ********************************************************** -->
+
+ <!-- Corba cannot be modified: it uses conf/jacorb.properties for its port number -->
+ <service-config name="jboss:service=CorbaORB"
+ delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
+ >
+ <delegate-config portName="Port" />
+ <binding port="23528" />
+ </service-config>
+
+ </server>
+
+</service-bindings>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/antlr.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/antlr.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/antlr.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,19 @@
+http://www.antlr.org/license.html
+
+Software License
+
+We reserve no legal rights to the ANTLR--it is fully in the public domain. An
+individual or company may do whatever they wish with source code distributed
+with ANTLR or the code generated by ANTLR, including the incorporation of ANTLR,
+or its output, into commerical software.
+
+We encourage users to develop software with ANTLR. However, we do ask that
+credit is given to us for developing ANTLR. By "credit", we mean that if you
+use ANTLR or incorporate any source code into one of your programs (commercial
+product, research project, or otherwise) that you acknowledge this fact
+somewhere in the documentation, research report, etc... If you like ANTLR and
+have developed a nice tool with the output, please mention that you developed
+it using ANTLR. In addition, we ask that the headers remain intact in our
+source code. As long as these guidelines are kept, we expect to continue
+enhancing this system and expect to make other tools available as they are
+completed.
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/apache-1.1.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/apache-1.1.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/apache-1.1.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,58 @@
+/* ====================================================================
+ * The Apache Software License, Version 1.1
+ *
+ * Copyright (c) 2000 The Apache Software Foundation. All rights
+ * reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright
+ * notice, this list of conditions and the following disclaimer.
+ *
+ * 2. Redistributions in binary form must reproduce the above copyright
+ * notice, this list of conditions and the following disclaimer in
+ * the documentation and/or other materials provided with the
+ * distribution.
+ *
+ * 3. The end-user documentation included with the redistribution,
+ * if any, must include the following acknowledgment:
+ * "This product includes software developed by the
+ * Apache Software Foundation (http://www.apache.org/)."
+ * Alternately, this acknowledgment may appear in the software itself,
+ * if and wherever such third-party acknowledgments normally appear.
+ *
+ * 4. The names "Apache" and "Apache Software Foundation" must
+ * not be used to endorse or promote products derived from this
+ * software without prior written permission. For written
+ * permission, please contact apache at apache.org.
+ *
+ * 5. Products derived from this software may not be called "Apache",
+ * nor may "Apache" appear in their name, without prior written
+ * permission of the Apache Software Foundation.
+ *
+ * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+ * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+ * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
+ * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+ * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
+ * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ * ====================================================================
+ *
+ * This software consists of voluntary contributions made by many
+ * individuals on behalf of the Apache Software Foundation. For more
+ * information on the Apache Software Foundation, please see
+ * <http://www.apache.org/>.
+ *
+ * Portions of this software are based upon public domain software
+ * originally written at the National Center for Supercomputing Applications,
+ * University of Illinois, Urbana-Champaign.
+ */
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/apache-2.0.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/apache-2.0.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/apache-2.0.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/bsd.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/bsd.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/bsd.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,27 @@
+The BSD License
+
+ The following is a BSD license template. To generate your own license, change the values of OWNER, ORGANIZATION and YEAR from their original values as given here, and substitute your own.
+
+ Note: The advertising clause in the license appearing on BSD Unix files was officially rescinded by the Director of the Office of Technology Licensing of the University of California on July 22 1999. He states that clause 3 is "hereby deleted in its entirety."
+
+ Note the new BSD license is thus equivalent to the MIT License, except for the no-endorsement final clause.
+
+<OWNER> = Regents of the University of California
+<ORGANIZATION> = University of California, Berkeley
+<YEAR> = 1998
+
+In the original BSD license, both occurrences of the phrase "COPYRIGHT HOLDERS AND CONTRIBUTORS" in the disclaimer read "REGENTS AND CONTRIBUTORS".
+
+Here is the license template:
+
+Copyright (c) <YEAR>, <OWNER>
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+ * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+ * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+ * Neither the name of the <ORGANIZATION> nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/cddl.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/cddl.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/cddl.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,384 @@
+COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0
+
+
+ 1. Definitions.
+
+ 1.1. "Contributor" means each individual or entity that
+ creates or contributes to the creation of Modifications.
+
+ 1.2. "Contributor Version" means the combination of the
+ Original Software, prior Modifications used by a
+ Contributor (if any), and the Modifications made by that
+ particular Contributor.
+
+ 1.3. "Covered Software" means (a) the Original Software, or
+ (b) Modifications, or (c) the combination of files
+ containing Original Software with files containing
+ Modifications, in each case including portions thereof.
+
+ 1.4. "Executable" means the Covered Software in any form
+ other than Source Code.
+
+ 1.5. "Initial Developer" means the individual or entity
+ that first makes Original Software available under this
+ License.
+
+ 1.6. "Larger Work" means a work which combines Covered
+ Software or portions thereof with code not governed by the
+ terms of this License.
+
+ 1.7. "License" means this document.
+
+ 1.8. "Licensable" means having the right to grant, to the
+ maximum extent possible, whether at the time of the initial
+ grant or subsequently acquired, any and all of the rights
+ conveyed herein.
+
+ 1.9. "Modifications" means the Source Code and Executable
+ form of any of the following:
+
+ A. Any file that results from an addition to,
+ deletion from or modification of the contents of a
+ file containing Original Software or previous
+ Modifications;
+
+ B. Any new file that contains any part of the
+ Original Software or previous Modification; or
+
+ C. Any new file that is contributed or otherwise made
+ available under the terms of this License.
+
+ 1.10. "Original Software" means the Source Code and
+ Executable form of computer software code that is
+ originally released under this License.
+
+ 1.11. "Patent Claims" means any patent claim(s), now owned
+ or hereafter acquired, including without limitation,
+ method, process, and apparatus claims, in any patent
+ Licensable by grantor.
+
+ 1.12. "Source Code" means (a) the common form of computer
+ software code in which modifications are made and (b)
+ associated documentation included in or with such code.
+
+ 1.13. "You" (or "Your") means an individual or a legal
+ entity exercising rights under, and complying with all of
+ the terms of, this License. For legal entities, "You"
+ includes any entity which controls, is controlled by, or is
+ under common control with You. For purposes of this
+ definition, "control" means (a) the power, direct or
+ indirect, to cause the direction or management of such
+ entity, whether by contract or otherwise, or (b) ownership
+ of more than fifty percent (50%) of the outstanding shares
+ or beneficial ownership of such entity.
+
+ 2. License Grants.
+
+ 2.1. The Initial Developer Grant.
+
+ Conditioned upon Your compliance with Section 3.1 below and
+ subject to third party intellectual property claims, the
+ Initial Developer hereby grants You a world-wide,
+ royalty-free, non-exclusive license:
+
+ (a) under intellectual property rights (other than
+ patent or trademark) Licensable by Initial Developer,
+ to use, reproduce, modify, display, perform,
+ sublicense and distribute the Original Software (or
+ portions thereof), with or without Modifications,
+ and/or as part of a Larger Work; and
+
+ (b) under Patent Claims infringed by the making,
+ using or selling of Original Software, to make, have
+ made, use, practice, sell, and offer for sale, and/or
+ otherwise dispose of the Original Software (or
+ portions thereof).
+
+ (c) The licenses granted in Sections 2.1(a) and (b)
+ are effective on the date Initial Developer first
+ distributes or otherwise makes the Original Software
+ available to a third party under the terms of this
+ License.
+
+ (d) Notwithstanding Section 2.1(b) above, no patent
+ license is granted: (1) for code that You delete from
+ the Original Software, or (2) for infringements
+ caused by: (i) the modification of the Original
+ Software, or (ii) the combination of the Original
+ Software with other software or devices.
+
+ 2.2. Contributor Grant.
+
+ Conditioned upon Your compliance with Section 3.1 below and
+ subject to third party intellectual property claims, each
+ Contributor hereby grants You a world-wide, royalty-free,
+ non-exclusive license:
+
+ (a) under intellectual property rights (other than
+ patent or trademark) Licensable by Contributor to
+ use, reproduce, modify, display, perform, sublicense
+ and distribute the Modifications created by such
+ Contributor (or portions thereof), either on an
+ unmodified basis, with other Modifications, as
+ Covered Software and/or as part of a Larger Work; and
+
+
+ (b) under Patent Claims infringed by the making,
+ using, or selling of Modifications made by that
+ Contributor either alone and/or in combination with
+ its Contributor Version (or portions of such
+ combination), to make, use, sell, offer for sale,
+ have made, and/or otherwise dispose of: (1)
+ Modifications made by that Contributor (or portions
+ thereof); and (2) the combination of Modifications
+ made by that Contributor with its Contributor Version
+ (or portions of such combination).
+
+ (c) The licenses granted in Sections 2.2(a) and
+ 2.2(b) are effective on the date Contributor first
+ distributes or otherwise makes the Modifications
+ available to a third party.
+
+ (d) Notwithstanding Section 2.2(b) above, no patent
+ license is granted: (1) for any code that Contributor
+ has deleted from the Contributor Version; (2) for
+ infringements caused by: (i) third party
+ modifications of Contributor Version, or (ii) the
+ combination of Modifications made by that Contributor
+ with other software (except as part of the
+ Contributor Version) or other devices; or (3) under
+ Patent Claims infringed by Covered Software in the
+ absence of Modifications made by that Contributor.
+
+ 3. Distribution Obligations.
+
+ 3.1. Availability of Source Code.
+
+ Any Covered Software that You distribute or otherwise make
+ available in Executable form must also be made available in
+ Source Code form and that Source Code form must be
+ distributed only under the terms of this License. You must
+ include a copy of this License with every copy of the
+ Source Code form of the Covered Software You distribute or
+ otherwise make available. You must inform recipients of any
+ such Covered Software in Executable form as to how they can
+ obtain such Covered Software in Source Code form in a
+ reasonable manner on or through a medium customarily used
+ for software exchange.
+
+ 3.2. Modifications.
+
+ The Modifications that You create or to which You
+ contribute are governed by the terms of this License. You
+ represent that You believe Your Modifications are Your
+ original creation(s) and/or You have sufficient rights to
+ grant the rights conveyed by this License.
+
+ 3.3. Required Notices.
+
+ You must include a notice in each of Your Modifications
+ that identifies You as the Contributor of the Modification.
+ You may not remove or alter any copyright, patent or
+ trademark notices contained within the Covered Software, or
+ any notices of licensing or any descriptive text giving
+ attribution to any Contributor or the Initial Developer.
+
+ 3.4. Application of Additional Terms.
+
+ You may not offer or impose any terms on any Covered
+ Software in Source Code form that alters or restricts the
+ applicable version of this License or the recipients"
+ rights hereunder. You may choose to offer, and to charge a
+ fee for, warranty, support, indemnity or liability
+ obligations to one or more recipients of Covered Software.
+ However, you may do so only on Your own behalf, and not on
+ behalf of the Initial Developer or any Contributor. You
+ must make it absolutely clear that any such warranty,
+ support, indemnity or liability obligation is offered by
+ You alone, and You hereby agree to indemnify the Initial
+ Developer and every Contributor for any liability incurred
+ by the Initial Developer or such Contributor as a result of
+ warranty, support, indemnity or liability terms You offer.
+
+
+ 3.5. Distribution of Executable Versions.
+
+ You may distribute the Executable form of the Covered
+ Software under the terms of this License or under the terms
+ of a license of Your choice, which may contain terms
+ different from this License, provided that You are in
+ compliance with the terms of this License and that the
+ license for the Executable form does not attempt to limit
+ or alter the recipient"s rights in the Source Code form
+ from the rights set forth in this License. If You
+ distribute the Covered Software in Executable form under a
+ different license, You must make it absolutely clear that
+ any terms which differ from this License are offered by You
+ alone, not by the Initial Developer or Contributor. You
+ hereby agree to indemnify the Initial Developer and every
+ Contributor for any liability incurred by the Initial
+ Developer or such Contributor as a result of any such terms
+ You offer.
+
+ 3.6. Larger Works.
+
+ You may create a Larger Work by combining Covered Software
+ with other code not governed by the terms of this License
+ and distribute the Larger Work as a single product. In such
+ a case, You must make sure the requirements of this License
+ are fulfilled for the Covered Software.
+
+ 4. Versions of the License.
+
+ 4.1. New Versions.
+
+ Sun Microsystems, Inc. is the initial license steward and
+ may publish revised and/or new versions of this License
+ from time to time. Each version will be given a
+ distinguishing version number. Except as provided in
+ Section 4.3, no one other than the license steward has the
+ right to modify this License.
+
+ 4.2. Effect of New Versions.
+
+ You may always continue to use, distribute or otherwise
+ make the Covered Software available under the terms of the
+ version of the License under which You originally received
+ the Covered Software. If the Initial Developer includes a
+ notice in the Original Software prohibiting it from being
+ distributed or otherwise made available under any
+ subsequent version of the License, You must distribute and
+ make the Covered Software available under the terms of the
+ version of the License under which You originally received
+ the Covered Software. Otherwise, You may also choose to
+ use, distribute or otherwise make the Covered Software
+ available under the terms of any subsequent version of the
+ License published by the license steward.
+
+ 4.3. Modified Versions.
+
+ When You are an Initial Developer and You want to create a
+ new license for Your Original Software, You may create and
+ use a modified version of this License if You: (a) rename
+ the license and remove any references to the name of the
+ license steward (except to note that the license differs
+ from this License); and (b) otherwise make it clear that
+ the license contains terms which differ from this License.
+
+
+ 5. DISCLAIMER OF WARRANTY.
+
+ COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS"
+ BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
+ INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED
+ SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR
+ PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND
+ PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY
+ COVERED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE
+ INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF
+ ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF
+ WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF
+ ANY COVERED SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS
+ DISCLAIMER.
+
+ 6. TERMINATION.
+
+ 6.1. This License and the rights granted hereunder will
+ terminate automatically if You fail to comply with terms
+ herein and fail to cure such breach within 30 days of
+ becoming aware of the breach. Provisions which, by their
+ nature, must remain in effect beyond the termination of
+ this License shall survive.
+
+ 6.2. If You assert a patent infringement claim (excluding
+ declaratory judgment actions) against Initial Developer or
+ a Contributor (the Initial Developer or Contributor against
+ whom You assert such claim is referred to as "Participant")
+ alleging that the Participant Software (meaning the
+ Contributor Version where the Participant is a Contributor
+ or the Original Software where the Participant is the
+ Initial Developer) directly or indirectly infringes any
+ patent, then any and all rights granted directly or
+ indirectly to You by such Participant, the Initial
+ Developer (if the Initial Developer is not the Participant)
+ and all Contributors under Sections 2.1 and/or 2.2 of this
+ License shall, upon 60 days notice from Participant
+ terminate prospectively and automatically at the expiration
+ of such 60 day notice period, unless if within such 60 day
+ period You withdraw Your claim with respect to the
+ Participant Software against such Participant either
+ unilaterally or pursuant to a written agreement with
+ Participant.
+
+ 6.3. In the event of termination under Sections 6.1 or 6.2
+ above, all end user licenses that have been validly granted
+ by You or any distributor hereunder prior to termination
+ (excluding licenses granted to You by any distributor)
+ shall survive termination.
+
+ 7. LIMITATION OF LIABILITY.
+
+ UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT
+ (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE
+ INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF
+ COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE
+ LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR
+ CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT
+ LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL, WORK
+ STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER
+ COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN
+ INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF
+ LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL
+ INJURY RESULTING FROM SUCH PARTY"S NEGLIGENCE TO THE EXTENT
+ APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO
+ NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR
+ CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT
+ APPLY TO YOU.
+
+ 8. U.S. GOVERNMENT END USERS.
+
+ The Covered Software is a "commercial item," as that term is
+ defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial
+ computer software" (as that term is defined at 48 C.F.R. "
+ 252.227-7014(a)(1)) and "commercial computer software
+ documentation" as such terms are used in 48 C.F.R. 12.212 (Sept.
+ 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1
+ through 227.7202-4 (June 1995), all U.S. Government End Users
+ acquire Covered Software with only those rights set forth herein.
+ This U.S. Government Rights clause is in lieu of, and supersedes,
+ any other FAR, DFAR, or other clause or provision that addresses
+ Government rights in computer software under this License.
+
+ 9. MISCELLANEOUS.
+
+ This License represents the complete agreement concerning subject
+ matter hereof. If any provision of this License is held to be
+ unenforceable, such provision shall be reformed only to the
+ extent necessary to make it enforceable. This License shall be
+ governed by the law of the jurisdiction specified in a notice
+ contained within the Original Software (except to the extent
+ applicable law, if any, provides otherwise), excluding such
+ jurisdiction"s conflict-of-law provisions. Any litigation
+ relating to this License shall be subject to the jurisdiction of
+ the courts located in the jurisdiction and venue specified in a
+ notice contained within the Original Software, with the losing
+ party responsible for costs, including, without limitation, court
+ costs and reasonable attorneys" fees and expenses. The
+ application of the United Nations Convention on Contracts for the
+ International Sale of Goods is expressly excluded. Any law or
+ regulation which provides that the language of a contract shall
+ be construed against the drafter shall not apply to this License.
+ You agree that You alone are responsible for compliance with the
+ United States export administration regulations (and the export
+ control laws and regulation of any other countries) when You use,
+ distribute or otherwise make available any Covered Software.
+
+ 10. RESPONSIBILITY FOR CLAIMS.
+
+ As between Initial Developer and the Contributors, each party is
+ responsible for claims and damages arising, directly or
+ indirectly, out of its utilization of rights under this License
+ and You agree to work with Initial Developer and Contributors to
+ distribute such responsibility on an equitable basis. Nothing
+ herein is intended or shall be deemed to constitute any admission
+ of liability.
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/cpl-1.0.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/cpl-1.0.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/cpl-1.0.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,213 @@
+Common Public License Version 1.0
+
+THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC
+LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
+CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
+
+1. DEFINITIONS
+
+"Contribution" means:
+
+ a) in the case of the initial Contributor, the initial code and documentation
+ distributed under this Agreement, and
+
+ b) in the case of each subsequent Contributor:
+
+ i) changes to the Program, and
+
+ ii) additions to the Program;
+
+ where such changes and/or additions to the Program originate from and are
+ distributed by that particular Contributor. A Contribution 'originates' from
+ a Contributor if it was added to the Program by such Contributor itself or
+ anyone acting on such Contributor's behalf. Contributions do not include
+ additions to the Program which: (i) are separate modules of software
+ distributed in conjunction with the Program under their own license
+ agreement, and (ii) are not derivative works of the Program.
+
+"Contributor" means any person or entity that distributes the Program.
+
+"Licensed Patents " mean patent claims licensable by a Contributor which are
+necessarily infringed by the use or sale of its Contribution alone or when
+combined with the Program.
+
+"Program" means the Contributions distributed in accordance with this Agreement.
+
+"Recipient" means anyone who receives the Program under this Agreement, including
+all Contributors.
+
+2. GRANT OF RIGHTS
+
+ a) Subject to the terms of this Agreement, each Contributor hereby grants
+ Recipient a non-exclusive, worldwide, royalty-free copyright license to
+ reproduce, prepare derivative works of, publicly display, publicly perform,
+ distribute and sublicense the Contribution of such Contributor, if any, and
+ such derivative works, in source code and object code form.
+
+ b) Subject to the terms of this Agreement, each Contributor hereby grants
+ Recipient a non-exclusive, worldwide, royalty-free patent license under
+ Licensed Patents to make, use, sell, offer to sell, import and otherwise
+ transfer the Contribution of such Contributor, if any, in source code and
+ object code form. This patent license shall apply to the combination of the
+ Contribution and the Program if, at the time the Contribution is added by
+ the Contributor, such addition of the Contribution causes such combination
+ to be covered by the Licensed Patents. The patent license shall not apply to
+ any other combinations which include the Contribution. No hardware per se is
+ licensed hereunder.
+
+ c) Recipient understands that although each Contributor grants the licenses
+ to its Contributions set forth herein, no assurances are provided by any
+ Contributor that the Program does not infringe the patent or other
+ intellectual property rights of any other entity. Each Contributor disclaims
+ any liability to Recipient for claims brought by any other entity based on
+ infringement of intellectual property rights or otherwise. As a condition to
+ exercising the rights and licenses granted hereunder, each Recipient hereby
+ assumes sole responsibility to secure any other intellectual property rights
+ needed, if any. For example, if a third party patent license is required to
+ allow Recipient to distribute the Program, it is Recipient's responsibility
+ to acquire that license before distributing the Program.
+
+ d) Each Contributor represents that to its knowledge it has sufficient
+ copyright rights in its Contribution, if any, to grant the copyright license
+ set forth in this Agreement.
+
+3. REQUIREMENTS
+
+A Contributor may choose to distribute the Program in object code form under its
+own license agreement, provided that:
+
+ a) it complies with the terms and conditions of this Agreement; and
+
+ b) its license agreement:
+
+ i) effectively disclaims on behalf of all Contributors all warranties and
+ conditions, express and implied, including warranties or conditions of title
+ and non-infringement, and implied warranties or conditions of merchantability
+ and fitness for a particular purpose;
+
+ ii) effectively excludes on behalf of all Contributors all liability for
+ damages, including direct, indirect, special, incidental and consequential
+ damages, such as lost profits;
+
+ iii) states that any provisions which differ from this Agreement are offered
+ by that Contributor alone and not by any other party; and
+
+ iv) states that source code for the Program is available from such Contributor,
+ and informs licensees how to obtain it in a reasonable manner on or through
+ a medium customarily used for software exchange.
+
+When the Program is made available in source code form:
+
+ a) it must be made available under this Agreement; and
+
+ b) a copy of this Agreement must be included with each copy of the Program.
+
+Contributors may not remove or alter any copyright notices contained within the Program.
+
+Each Contributor must identify itself as the originator of its Contribution, if
+any, in a manner that reasonably allows subsequent Recipients to identify the
+originator of the Contribution.
+
+4. COMMERCIAL DISTRIBUTION
+
+Commercial distributors of software may accept certain responsibilities with
+respect to end users, business partners and the like. While this license is
+intended to facilitate the commercial use of the Program, the Contributor who
+includes the Program in a commercial product offering should do so in a manner
+which does not create potential liability for other Contributors. Therefore, if
+a Contributor includes the Program in a commercial product offering, such
+Contributor ("Commercial Contributor") hereby agrees to defend and indemnify
+every other Contributor ("Indemnified Contributor") against any losses, damages
+and costs (collectively "Losses") arising from claims, lawsuits and other legal
+actions brought by a third party against the Indemnified Contributor to the
+extent caused by the acts or omissions of such Commercial Contributor in
+connection with its distribution of the Program in a commercial product offering.
+The obligations in this section do not apply to any claims or Losses relating to
+any actual or alleged intellectual property infringement. In order to qualify,
+an Indemnified Contributor must: a) promptly notify the Commercial Contributor
+n writing of such claim, and b) allow the Commercial Contributor to control,
+and cooperate with the Commercial Contributor in, the defense and any related
+settlement negotiations. The Indemnified Contributor may participate in any such
+claim at its own expense.
+
+For example, a Contributor might include the Program in a commercial product
+offering, Product X. That Contributor is then a Commercial Contributor. If that
+Commercial Contributor then makes performance claims, or offers warranties
+related to Product X, those performance claims and warranties are such Commercial
+Contributor's responsibility alone. Under this section, the Commercial
+Contributor would have to defend claims against the other Contributors related
+to those performance claims and warranties, and if a court requires any other
+Contributor to pay any damages as a result, the Commercial Contributor must pay
+those damages.
+
+5. NO WARRANTY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
+IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE,
+NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each
+Recipient is solely responsible for determining the appropriateness of using
+and distributing the Program and assumes all risks associated with its exercise
+of rights under this Agreement, including but not limited to the risks and costs
+of program errors, compliance with applicable laws, damage to or loss of data,
+programs or equipment, and unavailability or interruption of operations.
+
+6. DISCLAIMER OF LIABILITY
+
+EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
+CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST
+PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
+WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS
+GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. GENERAL
+
+If any provision of this Agreement is invalid or unenforceable under applicable
+law, it shall not affect the validity or enforceability of the remainder of the
+terms of this Agreement, and without further action by the parties hereto, such
+provision shall be reformed to the minimum extent necessary to make such
+provision valid and enforceable.
+
+If Recipient institutes patent litigation against a Contributor with respect to
+a patent applicable to software (including a cross-claim or counterclaim in a
+lawsuit), then any patent licenses granted by that Contributor to such Recipient
+under this Agreement shall terminate as of the date such litigation is filed.
+In addition, if Recipient institutes patent litigation against any entity
+(including a cross-claim or counterclaim in a lawsuit) alleging that the Program
+itself (excluding combinations of the Program with other software or hardware)
+infringes such Recipient's patent(s), then such Recipient's rights granted under
+Section 2(b) shall terminate as of the date such litigation is filed.
+
+All Recipient's rights under this Agreement shall terminate if it fails to comply
+with any of the material terms or conditions of this Agreement and does not cure
+such failure in a reasonable period of time after becoming aware of such
+noncompliance. If all Recipient's rights under this Agreement terminate, Recipient
+agrees to cease use and distribution of the Program as soon as reasonably
+practicable. However, Recipient's obligations under this Agreement and any
+licenses granted by Recipient relating to the Program shall continue and survive.
+
+Everyone is permitted to copy and distribute copies of this Agreement, but in
+order to avoid inconsistency the Agreement is copyrighted and may only be modified
+in the following manner. The Agreement Steward reserves the right to publish new
+versions (including revisions) of this Agreement from time to time. No one other
+than the Agreement Steward has the right to modify this Agreement. IBM is the
+initial Agreement Steward. IBM may assign the responsibility to serve as the
+Agreement Steward to a suitable separate entity. Each new version of the Agreement
+will be given a distinguishing version number. The Program (including Contributions)
+may always be distributed subject to the version of the Agreement under which it
+was received. In addition, after a new version of the Agreement is published,
+Contributor may elect to distribute the Program (including its Contributions)
+under the new version. Except as expressly stated in Sections 2(a) and 2(b) above,
+Recipient receives no rights or licenses to the intellectual property of any
+Contributor under this Agreement, whether expressly, by implication, estoppel or
+otherwise. All rights in the Program not expressly granted under this Agreement
+are reserved.
+
+This Agreement is governed by the laws of the State of New York and the
+intellectual property laws of the United States of America. No party to this
+Agreement will bring a legal action under this Agreement more than one year after
+the cause of action arose. Each party waives its rights to a jury trial in any
+resulting litigation.
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/dom4j.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/dom4j.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/dom4j.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,12 @@
+Redistribution and use of this software and associated documentation ("Software"), with or without modification, are permitted provided that the following conditions are met:
+
+ 1. Redistributions of source code must retain copyright statements and notices. Redistributions must also contain a copy of this document.
+ 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+ 3. The name "DOM4J" must not be used to endorse or promote products derived from this Software without prior written permission of MetaStuff, Ltd. For written permission, please contact dom4j-info at metastuff.com.
+ 4. Products derived from this Software may not be called "DOM4J" nor may "DOM4J" appear in their names without prior written permission of MetaStuff, Ltd. DOM4J is a registered trademark of MetaStuff, Ltd.
+ 5. Due credit should be given to the DOM4J Project - http://www.dom4j.org
+
+THIS SOFTWARE IS PROVIDED BY METASTUFF, LTD. AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+Copyright 2001-2004 (C) MetaStuff, Ltd. All Rights Reserved.
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/hsqldb.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/hsqldb.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/hsqldb.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,65 @@
+/* Copyright (c) 1995-2000, The Hypersonic SQL Group.
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions are met:
+ *
+ * Redistributions of source code must retain the above copyright notice, this
+ * list of conditions and the following disclaimer.
+ *
+ * Redistributions in binary form must reproduce the above copyright notice,
+ * this list of conditions and the following disclaimer in the documentation
+ * and/or other materials provided with the distribution.
+ *
+ * Neither the name of the Hypersonic SQL Group nor the names of its
+ * contributors may be used to endorse or promote products derived from this
+ * software without specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+ * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED. IN NO EVENT SHALL THE HYPERSONIC SQL GROUP,
+ * OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+ * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
+ * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+ * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+ * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ *
+ * This software consists of voluntary contributions made by many individuals
+ * on behalf of the Hypersonic SQL Group.
+ *
+ *
+ * For work added by the HSQL Development Group:
+ *
+ * Copyright (c) 2001-2005, The HSQL Development Group
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions are met:
+ *
+ * Redistributions of source code must retain the above copyright notice, this
+ * list of conditions and the following disclaimer.
+ *
+ * Redistributions in binary form must reproduce the above copyright notice,
+ * this list of conditions and the following disclaimer in the documentation
+ * and/or other materials provided with the distribution.
+ *
+ * Neither the name of the HSQL Development Group nor the names of its
+ * contributors may be used to endorse or promote products derived from this
+ * software without specific prior written permission.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+ * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED. IN NO EVENT SHALL HSQL DEVELOPMENT GROUP, HSQLDB.ORG,
+ * OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+ * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
+ * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+ * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+ * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ */
+
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/ironsmith.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/ironsmith.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/ironsmith.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,52 @@
+/* ====================================================================
+ * The IronSmith Software License, Version 1.1
+ *
+ * (this license is derived and fully compatible with the Apache Software
+ * License - see http://www.apache.org/LICENSE.txt)
+ *
+ * Copyright (c) 2002 The IronSmith Project. All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright
+ * notice, this list of conditions and the following disclaimer.
+ *
+ * 2. Redistributions in binary form must reproduce the above copyright
+ * notice, this list of conditions and the following disclaimer in
+ * the documentation and/or other materials provided with the
+ * distribution.
+ *
+ * 3. The end-user documentation included with the redistribution,
+ * if any, must include the following acknowledgment:
+ * "This product includes software developed by the
+ * IronSmith Project (http://www.ironsmith.org/)."
+ * Alternately, this acknowledgment may appear in the software itself,
+ * if and wherever such third-party acknowledgments normally appear.
+ *
+ * 4. The names "IronSmith" and "The IronSmith Project"
+ * must not be used to endorse or promote products derived from this
+ * software without prior written permission. For written
+ * permission, please contact help at ironsmith.org.
+ *
+ * 5. Products derived from this software may not be called "IronSmith"
+ * or "QDox", nor may "IronSmith" or "QDox" appear in their
+ * name, without prior written permission of the IronSmith Project.
+ *
+ * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+ * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+ * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
+ * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+ * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
+ * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ * ====================================================================
+ */
+
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/jaxen.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/jaxen.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/jaxen.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,33 @@
+/*
+ $Id: jaxen.txt,v 1.2 2006/09/19 10:57:22 dimitris Exp $
+
+ Copyright 2003-2006 The Werken Company. All Rights Reserved.
+
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions are
+ met:
+
+ * Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+
+ * Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+
+ * Neither the name of the Jaxen Project nor the names of its
+ contributors may be used to endorse or promote products derived
+ from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
+IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
+TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
+OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
+PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
+PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+ */
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/juddi.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/juddi.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/juddi.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,35 @@
+ jUDDI License
+
+Copyright (c) 2003, Steve Viens and contributors.
+All rights reserved. Redistribution and use in source and
+binary forms, with or without modification, are permitted
+provided that the following conditions are met:
+
+* Redistributions of source code must retain the above
+ copyright notice, this list of conditions and the
+ following disclaimer.
+
+* Redistributions in binary form must reproduce the
+ above copyright notice, this list of conditions and
+ the following disclaimer in the documentation and/or
+ other materials provided with the distribution.
+
+* Neither name of Steve Viens nor the names of any
+ jUDDI contributors may be used to endorse or promote
+ products derived from this software without specific
+ prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
+CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
+GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
+BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
+OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/lgpl.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/lgpl.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/lgpl.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,504 @@
+ GNU LESSER GENERAL PUBLIC LICENSE
+ Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it. You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+ When we speak of free software, we are referring to freedom of use,
+not price. Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ To protect each distributor, we want to make it very clear that
+there is no warranty for the free library. Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+ Finally, software patents pose a constant threat to the existence of
+any free program. We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder. Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+ Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License. This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License. We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+ When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library. The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom. The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+ We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License. It also provides other free software developers Less
+of an advantage over competing non-free programs. These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain
+special circumstances.
+
+ For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard. To achieve this, non-free programs must be
+allowed to use the library. A more frequent case is that a free
+library does the same job as widely used non-free libraries. In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+ In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software. For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+ Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+ 2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) The modified work must itself be a software library.
+
+ b) You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c) You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d) If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library". The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+ a) Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ Sections 1 and 2 above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable "work that
+ uses the Library", as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (1) uses at run time a
+ copy of the library already present on the user's computer system,
+ rather than copying library functions into the executable, and (2)
+ will operate properly with a modified version of the library, if
+ the user installs one, as long as the modified version is
+ interface-compatible with the version that the work was made with.
+
+ c) Accompany the work with a written offer, valid for at
+ least three years, to give the same user the materials
+ specified in Subsection 6a, above, for a charge no more
+ than the cost of performing this distribution.
+
+ d) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ e) Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+ a) Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b) Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+ 9. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+
+ 11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Libraries
+
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the library's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Lesser General Public
+ License as published by the Free Software Foundation; either
+ version 2.1 of the License, or (at your option) any later version.
+
+ This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+
+ You should have received a copy of the GNU Lesser General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+
+Also add information on how to contact you by electronic and paper mail.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the library, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ library `Frob' (a library for tweaking knobs) written by James Random Hacker.
+
+ <signature of Ty Coon>, 1 April 1990
+ Ty Coon, President of Vice
+
+That's all there is to it!
+
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/license-info.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/license-info.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/license-info.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,248 @@
+<!-- A summary of the licenses used by the repository components
+$Id: license-info.xml,v 1.12 2007/02/13 21:03:45 tdiesler Exp $
+-->
+<licenses>
+ <!-- The valid headers for each license type. These headers are validated
+ by the org.jboss.tools.copyright.ValidateLicenseHeaders utility.
+ -->
+ <license id="apache-1.1" licenseFile="apache-1.1.txt">
+ <terms-header id="apache#1">
+ * The Apache Software License, Version 1.1
+ *
+ *
+ * Copyright (c) 2001-2003 The Apache Software Foundation. All rights
+ * reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ </terms-header>
+ <terms-header id="apache#2">
+ * Copyright (C) The Apache Software Foundation. All rights reserved.
+ *
+ * This software is published under the terms of the Apache Software License
+ * version 1.1, a copy of which has been included with this distribution in
+ * the docs/licenses/apache-1.1.txt file.
+ </terms-header>
+ </license>
+ <license id="apache-2.0" licenseFile="apache-2.0.txt">
+ <terms-header id="apache2#1">
+ * Copyright 2001-2004 The Apache Software Foundation.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ </terms-header>
+ </license>
+ <license id="bouncycastle" licenseFile="bouncycastle.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="bsd" licenseFile="bsd.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="cpl-1.0" licenseFile="cpl-1.0.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="dom4j" licenseFile="dom4-license.txt">
+ </license>
+ <license id="epl-1.0" licenseFile="epl-1.0.txt">
+ <terms-header/>
+ </license>
+ <license id="hsqldb" licenseFile="hsqldb.txt">
+ <terms-header/>
+ </license>
+ <license id="lgpl" licenseFile="lgpl.txt">
+ <terms-header id="jboss#0">
+ JBoss, Home of Professional Open Source.
+ Copyright 2006, Red Hat Middleware LLC, and individual contributors
+ as indicated by the @author tags. See the copyright.txt file in the
+ distribution for a full listing of individual contributors.
+ This is free software; you can redistribute it and/or modify it
+ under the terms of the GNU Lesser General Public License as
+ published by the Free Software Foundation; either version 2.1 of
+ the License, or (at your option) any later version.
+ This software is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+ You should have received a copy of the GNU Lesser General Public
+ License along with this software; if not, write to the Free
+ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
+ </terms-header>
+ <!-- Legacy jboss headers that should be replaced with jboss#0 -->
+ <terms-header id="jboss#1">
+ JBoss, Home of Professional Open Source
+ Copyright 2005, JBoss Inc., and individual contributors as indicated
+ by the @authors tag. See the copyright.txt in the distribution for a
+ full listing of individual contributors.
+ This is free software; you can redistribute it and/or modify it
+ under the terms of the GNU Lesser General Public License as
+ published by the Free Software Foundation; either version 2.1 of
+ the License, or (at your option) any later version.
+ This software is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.
+ You should have received a copy of the GNU Lesser General Public
+ License along with this software; if not, write to the Free
+ Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+ 02110-1301 USA, or see the FSF site: http://www.fsf.org.
+ </terms-header>
+ <terms-header id="jboss#2">
+ JBoss, Home of Professional Open Source
+ Distributable under LGPL license.
+ See terms of license at gnu.org.
+ </terms-header>
+ <terms-header id="jboss#3">
+ JBoss, the OpenSource J2EE webOS
+ Distributable under LGPL license.
+ See terms of license at gnu.org.
+ </terms-header>
+ <terms-header id="jboss#4">
+ JBoss, the OpenSource EJB server
+ Distributable under LGPL license.
+ See terms of license at gnu.org.
+ </terms-header>
+ <terms-header id="jboss#5">
+ JBoss, the OpenSource WebOS
+ Distributable under LGPL license.
+ See terms of license at gnu.org.
+ </terms-header>
+ <terms-header id="jboss#6">
+ JBoss: The OpenSource J2EE WebOS
+ Distributable under LGPL license.
+ See terms of license at gnu.org.
+ </terms-header>
+ <terms-header id="jboss#7">
+ * JBossMQ, the OpenSource JMS implementation
+ *
+ * Distributable under LGPL license. See terms of license at gnu.org.
+ </terms-header>
+ <terms-header id="intracom#1">
+ * Copyright (c) 2003, Intracom S.A. - www.intracom.com
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Lesser General Public
+ * License as published by the Free Software Foundation; either
+ * version 2 of the License, or (at your option) any later version
+ *
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Lesser General Public License for more details.
+ *
+ * You should have received a copy of the GNU Lesser General Public
+ * License along with this library; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ *
+ * This package and its source code is available at www.jboss.org
+ </terms-header>
+ </license>
+ <license id="jbpm-bpel" licenseFile="jbpm-bpel.txt">
+ <terms-header id="jbpm-bpel#0">
+ * JBoss, Home of Professional Open Source
+ * Copyright 2005, JBoss Inc., and individual contributors as indicated
+ * by the @authors tag.
+ *
+ * This is free software; you can redistribute it and/or modify it
+ * under the terms of the JBPM BPEL PUBLIC LICENSE AGREEMENT as
+ * published by JBoss Inc.; either version 1.0 of the License, or
+ * (at your option) any later version.
+ *
+ * This software is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+ </terms-header>
+ </license>
+ <license id="mit" licenseFile="mit.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="mozilla" licenseFile="mozilla-1.0.1.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="opensaml" licenseFile="opensaml.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="public-domain" licenseFile="public-domain.txt">
+ <terms-header/>
+ </license>
+ <license id="ironsmith" licenseFile="ironsmith.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="joram-tests">
+ <terms-header id="joram-tests#1">
+ * JORAM: Java(TM) Open Reliable Asynchronous Messaging
+ * Copyright (C) 2002 INRIA
+ * Contact: joram-team at objectweb.org
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Lesser General Public
+ * License as published by the Free Software Foundation; either
+ * version 2.1 of the License, or any later version.
+ *
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Lesser General Public License for more details.
+ </terms-header>
+ </license>
+ <license id="juddi" licenseFile="juddi.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="sleepycat" licenseFile="sleepycat.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="sun-jaf" licenseFile="sun-jaf.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="sun-javamail" licenseFile="sun-javamail.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="sun-jmf" licenseFile="sun-jmf.txt">
+ <terms-header>
+ </terms-header>
+ </license>
+ <license id="sun-misc">
+ <terms-header id="sun-misc#1">
+ * Copyright (c) 1998, 1999 Sun Microsystems, Inc. All Rights Reserved.
+ *
+ * Sun grants you ("Licensee") a non-exclusive, royalty free, license to use,
+ * modify and redistribute this software in source and binary code form,
+ * provided that i) this copyright notice and license appear on all copies of
+ * the software; and ii) Licensee does not utilize the software in a manner
+ * which is disparaging to Sun.
+ </terms-header>
+ </license>
+ <license id="w3c" licenseFile="w3c.txt">
+ <terms-header id="w3c#1">
+ * Copyright (c) 2004 World Wide Web Consortium,
+ *
+ * (Massachusetts Institute of Technology, European Research Consortium for
+ * Informatics and Mathematics, Keio University). All Rights Reserved. This
+ * work is distributed under the W3C(r) Software License [1] in the hope that
+ * it will be useful, but WITHOUT ANY WARRANTY; without even the implied
+ * warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+ </terms-header>
+ </license>
+</licenses>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/oswego.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/oswego.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/oswego.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,7 @@
+All classes are released to the public domain and may be used for any purpose
+whatsoever without permission or acknowledgment. Portions of the
+CopyOnWriteArrayList and ConcurrentReaderHashMap classes are adapted from Sun
+JDK source code. These are copyright of Sun Microsystems, Inc, and are used
+with their kind permission, as described in this license.
+http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/sun-u.c.license.pdf
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/thirdparty-licenses.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/thirdparty-licenses.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/thirdparty-licenses.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,607 @@
+<thirdparty-licenses> <module name='jboss/jaxr'
+ licenseType='lgpl'
+ version='1.2.0.GA'
+ projectHome='null'
+ description='JBoss JAXR implementation'>
+ <jar name='juddi-service.sar' />
+ <jar name='juddi-saaj.jar' />
+ </module>
+ <module name='apache-digester'
+ licenseType='apache-2.0'
+ version='1.7-brew'
+ projectHome='http://jakarta.apache.org/commons/digester/'
+ description='XML to Java object mapping module'>
+ <jar name='commons-digester.jar' />
+ </module>
+ <module name='jboss/jbossts14'
+ licenseType='lgpl'
+ version='4.2.3.SP3'
+ projectHome='http://labs.jboss.com/portal/jbosstm'
+ description='JBoss Transaction Service'>
+ <jar name='jbossjta.jar' />
+ <jar name='jbossjta-integration.jar' />
+ <jar name='jbossts-common.jar' />
+ <jar name='jbossjta-properties.xml' />
+ </module>
+ <module name='apache-collections'
+ licenseType='apache-2.0'
+ version='3.1-brew'
+ projectHome='http://jakarta.apache.org/commons/collections/'
+ description='Extensions to java.util type of collections'>
+ <jar name='commons-collections.jar' />
+ </module>
+ <module name='apache-velocity'
+ licenseType='apache-2.0'
+ version='1.4jboss-brew'
+ projectHome='http://jakarta.apache.org/velocity'
+ description='Velocity is a Java-based template engine. This jboss patch allows ',' and ':' characters to be in a variable character set to work around the problem that velocity has no way to escape ${x:y} and ${x,y:z} constructs that should just pass through the template engine unchanged'>
+ <jar name='velocity.jar' />
+ </module>
+ <module name='qdox'
+ licenseType='ironsmith'
+ version='1.6.1-brew'
+ projectHome='http://qdox.codehaus.org/'
+ description='Parser for extracting class/interface/method definitions from source files complete with JavaDoc @tags.'>
+ <jar name='qdox.jar' />
+ </module>
+ <module name='apache-avalon'
+ licenseType='apache-1.1'
+ version='4.1.5-brew'
+ projectHome='http://www.apache.org/dist/avalon/avalon-framework/'
+ description='Java Apache Server Framework'>
+ <jar name='avalon-framework.jar' />
+ </module>
+ <module name='jboss/profiler/jvmti'
+ licenseType='lgpl'
+ version='1.0.0.CR5-brew'
+ projectHome='http://www.jboss.org/profiler'
+ description='JVMTI Wrapper Library'>
+ <jar name='jboss-profiler-jvmti.jar' />
+ </module>
+ <module name='oswego-concurrent'
+ licenseType='oswego'
+ version='1.3.4-brew'
+ projectHome='http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html'
+ description='Oswego util.concurrent package'>
+ <jar name='concurrent.jar' />
+ </module>
+ <module name='jacorb'
+ licenseType='lgpl'
+ version='2.2.4jboss.patch1-brew'
+ projectHome='http://www.jacorb.org'
+ description='Java implementation of the OMG's CORBA standard.'>
+ <jar name='idl.jar' />
+ <jar name='idl_g.jar' />
+ <jar name='jacorb.jar' />
+ <jar name='jacorb_g.jar' />
+ <jar name='orb.idl' />
+ <jar name='CSI.idl' />
+ <jar name='CosTransactions.idl' />
+ <jar name='jacorb.properties' />
+ </module>
+ <module name='apache-avalon-logkit'
+ licenseType='apache-1.1'
+ version='1.2-brew'
+ projectHome='http://www.apache.org/dist/avalon/logkit/'
+ description='Java Apache Server Framework Logging'>
+ <jar name='logkit.jar' />
+ </module>
+ <module name='jboss/jboss-vfs'
+ licenseType='lgpl'
+ version='1.0.0.GA'
+ projectHome='null'
+ description='A VFS library'>
+ <jar name='jboss-vfs.jar' />
+ <jar name='jboss-vfs-sources.jar' />
+ </module>
+ <module name='trove'
+ licenseType='lgpl'
+ version='1.0.2-brew'
+ projectHome='http://trove4j.sourceforge.net/'
+ description='High performance collections for Java'>
+ <jar name='trove.jar' />
+ </module>
+ <module name='sun-javacc'
+ licenseType='bsd'
+ version='3.2'
+ projectHome='https://javacc.dev.java.net/'
+ description='JavaCC is a parser/scanner generator for java'>
+ <jar name='javacc.jar' />
+ </module>
+ <module name='gjt-jpl-util'
+ licenseType='lgpl'
+ version='1.0'
+ projectHome='http://www.gjt.org/pkgdoc/org/gjt/lindfors/util/'
+ description='Miscellaneous utility classes and methods'>
+ <jar name='jpl-util.jar' />
+ <jar name='jpl-pattern.jar' />
+ </module>
+ <module name='quartz'
+ licenseType='apache-2.0'
+ version='1.5.2-brew'
+ projectHome='http://www.opensymphony.com/'
+ description='Quartz is a full-featured, open source job scheduling system that can be integrated with, or used along side virtually any J2EE or J2SE application'>
+ <jar name='quartz-all.jar' />
+ <jar name='quartz.jar' />
+ </module>
+ <module name='sun-jstl'
+ licenseType='cddl'
+ version='1.2'
+ projectHome='http://jcp.org/en/jsr/detail?id=52'
+ description='The JSTL 1.2 implementation'>
+ <jar name='jstl.jar' />
+ </module>
+ <module name='apache-fileupload'
+ licenseType='apache-2.0'
+ version='1.1.1-brew'
+ projectHome='http://jakarta.apache.org/commons/fileupload/'
+ description='FileUpload parses HTTP requests which conform to RFC 1867'>
+ <jar name='commons-fileupload.jar' />
+ </module>
+ <module name='javassist'
+ licenseType='lgpl'
+ version='3.5.0.GA-brew'
+ projectHome='http://sourceforge.net/projects/jboss'
+ description='Simple Java bytecode manipulation (cvstag rel_3_5_GA)'>
+ <jar name='javassist.jar' />
+ <jar name='javassist-src.jar' />
+ </module>
+ <module name='antlr'
+ licenseType='antlr'
+ version='2.7.6-brew'
+ projectHome='http://www.antlr.org/'
+ description='ANother Tool for Language Recognition'>
+ <jar name='antlr.jar' />
+ </module>
+ <module name='gnu-getopt'
+ licenseType='lgpl'
+ version='1.0.12-brew'
+ projectHome='http://www.urbanophile.com/arenn/hacking/download.html'
+ description='Java getopt classes for short and long argument parsing'>
+ <jar name='getopt.jar' />
+ </module>
+ <module name='jboss/web'
+ licenseType='lgpl'
+ version='2.0.0.GA'
+ projectHome='null'
+ description='JBoss Web 2.0.0.GA'>
+ <jar name='el-api.jar' />
+ <jar name='jasper-jdt.jar' />
+ <jar name='jbossweb.jar' />
+ <jar name='jbossweb-extras.jar' />
+ <jar name='jsp-api.jar' />
+ <jar name='servlet-api.jar' />
+ <jar name='jbossweb-src.zip' />
+ </module>
+ <module name='apache-xmlsec'
+ licenseType='apache-2.0'
+ version='1.3.0-brew'
+ projectHome='http://xml.apache.org/security/index.html'
+ description='implementation of security standards for XML'>
+ <jar name='xmlsec.jar' />
+ </module>
+ <module name='wutka-dtdparser'
+ licenseType='lgpl'
+ version='1.21-brew'
+ projectHome='http://www.wutka.com/dtdparser.html'
+ description='DTD parser for Java'>
+ <jar name='dtdparser.jar' />
+ </module>
+ <module name='sun-jsf'
+ licenseType='cddl'
+ version='1.2_04_P01'
+ projectHome='https://javaserverfaces.dev.java.net/'
+ description='The JSF 1.2 implementation'>
+ <jar name='jsf-api.jar' />
+ <jar name='jsf-impl.jar' />
+ </module>
+ <module name='cglib'
+ licenseType='apache-2.0'
+ version='2.1.3-brew'
+ projectHome='http://cglib.sourceforge.net/'
+ description='Code Generation Library with no dependencies'>
+ <jar name='cglib.jar' />
+ </module>
+ <module name='apache-xerces'
+ licenseType='apache-2.0'
+ version='2.7.1-brew'
+ projectHome='http://xml.apache.org/xerces2-j/index.html'
+ description='High performance, fully compliant XML parser'>
+ <jar name='xercesImpl.jar' />
+ </module>
+ <module name='sun-jaf'
+ licenseType='cddl'
+ version='1.1'
+ projectHome='https://glassfish.dev.java.net/'
+ description='JavaBeans Activation Frameworkfrom glashfish(http://wiki.java.net/bin/view/Projects/GlassFishCodeDependencies)'>
+ <jar name='activation.jar' />
+ </module>
+ <module name='hibernate'
+ licenseType='lgpl'
+ version='3.2.3.GA'
+ projectHome='http://hibernate.org/'
+ description='ultra-high performance object/relational persistence'>
+ <jar name='hibernate3.jar' />
+ </module>
+ <module name='jboss/jbossws'
+ licenseType='lgpl'
+ version='1.2.1.GA'
+ projectHome='null'
+ description='JBossWS an implementation of J2EE Web Services'>
+ <jar name='jbossws-integration.jar' />
+ <jar name='jbossws-client.jar' />
+ <jar name='jbossws-core.jar' />
+ <jar name='jbossws-core-src.zip' />
+ <jar name='jboss-jaxrpc.jar' />
+ <jar name='jboss-jaxws.jar' />
+ <jar name='jboss-saaj.jar' />
+ </module>
+ <module name='beanshell'
+ licenseType='lgpl'
+ version='1.3.0-brew'
+ projectHome='http://www.beanshell.org/'
+ description='Lightweight Scripting for Java'>
+ <jar name='bsh.jar' />
+ </module>
+ <module name='woodstox'
+ licenseType='lgpl'
+ version='3.1.1-brew'
+ projectHome='http://woodstox.codehaus.org/'
+ description='A fast STAX parser implementation'>
+ <jar name='wstx.jar' />
+ </module>
+ <module name='jboss/jbossxb'
+ licenseType='lgpl'
+ version='1.0.0.GA-brew'
+ projectHome='http://anonsvn.jboss.org/repos/common/jbossxb/'
+ description='JBoss XML Binding'>
+ <jar name='jboss-xml-binding.jar' />
+ <jar name='jboss-xml-binding-sources.jar' />
+ </module>
+ <module name='apache-scout'
+ licenseType='apache-2.0'
+ version='0.7rc2'
+ projectHome='http://ws.apache.org/scout/'
+ description='An implementation of the JAXR spec'>
+ <jar name='scout.jar' />
+ </module>
+ <module name='joesnmp'
+ licenseType='lgpl'
+ version='0.3.4-brew'
+ projectHome='http://sourceforge.net/projects/joesnmp'
+ description='joeSNMP is an open-source Java SNMP library'>
+ <jar name='joesnmp.jar' />
+ </module>
+ <module name='apache-codec'
+ licenseType='apache-2.0'
+ version='1.3.0-brew'
+ projectHome='http://jakarta.apache.org/commons/codec/'
+ description='Commons Codec provides implementations of common encoders and decoders'>
+ <jar name='commons-codec.jar' />
+ </module>
+ <module name='apache-bcel'
+ licenseType='apache-2.0'
+ version='5.1-brew'
+ projectHome='http://jakarta.apache.org/bcel/index.html'
+ description='Byte Code Engineering Library'>
+ <jar name='bcel.jar' />
+ </module>
+ <module name='hibernate-annotations'
+ licenseType='lgpl'
+ version='3.2.1.GA'
+ projectHome='http://annotations.hibernate.org'
+ description='Annotations for Hibernate/EJB3'>
+ <jar name='hibernate-annotations.jar' />
+ </module>
+ <module name='stax-api'
+ licenseType='apache-2.0'
+ version='1.0'
+ projectHome='http://stax.codehaus.org/'
+ description='The STAX API'>
+ <jar name='stax-api.jar' />
+ </module>
+ <module name='hibernate-entitymanager'
+ licenseType='lgpl'
+ version='3.2.1.GA'
+ projectHome='http://entitymanager.hibernate.org/'
+ description='Hibernate EntityManager for EJB3'>
+ <jar name='hibernate-entitymanager.jar' />
+ <jar name='ejb3-persistence.jar' />
+ </module>
+ <module name='apache-log4j'
+ licenseType='apache-2.0'
+ version='1.2.14-brew'
+ projectHome='http://logging.apache.org/'
+ description='Java logging framework'>
+ <jar name='log4j.jar' />
+ </module>
+ <module name='apache-slide'
+ licenseType='apache-2.0'
+ version='2.1-brew'
+ projectHome='http://jakarta.apache.org/slide/index.html'
+ description='WebDAV Support Library'>
+ <jar name='jakarta-slide-webdavlib.jar' />
+ </module>
+ <module name='jboss/common'
+ licenseType='lgpl'
+ version='1.2.0.GA-brew'
+ projectHome='null'
+ description='Common utilities used in Branch_4_x of the JBossAS project'>
+ <jar name='namespace.jar' />
+ <jar name='jboss-common.jar' />
+ <jar name='jboss-common-client.jar' />
+ <jar name='jboss-common-sources.jar' />
+ </module>
+ <module name='jgroups'
+ licenseType='lgpl'
+ version='2.4.1.SP3-brew'
+ projectHome='http://www.jgroups.org'
+ description='JGroups is a toolkit for reliable multicast communication'>
+ <jar name='jgroups.jar' />
+ </module>
+ <module name='jboss/cache'
+ licenseType='lgpl'
+ version='1.4.1.SP3'
+ projectHome='http://www.jboss.org/products/jbosscache'
+ description='JBoss Cache is a product designed to cache frequently accessed Java objects in order to dramatically improve the performance of e-business applications.'>
+ <jar name='jboss-cache-jdk50.jar' />
+ </module>
+ <module name='hsqldb'
+ licenseType='hsqldb'
+ version='1.8.0.2'
+ projectHome='http://hsqldb.org/'
+ description='Java relational database engine supporting a subset of ANSI-92 SQL plus SQL 99 and 2003 enhancements'>
+ <jar name='hsqldb.jar' />
+ </module>
+ <module name='apache-httpclient'
+ licenseType='apache-2.0'
+ version='3.0.1-brew'
+ projectHome='http://jakarta.apache.org/commons/httpclient/'
+ description='Implementation of client side of the most recent HTTP standards'>
+ <jar name='commons-httpclient.jar' />
+ </module>
+ <module name='jboss/dom4j-jarjar'
+ licenseType='dom4j'
+ version='1.6.1'
+ projectHome='http://dom4j.org/'
+ description='JarJar Dom4j(base package = org.jboss.dom4j)'>
+ <jar name='dom4j-jarjar.jar' />
+ </module>
+ <module name='jboss/remoting'
+ licenseType='lgpl'
+ version='2.2.0.SP4'
+ projectHome='http://www.jboss.org/products/remoting'
+ description='a single API for most network based invocations and related service that uses pluggable transports and data marshallers'>
+ <jar name='jboss-remoting.jar' />
+ </module>
+ <module name='jbpm/jpdl'
+ licenseType='lgpl'
+ version='3.2.GA'
+ projectHome='http://jbpm.org/'
+ description='BPM and workflow engine in Java'>
+ <jar name='jbpm-jpdl.jar' />
+ <jar name='jbpm-identity.jar' />
+ <jar name='jbpm-jmx.jar' />
+ <jar name='jbpm-console.war' />
+ </module>
+ <module name='jbpm/bpel'
+ licenseType='cpl-1.0'
+ version='1.1.0.GA'
+ projectHome='http://jbpm.org/'
+ description='Web services orchestration platform'>
+ <jar name='jbpm-bpel.jar' />
+ <jar name='jbpm-bpel-jbossws12.jar' />
+ <jar name='jbpm-bpel.war' />
+ <jar name='jbpm-bpel.sar' />
+ </module>
+ <module name='apache-lang'
+ licenseType='apache-2.0'
+ version='2.1'
+ projectHome='http://jakarta.apache.org/commons/lang/'
+ description='no description'>
+ <jar name='commons-lang-2.1.jar' />
+ <jar name='commons-lang.jar' />
+ </module>
+ <module name='jboss/jbossws-wsconsume-impl'
+ licenseType='cddl'
+ version='2.0.0'
+ projectHome='null'
+ description='JBossWS wsconsume implementation'>
+ <jar name='jbossws-wsconsume-impl.jar' />
+ </module>
+ <module name='jfreechart'
+ licenseType='lgpl'
+ version='0.9.20'
+ projectHome='http://www.jfree.org/jfreechart/'
+ description='A free Java class library for generating charts, including'>
+ <jar name='jfreechart.jar' />
+ <jar name='jcommon.jar' />
+ </module>
+ <module name='junit'
+ licenseType='cpl-1.0'
+ version='3.8.2-brew'
+ projectHome='http://www.junit.org/index.htm'
+ description='Java unit testing framework'>
+ <jar name='junit.jar' />
+ </module>
+ <module name='xdoclet'
+ licenseType='xdoclet'
+ version='1.2.3-brew'
+ projectHome='http://xdoclet.sourceforge.net/xdoclet/index.html'
+ description='Open source code generation engine'>
+ <jar name='xdoclet-ejb-module.jar' />
+ <jar name='xdoclet-hibernate-module.jar' />
+ <jar name='xdoclet-java-module.jar' />
+ <jar name='xdoclet-jboss-module.jar' />
+ <jar name='xdoclet-jmx-module.jar' />
+ <jar name='xdoclet-portlet-module.jar' />
+ <jar name='xdoclet-web-module.jar' />
+ <jar name='xdoclet-xdoclet-module.jar' />
+ <jar name='xjavadoc.jar' />
+ <jar name='xdoclet.jar' />
+ </module>
+ <module name='jboss/microcontainer'
+ licenseType='lgpl'
+ version='1.0.2'
+ projectHome='null'
+ description='no description'>
+ <jar name='jboss-container.jar' />
+ <jar name='jboss-dependency.jar' />
+ <jar name='jboss-microcontainer.jar' />
+ </module>
+ <module name='odmg'
+ licenseType='apache-2.0'
+ version='3.0-brew'
+ projectHome='http://www.odmg.org/'
+ description='ODMG Java binding'>
+ <jar name='odmg.jar' />
+ </module>
+ <module name='dom4j'
+ licenseType='dom4j'
+ version='1.6.1-brew'
+ projectHome='http://dom4j.org/'
+ description='Library for XML, XPath and XSLT on the Java platform'>
+ <jar name='dom4j.jar' />
+ </module>
+ <module name='jboss/jbossws-jboss42'
+ licenseType='lgpl'
+ version='1.2.1.GA'
+ projectHome='null'
+ description='JBossWS an implementation of J2EE Web Services'>
+ <jar name='jbossws42.sar' />
+ <jar name='jbossws42-src.zip' />
+ </module>
+ <module name='apache-jaxme'
+ licenseType='apache-2.0'
+ version='0.2-cvs'
+ projectHome='http://ws.apache.org/jaxme/'
+ description='no description'>
+ <jar name='jaxmexs.jar' />
+ </module>
+ <module name='sun-jaxb'
+ licenseType='cddl'
+ version='2.0.3jboss'
+ projectHome='https://jaxb.dev.java.net/'
+ description='The JAXB 2.0 implementation'>
+ <jar name='jaxb-api.jar' />
+ <jar name='jaxb-xjc.jar' />
+ <jar name='jaxb-impl.jar' />
+ </module>
+ <module name='ibm-wsdl4j'
+ licenseType='cpl-1.0'
+ version='1.6.2-brew'
+ projectHome='http://sourceforge.net/projects/wsdl4j'
+ description='Web Services Description Language for Java Toolkit'>
+ <jar name='wsdl4j.jar' />
+ <jar name='wsdl4j-src.jar' />
+ </module>
+ <module name='apache-bsf'
+ licenseType='apache-1.1'
+ version='2.3.0-brew'
+ projectHome='http://jakarta.apache.org/bsf/'
+ description='Apache Bean Scripting Framework (BSF)'>
+ <jar name='bsf.jar' />
+ </module>
+ <module name='sun-javamail'
+ licenseType='cddl'
+ version='1.4'
+ projectHome='https://glassfish.dev.java.net/javaee5/mail/'
+ description='JavaMail APIs from glashfish(http://wiki.java.net/bin/view/Projects/GlassFishCodeDependencies)'>
+ <jar name='mail.jar' />
+ </module>
+ <module name='apache-discovery'
+ licenseType='apache-2.0'
+ version='0.4-brew'
+ projectHome='http://jakarta.apache.org/commons/discovery/'
+ description='Jakarta Commons Discovery'>
+ <jar name='commons-discovery.jar' />
+ </module>
+ <module name='snmptrapappender'
+ licenseType='apache-2.0'
+ version='1.2.8-brew'
+ projectHome=' http://www.m2technologies.net/asp/snmpTrapAppender.asp'
+ description='SNMP Trap Appender extension for log4j'>
+ <jar name='snmpTrapAppender.jar' />
+ </module>
+ <module name='juddi'
+ licenseType='juddi'
+ version='0.9RC4-brew'
+ projectHome='http://ws.apache.org/juddi/'
+ description='Universal Description, Discovery, and Integration (UDDI)'>
+ <jar name='juddi.jar' />
+ <jar name='juddi.war' />
+ </module>
+ <module name='jaxen'
+ licenseType='jaxen'
+ version='1.1-brew'
+ projectHome='http://jaxen.codehaus.org/'
+ description='Java XPath Engine'>
+ <jar name='jaxen.jar' />
+ </module>
+ <module name='objectweb-joramtests'
+ licenseType='lgpl'
+ version='1.1'
+ projectHome='null'
+ description='no description'>
+ <jar name='joram-tests.jar' />
+ </module>
+ <module name='jboss/aop'
+ licenseType='lgpl'
+ version='1.5.5.GA'
+ projectHome='http://www.jboss.org/products/aop'
+ description='JBoss Aspect Oriented Programming'>
+ <jar name='common-softvaluehashmap.jar' />
+ <jar name='jboss-aop-jdk50-client.jar' />
+ <jar name='jboss-aop-jdk50.jar' />
+ <jar name='jboss-aop.jar' />
+ <jar name='jdk14-pluggable-instrumentor.jar' />
+ <jar name='jrockit-pluggable-instrumentor.jar' />
+ <jar name='pluggable-instrumentor.jar' />
+ </module>
+ <module name='sun-servlet'
+ licenseType='apache-2.0'
+ version='2.5-brew'
+ projectHome='http://jakarta.apache.org/tomcat/index.html'
+ description='Tomcat 6.0.10 servlet 2.5 spec api classes (jsp 2.1)'>
+ <jar name='servlet-api.jar' />
+ <jar name='jsp-api.jar' />
+ </module>
+ <module name='apache-logging'
+ licenseType='apache-2.0'
+ version='1.1.0.jboss'
+ projectHome='http://jakarta.apache.org/commons/logging/'
+ description='Yet another logging api. This is the 1.1 release with the reflective log4j logger patch.'>
+ <jar name='commons-logging.jar' />
+ <jar name='commons-logging-src.zip' />
+ </module>
+ <module name='apache-beanutils'
+ licenseType='apache-2.0'
+ version='1.7.0-brew'
+ projectHome='http://jakarta.apache.org/commons/beanutils/'
+ description='Jakarta Commons BeanUtils Package'>
+ <jar name='commons-beanutils.jar' />
+ </module>
+ <module name='apache-xalan'
+ licenseType='apache-2.0'
+ version='2.7.0.patch01-brew'
+ projectHome='http://xml.apache.org/xalan-j/'
+ description='Xalan-Java is an XSLT processor for transforming XML documents'>
+ <jar name='xalan.jar' />
+ <jar name='serializer.jar' />
+ </module>
+ <module name='jboss/serialization'
+ licenseType='lgpl'
+ version='1.0.3.GA'
+ projectHome='http://labs.jboss.com/serialization'
+ description='JBoss Alternative Serialization'>
+ <jar name='jboss-serialization.jar' />
+ </module>
+ <module name='apache-xml-commons'
+ licenseType='apache-2.0'
+ version='1.3.03-brew'
+ projectHome='http://xml.apache.org/commons/'
+ description='Common code for XML projects'>
+ <jar name='resolver.jar' />
+ <jar name='xml-apis.jar' />
+ </module>
+</thirdparty-licenses>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/xdoclet.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/xdoclet.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/licenses/xdoclet.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,27 @@
+Copyright (c) 2000-2004, XDoclet Team
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+Redistributions of source code must retain the above copyright notice, this list
+of conditions and the following disclaimer.
+
+Redistributions in binary form must reproduce the above copyright notice, this
+list of conditions and the following disclaimer in the documentation and/or
+other materials provided with the distribution.
+
+Neither the name of the XDoclet team nor the names of its contributors may be
+used to endorse or promote products derived from this software without specific
+prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS''
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY
+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/README-SCHEMA.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/README-SCHEMA.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/README-SCHEMA.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,18 @@
+$Id: README-SCHEMA.txt 60567 2007-02-15 11:35:43Z dimitris at jboss.org $
+The following files contained within this folder are covered by license terms
+documented in docs/licenses/sun-specs.txt of the distribution.
+
+application_1_4.xsd
+application-client_1_4.xsd
+connector_1_5.xsd
+ejb-jar_2_1.xsd
+j2ee_1_4.xsd
+j2ee_jaxrpc_mapping_1_1.xsd
+j2ee_web_services_1_1.xsd
+j2ee_web_services_client_1_1.xsd
+jsp_2_0.xsd
+web-app_2_4.xsd
+web-jsptaglibrary_2_0.xsd
+
+More details on using these J2EE Schemas are available at:
+java.sun.com/xml/ns/j2ee/#usage
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application-client_1_4.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application-client_1_4.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application-client_1_4.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,266 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.4">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)application-client_1_4.xsds 1.17 02/11/03
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
+ Road, Palo Alto, California 94303, U.S.A. All rights
+ reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This is the XML Schema for the application client 1.4
+ deployment descriptor. The deployment descriptor must
+ be named "META-INF/application-client.xml" in the
+ application client's jar file. All application client
+ deployment descriptors must indicate the application
+ client schema by using the J2EE namespace:
+
+ http://java.sun.com/xml/ns/j2ee
+
+ and indicate the version of the schema by
+ using the version element as shown below:
+
+ <application-client xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
+ http://java.sun.com/xml/ns/j2ee/application-client_1_4.xsd"
+ version="1.4">
+ ...
+ </application-client>
+
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute for J2EE
+ namespace with the following location:
+
+ http://java.sun.com/xml/ns/j2ee/application-client_1_4.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all J2EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
+
+
+<!-- **************************************************** -->
+
+
+ <xsd:element name="application-client" type="j2ee:application-clientType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The application-client element is the root element of an
+ application client deployment descriptor. The application
+ client deployment descriptor describes the EJB components
+ and external resources referenced by the application
+ client.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:unique name="env-entry-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entry-name element contains the name of an
+ application client's environment entry. The name is a JNDI
+ name relative to the java:comp/env context. The name must
+ be unique within an application client.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:env-entry"/>
+ <xsd:field xpath="j2ee:env-entry-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="ejb-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the application
+ client's environment and is relative to the
+ java:comp/env context. The name must be unique within the
+ application client.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:ejb-ref"/>
+ <xsd:field xpath="j2ee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="res-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference.The name
+ is a JNDI name relative to the java:comp/env context.
+ The name must be unique within an application client.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:resource-ref"/>
+ <xsd:field xpath="j2ee:res-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="resource-env-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name of
+ a resource environment reference; its value is the
+ environment entry name used in the application client
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ application client.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:resource-env-ref"/>
+ <xsd:field xpath="j2ee:resource-env-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="message-destination-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies the
+ name of a message destination reference; its value is
+ the message destination reference name used in the
+ application client code. The name is a JNDI name
+ relative to the java:comp/env context and must be unique
+ within an application client.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:message-destination-ref"/>
+ <xsd:field xpath="j2ee:message-destination-ref-name"/>
+ </xsd:unique>
+ </xsd:element>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="application-clientType">
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="env-entry"
+ type="j2ee:env-entryType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="ejb-ref"
+ type="j2ee:ejb-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:group ref="j2ee:service-refGroup"/>
+ <xsd:element name="resource-ref"
+ type="j2ee:resource-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="resource-env-ref"
+ type="j2ee:resource-env-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="message-destination-ref"
+ type="j2ee:message-destination-refType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="callback-handler"
+ type="j2ee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The callback-handler element names a class provided by
+ the application. The class must have a no args
+ constructor and must implement the
+ javax.security.auth.callback.CallbackHandler
+ interface. The class will be instantiated by the
+ application client container and used by the container
+ to collect authentication information from the user.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="message-destination"
+ type="j2ee:message-destinationType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+
+ <xsd:attribute name="version"
+ type="j2ee:dewey-versionType"
+ fixed="1.4"
+ use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The required value for the version is 1.4.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:attribute>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application-client_5.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application-client_5.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application-client_5.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,303 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="5">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)application-client_5.xsds 1.26 02/17/06
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003-2006 Sun Microsystems, Inc.
+ 4150 Network Circle
+ Santa Clara, California 95054
+ U.S.A
+ All rights reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This is the XML Schema for the application client 5
+ deployment descriptor. The deployment descriptor must
+ be named "META-INF/application-client.xml" in the
+ application client's jar file. All application client
+ deployment descriptors must indicate the application
+ client schema by using the Java EE namespace:
+
+ http://java.sun.com/xml/ns/javaee
+
+ and indicate the version of the schema by
+ using the version element as shown below:
+
+ <application-client xmlns="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
+ http://java.sun.com/xml/ns/javaee/application-client_5.xsd"
+ version="5">
+ ...
+ </application-client>
+
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute for Java EE
+ namespace with the following location:
+
+ http://java.sun.com/xml/ns/javaee/application-client_5.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all Java EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="javaee_5.xsd"/>
+
+
+<!-- **************************************************** -->
+
+ <xsd:element name="application-client" type="javaee:application-clientType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The application-client element is the root element of an
+ application client deployment descriptor. The application
+ client deployment descriptor describes the EJB components
+ and external resources referenced by the application
+ client.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:unique name="env-entry-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entry-name element contains the name of an
+ application client's environment entry. The name is a JNDI
+ name relative to the java:comp/env context. The name must
+ be unique within an application client.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:env-entry"/>
+ <xsd:field xpath="javaee:env-entry-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="ejb-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the application
+ client's environment and is relative to the
+ java:comp/env context. The name must be unique within the
+ application client.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:ejb-ref"/>
+ <xsd:field xpath="javaee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="res-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference.The name
+ is a JNDI name relative to the java:comp/env context.
+ The name must be unique within an application client.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:resource-ref"/>
+ <xsd:field xpath="javaee:res-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="resource-env-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name of
+ a resource environment reference; its value is the
+ environment entry name used in the application client
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ application client.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:resource-env-ref"/>
+ <xsd:field xpath="javaee:resource-env-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="message-destination-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies the
+ name of a message destination reference; its value is
+ the message destination reference name used in the
+ application client code. The name is a JNDI name
+ relative to the java:comp/env context and must be unique
+ within an application client.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:message-destination-ref"/>
+ <xsd:field xpath="javaee:message-destination-ref-name"/>
+ </xsd:unique>
+ </xsd:element>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="application-clientType">
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="env-entry"
+ type="javaee:env-entryType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="ejb-ref"
+ type="javaee:ejb-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:group ref="javaee:service-refGroup"/>
+ <xsd:element name="resource-ref"
+ type="javaee:resource-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="resource-env-ref"
+ type="javaee:resource-env-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="message-destination-ref"
+ type="javaee:message-destination-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="persistence-unit-ref"
+ type="javaee:persistence-unit-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="post-construct"
+ type="javaee:lifecycle-callbackType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="pre-destroy"
+ type="javaee:lifecycle-callbackType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="callback-handler"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The callback-handler element names a class provided by
+ the application. The class must have a no args
+ constructor and must implement the
+ javax.security.auth.callback.CallbackHandler
+ interface. The class will be instantiated by the
+ application client container and used by the container
+ to collect authentication information from the user.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="message-destination"
+ type="javaee:message-destinationType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+
+ <xsd:attribute name="version"
+ type="javaee:dewey-versionType"
+ fixed="5"
+ use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The required value for the version is 5.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:attribute>
+
+ <xsd:attribute name="metadata-complete" type="xsd:boolean">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The metadata-complete attribute defines whether this
+ deployment descriptor and other related deployment
+ descriptors for this module (e.g., web service
+ descriptors) are complete, or whether the class
+ files available to this module and packaged with
+ this application should be examined for annotations
+ that specify deployment information.
+
+ If metadata-complete is set to "true", the deployment
+ tool must ignore any annotations that specify deployment
+ information, which might be present in the class files
+ of the application.
+
+ If metadata-complete is not specified or is set to
+ "false", the deployment tool must examine the class
+ files of the application for annotations, as
+ specified by the specifications.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:attribute>
+
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application_1_4.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application_1_4.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application_1_4.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,314 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.4">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)application_1_4.xsds 1.13 02/11/03
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
+ Road, Palo Alto, California 94303, U.S.A. All rights
+ reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This is the XML Schema for the application 1.4 deployment
+ descriptor. The deployment descriptor must be named
+ "META-INF/application.xml" in the application's ear file.
+ All application deployment descriptors must indicate
+ the application schema by using the J2EE namespace:
+
+ http://java.sun.com/xml/ns/j2ee
+
+ and indicate the version of the schema by
+ using the version element as shown below:
+
+ <application xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
+ http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"
+ version="1.4">
+ ...
+ </application>
+
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute for J2EE
+ namespace with the following location:
+
+ http://java.sun.com/xml/ns/j2ee/application_1_4.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all J2EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
+
+
+<!-- **************************************************** -->
+
+
+ <xsd:element name="application" type="j2ee:applicationType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The application element is the root element of a J2EE
+ application deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:unique name="context-root-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The context-root element content must be unique
+ in the ear.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:module/j2ee:web"/>
+ <xsd:field xpath="j2ee:context-root"/>
+ </xsd:unique>
+
+ <xsd:unique name="security-role-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The security-role-name element content
+ must be unique in the ear.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:security-role"/>
+ <xsd:field xpath="j2ee:role-name"/>
+ </xsd:unique>
+
+ </xsd:element>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="applicationType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The applicationType defines the structure of the
+ application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="module"
+ type="j2ee:moduleType"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The application deployment descriptor must have one
+ module element for each J2EE module in the
+ application package. A module element is defined
+ by moduleType definition.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="security-role"
+ type="j2ee:security-roleType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="version"
+ type="j2ee:dewey-versionType"
+ fixed="1.4"
+ use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The required value for the version is 1.4.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="moduleType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The moduleType defines a single J2EE module and contains a
+ connector, ejb, java, or web element, which indicates the
+ module type and contains a path to the module file, and an
+ optional alt-dd element, which specifies an optional URI to
+ the post-assembly version of the deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:choice>
+ <xsd:element name="connector"
+ type="j2ee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The connector element specifies the URI of a
+ resource adapter archive file, relative to the
+ top level of the application package.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="ejb"
+ type="j2ee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb element specifies the URI of an ejb-jar,
+ relative to the top level of the application
+ package.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="java"
+ type="j2ee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The java element specifies the URI of a java
+ application client module, relative to the top
+ level of the application package.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="web"
+ type="j2ee:webType"/>
+ </xsd:choice>
+ <xsd:element name="alt-dd"
+ type="j2ee:pathType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The alt-dd element specifies an optional URI to the
+ post-assembly version of the deployment descriptor
+ file for a particular J2EE module. The URI must
+ specify the full pathname of the deployment
+ descriptor file relative to the application's root
+ directory. If alt-dd is not specified, the deployer
+ must read the deployment descriptor from the default
+ location and file name required by the respective
+ component specification.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="webType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The webType defines the web-uri and context-root of
+ a web application module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="web-uri"
+ type="j2ee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The web-uri element specifies the URI of a web
+ application file, relative to the top level of the
+ application package.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="context-root"
+ type="j2ee:string">
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The context-root element specifies the context root
+ of a web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application_5.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application_5.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/application_5.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,334 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="5">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)application_5.xsds 1.17 08/05/05
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003-2006 Sun Microsystems, Inc.
+ 4150 Network Circle
+ Santa Clara, California 95054
+ U.S.A
+ All rights reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This is the XML Schema for the application 5 deployment
+ descriptor. The deployment descriptor must be named
+ "META-INF/application.xml" in the application's ear file.
+ All application deployment descriptors must indicate
+ the application schema by using the Java EE namespace:
+
+ http://java.sun.com/xml/ns/javaee
+
+ and indicate the version of the schema by
+ using the version element as shown below:
+
+ <application xmlns="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
+ http://java.sun.com/xml/ns/javaee/application_5.xsd"
+ version="5">
+ ...
+ </application>
+
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute for Java EE
+ namespace with the following location:
+
+ http://java.sun.com/xml/ns/javaee/application_5.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all Java EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="javaee_5.xsd"/>
+
+
+<!-- **************************************************** -->
+
+ <xsd:element name="application" type="javaee:applicationType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The application element is the root element of a Java EE
+ application deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:unique name="context-root-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The context-root element content must be unique
+ in the ear.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:module/javaee:web"/>
+ <xsd:field xpath="javaee:context-root"/>
+ </xsd:unique>
+
+ <xsd:unique name="security-role-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The security-role-name element content
+ must be unique in the ear.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:security-role"/>
+ <xsd:field xpath="javaee:role-name"/>
+ </xsd:unique>
+
+ </xsd:element>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="applicationType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The applicationType defines the structure of the
+ application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="module"
+ type="javaee:moduleType"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The application deployment descriptor must have one
+ module element for each Java EE module in the
+ application package. A module element is defined
+ by moduleType definition.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="security-role"
+ type="javaee:security-roleType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="library-directory"
+ type="javaee:pathType"
+ minOccurs="0"
+ maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The library-directory element specifies the pathname
+ of a directory within the application package, relative
+ to the top level of the application package. All files
+ named "*.jar" in this directory must be made available
+ in the class path of all components included in this
+ application package. If this element isn't specified,
+ the directory named "lib" is searched. An empty element
+ may be used to disable searching.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="version"
+ type="javaee:dewey-versionType"
+ fixed="5"
+ use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The required value for the version is 5.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="moduleType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The moduleType defines a single Java EE module and contains a
+ connector, ejb, java, or web element, which indicates the
+ module type and contains a path to the module file, and an
+ optional alt-dd element, which specifies an optional URI to
+ the post-assembly version of the deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:choice>
+ <xsd:element name="connector"
+ type="javaee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The connector element specifies the URI of a
+ resource adapter archive file, relative to the
+ top level of the application package.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="ejb"
+ type="javaee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb element specifies the URI of an ejb-jar,
+ relative to the top level of the application
+ package.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="java"
+ type="javaee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The java element specifies the URI of a java
+ application client module, relative to the top
+ level of the application package.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="web"
+ type="javaee:webType"/>
+ </xsd:choice>
+ <xsd:element name="alt-dd"
+ type="javaee:pathType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The alt-dd element specifies an optional URI to the
+ post-assembly version of the deployment descriptor
+ file for a particular Java EE module. The URI must
+ specify the full pathname of the deployment
+ descriptor file relative to the application's root
+ directory. If alt-dd is not specified, the deployer
+ must read the deployment descriptor from the default
+ location and file name required by the respective
+ component specification.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="webType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The webType defines the web-uri and context-root of
+ a web application module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="web-uri"
+ type="javaee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The web-uri element specifies the URI of a web
+ application file, relative to the top level of the
+ application package.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="context-root"
+ type="javaee:string">
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The context-root element specifies the context root
+ of a web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/bean-deployer_1_0.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/bean-deployer_1_0.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/bean-deployer_1_0.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,688 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- A prototype xsd schema for the pojoserver xml deployer
+$Id: bean-deployer_1_0.xsd 39207 2005-12-21 22:49:56Z adrian $
+ -->
+<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="urn:jboss:bean-deployer"
+ xmlns="urn:jboss:bean-deployer"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.0">
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The xml deployer schema. The deployment document instance
+ root element should reference the schema in the root
+ deployment element using something like:
+
+ <deployment
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="urn:jboss:bean-deployer bean-deployer_1_0.xsd"
+ xmlns="urn:jboss:bean-deployer">
+ ...
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:element name="deployment" type="deploymentType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The root of the xml deployer instance document
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:complexType name="deploymentType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The deployment contains a number of beans and bean factories.
+
+ e.g.
+ <deployment ...>
+ <bean .../>
+ <bean .../>
+ <beanfactory .../>
+ </deployment>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="bean" type="beanType" minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="beanfactory" type="beanfactoryType" minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+ <xsd:complexType name="beanType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The bean is an instance of a pojo.
+
+ e.g.
+ <bean name="MyName" class="com.acme.POJO">
+ <constructor .../>
+ <property .../>
+ <property .../>
+ <depends .../>
+ </bean>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="annotation" type="annotationType" minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="constructor" type="constructorType" minOccurs="0"/>
+ <xsd:element name="property" type="propertyType" minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="create" type="lifecycleType" minOccurs="0"/>
+ <xsd:element name="start" type="lifecycleType" minOccurs="0"/>
+ <xsd:element name="stop" type="lifecycleType" minOccurs="0"/>
+ <xsd:element name="destroy" type="lifecycleType" minOccurs="0"/>
+ <xsd:element name="depends" type="dependsType" minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="demand" type="demandType" minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="supply" type="supplyType" minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="optional"/>
+ <xsd:attribute name="class" type="xsd:token" use="required"/>
+ <xsd:attribute name="mode" type="controllerModeType" use="optional"/>
+ </xsd:complexType>
+
+ <xsd:complexType name="beanfactoryType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The beanfactory is a org.jboss.beans.metadata.plugins.factory.GenericBeanFactory deployment.
+ This gives you a factory such you can invoke create() multiple times with the guarantee
+ that the injected objects are "installed".
+
+ e.g.
+ <bean name="User" class="com.acme.User">
+ <property name="factory"><inject bean="Factory"/></property>
+ </bean>
+
+ <beanfactory name="Factory" class="com.acme.SomeBean">
+ <property name="someProperty"><inject bean="SomeOtherBean"/></property>
+ </beanFactory>
+
+ package com.acme.User;
+ public class User {
+ // factory has been configured at this point
+ public void setFactory(GenericBeanFactory factory) {
+ SomeBean bean1 = factory.create();
+ System.out.println(bean1.getSomeProperty()); // "SomeOtherBean"
+ SomeBean bean2 = factory.create();
+ System.out.println(bean2.getSomeProperty()); // "SomeOtherBean"
+ }
+ }
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="constructor" type="constructorType" minOccurs="0"/>
+ <xsd:element name="property" type="propertyType" minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="optional"/>
+ <xsd:attribute name="class" type="xsd:token" use="required"/>
+ </xsd:complexType>
+
+ <xsd:complexType name="constructorType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The constructor for this bean(factory) instance.
+
+ e.g. simple constructor - new POJO(new String("String value"));
+ <bean name="MyBean" class="com.acme.POJO">
+ <constructor>
+ <parameter>String value</parameter>
+ </constructor>
+ </bean>
+
+ e.g. static factory - com.acme.Factory.newInstance(new String("String value"));
+ <bean name="MyBean" class="com.acme.POJO">
+ <constructor factoryClass="com.acme.Factory" factoryMethod="newInstance">
+ <parameter>String value</parameter>
+ </constructor>
+ </bean>
+
+ e.g. instance factory - "SomeOtherBean".newInstance(new String("String value"));
+ <bean name="MyBean" class="com.acme.POJO">
+ <constructor factoryMethod="newInstance">
+ <factory bean="SomeOtherBean"/>
+ <parameter>String value</parameter>
+ </constructor>
+ </bean>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="annotation" type="annotationType" minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="factory" type="dependencyType" minOccurs="0"/>
+ <xsd:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="factoryClass" type="classNameType" use="optional"/>
+ <xsd:attribute name="factoryMethod" type="xsd:token" use="optional"/>
+ </xsd:complexType>
+
+ <xsd:complexType name="lifecycleType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The lifecycle lets you override the method parameters passed to the
+ create, start, stop, destroy lifecycle callbacks.
+
+ e.g.
+ <bean>
+ <create method="initialize">
+ <parameter>String value</parameter>
+ </create>
+ </bean>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="annotation" type="annotationType" minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="parameter" type="parameterType" minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="method" type="xsd:token" use="optional"/>
+ </xsd:complexType>
+
+ <xsd:complexType name="dependencyType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A dependency represents an injection into the bean.
+ They can be used anywhere a string value can appear.
+
+ e.g. Bean instance - "InjectedIntoMe".setSomeProperty("BeanInjected");
+ <bean name="InjectedIntoMe" ...>
+ <property name="someProperty"><inject bean="BeanInjected"/>
+ </bean>
+ <bean name="BeanInjected" .../>
+
+ e.g. Bean property - "InjectedIntoMe".setSomeProperty("BeanInjected".getOtherProperty());
+ <bean name="InjectedIntoMe" ...>
+ <property name="someProperty"><inject bean="BeanInjected" property="otherProperty"/>
+ </bean>
+ <bean name="BeanInjected" .../>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="bean" type="xsd:string" use="required"/>
+ <xsd:attribute name="property" type="xsd:string" use="optional"/>
+ <xsd:attribute name="state" type="controllerStateType" use="optional"/>
+ </xsd:complexType>
+
+ <xsd:complexType name="parameterType" mixed="true">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A parameter is used to define the constructor, factory
+ and lifecycle method usage.
+
+ e.g. Using number of parameters when this is unique enough
+ <bean ...>
+ <constructor>
+ <parameter>1st Parameter</parameter>
+ <parameter>2nd Parameter</parameter>
+ </constructor>
+ </bean>
+
+ e.g. Explicitly stating the parameter type to resolve overloading
+ <bean ...>
+ <constructor>
+ <parameter>1st Parameter</parameter>
+ <parameter class="java.lang.String">2nd Parameter</parameter>
+ </constructor>
+ </bean>
+
+ e.g. To override the injected type use <value/>
+ <bean ...>
+ <constructor>
+ <parameter>1st Parameter</parameter>
+ <!-- Parameter is java.lang.Object, but we inject a String -->
+ <parameter class="java.lang.Object">
+ <value class="java.lang.String">2nd Parameter</value>
+ </parameter>
+ </constructor>
+ </bean>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexContent>
+ <xsd:extension base="annotatedValueType"/>
+ </xsd:complexContent>
+ </xsd:complexType>
+
+ <xsd:complexType name="propertyType" mixed="true">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A property defines values passed to the setters.
+
+ e.g. Using the type from the setter argument
+ <bean ...>
+ <property name="someProperty">Some value</property>
+ </bean>
+
+ e.g. Overridding the injected type
+ <bean ...>
+ <property name="someProperty" class="java.lang.String">Some value</property>
+ </bean>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexContent>
+ <xsd:extension base="namedValueType"/>
+ </xsd:complexContent>
+ </xsd:complexType>
+
+ <xsd:complexType name="annotationType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The annotation type represents an annotation on the particular join point.
+ TODO: This is currently unimplemented.
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="attribute" type="annotationAttributeType" minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <xsd:complexType name="annotationAttributeType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ An attribute attached to a particular annotation.
+ TODO: This is currently unimplemented.
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="value" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <xsd:simpleType name="classNameType">
+ <xsd:annotation>
+ <xsd:documentation> The elements that use this type designate the name
+ of a Java class or interface. The name is in the form of a "binary
+ name", as defined in the JLS and as used in Class.forName().
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:string">
+ <xsd:whiteSpace value="collapse"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <xsd:group name="valueGroup">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The value group represents the comment elements of the other configurations
+ <parameter/>, <property/> or collection components
+ e.g.
+
+ <property name="someProperty">
+ <list><value class="java.lang.String">Hello</value></list>
+ </property>
+
+ e.g. This also defines the null value
+ <property name="someProperty"><null/></property>
+ as opposed to the empty string
+ <property name="someProperty"></property>
+ or the string "null"
+ <property name="someProperty">null</property>
+
+ TODO: "any" is currently unimplemented.
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:choice>
+ <xsd:element name="value" type="plainValueType"/>
+ <xsd:element name="collection" type="collectionType"/>
+ <xsd:element name="list" type="listType"/>
+ <xsd:element name="set" type="setType"/>
+ <xsd:element name="array" type="arrayType"/>
+ <xsd:element name="map" type="mapType"/>
+ <xsd:element name="inject" type="dependencyType"/>
+ <xsd:element name="null">
+ <xsd:complexType/>
+ </xsd:element>
+ <xsd:any namespace="##other" processContents="strict">
+ <xsd:annotation>
+ <xsd:documentation>An extension value</xsd:documentation>
+ </xsd:annotation>
+ </xsd:any>
+ </xsd:choice>
+ </xsd:group>
+
+ <xsd:complexType name="plainValueType" mixed="true">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A simple value, used in collections and to specify a type for parameters.
+
+ e.g.
+ <parameter><value class="com.acme.MyClass">xxx</value></parameter>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="class" type="classNameType" use="optional"/>
+ </xsd:complexType>
+
+ <xsd:complexType name="valueType" mixed="true">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A value that can take other values, i.e. properties and parameters.
+
+ e.g.
+ <parameter><value class="com.acme.MyClass">xxx</value></parameter>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexContent>
+ <xsd:extension base="plainValueType">
+ <xsd:sequence>
+ <xsd:choice minOccurs="0">
+ <xsd:group ref="valueGroup"/>
+ </xsd:choice>
+ </xsd:sequence>
+ </xsd:extension>
+ </xsd:complexContent>
+ </xsd:complexType>
+
+ <xsd:complexType name="annotatedValueType" mixed="true">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A value that can take annotations.
+ TODO: This is currently unimplemented.
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexContent>
+ <xsd:extension base="valueType">
+ <xsd:sequence>
+ <xsd:element name="annotation" type="annotationType" minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:extension>
+ </xsd:complexContent>
+ </xsd:complexType>
+
+ <xsd:complexType name="namedValueType" mixed="true">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A value that has a name, currently only a property.
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexContent>
+ <xsd:extension base="annotatedValueType">
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:extension>
+ </xsd:complexContent>
+ </xsd:complexType>
+
+ <xsd:complexType name="baseCollectionType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A collection defines a java.util.Collection object.
+ It has two class definitions:
+ class: The implementation class of the collection
+ elementClass: The default implementation class of the elements
+ The default "class" is a java.util.ArrayList unless the point of injection
+ defines a concrete type, e.g. in the signature of the setter
+
+ example:
+ <property name="whatever" class="java.util.ArrayList" elementClass="java.net.URL">
+ <value>http://localhost</value> <!-- Creates a URL -->
+ <value class="java.lang.String">http://localhost</value> <!-- Creates a String -->
+ </property>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:choice minOccurs="0" maxOccurs="unbounded">
+ <xsd:group ref="valueGroup"/>
+ </xsd:choice>
+ <xsd:attribute name="class" type="classNameType" use="optional"/>
+ <xsd:attribute name="elementClass" type="classNameType" use="optional"/>
+ </xsd:complexType>
+
+ <xsd:complexType name="collectionType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A collection, see baseCollectionType
+ the default collection is a java.util.ArrayList
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexContent>
+ <xsd:extension base="baseCollectionType"/>
+ </xsd:complexContent>
+ </xsd:complexType>
+
+ <xsd:complexType name="listType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A list, see baseCollectionType
+ the default list is a java.util.ArrayList
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexContent>
+ <xsd:extension base="baseCollectionType"/>
+ </xsd:complexContent>
+ </xsd:complexType>
+
+ <xsd:complexType name="setType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A set, see baseCollectionType
+ the default set is a java.util.HashSet
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexContent>
+ <xsd:extension base="baseCollectionType"/>
+ </xsd:complexContent>
+ </xsd:complexType>
+
+ <xsd:complexType name="arrayType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ An array, see baseCollectionType
+ the default array is a java.lang.Object[]
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexContent>
+ <xsd:extension base="baseCollectionType"/>
+ </xsd:complexContent>
+ </xsd:complexType>
+
+ <xsd:complexType name="mapType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ A map defines a java.util.Map object.
+ It has three class definitions:
+ class: The implementation class of the class
+ keyClass: The default implementation class of the keys
+ valueClass: The default implementation class of the values
+ The default "class" is a java.util.HashMap unless the point of injection
+ defines a concrete type, e.g. in the signature of the setter
+
+ e.g.:
+ <property name="whatever" class="java.util.HashMap" keyClass="java.lang.String" valueClas="java.net.URL">
+ <!-- map.put(new String("default"), new URL("http://localhost"));
+ <entry><key>default</key><value>http://localhost</value>
+ <!-- map.put(new String("default"), new String("http://localhost"));
+ <entry><key>default</key><value class="java.lang.String">http://localhost</value>
+ </property>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="entry" type="entryType" minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="class" type="classNameType" use="optional"/>
+ <xsd:attribute name="keyClass" type="classNameType" use="optional"/>
+ <xsd:attribute name="valueClass" type="classNameType" use="optional"/>
+ </xsd:complexType>
+
+ <xsd:complexType name="entryType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ An entry in map. These are made of key/value pairs
+
+ e.g.:
+ <entry><key>default</key><value>http://localhost</value>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="key" type="valueType" minOccurs="0"/>
+ <xsd:element name="value" type="valueType" minOccurs="0"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+ <xsd:complexType name="dependsType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The depends element is used to define that one bean depends upon
+ another for the create/start/stop/destroy lifecycle
+
+ e.g.:
+ <bean name="IGoFirst" .../>
+ <bean name="IGoSecond" ...>
+ <depends>IGoFirst</depends>
+ </bean>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <xsd:complexType name="demandType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The demand is used to specify a dependency on a supply
+ and when the demand is should be deplied
+
+ e.g.:
+ ISupply must be installed before IDemand is constructed
+
+ <bean name="IDemand" ... whenRequired="Instantiated">
+ <demand>theSupply</demand>
+ </bean>
+ <bean name="ISupply" ...>
+ <supply>theSupply</supply>
+ </bean>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:string">
+ <xsd:attribute name="whenRequired" type="controllerStateType" use="optional"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <xsd:complexType name="supplyType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The supply is used to specify that the bean supplies a demanded dependency
+
+ e.g.:
+ <bean name="IDemand" ...>
+ <demand>theSupply</demand>
+ </bean>
+ <bean name="ISupply" ...>
+ <supply>theSupply</supply>
+ </bean>
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <xsd:simpleType name="controllerStateType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The controller state is used to say when dependencies must be satisfied.
+ Valid values include:
+ Described
+ Instantiated
+ Configured
+ Create
+ Start
+ Installed
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:string">
+ <xsd:whiteSpace value="collapse"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <xsd:simpleType name="controllerModeType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+ The controller mode, used to control how automatic the bean progresses
+ through the controller lifecyle (the states).
+ Valid values include:
+ Automatic (default) - the controller takes the bean to "Installed"
+ Manual - the user must tell the controller the required state
+ On Demand - the controller takes the bean to "Installed" when another bean depends on it
+ Disabled - the controller or user cannot change the state
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:string">
+ <xsd:whiteSpace value="collapse"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!--
+ WARN:
+ Do not use this in the bean deployer, it won't work!
+ FIXME:
+ The correct way to do this is to have two separate
+ schemas (one for deployments the other for beans)
+ then use schema imports.
+ -->
+ <xsd:element name="bean" type="beanType"/>
+
+ <!--
+ WARN:
+ Do not use this in the bean deployer, it won't work!
+ FIXME:
+ The correct way to do this is to have two separate
+ schemas (one for deployments the other for beans)
+ then use schema imports.
+ -->
+ <xsd:element name="beanfactory" type="beanfactoryType"/>
+
+</xsd:schema>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/connector_1_5.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/connector_1_5.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/connector_1_5.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1035 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.5">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)connector_1_5.xsds 1.27 06/17/03
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003 Sun Microsystems, Inc., 901 San Antonio
+ Road, Palo Alto, California 94303, U.S.A. All rights
+ reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This is the XML Schema for the Connector 1.5 deployment
+ descriptor. The deployment descriptor must be named
+ "META-INF/ra.xml" in the connector's rar file. All Connector
+ deployment descriptors must indicate the connector resource
+ adapter schema by using the J2EE namespace:
+
+ http://java.sun.com/xml/ns/j2ee
+
+ and by indicating the version of the schema by
+ using the version element as shown below:
+
+ <connector xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
+ http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd"
+ version="1.5">
+ ...
+ </connector>
+
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute for J2EE
+ namespace with the following location:
+
+ http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all J2EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
+
+
+<!-- **************************************************** -->
+
+
+ <xsd:element name="connector" type="j2ee:connectorType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The connector element is the root element of the deployment
+ descriptor for the resource adapter. This element includes
+ general information - vendor name, resource adapter version,
+ icon - about the resource adapter module. It also includes
+ information specific to the implementation of the resource
+ adapter library as specified through the element
+ resourceadapter.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="activationspecType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The activationspecType specifies an activation
+ specification. The information includes fully qualified
+ Java class name of an activation specification and a set of
+ required configuration property names.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="activationspec-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The element activationspec-class specifies the fully
+ qualified Java class name of the activation
+ specification class. This class must implement the
+ javax.resource.spi.ActivationSpec interface. The
+ implementation of this class is required to be a
+ JavaBean.
+
+ Example:
+ <activationspec-class>com.wombat.ActivationSpecImpl
+ </activationspec-class>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="required-config-property"
+ type="j2ee:required-config-propertyType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="adminobjectType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The adminobjectType specifies information about an
+ administered object. Administered objects are specific to a
+ messaging style or message provider. This contains
+ information on the Java type of the interface implemented by
+ an administered object, its Java class name and its
+ configuration properties.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="adminobject-interface"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The element adminobject-interface specifies the
+ fully qualified name of the Java type of the
+ interface implemented by an administered object.
+
+ Example:
+ <adminobject-interface>javax.jms.Destination
+ </adminobject-interface>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="adminobject-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The element adminobject-class specifies the fully
+ qualified Java class name of an administered object.
+
+ Example:
+ <adminobject-class>com.wombat.DestinationImpl
+ </adminobject-class>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="config-property"
+ type="j2ee:config-propertyType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="authentication-mechanismType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The authentication-mechanismType specifies an authentication
+ mechanism supported by the resource adapter. Note that this
+ support is for the resource adapter and not for the
+ underlying EIS instance. The optional description specifies
+ any resource adapter specific requirement for the support of
+ security contract and authentication mechanism.
+
+ Note that BasicPassword mechanism type should support the
+ javax.resource.spi.security.PasswordCredential interface.
+ The Kerbv5 mechanism type should support the
+ org.ietf.jgss.GSSCredential interface or the deprecated
+ javax.resource.spi.security.GenericCredential interface.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="authentication-mechanism-type"
+ type="j2ee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The element authentication-mechanism-type specifies
+ type of an authentication mechanism.
+
+ The example values are:
+
+ <authentication-mechanism-type>BasicPassword
+ </authentication-mechanism-type>
+
+ <authentication-mechanism-type>Kerbv5
+ </authentication-mechanism-type>
+
+ Any additional security mechanisms are outside the
+ scope of the Connector architecture specification.
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="credential-interface"
+ type="j2ee:credential-interfaceType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="config-property-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The config-property-nameType contains the name of a
+ configuration property.
+
+ The connector architecture defines a set of well-defined
+ properties all of type java.lang.String. These are as
+ follows.
+
+ ServerName
+ PortNumber
+ UserName
+ Password
+ ConnectionURL
+
+ A resource adapter provider can extend this property set to
+ include properties specific to the resource adapter and its
+ underlying EIS.
+
+ Possible values include
+ ServerName
+ PortNumber
+ UserName
+ Password
+ ConnectionURL
+
+ Example: <config-property-name>ServerName</config-property-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:xsdStringType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="config-property-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The config-property-typeType contains the fully
+ qualified Java type of a configuration property.
+
+ The following are the legal values:
+ java.lang.Boolean, java.lang.String, java.lang.Integer,
+ java.lang.Double, java.lang.Byte, java.lang.Short,
+ java.lang.Long, java.lang.Float, java.lang.Character
+
+ Used in: config-property
+
+ Example:
+ <config-property-type>java.lang.String</config-property-type>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="java.lang.Boolean"/>
+ <xsd:enumeration value="java.lang.String"/>
+ <xsd:enumeration value="java.lang.Integer"/>
+ <xsd:enumeration value="java.lang.Double"/>
+ <xsd:enumeration value="java.lang.Byte"/>
+ <xsd:enumeration value="java.lang.Short"/>
+ <xsd:enumeration value="java.lang.Long"/>
+ <xsd:enumeration value="java.lang.Float"/>
+ <xsd:enumeration value="java.lang.Character"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="config-propertyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The config-propertyType contains a declaration of a single
+ configuration property that may be used for providing
+ configuration information.
+
+ The declaration consists of an optional description, name,
+ type and an optional value of the configuration property. If
+ the resource adapter provider does not specify a value than
+ the deployer is responsible for providing a valid value for
+ a configuration property.
+
+ Any bounds or well-defined values of properties should be
+ described in the description element.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="config-property-name"
+ type="j2ee:config-property-nameType"/>
+ <xsd:element name="config-property-type"
+ type="j2ee:config-property-typeType"/>
+ <xsd:element name="config-property-value"
+ type="j2ee:xsdStringType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The element config-property-value contains the value
+ of a configuration entry. Note, it is possible for a
+ resource adapter deployer to override this
+ configuration information during deployment.
+
+ Example:
+ <config-property-value>WombatServer</config-property-value>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="connection-definitionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The connection-definitionType defines a set of connection
+ interfaces and classes pertaining to a particular connection
+ type. This also includes configurable properties for
+ ManagedConnectionFactory instances that may be produced out
+ of this set.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="managedconnectionfactory-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The element managedconnectionfactory-class specifies
+ the fully qualified name of the Java class that
+ implements the
+ javax.resource.spi.ManagedConnectionFactory interface.
+ This Java class is provided as part of resource
+ adapter's implementation of connector architecture
+ specified contracts. The implementation of this
+ class is required to be a JavaBean.
+
+ Example:
+ <managedconnectionfactory-class>
+ com.wombat.ManagedConnectionFactoryImpl
+ </managedconnectionfactory-class>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="config-property"
+ type="j2ee:config-propertyType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="connectionfactory-interface"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The element connectionfactory-interface specifies
+ the fully qualified name of the ConnectionFactory
+ interface supported by the resource adapter.
+
+ Example:
+ <connectionfactory-interface>com.wombat.ConnectionFactory
+ </connectionfactory-interface>
+
+ OR
+
+ <connectionfactory-interface>javax.resource.cci.ConnectionFactory
+ </connectionfactory-interface>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="connectionfactory-impl-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The element connectionfactory-impl-class specifies
+ the fully qualified name of the ConnectionFactory
+ class that implements resource adapter
+ specific ConnectionFactory interface.
+
+ Example:
+
+ <connectionfactory-impl-class>com.wombat.ConnectionFactoryImpl
+ </connectionfactory-impl-class>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="connection-interface"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The connection-interface element specifies the fully
+ qualified name of the Connection interface supported
+ by the resource adapter.
+
+ Example:
+
+ <connection-interface>javax.resource.cci.Connection
+ </connection-interface>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="connection-impl-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The connection-impl-classType specifies the fully
+ qualified name of the Connection class that
+ implements resource adapter specific Connection
+ interface. It is used by the connection-impl-class
+ elements.
+
+ Example:
+
+ <connection-impl-class>com.wombat.ConnectionImpl
+ </connection-impl-class>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="connectorType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The connectorType defines a resource adapter.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="vendor-name"
+ type="j2ee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The element vendor-name specifies the name of
+ resource adapter provider vendor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="eis-type"
+ type="j2ee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The element eis-type contains information about the
+ type of the EIS. For example, the type of an EIS can
+ be product name of EIS independent of any version
+ info.
+
+ This helps in identifying EIS instances that can be
+ used with this resource adapter.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="resourceadapter-version"
+ type="j2ee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The element resourceadapter-version specifies a string-based version
+ of the resource adapter from the resource adapter
+ provider.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="license"
+ type="j2ee:licenseType"
+ minOccurs="0"/>
+ <xsd:element name="resourceadapter"
+ type="j2ee:resourceadapterType"/>
+
+ </xsd:sequence>
+ <xsd:attribute name="version"
+ type="j2ee:dewey-versionType"
+ fixed="1.5"
+ use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The version specifies the version of the
+ connector architecture specification that is
+ supported by this resource adapter. This information
+ enables deployer to configure the resource adapter to
+ support deployment and runtime requirements of the
+ corresponding connector architecture specification.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="credential-interfaceType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The credential-interfaceType specifies the
+ interface that the resource adapter implementation
+ supports for the representation of the
+ credentials. This element(s) that use this type,
+ i.e. credential-interface, should be used by
+ application server to find out the Credential
+ interface it should use as part of the security
+ contract.
+
+ The possible values are:
+
+ javax.resource.spi.security.PasswordCredential
+ org.ietf.jgss.GSSCredential
+ javax.resource.spi.security.GenericCredential
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:fully-qualified-classType">
+ <xsd:enumeration
+ value="javax.resource.spi.security.PasswordCredential"/>
+ <xsd:enumeration
+ value="org.ietf.jgss.GSSCredential"/>
+ <xsd:enumeration
+ value="javax.resource.spi.security.GenericCredential"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="inbound-resourceadapterType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The inbound-resourceadapterType specifies information
+ about an inbound resource adapter. This contains information
+ specific to the implementation of the resource adapter
+ library as specified through the messageadapter element.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="messageadapter"
+ type="j2ee:messageadapterType"
+ minOccurs="0">
+ <xsd:unique name="messagelistener-type-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The messagelistener-type element content must be
+ unique in the messageadapter. Several messagelisteners
+ can not use the same messagelistener-type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:messagelistener"/>
+ <xsd:field xpath="j2ee:messagelistener-type"/>
+ </xsd:unique>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="licenseType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The licenseType specifies licensing requirements for the
+ resource adapter module. This type specifies whether a
+ license is required to deploy and use this resource adapter,
+ and an optional description of the licensing terms
+ (examples: duration of license, number of connection
+ restrictions). It is used by the license element.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="license-required"
+ type="j2ee:true-falseType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The element license-required specifies whether a
+ license is required to deploy and use the
+ resource adapter. This element must be one of
+ the following, "true" or "false".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="messageadapterType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The messageadapterType specifies information about the
+ messaging capabilities of the resource adapter. This
+ contains information specific to the implementation of the
+ resource adapter library as specified through the
+ messagelistener element.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="messagelistener"
+ type="j2ee:messagelistenerType"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="messagelistenerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The messagelistenerType specifies information about a
+ specific message listener supported by the messaging
+ resource adapter. It contains information on the Java type
+ of the message listener interface and an activation
+ specification.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="messagelistener-type"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The element messagelistener-type specifies the fully
+ qualified name of the Java type of a message
+ listener interface.
+
+ Example:
+
+ <messagelistener-type>javax.jms.MessageListener
+ </messagelistener-type>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="activationspec"
+ type="j2ee:activationspecType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="outbound-resourceadapterType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The outbound-resourceadapterType specifies information about
+ an outbound resource adapter. The information includes fully
+ qualified names of classes/interfaces required as part of
+ the connector architecture specified contracts for
+ connection management, level of transaction support
+ provided, one or more authentication mechanisms supported
+ and additional required security permissions.
+
+ If there is no authentication-mechanism specified as part of
+ resource adapter element then the resource adapter does not
+ support any standard security authentication mechanisms as
+ part of security contract. The application server ignores
+ the security part of the system contracts in this case.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="connection-definition"
+ type="j2ee:connection-definitionType"
+ maxOccurs="unbounded"/>
+ <xsd:element name="transaction-support"
+ type="j2ee:transaction-supportType"/>
+ <xsd:element name="authentication-mechanism"
+ type="j2ee:authentication-mechanismType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="reauthentication-support"
+ type="j2ee:true-falseType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The element reauthentication-support specifies
+ whether the resource adapter implementation supports
+ re-authentication of existing Managed- Connection
+ instance. Note that this information is for the
+ resource adapter implementation and not for the
+ underlying EIS instance. This element must have
+ either a "true" or "false" value.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="required-config-propertyType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The required-config-propertyType contains a declaration
+ of a single configuration property used for specifying a
+ required configuration property name. It is used
+ by required-config-property elements.
+
+ Example:
+
+ <required-config-property>Destination</required-config-property>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="config-property-name"
+ type="j2ee:config-property-nameType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="resourceadapterType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resourceadapterType specifies information about the
+ resource adapter. The information includes fully qualified
+ resource adapter Java class name, configuration properties,
+ information specific to the implementation of the resource
+ adapter library as specified through the
+ outbound-resourceadapter and inbound-resourceadapter
+ elements, and an optional set of administered objects.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="resourceadapter-class"
+ type="j2ee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The element resourceadapter-class specifies the
+ fully qualified name of a Java class that implements
+ the javax.resource.spi.ResourceAdapter
+ interface. This Java class is provided as part of
+ resource adapter's implementation of connector
+ architecture specified contracts. The implementation
+ of this class is required to be a JavaBean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="config-property"
+ type="j2ee:config-propertyType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="outbound-resourceadapter"
+ type="j2ee:outbound-resourceadapterType"
+ minOccurs="0">
+ <xsd:unique name="connectionfactory-interface-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The connectionfactory-interface element content
+ must be unique in the outbound-resourceadapter.
+ Multiple connection-definitions can not use the
+ same connectionfactory-type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:connection-definition"/>
+ <xsd:field xpath="j2ee:connectionfactory-interface"/>
+ </xsd:unique>
+ </xsd:element>
+ <xsd:element name="inbound-resourceadapter"
+ type="j2ee:inbound-resourceadapterType"
+ minOccurs="0"/>
+ <xsd:element name="adminobject"
+ type="j2ee:adminobjectType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="security-permission"
+ type="j2ee:security-permissionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="security-permissionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The security-permissionType specifies a security
+ permission that is required by the resource adapter code.
+
+ The security permission listed in the deployment descriptor
+ are ones that are different from those required by the
+ default permission set as specified in the connector
+ specification. The optional description can mention specific
+ reason that resource adapter requires a given security
+ permission.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="security-permission-spec"
+ type="j2ee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The element security-permission-spec specifies a security
+ permission based on the Security policy file
+ syntax. Refer to the following URL for Sun's
+ implementation of the security permission
+ specification:
+
+ http://java.sun.com/products/jdk/1.4/docs/guide/security/PolicyFiles.html#FileSyntax
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="transaction-supportType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The transaction-supportType specifies the level of
+ transaction support provided by the resource adapter. It is
+ used by transaction-support elements.
+
+ The value must be one of the following:
+
+ NoTransaction
+ LocalTransaction
+ XATransaction
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="NoTransaction"/>
+ <xsd:enumeration value="LocalTransaction"/>
+ <xsd:enumeration value="XATransaction"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/ejb-jar_2_1.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/ejb-jar_2_1.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/ejb-jar_2_1.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,2207 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="2.1">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)ejb-jar_2_1.xsds 1.23 08/01/03
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003 Sun Microsystems, Inc., 901 San Antonio
+ Road, Palo Alto, California 94303, U.S.A. All rights
+ reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This is the XML Schema for the EJB 2.1 deployment descriptor.
+ The deployment descriptor must be named "META-INF/ejb-jar.xml" in
+ the EJB's jar file. All EJB deployment descriptors must indicate
+ the ejb-jar schema by using the J2EE namespace:
+
+ http://java.sun.com/xml/ns/j2ee
+
+ and by indicating the version of the schema by
+ using the version element as shown below:
+
+ <ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
+ http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
+ version="2.1">
+ ...
+ </ejb-jar>
+
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute for the
+ J2EE namespace with the following location:
+
+ http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all J2EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
+
+
+<!-- **************************************************** -->
+
+
+ <xsd:element name="ejb-jar" type="j2ee:ejb-jarType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This is the root of the ejb-jar deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:key name="ejb-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-name element contains the name of an enterprise
+ bean. The name must be unique within the ejb-jar file.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:enterprise-beans/*"/>
+ <xsd:field xpath="j2ee:ejb-name"/>
+ </xsd:key>
+
+ <xsd:keyref name="ejb-name-references"
+ refer="j2ee:ejb-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The keyref indicates the references from
+ relationship-role-source must be to a specific ejb-name
+ defined within the scope of enterprise-beans element.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector
+ xpath=".//j2ee:ejb-relationship-role/j2ee:relationship-role-source"/>
+ <xsd:field
+ xpath="j2ee:ejb-name"/>
+ </xsd:keyref>
+
+ <xsd:key name="role-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ A role-name-key is specified to allow the references
+ from the security-role-refs.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:assembly-descriptor/j2ee:security-role"/>
+ <xsd:field xpath="j2ee:role-name"/>
+ </xsd:key>
+
+ <xsd:keyref name="role-name-references"
+ refer="j2ee:role-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The keyref indicates the references from
+ security-role-ref to a specified role-name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:enterprise-beans/*/j2ee:security-role-ref"/>
+ <xsd:field xpath="j2ee:role-link"/>
+ </xsd:keyref>
+ </xsd:element>
+
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="activation-config-propertyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The activation-config-propertyType contains a name/value
+ configuration property pair for a message-driven bean.
+
+ The properties that are recognized for a particular
+ message-driven bean are determined by the messaging type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="activation-config-property-name"
+ type="j2ee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The activation-config-property-name element contains
+ the name for an activation configuration property of
+ a message-driven bean.
+
+ For JMS message-driven beans, the following property
+ names are recognized: acknowledgeMode,
+ messageSelector, destinationType, subscriptionDurability
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="activation-config-property-value"
+ type="j2ee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The activation-config-property-value element
+ contains the value for an activation configuration
+ property of a message-driven bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="activation-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The activation-configType defines information about the
+ expected configuration properties of the message-driven bean
+ in its operational environment. This may include information
+ about message acknowledgement, message selector, expected
+ destination type, etc.
+
+ The configuration information is expressed in terms of
+ name/value configuration properties.
+
+ The properties that are recognized for a particular
+ message-driven bean are determined by the messaging type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="activation-config-property"
+ type="j2ee:activation-config-propertyType"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="assembly-descriptorType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The assembly-descriptorType defines
+ application-assembly information.
+
+ The application-assembly information consists of the
+ following parts: the definition of security roles, the
+ definition of method permissions, the definition of
+ transaction attributes for enterprise beans with
+ container-managed transaction demarcation and a list of
+ methods to be excluded from being invoked.
+
+ All the parts are optional in the sense that they are
+ omitted if the lists represented by them are empty.
+
+ Providing an assembly-descriptor in the deployment
+ descriptor is optional for the ejb-jar file producer.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="security-role"
+ type="j2ee:security-roleType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="method-permission"
+ type="j2ee:method-permissionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="container-transaction"
+ type="j2ee:container-transactionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="message-destination"
+ type="j2ee:message-destinationType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="exclude-list"
+ type="j2ee:exclude-listType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="cmp-fieldType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cmp-fieldType describes a container-managed field. The
+ cmp-fieldType contains an optional description of the field,
+ and the name of the field.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="field-name"
+ type="j2ee:java-identifierType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The field-name element specifies the name of a
+ container managed field.
+
+ The name of the cmp-field of an entity bean with
+ cmp-version 2.x must begin with a lowercase
+ letter. This field is accessed by methods whose
+ names consists of the name of the field specified by
+ field-name in which the first letter is uppercased,
+ prefixed by "get" or "set".
+
+ The name of the cmp-field of an entity bean with
+ cmp-version 1.x must denote a public field of the
+ enterprise bean class or one of its superclasses.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="cmp-versionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cmp-versionType specifies the version of an entity bean
+ with container-managed persistence. It is used by
+ cmp-version elements.
+
+ The value must be one of the two following:
+
+ 1.x
+ 2.x
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="1.x"/>
+ <xsd:enumeration value="2.x"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="cmr-field-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cmr-field-type element specifies the class of a
+ collection-valued logical relationship field in the entity
+ bean class. The value of an element using cmr-field-typeType
+ must be either: java.util.Collection or java.util.Set.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="java.util.Collection"/>
+ <xsd:enumeration value="java.util.Set"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="cmr-fieldType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cmr-fieldType describes the bean provider's view of
+ a relationship. It consists of an optional description, and
+ the name and the class type of a field in the source of a
+ role of a relationship. The cmr-field-name element
+ corresponds to the name used for the get and set accessor
+ methods for the relationship. The cmr-field-type element is
+ used only for collection-valued cmr-fields. It specifies the
+ type of the collection that is used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="cmr-field-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cmr-field-name element specifies the name of a
+ logical relationship field in the entity bean
+ class. The name of the cmr-field must begin with a
+ lowercase letter. This field is accessed by methods
+ whose names consist of the name of the field
+ specified by cmr-field-name in which the first
+ letter is uppercased, prefixed by "get" or "set".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="cmr-field-type"
+ type="j2ee:cmr-field-typeType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="container-transactionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The container-transactionType specifies how the container
+ must manage transaction scopes for the enterprise bean's
+ method invocations. It defines an optional description, a
+ list of method elements, and a transaction attribute. The
+ transaction attribute is to be applied to all the specified
+ methods.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="method"
+ type="j2ee:methodType"
+ maxOccurs="unbounded"/>
+ <xsd:element name="trans-attribute"
+ type="j2ee:trans-attributeType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The ejb-classType contains the fully-qualified name of the
+ enterprise bean's class. It is used by ejb-class elements.
+
+ Example:
+
+ <ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-jarType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-jarType defines the root element of the EJB
+ deployment descriptor. It contains
+
+ - an optional description of the ejb-jar file
+ - an optional display name
+ - an optional icon that contains a small and a large
+ icon file name
+ - mandatory structural information about all included
+ enterprise beans
+ - a descriptor for container managed relationships,
+ if any
+ - an optional application-assembly descriptor
+ - an optional name of an ejb-client-jar file for the
+ ejb-jar.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="enterprise-beans"
+ type="j2ee:enterprise-beansType"/>
+ <xsd:element name="relationships"
+ type="j2ee:relationshipsType"
+ minOccurs="0">
+ <xsd:unique name="relationship-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-relation-name contains the name of a
+ relation. The name must be unique within
+ relationships.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:ejb-relation"/>
+ <xsd:field xpath="j2ee:ejb-relation-name"/>
+ </xsd:unique>
+ </xsd:element>
+ <xsd:element name="assembly-descriptor"
+ type="j2ee:assembly-descriptorType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Providing an assembly-descriptor in the deployment
+ descriptor is optional for the ejb-jar file
+ producer.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="ejb-client-jar"
+ type="j2ee:pathType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The optional ejb-client-jar element specifies a JAR
+ file that contains the class files necessary for a
+ client program to access the
+ enterprise beans in the ejb-jar file.
+
+ Example:
+
+ <ejb-client-jar>employee_service_client.jar
+ </ejb-client-jar>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="version"
+ type="j2ee:dewey-versionType"
+ fixed="2.1"
+ use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The version specifies the version of the
+ EJB specification that the instance document must
+ comply with. This information enables deployment tools
+ to validate a particular EJB Deployment
+ Descriptor with respect to a specific version of the EJB
+ schema.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The ejb-nameType specifies an enterprise bean's name. It is
+ used by ejb-name elements. This name is assigned by the
+ ejb-jar file producer to name the enterprise bean in the
+ ejb-jar file's deployment descriptor. The name must be
+ unique among the names of the enterprise beans in the same
+ ejb-jar file.
+
+ There is no architected relationship between the used
+ ejb-name in the deployment descriptor and the JNDI name that
+ the Deployer will assign to the enterprise bean's home.
+
+ The name for an entity bean must conform to the lexical
+ rules for an NMTOKEN.
+
+ Example:
+
+ <ejb-name>EmployeeService</ejb-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:xsdNMTOKENType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-relationType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-relationType describes a relationship between two
+ entity beans with container-managed persistence. It is used
+ by ejb-relation elements. It contains a description; an
+ optional ejb-relation-name element; and exactly two
+ relationship role declarations, defined by the
+ ejb-relationship-role elements. The name of the
+ relationship, if specified, is unique within the ejb-jar
+ file.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-relation-name"
+ type="j2ee:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-relation-name element provides a unique name
+ within the ejb-jar file for a relationship.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="ejb-relationship-role"
+ type="j2ee:ejb-relationship-roleType"/>
+ <xsd:element name="ejb-relationship-role"
+ type="j2ee:ejb-relationship-roleType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-relationship-roleType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The ejb-relationship-roleType describes a role within a
+ relationship. There are two roles in each relationship.
+
+ The ejb-relationship-roleType contains an optional
+ description; an optional name for the relationship role; a
+ specification of the multiplicity of the role; an optional
+ specification of cascade-delete functionality for the role;
+ the role source; and a declaration of the cmr-field, if any,
+ by means of which the other side of the relationship is
+ accessed from the perspective of the role source.
+
+ The multiplicity and role-source element are mandatory.
+
+ The relationship-role-source element designates an entity
+ bean by means of an ejb-name element. For bidirectional
+ relationships, both roles of a relationship must declare a
+ relationship-role-source element that specifies a cmr-field
+ in terms of which the relationship is accessed. The lack of
+ a cmr-field element in an ejb-relationship-role specifies
+ that the relationship is unidirectional in navigability and
+ the entity bean that participates in the relationship is
+ "not aware" of the relationship.
+
+ Example:
+
+ <ejb-relation>
+ <ejb-relation-name>Product-LineItem</ejb-relation-name>
+ <ejb-relationship-role>
+ <ejb-relationship-role-name>product-has-lineitems
+ </ejb-relationship-role-name>
+ <multiplicity>One</multiplicity>
+ <relationship-role-source>
+ <ejb-name>ProductEJB</ejb-name>
+ </relationship-role-source>
+ </ejb-relationship-role>
+ </ejb-relation>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-relationship-role-name"
+ type="j2ee:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-relationship-role-name element defines a
+ name for a role that is unique within an
+ ejb-relation. Different relationships can use the
+ same name for a role.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="multiplicity"
+ type="j2ee:multiplicityType"/>
+ <xsd:element name="cascade-delete"
+ type="j2ee:emptyType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cascade-delete element specifies that, within a
+ particular relationship, the lifetime of one or more
+ entity beans is dependent upon the lifetime of
+ another entity bean. The cascade-delete element can
+ only be specified for an ejb-relationship-role
+ element contained in an ejb-relation element in
+ which the other ejb-relationship-role
+ element specifies a multiplicity of One.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="relationship-role-source"
+ type="j2ee:relationship-role-sourceType"/>
+ <xsd:element name="cmr-field"
+ type="j2ee:cmr-fieldType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="enterprise-beansType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The enterprise-beansType declares one or more enterprise
+ beans. Each bean can be a session, entity or message-driven
+ bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:choice maxOccurs="unbounded">
+ <xsd:element name="session"
+ type="j2ee:session-beanType">
+ <xsd:unique name="session-ejb-local-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of
+ an EJB reference. The EJB reference is an entry in
+ the component's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the component.
+
+ It is recommended that name be prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:ejb-local-ref"/>
+ <xsd:field xpath="j2ee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="session-ejb-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the
+ component's environment and is relative to the
+ java:comp/env context. The name must be unique
+ within the component.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:ejb-ref"/>
+ <xsd:field xpath="j2ee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="session-resource-env-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name
+ of a resource environment reference; its value is
+ the environment entry name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:resource-env-ref"/>
+ <xsd:field xpath="j2ee:resource-env-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="session-message-destination-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies the name
+ of a message destination reference; its value is
+ the message destination reference name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:message-destination-ref"/>
+ <xsd:field xpath="j2ee:message-destination-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="session-res-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference. The name
+ is a JNDI name relative to the java:comp/env context.
+ The name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:resource-ref"/>
+ <xsd:field xpath="j2ee:res-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="session-env-entry-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entry-name element contains the name of a
+ component's environment entry. The name is a JNDI
+ name relative to the java:comp/env context. The
+ name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:env-entry"/>
+ <xsd:field xpath="j2ee:env-entry-name"/>
+ </xsd:unique>
+ </xsd:element>
+
+ <xsd:element name="entity"
+ type="j2ee:entity-beanType">
+ <xsd:unique name="entity-ejb-local-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of
+ an EJB reference. The EJB reference is an entry in
+ the component's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the component.
+
+ It is recommended that name be prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:ejb-local-ref"/>
+ <xsd:field xpath="j2ee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="entity-ejb-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the
+ component's environment and is relative to the
+ java:comp/env context. The name must be unique
+ within the component.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:ejb-ref"/>
+ <xsd:field xpath="j2ee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="entity-resource-env-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name
+ of a resource environment reference; its value is
+ the environment entry name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:resource-env-ref"/>
+ <xsd:field xpath="j2ee:resource-env-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="entity-message-destination-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies the name
+ of a message destination reference; its value is
+ the message destination reference name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:message-destination-ref"/>
+ <xsd:field xpath="j2ee:message-destination-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="entity-res-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference. The name
+ is a JNDI name relative to the java:comp/env context.
+ The name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:resource-ref"/>
+ <xsd:field xpath="j2ee:res-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="entity-env-entry-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entry-name element contains the name of a
+ component's environment entry. The name is a JNDI
+ name relative to the java:comp/env context. The
+ name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:env-entry"/>
+ <xsd:field xpath="j2ee:env-entry-name"/>
+ </xsd:unique>
+ </xsd:element>
+
+ <xsd:element name="message-driven"
+ type="j2ee:message-driven-beanType">
+ <xsd:unique name="messaged-ejb-local-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of
+ an EJB reference. The EJB reference is an entry in
+ the component's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the component.
+
+ It is recommended that name be prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:ejb-local-ref"/>
+ <xsd:field xpath="j2ee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="messaged-ejb-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the
+ component's environment and is relative to the
+ java:comp/env context. The name must be unique
+ within the component.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:ejb-ref"/>
+ <xsd:field xpath="j2ee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="messaged-resource-env-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name
+ of a resource environment reference; its value is
+ the environment entry name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:resource-env-ref"/>
+ <xsd:field xpath="j2ee:resource-env-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="messaged-message-destination-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies the name
+ of a message destination reference; its value is
+ the message destination reference name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:message-destination-ref"/>
+ <xsd:field xpath="j2ee:message-destination-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="messaged-res-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference. The name
+ is a JNDI name relative to the java:comp/env context.
+ The name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:resource-ref"/>
+ <xsd:field xpath="j2ee:res-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="messaged-env-entry-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entry-name element contains the name of a
+ component's environment entry. The name is a JNDI
+ name relative to the java:comp/env context. The
+ name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:env-entry"/>
+ <xsd:field xpath="j2ee:env-entry-name"/>
+ </xsd:unique>
+ </xsd:element>
+
+ </xsd:choice>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="entity-beanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The entity-beanType declares an entity bean. The declaration
+ consists of:
+
+ - an optional description
+ - an optional display name
+ - an optional icon element that contains a small and a large
+ icon file name
+ - a unique name assigned to the enterprise bean
+ in the deployment descriptor
+ - the names of the entity bean's remote home
+ and remote interfaces, if any
+ - the names of the entity bean's local home and local
+ interfaces, if any
+ - the entity bean's implementation class
+ - the entity bean's persistence management type
+ - the entity bean's primary key class name
+ - an indication of the entity bean's reentrancy
+ - an optional specification of the
+ entity bean's cmp-version
+ - an optional specification of the entity bean's
+ abstract schema name
+ - an optional list of container-managed fields
+ - an optional specification of the primary key
+ field
+ - an optional declaration of the bean's environment
+ entries
+ - an optional declaration of the bean's EJB
+ references
+ - an optional declaration of the bean's local
+ EJB references
+ - an optional declaration of the bean's web
+ service references
+ - an optional declaration of the security role
+ references
+ - an optional declaration of the security identity
+ to be used for the execution of the bean's methods
+ - an optional declaration of the bean's
+ resource manager connection factory references
+ - an optional declaration of the bean's
+ resource environment references
+ - an optional declaration of the bean's message
+ destination references
+ - an optional set of query declarations
+ for finder and select methods for an entity
+ bean with cmp-version 2.x.
+
+ The optional abstract-schema-name element must be specified
+ for an entity bean with container-managed persistence and
+ cmp-version 2.x.
+
+ The optional primkey-field may be present in the descriptor
+ if the entity's persistence-type is Container.
+
+ The optional cmp-version element may be present in the
+ descriptor if the entity's persistence-type is Container. If
+ the persistence-type is Container and the cmp-version
+ element is not specified, its value defaults to 2.x.
+
+ The optional home and remote elements must be specified if
+ the entity bean cmp-version is 1.x.
+
+ The optional home and remote elements must be specified if
+ the entity bean has a remote home and remote interface.
+
+ The optional local-home and local elements must be specified
+ if the entity bean has a local home and local interface.
+
+ Either both the local-home and the local elements or both
+ the home and the remote elements must be specified.
+
+ The optional query elements must be present if the
+ persistence-type is Container and the cmp-version is 2.x and
+ query methods other than findByPrimaryKey have been defined
+ for the entity bean.
+
+ The other elements that are optional are "optional" in the
+ sense that they are omitted if the lists represented by them
+ are empty.
+
+ At least one cmp-field element must be present in the
+ descriptor if the entity's persistence-type is Container and
+ the cmp-version is 1.x, and none must not be present if the
+ entity's persistence-type is Bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="ejb-name"
+ type="j2ee:ejb-nameType"/>
+ <xsd:element name="home"
+ type="j2ee:homeType"
+ minOccurs="0"/>
+ <xsd:element name="remote"
+ type="j2ee:remoteType"
+ minOccurs="0"/>
+ <xsd:element name="local-home"
+ type="j2ee:local-homeType"
+ minOccurs="0"/>
+ <xsd:element name="local"
+ type="j2ee:localType"
+ minOccurs="0"/>
+ <xsd:element name="ejb-class"
+ type="j2ee:ejb-classType"/>
+ <xsd:element name="persistence-type"
+ type="j2ee:persistence-typeType"/>
+ <xsd:element name="prim-key-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The prim-key-class element contains the
+ fully-qualified name of an
+ entity bean's primary key class.
+
+ If the definition of the primary key class is
+ deferred to deployment time, the prim-key-class
+ element should specify java.lang.Object.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="reentrant"
+ type="j2ee:true-falseType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The reentrant element specifies whether an entity
+ bean is reentrant or not.
+
+ The reentrant element must be one of the two
+ following: true or false
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="cmp-version"
+ type="j2ee:cmp-versionType"
+ minOccurs="0"/>
+ <xsd:element name="abstract-schema-name"
+ type="j2ee:java-identifierType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The abstract-schema-name element specifies the name
+ of the abstract schema type of an entity bean with
+ cmp-version 2.x. It is used in EJB QL queries.
+
+ For example, the abstract-schema-name for an entity
+ bean whose local interface is
+ com.acme.commerce.Order might be Order.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="cmp-field"
+ type="j2ee:cmp-fieldType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="primkey-field"
+ type="j2ee:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The primkey-field element is used to specify the
+ name of the primary key field for an entity with
+ container-managed persistence.
+
+ The primkey-field must be one of the fields declared
+ in the cmp-field element, and the type of the field
+ must be the same as the primary key type.
+
+ The primkey-field element is not used if the primary
+ key maps to multiple container-managed fields
+ (i.e. the key is a compound key). In this case, the
+ fields of the primary key class must be public, and
+ their names must correspond to the field names of
+ the entity bean class that comprise the key.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:group ref="j2ee:jndiEnvironmentRefsGroup"/>
+ <xsd:element name="security-role-ref"
+ type="j2ee:security-role-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="security-identity"
+ type="j2ee:security-identityType"
+ minOccurs="0"/>
+ <xsd:element name="query"
+ type="j2ee:queryType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="exclude-listType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The exclude-listType specifies one or more methods which
+ the Assembler marks to be uncallable.
+
+ If the method permission relation contains methods that are
+ in the exclude list, the Deployer should consider those
+ methods to be uncallable.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="method"
+ type="j2ee:methodType"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-driven-beanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-driven element declares a message-driven
+ bean. The declaration consists of:
+
+ - an optional description
+ - an optional display name
+ - an optional icon element that contains a small and a large
+ icon file name.
+ - a name assigned to the enterprise bean in
+ the deployment descriptor
+ - the message-driven bean's implementation class
+ - an optional declaration of the bean's messaging
+ type
+ - the message-driven bean's transaction management type
+ - an optional declaration of the bean's
+ message-destination-type
+ - an optional declaration of the bean's
+ message-destination-link
+ - an optional declaration of the message-driven bean's
+ activation configuration properties
+ - an optional declaration of the bean's environment
+ entries
+ - an optional declaration of the bean's EJB references
+ - an optional declaration of the bean's local EJB
+ references
+ - an optional declaration of the bean's web service
+ references
+ - an optional declaration of the security
+ identity to be used for the execution of the bean's
+ methods
+ - an optional declaration of the bean's
+ resource manager connection factory
+ references
+ - an optional declaration of the bean's resource
+ environment references.
+ - an optional declaration of the bean's message
+ destination references
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="ejb-name"
+ type="j2ee:ejb-nameType"/>
+ <xsd:element name="ejb-class"
+ type="j2ee:ejb-classType"/>
+ <xsd:element name="messaging-type"
+ type="j2ee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The messaging-type element specifies the message
+ listener interface of the message-driven bean. If
+ the messaging-type element is not specified, it is
+ assumed to be javax.jms.MessageListener.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="transaction-type"
+ type="j2ee:transaction-typeType"/>
+ <xsd:element name="message-destination-type"
+ type="j2ee:message-destination-typeType"
+ minOccurs="0"/>
+ <xsd:element name="message-destination-link"
+ type="j2ee:message-destination-linkType"
+ minOccurs="0"/>
+ <xsd:element name="activation-config"
+ type="j2ee:activation-configType"
+ minOccurs="0"/>
+ <xsd:group ref="j2ee:jndiEnvironmentRefsGroup"/>
+ <xsd:element name="security-identity"
+ type="j2ee:security-identityType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="method-intfType">
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-intf element allows a method element to
+ differentiate between the methods with the same name and
+ signature that are multiply defined across the home and
+ component interfaces (e.g, in both an enterprise bean's
+ remote and local interfaces or in both an enterprise bean's
+ home and remote interfaces, etc.); the component and web
+ service endpoint interfaces, and so on.
+
+ The method-intf element must be one of the following:
+
+ Home
+ Remote
+ LocalHome
+ Local
+ ServiceEndpoint
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="Home"/>
+ <xsd:enumeration value="Remote"/>
+ <xsd:enumeration value="LocalHome"/>
+ <xsd:enumeration value="Local"/>
+ <xsd:enumeration value="ServiceEndpoint"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="method-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-nameType contains a name of an enterprise
+ bean method or the asterisk (*) character. The asterisk is
+ used when the element denotes all the methods of an
+ enterprise bean's client view interfaces.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="method-paramsType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-paramsType defines a list of the
+ fully-qualified Java type names of the method parameters.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="method-param"
+ type="j2ee:java-typeType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-param element contains a primitive
+ or a fully-qualified Java type name of a method
+ parameter.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="method-permissionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-permissionType specifies that one or more
+ security roles are allowed to invoke one or more enterprise
+ bean methods. The method-permissionType consists of an
+ optional description, a list of security role names or an
+ indicator to state that the method is unchecked for
+ authorization, and a list of method elements.
+
+ The security roles used in the method-permissionType
+ must be defined in the security-role elements of the
+ deployment descriptor, and the methods must be methods
+ defined in the enterprise bean's home, component and/or web
+ service endpoint interfaces.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:choice>
+ <xsd:element name="role-name"
+ type="j2ee:role-nameType"
+ maxOccurs="unbounded"/>
+ <xsd:element name="unchecked"
+ type="j2ee:emptyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The unchecked element specifies that a method is
+ not checked for authorization by the container
+ prior to invocation of the method.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:choice>
+ <xsd:element name="method"
+ type="j2ee:methodType"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="methodType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The methodType is used to denote a method of an enterprise
+ bean's home, component, and/or web service endpoint
+ interface, or, in the case of a message-driven bean, the
+ bean's message listener method, or a set of such
+ methods. The ejb-name element must be the name of one of the
+ enterprise beans declared in the deployment descriptor; the
+ optional method-intf element allows to distinguish between a
+ method with the same signature that is multiply defined
+ across the home, component, and/or web service endpoint
+ interfaces; the method-name element specifies the method
+ name; and the optional method-params elements identify a
+ single method among multiple methods with an overloaded
+ method name.
+
+ There are three possible styles of using methodType element
+ within a method element:
+
+ 1.
+ <method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>*</method-name>
+ </method>
+
+ This style is used to refer to all the methods of the
+ specified enterprise bean's home, component, and/or web
+ service endpoint interfaces.
+
+ 2.
+ <method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>METHOD</method-name>
+ </method>
+
+ This style is used to refer to the specified method of
+ the specified enterprise bean. If there are multiple
+ methods with the same overloaded name, the element of
+ this style refers to all the methods with the overloaded
+ name.
+
+ 3.
+ <method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>METHOD</method-name>
+ <method-params>
+ <method-param>PARAM-1</method-param>
+ <method-param>PARAM-2</method-param>
+ ...
+ <method-param>PARAM-n</method-param>
+ </method-params>
+ </method>
+
+ This style is used to refer to a single method within a
+ set of methods with an overloaded name. PARAM-1 through
+ PARAM-n are the fully-qualified Java types of the
+ method's input parameters (if the method has no input
+ arguments, the method-params element contains no
+ method-param elements). Arrays are specified by the
+ array element's type, followed by one or more pair of
+ square brackets (e.g. int[][]). If there are multiple
+ methods with the same overloaded name, this style refers
+ to all of the overloaded methods.
+
+ Examples:
+
+ Style 1: The following method element refers to all the
+ methods of the EmployeeService bean's home, component,
+ and/or web service endpoint interfaces:
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>*</method-name>
+ </method>
+
+ Style 2: The following method element refers to all the
+ create methods of the EmployeeService bean's home
+ interface(s).
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>create</method-name>
+ </method>
+
+ Style 3: The following method element refers to the
+ create(String firstName, String LastName) method of the
+ EmployeeService bean's home interface(s).
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+ </method>
+
+ The following example illustrates a Style 3 element with
+ more complex parameter types. The method
+ foobar(char s, int i, int[] iar, mypackage.MyClass mycl,
+ mypackage.MyClass[][] myclaar) would be specified as:
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>foobar</method-name>
+ <method-params>
+ <method-param>char</method-param>
+ <method-param>int</method-param>
+ <method-param>int[]</method-param>
+ <method-param>mypackage.MyClass</method-param>
+ <method-param>mypackage.MyClass[][]</method-param>
+ </method-params>
+ </method>
+
+ The optional method-intf element can be used when it becomes
+ necessary to differentiate between a method that is multiply
+ defined across the enterprise bean's home, component, and/or
+ web service endpoint interfaces with the same name and
+ signature.
+
+ For example, the method element
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>Remote</method-intf>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+ </method>
+
+ can be used to differentiate the create(String, String)
+ method defined in the remote interface from the
+ create(String, String) method defined in the remote home
+ interface, which would be defined as
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>Home</method-intf>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+ </method>
+
+ and the create method that is defined in the local home
+ interface which would be defined as
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>LocalHome</method-intf>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+ </method>
+
+ The method-intf element can be used with all th ree Styles
+ of the method element usage. For example, the following
+ method element example could be used to refer to all the
+ methods of the EmployeeService bean's remote home interface.
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>Home</method-intf>
+ <method-name>*</method-name>
+ </method>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="ejb-name"
+ type="j2ee:ejb-nameType"/>
+ <xsd:element name="method-intf"
+ type="j2ee:method-intfType"
+ minOccurs="0">
+ </xsd:element>
+ <xsd:element name="method-name"
+ type="j2ee:method-nameType"/>
+ <xsd:element name="method-params"
+ type="j2ee:method-paramsType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="multiplicityType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The multiplicityType describes the multiplicity of the
+ role that participates in a relation.
+
+ The value must be one of the two following:
+
+ One
+ Many
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="One"/>
+ <xsd:enumeration value="Many"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="persistence-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The persistence-typeType specifies an entity bean's persistence
+ management type.
+
+ The persistence-type element must be one of the two following:
+
+ Bean
+ Container
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="Bean"/>
+ <xsd:enumeration value="Container"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="query-methodType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The query-method specifies the method for a finder or select
+ query.
+
+ The method-name element specifies the name of a finder or select
+ method in the entity bean's implementation class.
+
+ Each method-param must be defined for a query-method using the
+ method-params element.
+
+ It is used by the query-method element.
+
+ Example:
+
+ <query>
+ <description>Method finds large orders</description>
+ <query-method>
+ <method-name>findLargeOrders</method-name>
+ <method-params></method-params>
+ </query-method>
+ <ejb-ql>
+ SELECT OBJECT(o) FROM Order o
+ WHERE o.amount > 1000
+ </ejb-ql>
+ </query>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="method-name"
+ type="j2ee:method-nameType"/>
+ <xsd:element name="method-params"
+ type="j2ee:method-paramsType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="queryType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The queryType defines a finder or select
+ query. It contains
+ - an optional description of the query
+ - the specification of the finder or select
+ method it is used by
+ - an optional specification of the result type
+ mapping, if the query is for a select method
+ and entity objects are returned.
+ - the EJB QL query string that defines the query.
+
+ Queries that are expressible in EJB QL must use the ejb-ql
+ element to specify the query. If a query is not expressible
+ in EJB QL, the description element should be used to
+ describe the semantics of the query and the ejb-ql element
+ should be empty.
+
+ The result-type-mapping is an optional element. It can only
+ be present if the query-method specifies a select method
+ that returns entity objects. The default value for the
+ result-type-mapping element is "Local".
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType" minOccurs="0"/>
+ <xsd:element name="query-method"
+ type="j2ee:query-methodType"/>
+ <xsd:element name="result-type-mapping"
+ type="j2ee:result-type-mappingType"
+ minOccurs="0"/>
+ <xsd:element name="ejb-ql"
+ type="j2ee:xsdStringType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="relationship-role-sourceType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The relationship-role-sourceType designates the source of a
+ role that participates in a relationship. A
+ relationship-role-sourceType is used by
+ relationship-role-source elements to uniquely identify an
+ entity bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-name"
+ type="j2ee:ejb-nameType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="relationshipsType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The relationshipsType describes the relationships in
+ which entity beans with container-managed persistence
+ participate. The relationshipsType contains an optional
+ description; and a list of ejb-relation elements, which
+ specify the container managed relationships.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-relation"
+ type="j2ee:ejb-relationType"
+ maxOccurs="unbounded">
+
+ <xsd:unique name="role-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-relationship-role-name contains the name of a
+ relationship role. The name must be unique within
+ a relationship, but can be reused in different
+ relationships.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector
+ xpath=".//j2ee:ejb-relationship-role-name"/>
+ <xsd:field
+ xpath="."/>
+ </xsd:unique>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="result-type-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The result-type-mappingType is used in the query element to
+ specify whether an abstract schema type returned by a query
+ for a select method is to be mapped to an EJBLocalObject or
+ EJBObject type.
+
+ The value must be one of the following:
+
+ Local
+ Remote
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="Local"/>
+ <xsd:enumeration value="Remote"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="security-identityType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The security-identityType specifies whether the caller's
+ security identity is to be used for the execution of the
+ methods of the enterprise bean or whether a specific run-as
+ identity is to be used. It contains an optional description
+ and a specification of the security identity to be used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:choice>
+ <xsd:element name="use-caller-identity"
+ type="j2ee:emptyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The use-caller-identity element specifies that
+ the caller's security identity be used as the
+ security identity for the execution of the
+ enterprise bean's methods.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="run-as"
+ type="j2ee:run-asType"/>
+ </xsd:choice>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="session-beanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The session-beanType declares an session bean. The
+ declaration consists of:
+
+ - an optional description
+ - an optional display name
+ - an optional icon element that contains a small and a large
+ icon file name
+ - a name assigned to the enterprise bean
+ in the deployment description
+ - the names of the session bean's remote home and
+ remote interfaces, if any
+ - the names of the session bean's local home and
+ local interfaces, if any
+ - the name of the session bean's web service endpoint
+ interface, if any
+ - the session bean's implementation class
+ - the session bean's state management type
+ - the session bean's transaction management type
+ - an optional declaration of the bean's
+ environment entries
+ - an optional declaration of the bean's EJB references
+ - an optional declaration of the bean's local
+ EJB references
+ - an optional declaration of the bean's web
+ service references
+ - an optional declaration of the security role
+ references
+ - an optional declaration of the security identity
+ to be used for the execution of the bean's methods
+ - an optional declaration of the bean's resource
+ manager connection factory references
+ - an optional declaration of the bean's resource
+ environment references.
+ - an optional declaration of the bean's message
+ destination references
+
+ The elements that are optional are "optional" in the sense
+ that they are omitted when if lists represented by them are
+ empty.
+
+ Either both the local-home and the local elements or both
+ the home and the remote elements must be specified for the
+ session bean.
+
+ The service-endpoint element may only be specified if the
+ bean is a stateless session bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="ejb-name"
+ type="j2ee:ejb-nameType"/>
+ <xsd:element name="home"
+ type="j2ee:homeType"
+ minOccurs="0"/>
+ <xsd:element name="remote"
+ type="j2ee:remoteType"
+ minOccurs="0"/>
+ <xsd:element name="local-home"
+ type="j2ee:local-homeType"
+ minOccurs="0"/>
+ <xsd:element name="local"
+ type="j2ee:localType"
+ minOccurs="0"/>
+ <xsd:element name="service-endpoint"
+ type="j2ee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-endpoint element contains the
+ fully-qualified name of the enterprise bean's web
+ service endpoint interface. The service-endpoint
+ element may only be specified for a stateless
+ session bean. The specified interface must be a
+ valid JAX-RPC service endpoint interface.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="ejb-class"
+ type="j2ee:ejb-classType"/>
+ <xsd:element name="session-type"
+ type="j2ee:session-typeType"/>
+ <xsd:element name="transaction-type"
+ type="j2ee:transaction-typeType"/>
+ <xsd:group ref="j2ee:jndiEnvironmentRefsGroup"/>
+ <xsd:element name="security-role-ref"
+ type="j2ee:security-role-refType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="security-identity"
+ type="j2ee:security-identityType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="session-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The session-typeType describes whether the session bean is a
+ stateful session or stateless session. It is used by
+ session-type elements.
+
+ The value must be one of the two following:
+
+ Stateful
+ Stateless
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="Stateful"/>
+ <xsd:enumeration value="Stateless"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="trans-attributeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The trans-attributeType specifies how the container must
+ manage the transaction boundaries when delegating a method
+ invocation to an enterprise bean's business method.
+
+ The value must be one of the following:
+
+ NotSupported
+ Supports
+ Required
+ RequiresNew
+ Mandatory
+ Never
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="NotSupported"/>
+ <xsd:enumeration value="Supports"/>
+ <xsd:enumeration value="Required"/>
+ <xsd:enumeration value="RequiresNew"/>
+ <xsd:enumeration value="Mandatory"/>
+ <xsd:enumeration value="Never"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="transaction-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The transaction-typeType specifies an enterprise bean's
+ transaction management type.
+
+ The transaction-type must be one of the two following:
+
+ Bean
+ Container
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="Bean"/>
+ <xsd:enumeration value="Container"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/ejb-jar_3_0.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/ejb-jar_3_0.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/ejb-jar_3_0.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,2705 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="3.0">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)ejb-jar_3_0.xsds 1.51 02/23/06
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003-2006 Sun Microsystems, Inc.
+ 4150 Network Circle
+ Santa Clara, California 95054
+ U.S.A
+ All rights reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This is the XML Schema for the EJB 3.0 deployment descriptor.
+ The deployment descriptor must be named "META-INF/ejb-jar.xml" in
+ the EJB's jar file. All EJB deployment descriptors must indicate
+ the ejb-jar schema by using the Java EE namespace:
+
+ http://java.sun.com/xml/ns/javaee
+
+ and by indicating the version of the schema by
+ using the version element as shown below:
+
+ <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
+ http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
+ version="3.0">
+ ...
+ </ejb-jar>
+
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute for the
+ Java EE namespace with the following location:
+
+ http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all Java EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="javaee_5.xsd"/>
+
+
+<!-- **************************************************** -->
+
+ <xsd:element name="ejb-jar" type="javaee:ejb-jarType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This is the root of the ejb-jar deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:key name="ejb-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-name element contains the name of an enterprise
+ bean. The name must be unique within the ejb-jar file.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:enterprise-beans/*"/>
+ <xsd:field xpath="javaee:ejb-name"/>
+ </xsd:key>
+
+ <xsd:keyref name="ejb-name-references"
+ refer="javaee:ejb-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The keyref indicates the references from
+ relationship-role-source must be to a specific ejb-name
+ defined within the scope of enterprise-beans element.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector
+xpath=".//javaee:ejb-relationship-role/javaee:relationship-role-source"/>
+ <xsd:field
+ xpath="javaee:ejb-name"/>
+ </xsd:keyref>
+
+ <xsd:key name="role-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ A role-name-key is specified to allow the references
+ from the security-role-refs.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:assembly-descriptor/javaee:security-role"/>
+ <xsd:field xpath="javaee:role-name"/>
+ </xsd:key>
+
+ <xsd:keyref name="role-name-references"
+ refer="javaee:role-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The keyref indicates the references from
+ security-role-ref to a specified role-name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:enterprise-beans/*/javaee:security-role-ref"/>
+ <xsd:field xpath="javaee:role-link"/>
+ </xsd:keyref>
+ </xsd:element>
+
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="activation-config-propertyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The activation-config-propertyType contains a name/value
+ configuration property pair for a message-driven bean.
+
+ The properties that are recognized for a particular
+ message-driven bean are determined by the messaging type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="activation-config-property-name"
+ type="javaee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The activation-config-property-name element contains
+ the name for an activation configuration property of
+ a message-driven bean.
+
+ For JMS message-driven beans, the following property
+ names are recognized: acknowledgeMode,
+ messageSelector, destinationType, subscriptionDurability
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="activation-config-property-value"
+ type="javaee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The activation-config-property-value element
+ contains the value for an activation configuration
+ property of a message-driven bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="activation-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The activation-configType defines information about the
+ expected configuration properties of the message-driven bean
+ in its operational environment. This may include information
+ about message acknowledgement, message selector, expected
+ destination type, etc.
+
+ The configuration information is expressed in terms of
+ name/value configuration properties.
+
+ The properties that are recognized for a particular
+ message-driven bean are determined by the messaging type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="activation-config-property"
+ type="javaee:activation-config-propertyType"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="application-exceptionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The application-exceptionType declares an application
+ exception. The declaration consists of:
+
+ - the exception class. When the container receives
+ an exception of this type, it is required to
+ forward this exception as an applcation exception
+ to the client regardless of whether it is a checked
+ or unchecked exception.
+ - an optional rollback element. If this element is
+ set to true, the container must rollback the current
+ transaction before forwarding the exception to the
+ client. If not specified, it defaults to false.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="exception-class"
+ type="javaee:fully-qualified-classType"/>
+ <xsd:element name="rollback"
+ type="javaee:true-falseType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="around-invokeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The around-invoke type specifies a method on a
+ class to be called during the around invoke portion of an
+ ejb invocation. Note that each class may have only one
+ around invoke method and that the method may not be
+ overloaded.
+
+ If the class element is missing then
+ the class defining the callback is assumed to be the
+ interceptor class or component class in scope at the
+ location in the descriptor in which the around invoke
+ definition appears.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="class"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0"/>
+ <xsd:element name="method-name"
+ type="javaee:java-identifierType"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="assembly-descriptorType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The assembly-descriptorType defines
+ application-assembly information.
+
+ The application-assembly information consists of the
+ following parts: the definition of security roles, the
+ definition of method permissions, the definition of
+ transaction attributes for enterprise beans with
+ container-managed transaction demarcation, the definition
+ of interceptor bindings, a list of
+ methods to be excluded from being invoked, and a list of
+ exception types that should be treated as application exceptions.
+
+ All the parts are optional in the sense that they are
+ omitted if the lists represented by them are empty.
+
+ Providing an assembly-descriptor in the deployment
+ descriptor is optional for the ejb-jar file producer.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="security-role"
+ type="javaee:security-roleType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="method-permission"
+ type="javaee:method-permissionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="container-transaction"
+ type="javaee:container-transactionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="interceptor-binding"
+ type="javaee:interceptor-bindingType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="message-destination"
+ type="javaee:message-destinationType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="exclude-list"
+ type="javaee:exclude-listType"
+ minOccurs="0"/>
+ <xsd:element name="application-exception"
+ type="javaee:application-exceptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="cmp-fieldType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cmp-fieldType describes a container-managed field. The
+ cmp-fieldType contains an optional description of the field,
+ and the name of the field.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="field-name"
+ type="javaee:java-identifierType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The field-name element specifies the name of a
+ container managed field.
+
+ The name of the cmp-field of an entity bean with
+ cmp-version 2.x must begin with a lowercase
+ letter. This field is accessed by methods whose
+ names consists of the name of the field specified by
+ field-name in which the first letter is uppercased,
+ prefixed by "get" or "set".
+
+ The name of the cmp-field of an entity bean with
+ cmp-version 1.x must denote a public field of the
+ enterprise bean class or one of its superclasses.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="cmp-versionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cmp-versionType specifies the version of an entity bean
+ with container-managed persistence. It is used by
+ cmp-version elements.
+
+ The value must be one of the two following:
+
+ 1.x
+ 2.x
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="1.x"/>
+ <xsd:enumeration value="2.x"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="cmr-field-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cmr-field-type element specifies the class of a
+ collection-valued logical relationship field in the entity
+ bean class. The value of an element using cmr-field-typeType
+ must be either: java.util.Collection or java.util.Set.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="java.util.Collection"/>
+ <xsd:enumeration value="java.util.Set"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="cmr-fieldType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cmr-fieldType describes the bean provider's view of
+ a relationship. It consists of an optional description, and
+ the name and the class type of a field in the source of a
+ role of a relationship. The cmr-field-name element
+ corresponds to the name used for the get and set accessor
+ methods for the relationship. The cmr-field-type element is
+ used only for collection-valued cmr-fields. It specifies the
+ type of the collection that is used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="cmr-field-name"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cmr-field-name element specifies the name of a
+ logical relationship field in the entity bean
+ class. The name of the cmr-field must begin with a
+ lowercase letter. This field is accessed by methods
+ whose names consist of the name of the field
+ specified by cmr-field-name in which the first
+ letter is uppercased, prefixed by "get" or "set".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="cmr-field-type"
+ type="javaee:cmr-field-typeType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="container-transactionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The container-transactionType specifies how the container
+ must manage transaction scopes for the enterprise bean's
+ method invocations. It defines an optional description, a
+ list of method elements, and a transaction attribute. The
+ transaction attribute is to be applied to all the specified
+ methods.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="method"
+ type="javaee:methodType"
+ maxOccurs="unbounded"/>
+ <xsd:element name="trans-attribute"
+ type="javaee:trans-attributeType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The ejb-classType contains the fully-qualified name of the
+ enterprise bean's class. It is used by ejb-class elements.
+
+ Example:
+
+ <ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-jarType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-jarType defines the root element of the EJB
+ deployment descriptor. It contains
+
+ - an optional description of the ejb-jar file
+ - an optional display name
+ - an optional icon that contains a small and a large
+ icon file name
+ - structural information about all included
+ enterprise beans that is not specified through
+ annotations
+ - structural information about interceptor classes
+ - a descriptor for container managed relationships,
+ if any.
+ - an optional application-assembly descriptor
+ - an optional name of an ejb-client-jar file for the
+ ejb-jar.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="enterprise-beans"
+ type="javaee:enterprise-beansType"
+ minOccurs="0"/>
+ <xsd:element name="interceptors"
+ type="javaee:interceptorsType"
+ minOccurs="0"/>
+ <xsd:element name="relationships"
+ type="javaee:relationshipsType"
+ minOccurs="0">
+ <xsd:unique name="relationship-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-relation-name contains the name of a
+ relation. The name must be unique within
+ relationships.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:ejb-relation"/>
+ <xsd:field xpath="javaee:ejb-relation-name"/>
+ </xsd:unique>
+ </xsd:element>
+ <xsd:element name="assembly-descriptor"
+ type="javaee:assembly-descriptorType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Providing an assembly-descriptor in the deployment
+ descriptor is optional for the ejb-jar file
+ producer.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="ejb-client-jar"
+ type="javaee:pathType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The optional ejb-client-jar element specifies a JAR
+ file that contains the class files necessary for a
+ client program to access the
+ enterprise beans in the ejb-jar file.
+
+ Example:
+
+ <ejb-client-jar>employee_service_client.jar
+ </ejb-client-jar>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="version"
+ type="javaee:dewey-versionType"
+ fixed="3.0"
+ use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The version specifies the version of the
+ EJB specification that the instance document must
+ comply with. This information enables deployment tools
+ to validate a particular EJB Deployment
+ Descriptor with respect to a specific version of the EJB
+ schema.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+ <xsd:attribute name="metadata-complete" type="xsd:boolean">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The metadata-complete attribute defines whether this
+ deployment descriptor and other related deployment
+ descriptors for this module (e.g., web service
+ descriptors) are complete, or whether the class
+ files available to this module and packaged with
+ this application should be examined for annotations
+ that specify deployment information.
+
+ If metadata-complete is set to "true", the deployment
+ tool must ignore any annotations that specify deployment
+ information, which might be present in the class files
+ of the application.
+
+ If metadata-complete is not specified or is set to
+ "false", the deployment tool must examine the class
+ files of the application for annotations, as
+ specified by the specifications.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:attribute>
+
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The ejb-nameType specifies an enterprise bean's name. It is
+ used by ejb-name elements. This name is assigned by the
+ ejb-jar file producer to name the enterprise bean in the
+ ejb-jar file's deployment descriptor. The name must be
+ unique among the names of the enterprise beans in the same
+ ejb-jar file.
+
+ There is no architected relationship between the used
+ ejb-name in the deployment descriptor and the JNDI name that
+ the Deployer will assign to the enterprise bean's home.
+
+ The name for an entity bean must conform to the lexical
+ rules for an NMTOKEN.
+
+ Example:
+
+ <ejb-name>EmployeeService</ejb-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:xsdNMTOKENType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-relationType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-relationType describes a relationship between two
+ entity beans with container-managed persistence. It is used
+ by ejb-relation elements. It contains a description; an
+ optional ejb-relation-name element; and exactly two
+ relationship role declarations, defined by the
+ ejb-relationship-role elements. The name of the
+ relationship, if specified, is unique within the ejb-jar
+ file.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-relation-name"
+ type="javaee:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-relation-name element provides a unique name
+ within the ejb-jar file for a relationship.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="ejb-relationship-role"
+ type="javaee:ejb-relationship-roleType"/>
+ <xsd:element name="ejb-relationship-role"
+ type="javaee:ejb-relationship-roleType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-relationship-roleType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The ejb-relationship-roleType describes a role within a
+ relationship. There are two roles in each relationship.
+
+ The ejb-relationship-roleType contains an optional
+ description; an optional name for the relationship role; a
+ specification of the multiplicity of the role; an optional
+ specification of cascade-delete functionality for the role;
+ the role source; and a declaration of the cmr-field, if any,
+ by means of which the other side of the relationship is
+ accessed from the perspective of the role source.
+
+ The multiplicity and role-source element are mandatory.
+
+ The relationship-role-source element designates an entity
+ bean by means of an ejb-name element. For bidirectional
+ relationships, both roles of a relationship must declare a
+ relationship-role-source element that specifies a cmr-field
+ in terms of which the relationship is accessed. The lack of
+ a cmr-field element in an ejb-relationship-role specifies
+ that the relationship is unidirectional in navigability and
+ the entity bean that participates in the relationship is
+ "not aware" of the relationship.
+
+ Example:
+
+ <ejb-relation>
+ <ejb-relation-name>Product-LineItem</ejb-relation-name>
+ <ejb-relationship-role>
+ <ejb-relationship-role-name>product-has-lineitems
+ </ejb-relationship-role-name>
+ <multiplicity>One</multiplicity>
+ <relationship-role-source>
+ <ejb-name>ProductEJB</ejb-name>
+ </relationship-role-source>
+ </ejb-relationship-role>
+ </ejb-relation>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-relationship-role-name"
+ type="javaee:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-relationship-role-name element defines a
+ name for a role that is unique within an
+ ejb-relation. Different relationships can use the
+ same name for a role.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="multiplicity"
+ type="javaee:multiplicityType"/>
+ <xsd:element name="cascade-delete"
+ type="javaee:emptyType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The cascade-delete element specifies that, within a
+ particular relationship, the lifetime of one or more
+ entity beans is dependent upon the lifetime of
+ another entity bean. The cascade-delete element can
+ only be specified for an ejb-relationship-role
+ element contained in an ejb-relation element in
+ which the other ejb-relationship-role
+ element specifies a multiplicity of One.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="relationship-role-source"
+ type="javaee:relationship-role-sourceType"/>
+ <xsd:element name="cmr-field"
+ type="javaee:cmr-fieldType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="enterprise-beansType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The enterprise-beansType declares one or more enterprise
+ beans. Each bean can be a session, entity or message-driven
+ bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:choice maxOccurs="unbounded">
+ <xsd:element name="session"
+ type="javaee:session-beanType">
+ <xsd:unique name="session-ejb-local-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of
+ an EJB reference. The EJB reference is an entry in
+ the component's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the component.
+
+ It is recommended that name be prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:ejb-local-ref"/>
+ <xsd:field xpath="javaee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="session-ejb-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the
+ component's environment and is relative to the
+ java:comp/env context. The name must be unique
+ within the component.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:ejb-ref"/>
+ <xsd:field xpath="javaee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="session-resource-env-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name
+ of a resource environment reference; its value is
+ the environment entry name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:resource-env-ref"/>
+ <xsd:field xpath="javaee:resource-env-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="session-message-destination-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies the name
+ of a message destination reference; its value is
+ the message destination reference name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:message-destination-ref"/>
+ <xsd:field xpath="javaee:message-destination-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="session-res-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference. The name
+ is a JNDI name relative to the java:comp/env context.
+ The name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:resource-ref"/>
+ <xsd:field xpath="javaee:res-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="session-env-entry-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entry-name element contains the name of a
+ component's environment entry. The name is a JNDI
+ name relative to the java:comp/env context. The
+ name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:env-entry"/>
+ <xsd:field xpath="javaee:env-entry-name"/>
+ </xsd:unique>
+ </xsd:element>
+
+ <xsd:element name="entity"
+ type="javaee:entity-beanType">
+ <xsd:unique name="entity-ejb-local-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of
+ an EJB reference. The EJB reference is an entry in
+ the component's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the component.
+
+ It is recommended that name be prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:ejb-local-ref"/>
+ <xsd:field xpath="javaee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="entity-ejb-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the
+ component's environment and is relative to the
+ java:comp/env context. The name must be unique
+ within the component.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:ejb-ref"/>
+ <xsd:field xpath="javaee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="entity-resource-env-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name
+ of a resource environment reference; its value is
+ the environment entry name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:resource-env-ref"/>
+ <xsd:field xpath="javaee:resource-env-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="entity-message-destination-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies the name
+ of a message destination reference; its value is
+ the message destination reference name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:message-destination-ref"/>
+ <xsd:field xpath="javaee:message-destination-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="entity-res-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference. The name
+ is a JNDI name relative to the java:comp/env context.
+ The name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:resource-ref"/>
+ <xsd:field xpath="javaee:res-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="entity-env-entry-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entry-name element contains the name of a
+ component's environment entry. The name is a JNDI
+ name relative to the java:comp/env context. The
+ name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:env-entry"/>
+ <xsd:field xpath="javaee:env-entry-name"/>
+ </xsd:unique>
+ </xsd:element>
+
+ <xsd:element name="message-driven"
+ type="javaee:message-driven-beanType">
+ <xsd:unique name="messaged-ejb-local-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of
+ an EJB reference. The EJB reference is an entry in
+ the component's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the component.
+
+ It is recommended that name be prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:ejb-local-ref"/>
+ <xsd:field xpath="javaee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="messaged-ejb-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the
+ component's environment and is relative to the
+ java:comp/env context. The name must be unique
+ within the component.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:ejb-ref"/>
+ <xsd:field xpath="javaee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="messaged-resource-env-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name
+ of a resource environment reference; its value is
+ the environment entry name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:resource-env-ref"/>
+ <xsd:field xpath="javaee:resource-env-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="messaged-message-destination-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies the name
+ of a message destination reference; its value is
+ the message destination reference name used in the component
+ code. The name is a JNDI name relative to the
+ java:comp/env context and must be unique within an
+ component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:message-destination-ref"/>
+ <xsd:field xpath="javaee:message-destination-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="messaged-res-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference. The name
+ is a JNDI name relative to the java:comp/env context.
+ The name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:resource-ref"/>
+ <xsd:field xpath="javaee:res-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="messaged-env-entry-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entry-name element contains the name of a
+ component's environment entry. The name is a JNDI
+ name relative to the java:comp/env context. The
+ name must be unique within an component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:env-entry"/>
+ <xsd:field xpath="javaee:env-entry-name"/>
+ </xsd:unique>
+ </xsd:element>
+
+ </xsd:choice>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="entity-beanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The entity-beanType declares an entity bean. The declaration
+ consists of:
+
+ - an optional description
+ - an optional display name
+ - an optional icon element that contains a small and a large
+ icon file name
+ - a unique name assigned to the enterprise bean
+ in the deployment descriptor
+ - an optional mapped-name element that can be used to provide
+ vendor-specific deployment information such as the physical
+ jndi-name of the entity bean's remote home interface. This
+ element is not required to be supported by all implementations.
+ Any use of this element is non-portable.
+ - the names of the entity bean's remote home
+ and remote interfaces, if any
+ - the names of the entity bean's local home and local
+ interfaces, if any
+ - the entity bean's implementation class
+ - the optional entity bean's persistence management type. If
+ this element is not specified it is defaulted to Container.
+ - the entity bean's primary key class name
+ - an indication of the entity bean's reentrancy
+ - an optional specification of the
+ entity bean's cmp-version
+ - an optional specification of the entity bean's
+ abstract schema name
+ - an optional list of container-managed fields
+ - an optional specification of the primary key
+ field
+ - an optional declaration of the bean's environment
+ entries
+ - an optional declaration of the bean's EJB
+ references
+ - an optional declaration of the bean's local
+ EJB references
+ - an optional declaration of the bean's web
+ service references
+ - an optional declaration of the security role
+ references
+ - an optional declaration of the security identity
+ to be used for the execution of the bean's methods
+ - an optional declaration of the bean's
+ resource manager connection factory references
+ - an optional declaration of the bean's
+ resource environment references
+ - an optional declaration of the bean's message
+ destination references
+ - an optional set of query declarations
+ for finder and select methods for an entity
+ bean with cmp-version 2.x.
+
+ The optional abstract-schema-name element must be specified
+ for an entity bean with container-managed persistence and
+ cmp-version 2.x.
+
+ The optional primkey-field may be present in the descriptor
+ if the entity's persistence-type is Container.
+
+ The optional cmp-version element may be present in the
+ descriptor if the entity's persistence-type is Container. If
+ the persistence-type is Container and the cmp-version
+ element is not specified, its value defaults to 2.x.
+
+ The optional home and remote elements must be specified if
+ the entity bean cmp-version is 1.x.
+
+ The optional home and remote elements must be specified if
+ the entity bean has a remote home and remote interface.
+
+ The optional local-home and local elements must be specified
+ if the entity bean has a local home and local interface.
+
+ Either both the local-home and the local elements or both
+ the home and the remote elements must be specified.
+
+ The optional query elements must be present if the
+ persistence-type is Container and the cmp-version is 2.x and
+ query methods other than findByPrimaryKey have been defined
+ for the entity bean.
+
+ The other elements that are optional are "optional" in the
+ sense that they are omitted if the lists represented by them
+ are empty.
+
+ At least one cmp-field element must be present in the
+ descriptor if the entity's persistence-type is Container and
+ the cmp-version is 1.x, and none must not be present if the
+ entity's persistence-type is Bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="ejb-name"
+ type="javaee:ejb-nameType"/>
+ <xsd:element name="mapped-name"
+ type="javaee:xsdStringType"
+ minOccurs="0"/>
+ <xsd:element name="home"
+ type="javaee:homeType"
+ minOccurs="0"/>
+ <xsd:element name="remote"
+ type="javaee:remoteType"
+ minOccurs="0"/>
+ <xsd:element name="local-home"
+ type="javaee:local-homeType"
+ minOccurs="0"/>
+ <xsd:element name="local"
+ type="javaee:localType"
+ minOccurs="0"/>
+ <xsd:element name="ejb-class"
+ type="javaee:ejb-classType"/>
+ <xsd:element name="persistence-type"
+ type="javaee:persistence-typeType"/>
+ <xsd:element name="prim-key-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The prim-key-class element contains the
+ fully-qualified name of an
+ entity bean's primary key class.
+
+ If the definition of the primary key class is
+ deferred to deployment time, the prim-key-class
+ element should specify java.lang.Object.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="reentrant"
+ type="javaee:true-falseType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The reentrant element specifies whether an entity
+ bean is reentrant or not.
+
+ The reentrant element must be one of the two
+ following: true or false
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="cmp-version"
+ type="javaee:cmp-versionType"
+ minOccurs="0"/>
+ <xsd:element name="abstract-schema-name"
+ type="javaee:java-identifierType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The abstract-schema-name element specifies the name
+ of the abstract schema type of an entity bean with
+ cmp-version 2.x. It is used in EJB QL queries.
+
+ For example, the abstract-schema-name for an entity
+ bean whose local interface is
+ com.acme.commerce.Order might be Order.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="cmp-field"
+ type="javaee:cmp-fieldType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="primkey-field"
+ type="javaee:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The primkey-field element is used to specify the
+ name of the primary key field for an entity with
+ container-managed persistence.
+
+ The primkey-field must be one of the fields declared
+ in the cmp-field element, and the type of the field
+ must be the same as the primary key type.
+
+ The primkey-field element is not used if the primary
+ key maps to multiple container-managed fields
+ (i.e. the key is a compound key). In this case, the
+ fields of the primary key class must be public, and
+ their names must correspond to the field names of
+ the entity bean class that comprise the key.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
+ <xsd:element name="security-role-ref"
+ type="javaee:security-role-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="security-identity"
+ type="javaee:security-identityType"
+ minOccurs="0"/>
+ <xsd:element name="query"
+ type="javaee:queryType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="exclude-listType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The exclude-listType specifies one or more methods which
+ the Assembler marks to be uncallable.
+
+ If the method permission relation contains methods that are
+ in the exclude list, the Deployer should consider those
+ methods to be uncallable.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="method"
+ type="javaee:methodType"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="init-methodType">
+ <xsd:sequence>
+ <xsd:element name="create-method"
+ type="javaee:named-methodType"/>
+ <xsd:element name="bean-method"
+ type="javaee:named-methodType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="interceptor-bindingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The interceptor-bindingType element describes the binding of
+ interceptor classes to beans within the ejb-jar.
+ It consists of :
+
+ - An optional description.
+ - The name of an ejb within the ejb-jar or the wildcard value "*",
+ which is used to define interceptors that are bound to all
+ beans in the ejb-jar.
+ - A list of interceptor classes that are bound to the contents of
+ the ejb-name element or a specification of the total ordering
+ over the interceptors defined for the given level and above.
+ - An optional exclude-default-interceptors element. If set to true,
+ specifies that default interceptors are not to be applied to
+ a bean-class and/or business method.
+ - An optional exclude-class-interceptors element. If set to true,
+ specifies that class interceptors are not to be applied to
+ a business method.
+ - An optional set of method elements for describing the name/params
+ of a method-level interceptor.
+
+ Interceptors bound to all classes using the wildcard syntax
+ "*" are default interceptors for the components in the ejb-jar.
+ In addition, interceptors may be bound at the level of the bean
+ class (class-level interceptors) or business methods (method-level
+ interceptors ).
+
+ The binding of interceptors to classes is additive. If interceptors
+ are bound at the class-level and/or default-level as well as the
+ method-level, both class-level and/or default-level as well as
+ method-level will apply.
+
+ There are four possible styles of the interceptor element syntax :
+
+ 1.
+ <interceptor-binding>
+ <ejb-name>*</ejb-name>
+ <interceptor-class>INTERCEPTOR</interceptor-class>
+ </interceptor-binding>
+
+ Specifying the ejb-name as the wildcard value "*" designates
+ default interceptors (interceptors that apply to all session and
+ message-driven beans contained in the ejb-jar).
+
+ 2.
+ <interceptor-binding>
+ <ejb-name>EJBNAME</ejb-name>
+ <interceptor-class>INTERCEPTOR</interceptor-class>
+ </interceptor-binding>
+
+ This style is used to refer to interceptors associated with the
+ specified enterprise bean(class-level interceptors).
+
+ 3.
+ <interceptor-binding>
+ <ejb-name>EJBNAME</ejb-name>
+ <interceptor-class>INTERCEPTOR</interceptor-class>
+ <method>
+ <method-name>METHOD</method-name>
+ </method>
+ </interceptor-binding>
+
+ This style is used to associate a method-level interceptor with
+ the specified enterprise bean. If there are multiple methods
+ with the same overloaded name, the element of this style refers
+ to all the methods with the overloaded name. Method-level
+ interceptors can only be associated with business methods of the
+ bean class. Note that the wildcard value "*" cannot be used
+ to specify method-level interceptors.
+
+ 4.
+ <interceptor-binding>
+ <ejb-name>EJBNAME</ejb-name>
+ <interceptor-class>INTERCEPTOR</interceptor-class>
+ <method>
+ <method-name>METHOD</method-name>
+ <method-params>
+ <method-param>PARAM-1</method-param>
+ <method-param>PARAM-2</method-param>
+ ...
+ <method-param>PARAM-N</method-param>
+ </method-params>
+ </method>
+ </interceptor-binding>
+
+ This style is used to associate a method-level interceptor with
+ the specified method of the specified enterprise bean. This
+ style is used to refer to a single method within a set of methods
+ with an overloaded name. The values PARAM-1 through PARAM-N
+ are the fully-qualified Java types of the method's input parameters
+ (if the method has no input arguments, the method-params element
+ contains no method-param elements). Arrays are specified by the
+ array element's type, followed by one or more pair of square
+ brackets (e.g. int[][]).
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-name"
+ type="javaee:string"/>
+ <xsd:choice>
+ <xsd:element name="interceptor-class"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="interceptor-order"
+ type="javaee:interceptor-orderType"
+ minOccurs="1"/>
+ </xsd:choice>
+ <xsd:element name="exclude-default-interceptors"
+ type="javaee:true-falseType"
+ minOccurs="0"/>
+ <xsd:element name="exclude-class-interceptors"
+ type="javaee:true-falseType"
+ minOccurs="0"/>
+ <xsd:element name="method"
+ type="javaee:named-methodType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="interceptor-orderType">
+ <xsd:annotation>
+ <xsd:documentation>
+ The interceptor-orderType element describes a total ordering
+ of interceptor classes.
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+
+ <xsd:element name="interceptor-class"
+ type="javaee:fully-qualified-classType"
+ minOccurs="1"
+ maxOccurs="unbounded"/>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="interceptorType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The interceptorType element declares information about a single
+ interceptor class. It consists of :
+
+ - An optional description.
+ - The fully-qualified name of the interceptor class.
+ - An optional list of around invoke methods declared on the
+ interceptor class and/or its super-classes.
+ - An optional list environment dependencies for the interceptor
+ class and/or its super-classes.
+ - An optional list of post-activate methods declared on the
+ interceptor class and/or its super-classes.
+ - An optional list of pre-passivate methods declared on the
+ interceptor class and/or its super-classes.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="interceptor-class"
+ type="javaee:fully-qualified-classType"/>
+ <xsd:element name="around-invoke"
+ type="javaee:around-invokeType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
+ <xsd:element name="post-activate"
+ type="javaee:lifecycle-callbackType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="pre-passivate"
+ type="javaee:lifecycle-callbackType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="interceptorsType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The interceptorsType element declares one or more interceptor
+ classes used by components within this ejb-jar. The declaration
+ consists of :
+
+ - An optional description.
+ - One or more interceptor elements.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="interceptor"
+ type="javaee:interceptorType"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-driven-beanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-driven element declares a message-driven
+ bean. The declaration consists of:
+
+ - an optional description
+ - an optional display name
+ - an optional icon element that contains a small and a large
+ icon file name.
+ - a name assigned to the enterprise bean in
+ the deployment descriptor
+ - an optional mapped-name element that can be used to provide
+ vendor-specific deployment information such as the physical
+ jndi-name of destination from which this message-driven bean
+ should consume. This element is not required to be supported
+ by all implementations. Any use of this element is non-portable.
+ - the message-driven bean's implementation class
+ - an optional declaration of the bean's messaging
+ type
+ - an optional declaration of the bean's timeout method.
+ - the optional message-driven bean's transaction management
+ type. If it is not defined, it is defaulted to Container.
+ - an optional declaration of the bean's
+ message-destination-type
+ - an optional declaration of the bean's
+ message-destination-link
+ - an optional declaration of the message-driven bean's
+ activation configuration properties
+ - an optional list of the message-driven bean class and/or
+ superclass around-invoke methods.
+ - an optional declaration of the bean's environment
+ entries
+ - an optional declaration of the bean's EJB references
+ - an optional declaration of the bean's local EJB
+ references
+ - an optional declaration of the bean's web service
+ references
+ - an optional declaration of the security
+ identity to be used for the execution of the bean's
+ methods
+ - an optional declaration of the bean's
+ resource manager connection factory
+ references
+ - an optional declaration of the bean's resource
+ environment references.
+ - an optional declaration of the bean's message
+ destination references
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="ejb-name"
+ type="javaee:ejb-nameType"/>
+ <xsd:element name="mapped-name"
+ type="javaee:xsdStringType"
+ minOccurs="0"/>
+ <xsd:element name="ejb-class"
+ type="javaee:ejb-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-class element specifies the fully qualified name
+ of the bean class for this ejb. It is required unless
+ there is a component-defining annotation for the same
+ ejb-name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="messaging-type"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The messaging-type element specifies the message
+ listener interface of the message-driven bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="timeout-method"
+ type="javaee:named-methodType"
+ minOccurs="0"/>
+ <xsd:element name="transaction-type"
+ type="javaee:transaction-typeType"
+ minOccurs="0"/>
+ <xsd:element name="message-destination-type"
+ type="javaee:message-destination-typeType"
+ minOccurs="0"/>
+ <xsd:element name="message-destination-link"
+ type="javaee:message-destination-linkType"
+ minOccurs="0"/>
+ <xsd:element name="activation-config"
+ type="javaee:activation-configType"
+ minOccurs="0"/>
+ <xsd:element name="around-invoke"
+ type="javaee:around-invokeType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
+ <xsd:element name="security-identity"
+ type="javaee:security-identityType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="method-intfType">
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-intf element allows a method element to
+ differentiate between the methods with the same name and
+ signature that are multiply defined across the home and
+ component interfaces (e.g, in both an enterprise bean's
+ remote and local interfaces or in both an enterprise bean's
+ home and remote interfaces, etc.); the component and web
+ service endpoint interfaces, and so on. The Local applies to
+ both local component interface and local business interface.
+ Similarly, Remote applies to both remote component interface
+ and the remote business interface.
+
+ The method-intf element must be one of the following:
+
+ Home
+ Remote
+ LocalHome
+ Local
+ ServiceEndpoint
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="Home"/>
+ <xsd:enumeration value="Remote"/>
+ <xsd:enumeration value="LocalHome"/>
+ <xsd:enumeration value="Local"/>
+ <xsd:enumeration value="ServiceEndpoint"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="method-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-nameType contains a name of an enterprise
+ bean method or the asterisk (*) character. The asterisk is
+ used when the element denotes all the methods of an
+ enterprise bean's client view interfaces.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="method-paramsType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-paramsType defines a list of the
+ fully-qualified Java type names of the method parameters.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="method-param"
+ type="javaee:java-typeType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-param element contains a primitive
+ or a fully-qualified Java type name of a method
+ parameter.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="method-permissionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-permissionType specifies that one or more
+ security roles are allowed to invoke one or more enterprise
+ bean methods. The method-permissionType consists of an
+ optional description, a list of security role names or an
+ indicator to state that the method is unchecked for
+ authorization, and a list of method elements.
+
+ The security roles used in the method-permissionType
+ must be defined in the security-role elements of the
+ deployment descriptor, and the methods must be methods
+ defined in the enterprise bean's business, home, component
+ and/or web service endpoint interfaces.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:choice>
+ <xsd:element name="role-name"
+ type="javaee:role-nameType"
+ maxOccurs="unbounded"/>
+ <xsd:element name="unchecked"
+ type="javaee:emptyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The unchecked element specifies that a method is
+ not checked for authorization by the container
+ prior to invocation of the method.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:choice>
+ <xsd:element name="method"
+ type="javaee:methodType"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="methodType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The methodType is used to denote a method of an enterprise
+ bean's business, home, component, and/or web service endpoint
+ interface, or, in the case of a message-driven bean, the
+ bean's message listener method, or a set of such
+ methods. The ejb-name element must be the name of one of the
+ enterprise beans declared in the deployment descriptor; the
+ optional method-intf element allows to distinguish between a
+ method with the same signature that is multiply defined
+ across the business, home, component, and/or web service
+ endpoint nterfaces; the method-name element specifies the
+ method name; and the optional method-params elements identify
+ a single method among multiple methods with an overloaded
+ method name.
+
+ There are three possible styles of using methodType element
+ within a method element:
+
+ 1.
+ <method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>*</method-name>
+ </method>
+
+ This style is used to refer to all the methods of the
+ specified enterprise bean's business, home, component,
+ and/or web service endpoint interfaces.
+
+ 2.
+ <method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>METHOD</method-name>
+ </method>
+
+ This style is used to refer to the specified method of
+ the specified enterprise bean. If there are multiple
+ methods with the same overloaded name, the element of
+ this style refers to all the methods with the overloaded
+ name.
+
+ 3.
+ <method>
+ <ejb-name>EJBNAME</ejb-name>
+ <method-name>METHOD</method-name>
+ <method-params>
+ <method-param>PARAM-1</method-param>
+ <method-param>PARAM-2</method-param>
+ ...
+ <method-param>PARAM-n</method-param>
+ </method-params>
+ </method>
+
+ This style is used to refer to a single method within a
+ set of methods with an overloaded name. PARAM-1 through
+ PARAM-n are the fully-qualified Java types of the
+ method's input parameters (if the method has no input
+ arguments, the method-params element contains no
+ method-param elements). Arrays are specified by the
+ array element's type, followed by one or more pair of
+ square brackets (e.g. int[][]). If there are multiple
+ methods with the same overloaded name, this style refers
+ to all of the overloaded methods.
+
+ Examples:
+
+ Style 1: The following method element refers to all the
+ methods of the EmployeeService bean's business, home,
+ component, and/or web service endpoint interfaces:
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>*</method-name>
+ </method>
+
+ Style 2: The following method element refers to all the
+ create methods of the EmployeeService bean's home
+ interface(s).
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>create</method-name>
+ </method>
+
+ Style 3: The following method element refers to the
+ create(String firstName, String LastName) method of the
+ EmployeeService bean's home interface(s).
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+ </method>
+
+ The following example illustrates a Style 3 element with
+ more complex parameter types. The method
+ foobar(char s, int i, int[] iar, mypackage.MyClass mycl,
+ mypackage.MyClass[][] myclaar) would be specified as:
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-name>foobar</method-name>
+ <method-params>
+ <method-param>char</method-param>
+ <method-param>int</method-param>
+ <method-param>int[]</method-param>
+ <method-param>mypackage.MyClass</method-param>
+ <method-param>mypackage.MyClass[][]</method-param>
+ </method-params>
+ </method>
+
+ The optional method-intf element can be used when it becomes
+ necessary to differentiate between a method that is multiply
+ defined across the enterprise bean's business, home, component,
+ and/or web service endpoint interfaces with the same name and
+ signature. However, if the same method is a method of both the
+ local business interface, and the local component interface,
+ the same attribute applies to the method for both interfaces.
+ Likewise, if the same method is a method of both the remote
+ business interface and the remote component interface, the same
+ attribute applies to the method for both interfaces.
+
+ For example, the method element
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>Remote</method-intf>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+ </method>
+
+ can be used to differentiate the create(String, String)
+ method defined in the remote interface from the
+ create(String, String) method defined in the remote home
+ interface, which would be defined as
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>Home</method-intf>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+ </method>
+
+ and the create method that is defined in the local home
+ interface which would be defined as
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>LocalHome</method-intf>
+ <method-name>create</method-name>
+ <method-params>
+ <method-param>java.lang.String</method-param>
+ <method-param>java.lang.String</method-param>
+ </method-params>
+ </method>
+
+ The method-intf element can be used with all three Styles
+ of the method element usage. For example, the following
+ method element example could be used to refer to all the
+ methods of the EmployeeService bean's remote home interface
+ and the remote business interface.
+
+ <method>
+ <ejb-name>EmployeeService</ejb-name>
+ <method-intf>Home</method-intf>
+ <method-name>*</method-name>
+ </method>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="ejb-name"
+ type="javaee:ejb-nameType"/>
+ <xsd:element name="method-intf"
+ type="javaee:method-intfType"
+ minOccurs="0">
+ </xsd:element>
+ <xsd:element name="method-name"
+ type="javaee:method-nameType"/>
+ <xsd:element name="method-params"
+ type="javaee:method-paramsType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="multiplicityType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The multiplicityType describes the multiplicity of the
+ role that participates in a relation.
+
+ The value must be one of the two following:
+
+ One
+ Many
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="One"/>
+ <xsd:enumeration value="Many"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="named-methodType">
+ <xsd:sequence>
+ <xsd:element name="method-name"
+ type="javaee:string"/>
+ <xsd:element name="method-params"
+ type="javaee:method-paramsType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="persistence-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The persistence-typeType specifies an entity bean's persistence
+ management type.
+
+ The persistence-type element must be one of the two following:
+
+ Bean
+ Container
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="Bean"/>
+ <xsd:enumeration value="Container"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="query-methodType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The query-method specifies the method for a finder or select
+ query.
+
+ The method-name element specifies the name of a finder or select
+ method in the entity bean's implementation class.
+
+ Each method-param must be defined for a query-method using the
+ method-params element.
+
+ It is used by the query-method element.
+
+ Example:
+
+ <query>
+ <description>Method finds large orders</description>
+ <query-method>
+ <method-name>findLargeOrders</method-name>
+ <method-params></method-params>
+ </query-method>
+ <ejb-ql>
+ SELECT OBJECT(o) FROM Order o
+ WHERE o.amount > 1000
+ </ejb-ql>
+ </query>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="method-name"
+ type="javaee:method-nameType"/>
+ <xsd:element name="method-params"
+ type="javaee:method-paramsType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="queryType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The queryType defines a finder or select
+ query. It contains
+ - an optional description of the query
+ - the specification of the finder or select
+ method it is used by
+ - an optional specification of the result type
+ mapping, if the query is for a select method
+ and entity objects are returned.
+ - the EJB QL query string that defines the query.
+
+ Queries that are expressible in EJB QL must use the ejb-ql
+ element to specify the query. If a query is not expressible
+ in EJB QL, the description element should be used to
+ describe the semantics of the query and the ejb-ql element
+ should be empty.
+
+ The result-type-mapping is an optional element. It can only
+ be present if the query-method specifies a select method
+ that returns entity objects. The default value for the
+ result-type-mapping element is "Local".
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType" minOccurs="0"/>
+ <xsd:element name="query-method"
+ type="javaee:query-methodType"/>
+ <xsd:element name="result-type-mapping"
+ type="javaee:result-type-mappingType"
+ minOccurs="0"/>
+ <xsd:element name="ejb-ql"
+ type="javaee:xsdStringType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="relationship-role-sourceType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The relationship-role-sourceType designates the source of a
+ role that participates in a relationship. A
+ relationship-role-sourceType is used by
+ relationship-role-source elements to uniquely identify an
+ entity bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-name"
+ type="javaee:ejb-nameType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="relationshipsType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The relationshipsType describes the relationships in
+ which entity beans with container-managed persistence
+ participate. The relationshipsType contains an optional
+ description; and a list of ejb-relation elements, which
+ specify the container managed relationships.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-relation"
+ type="javaee:ejb-relationType"
+ maxOccurs="unbounded">
+
+ <xsd:unique name="role-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-relationship-role-name contains the name of a
+ relationship role. The name must be unique within
+ a relationship, but can be reused in different
+ relationships.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector
+ xpath=".//javaee:ejb-relationship-role-name"/>
+ <xsd:field
+ xpath="."/>
+ </xsd:unique>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="remove-methodType">
+ <xsd:sequence>
+ <xsd:element name="bean-method"
+ type="javaee:named-methodType"/>
+ <xsd:element name="retain-if-exception"
+ type="javaee:true-falseType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="result-type-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The result-type-mappingType is used in the query element to
+ specify whether an abstract schema type returned by a query
+ for a select method is to be mapped to an EJBLocalObject or
+ EJBObject type.
+
+ The value must be one of the following:
+
+ Local
+ Remote
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="Local"/>
+ <xsd:enumeration value="Remote"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="security-identityType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The security-identityType specifies whether the caller's
+ security identity is to be used for the execution of the
+ methods of the enterprise bean or whether a specific run-as
+ identity is to be used. It contains an optional description
+ and a specification of the security identity to be used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:choice>
+ <xsd:element name="use-caller-identity"
+ type="javaee:emptyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The use-caller-identity element specifies that
+ the caller's security identity be used as the
+ security identity for the execution of the
+ enterprise bean's methods.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="run-as"
+ type="javaee:run-asType"/>
+ </xsd:choice>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="session-beanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The session-beanType declares an session bean. The
+ declaration consists of:
+
+ - an optional description
+ - an optional display name
+ - an optional icon element that contains a small and a large
+ icon file name
+ - a name assigned to the enterprise bean
+ in the deployment description
+ - an optional mapped-name element that can be used to provide
+ vendor-specific deployment information such as the physical
+ jndi-name of the session bean's remote home/business interface.
+ This element is not required to be supported by all
+ implementations. Any use of this element is non-portable.
+ - the names of all the remote or local business interfaces,
+ if any
+ - the names of the session bean's remote home and
+ remote interfaces, if any
+ - the names of the session bean's local home and
+ local interfaces, if any
+ - the name of the session bean's web service endpoint
+ interface, if any
+ - the session bean's implementation class
+ - the session bean's state management type
+ - an optional declaration of the session bean's timeout method.
+ - the optional session bean's transaction management type.
+ If it is not present, it is defaulted to Container.
+ - an optional list of the session bean class and/or
+ superclass around-invoke methods.
+ - an optional declaration of the bean's
+ environment entries
+ - an optional declaration of the bean's EJB references
+ - an optional declaration of the bean's local
+ EJB references
+ - an optional declaration of the bean's web
+ service references
+ - an optional declaration of the security role
+ references
+ - an optional declaration of the security identity
+ to be used for the execution of the bean's methods
+ - an optional declaration of the bean's resource
+ manager connection factory references
+ - an optional declaration of the bean's resource
+ environment references.
+ - an optional declaration of the bean's message
+ destination references
+
+ The elements that are optional are "optional" in the sense
+ that they are omitted when if lists represented by them are
+ empty.
+
+ Either both the local-home and the local elements or both
+ the home and the remote elements must be specified for the
+ session bean.
+
+ The service-endpoint element may only be specified if the
+ bean is a stateless session bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="ejb-name"
+ type="javaee:ejb-nameType"/>
+ <xsd:element name="mapped-name"
+ type="javaee:xsdStringType"
+ minOccurs="0"/>
+ <xsd:element name="home"
+ type="javaee:homeType"
+ minOccurs="0"/>
+ <xsd:element name="remote"
+ type="javaee:remoteType"
+ minOccurs="0"/>
+ <xsd:element name="local-home"
+ type="javaee:local-homeType"
+ minOccurs="0"/>
+ <xsd:element name="local"
+ type="javaee:localType"
+ minOccurs="0"/>
+ <xsd:element name="business-local"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="business-remote"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="service-endpoint"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-endpoint element contains the
+ fully-qualified name of the enterprise bean's web
+ service endpoint interface. The service-endpoint
+ element may only be specified for a stateless
+ session bean. The specified interface must be a
+ valid JAX-RPC service endpoint interface.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="ejb-class"
+ type="javaee:ejb-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-class element specifies the fully qualified name
+ of the bean class for this ejb. It is required unless
+ there is a component-defining annotation for the same
+ ejb-name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="session-type"
+ type="javaee:session-typeType"
+ minOccurs="0"/>
+ <xsd:element name="timeout-method"
+ type="javaee:named-methodType"
+ minOccurs="0"/>
+ <xsd:element name="init-method"
+ type="javaee:init-methodType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The init-method element specifies the mappings for
+ EJB 2.x style create methods for an EJB 3.0 bean.
+ This element can only be specified for stateful
+ session beans.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="remove-method"
+ type="javaee:remove-methodType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The remove-method element specifies the mappings for
+ EJB 2.x style remove methods for an EJB 3.0 bean.
+ This element can only be specified for stateful
+ session beans.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="transaction-type"
+ type="javaee:transaction-typeType"
+ minOccurs="0"/>
+ <xsd:element name="around-invoke"
+ type="javaee:around-invokeType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
+ <xsd:element name="post-activate"
+ type="javaee:lifecycle-callbackType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="pre-passivate"
+ type="javaee:lifecycle-callbackType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="security-role-ref"
+ type="javaee:security-role-refType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ </xsd:element>
+ <xsd:element name="security-identity"
+ type="javaee:security-identityType"
+ minOccurs="0">
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="session-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The session-typeType describes whether the session bean is a
+ stateful session or stateless session. It is used by
+ session-type elements.
+
+ The value must be one of the two following:
+
+ Stateful
+ Stateless
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="Stateful"/>
+ <xsd:enumeration value="Stateless"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="trans-attributeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The trans-attributeType specifies how the container must
+ manage the transaction boundaries when delegating a method
+ invocation to an enterprise bean's business method.
+
+ The value must be one of the following:
+
+ NotSupported
+ Supports
+ Required
+ RequiresNew
+ Mandatory
+ Never
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="NotSupported"/>
+ <xsd:enumeration value="Supports"/>
+ <xsd:enumeration value="Required"/>
+ <xsd:enumeration value="RequiresNew"/>
+ <xsd:enumeration value="Mandatory"/>
+ <xsd:enumeration value="Never"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="transaction-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The transaction-typeType specifies an enterprise bean's
+ transaction management type.
+
+ The transaction-type must be one of the two following:
+
+ Bean
+ Container
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="Bean"/>
+ <xsd:enumeration value="Container"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_1_4.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_1_4.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_1_4.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1607 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.4">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)j2ee_1_4.xsds 1.43 03/09/16
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003 Sun Microsystems, Inc., 901 San Antonio
+ Road, Palo Alto, California 94303, U.S.A. All rights
+ reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+<xsd:annotation>
+<xsd:documentation>
+
+The following definitions that appear in the common
+shareable schema(s) of J2EE deployment descriptors should be
+interpreted with respect to the context they are included:
+
+Deployment Component may indicate one of the following:
+ j2ee application;
+ application client;
+ web application;
+ enterprise bean;
+ resource adapter;
+
+Deployment File may indicate one of the following:
+ ear file;
+ war file;
+ jar file;
+ rar file;
+
+</xsd:documentation>
+</xsd:annotation>
+
+ <xsd:import namespace="http://www.w3.org/XML/1998/namespace"
+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
+
+ <xsd:include schemaLocation=
+ "http://www.ibm.com/webservices/xsd/j2ee_web_services_client_1_1.xsd"/>
+
+
+<!-- **************************************************** -->
+
+ <xsd:group name="descriptionGroup">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This group keeps the usage of the contained description related
+ elements consistent across J2EE deployment descriptors.
+
+ All elements may occur multiple times with different languages,
+ to support localization of the content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="display-name"
+ type="j2ee:display-nameType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="icon"
+ type="j2ee:iconType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:group>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="descriptionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The description type is used by a description element to
+ provide text describing the parent element. The elements
+ that use this type should include any information that the
+ Deployment Component's Deployment File file producer wants
+ to provide to the consumer of the Deployment Component's
+ Deployment File (i.e., to the Deployer). Typically, the
+ tools used by such a Deployment File consumer will display
+ the description when processing the parent element that
+ contains the description.
+
+ The lang attribute defines the language that the
+ description is provided in. The default value is "en" (English).
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="j2ee:xsdStringType">
+ <xsd:attribute ref="xml:lang"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="dewey-versionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type defines a dewey decimal which is used
+ to describe versions of documents.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:restriction base="xsd:decimal">
+ <xsd:whiteSpace value="collapse"/>
+ </xsd:restriction>
+
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="display-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The display-name type contains a short name that is intended
+ to be displayed by tools. It is used by display-name
+ elements. The display name need not be unique.
+
+ Example:
+
+ ...
+ <display-name xml:lang="en">Employee Self Service</display-name>
+
+ The value of the xml:lang attribute is "en" (English) by default.
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="j2ee:string">
+ <xsd:attribute ref="xml:lang"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-linkType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The ejb-linkType is used by ejb-link
+ elements in the ejb-ref or ejb-local-ref elements to specify
+ that an EJB reference is linked to enterprise bean.
+
+ The value of the ejb-link element must be the ejb-name of an
+ enterprise bean in the same ejb-jar file or in another ejb-jar
+ file in the same J2EE application unit.
+
+ Alternatively, the name in the ejb-link element may be
+ composed of a path name specifying the ejb-jar containing the
+ referenced enterprise bean with the ejb-name of the target
+ bean appended and separated from the path name by "#". The
+ path name is relative to the Deployment File containing
+ Deployment Component that is referencing the enterprise
+ bean. This allows multiple enterprise beans with the same
+ ejb-name to be uniquely identified.
+
+ Examples:
+
+ <ejb-link>EmployeeRecord</ejb-link>
+
+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-local-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-local-refType is used by ejb-local-ref elements for
+ the declaration of a reference to an enterprise bean's local
+ home. The declaration consists of:
+
+ - an optional description
+ - the EJB reference name used in the code of the Deployment
+ Component that's referencing the enterprise bean
+ - the expected type of the referenced enterprise bean
+ - the expected local home and local interfaces of the
+ referenced enterprise bean
+ - optional ejb-link information, used to specify the
+ referenced enterprise bean
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-ref-name"
+ type="j2ee:ejb-ref-nameType"/>
+ <xsd:element name="ejb-ref-type"
+ type="j2ee:ejb-ref-typeType"/>
+ <xsd:element name="local-home"
+ type="j2ee:local-homeType"/>
+ <xsd:element name="local"
+ type="j2ee:localType"/>
+ <xsd:element name="ejb-link"
+ type="j2ee:ejb-linkType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-ref-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the
+ Deployment Component's environment and is relative to the
+ java:comp/env context. The name must be unique within the
+ Deployment Component.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ Example:
+
+ <ejb-ref-name>ejb/Payroll</ejb-ref-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:jndi-nameType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-ref-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-typeType contains the expected type of the
+ referenced enterprise bean.
+
+ The ejb-ref-type designates a value
+ that must be one of the following:
+
+ Entity
+ Session
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="Entity"/>
+ <xsd:enumeration value="Session"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-refType is used by ejb-ref elements for the
+ declaration of a reference to an enterprise bean's home. The
+ declaration consists of:
+
+ - an optional description
+ - the EJB reference name used in the code of
+ the Deployment Component that's referencing the enterprise
+ bean
+ - the expected type of the referenced enterprise bean
+ - the expected home and remote interfaces of the referenced
+ enterprise bean
+ - optional ejb-link information, used to specify the
+ referenced enterprise bean
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-ref-name"
+ type="j2ee:ejb-ref-nameType"/>
+ <xsd:element name="ejb-ref-type"
+ type="j2ee:ejb-ref-typeType"/>
+
+ <xsd:element name="home"
+ type="j2ee:homeType"/>
+ <xsd:element name="remote"
+ type="j2ee:remoteType"/>
+ <xsd:element name="ejb-link"
+ type="j2ee:ejb-linkType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="emptyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type is used to designate an empty
+ element when used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="env-entry-type-valuesType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This type contains the fully-qualified Java type of the
+ environment entry value that is expected by the
+ application's code.
+
+ The following are the legal values of env-entry-type-valuesType:
+
+ java.lang.Boolean
+ java.lang.Byte
+ java.lang.Character
+ java.lang.String
+ java.lang.Short
+ java.lang.Integer
+ java.lang.Long
+ java.lang.Float
+ java.lang.Double
+
+ Example:
+
+ <env-entry-type>java.lang.Boolean</env-entry-type>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="java.lang.Boolean"/>
+ <xsd:enumeration value="java.lang.Byte"/>
+ <xsd:enumeration value="java.lang.Character"/>
+ <xsd:enumeration value="java.lang.String"/>
+ <xsd:enumeration value="java.lang.Short"/>
+ <xsd:enumeration value="java.lang.Integer"/>
+ <xsd:enumeration value="java.lang.Long"/>
+ <xsd:enumeration value="java.lang.Float"/>
+ <xsd:enumeration value="java.lang.Double"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="env-entryType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entryType is used to declare an application's
+ environment entry. The declaration consists of an optional
+ description, the name of the environment entry, and an
+ optional value. If a value is not specified, one must be
+ supplied during deployment.
+
+ It is used by env-entry elements.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="env-entry-name"
+ type="j2ee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The env-entry-name element contains the name of a
+ Deployment Component's environment entry. The name
+ is a JNDI name relative to the java:comp/env
+ context. The name must be unique within a
+ Deployment Component. The uniqueness
+ constraints must be defined within the declared
+ context.
+
+ Example:
+
+ <env-entry-name>minAmount</env-entry-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="env-entry-type"
+ type="j2ee:env-entry-type-valuesType"/>
+
+ <xsd:element name="env-entry-value"
+ type="j2ee:xsdStringType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The env-entry-value designates the value of a
+ Deployment Component's environment entry. The value
+ must be a String that is valid for the
+ constructor of the specified type that takes a
+ single String parameter, or for java.lang.Character,
+ a single character.
+
+ Example:
+
+ <env-entry-value>100.00</env-entry-value>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The elements that use this type designate the name of a
+ Java class or interface. The name is in the form of a
+ "binary name", as defined in the JLS. This is the form
+ of name used in Class.forName(). Tools that need the
+ canonical name (the name used in source code) will need
+ to convert this binary name to the canonical name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="generic-booleanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type defines four different values which can designate
+ boolean values. This includes values yes and no which are
+ not designated by xsd:boolean
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="true"/>
+ <xsd:enumeration value="false"/>
+ <xsd:enumeration value="yes"/>
+ <xsd:enumeration value="no"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="homeType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The homeType defines the fully-qualified name of
+ an enterprise bean's home interface.
+
+ Example:
+
+ <home>com.aardvark.payroll.PayrollHome</home>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="iconType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The icon type contains small-icon and large-icon elements
+ that specify the file names for small and large GIF or
+ JPEG icon images used to represent the parent element in a
+ GUI tool.
+
+ The xml:lang attribute defines the language that the
+ icon file names are provided in. Its value is "en" (English)
+ by default.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="small-icon" type="j2ee:pathType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The small-icon element contains the name of a file
+ containing a small (16 x 16) icon image. The file
+ name is a relative path within the Deployment
+ Component's Deployment File.
+
+ The image may be either in the JPEG or GIF format.
+ The icon can be used by tools.
+
+ Example:
+
+ <small-icon>employee-service-icon16x16.jpg</small-icon>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="large-icon" type="j2ee:pathType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The large-icon element contains the name of a file
+ containing a large
+ (32 x 32) icon image. The file name is a relative
+ path within the Deployment Component's Deployment
+ File.
+
+ The image may be either in the JPEG or GIF format.
+ The icon can be used by tools.
+
+ Example:
+
+ <large-icon>employee-service-icon32x32.jpg</large-icon>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ </xsd:sequence>
+
+ <xsd:attribute ref="xml:lang"/>
+ <xsd:attribute name="id" type="xsd:ID"/>
+
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="java-identifierType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The java-identifierType defines a Java identifier.
+ The users of this type should further verify that
+ the content does not contain Java reserved keywords.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="java-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This is a generic type that designates a Java primitive
+ type or a fully qualified name of a Java interface/type,
+ or an array of such types.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:pattern value="[^\p{Z}]*"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jndi-nameType type designates a JNDI name in the
+ Deployment Component's environment and is relative to the
+ java:comp/env context. A JNDI name must be unique within the
+ Deployment Component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:group name="jndiEnvironmentRefsGroup">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This group keeps the usage of the contained JNDI environment
+ reference elements consistent across J2EE deployment descriptors.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="env-entry"
+ type="j2ee:env-entryType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="ejb-ref"
+ type="j2ee:ejb-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="ejb-local-ref"
+ type="j2ee:ejb-local-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:group ref="j2ee:service-refGroup"/>
+ <xsd:element name="resource-ref"
+ type="j2ee:resource-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="resource-env-ref"
+ type="j2ee:resource-env-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="message-destination-ref"
+ type="j2ee:message-destination-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:group>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="listenerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The listenerType indicates the deployment properties for a web
+ application listener bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="listener-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The listener-class element declares a class in the
+ application must be registered as a web
+ application listener bean. The value is the fully
+ qualified classname of the listener class.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="local-homeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The local-homeType defines the fully-qualified
+ name of an enterprise bean's local home interface.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="localType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The localType defines the fully-qualified name of an
+ enterprise bean's local interface.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-destination-linkType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-linkType is used to link a message
+ destination reference or message-driven bean to a message
+ destination.
+
+ The Assembler sets the value to reflect the flow of messages
+ between producers and consumers in the application.
+
+ The value must be the message-destination-name of a message
+ destination in the same Deployment File or in another
+ Deployment File in the same J2EE application unit.
+
+ Alternatively, the value may be composed of a path name
+ specifying a Deployment File containing the referenced
+ message destination with the message-destination-name of the
+ destination appended and separated from the path name by
+ "#". The path name is relative to the Deployment File
+ containing Deployment Component that is referencing the
+ message destination. This allows multiple message
+ destinations with the same name to be uniquely identified.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-destination-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The message-destination-ref element contains a declaration
+ of Deployment Component's reference to a message destination
+ associated with a resource in Deployment Component's
+ environment. It consists of:
+
+ - an optional description
+ - the message destination reference name
+ - the message destination type
+ - a specification as to whether the
+ destination is used for
+ consuming or producing messages, or both
+ - a link to the message destination
+
+ Examples:
+
+ <message-destination-ref>
+ <message-destination-ref-name>jms/StockQueue
+ </message-destination-ref-name>
+ <message-destination-type>javax.jms.Queue
+ </message-destination-type>
+ <message-destination-usage>Consumes
+ </message-destination-usage>
+ <message-destination-link>CorporateStocks
+ </message-destination-link>
+ </message-destination-ref>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="message-destination-ref-name"
+ type="j2ee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies
+ the name of a message destination reference; its
+ value is the environment entry name used in
+ Deployment Component code. The name is a JNDI name
+ relative to the java:comp/env context and must be
+ unique within an ejb-jar (for enterprise beans) or a
+ Deployment File (for others).
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="message-destination-type"
+ type="j2ee:message-destination-typeType"/>
+ <xsd:element name="message-destination-usage"
+ type="j2ee:message-destination-usageType"/>
+ <xsd:element name="message-destination-link"
+ type="j2ee:message-destination-linkType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-destination-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The message-destination-typeType specifies the type of
+ the destination. The type is specified by the Java interface
+ expected to be implemented by the destination.
+
+ Example:
+
+ <message-destination-type>javax.jms.Queue
+ </message-destination-type>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-destination-usageType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-usageType specifies the use of the
+ message destination indicated by the reference. The value
+ indicates whether messages are consumed from the message
+ destination, produced for the destination, or both. The
+ Assembler makes use of this information in linking producers
+ of a destination with its consumers.
+
+ The value of the message-destination-usage element must be
+ one of the following:
+ Consumes
+ Produces
+ ConsumesProduces
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="Consumes"/>
+ <xsd:enumeration value="Produces"/>
+ <xsd:enumeration value="ConsumesProduces"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-destinationType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The message-destinationType specifies a message
+ destination. The logical destination described by this
+ element is mapped to a physical destination by the Deployer.
+
+ The message destination element contains:
+
+ - an optional description
+ - an optional display-name
+ - an optional icon
+ - a message destination name which must be unique
+ among message destination names within the same
+ Deployment File.
+
+ Example:
+
+ <message-destination>
+ <message-destination-name>CorporateStocks
+ </message-destination-name>
+ </message-destination>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="message-destination-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-name element specifies a
+ name for a message destination. This name must be
+ unique among the names of message destinations
+ within the Deployment File.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="param-valueType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type is a general type that can be used to declare
+ parameter/value lists.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="param-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The param-name element contains the name of a
+ parameter.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="param-value"
+ type="j2ee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The param-value element contains the value of a
+ parameter.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The elements that use this type designate either a relative
+ path or an absolute path starting with a "/".
+
+ In elements that specify a pathname to a file within the
+ same Deployment File, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the Deployment File's namespace. Absolute filenames (i.e.,
+ those starting with "/") also specify names in the root of
+ the Deployment File's namespace. In general, relative names
+ are preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="remoteType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The remote element contains the fully-qualified name
+ of the enterprise bean's remote interface.
+
+ Example:
+
+ <remote>com.wombat.empl.EmployeeService</remote>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="res-authType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-authType specifies whether the Deployment Component
+ code signs on programmatically to the resource manager, or
+ whether the Container will sign on to the resource manager
+ on behalf of the Deployment Component. In the latter case,
+ the Container uses information that is supplied by the
+ Deployer.
+
+ The value must be one of the two following:
+
+ Application
+ Container
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="Application"/>
+ <xsd:enumeration value="Container"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="res-sharing-scopeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-sharing-scope type specifies whether connections
+ obtained through the given resource manager connection
+ factory reference can be shared. The value, if specified,
+ must be one of the two following:
+
+ Shareable
+ Unshareable
+
+ The default value is Shareable.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="Shareable"/>
+ <xsd:enumeration value="Unshareable"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="resource-env-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The resource-env-refType is used to define
+ resource-env-type elements. It contains a declaration of a
+ Deployment Component's reference to an administered object
+ associated with a resource in the Deployment Component's
+ environment. It consists of an optional description, the
+ resource environment reference name, and an indication of
+ the resource environment reference type expected by the
+ Deployment Component code.
+
+ Example:
+
+ <resource-env-ref>
+ <resource-env-ref-name>jms/StockQueue
+ </resource-env-ref-name>
+ <resource-env-ref-type>javax.jms.Queue
+ </resource-env-ref-type>
+ </resource-env-ref>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="resource-env-ref-name"
+ type="j2ee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name
+ of a resource environment reference; its value is
+ the environment entry name used in
+ the Deployment Component code. The name is a JNDI
+ name relative to the java:comp/env context and must
+ be unique within a Deployment Component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="resource-env-ref-type"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-type element specifies the type
+ of a resource environment reference. It is the
+ fully qualified name of a Java language class or
+ interface.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="resource-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The resource-refType contains a declaration of a
+ Deployment Component's reference to an external resource. It
+ consists of an optional description, the resource manager
+ connection factory reference name, the indication of the
+ resource manager connection factory type expected by the
+ Deployment Component code, the type of authentication
+ (Application or Container), and an optional specification of
+ the shareability of connections obtained from the resource
+ (Shareable or Unshareable).
+
+ Example:
+
+ <resource-ref>
+ <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
+ <res-type>javax.sql.DataSource</res-type>
+ <res-auth>Container</res-auth>
+ <res-sharing-scope>Shareable</res-sharing-scope>
+ </resource-ref>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="res-ref-name"
+ type="j2ee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference.
+ The name is a JNDI name relative to the
+ java:comp/env context.
+ The name must be unique within a Deployment File.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="res-type"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-type element specifies the type of the data
+ source. The type is specified by the fully qualified
+ Java language class or interface
+ expected to be implemented by the data source.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="res-auth"
+ type="j2ee:res-authType"/>
+
+ <xsd:element name="res-sharing-scope"
+ type="j2ee:res-sharing-scopeType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="role-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The role-nameType designates the name of a security role.
+
+ The name must conform to the lexical rules for a token.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="run-asType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The run-asType specifies the run-as identity to be
+ used for the execution of a component. It contains an
+ optional description, and the name of a security role.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="role-name"
+ type="j2ee:role-nameType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="security-role-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The security-role-refType contains the declaration of a
+ security role reference in a component's or a
+ Deployment Component's code. The declaration consists of an
+ optional description, the security role name used in the
+ code, and an optional link to a security role. If the
+ security role is not specified, the Deployer must choose an
+ appropriate security role.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="role-name"
+ type="j2ee:role-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The value of the role-name element must be the String used
+ as the parameter to the
+ EJBContext.isCallerInRole(String roleName) method or the
+ HttpServletRequest.isUserInRole(String role) method.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="role-link"
+ type="j2ee:role-nameType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The role-link element is a reference to a defined
+ security role. The role-link element must contain
+ the name of one of the security roles defined in the
+ security-role elements.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="security-roleType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The security-roleType contains the definition of a security
+ role. The definition consists of an optional description of the
+ security role, and the security role name.
+
+ Example:
+
+ <security-role>
+ <description>
+ This role includes all employees who are authorized
+ to access the employee service application.
+ </description>
+ <role-name>employee</role-name>
+ </security-role>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="role-name"
+ type="j2ee:role-nameType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This is a special string datatype that is defined by J2EE as
+ a base type for defining collapsed strings. When schemas
+ require trailing/leading space elimination as well as
+ collapsing the existing whitespace, this base type may be
+ used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:token">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="true-falseType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This simple type designates a boolean with only two
+ permissible values
+
+ - true
+ - false
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:xsdBooleanType">
+ <xsd:pattern value="(true|false)"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="url-patternType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The url-patternType contains the url pattern of the mapping.
+ It must follow the rules specified in Section 11.2 of the
+ Servlet API Specification. This pattern is assumed to be in
+ URL-decoded form and must not contain CR(#xD) or LF(#xA).
+ If it contains those characters, the container must inform
+ the developer with a descriptive error message.
+ The container must preserve all characters including whitespaces.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdAnyURIType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:anyURI.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:anyURI">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdBooleanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:boolean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:boolean">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdIntegerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:integer.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:integer">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdNMTOKENType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:NMTOKEN.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:NMTOKEN">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdNonNegativeIntegerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:nonNegativeInteger.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:nonNegativeInteger">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdPositiveIntegerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:positiveInteger.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:positiveInteger">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdQNameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:QName.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:QName">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:string.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:string">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_jaxrpc_mapping_1_1.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_jaxrpc_mapping_1_1.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_jaxrpc_mapping_1_1.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,885 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.1">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)j2ee_jaxrpc_mapping_1_1.xsds 1.11 09/03/03
+
+ Based on j2ee_jaxrpc_mapping_1_0.dtd, Last updated: 09/19/2002 10:26
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003 Sun Microsystems, Inc., 901 San Antonio
+ Road, Palo Alto, California 94303, U.S.A. All rights
+ reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ (C) Copyright International Business Machines Corporation 2002
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The element describes the Java mapping to a known WSDL document.
+
+ It contains the mapping between package names and XML namespaces,
+ WSDL root types and Java artifacts, and the set of mappings for
+ services.
+
+ All java-wsdl-mapping deployment descriptors must indicate the
+ schema by using the J2EE namespace:
+
+ http://java.sun.com/xml/ns/j2ee
+
+ and by indicating the version of the schema by using the
+ version element as shown below:
+
+ <java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
+ http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd"
+ version="1.1">
+ ...
+ </java-wsdl-mapping>
+
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute for J2EE
+ namespace with the following location:
+
+ http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all J2EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
+
+
+<!-- **************************************************** -->
+
+
+ <xsd:element name="java-wsdl-mapping" type="j2ee:java-wsdl-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This is the root of the java-wsdl-mapping deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="constructor-parameter-orderType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The constructor-parameter-order element defines the order
+ that complexType element values are applied to a Java
+ exception constructor. Element names are specified for each
+ parameter of the constructor, including element names of
+ inherited types if necessary.
+
+ Used in: exception-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="element-name"
+ type="j2ee:string"
+ minOccurs="1" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The element-name element defines the name of a complexType
+ element name attribute value.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="exception-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The exception-mapping element defines the mapping between the
+ service specific exception types and wsdl faults and
+ SOAP headerfaults.
+
+ This element should be interpreted with respect to the
+ mapping between a method and an operation which provides the
+ mapping context.
+
+ Used in: service-endpoint-method-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="exception-type"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The exception-type element defines Java type of the exception.
+ It may be a service specific exception.
+
+ It must be a fully qualified class name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-message"
+ type="j2ee:wsdl-messageType"/>
+ <xsd:element name="wsdl-message-part-name"
+ type="j2ee:wsdl-message-part-nameType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-message-part-name element is required only
+ when the message referenced by the wsdl-message element
+ has more than one part.
+
+ This only occurs when multiple headerfaults use the
+ same message.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="constructor-parameter-order"
+ type="j2ee:constructor-parameter-orderType"
+ minOccurs="0" maxOccurs="1"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="java-wsdl-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The element describes the Java mapping to a known WSDL document.
+
+ It contains the mapping between package names and XML namespaces,
+ WSDL root types and Java artifacts, and the set of mappings for
+ services.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="package-mapping"
+ type="j2ee:package-mappingType"
+ minOccurs="1" maxOccurs="unbounded"/>
+ <xsd:element name="java-xml-type-mapping"
+ type="j2ee:java-xml-type-mappingType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="exception-mapping"
+ type="j2ee:exception-mappingType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:sequence minOccurs="0" maxOccurs="unbounded">
+ <xsd:element name="service-interface-mapping"
+ type="j2ee:service-interface-mappingType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="service-endpoint-interface-mapping"
+ type="j2ee:service-endpoint-interface-mappingType"
+ minOccurs="1" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:sequence>
+
+ <xsd:attribute name="version"
+ type="j2ee:dewey-versionType"
+ fixed="1.1"
+ use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The required value for the version is 1.1.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="java-xml-type-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The java-xml-type-mapping element contains a java-type that is the
+ fully qualified name of the Java class, primitive type, or array
+ type, QName of the XML root type or anonymous type, the WSDL type
+ scope the QName applies to and the set of variable mappings for
+ each public variable within the Java class.
+
+ Used in: java-wsdl-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="java-type"
+ type="j2ee:java-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The java-type element is the fully qualified class name of
+ a Java class, primitive, or array type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <choice>
+ <xsd:element name="root-type-qname"
+ type="j2ee:xsdQNameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The root-type-qname identifies the WSDL QName of an XML type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="anonymous-type-qname"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The anonymous-type-qname identifies the WSDL QName of an
+ anonymous XML type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </choice>
+ <xsd:element name="qname-scope"
+ type="j2ee:qname-scopeType"/>
+ <xsd:element name="variable-mapping"
+ type="j2ee:variable-mappingType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="method-param-parts-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-param-parts-mapping element defines the mapping between a
+ Java method parameters and a wsdl-message.
+
+ Used in: service-endpoint-method-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="param-position"
+ type="j2ee:xsdNonNegativeIntegerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The param-position element defines the position of a
+ parameter within a Java method. It must be an integer
+ starting from 0.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="param-type"
+ type="j2ee:java-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The param-type element defines the fully qualified
+ class name of a Java class, primitive, or array type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-message-mapping"
+ type="j2ee:wsdl-message-mappingType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="package-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The package-mapping indicates the mapping between java-package-name
+ and XML namespace in the WSDL document.
+
+ Used in: java-wsdl-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="package-type"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The package-type indicates the Java package name. It must be a fully
+ qualified package name, even though the XML schema type is
+ fully-qualified-classType.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="namespaceURI"
+ type="j2ee:xsdAnyURIType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The namespaceURI element indicates a URI.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="parameter-modeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The parameter-mode element defines the mode of the parameter.
+ It can have only three values, IN, OUT, INOUT.
+
+ Used in: java-xml-type-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="IN"/>
+ <xsd:enumeration value="OUT"/>
+ <xsd:enumeration value="INOUT"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="port-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-mapping defines the mapping of the WSDL port name attribute
+ to the Java name used to generate the Generated Service Interface
+ method get{java-name}.
+
+ Used in: service-interface-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="port-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-mapping defines the mapping of the WSDL port name
+ attribute to the Java name used to generate the Generated
+ Service Interface method get{java-name}.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="java-port-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The java-port-name element is the string to use as the port
+ name in Java. It is used in generating the Generated
+ Service Interface method get{java-port-name}.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="qname-scopeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The qname-scope elements scopes the reference of a QName to the WSDL
+ element type it applies to. The value of qname-scope may be
+ simpleType, complexType, or element.
+
+ Used in: java-xml-type-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="simpleType"/>
+ <xsd:enumeration value="complexType"/>
+ <xsd:enumeration value="element"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="service-endpoint-interface-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-endpoint-interface-mapping defines a tuple
+ to specify Service Endpoint Interfaces to
+ WSDL port types and WSDL bindings.
+
+ An interface may be mapped to a port-type and binding multiple
+ times. This happens rarely.
+
+ Used in: java-wsdl-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="service-endpoint-interface"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-endpoint-interface element defines the Java
+ type for the endpoint interface. The name must be a fully
+ qualified class name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-port-type"
+ type="j2ee:xsdQNameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-port-type element defines the wsdl port type
+ by a QNAME which uniquely identifies the port type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-binding"
+ type="j2ee:xsdQNameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-binding element defines the wsdl binding
+ by a QNAME which uniquely identifies the binding.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="service-endpoint-method-mapping"
+ type="j2ee:service-endpoint-method-mappingType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="service-endpoint-method-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-endpoint-method-mapping element defines the mapping of
+ Java methods to operations (which are not uniquely qualified by
+ qnames).
+
+ The wsdl-operation should be interpreted with respect to the
+ portType and binding in which this definition is embedded within.
+ See the definitions for service-endpoint-interface-mapping and
+ service-interface-mapping to acquire the proper context. The
+ wrapped-element indicator should only be specified when a WSDL
+ message wraps an element type. The wsdl-return-value-mapping is
+ not specified for one-way operations.
+
+ Used in: service-endpoint-interface-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="java-method-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The java-method-name element defines the name of a Java method
+ within an interface.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-operation"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-operation element defines an operation within a WSDL
+ document. It must be interpreted with respect to a port type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wrapped-element"
+ type="j2ee:emptyType"
+ minOccurs="0"
+ maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wrapped-element element is defined when a WSDL message
+ with a single part is used to wrap an element type and the
+ element's name matches the operation name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="method-param-parts-mapping"
+ type="j2ee:method-param-parts-mappingType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="wsdl-return-value-mapping"
+ type="j2ee:wsdl-return-value-mappingType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="service-interface-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-interface-mapping element defines how a Java type for
+ the service interface maps to a WSDL service.
+
+ Used in: java-wsdl-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="service-interface"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-interface element defines the Java type for the service.
+ For static services, it is javax.xml.rpc.Service interface. For
+ generated service, it would be the generated interface name.
+
+ The name must be a fully qualified class name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-service-name"
+ type="j2ee:xsdQNameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-service-name element defines the wsdl service name
+ by a QNAME which uniquely identifies the service.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="port-mapping"
+ type="j2ee:port-mappingType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="variable-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The variable-mapping element defines the correlation between a
+ Java class data member or JavaBeans property to an XML element
+ or attribute name of an XML root type. If the data-member
+ element is present, the Java variable name is a public data
+ member. If data-member is not present, the Java variable name
+ is a JavaBeans property.
+
+ Used in: java-xml-type-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="java-variable-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The java-variable-name defines the name of a public data member or
+ JavaBeans property within a Java class.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="data-member"
+ type="j2ee:emptyType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The data-member element is a boolean indicator that a Java
+ variable is a public data member and not a JavaBeans property.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:choice>
+ <xsd:element name="xml-attribute-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The xml-attribute-name element defines name attribute value
+ of a WSDL attribute element within a root type. The value
+ of an xml-attribute-name element must match the value of
+ the ref attribute if mapping an attribute reference.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="xml-element-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The xml-element-name element defines name attribute value of
+ a WSDL element within a root type. The value of an
+ xml-element-name element must match the value of the ref
+ attribute if mapping an element reference.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="xml-wildcard"
+ type="j2ee:emptyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The xml-wildcard element associates the variable-mapping with
+ an xsd:any element within a root type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:choice>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="wsdl-message-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-message-mapping element defines the mapping to a
+ specific message and its part. Together they define uniquely
+ the mapping for a specific parameter. Parts within a message
+ context are uniquely identified with their names.
+
+ The parameter-mode is defined by the mapping to indicate
+ whether the mapping will be IN, OUT, or INOUT.. The presence
+ of the soap-header element indicates that the parameter is
+ mapped to a soap header only. When absent, it means that the
+ wsdl-message is mapped to a Java parameter. The soap headers
+ are interpreted in the order they are provided in the mapping.
+
+ Used in: method-param-parts-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="wsdl-message"
+ type="j2ee:wsdl-messageType"/>
+ <xsd:element name="wsdl-message-part-name"
+ type="j2ee:wsdl-message-part-nameType"/>
+ <xsd:element name="parameter-mode"
+ type="j2ee:parameter-modeType"/>
+ <xsd:element name="soap-header"
+ type="j2ee:emptyType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The soap-header element is a boolean element indicating that
+ a parameter is mapped to a SOAP header.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="wsdl-message-part-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Interpretation of the wsdl-message-part-name element depends on
+ whether or not wrapped-element has been defined in the
+ service-endpoint-method-mapping. If wrapped-element is not
+ specified, wsdl-message-part-name defines a WSDL message part. It
+ should always be interpreted with respect to a wsdl-message
+ element. If wrapped-element is specified, wsdl-message-part-name
+ refers to an element name of the element type.
+
+ Used in: wsdl-message-mapping, wsdl-return-value-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="wsdl-messageType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-message element defines a WSDL message by a QNAME.
+
+ Used in: wsdl-message-mapping, wsdl-return-value-mapping,
+ exception-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:xsdQNameType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="wsdl-return-value-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-return-value-mapping element defines the mapping for the
+ method's return value. It defines the mapping to a specific message
+ and its part. Together they define uniquely the mapping for a
+ specific parameter. Parts within a message context are uniquely
+ identified with their names. The wsdl-message-part-name is not
+ specified if there is no return value or OUT parameters.
+
+ Used in: service-endpoint-method-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="method-return-value"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The method-return-value element defines a fully qualified
+ class name or void type for the method's return value
+ type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-message"
+ type="j2ee:wsdl-messageType"/>
+ <xsd:element name="wsdl-message-part-name"
+ type="j2ee:wsdl-message-part-nameType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_web_services_1_1.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_web_services_1_1.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_web_services_1_1.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,490 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.1">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)j2ee_web_services_1_1.xsds 1.11 02/11/03
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003 Sun Microsystems, Inc., 901 San Antonio
+ Road, Palo Alto, California 94303, U.S.A. All rights
+ reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ (C) Copyright International Business Machines Corporation 2002
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The webservices element is the root element for the web services
+ deployment descriptor. It specifies the set of web service
+ descriptions that are to be deployed into the J2EE Application
+ Server and the dependencies they have on container resources and
+ services. The deployment descriptor must be named
+ "META-INF/webservices.xml" in the web services' jar file.
+
+ Used in: webservices.xml
+
+ All webservices deployment descriptors must indicate the
+ webservices schema by using the J2EE namespace:
+
+ http://java.sun.com/xml/ns/j2ee
+
+ and by indicating the version of the schema by using the version
+ element as shown below:
+
+ <webservices xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
+ http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd"
+ version="1.1">
+ ...
+ </webservices>
+
+ The instance documents may indicate the published version of the
+ schema using the xsi:schemaLocation attribute for the J2EE
+ namespace with the following location:
+
+ http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all J2EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
+
+
+ <!-- **************************************************** -->
+
+
+ <xsd:element name="webservices" type="j2ee:webservicesType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The webservices element is the root element for the web services
+ deployment descriptor. It specifies the set of web service
+ descriptions that are to be deployed into the J2EE Application Server
+ and the dependencies they have on container resources and services.
+
+ Used in: webservices.xml
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:key name="webservice-description-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The webservice-description-name identifies the collection of
+ port-components associated with a WSDL file and JAX-RPC mapping. The
+ name must be unique within the deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:webservice-description"/>
+ <xsd:field xpath="j2ee:webservice-description-name"/>
+ </xsd:key>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="port-componentType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component element associates a WSDL port with a web service
+ interface and implementation. It defines the name of the port as a
+ component, optional description, optional display name, optional iconic
+ representations, WSDL port QName, Service Endpoint Interface, Service
+ Implementation Bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="display-name"
+ type="j2ee:display-nameType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="icon"
+ type="j2ee:iconType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="port-component-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The port-component-name element specifies a port component's
+ name. This name is assigned by the module producer to name
+ the service implementation bean in the module's deployment
+ descriptor. The name must be unique among the port component
+ names defined in the same module.
+
+ Used in: port-component
+
+ Example:
+ <port-component-name>EmployeeService
+ </port-component-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-port"
+ type="j2ee:xsdQNameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name space and local name part of the WSDL port QName.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="service-endpoint-interface"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The service-endpoint-interface element contains the
+ fully-qualified name of the port component's Service Endpoint
+ Interface.
+
+ Used in: port-component
+
+ Example:
+ <remote>com.wombat.empl.EmployeeService</remote>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="service-impl-bean"
+ type="j2ee:service-impl-beanType"/>
+
+ <xsd:element name="handler"
+ type="j2ee:port-component_handlerType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="port-component_handlerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Declares the handler for a port-component. Handlers can access the
+ init-param name/value pairs using the HandlerInfo interface.
+
+ Used in: port-component
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="handler-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique within the
+ module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="handler-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines a fully qualified class name for the handler implementation.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="init-param"
+ type="j2ee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded"/>
+
+ <xsd:element name="soap-header"
+ type="j2ee:xsdQNameType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the QName of a SOAP header that will be processed by the
+ handler.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="soap-role"
+ type="j2ee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The soap-role element contains a SOAP actor definition that the
+ Handler will play as a role.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="service-impl-beanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-impl-bean element defines the web service implementation.
+ A service implementation can be an EJB bean class or JAX-RPC web
+ component. Existing EJB implementations are exposed as a web service
+ using an ejb-link.
+
+ Used in: port-component
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:choice>
+ <xsd:element name="ejb-link"
+ type="j2ee:ejb-linkType"/>
+ <xsd:element name="servlet-link"
+ type="j2ee:servlet-linkType"/>
+ </xsd:choice>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="servlet-linkType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The servlet-link element is used in the service-impl-bean element
+ to specify that a Service Implementation Bean is defined as a
+ JAX-RPC Service Endpoint.
+
+ The value of the servlet-link element must be the servlet-name of
+ a JAX-RPC Service Endpoint in the same WAR file.
+
+ Used in: service-impl-bean
+
+ Example:
+ <servlet-link>StockQuoteService</servlet-link>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="webservice-descriptionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The webservice-description element defines a WSDL document file
+ and the set of Port components associated with the WSDL ports
+ defined in the WSDL document. There may be multiple
+ webservice-descriptions defined within a module.
+
+ All WSDL file ports must have a corresponding port-component element
+ defined.
+
+ Used in: webservices
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="display-name"
+ type="j2ee:display-nameType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="icon"
+ type="j2ee:iconType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="webservice-description-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The webservice-description-name identifies the collection of
+ port-components associated with a WSDL file and JAX-RPC
+ mapping. The name must be unique within the deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-file"
+ type="j2ee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-file element contains the name of a WSDL file in the
+ module. The file name is a relative path within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="jaxrpc-mapping-file"
+ type="j2ee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jaxrpc-mapping-file element contains the name of a file that
+ describes the JAX-RPC mapping between the Java interaces used by
+ the application and the WSDL description in the wsdl-file. The
+ file name is a relative path within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="port-component"
+ type="j2ee:port-componentType"
+ minOccurs="1" maxOccurs="unbounded">
+ <xsd:key name="port-component_handler-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique
+ within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:handler"/>
+ <xsd:field xpath="j2ee:handler-name"/>
+ </xsd:key>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="webservicesType">
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="webservice-description"
+ type="j2ee:webservice-descriptionType"
+ minOccurs="1" maxOccurs="unbounded">
+ <xsd:key name="port-component-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The port-component-name element specifies a port
+ component's name. This name is assigned by the module
+ producer to name the service implementation bean in the
+ module's deployment descriptor. The name must be unique
+ among the port component names defined in the same module.
+
+ Used in: port-component
+
+ Example:
+ <port-component-name>EmployeeService
+ </port-component-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:port-component"/>
+ <xsd:field xpath="j2ee:port-component-name"/>
+ </xsd:key>
+ </xsd:element>
+ </xsd:sequence>
+
+ <xsd:attribute name="version"
+ type="j2ee:dewey-versionType"
+ fixed="1.1"
+ use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The required value for the version is 1.1.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_web_services_client_1_1.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_web_services_client_1_1.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/j2ee_web_services_client_1_1.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,344 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.1">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)j2ee_web_services_client_1_1.xsds 1.10 02/11/03
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003 Sun Microsystems, Inc., 901 San Antonio
+ Road, Palo Alto, California 94303, U.S.A. All rights
+ reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ (C) Copyright International Business Machines Corporation 2002
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="port-component-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component-ref element declares a client dependency
+ on the container for resolving a Service Endpoint Interface
+ to a WSDL port. It optionally associates the Service Endpoint
+ Interface with a particular port-component. This is only used
+ by the container for a Service.getPort(Class) method call.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="service-endpoint-interface"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-endpoint-interface element defines a fully qualified
+ Java class that represents the Service Endpoint Interface of a
+ WSDL port.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="port-component-link"
+ type="j2ee:string"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component-link element links a port-component-ref
+ to a specific port-component required to be made available
+ by a service reference.
+
+ The value of a port-component-link must be the
+ port-component-name of a port-component in the same module
+ or another module in the same application unit. The syntax
+ for specification follows the syntax defined for ejb-link
+ in the EJB 2.0 specification.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:group name="service-refGroup">
+ <xsd:sequence>
+ <xsd:element name="service-ref"
+ type="j2ee:service-refType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:key name="service-ref_handler-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique
+ within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:handler"/>
+ <xsd:field xpath="j2ee:handler-name"/>
+ </xsd:key>
+ </xsd:element>
+ </xsd:sequence>
+ </xsd:group>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="service-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-ref element declares a reference to a Web
+ service. It contains optional description, display name and
+ icons, a declaration of the required Service interface,
+ an optional WSDL document location, an optional set
+ of JAX-RPC mappings, an optional QName for the service element,
+ an optional set of Service Endpoint Interfaces to be resolved
+ by the container to a WSDL port, and an optional set of handlers.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="service-ref-name"
+ type="j2ee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-ref-name element declares logical name that the
+ components in the module use to look up the Web service. It
+ is recommended that all service reference names start with
+ "service/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="service-interface"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-interface element declares the fully qualified class
+ name of the JAX-RPC Service interface the client depends on.
+ In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
+ generated Service Interface class may also be specified.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="wsdl-file"
+ type="j2ee:xsdAnyURIType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-file element contains the URI location of a WSDL
+ file. The location is relative to the root of the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="jaxrpc-mapping-file"
+ type="j2ee:pathType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jaxrpc-mapping-file element contains the name of a file that
+ describes the JAX-RPC mapping between the Java interaces used by
+ the application and the WSDL description in the wsdl-file. The
+ file name is a relative path within the module file.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="service-qname"
+ type="j2ee:xsdQNameType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-qname element declares the specific WSDL service
+ element that is being refered to. It is not specified if no
+ wsdl-file is declared.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="port-component-ref"
+ type="j2ee:port-component-refType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component-ref element declares a client dependency
+ on the container for resolving a Service Endpoint Interface
+ to a WSDL port. It optionally associates the Service Endpoint
+ Interface with a particular port-component. This is only used
+ by the container for a Service.getPort(Class) method call.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="handler"
+ type="j2ee:service-ref_handlerType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Declares the handler for a port-component. Handlers can
+ access the init-param name/value pairs using the
+ HandlerInfo interface. If port-name is not specified, the
+ handler is assumed to be associated with all ports of the
+ service.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="service-ref_handlerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Declares the handler for a port-component. Handlers can access the
+ init-param name/value pairs using the HandlerInfo interface. If
+ port-name is not specified, the handler is assumed to be associated
+ with all ports of the service.
+
+ Used in: service-ref
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="handler-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique
+ within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="handler-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines a fully qualified class name for the handler
+ implementation.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="init-param"
+ type="j2ee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded"/>
+
+ <xsd:element name="soap-header"
+ type="j2ee:xsdQNameType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the QName of a SOAP header that will be processed
+ by the handler.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="soap-role"
+ type="j2ee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The soap-role element contains a SOAP actor definition that
+ the Handler will play as a role.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="port-name"
+ type="j2ee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-name element defines the WSDL port-name that a
+ handler should be associated with.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/java-properties_1_0.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/java-properties_1_0.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/java-properties_1_0.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: java-properties_1_0.xsd 33895 2005-07-25 03:47:22Z $
+-->
+<xs:schema version="1.0"
+ targetNamespace="urn:jboss:java-properties"
+ xmlns:java="urn:jboss:custom-object-binding"
+ xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ xmlns:jbxb="http://www.jboss.org/xml/ns/jbxb"
+ attributeFormDefault="unqualified"
+ elementFormDefault="qualified"
+ >
+ <xs:annotation>
+ <xs:documentation>A JBossXB schema for specifying how a java.util.Properties
+ object is unmarshalled.
+ </xs:documentation>
+ </xs:annotation>
+ <xs:element name="properties">
+ <xs:annotation>
+ <xs:appinfo>
+ <jbxb:class impl="java.util.Properties"/>
+ </xs:appinfo>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:element name="property" maxOccurs="unbounded">
+ <xs:annotation>
+ <xs:appinfo>
+ <jbxb:putMethod name="setProperty" keyType="java.lang.String" valueType="java.lang.String"/>
+ </xs:appinfo>
+ </xs:annotation>
+ <xs:complexType id="propertyType">
+ <xs:annotation>
+ <xs:appinfo>
+ <jbxb:mapEntry/>
+ </xs:appinfo>
+ </xs:annotation>
+ <xs:sequence>
+ <xs:element name="key" type="xs:string">
+ <xs:annotation>
+ <xs:appinfo>
+ <jbxb:mapEntryKey/>
+ </xs:appinfo>
+ </xs:annotation>
+ </xs:element>
+ <xs:element name="value" type="xs:string">
+ <xs:annotation>
+ <xs:appinfo>
+ <jbxb:mapEntryValue/>
+ </xs:appinfo>
+ </xs:annotation>
+ </xs:element>
+ </xs:sequence>
+ </xs:complexType>
+ </xs:element>
+ </xs:sequence>
+ </xs:complexType>
+ </xs:element>
+</xs:schema>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_5.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_5.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_5.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,2095 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="5">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)javaee_5.xsds 1.65 06/02/17
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003-2006 Sun Microsystems, Inc.
+ 4150 Network Circle
+ Santa Clara, California 95054
+ U.S.A
+ All rights reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+<xsd:annotation>
+<xsd:documentation>
+
+The following definitions that appear in the common
+shareable schema(s) of J2EE deployment descriptors should be
+interpreted with respect to the context they are included:
+
+Deployment Component may indicate one of the following:
+ j2ee application;
+ application client;
+ web application;
+ enterprise bean;
+ resource adapter;
+
+Deployment File may indicate one of the following:
+ ear file;
+ war file;
+ jar file;
+ rar file;
+
+</xsd:documentation>
+</xsd:annotation>
+
+ <xsd:import namespace="http://www.w3.org/XML/1998/namespace"
+ schemaLocation="http://www.w3.org/2001/xml.xsd"/>
+
+ <xsd:include schemaLocation="javaee_web_services_client_1_2.xsd"/>
+
+
+<!-- **************************************************** -->
+
+ <xsd:group name="descriptionGroup">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This group keeps the usage of the contained description related
+ elements consistent across Java EE deployment descriptors.
+
+ All elements may occur multiple times with different languages,
+ to support localization of the content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="display-name"
+ type="javaee:display-nameType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="icon"
+ type="javaee:iconType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:group>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="descriptionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The description type is used by a description element to
+ provide text describing the parent element. The elements
+ that use this type should include any information that the
+ Deployment Component's Deployment File file producer wants
+ to provide to the consumer of the Deployment Component's
+ Deployment File (i.e., to the Deployer). Typically, the
+ tools used by such a Deployment File consumer will display
+ the description when processing the parent element that
+ contains the description.
+
+ The lang attribute defines the language that the
+ description is provided in. The default value is "en" (English).
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="javaee:xsdStringType">
+ <xsd:attribute ref="xml:lang"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="dewey-versionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type defines a dewey decimal that is used
+ to describe versions of documents.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:restriction base="xsd:token">
+ <xsd:pattern value="\.?[0-9]+(\.[0-9]+)*"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="display-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The display-name type contains a short name that is intended
+ to be displayed by tools. It is used by display-name
+ elements. The display name need not be unique.
+
+ Example:
+
+ ...
+ <display-name xml:lang="en">
+ Employee Self Service
+ </display-name>
+
+ The value of the xml:lang attribute is "en" (English) by default.
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="javaee:string">
+ <xsd:attribute ref="xml:lang"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-linkType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The ejb-linkType is used by ejb-link
+ elements in the ejb-ref or ejb-local-ref elements to specify
+ that an EJB reference is linked to enterprise bean.
+
+ The value of the ejb-link element must be the ejb-name of an
+ enterprise bean in the same ejb-jar file or in another ejb-jar
+ file in the same Java EE application unit.
+
+ Alternatively, the name in the ejb-link element may be
+ composed of a path name specifying the ejb-jar containing the
+ referenced enterprise bean with the ejb-name of the target
+ bean appended and separated from the path name by "#". The
+ path name is relative to the Deployment File containing
+ Deployment Component that is referencing the enterprise
+ bean. This allows multiple enterprise beans with the same
+ ejb-name to be uniquely identified.
+
+ Examples:
+
+ <ejb-link>EmployeeRecord</ejb-link>
+
+ <ejb-link>../products/product.jar#ProductEJB</ejb-link>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-local-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-local-refType is used by ejb-local-ref elements for
+ the declaration of a reference to an enterprise bean's local
+ home or to the local business interface of a 3.0 bean.
+ The declaration consists of:
+
+ - an optional description
+ - the EJB reference name used in the code of the Deployment
+ Component that's referencing the enterprise bean.
+ - the optional expected type of the referenced enterprise bean
+ - the optional expected local interface of the referenced
+ enterprise bean or the local business interface of the
+ referenced enterprise bean.
+ - the optional expected local home interface of the referenced
+ enterprise bean. Not applicable if this ejb-local-ref refers
+ to the local business interface of a 3.0 bean.
+ - optional ejb-link information, used to specify the
+ referenced enterprise bean
+ - optional elements to define injection of the named enterprise
+ bean into a component field or property.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-ref-name"
+ type="javaee:ejb-ref-nameType"/>
+ <xsd:element name="ejb-ref-type"
+ type="javaee:ejb-ref-typeType"
+ minOccurs="0"/>
+ <xsd:element name="local-home"
+ type="javaee:local-homeType"
+ minOccurs="0"/>
+ <xsd:element name="local"
+ type="javaee:localType"
+ minOccurs="0"/>
+ <xsd:element name="ejb-link"
+ type="javaee:ejb-linkType"
+ minOccurs="0"/>
+ <xsd:group ref="javaee:resourceGroup"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-ref-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the
+ Deployment Component's environment and is relative to the
+ java:comp/env context. The name must be unique within the
+ Deployment Component.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ Example:
+
+ <ejb-ref-name>ejb/Payroll</ejb-ref-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:jndi-nameType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-ref-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-typeType contains the expected type of the
+ referenced enterprise bean.
+
+ The ejb-ref-type designates a value
+ that must be one of the following:
+
+ Entity
+ Session
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="Entity"/>
+ <xsd:enumeration value="Session"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="ejb-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-refType is used by ejb-ref elements for the
+ declaration of a reference to an enterprise bean's home or
+ to the remote business interface of a 3.0 bean.
+ The declaration consists of:
+
+ - an optional description
+ - the EJB reference name used in the code of
+ the Deployment Component that's referencing the enterprise
+ bean.
+ - the optional expected type of the referenced enterprise bean
+ - the optional remote interface of the referenced enterprise bean
+ or the remote business interface of the referenced enterprise
+ bean
+ - the optional expected home interface of the referenced
+ enterprise bean. Not applicable if this ejb-ref
+ refers to the remote business interface of a 3.0 bean.
+ - optional ejb-link information, used to specify the
+ referenced enterprise bean
+ - optional elements to define injection of the named enterprise
+ bean into a component field or property
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="ejb-ref-name"
+ type="javaee:ejb-ref-nameType"/>
+ <xsd:element name="ejb-ref-type"
+ type="javaee:ejb-ref-typeType"
+ minOccurs="0"/>
+ <xsd:element name="home"
+ type="javaee:homeType"
+ minOccurs="0"/>
+ <xsd:element name="remote"
+ type="javaee:remoteType"
+ minOccurs="0"/>
+ <xsd:element name="ejb-link"
+ type="javaee:ejb-linkType"
+ minOccurs="0"/>
+ <xsd:group ref="javaee:resourceGroup"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="emptyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type is used to designate an empty
+ element when used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="env-entry-type-valuesType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This type contains the fully-qualified Java type of the
+ environment entry value that is expected by the
+ application's code.
+
+ The following are the legal values of env-entry-type-valuesType:
+
+ java.lang.Boolean
+ java.lang.Byte
+ java.lang.Character
+ java.lang.String
+ java.lang.Short
+ java.lang.Integer
+ java.lang.Long
+ java.lang.Float
+ java.lang.Double
+
+ Example:
+
+ <env-entry-type>java.lang.Boolean</env-entry-type>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="java.lang.Boolean"/>
+ <xsd:enumeration value="java.lang.Byte"/>
+ <xsd:enumeration value="java.lang.Character"/>
+ <xsd:enumeration value="java.lang.String"/>
+ <xsd:enumeration value="java.lang.Short"/>
+ <xsd:enumeration value="java.lang.Integer"/>
+ <xsd:enumeration value="java.lang.Long"/>
+ <xsd:enumeration value="java.lang.Float"/>
+ <xsd:enumeration value="java.lang.Double"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="env-entryType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entryType is used to declare an application's
+ environment entry. The declaration consists of an optional
+ description, the name of the environment entry, a type
+ (optional if the value is injected, otherwise required), and
+ an optional value.
+
+ It also includes optional elements to define injection of
+ the named resource into fields or JavaBeans properties.
+
+ If a value is not specified and injection is requested,
+ no injection will occur and no entry of the specified name
+ will be created. This allows an initial value to be
+ specified in the source code without being incorrectly
+ changed when no override has been specified.
+
+ If a value is not specified and no injection is requested,
+ a value must be supplied during deployment.
+
+ This type is used by env-entry elements.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="env-entry-name"
+ type="javaee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The env-entry-name element contains the name of a
+ Deployment Component's environment entry. The name
+ is a JNDI name relative to the java:comp/env
+ context. The name must be unique within a
+ Deployment Component. The uniqueness
+ constraints must be defined within the declared
+ context.
+
+ Example:
+
+ <env-entry-name>minAmount</env-entry-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="env-entry-type"
+ type="javaee:env-entry-type-valuesType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The env-entry-type element contains the Java language
+ type of the environment entry. If an injection target
+ is specified for the environment entry, the type may
+ be omitted, or must match the type of the injection
+ target. If no injection target is specified, the type
+ is required.
+
+ Example:
+
+ <env-entry-type>java.lang.Integer</env-entry-type>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="env-entry-value"
+ type="javaee:xsdStringType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The env-entry-value designates the value of a
+ Deployment Component's environment entry. The value
+ must be a String that is valid for the
+ constructor of the specified type that takes a
+ single String parameter, or for java.lang.Character,
+ a single character.
+
+ Example:
+
+ <env-entry-value>100.00</env-entry-value>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:group ref="javaee:resourceGroup"/>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The elements that use this type designate the name of a
+ Java class or interface. The name is in the form of a
+ "binary name", as defined in the JLS. This is the form
+ of name used in Class.forName(). Tools that need the
+ canonical name (the name used in source code) will need
+ to convert this binary name to the canonical name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="generic-booleanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type defines four different values which can designate
+ boolean values. This includes values yes and no which are
+ not designated by xsd:boolean
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="true"/>
+ <xsd:enumeration value="false"/>
+ <xsd:enumeration value="yes"/>
+ <xsd:enumeration value="no"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="homeType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The homeType defines the fully-qualified name of
+ an enterprise bean's home interface.
+
+ Example:
+
+ <home>com.aardvark.payroll.PayrollHome</home>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="iconType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The icon type contains small-icon and large-icon elements
+ that specify the file names for small and large GIF, JPEG,
+ or PNG icon images used to represent the parent element in a
+ GUI tool.
+
+ The xml:lang attribute defines the language that the
+ icon file names are provided in. Its value is "en" (English)
+ by default.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="small-icon" type="javaee:pathType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The small-icon element contains the name of a file
+ containing a small (16 x 16) icon image. The file
+ name is a relative path within the Deployment
+ Component's Deployment File.
+
+ The image may be in the GIF, JPEG, or PNG format.
+ The icon can be used by tools.
+
+ Example:
+
+ <small-icon>employee-service-icon16x16.jpg</small-icon>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="large-icon" type="javaee:pathType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The large-icon element contains the name of a file
+ containing a large
+ (32 x 32) icon image. The file name is a relative
+ path within the Deployment Component's Deployment
+ File.
+
+ The image may be in the GIF, JPEG, or PNG format.
+ The icon can be used by tools.
+
+ Example:
+
+ <large-icon>employee-service-icon32x32.jpg</large-icon>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ </xsd:sequence>
+
+ <xsd:attribute ref="xml:lang"/>
+ <xsd:attribute name="id" type="xsd:ID"/>
+
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="injection-targetType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ An injection target specifies a class and a name within
+ that class into which a resource should be injected.
+
+ The injection target class specifies the fully qualified
+ class name that is the target of the injection. The
+ Java EE specifications describe which classes can be an
+ injection target.
+
+ The injection target name specifies the target within
+ the specified class. The target is first looked for as a
+ JavaBeans property name. If not found, the target is
+ looked for as a field name.
+
+ The specified resource will be injected into the target
+ during initialization of the class by either calling the
+ set method for the target property or by setting a value
+ into the named field.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="injection-target-class"
+ type="javaee:fully-qualified-classType"/>
+ <xsd:element name="injection-target-name"
+ type="javaee:java-identifierType"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="java-identifierType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The java-identifierType defines a Java identifier.
+ The users of this type should further verify that
+ the content does not contain Java reserved keywords.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:pattern value="($|_|\p{L})(\p{L}|\p{Nd}|_|$)*"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="java-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This is a generic type that designates a Java primitive
+ type or a fully qualified name of a Java interface/type,
+ or an array of such types.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:pattern value="[^\p{Z}]*"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jndi-nameType type designates a JNDI name in the
+ Deployment Component's environment and is relative to the
+ java:comp/env context. A JNDI name must be unique within the
+ Deployment Component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:group name="jndiEnvironmentRefsGroup">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This group keeps the usage of the contained JNDI environment
+ reference elements consistent across Java EE deployment descriptors.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="env-entry"
+ type="javaee:env-entryType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="ejb-ref"
+ type="javaee:ejb-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="ejb-local-ref"
+ type="javaee:ejb-local-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:group ref="javaee:service-refGroup"/>
+ <xsd:element name="resource-ref"
+ type="javaee:resource-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="resource-env-ref"
+ type="javaee:resource-env-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="message-destination-ref"
+ type="javaee:message-destination-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="persistence-context-ref"
+ type="javaee:persistence-context-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="persistence-unit-ref"
+ type="javaee:persistence-unit-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="post-construct"
+ type="javaee:lifecycle-callbackType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="pre-destroy"
+ type="javaee:lifecycle-callbackType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:group>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="lifecycle-callbackType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The lifecycle-callback type specifies a method on a
+ class to be called when a lifecycle event occurs.
+ Note that each class may have only one lifecycle callback
+ method for any given event and that the method may not
+ be overloaded.
+
+ If the lifefycle-callback-class element is missing then
+ the class defining the callback is assumed to be the
+ component class in scope at the place in the descriptor
+ in which the callback definition appears.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="lifecycle-callback-class"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0"/>
+ <xsd:element name="lifecycle-callback-method"
+ type="javaee:java-identifierType"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="listenerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The listenerType indicates the deployment properties for a web
+ application listener bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="listener-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The listener-class element declares a class in the
+ application must be registered as a web
+ application listener bean. The value is the fully
+ qualified classname of the listener class.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="local-homeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The local-homeType defines the fully-qualified
+ name of an enterprise bean's local home interface.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="localType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The localType defines the fully-qualified name of an
+ enterprise bean's local interface.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-destination-linkType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-linkType is used to link a message
+ destination reference or message-driven bean to a message
+ destination.
+
+ The Assembler sets the value to reflect the flow of messages
+ between producers and consumers in the application.
+
+ The value must be the message-destination-name of a message
+ destination in the same Deployment File or in another
+ Deployment File in the same Java EE application unit.
+
+ Alternatively, the value may be composed of a path name
+ specifying a Deployment File containing the referenced
+ message destination with the message-destination-name of the
+ destination appended and separated from the path name by
+ "#". The path name is relative to the Deployment File
+ containing Deployment Component that is referencing the
+ message destination. This allows multiple message
+ destinations with the same name to be uniquely identified.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-destination-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The message-destination-ref element contains a declaration
+ of Deployment Component's reference to a message destination
+ associated with a resource in Deployment Component's
+ environment. It consists of:
+
+ - an optional description
+ - the message destination reference name
+ - an optional message destination type
+ - an optional specification as to whether
+ the destination is used for
+ consuming or producing messages, or both.
+ if not specified, "both" is assumed.
+ - an optional link to the message destination
+ - optional injection targets
+
+ The message destination type must be supplied unless an
+ injection target is specified, in which case the type
+ of the target is used. If both are specified, the type
+ must be assignment compatible with the type of the injection
+ target.
+
+ Examples:
+
+ <message-destination-ref>
+ <message-destination-ref-name>jms/StockQueue
+ </message-destination-ref-name>
+ <message-destination-type>javax.jms.Queue
+ </message-destination-type>
+ <message-destination-usage>Consumes
+ </message-destination-usage>
+ <message-destination-link>CorporateStocks
+ </message-destination-link>
+ </message-destination-ref>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="message-destination-ref-name"
+ type="javaee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies
+ the name of a message destination reference; its
+ value is the environment entry name used in
+ Deployment Component code. The name is a JNDI name
+ relative to the java:comp/env context and must be
+ unique within an ejb-jar (for enterprise beans) or a
+ Deployment File (for others).
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="message-destination-type"
+ type="javaee:message-destination-typeType"
+ minOccurs="0"/>
+ <xsd:element name="message-destination-usage"
+ type="javaee:message-destination-usageType"
+ minOccurs="0"/>
+ <xsd:element name="message-destination-link"
+ type="javaee:message-destination-linkType"
+ minOccurs="0"/>
+
+ <xsd:group ref="javaee:resourceGroup"/>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-destination-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The message-destination-typeType specifies the type of
+ the destination. The type is specified by the Java interface
+ expected to be implemented by the destination.
+
+ Example:
+
+ <message-destination-type>javax.jms.Queue
+ </message-destination-type>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-destination-usageType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-usageType specifies the use of the
+ message destination indicated by the reference. The value
+ indicates whether messages are consumed from the message
+ destination, produced for the destination, or both. The
+ Assembler makes use of this information in linking producers
+ of a destination with its consumers.
+
+ The value of the message-destination-usage element must be
+ one of the following:
+ Consumes
+ Produces
+ ConsumesProduces
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="Consumes"/>
+ <xsd:enumeration value="Produces"/>
+ <xsd:enumeration value="ConsumesProduces"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="message-destinationType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The message-destinationType specifies a message
+ destination. The logical destination described by this
+ element is mapped to a physical destination by the Deployer.
+
+ The message destination element contains:
+
+ - an optional description
+ - an optional display-name
+ - an optional icon
+ - a message destination name which must be unique
+ among message destination names within the same
+ Deployment File.
+ - an optional mapped name
+
+ Example:
+
+ <message-destination>
+ <message-destination-name>CorporateStocks
+ </message-destination-name>
+ </message-destination>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="message-destination-name"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-name element specifies a
+ name for a message destination. This name must be
+ unique among the names of message destinations
+ within the Deployment File.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="mapped-name"
+ type="javaee:xsdStringType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ A product specific name that this message destination
+ should be mapped to. Each message-destination-ref
+ element that references this message destination will
+ define a name in the namespace of the referencing
+ component. (It's a name in the JNDI java:comp/env
+ namespace.) Many application servers provide a way to
+ map these local names to names of resources known to the
+ application server. This mapped name is often a global
+ JNDI name, but may be a name of any form. Each of the
+ local names should be mapped to this same global name.
+
+ Application servers are not required to support any
+ particular form or type of mapped name, nor the ability
+ to use mapped names. The mapped name is
+ product-dependent and often installation-dependent. No
+ use of a mapped name is portable.
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="param-valueType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type is a general type that can be used to declare
+ parameter/value lists.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="param-name"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The param-name element contains the name of a
+ parameter.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="param-value"
+ type="javaee:xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The param-value element contains the value of a
+ parameter.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The elements that use this type designate either a relative
+ path or an absolute path starting with a "/".
+
+ In elements that specify a pathname to a file within the
+ same Deployment File, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the Deployment File's namespace. Absolute filenames (i.e.,
+ those starting with "/") also specify names in the root of
+ the Deployment File's namespace. In general, relative names
+ are preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="persistence-context-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The persistence-context-ref element contains a declaration
+ of Deployment Component's reference to a persistence context
+ associated within a Deployment Component's
+ environment. It consists of:
+
+ - an optional description
+ - the persistence context reference name
+ - an optional persistence unit name. If not specified,
+ the default persistence unit is assumed.
+ - an optional specification as to whether
+ the persistence context type is Transaction or
+ Extended. If not specified, Transaction is assumed.
+ - an optional list of persistence properties
+ - optional injection targets
+
+ Examples:
+
+ <persistence-context-ref>
+ <persistence-context-ref-name>myPersistenceContext
+ </persistence-context-ref-name>
+ </persistence-context-ref>
+
+ <persistence-context-ref>
+ <persistence-context-ref-name>myPersistenceContext
+ </persistence-context-ref-name>
+ <persistence-unit-name>PersistenceUnit1
+ </persistence-unit-name>
+ <persistence-context-type>Extended</persistence-context-type>
+ </persistence-context-ref>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="persistence-context-ref-name"
+ type="javaee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The persistence-context-ref-name element specifies
+ the name of a persistence context reference; its
+ value is the environment entry name used in
+ Deployment Component code. The name is a JNDI name
+ relative to the java:comp/env context.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="persistence-unit-name"
+ type="javaee:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The Application Assembler(or BeanProvider) may use the
+ following syntax to avoid the need to rename persistence
+ units to have unique names within a Java EE application.
+
+ The Application Assembler specifies the pathname of the
+ root of the persistence.xml file for the referenced
+ persistence unit and appends the name of the persistence
+ unit separated from the pathname by #. The pathname is
+ relative to the referencing application component jar file.
+ In this manner, multiple persistence units with the same
+ persistence unit name may be uniquely identified when the
+ Application Assembler cannot change persistence unit names.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="persistence-context-type"
+ type="javaee:persistence-context-typeType"
+ minOccurs="0"/>
+
+ <xsd:element name="persistence-property"
+ type="javaee:propertyType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Used to specify properties for the container or persistence
+ provider. Vendor-specific properties may be included in
+ the set of properties. Properties that are not recognized
+ by a vendor must be ignored. Entries that make use of the
+ namespace javax.persistence and its subnamespaces must not
+ be used for vendor-specific properties. The namespace
+ javax.persistence is reserved for use by the specification.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:group ref="javaee:resourceGroup"/>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="persistence-context-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The persistence-context-typeType specifies the transactional
+ nature of a persistence context reference.
+
+ The value of the persistence-context-type element must be
+ one of the following:
+ Transaction
+ Extended
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="Transaction"/>
+ <xsd:enumeration value="Extended"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="persistence-unit-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The persistence-unit-ref element contains a declaration
+ of Deployment Component's reference to a persistence unit
+ associated within a Deployment Component's
+ environment. It consists of:
+
+ - an optional description
+ - the persistence unit reference name
+ - an optional persistence unit name. If not specified,
+ the default persistence unit is assumed.
+ - optional injection targets
+
+ Examples:
+
+ <persistence-unit-ref>
+ <persistence-unit-ref-name>myPersistenceUnit
+ </persistence-unit-ref-name>
+ </persistence-unit-ref>
+
+ <persistence-unit-ref>
+ <persistence-unit-ref-name>myPersistenceUnit
+ </persistence-unit-ref-name>
+ <persistence-unit-name>PersistenceUnit1
+ </persistence-unit-name>
+ </persistence-unit-ref>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="persistence-unit-ref-name"
+ type="javaee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The persistence-unit-ref-name element specifies
+ the name of a persistence unit reference; its
+ value is the environment entry name used in
+ Deployment Component code. The name is a JNDI name
+ relative to the java:comp/env context.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="persistence-unit-name"
+ type="javaee:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The Application Assembler(or BeanProvider) may use the
+ following syntax to avoid the need to rename persistence
+ units to have unique names within a Java EE application.
+
+ The Application Assembler specifies the pathname of the
+ root of the persistence.xml file for the referenced
+ persistence unit and appends the name of the persistence
+ unit separated from the pathname by #. The pathname is
+ relative to the referencing application component jar file.
+ In this manner, multiple persistence units with the same
+ persistence unit name may be uniquely identified when the
+ Application Assembler cannot change persistence unit names.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:group ref="javaee:resourceGroup"/>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="propertyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Specifies a name/value pair.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="name"
+ type="javaee:xsdStringType">
+ </xsd:element>
+ <xsd:element name="value"
+ type="javaee:xsdStringType">
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="remoteType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The remote element contains the fully-qualified name
+ of the enterprise bean's remote interface.
+
+ Example:
+
+ <remote>com.wombat.empl.EmployeeService</remote>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="res-authType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-authType specifies whether the Deployment Component
+ code signs on programmatically to the resource manager, or
+ whether the Container will sign on to the resource manager
+ on behalf of the Deployment Component. In the latter case,
+ the Container uses information that is supplied by the
+ Deployer.
+
+ The value must be one of the two following:
+
+ Application
+ Container
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="Application"/>
+ <xsd:enumeration value="Container"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="res-sharing-scopeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-sharing-scope type specifies whether connections
+ obtained through the given resource manager connection
+ factory reference can be shared. The value, if specified,
+ must be one of the two following:
+
+ Shareable
+ Unshareable
+
+ The default value is Shareable.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="Shareable"/>
+ <xsd:enumeration value="Unshareable"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="resource-env-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The resource-env-refType is used to define
+ resource-env-type elements. It contains a declaration of a
+ Deployment Component's reference to an administered object
+ associated with a resource in the Deployment Component's
+ environment. It consists of an optional description, the
+ resource environment reference name, and an optional
+ indication of the resource environment reference type
+ expected by the Deployment Component code.
+
+ It also includes optional elements to define injection of
+ the named resource into fields or JavaBeans properties.
+
+ The resource environment type must be supplied unless an
+ injection target is specified, in which case the type
+ of the target is used. If both are specified, the type
+ must be assignment compatible with the type of the injection
+ target.
+
+ Example:
+
+ <resource-env-ref>
+ <resource-env-ref-name>jms/StockQueue
+ </resource-env-ref-name>
+ <resource-env-ref-type>javax.jms.Queue
+ </resource-env-ref-type>
+ </resource-env-ref>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="resource-env-ref-name"
+ type="javaee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name
+ of a resource environment reference; its value is
+ the environment entry name used in
+ the Deployment Component code. The name is a JNDI
+ name relative to the java:comp/env context and must
+ be unique within a Deployment Component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="resource-env-ref-type"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-type element specifies the type
+ of a resource environment reference. It is the
+ fully qualified name of a Java language class or
+ interface.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:group ref="javaee:resourceGroup"/>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="resource-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The resource-refType contains a declaration of a
+ Deployment Component's reference to an external resource. It
+ consists of an optional description, the resource manager
+ connection factory reference name, an optional indication of
+ the resource manager connection factory type expected by the
+ Deployment Component code, an optional type of authentication
+ (Application or Container), and an optional specification of
+ the shareability of connections obtained from the resource
+ (Shareable or Unshareable).
+
+ It also includes optional elements to define injection of
+ the named resource into fields or JavaBeans properties.
+
+ The connection factory type must be supplied unless an
+ injection target is specified, in which case the type
+ of the target is used. If both are specified, the type
+ must be assignment compatible with the type of the injection
+ target.
+
+ Example:
+
+ <resource-ref>
+ <res-ref-name>jdbc/EmployeeAppDB</res-ref-name>
+ <res-type>javax.sql.DataSource</res-type>
+ <res-auth>Container</res-auth>
+ <res-sharing-scope>Shareable</res-sharing-scope>
+ </resource-ref>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="res-ref-name"
+ type="javaee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference.
+ The name is a JNDI name relative to the
+ java:comp/env context.
+ The name must be unique within a Deployment File.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="res-type"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-type element specifies the type of the data
+ source. The type is specified by the fully qualified
+ Java language class or interface
+ expected to be implemented by the data source.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="res-auth"
+ type="javaee:res-authType"
+ minOccurs="0"/>
+
+ <xsd:element name="res-sharing-scope"
+ type="javaee:res-sharing-scopeType"
+ minOccurs="0"/>
+
+ <xsd:group ref="javaee:resourceGroup"/>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:group name="resourceGroup">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This group collects elements that are common to all the
+ JNDI resource elements.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="mapped-name"
+ type="javaee:xsdStringType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ A product specific name that this resource should be
+ mapped to. The name of this resource, as defined by the
+ resource's name element or defaulted, is a name that is
+ local to the application component using the resource.
+ (It's a name in the JNDI java:comp/env namespace.) Many
+ application servers provide a way to map these local
+ names to names of resources known to the application
+ server. This mapped name is often a global JNDI name,
+ but may be a name of any form.
+
+ Application servers are not required to support any
+ particular form or type of mapped name, nor the ability
+ to use mapped names. The mapped name is
+ product-dependent and often installation-dependent. No
+ use of a mapped name is portable.
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="injection-target"
+ type="javaee:injection-targetType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:group>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="role-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The role-nameType designates the name of a security role.
+
+ The name must conform to the lexical rules for a token.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="run-asType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The run-asType specifies the run-as identity to be
+ used for the execution of a component. It contains an
+ optional description, and the name of a security role.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="role-name"
+ type="javaee:role-nameType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="security-role-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The security-role-refType contains the declaration of a
+ security role reference in a component's or a
+ Deployment Component's code. The declaration consists of an
+ optional description, the security role name used in the
+ code, and an optional link to a security role. If the
+ security role is not specified, the Deployer must choose an
+ appropriate security role.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="role-name"
+ type="javaee:role-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The value of the role-name element must be the String used
+ as the parameter to the
+ EJBContext.isCallerInRole(String roleName) method or the
+ HttpServletRequest.isUserInRole(String role) method.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="role-link"
+ type="javaee:role-nameType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The role-link element is a reference to a defined
+ security role. The role-link element must contain
+ the name of one of the security roles defined in the
+ security-role elements.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="security-roleType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The security-roleType contains the definition of a security
+ role. The definition consists of an optional description of
+ the security role, and the security role name.
+
+ Example:
+
+ <security-role>
+ <description>
+ This role includes all employees who are authorized
+ to access the employee service application.
+ </description>
+ <role-name>employee</role-name>
+ </security-role>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="role-name"
+ type="javaee:role-nameType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This is a special string datatype that is defined by Java EE as
+ a base type for defining collapsed strings. When schemas
+ require trailing/leading space elimination as well as
+ collapsing the existing whitespace, this base type may be
+ used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:token">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="true-falseType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This simple type designates a boolean with only two
+ permissible values
+
+ - true
+ - false
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:xsdBooleanType">
+ <xsd:pattern value="(true|false)"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="url-patternType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The url-patternType contains the url pattern of the mapping.
+ It must follow the rules specified in Section 11.2 of the
+ Servlet API Specification. This pattern is assumed to be in
+ URL-decoded form and must not contain CR(#xD) or LF(#xA).
+ If it contains those characters, the container must inform
+ the developer with a descriptive error message.
+ The container must preserve all characters including whitespaces.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdAnyURIType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:anyURI.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:anyURI">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdBooleanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:boolean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:boolean">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdIntegerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:integer.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:integer">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdNMTOKENType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:NMTOKEN.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:NMTOKEN">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdNonNegativeIntegerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:nonNegativeInteger.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:nonNegativeInteger">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdPositiveIntegerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:positiveInteger.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:positiveInteger">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdQNameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:QName.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:QName">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="xsdStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type adds an "id" attribute to xsd:string.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="xsd:string">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_web_services_1_2.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_web_services_1_2.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_web_services_1_2.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,747 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.2">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)javaee_web_services_1_2.xsds 1.18 02/13/06
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003-2006 Sun Microsystems, Inc.
+ 4150 Network Circle
+ Santa Clara, California 95054
+ U.S.A
+ All rights reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ (C) Copyright International Business Machines Corporation 2002
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The webservices element is the root element for the web services
+ deployment descriptor. It specifies the set of web service
+ descriptions that are to be deployed into the Java EE Application
+ Server and the dependencies they have on container resources and
+ services. The deployment descriptor must be named
+ "META-INF/webservices.xml" in the web services' jar file.
+
+ Used in: webservices.xml
+
+ All webservices deployment descriptors must indicate the
+ webservices schema by using the Java EE namespace:
+
+ http://java.sun.com/xml/ns/javaee
+
+ and by indicating the version of the schema by using the version
+ element as shown below:
+
+ <webservices xmlns="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
+ http://java.sun.com/xml/ns/javaee/javaee_web_services_1_2.xsd"
+ version="1.2">
+ ...
+ </webservices>
+
+ The instance documents may indicate the published version of the
+ schema using the xsi:schemaLocation attribute for the Java EE
+ namespace with the following location:
+
+ http://java.sun.com/xml/ns/javaee/javaee_web_services_1_2.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all Java EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="javaee_5.xsd"/>
+
+
+<!-- **************************************************** -->
+
+ <xsd:element name="webservices" type="javaee:webservicesType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The webservices element is the root element for the web services
+ deployment descriptor. It specifies the set of web service
+ descriptions that are to be deployed into the Java EE Application Server
+ and the dependencies they have on container resources and services.
+
+ Used in: webservices.xml
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:key name="webservice-description-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The webservice-description-name identifies the collection of
+ port-components associated with a WSDL file and JAX-RPC mapping. The
+ name must be unique within the deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:webservice-description"/>
+ <xsd:field xpath="javaee:webservice-description-name"/>
+ </xsd:key>
+ </xsd:element>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="handler-chainType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The handler-chain element defines the handlerchain.
+ Handlerchain can be defined such that the handlers in the
+ handlerchain operate,all ports of a service, on a specific
+ port or on a list of protocol-bindings. The choice of elements
+ service-name-pattern, port-name-pattern and protocol-bindings
+ are used to specify whether the handlers in handler-chain are
+ for a service, port or protocol binding. If none of these
+ choices are specified with the handler-chain element then the
+ handlers specified in the handler-chain will be applied on
+ everything.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+
+ <xsd:choice minOccurs="0" maxOccurs="1">
+ <xsd:element name="service-name-pattern"
+ type="javaee:qname-pattern" />
+ <xsd:element name="port-name-pattern"
+ type="javaee:qname-pattern" />
+ <xsd:element name="protocol-bindings"
+ type="javaee:protocol-bindingListType"/>
+ </xsd:choice>
+
+ <xsd:element name="handler"
+ type="javaee:port-component_handlerType"
+ minOccurs="1" maxOccurs="unbounded"/>
+ </xsd:sequence>
+
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="handler-chainsType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The handler-chains element defines the handlerchains associated
+ with this service or service endpoint.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="handler-chain"
+ type="javaee:handler-chainType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="port-componentType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component element associates a WSDL port with a web service
+ interface and implementation. It defines the name of the port as a
+ component, optional description, optional display name, optional iconic
+ representations, WSDL port QName, Service Endpoint Interface, Service
+ Implementation Bean.
+
+ This element also associates a WSDL service with a JAX-WS Provider
+ implementation.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="display-name"
+ type="javaee:display-nameType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="icon"
+ type="javaee:iconType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="port-component-name"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The port-component-name element specifies a port component's
+ name. This name is assigned by the module producer to name
+ the service implementation bean in the module's deployment
+ descriptor. The name must be unique among the port component
+ names defined in the same module.
+
+ Used in: port-component
+
+ Example:
+ <port-component-name>EmployeeService
+ </port-component-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-service"
+ type="javaee:xsdQNameType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name space and local name part of the WSDL
+ service QName. This is required to be specified for
+ port components that are JAX-WS Provider implementations.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-port"
+ type="javaee:xsdQNameType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name space and local name part of the WSDL
+ port QName. This is not required to be specified for port
+ components that are JAX-WS Provider implementations
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="enable-mtom"
+ type="javaee:true-falseType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Used to enable or disable SOAP MTOM/XOP mechanism for an
+ endpoint implementation.
+
+ Not to be specified for JAX-RPC runtime
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="protocol-binding"
+ type="javaee:protocol-bindingType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Used to specify the protocol binding used by the port-component.
+ If this element is not specified, then the default binding is
+ used (SOAP 1.1 over HTTP)
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="service-endpoint-interface"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The service-endpoint-interface element contains the
+ fully-qualified name of the port component's Service Endpoint
+ Interface.
+
+ Used in: port-component
+
+ Example:
+ <remote>com.wombat.empl.EmployeeService</remote>
+
+ This may not be specified in case there is no Service
+ Enpoint Interface as is the case with directly using an
+ implementation class with the @WebService annotation.
+
+ When the port component is a Provider implementation
+ this is not specified.
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="service-impl-bean"
+ type="javaee:service-impl-beanType"/>
+
+ <xsd:choice>
+ <xsd:element name="handler"
+ type="javaee:port-component_handlerType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+ To be used with JAX-RPC based runtime only.
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="handler-chains"
+ type="javaee:handler-chainsType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+ To be used with JAX-WS based runtime only.
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:choice>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="port-component_handlerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Declares the handler for a port-component. Handlers can access the
+ init-param name/value pairs using the HandlerInfo interface.
+
+ Used in: port-component
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="handler-name"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique within the
+ module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="handler-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines a fully qualified class name for the handler implementation.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="init-param"
+ type="javaee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded"/>
+
+ <xsd:element name="soap-header"
+ type="javaee:xsdQNameType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the QName of a SOAP header that will be processed by the
+ handler.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="soap-role"
+ type="javaee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The soap-role element contains a SOAP actor definition that the
+ Handler will play as a role.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="protocol-URIAliasType">
+ <xsd:annotation>
+ <xsd:documentation>
+ Defines the type that is used for specifying tokens that
+ start with ## which are used to alias existing standard
+ protocol bindings and support aliases for new standard
+ binding URIs that are introduced in future specifications.
+
+ The following tokens alias the standard protocol binding
+ URIs:
+
+ ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
+ ##SOAP11_HTTP_MTOM =
+ "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
+ ##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
+ ##SOAP12_HTTP_MTOM =
+ "http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
+ ##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http"
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:pattern value="##.+"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="protocol-bindingListType">
+ <xsd:annotation>
+ <xsd:documentation>
+ Defines the type used for specifying a list of
+ protocol-bindingType(s). For e.g.
+
+ ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:list itemType="javaee:protocol-bindingType"/>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="protocol-bindingType">
+ <xsd:annotation>
+ <xsd:documentation>
+ Defines the type used for specifying the URI for the
+ protocol binding used by the port-component. For
+ portability one could use one of the following tokens that
+ alias the standard binding types:
+
+ ##SOAP11_HTTP
+ ##SOAP11_HTTP_MTOM
+ ##SOAP12_HTTP
+ ##SOAP12_HTTP_MTOM
+ ##XML_HTTP
+
+ Other specifications could define tokens that start with ##
+ to alias new standard binding URIs that are introduced.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:union memberTypes="xsd:anyURI javaee:protocol-URIAliasType"/>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="qname-pattern">
+ <xsd:annotation>
+ <xsd:documentation>
+ This is used to specify the QName pattern in the
+ attribute service-name-pattern and port-name-pattern in
+ the handler-chain element
+
+ For example, the various forms acceptable here for
+ service-name-pattern attribute in handler-chain element
+ are :
+
+ Exact Name: service-name-pattern="ns1:EchoService"
+
+ In this case, handlers specified in this
+ handler-chain element will apply to all ports with
+ this exact service name. The namespace prefix must
+ have been declared in a namespace declaration
+ attribute in either the start-tag of the element
+ where the prefix is used or in an an ancestor
+ element (i.e. an element in whose content the
+ prefixed markup occurs)
+
+ Pattern : service-name-pattern="ns1:EchoService*"
+
+ In this case, handlers specified in this
+ handler-chain element will apply to all ports whose
+ Service names are like EchoService1, EchoServiceFoo
+ etc. The namespace prefix must have been declared in
+ a namespace declaration attribute in either the
+ start-tag of the element where the prefix is used or
+ in an an ancestor element (i.e. an element in whose
+ content the prefixed markup occurs)
+
+ Wild Card : service-name-pattern="*"
+
+ In this case, handlers specified in this handler-chain
+ element will apply to ports of all service names.
+
+ The same can be applied to port-name attribute in
+ handler-chain element.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:restriction base="xsd:token">
+ <xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
+ </xsd:restriction>
+
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="service-impl-beanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-impl-bean element defines the web service implementation.
+ A service implementation can be an EJB bean class or JAX-RPC web
+ component. Existing EJB implementations are exposed as a web service
+ using an ejb-link.
+
+ Used in: port-component
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:choice>
+ <xsd:element name="ejb-link"
+ type="javaee:ejb-linkType"/>
+ <xsd:element name="servlet-link"
+ type="javaee:servlet-linkType"/>
+ </xsd:choice>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="servlet-linkType">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The servlet-link element is used in the service-impl-bean element
+ to specify that a Service Implementation Bean is defined as a
+ JAX-RPC Service Endpoint.
+
+ The value of the servlet-link element must be the servlet-name of
+ a JAX-RPC Service Endpoint in the same WAR file.
+
+ Used in: service-impl-bean
+
+ Example:
+ <servlet-link>StockQuoteService</servlet-link>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="webservice-descriptionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The webservice-description element defines a WSDL document file
+ and the set of Port components associated with the WSDL ports
+ defined in the WSDL document. There may be multiple
+ webservice-descriptions defined within a module.
+
+ All WSDL file ports must have a corresponding port-component element
+ defined.
+
+ Used in: webservices
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="display-name"
+ type="javaee:display-nameType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="icon"
+ type="javaee:iconType"
+ minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="webservice-description-name"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The webservice-description-name identifies the collection of
+ port-components associated with a WSDL file and JAX-RPC
+ mapping. The name must be unique within the deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="wsdl-file"
+ type="javaee:pathType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-file element contains the name of a WSDL file in the
+ module. The file name is a relative path within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="jaxrpc-mapping-file"
+ type="javaee:pathType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jaxrpc-mapping-file element contains the name of a file that
+ describes the JAX-RPC mapping between the Java interaces used by
+ the application and the WSDL description in the wsdl-file. The
+ file name is a relative path within the module.
+
+ This is not required when JAX-WS based runtime is used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="port-component"
+ type="javaee:port-componentType"
+ minOccurs="1" maxOccurs="unbounded">
+ <xsd:key name="port-component_handler-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique
+ within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:handler"/>
+ <xsd:field xpath="javaee:handler-name"/>
+ </xsd:key>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="webservicesType">
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="webservice-description"
+ type="javaee:webservice-descriptionType"
+ minOccurs="1" maxOccurs="unbounded">
+ <xsd:key name="port-component-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ The port-component-name element specifies a port
+ component's name. This name is assigned by the module
+ producer to name the service implementation bean in the
+ module's deployment descriptor. The name must be unique
+ among the port component names defined in the same module.
+
+ Used in: port-component
+
+ Example:
+ <port-component-name>EmployeeService
+ </port-component-name>
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:port-component"/>
+ <xsd:field xpath="javaee:port-component-name"/>
+ </xsd:key>
+ </xsd:element>
+ </xsd:sequence>
+
+ <xsd:attribute name="version"
+ type="javaee:dewey-versionType"
+ fixed="1.2"
+ use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The required value for the version is 1.2.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_web_services_client_1_2.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_web_services_client_1_2.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/javaee_web_services_client_1_2.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,578 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.2">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)javaee_web_services_client_1_2.xsds 1.19 02/13/06
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003-2006 Sun Microsystems, Inc.
+ 4150 Network Circle
+ Santa Clara, California 95054
+ U.S.A
+ All rights reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ (C) Copyright International Business Machines Corporation 2002
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="port-component-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component-ref element declares a client dependency
+ on the container for resolving a Service Endpoint Interface
+ to a WSDL port. It optionally associates the Service Endpoint
+ Interface with a particular port-component. This is only used
+ by the container for a Service.getPort(Class) method call.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="service-endpoint-interface"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-endpoint-interface element defines a fully qualified
+ Java class that represents the Service Endpoint Interface of a
+ WSDL port.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="enable-mtom"
+ type="javaee:true-falseType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Used to enable or disable SOAP MTOM/XOP mechanism on the client
+ side for a port-component.
+
+ Not to be specified for JAX-RPC runtime
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="port-component-link"
+ type="javaee:string"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component-link element links a port-component-ref
+ to a specific port-component required to be made available
+ by a service reference.
+
+ The value of a port-component-link must be the
+ port-component-name of a port-component in the same module
+ or another module in the same application unit. The syntax
+ for specification follows the syntax defined for ejb-link
+ in the EJB 2.0 specification.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:group name="service-refGroup">
+ <xsd:sequence>
+ <xsd:element name="service-ref"
+ type="javaee:service-refType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:key name="service-ref_handler-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique
+ within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:handler"/>
+ <xsd:field xpath="javaee:handler-name"/>
+ </xsd:key>
+ </xsd:element>
+ </xsd:sequence>
+ </xsd:group>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="service-refType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-ref element declares a reference to a Web
+ service. It contains optional description, display name and
+ icons, a declaration of the required Service interface,
+ an optional WSDL document location, an optional set
+ of JAX-RPC mappings, an optional QName for the service element,
+ an optional set of Service Endpoint Interfaces to be resolved
+ by the container to a WSDL port, and an optional set of handlers.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="service-ref-name"
+ type="javaee:jndi-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-ref-name element declares logical name that the
+ components in the module use to look up the Web service. It
+ is recommended that all service reference names start with
+ "service/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="service-interface"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-interface element declares the fully qualified class
+ name of the JAX-RPC Service interface the client depends on.
+ In most cases the value will be javax.xml.rpc.Service. A JAX-RPC
+ generated Service Interface class may also be specified.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="service-ref-type"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-ref-type element declares the type of the service-ref
+ element that is injected or returned when a JNDI lookup is done.
+ This must be either a fully qualified name of Service class or
+ the fully qualified name of service endpoint interface class.
+ This is only used with JAX-WS runtime where the corresponding
+ @WebServiceRef annotation can be used to denote both a Service
+ or a Port.
+
+ If this is not specified, then the type of service-ref element
+ that is injected or returned when a JNDI lookup is done is
+ always a Service interface/class.
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="wsdl-file"
+ type="javaee:xsdAnyURIType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The wsdl-file element contains the URI location of a WSDL
+ file. The location is relative to the root of the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="jaxrpc-mapping-file"
+ type="javaee:pathType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jaxrpc-mapping-file element contains the name of a file that
+ describes the JAX-RPC mapping between the Java interaces used by
+ the application and the WSDL description in the wsdl-file. The
+ file name is a relative path within the module file.
+
+ This is not required when JAX-WS based runtime is used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="service-qname"
+ type="javaee:xsdQNameType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The service-qname element declares the specific WSDL service
+ element that is being refered to. It is not specified if no
+ wsdl-file is declared.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="port-component-ref"
+ type="javaee:port-component-refType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-component-ref element declares a client dependency
+ on the container for resolving a Service Endpoint Interface
+ to a WSDL port. It optionally associates the Service Endpoint
+ Interface with a particular port-component. This is only used
+ by the container for a Service.getPort(Class) method call.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:choice>
+ <xsd:element name="handler"
+ type="javaee:service-ref_handlerType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Declares the handler for a port-component. Handlers can
+ access the init-param name/value pairs using the
+ HandlerInfo interface. If port-name is not specified, the
+ handler is assumed to be associated with all ports of the
+ service.
+
+ To be used with JAX-RPC based runtime only.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="handler-chains"
+ type="javaee:service-ref_handler-chainsType"
+ minOccurs="0" maxOccurs="1">
+ <xsd:annotation>
+ <xsd:documentation>
+ To be used with JAX-WS based runtime only.
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:choice>
+
+ <xsd:group ref="javaee:resourceGroup"/>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="service-ref_handler-chainType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The handler-chain element defines the handlerchain.
+ Handlerchain can be defined such that the handlers in the
+ handlerchain operate,all ports of a service, on a specific
+ port or on a list of protocol-bindings. The choice of elements
+ service-name-pattern, port-name-pattern and protocol-bindings
+ are used to specify whether the handlers in handler-chain are
+ for a service, port or protocol binding. If none of these
+ choices are specified with the handler-chain element then the
+ handlers specified in the handler-chain will be applied on
+ everything.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+
+ <xsd:choice minOccurs="0" maxOccurs="1">
+ <xsd:element name="service-name-pattern"
+ type="javaee:service-ref_qname-pattern" />
+ <xsd:element name="port-name-pattern"
+ type="javaee:service-ref_qname-pattern" />
+ <xsd:element name="protocol-bindings"
+ type="javaee:service-ref_protocol-bindingListType"/>
+ </xsd:choice>
+
+ <xsd:element name="handler"
+ type="javaee:service-ref_handlerType"
+ minOccurs="1" maxOccurs="unbounded"/>
+ </xsd:sequence>
+
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="service-ref_handler-chainsType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The handler-chains element defines the handlerchains associated with this
+ service or service endpoint.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="handler-chain"
+ type="javaee:service-ref_handler-chainType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="service-ref_handlerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Declares the handler for a port-component. Handlers can access the
+ init-param name/value pairs using the HandlerInfo interface. If
+ port-name is not specified, the handler is assumed to be associated
+ with all ports of the service.
+
+ Used in: service-ref
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="handler-name"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the name of the handler. The name must be unique
+ within the module.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="handler-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines a fully qualified class name for the handler
+ implementation.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="init-param"
+ type="javaee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded"/>
+
+ <xsd:element name="soap-header"
+ type="javaee:xsdQNameType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the QName of a SOAP header that will be processed
+ by the handler.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="soap-role"
+ type="javaee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The soap-role element contains a SOAP actor definition that
+ the Handler will play as a role.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="port-name"
+ type="javaee:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The port-name element defines the WSDL port-name that a
+ handler should be associated with.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="service-ref_protocol-URIAliasType">
+ <xsd:annotation>
+ <xsd:documentation>
+ Defines the type that is used for specifying tokens that
+ start with ## which are used to alias existing standard
+ protocol bindings and support aliases for new standard
+ binding URIs that are introduced in future specifications.
+
+ The following tokens alias the standard protocol binding
+ URIs:
+
+ ##SOAP11_HTTP = "http://schemas.xmlsoap.org/wsdl/soap/http"
+ ##SOAP11_HTTP_MTOM =
+ "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"
+ ##SOAP12_HTTP = "http://www.w3.org/2003/05/soap/bindings/HTTP/"
+ ##SOAP12_HTTP_MTOM =
+ "http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true"
+ ##XML_HTTP = "http://www.w3.org/2004/08/wsdl/http"
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:pattern value="##.+"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="service-ref_protocol-bindingListType">
+ <xsd:annotation>
+ <xsd:documentation>
+ Defines the type used for specifying a list of
+ protocol-bindingType(s). For e.g.
+
+ ##SOAP11_HTTP ##SOAP12_HTTP ##XML_HTTP
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:list itemType="javaee:service-ref_protocol-bindingType"/>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="service-ref_protocol-bindingType">
+ <xsd:annotation>
+ <xsd:documentation>
+ Defines the type used for specifying the URI for the
+ protocol binding used by the port-component. For
+ portability one could use one of the following tokens that
+ alias the standard binding types:
+
+ ##SOAP11_HTTP
+ ##SOAP11_HTTP_MTOM
+ ##SOAP12_HTTP
+ ##SOAP12_HTTP_MTOM
+ ##XML_HTTP
+
+ Other specifications could define tokens that start with ##
+ to alias new standard binding URIs that are introduced.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:union memberTypes="xsd:anyURI javaee:service-ref_protocol-URIAliasType"/>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="service-ref_qname-pattern">
+ <xsd:annotation>
+ <xsd:documentation>
+ This is used to specify the QName pattern in the
+ attribute service-name-pattern and port-name-pattern in
+ the handler-chain element
+
+ For example, the various forms acceptable here for
+ service-name-pattern attribute in handler-chain element
+ are :
+
+ Exact Name: service-name-pattern="ns1:EchoService"
+
+ In this case, handlers specified in this
+ handler-chain element will apply to all ports with
+ this exact service name. The namespace prefix must
+ have been declared in a namespace declaration
+ attribute in either the start-tag of the element
+ where the prefix is used or in an an ancestor
+ element (i.e. an element in whose content the
+ prefixed markup occurs)
+
+ Pattern : service-name-pattern="ns1:EchoService*"
+
+ In this case, handlers specified in this
+ handler-chain element will apply to all ports whose
+ Service names are like EchoService1, EchoServiceFoo
+ etc. The namespace prefix must have been declared in
+ a namespace declaration attribute in either the
+ start-tag of the element where the prefix is used or
+ in an an ancestor element (i.e. an element in whose
+ content the prefixed markup occurs)
+
+ Wild Card : service-name-pattern="*"
+
+ In this case, handlers specified in this handler-chain
+ element will apply to ports of all service names.
+
+ The same can be applied to port-name attribute in
+ handler-chain element.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:restriction base="xsd:token">
+ <xsd:pattern value="\*|([\i-[:]][\c-[:]]*:)?[\i-[:]][\c-[:]]*\*?"/>
+ </xsd:restriction>
+
+ </xsd:simpleType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jbxb_1_0.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jbxb_1_0.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jbxb_1_0.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,425 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xs:schema version="1.0beta"
+ attributeFormDefault="unqualified"
+ elementFormDefault="qualified"
+ xmlns:jbxb="http://www.jboss.org/xml/ns/jbxb"
+ xmlns:xs="http://www.w3.org/2001/XMLSchema">
+ <xs:annotation>
+ <xs:documentation>The JBossXB schema customization
+ elements</xs:documentation>
+ </xs:annotation>
+ <xs:element name="schemaBindings">
+ <xs:annotation>
+ <xs:documentation>This element defines default bindings for the
+ schema</xs:documentation>
+ </xs:annotation>
+ <xs:complexType>
+ <!-- The child elements can be selected in any order. -->
+ <xs:choice maxOccurs="unbounded" minOccurs="1">
+ <xs:element maxOccurs="1" minOccurs="0" ref="jbxb:package"/>
+
+ <xs:element name="ignoreUnresolvedFieldOrClass" type="xs:boolean" default="true"
+ maxOccurs="1" minOccurs="0">
+ <xs:annotation>
+ <xs:documentation>The ignoreUnresolvedFieldOrClass specifies the behavior the parser chooses
+ when a field is not found in the parent class for a child value, or when an element does not have
+ any class assignement. If false, an exception will be thrown when either situation is encountered.
+ If true, the missing mapping is ignored and the parse continues.
+ </xs:documentation>
+ </xs:annotation>
+ </xs:element>
+
+ <xs:element name="replacePropertyRefs" type="xs:boolean" default="true"
+ maxOccurs="1" minOccurs="0">
+ <xs:annotation>
+ <xs:documentation>The replacePropertyRefs flag indicates whether the
+ text content of values has ${x} system property references replaced
+ during parsing. The default is true.
+ </xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ </xs:choice>
+ </xs:complexType>
+ </xs:element>
+ <xs:element name="package" type="xs:NCName">
+ <xs:annotation>
+ <xs:documentation> Defines the default package for the schema which
+ is used for searching classes when unmarshalling elements of
+ complex types. If jbxb:package is not present, schema's
+ namespace URI will be used as the base to generate the default
+ package name for the schema (the mapping is defined in JAXB2.0
+ spec D.5.1 Mapping from a Namespace URI). Example: <![CDATA[
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:schema>
+ <jbxb:package name="org.jboss.test.xml.pojoserver.metadata"/>
+ </jbxb:schema>
+ </xsd:appinfo>
+ </xsd:annotation>
+ ]]></xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ <xs:element name="characters">
+ <xs:annotation>
+ <xs:documentation> Binds text content of complex types. This element
+ is just a container for jbxb:value, jbxb:property,
+ jbxb:mapEntryKey, jbxb:mapEntryValue elements, all of them are
+ optional. This element can only appear inside complex type
+ definitions. Example: <![CDATA[
+ <xsd:complexType name="namedValueType" mixed="true">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:class impl="org.jboss.test.xml.pojoserver.metadata.AbstractPropertyMetaData"/>
+ <jbxb:characters>
+ <jbxb:property name="value"/>
+ <jbxb:value unmarshalMethod="org.jboss.test.xml.pojoserver.metadata.DataTypeConverter.unmarshalStringValue"/>
+ </jbxb:characters>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xsd:complexContent>
+ ...
+ </xsd:complexContent>
+ </xsd:complexType>
+ ]]></xs:documentation>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:choice>
+ <xs:element ref="jbxb:property"/>
+ <xs:element ref="jbxb:value"/>
+ <xs:element ref="jbxb:mapEntryKey"/>
+ <xs:element ref="jbxb:mapEntryValue"/>
+ </xs:choice>
+ </xs:complexType>
+ </xs:element>
+ <xs:element name="class" type="xs:NCName">
+ <xs:annotation>
+ <xs:documentation> Binds XML element or complex type to a Java class
+ which is specified as a value of attribute 'impl'. If jbxb:class
+ is used inside complex type definition, all elements of this
+ complex type will be unmarshalled into the specified Java type
+ unless there is overriding jbxb:class in an element declaration.
+ Example: <![CDATA[
+ <xsd:complexType name="deploymentType">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:class impl="org.jboss.test.xml.pojoserver.deployment.AbstractKernelDeployment"/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xsd:sequence>
+ ...
+ </xsd:sequence>
+ </xsd:complexType>
+
+ <xsd:element name="list" type="listType">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:class impl="org.jboss.test.xml.pojoserver.metadata.AbstractListMetaData"/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ </xsd:element>
+ ]]></xs:documentation>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:attribute name="impl" type="xs:NCName" use="required"/>
+ </xs:complexType>
+ </xs:element>
+ <xs:element name="property">
+ <xs:annotation>
+ <xs:documentation> Binds an element to property/field in a class.
+ This element can appear inside an element definition or inside
+ jbxb:characters. If jbxb:property is not specified for an
+ element, the property name is resolved based on the element's
+ name using "D.2 The Name to Identifier Mapping Algorithm"
+ defined in JAXB2.0 spec. Example: <![CDATA[
+ <xsd:element name="list" type="listType">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:property name="value"/>
+ <jbxb:class impl="org.jboss.test.xml.pojoserver.metadata.AbstractListMetaData"/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ </xsd:element>
+ ]]></xs:documentation>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:attribute name="name" type="xs:NCName" use="required"/>
+ </xs:complexType>
+ </xs:element>
+ <xs:element name="value">
+ <xs:annotation>
+ <xs:documentation> Binds text value (attribute value or text
+ content) to a Java value. There are two attributes:
+ unmarshalMethod which specfies a public static method that is
+ used to unmarshal text values and marshalMethod which also a
+ public static method that is used to marshal Java values. Both
+ methods are defined as concatenation of fully-qualified class
+ name, '.' and the method name. unmarshalMethod must have two
+ parameters: the first one of type java.lang.String and the
+ second one is of type javax.xml.namespace.NamespaceContext.
+ marshalMethod must also have two parameters: the first one is of
+ type java.lang.Object and the second one is of type
+ javax.xml.namespace.NamespaceContext. jbxb:value can appear
+ inside simple type definitions, attribute declarations and
+ jbxb:characters. If jbxb:value is not used, text values are
+ unmarshalled using default simple types to Java bindings
+ defained in JAXB2.0 spec. If simple type is a user-defined, by
+ default it is not unmarshalled and passed as a string. Example: <![CDATA[
+ <xsd:simpleType name="kernelControllerState">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:value unmarshalMethod="org.jboss.test.xml.pojoserver.metadata.KernelControllerStateDatatypeConverter.unmarshal"/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:string">
+ <xsd:enumeration value="Not Installed" />
+ <xsd:enumeration value="Described" />
+ <xsd:enumeration value="Instantiated" />
+ <xsd:enumeration value="Configured" />
+ <xsd:enumeration value="Lifecycle" />
+ <xsd:enumeration value="Started" />
+ <xsd:enumeration value="Installed" />
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ public class KernelControllerStateDatatypeConverter
+ {
+ public static KernelControllerState unmarshal(String text, NamespaceContext nsCtx)
+ {
+ KernelControllerState state;
+ if(KernelControllerState.NOT_INSTALLED.getStateString().equals(text))
+ {
+ state = KernelControllerState.NOT_INSTALLED;
+ }
+ else
+ ...
+ ]]></xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ <xs:element name="addMethod">
+ <xs:annotation>
+ <xs:documentation> Specified on an element that should be added to
+ its parent not with a setter (is not a property) and not with a
+ field but with a custom method. The attributes are: * name - the
+ name of the method. There is not default value for this
+ attribute. It must be set. * valueType - the type of the
+ argument. If not present, the default is java.lang.Object. And
+ there is a special value 'child' which means the type of the
+ child should be used as the argument's type. Example: <![CDATA[
+ <xs:element name="user">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:class impl="org.jboss.test.xml.mbeanserver.Users$User"/>
+ <jbxb:addMethod name="addUser" valueType="child"/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:element minOccurs="0" maxOccurs="unbounded" ref="ur:role"/>
+ </xs:sequence>
+ <xs:attribute name="name" use="required" type="xs:NCName"/>
+ <xs:attribute name="password" use="required" type="xs:NCName"/>
+ </xs:complexType>
+ </xs:element>
+ ]]></xs:documentation>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:attribute name="name" type="xs:NCName" use="required">
+ <xs:annotation>
+ <xs:documentation>This required attribute specifies the name
+ of the add method</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute default="java.lang.Object" name="valueType"
+ type="xs:NCName" use="optional">
+ <xs:annotation>
+ <xs:documentation> the type of the add method argument. If
+ not present, the default is java.lang.Object. And there
+ is a special value 'child' which means the type of the
+ child should be used as the argument's type.
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:complexType>
+ </xs:element>
+ <xs:element name="putMethod">
+ <xs:annotation>
+ <xs:documentation/>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:attribute default="put" name="name" type="xs:NCName"
+ use="optional">
+ <xs:annotation>
+ <xs:documentation> the method name in the parent object's
+ class that adds child to to its parent object. If not
+ present, the default is 'put'. </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute default="java.lang.Object" name="keyType"
+ type="xs:NCName" use="optional">
+ <xs:annotation>
+ <xs:documentation> fully qualified type name of the
+ key-parameter to the put-method. If not present, the
+ default is java.lang.Object. </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute default="java.lang.Object" name="valueType"
+ type="xs:NCName" use="optional">
+ <xs:annotation>
+ <xs:documentation>fully qualified type name of the
+ value-parameter to the put-method. If not present, the
+ default is java.lang.Object. </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:complexType>
+ </xs:element>
+ <xs:element name="mapEntry">
+ <xs:annotation>
+ <xs:documentation> Specified on an element or a complex type
+ definition that is bound to a map entry. jbxb:class and
+ jbxb:mapEntry are mutually exclusive, meanning an element or a
+ complex type cannot be annotated with both jbxb:class and
+ jbxb:mapEntry at the same time. Otherwise, it will result in an
+ exception during binding. </xs:documentation>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:attribute name="impl" type="xs:NCName" use="optional">
+ <xs:annotation>
+ <xs:documentation>an optional element that specifies a fully
+ qualified name of the class that will represent map
+ entry. If absent, a special class will be used by the
+ framework internally.</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute default="getKey" name="getKeyMethod" type="xs:NCName"
+ use="optional">
+ <xs:annotation>
+ <xs:documentation>an optional attribute that specifies the
+ name of the method that is used to get the key out of
+ the object that represents a map
+ entry.</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute default="setKey" name="setKeyMethod" type="xs:NCName"
+ use="optional">
+ <xs:annotation>
+ <xs:documentation>an optional attribute that specifies the
+ name of the method that is used to set the key value on
+ the object that represents a map
+ entry.</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute default="getValue" name="getValueMethod"
+ type="xs:NCName" use="optional">
+ <xs:annotation>
+ <xs:documentation>an optional element that specifies the
+ name of the method that is used to get the value out of
+ the object that represents a map entry. If absent and
+ impl attribute is absent too, the default value is
+ "getValue". If absent and impl attribute is present, the
+ value will be the object that reprents the map entry
+ itself.</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute default="setValue" name="setValueMethod"
+ type="xs:NCName" use="optional">
+ <xs:annotation>
+ <xs:documentation>an optional element that specifies the
+ name of the method that is used to set the value on the
+ object that represents a map entry.</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="valueType" type="xs:NCName" use="optional">
+ <xs:annotation>
+ <xs:documentation>an optional attribute that specifies the
+ type of the map entry value. Used when map entry value
+ should be a parent for element/type's
+ content.</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute default="false" name="nonNullValue" type="xs:boolean"
+ use="optional">
+ <xs:annotation>
+ <xs:documentation>If true, when a map entry is created, a
+ non-null map entry value will also be created and set on
+ the map entry. Otherwise, a map entry object is created
+ with null value and the value will be created and set
+ later when it is actually parsed. This attribute is used
+ in combination with valueType.</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:complexType>
+ </xs:element>
+ <xs:element name="mapEntryKey">
+ <xs:annotation>
+ <xs:documentation>This element is a marker element that has no
+ attributes. It is specified on an element, attribute or inside
+ jbxb:characters to specify that the element, attribute or
+ characters should be used as the key in map
+ entry.</xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ <xs:element name="mapEntryValue">
+ <xs:annotation>
+ <xs:documentation>This element is a marker element that has no
+ attributes. It is specified on an element, attribute or inside
+ jbxb:characters to specify that the element, attribute or
+ characters should be used as the value in map entry. Example:<![CDATA[
+ <xsd:element name="entry1">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <putMethod/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xsd:complexType>
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:mapEntry/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="key1" type="xsd:string">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:mapEntryKey/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="value1" type="xsd:string">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:mapEntryValue/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ </xsd:complexType>
+ </xsd:element>
+ ]]></xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ <xs:element name="skip">
+ <xs:annotation>
+ <xs:documentation>This element can be used on an element declaration
+ or a complex type definition. Unmarshaller will not try to
+ create new objects for elements (or elements of complex types)
+ that are annotated with jbxb:skip. Instead, the object that was
+ created for the parent of such elements will be propagated and
+ values of attributes, character contents and child elements of
+ such elements will be set on their parent's
+ object. Example:<![CDATA[
+ <xs:element name="authentication">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:skip/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:element ref="jaas:login-module"/>
+ </xs:sequence>
+ </xs:complexType>
+ </xs:element>
+ ]]>In the example above, login-modules will be added to the parent of authentication element.</xs:documentation>
+ </xs:annotation>
+ </xs:element>
+</xs:schema>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jndi-binding-service_1_0.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jndi-binding-service_1_0.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jndi-binding-service_1_0.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xs:schema version="1.0beta" attributeFormDefault="unqualified"
+ elementFormDefault="qualified"
+ targetNamespace="urn:jboss:jndi-binding-service:1.0"
+ xmlns:jndi="urn:jboss:jndi-binding-service:1.0"
+ xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ xmlns:jbxb="http://www.jboss.org/xml/ns/jbxb"
+ >
+ <xs:annotation>
+ <xs:documentation>This schema defines the content model for the
+ JNDIBindingService BindingsConfig attribute content.<![CDATA[
+ <jndi:bindings xmlns:jndi="urn:jboss:jndi-binding-service"
+ version="1.0">
+ ...
+ </jndi:bindings>
+ ]]></xs:documentation>
+ <xs:appinfo>
+ <jbxb:schemaBindings>
+ <jbxb:ignoreUnresolvedFieldOrClass>false</jbxb:ignoreUnresolvedFieldOrClass>
+ <jbxb:replacePropertyRefs>true</jbxb:replacePropertyRefs>
+ </jbxb:schemaBindings>
+ </xs:appinfo>
+ </xs:annotation>
+ <xs:element name="bindings">
+ <xs:annotation>
+ <xs:appinfo>
+ <jbxb:class impl="org.jboss.naming.JNDIBindings"/>
+ </xs:appinfo>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:element name="binding" minOccurs="1"
+ maxOccurs="unbounded">
+ <xs:annotation>
+ <xs:appinfo>
+ <jbxb:class impl="org.jboss.naming.JNDIBinding"/>
+ <jbxb:property name="Bindings" />
+ </xs:appinfo>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:choice minOccurs="1" maxOccurs="1">
+ <xs:element name="value">
+ <xs:annotation>
+ <xs:appinfo>
+ <jbxb:skip/>
+ </xs:appinfo>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:annotation>
+ <xs:appinfo>
+ <jbxb:characters>
+ <jbxb:property name="text"/>
+ </jbxb:characters>
+ </xs:appinfo>
+ </xs:annotation>
+ <xs:simpleContent>
+ <xs:extension base="xs:string">
+ <xs:attribute name="type" type="xs:string" use="optional">
+ </xs:attribute>
+ <xs:attribute name="editor" type="xs:string" use="optional">
+ </xs:attribute>
+ <xs:attribute name="trim" type="xs:boolean" default="true">
+ </xs:attribute>
+ </xs:extension>
+ </xs:simpleContent>
+ </xs:complexType>
+ </xs:element>
+ <xs:any namespace="##other">
+ <xs:annotation>
+ <xs:documentation>An extension point for arbitrary xml value fragments</xs:documentation>
+ <xs:appinfo>
+ <jbxb:property name="value"/>
+ </xs:appinfo>
+ </xs:annotation>
+ </xs:any>
+ </xs:choice>
+ <xs:attribute name="name" type="xs:string" use="required">
+ <xs:annotation>
+ <xs:documentation>The JNDI name of the binding</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:complexType>
+ </xs:element>
+ </xs:sequence>
+ </xs:complexType>
+ </xs:element>
+</xs:schema>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jsp_2_0.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jsp_2_0.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jsp_2_0.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,307 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="2.0">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)jsp_2_0.xsds 1.17 03/18/03
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
+ Road, Palo Alto, California 94303, U.S.A. All rights
+ reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This is the XML Schema for the JSP 2.0 deployment descriptor
+ types. The JSP 2.0 schema contains all the special
+ structures and datatypes that are necessary to use JSP files
+ from a web application.
+
+ The contents of this schema is used by the web-app_2_4.xsd
+ file to define JSP specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all J2EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
+
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="jsp-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jsp-configType is used to provide global configuration
+ information for the JSP files in a web application. It has
+ two subelements, taglib and jsp-property-group.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="taglib"
+ type="j2ee:taglibType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="jsp-property-group"
+ type="j2ee:jsp-property-groupType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="jsp-fileType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jsp-file element contains the full path to a JSP file
+ within the web application beginning with a `/'.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:pathType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="jsp-property-groupType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jsp-property-groupType is used to group a number of
+ files so they can be given global property information.
+ All files so described are deemed to be JSP files. The
+ following additional properties can be described:
+
+ - Control whether EL is ignored
+ - Control whether scripting elements are invalid
+ - Indicate pageEncoding information.
+ - Indicate that a resource is a JSP document (XML)
+ - Prelude and Coda automatic includes.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="url-pattern"
+ type="j2ee:url-patternType"
+ maxOccurs="unbounded"/>
+ <xsd:element name="el-ignored"
+ type="j2ee:true-falseType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Can be used to easily set the isELIgnored
+ property of a group of JSP pages. By default, the
+ EL evaluation is enabled for Web Applications using
+ a Servlet 2.4 or greater web.xml, and disabled
+ otherwise.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="page-encoding"
+ type="j2ee:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The valid values of page-encoding are those of the
+ pageEncoding page directive. It is a
+ translation-time error to name different encodings
+ in the pageEncoding attribute of the page directive
+ of a JSP page and in a JSP configuration element
+ matching the page. It is also a translation-time
+ error to name different encodings in the prolog
+ or text declaration of a document in XML syntax and
+ in a JSP configuration element matching the document.
+ It is legal to name the same encoding through
+ mulitple mechanisms.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="scripting-invalid"
+ type="j2ee:true-falseType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Can be used to easily disable scripting in a
+ group of JSP pages. By default, scripting is
+ enabled.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="is-xml"
+ type="j2ee:true-falseType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ If true, denotes that the group of resources
+ that match the URL pattern are JSP documents,
+ and thus must be interpreted as XML documents.
+ If false, the resources are assumed to not
+ be JSP documents, unless there is another
+ property group that indicates otherwise.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="include-prelude"
+ type="j2ee:pathType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The include-prelude element is a context-relative
+ path that must correspond to an element in the
+ Web Application. When the element is present,
+ the given path will be automatically included (as
+ in an include directive) at the beginning of each
+ JSP page in this jsp-property-group.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="include-coda"
+ type="j2ee:pathType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The include-coda element is a context-relative
+ path that must correspond to an element in the
+ Web Application. When the element is present,
+ the given path will be automatically included (as
+ in an include directive) at the end of each
+ JSP page in this jsp-property-group.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="taglibType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The taglibType defines the syntax for declaring in
+ the deployment descriptor that a tag library is
+ available to the application. This can be done
+ to override implicit map entries from TLD files and
+ from the container.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="taglib-uri"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ A taglib-uri element describes a URI identifying a
+ tag library used in the web application. The body
+ of the taglib-uri element may be either an
+ absolute URI specification, or a relative URI.
+ There should be no entries in web.xml with the
+ same taglib-uri value.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="taglib-location"
+ type="j2ee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ the taglib-location element contains the location
+ (as a resource relative to the root of the web
+ application) where to find the Tag Library
+ Description file for the tag library.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jsp_2_1.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jsp_2_1.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/jsp_2_1.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,342 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="2.1">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)jsp_2_1.xsds 1.5 08/11/05
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003-2006 Sun Microsystems, Inc.
+ 4150 Network Circle
+ Santa Clara, California 95054
+ U.S.A
+ All rights reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This is the XML Schema for the JSP 2.1 deployment descriptor
+ types. The JSP 2.1 schema contains all the special
+ structures and datatypes that are necessary to use JSP files
+ from a web application.
+
+ The contents of this schema is used by the web-app_2_5.xsd
+ file to define JSP specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all Java EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="javaee_5.xsd"/>
+
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="jsp-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jsp-configType is used to provide global configuration
+ information for the JSP files in a web application. It has
+ two subelements, taglib and jsp-property-group.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="taglib"
+ type="javaee:taglibType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="jsp-property-group"
+ type="javaee:jsp-property-groupType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="jsp-fileType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jsp-file element contains the full path to a JSP file
+ within the web application beginning with a `/'.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:pathType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="jsp-property-groupType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The jsp-property-groupType is used to group a number of
+ files so they can be given global property information.
+ All files so described are deemed to be JSP files. The
+ following additional properties can be described:
+
+ - Control whether EL is ignored.
+ - Control whether scripting elements are invalid.
+ - Indicate pageEncoding information.
+ - Indicate that a resource is a JSP document (XML).
+ - Prelude and Coda automatic includes.
+ - Control whether the character sequence #{ is allowed
+ when used as a String literal.
+ - Control whether template text containing only
+ whitespaces must be removed from the response output.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="url-pattern"
+ type="javaee:url-patternType"
+ maxOccurs="unbounded"/>
+ <xsd:element name="el-ignored"
+ type="javaee:true-falseType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Can be used to easily set the isELIgnored
+ property of a group of JSP pages. By default, the
+ EL evaluation is enabled for Web Applications using
+ a Servlet 2.4 or greater web.xml, and disabled
+ otherwise.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="page-encoding"
+ type="javaee:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The valid values of page-encoding are those of the
+ pageEncoding page directive. It is a
+ translation-time error to name different encodings
+ in the pageEncoding attribute of the page directive
+ of a JSP page and in a JSP configuration element
+ matching the page. It is also a translation-time
+ error to name different encodings in the prolog
+ or text declaration of a document in XML syntax and
+ in a JSP configuration element matching the document.
+ It is legal to name the same encoding through
+ mulitple mechanisms.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="scripting-invalid"
+ type="javaee:true-falseType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Can be used to easily disable scripting in a
+ group of JSP pages. By default, scripting is
+ enabled.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="is-xml"
+ type="javaee:true-falseType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ If true, denotes that the group of resources
+ that match the URL pattern are JSP documents,
+ and thus must be interpreted as XML documents.
+ If false, the resources are assumed to not
+ be JSP documents, unless there is another
+ property group that indicates otherwise.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="include-prelude"
+ type="javaee:pathType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The include-prelude element is a context-relative
+ path that must correspond to an element in the
+ Web Application. When the element is present,
+ the given path will be automatically included (as
+ in an include directive) at the beginning of each
+ JSP page in this jsp-property-group.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="include-coda"
+ type="javaee:pathType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The include-coda element is a context-relative
+ path that must correspond to an element in the
+ Web Application. When the element is present,
+ the given path will be automatically included (as
+ in an include directive) at the end of each
+ JSP page in this jsp-property-group.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="deferred-syntax-allowed-as-literal"
+ type="javaee:true-falseType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The character sequence #{ is reserved for EL expressions.
+ Consequently, a translation error occurs if the #{
+ character sequence is used as a String literal, unless
+ this element is enabled (true). Disabled (false) by
+ default.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="trim-directive-whitespaces"
+ type="javaee:true-falseType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Indicates that template text containing only whitespaces
+ must be removed from the response output. It has no
+ effect on JSP documents (XML syntax). Disabled (false)
+ by default.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="taglibType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The taglibType defines the syntax for declaring in
+ the deployment descriptor that a tag library is
+ available to the application. This can be done
+ to override implicit map entries from TLD files and
+ from the container.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="taglib-uri"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ A taglib-uri element describes a URI identifying a
+ tag library used in the web application. The body
+ of the taglib-uri element may be either an
+ absolute URI specification, or a relative URI.
+ There should be no entries in web.xml with the
+ same taglib-uri value.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="taglib-location"
+ type="javaee:pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ the taglib-location element contains the location
+ (as a resource relative to the root of the web
+ application) where to find the Tag Library
+ Description file for the tag library.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/orm_1_0.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/orm_1_0.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/orm_1_0.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1516 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- Java Persistence API object-relational mapping file schema -->
+<xsd:schema targetNamespace="http://java.sun.com/xml/ns/persistence/orm"
+ xmlns:orm="http://java.sun.com/xml/ns/persistence/orm"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.0">
+
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)orm_1_0.xsd 1.0 Feb 14 2006
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:annotation>
+ <xsd:documentation><![CDATA[
+
+ This is the XML Schema for the persistence object-relational
+ mapping file.
+ The file may be named "META-INF/orm.xml" in the persistence
+ archive or it may be named some other name which would be
+ used to locate the file as resource on the classpath.
+
+ ]]></xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:complexType name="emptyType"/>
+
+ <xsd:simpleType name="versionType">
+ <xsd:restriction base="xsd:token">
+ <xsd:pattern value="[0-9]+(\.[0-9]+)*"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="entity-mappings">
+ <xsd:complexType>
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The entity-mappings element is the root element of an mapping
+ file. It contains the following four types of elements:
+
+ 1. The persistence-unit-metadata element contains metadata
+ for the entire persistence unit. It is undefined if this element
+ occurs in multiple mapping files within the same persistence unit.
+
+ 2. The package, schema, catalog and access elements apply to all of
+ the entity, mapped-superclass and embeddable elements defined in
+ the same file in which they occur.
+
+ 3. The sequence-generator, table-generator, named-query,
+ named-native-query and sql-result-set-mapping elements are global
+ to the persistence unit. It is undefined to have more than one
+ sequence-generator or table-generator of the same name in the same
+ or different mapping files in a persistence unit. It is also
+ undefined to have more than one named-query or named-native-query
+ of the same name in the same or different mapping files in a
+ persistence unit.
+
+ 4. The entity, mapped-superclass and embeddable elements each define
+ the mapping information for a managed persistent class. The mapping
+ information contained in these elements may be complete or it may
+ be partial.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description" type="xsd:string"
+ minOccurs="0"/>
+ <xsd:element name="persistence-unit-metadata"
+ type="orm:persistence-unit-metadata"
+ minOccurs="0"/>
+ <xsd:element name="package" type="xsd:string"
+ minOccurs="0"/>
+ <xsd:element name="schema" type="xsd:string"
+ minOccurs="0"/>
+ <xsd:element name="catalog" type="xsd:string"
+ minOccurs="0"/>
+ <xsd:element name="access" type="orm:access-type"
+ minOccurs="0"/>
+ <xsd:element name="sequence-generator" type="orm:sequence-generator"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="table-generator" type="orm:table-generator"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="named-query" type="orm:named-query"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="named-native-query" type="orm:named-native-query"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="sql-result-set-mapping"
+ type="orm:sql-result-set-mapping"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="mapped-superclass" type="orm:mapped-superclass"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="entity" type="orm:entity"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="embeddable" type="orm:embeddable"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="version" type="orm:versionType"
+ fixed="1.0" use="required"/>
+ </xsd:complexType>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="persistence-unit-metadata">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Metadata that applies to the persistence unit and not just to
+ the mapping file in which it is contained.
+
+ If the xml-mapping-metadata-complete element is specified then
+ the complete set of mapping metadata for the persistence unit
+ is contained in the XML mapping files for the persistence unit.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="xml-mapping-metadata-complete" type="orm:emptyType"
+ minOccurs="0"/>
+ <xsd:element name="persistence-unit-defaults"
+ type="orm:persistence-unit-defaults"
+ minOccurs="0"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="persistence-unit-defaults">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ These defaults are applied to the persistence unit as a whole
+ unless they are overridden by local annotation or XML
+ element settings.
+
+ schema - Used as the schema for all tables or secondary tables
+ that apply to the persistence unit
+ catalog - Used as the catalog for all tables or secondary tables
+ that apply to the persistence unit
+ access - Used as the access type for all managed classes in
+ the persistence unit
+ cascade-persist - Adds cascade-persist to the set of cascade options
+ in entity relationships of the persistence unit
+ entity-listeners - List of default entity listeners to be invoked
+ on each entity in the persistence unit.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="schema" type="xsd:string"
+ minOccurs="0"/>
+ <xsd:element name="catalog" type="xsd:string"
+ minOccurs="0"/>
+ <xsd:element name="access" type="orm:access-type"
+ minOccurs="0"/>
+ <xsd:element name="cascade-persist" type="orm:emptyType"
+ minOccurs="0"/>
+ <xsd:element name="entity-listeners" type="orm:entity-listeners"
+ minOccurs="0"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="entity">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the settings and mappings for an entity. Is allowed to be
+ sparsely populated and used in conjunction with the annotations.
+ Alternatively, the metadata-complete attribute can be used to
+ indicate that no annotations on the entity class (and its fields
+ or properties) are to be processed. If this is the case then
+ the defaulting rules for the entity and its subelements will
+ be recursively applied.
+
+ @Target(TYPE) @Retention(RUNTIME)
+ public @interface Entity {
+ String name() default "";
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description" type="xsd:string" minOccurs="0"/>
+ <xsd:element name="table" type="orm:table"
+ minOccurs="0"/>
+ <xsd:element name="secondary-table" type="orm:secondary-table"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="primary-key-join-column"
+ type="orm:primary-key-join-column"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="id-class" type="orm:id-class" minOccurs="0"/>
+ <xsd:element name="inheritance" type="orm:inheritance" minOccurs="0"/>
+ <xsd:element name="discriminator-value" type="orm:discriminator-value"
+ minOccurs="0"/>
+ <xsd:element name="discriminator-column"
+ type="orm:discriminator-column"
+ minOccurs="0"/>
+ <xsd:element name="sequence-generator" type="orm:sequence-generator"
+ minOccurs="0"/>
+ <xsd:element name="table-generator" type="orm:table-generator"
+ minOccurs="0"/>
+ <xsd:element name="named-query" type="orm:named-query"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="named-native-query" type="orm:named-native-query"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="sql-result-set-mapping"
+ type="orm:sql-result-set-mapping"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="exclude-default-listeners" type="orm:emptyType"
+ minOccurs="0"/>
+ <xsd:element name="exclude-superclass-listeners" type="orm:emptyType"
+ minOccurs="0"/>
+ <xsd:element name="entity-listeners" type="orm:entity-listeners"
+ minOccurs="0"/>
+ <xsd:element name="pre-persist" type="orm:pre-persist" minOccurs="0"/>
+ <xsd:element name="post-persist" type="orm:post-persist"
+ minOccurs="0"/>
+ <xsd:element name="pre-remove" type="orm:pre-remove" minOccurs="0"/>
+ <xsd:element name="post-remove" type="orm:post-remove" minOccurs="0"/>
+ <xsd:element name="pre-update" type="orm:pre-update" minOccurs="0"/>
+ <xsd:element name="post-update" type="orm:post-update" minOccurs="0"/>
+ <xsd:element name="post-load" type="orm:post-load" minOccurs="0"/>
+ <xsd:element name="attribute-override" type="orm:attribute-override"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="association-override"
+ type="orm:association-override"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="attributes" type="orm:attributes" minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string"/>
+ <xsd:attribute name="class" type="xsd:string" use="required"/>
+ <xsd:attribute name="access" type="orm:access-type"/>
+ <xsd:attribute name="metadata-complete" type="xsd:boolean"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="attributes">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This element contains the entity field or property mappings.
+ It may be sparsely populated to include only a subset of the
+ fields or properties. If metadata-complete for the entity is true
+ then the remainder of the attributes will be defaulted according
+ to the default rules.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:choice>
+ <xsd:element name="id" type="orm:id"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="embedded-id" type="orm:embedded-id"
+ minOccurs="0"/>
+ </xsd:choice>
+ <xsd:element name="basic" type="orm:basic"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="version" type="orm:version"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="many-to-one" type="orm:many-to-one"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="one-to-many" type="orm:one-to-many"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="one-to-one" type="orm:one-to-one"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="many-to-many" type="orm:many-to-many"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="embedded" type="orm:embedded"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="transient" type="orm:transient"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="access-type">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This element determines how the persistence provider accesses the
+ state of an entity or embedded object.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:enumeration value="PROPERTY"/>
+ <xsd:enumeration value="FIELD"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="entity-listeners">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE}) @Retention(RUNTIME)
+ public @interface EntityListeners {
+ Class[] value();
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="entity-listener" type="orm:entity-listener"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="entity-listener">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines an entity listener to be invoked at lifecycle events
+ for the entities that list this listener.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="pre-persist" type="orm:pre-persist" minOccurs="0"/>
+ <xsd:element name="post-persist" type="orm:post-persist"
+ minOccurs="0"/>
+ <xsd:element name="pre-remove" type="orm:pre-remove" minOccurs="0"/>
+ <xsd:element name="post-remove" type="orm:post-remove" minOccurs="0"/>
+ <xsd:element name="pre-update" type="orm:pre-update" minOccurs="0"/>
+ <xsd:element name="post-update" type="orm:post-update" minOccurs="0"/>
+ <xsd:element name="post-load" type="orm:post-load" minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="class" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="pre-persist">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD}) @Retention(RUNTIME)
+ public @interface PrePersist {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="method-name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="post-persist">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD}) @Retention(RUNTIME)
+ public @interface PostPersist {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="method-name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="pre-remove">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD}) @Retention(RUNTIME)
+ public @interface PreRemove {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="method-name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="post-remove">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD}) @Retention(RUNTIME)
+ public @interface PostRemove {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="method-name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="pre-update">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD}) @Retention(RUNTIME)
+ public @interface PreUpdate {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="method-name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="post-update">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD}) @Retention(RUNTIME)
+ public @interface PostUpdate {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="method-name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="post-load">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD}) @Retention(RUNTIME)
+ public @interface PostLoad {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="method-name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="query-hint">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({}) @Retention(RUNTIME)
+ public @interface QueryHint {
+ String name();
+ String value();
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="value" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="named-query">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE}) @Retention(RUNTIME)
+ public @interface NamedQuery {
+ String name();
+ String query();
+ QueryHint[] hints() default {};
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="query" type="xsd:string"/>
+ <xsd:element name="hint" type="orm:query-hint"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="named-native-query">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE}) @Retention(RUNTIME)
+ public @interface NamedNativeQuery {
+ String name();
+ String query();
+ QueryHint[] hints() default {};
+ Class resultClass() default void.class;
+ String resultSetMapping() default ""; //named SqlResultSetMapping
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="query" type="xsd:string"/>
+ <xsd:element name="hint" type="orm:query-hint"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="result-class" type="xsd:string"/>
+ <xsd:attribute name="result-set-mapping" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="sql-result-set-mapping">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE}) @Retention(RUNTIME)
+ public @interface SqlResultSetMapping {
+ String name();
+ EntityResult[] entities() default {};
+ ColumnResult[] columns() default {};
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="entity-result" type="orm:entity-result"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="column-result" type="orm:column-result"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="entity-result">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({}) @Retention(RUNTIME)
+ public @interface EntityResult {
+ Class entityClass();
+ FieldResult[] fields() default {};
+ String discriminatorColumn() default "";
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="field-result" type="orm:field-result"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="entity-class" type="xsd:string" use="required"/>
+ <xsd:attribute name="discriminator-column" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="field-result">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({}) @Retention(RUNTIME)
+ public @interface FieldResult {
+ String name();
+ String column();
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="column" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="column-result">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({}) @Retention(RUNTIME)
+ public @interface ColumnResult {
+ String name();
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="table">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE}) @Retention(RUNTIME)
+ public @interface Table {
+ String name() default "";
+ String catalog() default "";
+ String schema() default "";
+ UniqueConstraint[] uniqueConstraints() default {};
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="unique-constraint" type="orm:unique-constraint"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string"/>
+ <xsd:attribute name="catalog" type="xsd:string"/>
+ <xsd:attribute name="schema" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="secondary-table">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE}) @Retention(RUNTIME)
+ public @interface SecondaryTable {
+ String name();
+ String catalog() default "";
+ String schema() default "";
+ PrimaryKeyJoinColumn[] pkJoinColumns() default {};
+ UniqueConstraint[] uniqueConstraints() default {};
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="primary-key-join-column"
+ type="orm:primary-key-join-column"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="unique-constraint" type="orm:unique-constraint"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="catalog" type="xsd:string"/>
+ <xsd:attribute name="schema" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="unique-constraint">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({}) @Retention(RUNTIME)
+ public @interface UniqueConstraint {
+ String[] columnNames();
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="column-name" type="xsd:string"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="column">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface Column {
+ String name() default "";
+ boolean unique() default false;
+ boolean nullable() default true;
+ boolean insertable() default true;
+ boolean updatable() default true;
+ String columnDefinition() default "";
+ String table() default "";
+ int length() default 255;
+ int precision() default 0; // decimal precision
+ int scale() default 0; // decimal scale
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="name" type="xsd:string"/>
+ <xsd:attribute name="unique" type="xsd:boolean"/>
+ <xsd:attribute name="nullable" type="xsd:boolean"/>
+ <xsd:attribute name="insertable" type="xsd:boolean"/>
+ <xsd:attribute name="updatable" type="xsd:boolean"/>
+ <xsd:attribute name="column-definition" type="xsd:string"/>
+ <xsd:attribute name="table" type="xsd:string"/>
+ <xsd:attribute name="length" type="xsd:int"/>
+ <xsd:attribute name="precision" type="xsd:int"/>
+ <xsd:attribute name="scale" type="xsd:int"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="join-column">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface JoinColumn {
+ String name() default "";
+ String referencedColumnName() default "";
+ boolean unique() default false;
+ boolean nullable() default true;
+ boolean insertable() default true;
+ boolean updatable() default true;
+ String columnDefinition() default "";
+ String table() default "";
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="name" type="xsd:string"/>
+ <xsd:attribute name="referenced-column-name" type="xsd:string"/>
+ <xsd:attribute name="unique" type="xsd:boolean"/>
+ <xsd:attribute name="nullable" type="xsd:boolean"/>
+ <xsd:attribute name="insertable" type="xsd:boolean"/>
+ <xsd:attribute name="updatable" type="xsd:boolean"/>
+ <xsd:attribute name="column-definition" type="xsd:string"/>
+ <xsd:attribute name="table" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="generation-type">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ public enum GenerationType { TABLE, SEQUENCE, IDENTITY, AUTO };
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:enumeration value="TABLE"/>
+ <xsd:enumeration value="SEQUENCE"/>
+ <xsd:enumeration value="IDENTITY"/>
+ <xsd:enumeration value="AUTO"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="attribute-override">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE, METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface AttributeOverride {
+ String name();
+ Column column();
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="column" type="orm:column"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="association-override">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE, METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface AssociationOverride {
+ String name();
+ JoinColumn[] joinColumns();
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="join-column" type="orm:join-column"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="id-class">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE}) @Retention(RUNTIME)
+ public @interface IdClass {
+ Class value();
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="class" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="id">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface Id {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="column" type="orm:column"
+ minOccurs="0"/>
+ <xsd:element name="generated-value" type="orm:generated-value"
+ minOccurs="0"/>
+ <xsd:element name="temporal" type="orm:temporal"
+ minOccurs="0"/>
+ <xsd:element name="table-generator" type="orm:table-generator"
+ minOccurs="0"/>
+ <xsd:element name="sequence-generator" type="orm:sequence-generator"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="embedded-id">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface EmbeddedId {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="attribute-override" type="orm:attribute-override"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="transient">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface Transient {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="version">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface Version {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="column" type="orm:column" minOccurs="0"/>
+ <xsd:element name="temporal" type="orm:temporal" minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="basic">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface Basic {
+ FetchType fetch() default EAGER;
+ boolean optional() default true;
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="column" type="orm:column" minOccurs="0"/>
+ <xsd:choice>
+ <xsd:element name="lob" type="orm:lob" minOccurs="0"/>
+ <xsd:element name="temporal" type="orm:temporal" minOccurs="0"/>
+ <xsd:element name="enumerated" type="orm:enumerated" minOccurs="0"/>
+ </xsd:choice>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="fetch" type="orm:fetch-type"/>
+ <xsd:attribute name="optional" type="xsd:boolean"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="fetch-type">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ public enum FetchType { LAZY, EAGER };
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:enumeration value="LAZY"/>
+ <xsd:enumeration value="EAGER"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="lob">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface Lob {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="temporal">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface Temporal {
+ TemporalType value();
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="orm:temporal-type"/>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="temporal-type">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ public enum TemporalType {
+ DATE, // java.sql.Date
+ TIME, // java.sql.Time
+ TIMESTAMP // java.sql.Timestamp
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:enumeration value="DATE"/>
+ <xsd:enumeration value="TIME"/>
+ <xsd:enumeration value="TIMESTAMP"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="enumerated">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface Enumerated {
+ EnumType value() default ORDINAL;
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="orm:enum-type"/>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="enum-type">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ public enum EnumType {
+ ORDINAL,
+ STRING
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:enumeration value="ORDINAL"/>
+ <xsd:enumeration value="STRING"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="many-to-one">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface ManyToOne {
+ Class targetEntity() default void.class;
+ CascadeType[] cascade() default {};
+ FetchType fetch() default EAGER;
+ boolean optional() default true;
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:choice>
+ <xsd:element name="join-column" type="orm:join-column"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="join-table" type="orm:join-table"
+ minOccurs="0"/>
+ </xsd:choice>
+ <xsd:element name="cascade" type="orm:cascade-type"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="target-entity" type="xsd:string"/>
+ <xsd:attribute name="fetch" type="orm:fetch-type"/>
+ <xsd:attribute name="optional" type="xsd:boolean"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="cascade-type">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ public enum CascadeType { ALL, PERSIST, MERGE, REMOVE, REFRESH};
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="cascade-all" type="orm:emptyType"
+ minOccurs="0"/>
+ <xsd:element name="cascade-persist" type="orm:emptyType"
+ minOccurs="0"/>
+ <xsd:element name="cascade-merge" type="orm:emptyType"
+ minOccurs="0"/>
+ <xsd:element name="cascade-remove" type="orm:emptyType"
+ minOccurs="0"/>
+ <xsd:element name="cascade-refresh" type="orm:emptyType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="one-to-one">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface OneToOne {
+ Class targetEntity() default void.class;
+ CascadeType[] cascade() default {};
+ FetchType fetch() default EAGER;
+ boolean optional() default true;
+ String mappedBy() default "";
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:choice>
+ <xsd:element name="primary-key-join-column"
+ type="orm:primary-key-join-column"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="join-column" type="orm:join-column"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="join-table" type="orm:join-table"
+ minOccurs="0"/>
+ </xsd:choice>
+ <xsd:element name="cascade" type="orm:cascade-type"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="target-entity" type="xsd:string"/>
+ <xsd:attribute name="fetch" type="orm:fetch-type"/>
+ <xsd:attribute name="optional" type="xsd:boolean"/>
+ <xsd:attribute name="mapped-by" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="one-to-many">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface OneToMany {
+ Class targetEntity() default void.class;
+ CascadeType[] cascade() default {};
+ FetchType fetch() default LAZY;
+ String mappedBy() default "";
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="order-by" type="orm:order-by"
+ minOccurs="0"/>
+ <xsd:element name="map-key" type="orm:map-key"
+ minOccurs="0"/>
+ <xsd:choice>
+ <xsd:element name="join-table" type="orm:join-table"
+ minOccurs="0"/>
+ <xsd:element name="join-column" type="orm:join-column"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:choice>
+ <xsd:element name="cascade" type="orm:cascade-type"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="target-entity" type="xsd:string"/>
+ <xsd:attribute name="fetch" type="orm:fetch-type"/>
+ <xsd:attribute name="mapped-by" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="join-table">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface JoinTable {
+ String name() default "";
+ String catalog() default "";
+ String schema() default "";
+ JoinColumn[] joinColumns() default {};
+ JoinColumn[] inverseJoinColumns() default {};
+ UniqueConstraint[] uniqueConstraints() default {};
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="join-column" type="orm:join-column"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="inverse-join-column" type="orm:join-column"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="unique-constraint" type="orm:unique-constraint"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string"/>
+ <xsd:attribute name="catalog" type="xsd:string"/>
+ <xsd:attribute name="schema" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="many-to-many">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface ManyToMany {
+ Class targetEntity() default void.class;
+ CascadeType[] cascade() default {};
+ FetchType fetch() default LAZY;
+ String mappedBy() default "";
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="order-by" type="orm:order-by"
+ minOccurs="0"/>
+ <xsd:element name="map-key" type="orm:map-key"
+ minOccurs="0"/>
+ <xsd:element name="join-table" type="orm:join-table"
+ minOccurs="0"/>
+ <xsd:element name="cascade" type="orm:cascade-type"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="target-entity" type="xsd:string"/>
+ <xsd:attribute name="fetch" type="orm:fetch-type"/>
+ <xsd:attribute name="mapped-by" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="generated-value">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface GeneratedValue {
+ GenerationType strategy() default AUTO;
+ String generator() default "";
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="strategy" type="orm:generation-type"/>
+ <xsd:attribute name="generator" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="map-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface MapKey {
+ String name() default "";
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="name" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="order-by">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface OrderBy {
+ String value() default "";
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:string"/>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="inheritance">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE}) @Retention(RUNTIME)
+ public @interface Inheritance {
+ InheritanceType strategy() default SINGLE_TABLE;
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="strategy" type="orm:inheritance-type"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="inheritance-type">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ public enum InheritanceType
+ { SINGLE_TABLE, JOINED, TABLE_PER_CLASS};
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:enumeration value="SINGLE_TABLE"/>
+ <xsd:enumeration value="JOINED"/>
+ <xsd:enumeration value="TABLE_PER_CLASS"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="discriminator-value">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE}) @Retention(RUNTIME)
+ public @interface DiscriminatorValue {
+ String value();
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:string"/>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="discriminator-type">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ public enum DiscriminatorType { STRING, CHAR, INTEGER };
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:enumeration value="STRING"/>
+ <xsd:enumeration value="CHAR"/>
+ <xsd:enumeration value="INTEGER"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="primary-key-join-column">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE, METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface PrimaryKeyJoinColumn {
+ String name() default "";
+ String referencedColumnName() default "";
+ String columnDefinition() default "";
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="name" type="xsd:string"/>
+ <xsd:attribute name="referenced-column-name" type="xsd:string"/>
+ <xsd:attribute name="column-definition" type="xsd:string"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="discriminator-column">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE}) @Retention(RUNTIME)
+ public @interface DiscriminatorColumn {
+ String name() default "DTYPE";
+ DiscriminatorType discriminatorType() default STRING;
+ String columnDefinition() default "";
+ int length() default 31;
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="name" type="xsd:string"/>
+ <xsd:attribute name="discriminator-type" type="orm:discriminator-type"/>
+ <xsd:attribute name="column-definition" type="xsd:string"/>
+ <xsd:attribute name="length" type="xsd:int"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="embeddable">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the settings and mappings for embeddable objects. Is
+ allowed to be sparsely populated and used in conjunction with
+ the annotations. Alternatively, the metadata-complete attribute
+ can be used to indicate that no annotations are to be processed
+ in the class. If this is the case then the defaulting rules will
+ be recursively applied.
+
+ @Target({TYPE}) @Retention(RUNTIME)
+ public @interface Embeddable {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description" type="xsd:string" minOccurs="0"/>
+ <xsd:element name="attributes" type="orm:embeddable-attributes"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="class" type="xsd:string" use="required"/>
+ <xsd:attribute name="access" type="orm:access-type"/>
+ <xsd:attribute name="metadata-complete" type="xsd:boolean"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="embeddable-attributes">
+ <xsd:sequence>
+ <xsd:element name="basic" type="orm:basic"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="transient" type="orm:transient"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="embedded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface Embedded {}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="attribute-override" type="orm:attribute-override"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="mapped-superclass">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the settings and mappings for a mapped superclass. Is
+ allowed to be sparsely populated and used in conjunction with
+ the annotations. Alternatively, the metadata-complete attribute
+ can be used to indicate that no annotations are to be processed
+ If this is the case then the defaulting rules will be recursively
+ applied.
+
+ @Target(TYPE) @Retention(RUNTIME)
+ public @interface MappedSuperclass{}
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description" type="xsd:string" minOccurs="0"/>
+ <xsd:element name="id-class" type="orm:id-class" minOccurs="0"/>
+ <xsd:element name="exclude-default-listeners" type="orm:emptyType"
+ minOccurs="0"/>
+ <xsd:element name="exclude-superclass-listeners" type="orm:emptyType"
+ minOccurs="0"/>
+ <xsd:element name="entity-listeners" type="orm:entity-listeners"
+ minOccurs="0"/>
+ <xsd:element name="pre-persist" type="orm:pre-persist" minOccurs="0"/>
+ <xsd:element name="post-persist" type="orm:post-persist"
+ minOccurs="0"/>
+ <xsd:element name="pre-remove" type="orm:pre-remove" minOccurs="0"/>
+ <xsd:element name="post-remove" type="orm:post-remove" minOccurs="0"/>
+ <xsd:element name="pre-update" type="orm:pre-update" minOccurs="0"/>
+ <xsd:element name="post-update" type="orm:post-update" minOccurs="0"/>
+ <xsd:element name="post-load" type="orm:post-load" minOccurs="0"/>
+ <xsd:element name="attributes" type="orm:attributes" minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="class" type="xsd:string" use="required"/>
+ <xsd:attribute name="access" type="orm:access-type"/>
+ <xsd:attribute name="metadata-complete" type="xsd:boolean"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="sequence-generator">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE, METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface SequenceGenerator {
+ String name();
+ String sequenceName() default "";
+ int initialValue() default 1;
+ int allocationSize() default 50;
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="sequence-name" type="xsd:string"/>
+ <xsd:attribute name="initial-value" type="xsd:int"/>
+ <xsd:attribute name="allocation-size" type="xsd:int"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="table-generator">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ @Target({TYPE, METHOD, FIELD}) @Retention(RUNTIME)
+ public @interface TableGenerator {
+ String name();
+ String table() default "";
+ String catalog() default "";
+ String schema() default "";
+ String pkColumnName() default "";
+ String valueColumnName() default "";
+ String pkColumnValue() default "";
+ int initialValue() default 0;
+ int allocationSize() default 50;
+ UniqueConstraint[] uniqueConstraints() default {};
+ }
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="unique-constraint" type="orm:unique-constraint"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ <xsd:attribute name="table" type="xsd:string"/>
+ <xsd:attribute name="catalog" type="xsd:string"/>
+ <xsd:attribute name="schema" type="xsd:string"/>
+ <xsd:attribute name="pk-column-name" type="xsd:string"/>
+ <xsd:attribute name="value-column-name" type="xsd:string"/>
+ <xsd:attribute name="pk-column-value" type="xsd:string"/>
+ <xsd:attribute name="initial-value" type="xsd:int"/>
+ <xsd:attribute name="allocation-size" type="xsd:int"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/persistence_1_0.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/persistence_1_0.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/persistence_1_0.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,260 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- persistence.xml schema -->
+<xsd:schema targetNamespace="http://java.sun.com/xml/ns/persistence"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ xmlns:persistence="http://java.sun.com/xml/ns/persistence"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.0">
+
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)persistence_1_0.xsd 1.0 Feb 9 2006
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:annotation>
+ <xsd:documentation><![CDATA[
+
+ This is the XML Schema for the persistence configuration file.
+ The file must be named "META-INF/persistence.xml" in the
+ persistence archive.
+ Persistence configuration files must indicate
+ the persistence schema by using the persistence namespace:
+
+ http://java.sun.com/xml/ns/persistence
+
+ and indicate the version of the schema by
+ using the version element as shown below:
+
+ <persistence xmlns="http://java.sun.com/xml/ns/persistence"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
+ http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
+ version="1.0">
+ ...
+ </persistence>
+
+ ]]></xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleType name="versionType">
+ <xsd:restriction base="xsd:token">
+ <xsd:pattern value="[0-9]+(\.[0-9]+)*"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="persistence">
+ <xsd:complexType>
+ <xsd:sequence>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="persistence-unit"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:complexType>
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Configuration of a persistence unit.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="description" type="xsd:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Textual description of this persistence unit.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="provider" type="xsd:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Provider class that supplies EntityManagers for this
+ persistence unit.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="jta-data-source" type="xsd:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The container-specific name of the JTA datasource to use.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="non-jta-data-source" type="xsd:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The container-specific name of a non-JTA datasource to use.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="mapping-file" type="xsd:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ File containing mapping information. Loaded as a resource
+ by the persistence provider.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="jar-file" type="xsd:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Jar file that should be scanned for entities.
+ Not applicable to Java SE persistence units.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="class" type="xsd:string"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Class to scan for annotations. It should be annotated
+ with either @Entity, @Embeddable or @MappedSuperclass.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="exclude-unlisted-classes" type="xsd:boolean"
+ default="false" minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ When set to true then only listed classes and jars will
+ be scanned for persistent classes, otherwise the enclosing
+ jar or directory will also be scanned. Not applicable to
+ Java SE persistence units.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name="properties" minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ A list of vendor-specific properties.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexType>
+ <xsd:sequence>
+ <xsd:element name="property"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+ A name-value pair.
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:complexType>
+ <xsd:attribute name="name" type="xsd:string"
+ use="required"/>
+ <xsd:attribute name="value" type="xsd:string"
+ use="required"/>
+ </xsd:complexType>
+ </xsd:element>
+ </xsd:sequence>
+ </xsd:complexType>
+ </xsd:element>
+
+ </xsd:sequence>
+
+ <!-- **************************************************** -->
+
+ <xsd:attribute name="name" type="xsd:string" use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Name used in code to reference this persistence unit.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+
+ <!-- **************************************************** -->
+
+ <xsd:attribute name="transaction-type"
+ type="persistence:persistence-unit-transaction-type">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Type of transactions used by EntityManagers from this
+ persistence unit.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+
+ </xsd:complexType>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="version" type="persistence:versionType"
+ fixed="1.0" use="required"/>
+ </xsd:complexType>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="persistence-unit-transaction-type">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ public enum TransactionType { JTA, RESOURCE_LOCAL };
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:enumeration value="JTA"/>
+ <xsd:enumeration value="RESOURCE_LOCAL"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/security-config_4_0.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/security-config_4_0.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/security-config_4_0.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,160 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
+ xmlns="http://www.jboss.org/j2ee/schema/jaas"
+ targetNamespace="http://www.jboss.org/j2ee/schema/jaas"
+ elementFormDefault="unqualified" attributeFormDefault="unqualified" version="4.0">
+ <xs:annotation>
+ <xs:documentation><![CDATA[
+ $Id: security-config_4_0.xsd 26732 2004-12-19 14:34:44Z $
+ This is the XML Schema for the jboss 4.0 security configuration descriptor.
+ The default version of the descriptor is found in conf/login-config.xml
+ and this version of the schema is indicated using:
+
+ <policy xmlns="http://www.jboss.org/j2ee/schema/jaas"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://www.jboss.org/j2ee/schema/security-config_4_0.xsd"
+ version="4.0">
+ ...
+ </policy>
+
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute:
+ http://www.jboss.org/j2ee/schema/security-config_4_0.xsd
+
+ The outline of a policy/application-policy is:
+ <policy>
+ <application-policy name="security-domain-name">
+ <authentication>
+ <login-module code="login.module1.class.name" flag="control_flag">
+ <module-option name = "option1-name">option1-value</module-option>
+ <module-option name = "option2-name">option2-value</module-option>
+ ...
+ </login-module>
+
+ <login-module code="login.module2.class.name" flag="control_flag">
+ ...
+ </login-module>
+ ...
+ </authentication>
+ </application-policy>
+ </policy>
+ ]]></xs:documentation>
+ </xs:annotation>
+ <xs:element name="policy">
+ <xs:annotation>
+ <xs:documentation>The policy element is the root of the security
+ configuration descriptor.</xs:documentation>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:element maxOccurs="unbounded" ref="application-policy"/>
+ </xs:sequence>
+ </xs:complexType>
+ </xs:element>
+ <xs:element name="application-policy">
+ <xs:annotation>
+ <xs:documentation>The application-policy lists configuration for a
+ named policy. This currently only consists of the authentication
+ configuration. </xs:documentation>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:element ref="authentication"/>
+ </xs:sequence>
+ <xs:attribute name="name" use="required" type="xs:NCName">
+ <xs:annotation>
+ <xs:documentation>The name attribute defines the authentication
+ configuration name. This is the name that would be passed to
+ the JAAS LoginContext ctor to use the associated login module stack.</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:complexType>
+ </xs:element>
+ <xs:element name="authentication">
+ <xs:annotation>
+ <xs:documentation>The authentication element contains the login module
+ stack configuration. Each login module configuration is specified
+ using a login-module element.</xs:documentation>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:element maxOccurs="unbounded" ref="login-module"/>
+ </xs:sequence>
+ </xs:complexType>
+ </xs:element>
+ <xs:element name="login-module">
+ <xs:annotation>
+ <xs:documentation>The login-module element defines a JAAS login module
+ configuration entry. Each entry must have a code and flag attribute
+ along with zero or more login module options specified via the
+ module-option element. </xs:documentation>
+ </xs:annotation>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:element minOccurs="0" maxOccurs="unbounded" ref="module-option"/>
+ </xs:sequence>
+ <xs:attribute name="code" use="required">
+ <xs:annotation>
+ <xs:documentation>The code attribute gives the fully qualifed class
+ name of the javax.security.auth.spi.LoginModule interface implementation
+ for the login module.
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="flag" use="required">
+ <xs:annotation>
+ <xs:documentation>The flag attribute controls how a login module
+ participates in the overall authentication proceedure.
+ Required - The LoginModule is required to succeed. If it
+ succeeds or fails, authentication still continues to proceed
+ down the LoginModule list.
+
+ Requisite - The LoginModule is required to succeed. If it succeeds,
+ authentication continues down the LoginModule list. If it fails,
+ control immediately returns to the application (authentication does not proceed
+ down the LoginModule list).
+
+ Sufficient - The LoginModule is not required to succeed. If it does
+ succeed, control immediately returns to the application (authentication
+ does not proceed down the LoginModule list). If it fails,
+ authentication continues down the LoginModule list.
+
+ Optional - The LoginModule is not required to succeed. If it succeeds or
+ fails, authentication still continues to proceed down the
+ LoginModule list.
+
+ The overall authentication succeeds only if
+ all required and requisite LoginModules succeed. If a
+ sufficient LoginModule is configured and succeeds, then only
+ the required and requisite LoginModules prior to that
+ sufficient LoginModule need to have succeeded for the overall
+ authentication to succeed. If no required or requisite
+ LoginModules are configured for an application, then at least
+ one sufficient or optional LoginModule must succeed. </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:complexType>
+ </xs:element>
+ <xs:element name="module-option">
+ <xs:annotation>
+ <xs:documentation>A module option defines a name, value pair that are
+ passed to a LoginModule when it is initialized during the login proceedure.
+ The name attribute defines the option name while the element value is the
+ option value. The type of the value can be anything from a string obtained
+ from the module-option body, to arbitary objects unmarshalled based on
+ the namespace associated with the module-option child element.</xs:documentation>
+ </xs:annotation>
+ <xs:complexType mixed="true">
+ <xs:sequence>
+ <xs:any namespace="##any"/>
+ </xs:sequence>
+ <xs:attribute name="name" use="required" type="xs:NCName">
+ <xs:annotation>
+ <xs:documentation>The module option name. This is the key used to store
+ the module value in the LoginModule initalize options Map.</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:complexType>
+ </xs:element>
+</xs:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/security-config_4_1.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/security-config_4_1.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/security-config_4_1.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,182 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: security-config_4_1.xsd 44282 2006-04-27 00:11:58Z asaldhana $ -->
+
+<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ xmlns:jaas="urn:jboss:security-config:4.1"
+ xmlns:jbxb="http://www.jboss.org/xml/ns/jbxb"
+ targetNamespace="urn:jboss:security-config:4.1">
+
+ <xsd:annotation>
+ <xsd:documentation><![CDATA[
+ The login-config.xml schema with jbossxb annotations that map conforming
+ documents to the org.jboss.security.auth.login.PolicyConfig.
+ $Id: security-config_4_1.xsd 44282 2006-04-27 00:11:58Z asaldhana $
+ This is the XML Schema for the jboss 4.1 security configuration descriptor.
+ The default version of the descriptor is found in conf/login-config.xml
+ and this version of the schema is indicated using:
+
+ <policy xmlns="urn:jboss:security-config:4.1"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ version="4.1">
+ ...
+ </policy>
+
+ The outline of a policy/application-policy is:
+ <policy>
+ <application-policy name="security-domain-name">
+ <authentication>
+ <login-module code="login.module1.class.name" flag="control_flag">
+ <module-option name = "option1-name">option1-value</module-option>
+ <module-option name = "option2-name">option2-value</module-option>
+ ...
+ </login-module>
+
+ <login-module code="login.module2.class.name" flag="control_flag">
+ ...
+ </login-module>
+ ...
+ </authentication>
+ </application-policy>
+ </policy>
+ ]]></xsd:documentation>
+ <xsd:appinfo>
+ <jbxb:schemaBindings>
+ <jbxb:package name="org.jboss.security.auth.login"/>
+ <jbxb:ignoreUnresolvedFieldOrClass>false</jbxb:ignoreUnresolvedFieldOrClass>
+ </jbxb:schemaBindings>
+ </xsd:appinfo>
+ </xsd:annotation>
+
+ <xsd:element name="policy">
+ <xsd:complexType>
+ <xsd:annotation>
+ <xsd:documentation>The policy element is the root of the security
+ configuration descriptor.</xsd:documentation>
+ <xsd:appinfo>
+ <jbxb:class impl="org.jboss.security.auth.login.PolicyConfig"/>
+ </xsd:appinfo>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element maxOccurs="unbounded" ref="jaas:application-policy"/>
+ </xsd:sequence>
+ </xsd:complexType>
+ </xsd:element>
+
+ <xsd:element name="application-policy">
+ <xsd:complexType>
+ <xsd:annotation>
+ <xsd:documentation>The application-policy lists configuration for a
+ named policy. This currently only consists of the authentication
+ configuration. </xsd:documentation>
+ <xsd:appinfo>
+ <jbxb:class impl="org.jboss.security.auth.login.AuthenticationInfoContainer"/>
+ <jbxb:addMethod name="add" valueType="child"/>
+ </xsd:appinfo>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element ref="jaas:authentication"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" use="required" type="xsd:string"/>
+ </xsd:complexType>
+ </xsd:element>
+
+ <xsd:element name="authentication">
+ <xsd:annotation>
+ <xsd:documentation>The authentication element contains the login module
+ stack configuration. Each login module configuration is specified
+ using a login-module element.</xsd:documentation>
+ <xsd:appinfo>
+ <jbxb:skip/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xsd:complexType>
+ <xsd:sequence>
+ <xsd:element maxOccurs="unbounded" ref="jaas:login-module"/>
+ </xsd:sequence>
+ </xsd:complexType>
+ </xsd:element>
+ <xsd:element name="login-module">
+ <xsd:complexType>
+ <xsd:annotation>
+ <xsd:documentation>The login-module element defines a JAAS login module
+ configuration entry. Each entry must have a code and flag attribute
+ along with zero or more login module options specified via the
+ module-option element. </xsd:documentation>
+ <xsd:appinfo>
+ <jbxb:class impl="org.jboss.security.auth.login.AppConfigurationEntryHolder"/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element minOccurs="0" maxOccurs="unbounded" ref="jaas:module-option"/>
+ </xsd:sequence>
+ <xsd:attribute name="code" use="required" type="xsd:string"/>
+ <xsd:attribute name="flag" use="required">
+ <xsd:annotation>
+ <xsd:documentation>The flag attribute controls how a login module
+ participates in the overall authentication proceedure.
+ Required - The LoginModule is required to succeed. If it
+ succeeds or fails, authentication still continues to proceed
+ down the LoginModule list.
+
+ Requisite - The LoginModule is required to succeed. If it succeeds,
+ authentication continues down the LoginModule list. If it fails,
+ control immediately returns to the application (authentication does not proceed
+ down the LoginModule list).
+
+ Sufficient - The LoginModule is not required to succeed. If it does
+ succeed, control immediately returns to the application (authentication
+ does not proceed down the LoginModule list). If it fails,
+ authentication continues down the LoginModule list.
+
+ Optional - The LoginModule is not required to succeed. If it succeeds or
+ fails, authentication still continues to proceed down the
+ LoginModule list.
+
+ The overall authentication succeeds only if
+ all required and requisite LoginModules succeed. If a
+ sufficient LoginModule is configured and succeeds, then only
+ the required and requisite LoginModules prior to that
+ sufficient LoginModule need to have succeeded for the overall
+ authentication to succeed. If no required or requisite
+ LoginModules are configured for an application, then at least
+ one sufficient or optional LoginModule must succeed.
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleType>
+ <xsd:restriction base="xsd:string">
+ <xsd:enumeration value="required" />
+ <xsd:enumeration value="requisite" />
+ <xsd:enumeration value="sufficient" />
+ <xsd:enumeration value="optional" />
+ </xsd:restriction>
+ </xsd:simpleType>
+ </xsd:attribute>
+ </xsd:complexType>
+ </xsd:element>
+ <xsd:element name="module-option">
+ <xsd:complexType mixed="true">
+ <xsd:annotation>
+ <xsd:documentation>A module option defines a name, value pair that are
+ passed to a LoginModule when it is initialized during the login proceedure.
+ The name attribute defines the option name while the element value is the
+ option value. The type of the value can be anything from a string obtained
+ from the module-option body, to arbitary objects unmarshalled based on
+ the namespace associated with the module-option child element
+ </xsd:documentation>
+ <xsd:appinfo>
+ <!-- ModuleOption declares a constructor that takes name as a parameter
+ while the value should be set with the setter.
+ This use-case is not supported out-of-the-box. So, we use this container. -->
+ <jbxb:class impl="org.jboss.security.auth.login.ModuleOptionContainer"/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:any minOccurs="0" maxOccurs="1" namespace="##other" />
+ </xsd:sequence>
+ <xsd:attribute name="name" use="required" type="xsd:string"/>
+ </xsd:complexType>
+ </xsd:element>
+</xsd:schema>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/user-roles_1_0.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/user-roles_1_0.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/user-roles_1_0.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: user-roles_1_0.xsd 36253 2005-09-22 23:25:51Z starksm $ -->
+
+<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ targetNamespace="urn:jboss:user-roles:1.0"
+ xmlns:jbxb="http://www.jboss.org/xml/ns/jbxb"
+ xmlns:ur="urn:jboss:user-roles:1.0">
+
+ <xsd:element name="users">
+ <xsd:annotation>
+ <xsd:documentation>
+ This is the jbossxb annotated schema for the embedded users content
+ for the org.jboss.security.auth.spi.XMLLoginModule
+ </xsd:documentation>
+ <xsd:appinfo>
+ <jbxb:class impl="org.jboss.security.auth.spi.Users"/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xsd:complexType>
+ <xsd:sequence>
+ <xsd:element minOccurs="1" maxOccurs="unbounded" ref="ur:user"/>
+ </xsd:sequence>
+ </xsd:complexType>
+ </xsd:element>
+ <xsd:element name="user">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:class impl="org.jboss.security.auth.spi.Users$User"/>
+ <jbxb:addMethod name="addUser" valueType="child"/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ <xsd:complexType>
+ <xsd:sequence>
+ <xsd:element minOccurs="0" maxOccurs="unbounded" ref="ur:role"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" use="required" type="xsd:NCName"/>
+ <xsd:attribute name="password" use="required" type="xsd:NCName"/>
+ </xsd:complexType>
+ </xsd:element>
+ <xsd:element name="role">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:mapEntry/>
+ <jbxb:putMethod name="addRole"
+ keyType="java.lang.String" valueType="java.lang.String" />
+ </xsd:appinfo>
+ </xsd:annotation>
+
+ <xsd:complexType>
+ <xsd:attribute name="group" use="optional" type="xsd:NCName" default="Roles">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:mapEntryValue/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ </xsd:attribute>
+ <xsd:attribute name="name" use="required" type="xsd:NCName">
+ <xsd:annotation>
+ <xsd:appinfo>
+ <jbxb:mapEntryKey/>
+ </xsd:appinfo>
+ </xsd:annotation>
+ </xsd:attribute>
+ </xsd:complexType>
+ </xsd:element>
+</xsd:schema>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-app_2_4.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-app_2_4.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-app_2_4.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1266 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="2.4">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)web-app_2_4.xsds 1.57 03/04/07
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
+ Road, Palo Alto, California 94303, U.S.A. All rights
+ reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This is the XML Schema for the Servlet 2.4 deployment descriptor.
+ The deployment descriptor must be named "WEB-INF/web.xml" in the
+ web application's war file. All Servlet deployment descriptors
+ must indicate the web application schema by using the J2EE
+ namespace:
+
+ http://java.sun.com/xml/ns/j2ee
+
+ and by indicating the version of the schema by
+ using the version element as shown below:
+
+ <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="..."
+ version="2.4">
+ ...
+ </web-app>
+
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute for J2EE
+ namespace with the following location:
+
+ http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all J2EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
+ <xsd:include schemaLocation="jsp_2_0.xsd"/>
+
+
+<!-- **************************************************** -->
+
+
+ <xsd:element name="web-app" type="j2ee:web-appType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The web-app element is the root of the deployment
+ descriptor for a web application. Note that the sub-elements
+ of this element can be in the arbitrary order. Because of
+ that, the multiplicity of the elements of distributable,
+ session-config, welcome-file-list, jsp-config, login-config,
+ and locale-encoding-mapping-list was changed from "?" to "*"
+ in this schema. However, the deployment descriptor instance
+ file must not contain multiple elements of session-config,
+ jsp-config, and login-config. When there are multiple elements of
+ welcome-file-list or locale-encoding-mapping-list, the container
+ must concatinate the element contents. The multiple occurance
+ of the element distributable is redundant and the container
+ treats that case exactly in the same way when there is only
+ one distributable.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:unique name="servlet-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The servlet element contains the name of a servlet.
+ The name must be unique within the web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:servlet"/>
+ <xsd:field xpath="j2ee:servlet-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="filter-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The filter element contains the name of a filter.
+ The name must be unique within the web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:filter"/>
+ <xsd:field xpath="j2ee:filter-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="ejb-local-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-local-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the web
+ application's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the web application.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:ejb-local-ref"/>
+ <xsd:field xpath="j2ee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="ejb-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the web
+ application's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the web application.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:ejb-ref"/>
+ <xsd:field xpath="j2ee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="resource-env-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name of
+ a resource environment reference; its value is the
+ environment entry name used in the web application code.
+ The name is a JNDI name relative to the java:comp/env
+ context and must be unique within a web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:resource-env-ref"/>
+ <xsd:field xpath="j2ee:resource-env-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="message-destination-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies the name of
+ a message destination reference; its value is the
+ environment entry name used in the web application code.
+ The name is a JNDI name relative to the java:comp/env
+ context and must be unique within a web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:message-destination-ref"/>
+ <xsd:field xpath="j2ee:message-destination-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="res-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference. The name
+ is a JNDI name relative to the java:comp/env context.
+ The name must be unique within a web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:resource-ref"/>
+ <xsd:field xpath="j2ee:res-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="env-entry-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entry-name element contains the name of a web
+ application's environment entry. The name is a JNDI
+ name relative to the java:comp/env context. The name
+ must be unique within a web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:selector xpath="j2ee:env-entry"/>
+ <xsd:field xpath="j2ee:env-entry-name"/>
+ </xsd:unique>
+
+ <xsd:key name="role-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ A role-name-key is specified to allow the references
+ from the security-role-refs.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:security-role"/>
+ <xsd:field xpath="j2ee:role-name"/>
+ </xsd:key>
+
+ <xsd:keyref name="role-name-references"
+ refer="j2ee:role-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The keyref indicates the references from
+ security-role-ref to a specified role-name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:servlet/j2ee:security-role-ref"/>
+ <xsd:field xpath="j2ee:role-link"/>
+ </xsd:keyref>
+ </xsd:element>
+
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="auth-constraintType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The auth-constraintType indicates the user roles that
+ should be permitted access to this resource
+ collection. The role-name used here must either correspond
+ to the role-name of one of the security-role elements
+ defined for this web application, or be the specially
+ reserved role-name "*" that is a compact syntax for
+ indicating all roles in the web application. If both "*"
+ and rolenames appear, the container interprets this as all
+ roles. If no roles are defined, no user is allowed access
+ to the portion of the web application described by the
+ containing security-constraint. The container matches
+ role names case sensitively when determining access.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="role-name"
+ type="j2ee:role-nameType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="auth-methodType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The auth-methodType is used to configure the authentication
+ mechanism for the web application. As a prerequisite to
+ gaining access to any web resources which are protected by
+ an authorization constraint, a user must have authenticated
+ using the configured mechanism. Legal values are "BASIC",
+ "DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific
+ authentication scheme.
+
+ Used in: login-config
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="dispatcherType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
+ and ERROR. A value of FORWARD means the Filter will be applied
+ under RequestDispatcher.forward() calls. A value of REQUEST
+ means the Filter will be applied under ordinary client calls to
+ the path or servlet. A value of INCLUDE means the Filter will be
+ applied under RequestDispatcher.include() calls. A value of
+ ERROR means the Filter will be applied under the error page
+ mechanism. The absence of any dispatcher elements in a
+ filter-mapping indicates a default of applying filters only under
+ ordinary client calls to the path or servlet.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="FORWARD"/>
+ <xsd:enumeration value="INCLUDE"/>
+ <xsd:enumeration value="REQUEST"/>
+ <xsd:enumeration value="ERROR"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="encodingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The encodingType defines IANA character sets.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:restriction base="xsd:string">
+ <xsd:pattern value="[^\s]+"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="error-codeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The error-code contains an HTTP error code, ex: 404
+
+ Used in: error-page
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:xsdPositiveIntegerType">
+ <xsd:pattern value="\d{3}"/>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="error-pageType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The error-pageType contains a mapping between an error code
+ or exception type to the path of a resource in the web
+ application.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:choice>
+ <xsd:element name="error-code"
+ type="j2ee:error-codeType"/>
+
+ <xsd:element name="exception-type"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The exception-type contains a fully qualified class
+ name of a Java exception type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:choice>
+
+ <xsd:element name="location"
+ type="j2ee:war-pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The location element contains the location of the
+ resource in the web application relative to the root of
+ the web application. The value of the location must have
+ a leading `/'.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="filter-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Declaration of the filter mappings in this web
+ application is done by using filter-mappingType.
+ The container uses the filter-mapping
+ declarations to decide which filters to apply to a request,
+ and in what order. The container matches the request URI to
+ a Servlet in the normal way. To determine which filters to
+ apply it matches filter-mapping declarations either on
+ servlet-name, or on url-pattern for each filter-mapping
+ element, depending on which style is used. The order in
+ which filters are invoked is the order in which
+ filter-mapping declarations that match a request URI for a
+ servlet appear in the list of filter-mapping elements.The
+ filter-name value must be the value of the filter-name
+ sub-elements of one of the filter declarations in the
+ deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="filter-name"
+ type="j2ee:filter-nameType"/>
+ <xsd:choice>
+ <xsd:element name="url-pattern"
+ type="j2ee:url-patternType"/>
+ <xsd:element name="servlet-name"
+ type="j2ee:servlet-nameType"/>
+ </xsd:choice>
+ <xsd:element name="dispatcher"
+ type="j2ee:dispatcherType"
+ minOccurs="0" maxOccurs="4"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="filter-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The logical name of the filter is declare
+ by using filter-nameType. This name is used to map the
+ filter. Each filter name is unique within the web
+ application.
+
+ Used in: filter, filter-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:extension base="j2ee:nonEmptyStringType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="filterType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The filterType is used to declare a filter in the web
+ application. The filter is mapped to either a servlet or a
+ URL pattern in the filter-mapping element, using the
+ filter-name value to reference. Filters can access the
+ initialization parameters declared in the deployment
+ descriptor at runtime via the FilterConfig interface.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="filter-name"
+ type="j2ee:filter-nameType"/>
+ <xsd:element name="filter-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The fully qualified classname of the filter.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="init-param"
+ type="j2ee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The init-param element contains a name/value pair as
+ an initialization param of a servlet filter
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="form-login-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The form-login-configType specifies the login and error
+ pages that should be used in form based login. If form based
+ authentication is not used, these elements are ignored.
+
+ Used in: login-config
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+
+ <xsd:element name="form-login-page"
+ type="j2ee:war-pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The form-login-page element defines the location in the web
+ app where the page that can be used for login can be
+ found. The path begins with a leading / and is interpreted
+ relative to the root of the WAR.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="form-error-page"
+ type="j2ee:war-pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The form-error-page element defines the location in
+ the web app where the error page that is displayed
+ when login is not successful can be found.
+ The path begins with a leading / and is interpreted
+ relative to the root of the WAR.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="http-methodType">
+ <xsd:annotation>
+
+ <xsd:documentation>
+
+ The http-method contains an HTTP method recognized by the
+ web-app, for example GET, POST, ...
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="GET"/>
+ <xsd:enumeration value="POST"/>
+ <xsd:enumeration value="PUT"/>
+ <xsd:enumeration value="DELETE"/>
+ <xsd:enumeration value="HEAD"/>
+ <xsd:enumeration value="OPTIONS"/>
+ <xsd:enumeration value="TRACE"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="listenerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The listenerType indicates the deployment properties for a web
+ application listener bean.
+
+ Used in: web-app:listenerType
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="listener-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The listener-class element declares a class in the
+ application must be registered as a web
+ application listener bean. The value is the fully
+ qualified classname of the listener class.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="locale-encoding-mapping-listType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The locale-encoding-mapping-list contains one or more
+ locale-encoding-mapping(s).
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="locale-encoding-mapping"
+ type="j2ee:locale-encoding-mappingType"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="locale-encoding-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The locale-encoding-mapping contains locale name and
+ encoding name. The locale name must be either "Language-code",
+ such as "ja", defined by ISO-639 or "Language-code_Country-code",
+ such as "ja_JP". "Country code" is defined by ISO-3166.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="locale"
+ type="j2ee:localeType"/>
+ <xsd:element name="encoding"
+ type="j2ee:encodingType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="localeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The localeType defines valid locale defined by ISO-639-1
+ and ISO-3166.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:restriction base="xsd:string">
+ <xsd:pattern value="[a-z]{2}(_|-)?([\p{L}\-\p{Nd}]{2})?"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="login-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The login-configType is used to configure the authentication
+ method that should be used, the realm name that should be
+ used for this application, and the attributes that are
+ needed by the form login mechanism.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="auth-method"
+ type="j2ee:auth-methodType"
+ minOccurs="0"/>
+ <xsd:element name="realm-name"
+ type="j2ee:string" minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The realm name element specifies the realm name to
+ use in HTTP Basic authorization.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="form-login-config"
+ type="j2ee:form-login-configType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="mime-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The mime-mappingType defines a mapping between an extension
+ and a mime type.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The extension element contains a string describing an
+ extension. example: "txt"
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:element name="extension"
+ type="j2ee:string"/>
+ <xsd:element name="mime-type"
+ type="j2ee:mime-typeType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="mime-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The mime-typeType is used to indicate a defined mime type.
+
+ Example:
+ "text/plain"
+
+ Used in: mime-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:pattern value="[\p{L}\-\p{Nd}]+/[\p{L}\-\p{Nd}\.]+"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="nonEmptyStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+ This type defines a string which contains at least one
+ character.
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:minLength value="1"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="security-constraintType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The security-constraintType is used to associate
+ security constraints with one or more web resource
+ collections
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="display-name"
+ type="j2ee:display-nameType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="web-resource-collection"
+ type="j2ee:web-resource-collectionType"
+ maxOccurs="unbounded"/>
+ <xsd:element name="auth-constraint"
+ type="j2ee:auth-constraintType"
+ minOccurs="0"/>
+ <xsd:element name="user-data-constraint"
+ type="j2ee:user-data-constraintType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="servlet-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The servlet-mappingType defines a mapping between a
+ servlet and a url pattern.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="servlet-name"
+ type="j2ee:servlet-nameType"/>
+ <xsd:element name="url-pattern"
+ type="j2ee:url-patternType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="servlet-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The servlet-name element contains the canonical name of the
+ servlet. Each servlet name is unique within the web
+ application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:extension base="j2ee:nonEmptyStringType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="servletType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The servletType is used to declare a servlet.
+ It contains the declarative data of a
+ servlet. If a jsp-file is specified and the load-on-startup
+ element is present, then the JSP should be precompiled and
+ loaded.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="servlet-name"
+ type="j2ee:servlet-nameType"/>
+ <xsd:choice>
+ <xsd:element name="servlet-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The servlet-class element contains the fully
+ qualified class name of the servlet.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="jsp-file"
+ type="j2ee:jsp-fileType"/>
+
+ </xsd:choice>
+
+ <xsd:element name="init-param"
+ type="j2ee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="load-on-startup"
+ type="j2ee:xsdIntegerType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The load-on-startup element indicates that this
+ servlet should be loaded (instantiated and have
+ its init() called) on the startup of the web
+ application. The optional contents of these
+ element must be an integer indicating the order in
+ which the servlet should be loaded. If the value
+ is a negative integer, or the element is not
+ present, the container is free to load the servlet
+ whenever it chooses. If the value is a positive
+ integer or 0, the container must load and
+ initialize the servlet as the application is
+ deployed. The container must guarantee that
+ servlets marked with lower integers are loaded
+ before servlets marked with higher integers. The
+ container may choose the order of loading of
+ servlets with the same load-on-start-up value.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="run-as"
+ type="j2ee:run-asType"
+ minOccurs="0"/>
+ <xsd:element name="security-role-ref"
+ type="j2ee:security-role-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="session-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The session-configType defines the session parameters
+ for this web application.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="session-timeout"
+ type="j2ee:xsdIntegerType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The session-timeout element defines the default
+ session timeout interval for all sessions created
+ in this web application. The specified timeout
+ must be expressed in a whole number of minutes.
+ If the timeout is 0 or less, the container ensures
+ the default behaviour of sessions is never to time
+ out. If this element is not specified, the container
+ must set its default timeout period.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="transport-guaranteeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The transport-guaranteeType 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: user-data-constraint
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="NONE"/>
+ <xsd:enumeration value="INTEGRAL"/>
+ <xsd:enumeration value="CONFIDENTIAL"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="user-data-constraintType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The user-data-constraintType is used to indicate how
+ data communicated between the client and container should be
+ protected.
+
+ Used in: security-constraint
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="transport-guarantee"
+ type="j2ee:transport-guaranteeType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="war-pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The elements that use this type designate a path starting
+ with a "/" and interpreted relative to the root of a WAR
+ file.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:pattern value="/.*"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="web-app-versionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type contains the recognized versions of
+ web-application supported. It is used to designate the
+ version of the web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:enumeration value="2.4"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="web-appType">
+
+ <xsd:choice minOccurs="0" maxOccurs="unbounded">
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="distributable"
+ type="j2ee:emptyType"/>
+ <xsd:element name="context-param"
+ type="j2ee:param-valueType">
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The context-param element contains the declaration
+ of a web application's servlet context
+ initialization parameters.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="filter"
+ type="j2ee:filterType"/>
+ <xsd:element name="filter-mapping"
+ type="j2ee:filter-mappingType"/>
+ <xsd:element name="listener"
+ type="j2ee:listenerType"/>
+ <xsd:element name="servlet"
+ type="j2ee:servletType"/>
+ <xsd:element name="servlet-mapping"
+ type="j2ee:servlet-mappingType"/>
+ <xsd:element name="session-config"
+ type="j2ee:session-configType"/>
+ <xsd:element name="mime-mapping"
+ type="j2ee:mime-mappingType"/>
+ <xsd:element name="welcome-file-list"
+ type="j2ee:welcome-file-listType"/>
+ <xsd:element name="error-page"
+ type="j2ee:error-pageType"/>
+ <xsd:element name="jsp-config"
+ type="j2ee:jsp-configType"/>
+ <xsd:element name="security-constraint"
+ type="j2ee:security-constraintType"/>
+ <xsd:element name="login-config"
+ type="j2ee:login-configType"/>
+ <xsd:element name="security-role"
+ type="j2ee:security-roleType"/>
+ <xsd:group ref="j2ee:jndiEnvironmentRefsGroup"/>
+ <xsd:element name="message-destination"
+ type="j2ee:message-destinationType"/>
+ <xsd:element name="locale-encoding-mapping-list"
+ type="j2ee:locale-encoding-mapping-listType"/>
+ </xsd:choice>
+
+ <xsd:attribute name="version"
+ type="j2ee:web-app-versionType"
+ use="required"/>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="web-resource-collectionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The web-resource-collectionType is used to identify a subset
+ of the resources and HTTP methods on those resources within
+ a web application to which a security constraint applies. If
+ no HTTP methods are specified, then the security constraint
+ applies to all HTTP methods.
+
+ Used in: security-constraint
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="web-resource-name"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The web-resource-name contains the name of this web
+ resource collection.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="url-pattern"
+ type="j2ee:url-patternType"
+ maxOccurs="unbounded"/>
+ <xsd:element name="http-method"
+ type="j2ee:http-methodType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="welcome-file-listType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The welcome-file-list contains an ordered list of welcome
+ files elements.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="welcome-file"
+ type="j2ee:string"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The welcome-file element contains file name to use
+ as a default welcome file, such as index.html
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-app_2_5.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-app_2_5.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-app_2_5.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1268 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema"
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="2.5">
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)web-app_2_5.xsds 1.62 05/08/06
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2003-2006 Sun Microsystems, Inc.
+ 4150 Network Circle
+ Santa Clara, California 95054
+ U.S.A
+ All rights reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This is the XML Schema for the Servlet 2.5 deployment descriptor.
+ The deployment descriptor must be named "WEB-INF/web.xml" in the
+ web application's war file. All Servlet deployment descriptors
+ must indicate the web application schema by using the Java EE
+ namespace:
+
+ http://java.sun.com/xml/ns/javaee
+
+ and by indicating the version of the schema by
+ using the version element as shown below:
+
+ <web-app xmlns="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="..."
+ version="2.5">
+ ...
+ </web-app>
+
+ The instance documents may indicate the published version of
+ the schema using the xsi:schemaLocation attribute for Java EE
+ namespace with the following location:
+
+ http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The following conventions apply to all Java EE
+ deployment descriptor elements unless indicated otherwise.
+
+ - In elements that specify a pathname to a file within the
+ same JAR file, relative filenames (i.e., those not
+ starting with "/") are considered relative to the root of
+ the JAR file's namespace. Absolute filenames (i.e., those
+ starting with "/") also specify names in the root of the
+ JAR file's namespace. In general, relative names are
+ preferred. The exception is .war files where absolute
+ names are preferred for consistency with the Servlet API.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="javaee_5.xsd"/>
+ <xsd:include schemaLocation="jsp_2_1.xsd"/>
+
+
+<!-- **************************************************** -->
+
+ <xsd:element name="web-app" type="javaee:web-appType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The web-app element is the root of the deployment
+ descriptor for a web application. Note that the sub-elements
+ of this element can be in the arbitrary order. Because of
+ that, the multiplicity of the elements of distributable,
+ session-config, welcome-file-list, jsp-config, login-config,
+ and locale-encoding-mapping-list was changed from "?" to "*"
+ in this schema. However, the deployment descriptor instance
+ file must not contain multiple elements of session-config,
+ jsp-config, and login-config. When there are multiple elements of
+ welcome-file-list or locale-encoding-mapping-list, the container
+ must concatenate the element contents. The multiple occurence
+ of the element distributable is redundant and the container
+ treats that case exactly in the same way when there is only
+ one distributable.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:unique name="web-app-servlet-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The servlet element contains the name of a servlet.
+ The name must be unique within the web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:servlet"/>
+ <xsd:field xpath="javaee:servlet-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="web-app-filter-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The filter element contains the name of a filter.
+ The name must be unique within the web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:filter"/>
+ <xsd:field xpath="javaee:filter-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="web-app-ejb-local-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-local-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the web
+ application's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the web application.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:ejb-local-ref"/>
+ <xsd:field xpath="javaee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="web-app-ejb-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The ejb-ref-name element contains the name of an EJB
+ reference. The EJB reference is an entry in the web
+ application's environment and is relative to the
+ java:comp/env context. The name must be unique within
+ the web application.
+
+ It is recommended that name is prefixed with "ejb/".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:ejb-ref"/>
+ <xsd:field xpath="javaee:ejb-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="web-app-resource-env-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-env-ref-name element specifies the name of
+ a resource environment reference; its value is the
+ environment entry name used in the web application code.
+ The name is a JNDI name relative to the java:comp/env
+ context and must be unique within a web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:resource-env-ref"/>
+ <xsd:field xpath="javaee:resource-env-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="web-app-message-destination-ref-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The message-destination-ref-name element specifies the name of
+ a message destination reference; its value is the
+ environment entry name used in the web application code.
+ The name is a JNDI name relative to the java:comp/env
+ context and must be unique within a web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:message-destination-ref"/>
+ <xsd:field xpath="javaee:message-destination-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="web-app-res-ref-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The res-ref-name element specifies the name of a
+ resource manager connection factory reference. The name
+ is a JNDI name relative to the java:comp/env context.
+ The name must be unique within a web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:resource-ref"/>
+ <xsd:field xpath="javaee:res-ref-name"/>
+ </xsd:unique>
+
+ <xsd:unique name="web-app-env-entry-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The env-entry-name element contains the name of a web
+ application's environment entry. The name is a JNDI
+ name relative to the java:comp/env context. The name
+ must be unique within a web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:selector xpath="javaee:env-entry"/>
+ <xsd:field xpath="javaee:env-entry-name"/>
+ </xsd:unique>
+
+ <xsd:key name="web-app-role-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ A role-name-key is specified to allow the references
+ from the security-role-refs.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:security-role"/>
+ <xsd:field xpath="javaee:role-name"/>
+ </xsd:key>
+
+ <xsd:keyref name="web-app-role-name-references"
+ refer="javaee:web-app-role-name-key">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The keyref indicates the references from
+ security-role-ref to a specified role-name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="javaee:servlet/javaee:security-role-ref"/>
+ <xsd:field xpath="javaee:role-link"/>
+ </xsd:keyref>
+ </xsd:element>
+
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="auth-constraintType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The auth-constraintType indicates the user roles that
+ should be permitted access to this resource
+ collection. The role-name used here must either correspond
+ to the role-name of one of the security-role elements
+ defined for this web application, or be the specially
+ reserved role-name "*" that is a compact syntax for
+ indicating all roles in the web application. If both "*"
+ and rolenames appear, the container interprets this as all
+ roles. If no roles are defined, no user is allowed access
+ to the portion of the web application described by the
+ containing security-constraint. The container matches
+ role names case sensitively when determining access.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="role-name"
+ type="javaee:role-nameType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="auth-methodType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The auth-methodType is used to configure the authentication
+ mechanism for the web application. As a prerequisite to
+ gaining access to any web resources which are protected by
+ an authorization constraint, a user must have authenticated
+ using the configured mechanism. Legal values are "BASIC",
+ "DIGEST", "FORM", "CLIENT-CERT", or a vendor-specific
+ authentication scheme.
+
+ Used in: login-config
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="dispatcherType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The dispatcher has four legal values: FORWARD, REQUEST, INCLUDE,
+ and ERROR. A value of FORWARD means the Filter will be applied
+ under RequestDispatcher.forward() calls. A value of REQUEST
+ means the Filter will be applied under ordinary client calls to
+ the path or servlet. A value of INCLUDE means the Filter will be
+ applied under RequestDispatcher.include() calls. A value of
+ ERROR means the Filter will be applied under the error page
+ mechanism. The absence of any dispatcher elements in a
+ filter-mapping indicates a default of applying filters only under
+ ordinary client calls to the path or servlet.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="FORWARD"/>
+ <xsd:enumeration value="INCLUDE"/>
+ <xsd:enumeration value="REQUEST"/>
+ <xsd:enumeration value="ERROR"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="encodingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The encodingType defines IANA character sets.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:restriction base="xsd:string">
+ <xsd:pattern value="[^\s]+"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="error-codeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The error-code contains an HTTP error code, ex: 404
+
+ Used in: error-page
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:xsdPositiveIntegerType">
+ <xsd:pattern value="\d{3}"/>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="error-pageType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The error-pageType contains a mapping between an error code
+ or exception type to the path of a resource in the web
+ application.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:choice>
+ <xsd:element name="error-code"
+ type="javaee:error-codeType"/>
+
+ <xsd:element name="exception-type"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The exception-type contains a fully qualified class
+ name of a Java exception type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:choice>
+
+ <xsd:element name="location"
+ type="javaee:war-pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The location element contains the location of the
+ resource in the web application relative to the root of
+ the web application. The value of the location must have
+ a leading `/'.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="filter-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Declaration of the filter mappings in this web
+ application is done by using filter-mappingType.
+ The container uses the filter-mapping
+ declarations to decide which filters to apply to a request,
+ and in what order. The container matches the request URI to
+ a Servlet in the normal way. To determine which filters to
+ apply it matches filter-mapping declarations either on
+ servlet-name, or on url-pattern for each filter-mapping
+ element, depending on which style is used. The order in
+ which filters are invoked is the order in which
+ filter-mapping declarations that match a request URI for a
+ servlet appear in the list of filter-mapping elements.The
+ filter-name value must be the value of the filter-name
+ sub-elements of one of the filter declarations in the
+ deployment descriptor.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="filter-name"
+ type="javaee:filter-nameType"/>
+ <xsd:choice minOccurs="1" maxOccurs="unbounded">
+ <xsd:element name="url-pattern"
+ type="javaee:url-patternType"/>
+ <xsd:element name="servlet-name"
+ type="javaee:servlet-nameType"/>
+ </xsd:choice>
+ <xsd:element name="dispatcher"
+ type="javaee:dispatcherType"
+ minOccurs="0" maxOccurs="4"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="filter-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The logical name of the filter is declare
+ by using filter-nameType. This name is used to map the
+ filter. Each filter name is unique within the web
+ application.
+
+ Used in: filter, filter-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:extension base="javaee:nonEmptyStringType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="filterType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The filterType is used to declare a filter in the web
+ application. The filter is mapped to either a servlet or a
+ URL pattern in the filter-mapping element, using the
+ filter-name value to reference. Filters can access the
+ initialization parameters declared in the deployment
+ descriptor at runtime via the FilterConfig interface.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="filter-name"
+ type="javaee:filter-nameType"/>
+ <xsd:element name="filter-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The fully qualified classname of the filter.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="init-param"
+ type="javaee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The init-param element contains a name/value pair as
+ an initialization param of a servlet filter
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="form-login-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The form-login-configType specifies the login and error
+ pages that should be used in form based login. If form based
+ authentication is not used, these elements are ignored.
+
+ Used in: login-config
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+
+ <xsd:element name="form-login-page"
+ type="javaee:war-pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The form-login-page element defines the location in the web
+ app where the page that can be used for login can be
+ found. The path begins with a leading / and is interpreted
+ relative to the root of the WAR.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="form-error-page"
+ type="javaee:war-pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The form-error-page element defines the location in
+ the web app where the error page that is displayed
+ when login is not successful can be found.
+ The path begins with a leading / and is interpreted
+ relative to the root of the WAR.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="http-methodType">
+ <xsd:annotation>
+
+ <xsd:documentation>
+
+ A HTTP method type as defined in HTTP 1.1 section 2.2.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:restriction base="xsd:token">
+ <xsd:pattern value="[\p{L}-[\p{Cc}\p{Z}]]+"/>
+ </xsd:restriction>
+
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="load-on-startupType">
+ <xsd:union memberTypes="javaee:null-charType xsd:integer"/>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="locale-encoding-mapping-listType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The locale-encoding-mapping-list contains one or more
+ locale-encoding-mapping(s).
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="locale-encoding-mapping"
+ type="javaee:locale-encoding-mappingType"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="locale-encoding-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The locale-encoding-mapping contains locale name and
+ encoding name. The locale name must be either "Language-code",
+ such as "ja", defined by ISO-639 or "Language-code_Country-code",
+ such as "ja_JP". "Country code" is defined by ISO-3166.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="locale"
+ type="javaee:localeType"/>
+ <xsd:element name="encoding"
+ type="javaee:encodingType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="localeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The localeType defines valid locale defined by ISO-639-1
+ and ISO-3166.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:restriction base="xsd:string">
+ <xsd:pattern value="[a-z]{2}(_|-)?([\p{L}\-\p{Nd}]{2})?"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="login-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The login-configType is used to configure the authentication
+ method that should be used, the realm name that should be
+ used for this application, and the attributes that are
+ needed by the form login mechanism.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="auth-method"
+ type="javaee:auth-methodType"
+ minOccurs="0"/>
+ <xsd:element name="realm-name"
+ type="javaee:string" minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The realm name element specifies the realm name to
+ use in HTTP Basic authorization.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="form-login-config"
+ type="javaee:form-login-configType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="mime-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The mime-mappingType defines a mapping between an extension
+ and a mime type.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The extension element contains a string describing an
+ extension. example: "txt"
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:element name="extension"
+ type="javaee:string"/>
+ <xsd:element name="mime-type"
+ type="javaee:mime-typeType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="mime-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The mime-typeType is used to indicate a defined mime type.
+
+ Example:
+ "text/plain"
+
+ Used in: mime-mapping
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:pattern value="[^\p{Cc}^\s]+/[^\p{Cc}^\s]+"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="nonEmptyStringType">
+ <xsd:annotation>
+ <xsd:documentation>
+ This type defines a string which contains at least one
+ character.
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:minLength value="1"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="null-charType">
+ <xsd:restriction base="xsd:string">
+ <xsd:enumeration value=""/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="security-constraintType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The security-constraintType is used to associate
+ security constraints with one or more web resource
+ collections
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="display-name"
+ type="javaee:display-nameType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="web-resource-collection"
+ type="javaee:web-resource-collectionType"
+ maxOccurs="unbounded"/>
+ <xsd:element name="auth-constraint"
+ type="javaee:auth-constraintType"
+ minOccurs="0"/>
+ <xsd:element name="user-data-constraint"
+ type="javaee:user-data-constraintType"
+ minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="servlet-mappingType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The servlet-mappingType defines a mapping between a
+ servlet and a url pattern.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="servlet-name"
+ type="javaee:servlet-nameType"/>
+ <xsd:element name="url-pattern"
+ type="javaee:url-patternType"
+ minOccurs="1" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="servlet-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The servlet-name element contains the canonical name of the
+ servlet. Each servlet name is unique within the web
+ application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:extension base="javaee:nonEmptyStringType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="servletType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The servletType is used to declare a servlet.
+ It contains the declarative data of a
+ servlet. If a jsp-file is specified and the load-on-startup
+ element is present, then the JSP should be precompiled and
+ loaded.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="servlet-name"
+ type="javaee:servlet-nameType"/>
+ <xsd:choice>
+ <xsd:element name="servlet-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The servlet-class element contains the fully
+ qualified class name of the servlet.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="jsp-file"
+ type="javaee:jsp-fileType"/>
+
+ </xsd:choice>
+
+ <xsd:element name="init-param"
+ type="javaee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="load-on-startup"
+ type="javaee:load-on-startupType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The load-on-startup element indicates that this
+ servlet should be loaded (instantiated and have
+ its init() called) on the startup of the web
+ application. The optional contents of these
+ element must be an integer indicating the order in
+ which the servlet should be loaded. If the value
+ is a negative integer, or the element is not
+ present, the container is free to load the servlet
+ whenever it chooses. If the value is a positive
+ integer or 0, the container must load and
+ initialize the servlet as the application is
+ deployed. The container must guarantee that
+ servlets marked with lower integers are loaded
+ before servlets marked with higher integers. The
+ container may choose the order of loading of
+ servlets with the same load-on-start-up value.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="run-as"
+ type="javaee:run-asType"
+ minOccurs="0"/>
+ <xsd:element name="security-role-ref"
+ type="javaee:security-role-refType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="session-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The session-configType defines the session parameters
+ for this web application.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="session-timeout"
+ type="javaee:xsdIntegerType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The session-timeout element defines the default
+ session timeout interval for all sessions created
+ in this web application. The specified timeout
+ must be expressed in a whole number of minutes.
+ If the timeout is 0 or less, the container ensures
+ the default behaviour of sessions is never to time
+ out. If this element is not specified, the container
+ must set its default timeout period.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="transport-guaranteeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The transport-guaranteeType 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: user-data-constraint
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="NONE"/>
+ <xsd:enumeration value="INTEGRAL"/>
+ <xsd:enumeration value="CONFIDENTIAL"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="user-data-constraintType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The user-data-constraintType is used to indicate how
+ data communicated between the client and container should be
+ protected.
+
+ Used in: security-constraint
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="transport-guarantee"
+ type="javaee:transport-guaranteeType"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="war-pathType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The elements that use this type designate a path starting
+ with a "/" and interpreted relative to the root of a WAR
+ file.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:pattern value="/.*"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:simpleType name="web-app-versionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type contains the recognized versions of
+ web-application supported. It is used to designate the
+ version of the web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:enumeration value="2.5"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="web-appType">
+
+ <xsd:choice minOccurs="0" maxOccurs="unbounded">
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="distributable"
+ type="javaee:emptyType"/>
+ <xsd:element name="context-param"
+ type="javaee:param-valueType">
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The context-param element contains the declaration
+ of a web application's servlet context
+ initialization parameters.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="filter"
+ type="javaee:filterType"/>
+ <xsd:element name="filter-mapping"
+ type="javaee:filter-mappingType"/>
+ <xsd:element name="listener"
+ type="javaee:listenerType"/>
+ <xsd:element name="servlet"
+ type="javaee:servletType"/>
+ <xsd:element name="servlet-mapping"
+ type="javaee:servlet-mappingType"/>
+ <xsd:element name="session-config"
+ type="javaee:session-configType"/>
+ <xsd:element name="mime-mapping"
+ type="javaee:mime-mappingType"/>
+ <xsd:element name="welcome-file-list"
+ type="javaee:welcome-file-listType"/>
+ <xsd:element name="error-page"
+ type="javaee:error-pageType"/>
+ <xsd:element name="jsp-config"
+ type="javaee:jsp-configType"/>
+ <xsd:element name="security-constraint"
+ type="javaee:security-constraintType"/>
+ <xsd:element name="login-config"
+ type="javaee:login-configType"/>
+ <xsd:element name="security-role"
+ type="javaee:security-roleType"/>
+ <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
+ <xsd:element name="message-destination"
+ type="javaee:message-destinationType"/>
+ <xsd:element name="locale-encoding-mapping-list"
+ type="javaee:locale-encoding-mapping-listType"/>
+ </xsd:choice>
+
+ <xsd:attribute name="version"
+ type="javaee:web-app-versionType"
+ use="required"/>
+ <xsd:attribute name="id" type="xsd:ID"/>
+
+ <xsd:attribute name="metadata-complete" type="xsd:boolean">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The metadata-complete attribute defines whether this
+ deployment descriptor and other related deployment
+ descriptors for this module (e.g., web service
+ descriptors) are complete, or whether the class
+ files available to this module and packaged with
+ this application should be examined for annotations
+ that specify deployment information.
+
+ If metadata-complete is set to "true", the deployment
+ tool must ignore any annotations that specify deployment
+ information, which might be present in the class files
+ of the application.
+
+ If metadata-complete is not specified or is set to
+ "false", the deployment tool must examine the class
+ files of the application for annotations, as
+ specified by the specifications.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:attribute>
+
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="web-resource-collectionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The web-resource-collectionType is used to identify a subset
+ of the resources and HTTP methods on those resources within
+ a web application to which a security constraint applies. If
+ no HTTP methods are specified, then the security constraint
+ applies to all HTTP methods.
+
+ Used in: security-constraint
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="web-resource-name"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The web-resource-name contains the name of this web
+ resource collection.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="description"
+ type="javaee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="url-pattern"
+ type="javaee:url-patternType"
+ maxOccurs="unbounded"/>
+ <xsd:element name="http-method"
+ type="javaee:http-methodType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="welcome-file-listType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The welcome-file-list contains an ordered list of welcome
+ files elements.
+
+ Used in: web-app
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="welcome-file"
+ type="xsd:string"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The welcome-file element contains file name to use
+ as a default welcome file, such as index.html
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-facesconfig_1_2.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-facesconfig_1_2.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-facesconfig_1_2.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,2071 @@
+<?xml version = "1.0" encoding = "UTF-8"?>
+
+<xsd:schema
+ targetNamespace="http://java.sun.com/xml/ns/javaee"
+ xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ xmlns:xml="http://www.w3.org/XML/1998/namespace"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="1.2">
+
+ <xsd:annotation>
+ <xsd:documentation>
+ $Id: web-facesconfig_1_2.xsd,v 1.11 2006/03/27 00:12:24 rogerk Exp $
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2005 Sun Microsystems, Inc.,
+ 901 San Antonio Road,
+ Palo Alto, California 94303, U.S.A.
+ All rights reserved.
+
+ Sun Microsystems, Inc. has intellectual property
+ rights relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, Java EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ <![CDATA[
+
+ The XML Schema for the JavaServer Faces Application
+ Configuration File (Version 1.2).
+
+ All JavaServer Faces configuration files must indicate
+ the JavaServer Faces schema by indicating the JavaServer
+ Faces namespace:
+
+ http://java.sun.com/xml/ns/javaee
+
+ and by indicating the version of the schema by
+ using the version element as shown below:
+
+ <faces-config xmlns="http://java.sun.com/xml/ns/javaee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="..."
+ version="1.2">
+ ...
+ </faces-config>
+
+ The instance documents may indicate the published
+ version of the schema using xsi:schemaLocation attribute
+ for javaee namespace with the following location:
+
+ http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd
+
+ ]]>
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="javaee_5.xsd"/>
+
+ <!-- **************************************************** -->
+
+ <xsd:element name = "faces-config" type="javaee:faces-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "faces-config" element is the root of the configuration
+ information hierarchy, and contains nested elements for all
+ of the other configuration settings.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:unique name="faces-config-converter-ID-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Converter IDs must be unique within a document.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:selector xpath="javaee:converter"/>
+ <xsd:field xpath="javaee:converter-id"/>
+ </xsd:unique>
+
+ <xsd:unique name="faces-config-converter-for-class-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ 'converter-for-class' element values must be unique
+ within a document.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:selector xpath="javaee:converter"/>
+ <xsd:field xpath="javaee:converter-for-class"/>
+ </xsd:unique>
+
+ <xsd:unique name="faces-config-validator-ID-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Validator IDs must be unique within a document.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:selector xpath="javaee:validator"/>
+ <xsd:field xpath="javaee:validator-id"/>
+ </xsd:unique>
+
+ <xsd:unique name="faces-config-managed-bean-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Managed bean names must be unique within a document.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:selector xpath="javaee:managed-bean"/>
+ <xsd:field xpath="javaee:managed-bean-name"/>
+ </xsd:unique>
+ </xsd:element>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "faces-config" element is the root of the configuration
+ information hierarchy, and contains nested elements for all
+ of the other configuration settings.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:choice minOccurs="0" maxOccurs="unbounded">
+ <xsd:element name="application"
+ type="javaee:faces-config-applicationType"/>
+ <xsd:element name="factory"
+ type="javaee:faces-config-factoryType"/>
+ <xsd:element name="component"
+ type="javaee:faces-config-componentType"/>
+ <xsd:element name="converter"
+ type="javaee:faces-config-converterType"/>
+ <xsd:element name="managed-bean"
+ type="javaee:faces-config-managed-beanType"/>
+ <xsd:element name="navigation-rule"
+ type="javaee:faces-config-navigation-ruleType"/>
+ <xsd:element name="referenced-bean"
+ type="javaee:faces-config-referenced-beanType"/>
+ <xsd:element name="render-kit"
+ type="javaee:faces-config-render-kitType"/>
+ <xsd:element name="lifecycle"
+ type="javaee:faces-config-lifecycleType"/>
+ <xsd:element name="validator"
+ type="javaee:faces-config-validatorType"/>
+ <xsd:element name="faces-config-extension"
+ type="javaee:faces-config-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:choice>
+ <xsd:attribute name = "id" type = "xsd:ID"/>
+ <xsd:attribute name="version"
+ type="javaee:faces-config-versionType"
+ use="required"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name = "faces-config-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for faces-config. It may contain
+ implementation specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-applicationType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "application" element provides a mechanism to define the
+ various per-application-singleton implementation artifacts for
+ a particular web application that is utilizing
+ JavaServer Faces. For nested elements that are not specified,
+ the JSF implementation must provide a suitable default.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:choice minOccurs="0" maxOccurs="unbounded">
+ <xsd:element name="action-listener"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "action-listener" element contains the fully
+ qualified class name of the concrete
+ ActionListener implementation class that will be
+ called during the Invoke Application phase of the
+ request processing lifecycle.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="default-render-kit-id"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "default-render-kit-id" element allows the
+ application to define a renderkit to be used other
+ than the standard one.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="message-bundle"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The base name of a resource bundle representing
+ the message resources for this application. See
+ the JavaDocs for the "java.util.ResourceBundle"
+ class for more information on the syntax of
+ resource bundle names.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="navigation-handler"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "navigation-handler" element contains the
+ fully qualified class name of the concrete
+ NavigationHandler implementation class that will
+ be called during the Invoke Application phase
+ of the request processing lifecycle, if the
+ default ActionListener (provided by the JSF
+ implementation) is used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="view-handler"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "view-handler" element contains the fully
+ qualified class name of the concrete ViewHandler
+ implementation class that will be called during
+ the Restore View and Render Response phases of the
+ request processing lifecycle. The faces
+ implementation must provide a default
+ implementation of this class.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="state-manager"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "state-manager" element contains the fully
+ qualified class name of the concrete StateManager
+ implementation class that will be called during
+ the Restore View and Render Response phases of the
+ request processing lifecycle. The faces
+ implementation must provide a default
+ implementation of this class.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="el-resolver"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "el-resolver" element contains the fully
+ qualified class name of the concrete
+ javax.el.ELResolver implementation class
+ that will be used during the processing of
+ EL expressions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="property-resolver"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "property-resolver" element contains the fully
+ qualified class name of the concrete
+ PropertyResolver implementation class that will
+ be used during the processing of value binding
+ expressions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="variable-resolver"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "variable-resolver" element contains the fully
+ qualified class name of the concrete
+ VariableResolver implementation class that will
+ be used during the processing of value binding
+ expressions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element
+ name="locale-config"
+ type="javaee:faces-config-locale-configType"/>
+ <xsd:element
+ name="resource-bundle"
+ type="javaee:faces-config-application-resource-bundleType"/>
+ <xsd:element name="application-extension"
+ type="javaee:faces-config-application-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:choice>
+ <xsd:attribute name = "id" type = "xsd:ID"/>
+ </xsd:complexType>
+
+ <xsd:complexType name="faces-config-application-resource-bundleType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The resource-bundle element inside the application element
+ references a java.util.ResourceBundle instance by name
+ using the var element. ResourceBundles referenced in this
+ manner may be returned by a call to
+ Application.getResourceBundle() passing the current
+ FacesContext for this request and the value of the var
+ element below.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="base-name"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The fully qualified class name of the
+ java.util.ResourceBundle instance.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="var"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The name by which this ResourceBundle instance
+ is retrieved by a call to
+ Application.getResourceBundle().
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name = "faces-config-application-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for application. It may contain
+ implementation specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name = "faces-config-factoryType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "factory" element provides a mechanism to define the
+ various Factories that comprise parts of the implementation
+ of JavaServer Faces. For nested elements that are not
+ specified, the JSF implementation must provide a suitable
+ default.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:choice minOccurs="0" maxOccurs="unbounded">
+ <xsd:element name="application-factory"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "application-factory" element contains the
+ fully qualified class name of the concrete
+ ApplicationFactory implementation class that will
+ be called when
+ FactoryFinder.getFactory(APPLICATION_FACTORY) is
+ called.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="faces-context-factory"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "faces-context-factory" element contains the
+ fully qualified class name of the concrete
+ FacesContextFactory implementation class that will
+ be called when
+ FactoryFinder.getFactory(FACES_CONTEXT_FACTORY)
+ is called.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="lifecycle-factory"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "lifecycle-factory" element contains the fully
+ qualified class name of the concrete LifecycleFactory
+ implementation class that will be called when
+ FactoryFinder.getFactory(LIFECYCLE_FACTORY) is called.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="render-kit-factory"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "render-kit-factory" element contains the fully
+ qualified class name of the concrete RenderKitFactory
+ implementation class that will be called when
+ FactoryFinder.getFactory(RENDER_KIT_FACTORY) is
+ called.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="factory-extension"
+ type="javaee:faces-config-factory-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:choice>
+ <xsd:attribute name = "id" type = "xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name = "faces-config-factory-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for factory. It may contain
+ implementation specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-attributeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "attribute" element represents a named, typed, value
+ associated with the parent UIComponent via the generic
+ attributes mechanism.
+
+ Attribute names must be unique within the scope of the parent
+ (or related) component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="attribute-name"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "attribute-name" element represents the name under
+ which the corresponding value will be stored, in the
+ generic attributes of the UIComponent we are related
+ to.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="attribute-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "attribute-class" element represents the Java type
+ of the value associated with this attribute name.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="default-value"
+ type="javaee:faces-config-default-valueType"
+ minOccurs="0"/>
+ <xsd:element name="suggested-value"
+ type="javaee:faces-config-suggested-valueType"
+ minOccurs="0"/>
+ <xsd:element name="attribute-extension"
+ type="javaee:faces-config-attribute-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name = "id" type = "xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name = "faces-config-attribute-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for attribute. It may contain
+ implementation specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-componentType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "component" element represents a concrete UIComponent
+ implementation class that should be registered under the
+ specified type identifier, along with its associated
+ properties and attributes. Component types must be unique
+ within the entire web application.
+
+ Nested "attribute" elements identify generic attributes that
+ are recognized by the implementation logic of this component.
+ Nested "property" elements identify JavaBeans properties of
+ the component class that may be exposed for manipulation
+ via tools.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="component-type"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "component-type" element represents the name under
+ which the corresponding UIComponent class should be
+ registered.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="component-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "component-class" element represents the fully
+ qualified class name of a concrete UIComponent
+ implementation class.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="facet"
+ type="javaee:faces-config-facetType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="attribute"
+ type="javaee:faces-config-attributeType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="property"
+ type="javaee:faces-config-propertyType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="component-extension"
+ type="javaee:faces-config-component-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-component-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+ Extension element for component. It may contain
+ implementation specific content.
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-default-localeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "default-locale" element declares the default locale
+ for this application instance.
+
+ It must be specified as :language:[_:country:[_:variant:]]
+ without the colons, for example "ja_JP_SJIS". The
+ separators between the segments may be '-' or '_'.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="javaee:faces-config-localeType">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+
+ <xsd:complexType name="faces-config-default-valueType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "default-value" contains the value for the property or
+ attribute in which this element resides. This value differs
+ from the "suggested-value" in that the property or attribute
+ must take the value, whereas in "suggested-value" taking the
+ value is optional.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="faces-config-el-expressionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ EL expressions present within a faces config file
+ must start with the character sequence of '#{' and
+ end with '}'.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:string">
+ <xsd:pattern value="#\{.*\}"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-facetType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Define the name and other design-time information for a facet
+ that is associated with a renderer or a component.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="facet-name"
+ type="javaee:java-identifierType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "facet-name" element represents the facet name
+ under which a UIComponent will be added to its parent.
+ It must be of type "Identifier".
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="facet-extension"
+ type="javaee:faces-config-facet-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-facet-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for facet. It may contain implementation
+ specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-from-view-idType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The value of from-view-id must contain one of the following
+ values:
+
+ - The exact match for a view identifier that is recognized
+ by the the ViewHandler implementation being used (such as
+ "/index.jsp" if you are using the default ViewHandler).
+
+ - A proper prefix of a view identifier, plus a trailing
+ "*" character. This pattern indicates that all view
+ identifiers that match the portion of the pattern up to
+ the asterisk will match the surrounding rule. When more
+ than one match exists, the match with the longest pattern
+ is selected.
+
+ - An "*" character, which means that this pattern applies
+ to all view identifiers.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-from-actionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "from-action" element contains an action reference
+ expression that must have been executed (by the default
+ ActionListener for handling application level events)
+ in order to select the navigation rule. If not specified,
+ this rule will be relevant no matter which action reference
+ was executed (or if no action reference was executed).
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="javaee:faces-config-el-expressionType">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-converterType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "converter" element represents a concrete Converter
+ implementation class that should be registered under the
+ specified converter identifier. Converter identifiers must
+ be unique within the entire web application.
+
+ Nested "attribute" elements identify generic attributes that
+ may be configured on the corresponding UIComponent in order
+ to affect the operation of the Converter. Nested "property"
+ elements identify JavaBeans properties of the Converter
+ implementation class that may be configured to affect the
+ operation of the Converter. "attribute" and "property"
+ elements are intended to allow component developers to
+ more completely describe their components to tools and users.
+ These elements have no required runtime semantics.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:choice>
+ <xsd:element name="converter-id"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "converter-id" element represents the
+ identifier under which the corresponding
+ Converter class should be registered.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="converter-for-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "converter-for-class" element represents the
+ fully qualified class name for which a Converter
+ class will be registered.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:choice>
+
+ <xsd:element name="converter-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "converter-class" element represents the fully
+ qualified class name of a concrete Converter
+ implementation class.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="attribute"
+ type="javaee:faces-config-attributeType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Nested "attribute" elements identify generic
+ attributes that may be configured on the
+ corresponding UIComponent in order to affect the
+ operation of the Converter. This attribute is
+ primarily for design-time tools and is not
+ specified to have any meaning at runtime.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="property"
+ type="javaee:faces-config-propertyType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Nested "property" elements identify JavaBeans
+ properties of the Converter implementation class
+ that may be configured to affect the operation of
+ the Converter. This attribute is primarily for
+ design-time tools and is not specified to have
+ any meaning at runtime.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="converter-extension"
+ type="javaee:faces-config-converter-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name = "faces-config-converter-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for converter. It may contain
+ implementation specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-lifecycleType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "lifecycle" element provides a mechanism to specify
+ modifications to the behaviour of the default Lifecycle
+ implementation for this web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="phase-listener"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "phase-listener" element contains the fully
+ qualified class name of the concrete PhaseListener
+ implementation class that will be registered on
+ the Lifecycle.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="lifecycle-extension"
+ type="javaee:faces-config-lifecycle-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name = "faces-config-lifecycle-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for lifecycle. It may contain
+ implementation specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="faces-config-localeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The localeType defines valid locale defined by ISO-639-1
+ and ISO-3166.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:restriction base="xsd:string">
+ <xsd:pattern value="[a-z]{2}(_|-)?([\p{L}\-\p{Nd}]{2})?"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-locale-configType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "locale-config" element allows the app developer to
+ declare the supported locales for this application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="default-locale"
+ type="javaee:faces-config-default-localeType"
+ minOccurs="0">
+ </xsd:element>
+ <xsd:element name="supported-locale"
+ type="javaee:faces-config-supported-localeType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-managed-beanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "managed-bean" element represents a JavaBean, of a
+ particular class, that will be dynamically instantiated
+ at runtime (by the default VariableResolver implementation)
+ if it is referenced as the first element of a value binding
+ expression, and no corresponding bean can be identified in
+ any scope. In addition to the creation of the managed bean,
+ and the optional storing of it into the specified scope,
+ the nested managed-property elements can be used to
+ initialize the contents of settable JavaBeans properties of
+ the created instance.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="managed-bean-name"
+ type="javaee:java-identifierType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "managed-bean-name" element represents the
+ attribute name under which a managed bean will
+ be searched for, as well as stored (unless the
+ "managed-bean-scope" value is "none").
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="managed-bean-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "managed-bean-class" element represents the fully
+ qualified class name of the Java class that will be
+ used`to instantiate a new instance if creation of the
+ specified`managed bean is requested.
+
+ The specified class must conform to standard JavaBeans
+ conventions. In particular, it must have a public
+ zero-arguments constructor, and zero or more public
+ property setters.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element
+ name="managed-bean-scope"
+ type="javaee:faces-config-managed-bean-scopeOrNoneType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "managed-bean-scope" element represents the scope
+ into which a newly created instance of the specified
+ managed bean will be stored (unless the value is
+ "none").
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:choice>
+ <xsd:element name="managed-property"
+ type="javaee:faces-config-managed-propertyType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="map-entries"
+ type="javaee:faces-config-map-entriesType"/>
+ <xsd:element name="list-entries"
+ type="javaee:faces-config-list-entriesType"/>
+ </xsd:choice>
+ <xsd:element name="managed-bean-extension"
+ type="javaee:faces-config-managed-bean-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name = "faces-config-managed-bean-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for managed-bean. It may contain
+ implementation specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-managed-bean-scopeOrNoneType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ <![CDATA[
+ Defines the legal values for the <managed-bean-scope>
+ element's body content, which includes all of the scopes
+ normally used in a web application, plus the "none" value
+ indicating that a created bean should not be stored into
+ any scope.
+ ]]>
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string">
+ <xsd:enumeration value="request"/>
+ <xsd:enumeration value="session"/>
+ <xsd:enumeration value="application"/>
+ <xsd:enumeration value="none"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-managed-propertyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "managed-property" element represents an individual
+ property of a managed bean that will be configured to the
+ specified value (or value set) if the corresponding
+ managed bean is automatically created.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="property-name"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "property-name" element represents the JavaBeans
+ property name under which the corresponding value may
+ be stored.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="property-class"
+ type="javaee:java-typeType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "property-class" element represents the Java type
+ of the value associated with this property name.
+ If not specified, it can be inferred from existing
+ classes; however, this element should be specified
+ if the configuration file is going to be the source
+ for generating the corresponding classes.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:choice>
+ <xsd:element name="map-entries"
+ type="javaee:faces-config-map-entriesType"/>
+ <xsd:element name="null-value"
+ type="javaee:faces-config-null-valueType">
+ </xsd:element>
+ <xsd:element name="value"
+ type="javaee:faces-config-valueType"/>
+ <xsd:element name="list-entries"
+ type="javaee:faces-config-list-entriesType"/>
+ </xsd:choice>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-map-entryType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "map-entry" element reprsents a single key-entry pair
+ that will be added to the computed value of a managed
+ property of type java.util.Map.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="key"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "key" element is the String representation of a
+ map key that will be stored in a managed property of
+ type java.util.Map.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:choice>
+ <xsd:element name="null-value"
+ type="javaee:faces-config-null-valueType"/>
+ <xsd:element name="value"
+ type="javaee:faces-config-valueType"/>
+ </xsd:choice>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-map-entriesType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "map-entries' element represents a set of key-entry pairs
+ that will be added to the computed value of a managed property
+ of type java.util.Map. In addition, the Java class types
+ of the key and entry values may be optionally declared.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="key-class"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "key-class" element defines the Java type to which
+ each "key" element in a set of "map-entry" elements
+ will be converted to. If omitted, "java.lang.String"
+ is assumed.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="value-class"
+ type="javaee:faces-config-value-classType"
+ minOccurs="0"/>
+ <xsd:element name="map-entry"
+ type="javaee:faces-config-map-entryType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-navigation-caseType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "navigation-case" element describes a particular
+ combination of conditions that must match for this case to
+ be executed, and the view id of the component tree that
+ should be selected next.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="from-action"
+ type="javaee:faces-config-from-actionType"
+ minOccurs="0">
+ </xsd:element>
+ <xsd:element name="from-outcome"
+ type="javaee:string" minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "from-outcome" element contains a logical outcome
+ string returned by the execution of an application
+ action method selected via an "actionRef" property
+ (or a literal value specified by an "action" property)
+ of a UICommand component. If specified, this rule
+ will be relevant only if the outcome value matches
+ this element's value. If not specified, this rule
+ will be relevant no matter what the outcome value was.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="to-view-id"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "to-view-id" element contains the view identifier
+ of the next view that should be displayed if this
+ navigation rule is matched.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element
+ name="redirect"
+ type="javaee:faces-config-redirectType" minOccurs="0"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-navigation-ruleType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "navigation-rule" element represents an individual
+ decision rule that will be utilized by the default
+ NavigationHandler implementation to make decisions on
+ what view should be displayed next, based on the
+ view id being processed.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="from-view-id"
+ type="javaee:faces-config-from-view-idType"
+ minOccurs="0"/>
+ <xsd:element name="navigation-case"
+ type="javaee:faces-config-navigation-caseType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element
+ name="navigation-rule-extension"
+ type="javaee:faces-config-navigation-rule-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name = "faces-config-navigation-rule-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for navigation-rule. It may contain
+ implementation specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-null-valueType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "null-value" element indicates that the managed
+ property in which we are nested will be explicitly
+ set to null if our managed bean is automatically
+ created. This is different from omitting the managed
+ property element entirely, which will cause no
+ property setter to be called for this property.
+
+ The "null-value" element can only be used when the
+ associated "property-class" identifies a Java class,
+ not a Java primitive.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-propertyType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "property" element represents a JavaBean property of the
+ Java class represented by our parent element.
+
+ Property names must be unique within the scope of the Java
+ class that is represented by the parent element, and must
+ correspond to property names that will be recognized when
+ performing introspection against that class via
+ java.beans.Introspector.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="property-name"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "property-name" element represents the JavaBeans
+ property name under which the corresponding value
+ may be stored.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="property-class"
+ type="javaee:java-typeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "property-class" element represents the Java type
+ of the value associated with this property name.
+ If not specified, it can be inferred from existing
+ classes; however, this element should be specified if
+ the configuration file is going to be the source for
+ generating the corresponding classes.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="default-value"
+ type="javaee:faces-config-default-valueType"
+ minOccurs="0"/>
+ <xsd:element name="suggested-value"
+ type="javaee:faces-config-suggested-valueType"
+ minOccurs="0"/>
+ <xsd:element name="property-extension"
+ type="javaee:faces-config-property-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-property-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for property. It may contain
+ implementation specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-redirectType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "redirect" element indicates that navigation to the
+ specified "to-view-id" should be accomplished by
+ performing an HTTP redirect rather than the usual
+ ViewHandler mechanisms.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-referenced-beanType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "referenced-bean" element represents at design time the
+ promise that a Java object of the specified type will exist at
+ runtime in some scope, under the specified key. This can be
+ used by design time tools to construct user interface dialogs
+ based on the properties of the specified class. The presence
+ or absence of a referenced bean element has no impact on the
+ JavaServer Faces runtime environment inside a web application.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="referenced-bean-name"
+ type="javaee:java-identifierType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "referenced-bean-name" element represents the
+ attribute name under which the corresponding
+ referenced bean may be assumed to be stored, in one
+ of 'request', 'session', or 'application' scopes.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="referenced-bean-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "referenced-bean-class" element represents the
+ fully qualified class name of the Java class
+ (either abstract or concrete) or Java interface
+ implemented by the corresponding referenced bean.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-render-kitType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "render-kit" element represents a concrete RenderKit
+ implementation that should be registered under the specified
+ render-kit-id. If no render-kit-id is specified, the
+ identifier of the default RenderKit
+ (RenderKitFactory.DEFAULT_RENDER_KIT) is assumed.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="render-kit-id"
+ type="javaee:string"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "render-kit-id" element represents an identifier
+ for the RenderKit represented by the parent
+ "render-kit" element.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="render-kit-class"
+ type="javaee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "render-kit-class" element represents the fully
+ qualified class name of a concrete RenderKit
+ implementation class.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="renderer"
+ type="javaee:faces-config-rendererType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="render-kit-extension"
+ type="javaee:faces-config-render-kit-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-rendererType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "renderer" element represents a concrete Renderer
+ implementation class that should be registered under the
+ specified component family and renderer type identifiers,
+ in the RenderKit associated with the parent "render-kit"
+ element. Combinations of component family and
+ renderer type must be unique within the RenderKit
+ associated with the parent "render-kit" element.
+
+ Nested "attribute" elements identify generic component
+ attributes that are recognized by this renderer.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="component-family"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "component-family" element represents the
+ component family for which the Renderer represented
+ by the parent "renderer" element will be used.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="renderer-type"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "renderer-type" element represents a renderer type
+ identifier for the Renderer represented by the parent
+ "renderer" element.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="renderer-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "renderer-class" element represents the fully
+ qualified class name of a concrete Renderer
+ implementation class.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="facet"
+ type="javaee:faces-config-facetType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="attribute"
+ type="javaee:faces-config-attributeType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="renderer-extension"
+ type="javaee:faces-config-renderer-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-renderer-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for renderer. It may contain implementation
+ specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-render-kit-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for render-kit. It may contain
+ implementation specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-suggested-valueType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "suggested-value" contains the value for the property or
+ attribute in which this element resides. This value is
+ advisory only and is intended for tools to use when
+ populating pallettes.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:string"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-supported-localeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "supported-locale" element allows authors to declare
+ which locales are supported in this application instance.
+
+ It must be specified as :language:[_:country:[_:variant:]]
+ without the colons, for example "ja_JP_SJIS". The
+ separators between the segments may be '-' or '_'.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:extension base="javaee:faces-config-localeType">
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:extension>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-validatorType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "validator" element represents a concrete Validator
+ implementation class that should be registered under the
+ specified validator identifier. Validator identifiers must
+ be unique within the entire web application.
+
+ Nested "attribute" elements identify generic attributes that
+ may be configured on the corresponding UIComponent in order
+ to affect the operation of the Validator. Nested "property"
+ elements identify JavaBeans properties of the Validator
+ implementation class that may be configured to affect the
+ operation of the Validator. "attribute" and "property"
+ elements are intended to allow component developers to
+ more completely describe their components to tools and users.
+ These elements have no required runtime semantics.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="javaee:descriptionGroup"/>
+ <xsd:element name="validator-id"
+ type="javaee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "validator-id" element represents the identifier
+ under which the corresponding Validator class should
+ be registered.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="validator-class"
+ type="javaee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "validator-class" element represents the fully
+ qualified class name of a concrete Validator
+ implementation class.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="attribute"
+ type="javaee:faces-config-attributeType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Nested "attribute" elements identify generic
+ attributes that may be configured on the
+ corresponding UIComponent in order to affect the
+ operation of the Validator. This attribute is
+ primarily for design-time tools and is not
+ specified to have any meaning at runtime.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="property"
+ type="javaee:faces-config-propertyType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Nested "property" elements identify JavaBeans
+ properties of the Validator implementation class
+ that may be configured to affect the operation of
+ the Validator. This attribute is primarily for
+ design-time tools and is not specified to have
+ any meaning at runtime.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="validator-extension"
+ type="javaee:faces-config-validator-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name = "faces-config-validator-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Extension element for validator. It may contain
+ implementation specific content.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:any namespace="##any"
+ processContents="lax"
+ minOccurs="0"
+ maxOccurs="unbounded" />
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="faces-config-valueType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "value" element is the String representation of
+ a literal value to which a scalar managed property
+ will be set, or a value binding expression ("#{...}")
+ that will be used to calculate the required value.
+ It will be converted as specified for the actual
+ property type.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:union
+ memberTypes="javaee:faces-config-el-expressionType xsd:string"/>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-value-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "value-class" element defines the Java type to which each
+ "value" element's value will be converted to, prior to adding
+ it to the "list-entries" list for a managed property that is
+ a java.util.List, or a "map-entries" map for a managed
+ property that is a java.util.Map.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:simpleContent>
+ <xsd:restriction base="javaee:fully-qualified-classType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:complexType name="faces-config-list-entriesType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The "list-entries" element represents a set of initialization
+ elements for a managed property that is a java.util.List or an
+ array. In the former case, the "value-class" element can
+ optionally be used to declare the Java type to which each
+ value should be converted before adding it to the Collection.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="value-class"
+ type="javaee:faces-config-value-classType"
+ minOccurs="0"/>
+ <xsd:choice minOccurs="0" maxOccurs="unbounded">
+ <xsd:element name="null-value"
+ type="javaee:faces-config-null-valueType"/>
+ <xsd:element name="value"
+ type="javaee:faces-config-valueType"/>
+ </xsd:choice>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+ <!-- **************************************************** -->
+
+ <xsd:simpleType name="faces-config-versionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type contains the recognized versions of
+ faces-config supported.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:restriction base="xsd:token">
+ <xsd:enumeration value="1.2"/>
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <!-- **************************************************** -->
+
+</xsd:schema>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-jsptaglibrary_2_0.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-jsptaglibrary_2_0.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/web-jsptaglibrary_2_0.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1031 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema
+ targetNamespace="http://java.sun.com/xml/ns/j2ee"
+ xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ xmlns:xml="http://www.w3.org/XML/1998/namespace"
+ elementFormDefault="qualified"
+ attributeFormDefault="unqualified"
+ version="2.0">
+
+ <xsd:annotation>
+ <xsd:documentation>
+ @(#)web-jsptaglibrary_2_0.xsds 1.33 03/18/03
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Copyright 2002 Sun Microsystems, Inc., 901 San Antonio
+ Road, Palo Alto, California 94303, U.S.A. All rights
+ reserved.
+
+ Sun Microsystems, Inc. has intellectual property rights
+ relating to technology described in this document. In
+ particular, and without limitation, these intellectual
+ property rights may include one or more of the U.S. patents
+ listed at http://www.sun.com/patents and one or more
+ additional patents or pending patent applications in the
+ U.S. and other countries.
+
+ This document and the technology which it describes are
+ distributed under licenses restricting their use, copying,
+ distribution, and decompilation. No part of this document
+ may be reproduced in any form by any means without prior
+ written authorization of Sun and its licensors, if any.
+
+ Third-party software, including font technology, is
+ copyrighted and licensed from Sun suppliers.
+
+ Sun, Sun Microsystems, the Sun logo, Solaris, Java, J2EE,
+ JavaServer Pages, Enterprise JavaBeans and the Java Coffee
+ Cup logo are trademarks or registered trademarks of Sun
+ Microsystems, Inc. in the U.S. and other countries.
+
+ Federal Acquisitions: Commercial Software - Government Users
+ Subject to Standard License Terms and Conditions.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:annotation>
+ <xsd:documentation>
+ <![CDATA[
+
+ This is the XML Schema for the JSP Taglibrary
+ descriptor. All Taglibrary descriptors must
+ indicate the tag library schema by using the Taglibrary
+ namespace:
+
+ http://java.sun.com/xml/ns/j2ee
+
+ and by indicating the version of the schema by
+ using the version element as shown below:
+
+ <taglib xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="..."
+ version="2.0">
+ ...
+ </taglib>
+
+ The instance documents may indicate the published
+ version of the schema using xsi:schemaLocation attribute
+ for J2EE namespace with the following location:
+
+ http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd
+
+ ]]>
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:include schemaLocation="j2ee_1_4.xsd"/>
+
+
+<!-- **************************************************** -->
+
+
+ <xsd:element name="taglib" type="j2ee:taglibType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The taglib tag is the document root.
+ The definition of taglib is provided
+ by the taglibType.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:unique name="tag-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The taglib element contains, among other things, tag and
+ tag-file elements.
+ The name subelements of these elements must each be unique.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:tag|j2ee:tag-file"/>
+ <xsd:field xpath="j2ee:name"/>
+ </xsd:unique>
+
+ <xsd:unique name="function-name-uniqueness">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The taglib element contains function elements.
+ The name subelements of these elements must each be unique.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:selector xpath="j2ee:function"/>
+ <xsd:field xpath="j2ee:name"/>
+ </xsd:unique>
+
+ </xsd:element>
+
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="body-contentType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Provides a hint as to the content of the body of this tag.
+ Primarily intended for use by page composition tools.
+
+ There are currently four values specified:
+
+ tagdependent The body of the tag is interpreted by the tag
+ implementation itself, and is most likely
+ in a different "language", e.g embedded SQL
+ statements.
+
+ JSP The body of the tag contains nested JSP
+ syntax.
+
+ empty The body must be empty
+
+ scriptless The body accepts only template text, EL
+ Expressions, and JSP action elements. No
+ scripting elements are allowed.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="tagdependent"/>
+ <xsd:enumeration value="JSP"/>
+ <xsd:enumeration value="empty"/>
+ <xsd:enumeration value="scriptless"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="extensibleType" abstract="true">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The extensibleType is an abstract base type that is used to
+ define the type of extension-elements. Instance documents
+ must substitute a known type to define the extension by
+ using xsi:type attribute to define the actual type of
+ extension-elements.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="functionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The function element is used to provide information on each
+ function in the tag library that is to be exposed to the EL.
+
+ The function element may have several subelements defining:
+
+ description Optional tag-specific information
+
+ display-name A short name that is intended to be
+ displayed by tools
+
+ icon Optional icon element that can be used
+ by tools
+
+ name A unique name for this function
+
+ function-class Provides the name of the Java class that
+ implements the function
+
+ function-signature Provides the signature, as in the Java
+ Language Specification, of the Java
+ method that is to be used to implement
+ the function.
+
+ example Optional informal description of an
+ example of a use of this function
+
+ function-extension Zero or more extensions that provide extra
+ information about this function, for tool
+ consumption
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="name"
+ type="j2ee:tld-canonical-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ A unique name for this function.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="function-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Provides the fully-qualified class name of the Java
+ class containing the static method that implements
+ the function.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="function-signature"
+ type="j2ee:string">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Provides the signature, of the static Java method that is
+ to be used to implement the function. The syntax of the
+ function-signature element is as follows:
+
+ FunctionSignature ::= ReturnType S MethodName S?
+ '(' S? Parameters? S? ')'
+
+ ReturnType ::= Type
+
+ MethodName ::= Identifier
+
+ Parameters ::= Parameter
+ | ( Parameter S? ',' S? Parameters )
+
+ Parameter ::= Type
+
+ Where:
+
+ * Type is a basic type or a fully qualified Java class name
+ (including package name), as per the 'Type' production
+ in the Java Language Specification, Second Edition,
+ Chapter 18.
+
+ * Identifier is a Java identifier, as per the 'Identifier'
+ production in the Java Language Specification, Second
+ Edition, Chapter 18.
+
+ Example:
+
+ java.lang.String nickName( java.lang.String, int )
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="example"
+ type="j2ee:xsdStringType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The example element contains an informal description
+ of an example of the use of this function.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="function-extension"
+ type="j2ee:tld-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Function extensions are for tool use only and must not affect
+ the behavior of a container.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="listenerType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines an event listener object to be instantiated and
+ registered automatically.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="listener-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The listener-class element declares a class in the
+ application that must be registered as a web
+ application listener bean. See the Servlet
+ specification for details.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="tagFileType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines an action in this tag library that is implemented
+ as a .tag file.
+
+ The tag-file element has two required subelements:
+
+ description Optional tag-specific information
+
+ display-name A short name that is intended to be
+ displayed by tools
+
+ icon Optional icon element that can be used
+ by tools
+
+ name The unique action name
+
+ path Where to find the .tag file implementing this
+ action, relative to the root of the web
+ application or the root of the JAR file for a
+ tag library packaged in a JAR. This must
+ begin with /WEB-INF/tags if the .tag file
+ resides in the WAR, or /META-INF/tags if the
+ .tag file resides in a JAR.
+
+ example Optional informal description of an
+ example of a use of this tag
+
+ tag-extension Zero or more extensions that provide extra
+ information about this tag, for tool
+ consumption
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="name"
+ type="j2ee:tld-canonical-nameType"/>
+ <xsd:element name="path"
+ type="j2ee:pathType"/>
+ <xsd:element name="example"
+ type="j2ee:xsdStringType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The example element contains an informal description
+ of an example of the use of a tag.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="tag-extension"
+ type="j2ee:tld-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Tag extensions are for tool use only and must not affect
+ the behavior of a container.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="tagType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The tag defines a unique tag in this tag library. It has one
+ attribute, id.
+
+ The tag element may have several subelements defining:
+
+ description Optional tag-specific information
+
+ display-name A short name that is intended to be
+ displayed by tools
+
+ icon Optional icon element that can be used
+ by tools
+
+ name The unique action name
+
+ tag-class The tag handler class implementing
+ javax.servlet.jsp.tagext.JspTag
+
+ tei-class An optional subclass of
+ javax.servlet.jsp.tagext.TagExtraInfo
+
+ body-content The body content type
+
+ variable Optional scripting variable information
+
+ attribute All attributes of this action that are
+ evaluated prior to invocation.
+
+ dynamic-attributes Whether this tag supports additional
+ attributes with dynamic names. If
+ true, the tag-class must implement the
+ javax.servlet.jsp.tagext.DynamicAttributes
+ interface. Defaults to false.
+
+ example Optional informal description of an
+ example of a use of this tag
+
+ tag-extension Zero or more extensions that provide extra
+ information about this tag, for tool
+ consumption
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="name"
+ type="j2ee:tld-canonical-nameType"/>
+ <xsd:element name="tag-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the subclass of javax.serlvet.jsp.tagext.JspTag
+ that implements the request time semantics for
+ this tag. (required)
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="tei-class"
+ type="j2ee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the subclass of javax.servlet.jsp.tagext.TagExtraInfo
+ for this tag. (optional)
+
+ If this is not given, the class is not consulted at
+ translation time.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="body-content"
+ type="j2ee:body-contentType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The default (if not defined) is JSP
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="variable"
+ type="j2ee:variableType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="attribute"
+ type="j2ee:tld-attributeType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="dynamic-attributes"
+ type="j2ee:generic-booleanType"
+ minOccurs="0"/>
+ <xsd:element name="example"
+ type="j2ee:xsdStringType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The example element contains an informal description
+ of an example of the use of a tag.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="tag-extension"
+ type="j2ee:tld-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Tag extensions are for tool use only and must not affect
+ the behavior of a container.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="taglibType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The taglib tag is the document root, it defines:
+
+ description a simple string describing the "use" of this taglib,
+ should be user discernable
+
+ display-name the display-name element contains a
+ short name that is intended to be displayed
+ by tools
+
+ icon optional icon that can be used by tools
+
+ tlib-version the version of the tag library implementation
+
+ short-name a simple default short name that could be
+ used by a JSP authoring tool to create
+ names with a mnemonic value; for example,
+ the it may be used as the prefered prefix
+ value in taglib directives
+
+ uri a uri uniquely identifying this taglib
+
+ validator optional TagLibraryValidator information
+
+ listener optional event listener specification
+
+ tag tags in this tag library
+
+ tag-file tag files in this tag library
+
+ function zero or more EL functions defined in this
+ tag library
+
+ taglib-extension zero or more extensions that provide extra
+ information about this taglib, for tool
+ consumption
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:group ref="j2ee:descriptionGroup"/>
+ <xsd:element name="tlib-version"
+ type="j2ee:dewey-versionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Describes this version (number) of the taglibrary.
+ It is described as a dewey decimal.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+
+ <xsd:element name="short-name"
+ type="j2ee:tld-canonical-nameType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines a simple default name that could be used by
+ a JSP authoring tool to create names with a
+ mnemonicvalue; for example, it may be used as the
+ preferred prefix value in taglib directives. Do
+ not use white space, and do not start with digits
+ or underscore.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="uri"
+ type="j2ee:xsdAnyURIType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines a public URI that uniquely identifies this
+ version of the taglibrary. Leave it empty if it
+ does not apply.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="validator"
+ type="j2ee:validatorType"
+ minOccurs="0">
+ </xsd:element>
+ <xsd:element name="listener"
+ type="j2ee:listenerType"
+ minOccurs="0" maxOccurs="unbounded">
+ </xsd:element>
+ <xsd:element name="tag"
+ type="j2ee:tagType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="tag-file"
+ type="j2ee:tagFileType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="function"
+ type="j2ee:functionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="taglib-extension"
+ type="j2ee:tld-extensionType"
+ minOccurs="0"
+ maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Taglib extensions are for tool use only and must not affect
+ the behavior of a container.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="version"
+ type="j2ee:dewey-versionType"
+ fixed="2.0"
+ use="required">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Describes the JSP version (number) this taglibrary
+ requires in order to function (dewey decimal)
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:attribute>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="tld-attributeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The attribute element defines an attribute for the nesting
+ tag. The attributre element may have several subelements
+ defining:
+
+ description a description of the attribute
+
+ name the name of the attribute
+
+ required whether the attribute is required or
+ optional
+
+ rtexprvalue whether the attribute is a runtime attribute
+
+ type the type of the attributes
+
+ fragment whether this attribute is a fragment
+
+ </xsd:documentation>
+ </xsd:annotation>
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:element name="name"
+ type="j2ee:java-identifierType"/>
+ <xsd:element name="required"
+ type="j2ee:generic-booleanType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines if the nesting attribute is required or
+ optional.
+
+ If not present then the default is "false", i.e
+ the attribute is optional.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:choice>
+ <xsd:sequence>
+ <xsd:element name="rtexprvalue"
+ type="j2ee:generic-booleanType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines if the nesting attribute can have scriptlet
+ expressions as a value, i.e the value of the
+ attribute may be dynamically calculated at request
+ time, as opposed to a static value determined at
+ translation time.
+
+ If not present then the default is "false", i.e the
+ attribute has a static value
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+ <xsd:element name="type"
+ type="j2ee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the Java type of the attributes value. For
+ static values (those determined at translation time)
+ the type is always java.lang.String.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:element name="fragment"
+ type="j2ee:generic-booleanType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ "true" if this attribute is of type
+ javax.jsp.tagext.JspFragment, representing dynamic
+ content that can be re-evaluated as many times
+ as needed by the tag handler. If omitted or "false",
+ the default is still type="java.lang.String"
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:choice>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="tld-canonical-nameType">
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the canonical name of a tag or attribute being
+ defined.
+
+ The name must conform to the lexical rules for an NMTOKEN.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:xsdNMTOKENType"/>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="tld-extensionType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The tld-extensionType is used to indicate
+ extensions to a specific TLD element.
+
+ It is used by elements to designate an extension block
+ that is targeted to a specific extension designated by
+ a set of extension elements that are declared by a
+ namespace. The namespace identifies the extension to
+ the tool that processes the extension.
+
+ The type of the extension-element is abstract. Therefore,
+ a concrete type must be specified by the TLD using
+ xsi:type attribute for each extension-element.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="extension-element"
+ type="j2ee:extensibleType"
+ maxOccurs="unbounded"/>
+ </xsd:sequence>
+
+ <xsd:attribute name="namespace"
+ use="required"
+ type="xsd:anyURI"/>
+ <xsd:attribute name="id" type="xsd:ID"/>
+
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="validatorType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ A validator that can be used to validate
+ the conformance of a JSP page to using this tag library is
+ defined by a validatorType.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0"
+ maxOccurs="unbounded"/>
+ <xsd:element name="validator-class"
+ type="j2ee:fully-qualified-classType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Defines the TagLibraryValidator class that can be used
+ to validate the conformance of a JSP page to using this
+ tag library.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="init-param"
+ type="j2ee:param-valueType"
+ minOccurs="0" maxOccurs="unbounded">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The init-param element contains a name/value pair as an
+ initialization param.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="variable-scopeType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ This type defines scope of the scripting variable. See
+ TagExtraInfo for details. The allowed values are,
+ "NESTED", "AT_BEGIN" and "AT_END".
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:simpleContent>
+ <xsd:restriction base="j2ee:string">
+ <xsd:enumeration value="NESTED"/>
+ <xsd:enumeration value="AT_BEGIN"/>
+ <xsd:enumeration value="AT_END"/>
+ </xsd:restriction>
+ </xsd:simpleContent>
+ </xsd:complexType>
+
+<!-- **************************************************** -->
+
+ <xsd:complexType name="variableType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The variableType provides information on the scripting
+ variables defined by using this tag. It is a (translation
+ time) error for a tag that has one or more variable
+ subelements to have a TagExtraInfo class that returns a
+ non-null value from a call to getVariableInfo().
+
+ The subelements of variableType are of the form:
+
+ description Optional description of this
+ variable
+
+ name-given The variable name as a constant
+
+ name-from-attribute The name of an attribute whose
+ (translation time) value will
+ give the name of the
+ variable. One of name-given or
+ name-from-attribute is required.
+
+ variable-class Name of the class of the variable.
+ java.lang.String is default.
+
+ declare Whether the variable is declared
+ or not. True is the default.
+
+ scope The scope of the scripting varaible
+ defined. NESTED is default.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:sequence>
+ <xsd:element name="description"
+ type="j2ee:descriptionType"
+ minOccurs="0" maxOccurs="unbounded"/>
+ <xsd:choice>
+ <xsd:element name="name-given"
+ type="j2ee:java-identifierType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The name for the scripting variable.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+
+ <xsd:element name="name-from-attribute"
+ type="j2ee:java-identifierType">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The name of an attribute whose
+ (translation-time) value will give the name of
+ the variable.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:choice>
+ <xsd:element name="variable-class"
+ type="j2ee:fully-qualified-classType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The optional name of the class for the scripting
+ variable. The default is java.lang.String.
+
+ </xsd:documentation>
+ </xsd:annotation>
+
+ </xsd:element>
+
+ <xsd:element name="declare"
+ type="j2ee:generic-booleanType"
+ minOccurs="0">
+
+ <xsd:annotation>
+ <xsd:documentation>
+
+ Whether the scripting variable is to be defined
+ or not. See TagExtraInfo for details. This
+ element is optional and "true" is the default.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ <xsd:element name="scope"
+ type="j2ee:variable-scopeType"
+ minOccurs="0">
+ <xsd:annotation>
+ <xsd:documentation>
+
+ The element is optional and "NESTED" is the default.
+
+ </xsd:documentation>
+ </xsd:annotation>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="id" type="xsd:ID"/>
+ </xsd:complexType>
+
+</xsd:schema>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/xml.xsd
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/xml.xsd (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/schema/xml.xsd 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,86 @@
+<?xml version='1.0'?>
+<xs:schema targetNamespace="http://www.w3.org/XML/1998/namespace" xmlns:xs="http://www.w3.org/2001/XMLSchema" xml:lang="en">
+
+ <xs:annotation>
+ <xs:documentation> See http://www.w3.org/XML/1998/namespace.html and http://www.w3.org/TR/REC-xml for information about this namespace. This schema document describes the XML
+ namespace, in a form suitable for import by other schema documents. Note that local names in this namespace are intended to be defined only by the World Wide Web Consortium or its subgroups. The
+ following names are currently defined in this namespace and should not be used with conflicting semantics by any Working Group, specification, or document instance: base (as an attribute
+ name): denotes an attribute whose value provides a URI to be used as the base for interpreting any relative URIs in the scope of the element on which it appears; its value is inherited. This name is
+ reserved by virtue of its definition in the XML Base specification. id (as an attribute name): denotes an attribute whose value should be interpreted as if declared to be of type ID. The xml:id
+ specification is not yet a W3C Recommendation, but this attribute is included here to facilitate experimentation with the mechanisms it proposes. Note that it is _not_ included in the
+ specialAttrs attribute group. lang (as an attribute name): denotes an attribute whose value is a language code for the natural language of the content of any element; its value is inherited.
+ This name is reserved by virtue of its definition in the XML specification. space (as an attribute name): denotes an attribute whose value is a keyword indicating what whitespace processing
+ discipline is intended for the content of the element; its value is inherited. This name is reserved by virtue of its definition in the XML specification. Father (in any context at all): denotes
+ Jon Bosak, the chair of the original XML Working Group. This name is reserved by the following decision of the W3C XML Plenary and XML Coordination groups: In appreciation for his vision,
+ leadership and dedication the W3C XML Plenary on this 10th day of February, 2000 reserves for Jon Bosak in perpetuity the XML name xml:Father </xs:documentation>
+ </xs:annotation>
+
+ <xs:annotation>
+ <xs:documentation>This schema defines attributes and an attribute group suitable for use by schemas wishing to allow xml:base, xml:lang, xml:space or xml:id attributes on elements they
+ define. To enable this, such a schema must import this schema for the XML namespace, e.g. as follows:
+ <schema . . .> . . .
+ <import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> Subsequently, qualified reference to any of the attributes or
+ the group defined below will have the desired effect, e.g.
+
+ <type . . .> . . .
+ <attributeGroup ref="xml:specialAttrs"/> will define a type which will schema-validate an instance element with any of those attributes</xs:documentation>
+
+ </xs:annotation>
+
+ <xs:annotation>
+ <xs:documentation>In keeping with the XML Schema WG's standard versioning policy, this schema document will persist at http://www.w3.org/2005/08/xml.xsd. At the date of issue it can also be
+ found at http://www.w3.org/2001/xml.xsd. The schema document at that URI may however change in the future, in order to remain compatible with the latest version of XML Schema itself, or with
+ the XML namespace itself. In other words, if the XML Schema or XML namespaces change, the version of this document at http://www.w3.org/2001/xml.xsd will change accordingly; the version at
+ http://www.w3.org/2005/08/xml.xsd will not change. </xs:documentation>
+ </xs:annotation>
+
+ <xs:attribute name="lang">
+ <xs:annotation>
+ <xs:documentation>Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at
+ http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the
+ 'un-declaration' of xml:lang with the empty string.</xs:documentation>
+
+ </xs:annotation>
+ <xs:simpleType>
+ <xs:union memberTypes="xs:language">
+ <xs:simpleType>
+ <xs:restriction base="xs:string">
+ <xs:enumeration value=""/>
+ </xs:restriction>
+ </xs:simpleType>
+ </xs:union>
+
+ </xs:simpleType>
+ </xs:attribute>
+
+ <xs:attribute name="space">
+ <xs:simpleType>
+ <xs:restriction base="xs:NCName">
+ <xs:enumeration value="default"/>
+ <xs:enumeration value="preserve"/>
+ </xs:restriction>
+
+ </xs:simpleType>
+ </xs:attribute>
+
+ <xs:attribute name="base" type="xs:anyURI">
+ <xs:annotation>
+ <xs:documentation>See http://www.w3.org/TR/xmlbase/ for information about this attribute.</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+
+ <xs:attribute name="id" type="xs:ID">
+
+ <xs:annotation>
+ <xs:documentation>See http://www.w3.org/TR/xml-id/ for information about this attribute.</xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+
+ <xs:attributeGroup name="specialAttrs">
+ <xs:attribute ref="xml:base"/>
+ <xs:attribute ref="xml:lang"/>
+ <xs:attribute ref="xml:space"/>
+
+ </xs:attributeGroup>
+
+</xs:schema>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/tests/TESTS-TestSuites.txt
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/tests/TESTS-TestSuites.txt (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/docs/tests/TESTS-TestSuites.txt 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,44 @@
+
+
+JBoss daily test results
+
+SUMMARY
+
+Number of tests run: 4119
+
+--------------------------------------------
+
+Successful tests: 4119
+
+Errors: 0
+
+Failures: 0
+
+--------------------------------------------
+
+
+
+[time of test: 2007-05-11.22-14 GMT]
+[java.version: 1.5.0_11]
+[java.vendor: Sun Microsystems Inc.]
+[java.vm.version: 1.5.0_11-b03]
+[java.vm.name: Java HotSpot(TM) Server VM]
+[java.vm.info: mixed mode]
+[os.name: Linux]
+[os.arch: i386]
+[os.version: 2.6.9-55.ELsmp]
+
+Useful resources:
+
+- http://jboss.sourceforge.net/junit-results/32/2007-05-11.22-14 for
+the junit report of this test.
+
+
+NOTE: If there are any errors shown above - this mail is only highlighting
+them - it is NOT indicating that they are being looked at by anyone.
+
+It is assumed that whoever makes change(s) to jboss that
+break the test will be fixing the test or jboss, as appropriate!
+
+--------------------------------------------
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/jar-versions.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/jar-versions.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/jar-versions.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,162 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<jar-versions>
+ <jar name="activation.jar" specVersion="1.1" specVendor="Sun Microsystems, Inc." specTitle="JavaBeans(TM) Activation Framework Specification" implVersion="1.1" implVendor="Sun Microsystems, Inc." implTitle="Sun Java System Application Server" implVendorID="com.sun" implURL="http://www.jboss.org/" sealed="false" md5Digest="56f989e553b38d5c8076e86b2d6a6d04"/>
+ <jar name="antlr.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="f0af9a2a2d2ab3365e0ef1db6cf10ce3"/>
+ <jar name="applet.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="a6434aa8c2dc6fbfc6d83cf94140e7a2"/>
+ <jar name="autonumber-plugin.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="b785649e506eda1dc6c712bd05ccfa11"/>
+ <jar name="avalon-framework.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="608fe334d66cdccb044e29a9e79a6416"/>
+ <jar name="bcel.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="d27a150419b9ded5ce0eb1e529774c30"/>
+ <jar name="bindingservice-plugin.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="11aaac9331692a9e01d8d77efd34ed48"/>
+ <jar name="bsf.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="74ec5681dca78b9e8fe981faad8640b3"/>
+ <jar name="bsh-deployer.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="632b0216436acdfd48f8c7f20e184a6b"/>
+ <jar name="bsh.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="731a161a8f058ce4921a1bffaa056f56"/>
+ <jar name="cglib.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="fd82c80a216878e14a987c12a9571157"/>
+ <jar name="commons-codec.jar" specVersion="1.3" specVendor="Apache Software Foundation" specTitle="Jakarta Commons Codec" implVersion="1.3" implVendor="Apache Software Foundation" implTitle="org.apache.commons.codec" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="f7d1db6a08817c54201bc2031493e4d1"/>
+ <jar name="commons-collections.jar" specVersion="3.1" specVendor="Apache Software Foundation" specTitle="Commons Collections" implVersion="3.1" implVendor="Apache Software Foundation" implTitle="JBoss [Trinity]" implVendorID="" implURL="http://www.jboss.org/" sealed="false" md5Digest="6a88f6e1ae521fffe48ba25d1784f014"/>
+ <jar name="commons-httpclient.jar" specVersion="1.0" specVendor="Apache Software Foundation" specTitle="JBoss" implVersion="3.0.1" implVendor="Apache Software Foundation" implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="c2b07ce74ae09e2ea2d3af8abbfe3f5"/>
+ <jar name="commons-logging.jar" specVersion="1.0" specVendor="Apache Software Foundation" specTitle="Jakarta Commons Logging" implVersion="1.1.0.jboss" implVendor="Red Hat Middleware LLC" implTitle="Jakarta Commons Logging" implVendorID="jboss.org" implURL="http://www.jboss.org/" sealed="false" md5Digest="ea7f3553f01962f0a1343bc5452a7b09"/>
+ <jar name="concurrent.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="4042f9159713b8ea0a7111e63448373c"/>
+ <jar name="console-mgr-classes.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="54bbf5d238fb5f0ac06709c29d5e59cb"/>
+ <jar name="deployment-service.sar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="43e42c4b2ec7a85292d1d9d22b03b5c1"/>
+ <jar name="derby-plugin.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="606dc18054628797f2e8b13e624476e3"/>
+ <jar name="dom4j.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="d06edb890db8866f7557eabfa030dbf2"/>
+ <jar name="ejb-management.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="3378d61ec12ad9c3ccc61a376cdc3704"/>
+ <jar name="ejb3-persistence.jar" specVersion="3.0 Final Release" specVendor="Sun Microsystems, Inc." specTitle="EJB 3.0" implVersion="3.0 Final Release September 22 2006" implVendor="hibernate.org" implTitle="EJB" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="8102923333fd2360d044622a9c5d7f55"/>
+ <jar name="el-api.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="fac770308e04b940e65e3b827e5c9231"/>
+ <jar name="getopt.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="51585ef7b7403b46db5f9e796b448935"/>
+ <jar name="hibernate-annotations.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="7fa343c1ea935974c5ce3ed26fafa25a"/>
+ <jar name="hibernate-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="51bca7e5cea67978c05fa5f0bdb2a50f"/>
+ <jar name="hibernate-entitymanager.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="c9510437f2a32e7448590086392aabdf"/>
+ <jar name="hibernate3.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="3.2.3.ga" implVendor="hibernate.org" implTitle="Hibernate3" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="ddd4c58676264b2d3de94f9cba71e919"/>
+ <jar name="hsqldb-plugin.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="e1e502ebe724603da7435433f7c3d2d4"/>
+ <jar name="hsqldb.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="651b39be324b2a123e7dfdacd6f7ad1f"/>
+ <jar name="jacorb.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="6e0a587baa8cb1c570fdcd5c84962569"/>
+ <jar name="jasper-jdt.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="34db7d2cd34c143d0f6db1fe8140ee10"/>
+ <jar name="javassist.jar" specVersion="snapshot" specVendor="Shigeru Chiba, Tokyo Institute of Technology" specTitle="Javassist" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="c6266e704766f6932733c04145d4176"/>
+ <jar name="jaxb-api.jar" specVersion="2.0" specVendor="Sun Microsystems, Inc." specTitle="Java Architecture for XML Binding" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="e16252d50b9b06b35a818b9f3c3b795a"/>
+ <jar name="jaxb-impl.jar" specVersion="2.0" specVendor="Sun Microsystems, Inc." specTitle="Java Architecture for XML Binding" implVersion="2.0.3" implVendor="Sun Microsystems, Inc." implTitle="JAXB Reference Implementation " implVendorID="com.sun" implURL="http://www.jboss.org/" sealed="false" md5Digest="14802ca8da65b24ef19ca138b3ab0a46"/>
+ <jar name="jaxb-xjc.jar" specVersion="2.0" specVendor="Sun Microsystems, Inc." specTitle="Java Architecture for XML Binding" implVersion="2.0.3" implVendor="Sun Microsystems, Inc." implTitle="JAXB Reference Implementation " implVendorID="com.sun" implURL="http://www.jboss.org/" sealed="false" md5Digest="7c7482d72e06974dd5d9518fb0358abd"/>
+ <jar name="jaxen.jar" specVersion="4.2.0.GA" specVendor="Codehaus" specTitle="Universal Java XPath Engine" implVersion="1.1" implVendor="Codehaus" implTitle="org.jaxen" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="5540894b2c7d7c5cc11ba48ed1522a79"/>
+ <jar name="jboss-annotations-ejb3.jar" specVersion="JBoss EJB 3.0 AS 4.2.0 GA" specVendor="JBoss" specTitle="JBoss EJB 3.0" implVersion="JBoss EJB 3.0 AS 4.2.0 GA" implVendor="JBoss" implTitle="JBoss EJB 3.0" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.com/products/ejb3" sealed="false" md5Digest="6522d2603355b94100fa5913ef7b768c"/>
+ <jar name="jboss-aop-jdk50-client.jar" specVersion="jboss-aop-1.5.5.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss AOP Framework" implVersion="jboss-aop-1.5.5.GA" implVendor="JBoss.org" implTitle="JBoss AOP Framework" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="3d4d940d080b11a0d0a6c88f77a27183"/>
+ <jar name="jboss-aop-jdk50.jar" specVersion="jboss-aop-1.5.5.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss AOP Framework" implVersion="jboss-aop-1.5.5.GA" implVendor="JBoss.org" implTitle="JBoss AOP Framework" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="b1b323895d4dfde9b6cf49b4278de12b"/>
+ <jar name="jboss-aspect-jdk50-client.jar" specVersion="jboss-aspect-library-1.5" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss AOP Aspect Library" implVersion="jboss-aspect-library-1.5" implVendor="JBoss Inc." implTitle="JBoss AOP Aspect Library" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="714e807f00d6124a63d6aad054a3bdc4"/>
+ <jar name="jboss-aspect-library-jdk50.jar" specVersion="jboss-aspect-library-1.5" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss AOP Aspect Library" implVersion="jboss-aspect-library-1.5" implVendor="JBoss Inc." implTitle="JBoss AOP Aspect Library" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="2217e79f8256eccdfaf4f07022f86641"/>
+ <jar name="jboss-bean-deployer.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="a6ca618fd3e2405771d63be5a828c263"/>
+ <jar name="jboss-cache-jdk50.jar" specVersion="1.4.1.SP3" specVendor="JBoss Inc." specTitle="JBossCache" implVersion="1.4.1.SP3" implVendor="JBoss Inc." implTitle="JBossCache" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="34f0e8dedc902a97fdd674f1f5f4b25a"/>
+ <jar name="jboss-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="115572c126bf87e3b1aa2d0e27ddbcd5"/>
+ <jar name="jboss-common-client.jar" specVersion="1.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss Common" implVersion="1.2.0.GA (build: SVNTag=JBossCommon_1_2_0_GA date=200703301431)" implVendor="JBoss.org" implTitle="JBoss Common [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="f498040f7b3ffba4251ca640e0118b9e"/>
+ <jar name="jboss-common-jdbc-wrapper.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="e8facde2bd9239987eaabdfe5c0400f9"/>
+ <jar name="jboss-common.jar" specVersion="1.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss Common" implVersion="1.2.0.GA (build: SVNTag=JBossCommon_1_2_0_GA date=200703301431)" implVendor="JBoss.org" implTitle="JBoss Common [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="69554b158e33ebc52f4821dc2f104412"/>
+ <jar name="jboss-container.jar" specVersion="5.0.0" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="5.0.0alpha (build: CVSTag=HEAD date=200601252203)" implVendor="JBoss.org" implTitle="JBoss [TheOne]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="b467ca8b231893b2500c8568a65d4514"/>
+ <jar name="jboss-dependency.jar" specVersion="5.0.0" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="5.0.0alpha (build: CVSTag=HEAD date=200601252203)" implVendor="JBoss.org" implTitle="JBoss [TheOne]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="8f511acb5031f51dcbb44be3432a6457"/>
+ <jar name="jboss-deployment.jar" specVersion="1.1" specVendor="Sun Microsystems, Inc." specTitle="J2EE Deployment API" implVersion="1.1-DEV" implVendor="JBoss Inc." implTitle="JBoss JSR-88 Deployment API" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="4abf60a9ea5d3335f348bdf9b896dcec"/>
+ <jar name="jboss-ejb3-client.jar" specVersion="JBoss EJB 3.0 AS 4.2.0 GA" specVendor="JBoss" specTitle="JBoss EJB 3.0" implVersion="JBoss EJB 3.0 AS 4.2.0 GA" implVendor="JBoss" implTitle="JBoss EJB 3.0" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.com/products/ejb3" sealed="false" md5Digest="ff4e2772063bdd1be3cbd152950fcef8"/>
+ <jar name="jboss-ejb3.jar" specVersion="JBoss EJB 3.0 AS 4.2.0 GA" specVendor="JBoss" specTitle="JBoss EJB 3.0" implVersion="JBoss EJB 3.0 AS 4.2.0 GA" implVendor="JBoss" implTitle="JBoss EJB 3.0" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.com/products/ejb3" sealed="false" md5Digest="d41e2e46d197b9f916ce3197da208108"/>
+ <jar name="jboss-ejb3x.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="881245fea2c6314f44371ba62bf641b1"/>
+ <jar name="jboss-faces.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="1c0d3306d1c392e122a112527b59e9a2"/>
+ <jar name="jboss-ha-local-jdbc.rar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="7a27ce8881feec9ee40649554cbcb4e8"/>
+ <jar name="jboss-ha-xa-jdbc.rar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="24054fcb8e575201cac12997f87f62e6"/>
+ <jar name="jboss-hibernate.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="435952c0260ac09f0fa826ba74030771"/>
+ <jar name="jboss-iiop-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="6803ae9ebd544231fade40070090e756"/>
+ <jar name="jboss-iiop.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="d0e81c13cb73b5f7b6304d3ce1d63f4f"/>
+ <jar name="jboss-j2ee.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="f5c049ed59c17c6bc61a2a6db4617642"/>
+ <jar name="jboss-jaxrpc.jar" specVersion="jbossws-1.2" specVendor="JBoss (http://www.jboss.org)" specTitle="JBossWS" implVersion="jbossws-1.2.1.GA (build=200704151756)" implVendor="JBoss Inc." implTitle="JBoss Web Services (JBossWS)" implVendorID="http://www.jboss.org" implURL="http://www.jboss.org/products/jbossws" sealed="false" md5Digest="48c0587afcd91449f17ffc2e21c37574"/>
+ <jar name="jboss-jaxws.jar" specVersion="jbossws-1.2" specVendor="JBoss (http://www.jboss.org)" specTitle="JBossWS" implVersion="jbossws-1.2.1.GA (build=200704151756)" implVendor="JBoss Inc." implTitle="JBoss Web Services (JBossWS)" implVendorID="http://www.jboss.org" implURL="http://www.jboss.org/products/jbossws" sealed="false" md5Digest="7593cfd1b50b85462dee0a191c370931"/>
+ <jar name="jboss-jca.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="886e08263bf3d06d373a9efdcd01f45b"/>
+ <jar name="jboss-jmx.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="54a342a0f5de32a94c256d07cbfade56"/>
+ <jar name="jboss-jsr77-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="7010f7a67442e2a9894e64d3af5ba773"/>
+ <jar name="jboss-jsr77.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="518a25357b6e97ff7a1b836d808aac4e"/>
+ <jar name="jboss-jsr88.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="a895aafc2443bde30b97dd008310f9ff"/>
+ <jar name="jboss-local-jdbc.rar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="27455b3d929eb0a51ba83c6c4441e244"/>
+ <jar name="jboss-management.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="1472ffb6a19ee9ea5a6e5aa6c726c557"/>
+ <jar name="jboss-microcontainer.jar" specVersion="5.0.0" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="5.0.0alpha (build: CVSTag=HEAD date=200601252203)" implVendor="JBoss.org" implTitle="JBoss [TheOne]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="d19f63e833349860c0eea0483e953c9e"/>
+ <jar name="jboss-minimal.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="5e00647840e935014c04b74d50c8a08a"/>
+ <jar name="jboss-monitoring.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="9e7504e558afe1df6be5498a61f9bb4f"/>
+ <jar name="jboss-remoting-int.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="7c6fe6898c0d633d463d040e63151fd0"/>
+ <jar name="jboss-remoting.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="ff4f11c2aebf65b86933dedb554c650b"/>
+ <jar name="jboss-saaj.jar" specVersion="jbossws-1.2" specVendor="JBoss (http://www.jboss.org)" specTitle="JBossWS" implVersion="jbossws-1.2.1.GA (build=200704151756)" implVendor="JBoss Inc." implTitle="JBoss Web Services (JBossWS)" implVendorID="http://www.jboss.org" implURL="http://www.jboss.org/products/jbossws" sealed="false" md5Digest="eae9b940d88ac30555762cf77d03d909"/>
+ <jar name="jboss-serialization.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="cd89b1182ef893d3366975e49be8b4ff"/>
+ <jar name="jboss-srp-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="eb221f2383424d32a28a629ad4673400"/>
+ <jar name="jboss-srp.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="b6b4cc7afd664c16ea0a2d61d8b29759"/>
+ <jar name="jboss-system-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="c7c1a81d088650fe05c61887bd6c9496"/>
+ <jar name="jboss-system.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="355256d8d7ef4ab5b359bd09e80289b6"/>
+ <jar name="jboss-transaction-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="136ffac107027f7e5f388677a8a6e071"/>
+ <jar name="jboss-transaction.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="5608c6be63fdf7695f6fc764435e23bb"/>
+ <jar name="jboss-vfs.jar" specVersion="1.0.0.GA" specVendor="JBoss, A division of Red Hat" specTitle="JBoss VFS" implVersion="1.0.0.GA" implVendor="JBoss, A division of Red Hat" implTitle="JBoss VFS" implVendorID="jboss" implURL="http://www.jboss.org/" sealed="false" md5Digest="1b9e6aed550b4492773eccb5b9b62b45"/>
+ <jar name="jboss-web-cluster.aop" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="6f06de6c627dbb34ba778b2d540b170f"/>
+ <jar name="jboss-xa-jdbc.rar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="ef93b690c419b64be7d3e7fe060cc29f"/>
+ <jar name="jboss-xml-binding.jar" specVersion="4.2.0.GA" specVendor="JBoss Inc." specTitle="JBoss XML Binding" implVersion="1.0.0.GA" implVendor="JBoss Inc." implTitle="jbossxb" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="9e04c05a536502fd9b0ba4dfee28bc75"/>
+ <jar name="jboss.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="f955757257850b2f5ae7383669fa2843"/>
+ <jar name="jbossall-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="3723ce20938322ccea6260200e01fa2a"/>
+ <jar name="jbosscx-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="a95e9cda793bba8de18ce282e9a2962c"/>
+ <jar name="jbossha-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="3f97a8b15e7b9ea44a0e363d824813e7"/>
+ <jar name="jbossha.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="9b4932c1fb0ecfe2f5c17525f7bade1e"/>
+ <jar name="jbossjmx-ant.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="65a3bd1aa6eddec45a318e4b24ac659"/>
+ <jar name="jbossjta-integration.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="a6576e5cb6cb5bf43c393500719f7aa5"/>
+ <jar name="jbossjta.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="595377e50dc5b20ed7bbcb5755d98fe"/>
+ <jar name="jbossmq-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="d145eadac6f97d35a94122ef8e1dbd8f"/>
+ <jar name="jbossmq.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="2a652da8df9784c5c18d0e4506948844"/>
+ <jar name="jbosssx-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="d6f8ed680f5b1624c72c75fba0166fe7"/>
+ <jar name="jbosssx.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="39893e387939ace3efbc12327b80bb95"/>
+ <jar name="jbossts-common.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="bb42f8349ff6a2a88ab06780cae5eaa1"/>
+ <jar name="jbossweb-extras.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="db0f8807dd533a3a120a76d4b0c26d97"/>
+ <jar name="jbossweb-service.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="537a6830847b82670ce77067893c8ebc"/>
+ <jar name="jbossweb.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="548b4dc32f8a6aecdf617b9b53f1aa6c"/>
+ <jar name="jbossws-client.jar" specVersion="jbossws-1.2" specVendor="JBoss (http://www.jboss.org)" specTitle="JBossWS" implVersion="jbossws-1.2.1.GA (build=200704151756)" implVendor="JBoss Inc." implTitle="JBoss Web Services (JBossWS)" implVendorID="http://www.jboss.org" implURL="http://www.jboss.org/products/jbossws" sealed="false" md5Digest="e6f3adfbc9f92a71a74e80b6aba43e90"/>
+ <jar name="jbossws-context.war" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="c09d1ba4006cf80718dace4159540ea7"/>
+ <jar name="jbossws-core.jar" specVersion="jbossws-1.2" specVendor="JBoss (http://www.jboss.org)" specTitle="JBossWS" implVersion="jbossws-1.2.1.GA (build=200704151756)" implVendor="JBoss Inc." implTitle="JBoss Web Services (JBossWS)" implVendorID="http://www.jboss.org" implURL="http://www.jboss.org/products/jbossws" sealed="false" md5Digest="e5748abb48044cf11aaec44cb95881eb"/>
+ <jar name="jbossws-integration.jar" specVersion="jbossws-1.2" specVendor="JBoss (http://www.jboss.org)" specTitle="JBossWS" implVersion="jbossws-1.2.1.GA (build=200704151756)" implVendor="JBoss Inc." implTitle="JBoss Web Services (JBossWS)" implVendorID="http://www.jboss.org" implURL="http://www.jboss.org/products/jbossws" sealed="false" md5Digest="53bdb1761e9ea3067729ce3ba7b6fa01"/>
+ <jar name="jbossws-jboss42-integration.jar" specVersion="jbossws-1.2" specVendor="JBoss (http://www.jboss.org)" specTitle="JBossWS" implVersion="jbossws-1.2.1.GA (build=200704151756)" implVendor="JBoss Inc." implTitle="JBoss Web Services (JBossWS)" implVendorID="http://www.jboss.org" implURL="http://www.jboss.org/products/jbossws" sealed="false" md5Digest="632f1955a61b29646eb86bc6f52a9f3c"/>
+ <jar name="jbossws-wsconsume-impl.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="jbossws-wsconsume-impl 2.0.0-02/20/2007 17:08:52(jason)" implVendor="jboss" implTitle="jbossws-wsconsume-impl" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="6ecd6cac78a7faf52b4284b141732f32"/>
+ <jar name="jcommon.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="3e9f0bd4f3c4302dcf00d557596032dd"/>
+ <jar name="jfreechart.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="352fbe71d736a50403e29415033536ab"/>
+ <jar name="jgroups.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="2.4.1-SP3" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="ff554d5680ff9e1a64613d825332fb24"/>
+ <jar name="jms-ra.rar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="c9e254ed96db86d32a4a6ae98b90304e"/>
+ <jar name="jmx-adaptor-plugin.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="b3005030067cf53652bc02cce941633e"/>
+ <jar name="jmx-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="d698e17ed914acc18c1e5630ec0082af"/>
+ <jar name="jmx-invoker-adaptor-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="c1b0ea848c924fc5ae61f831ef78e59d"/>
+ <jar name="jnp-client.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="2c8cdc1aef5dfab67d9363573b4087d7"/>
+ <jar name="jnpserver.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="4f23bd6c8e186bb51a43172eb98238e1"/>
+ <jar name="joesnmp.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="0.3.4" implVendor="joeSNMP" implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://sourceforge.net/projects/joesnmp" sealed="false" md5Digest="8cb6a46375f6d7b75c36ca54695fdee1"/>
+ <jar name="jpl-pattern.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="95d213c97907b8189d1807a4fccc3a14"/>
+ <jar name="jpl-util.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="528fa3293d8669a414353710c47e12a5"/>
+ <jar name="jsf-api.jar" specVersion="1.2MR1" specVendor="JBoss (http://www.jboss.org/)" specTitle="JavaServer Faces" implVersion="1.2_04-b10-p01" implVendor="Sun Microsystems, Inc." implTitle="Sun Microsystems JavaServer Faces Implementation" implVendorID="com.sun" implURL="http://www.jboss.org/" sealed="false" md5Digest="6c9b4b459e62753610fda27a4d6d8245"/>
+ <jar name="jsf-impl.jar" specVersion="1.2MR1" specVendor="JBoss (http://www.jboss.org/)" specTitle="JavaServer Faces" implVersion="1.2_04-b10-p01" implVendor="Sun Microsystems, Inc." implTitle="Sun Microsystems JavaServer Faces Implementation" implVendorID="com.sun" implURL="http://www.jboss.org/" sealed="false" md5Digest="90562bbdd9fd53c28e7c0bc65e1226f4"/>
+ <jar name="jsp-api.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="df1def9608cdd7f7f85e3ad90a0cfee7"/>
+ <jar name="jstl.jar" specVersion="1.2" specVendor="Sun Microsystems, Inc." specTitle="JavaServer Pages(TM) Standard Tag Library" implVersion="1.2" implVendor="Sun Microsystems, Inc." implTitle="Sun Java System Application Server" implVendorID="org.apache" implURL="http://www.jboss.org/" sealed="false" md5Digest="54e42a01b3e97b72f69522a359a30b35"/>
+ <jar name="juddi-saaj.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="545cef33708f36eda67e3fddf75e465d"/>
+ <jar name="juddi-service.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="6f007c7198d010ad8930f38bb75520fd"/>
+ <jar name="juddi.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="bee0cc9c7f96a595319e6507b64fba2a"/>
+ <jar name="log4j-boot.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="52796918f3240a16f3a1e7ee613083aa"/>
+ <jar name="log4j-snmp-appender.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="3f4ed622f05dca69c01e63ccad720b5b"/>
+ <jar name="log4j.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="af4d79a5b38a3ccd996680e3f339bb7f"/>
+ <jar name="logging-monitor.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="5615d2162350a0a0d54072bb38ceee04"/>
+ <jar name="logkit.jar" specVersion="1.0" specVendor="Apache Software Foundation" specTitle="JBoss" implVersion="1.2" implVendor="Apache Software Foundation" implTitle="JBoss [Trinity]" implVendorID="ASF" implURL="http://www.jboss.org/" sealed="false" md5Digest="5a24213d2934f8272d3f4fe450a4fb76"/>
+ <jar name="mail-plugin.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="b799484dfd095d7a22bf22ab7d7cfaeb"/>
+ <jar name="mail.jar" specVersion="1.4" specVendor="Sun Microsystems, Inc." specTitle="JavaMail(TM) API Design Specification" implVersion="1.4" implVendor="Sun Microsystems, Inc." implTitle="JavaMail(TM) API Reference Implementation" implVendorID="com.sun" implURL="http://www.jboss.org/" sealed="false" md5Digest="bc2ebb7dad20a412b96a25770beeca73"/>
+ <jar name="netboot.war" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="f182a2c20fcbac33799cd6304a5d7a20"/>
+ <jar name="otherimages.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="3f6a1e8c40b304802006558609a13f97"/>
+ <jar name="policy.jar" specVersion="4.2.0.GA" specVendor="Apache Software Foundation" specTitle="" implVersion="1.0" implVendor="Apache Software Foundation" implTitle="org.apache.ws.policy" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="24543cb1f4c1d43b6594115b918022bb"/>
+ <jar name="properties-plugin.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="c7815f636efb14d2f570fc612cf13e19"/>
+ <jar name="quartz-ra.rar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="2ad92c9e138afa3e481422d5d9952685"/>
+ <jar name="quartz.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="1.5.2" implVendor="OpenSymphony" implTitle="Quartz Enterprise Job Scheduler" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="4f6a2cb57f0fdb6a35f5072f1c501b3e"/>
+ <jar name="run.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="726b982d07d7927dda31128eb54a78f1"/>
+ <jar name="scheduler-plugin-example.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="45a86e76658899c3cdf1ed2e78c1bb5d"/>
+ <jar name="scheduler-plugin.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="f5b1f088882867e0484b9461fd5bb087"/>
+ <jar name="scout.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="2fbcfb055585affb89876c1033470f1f"/>
+ <jar name="serializer.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="4aed7dd9e29835658e3b981c9ce4ae5b"/>
+ <jar name="servlet-api.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="3ce9fea0fcf0b82d482311e9d317f84d"/>
+ <jar name="shutdown.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="26eba8bf1d84bc94e5ff865bf87eef7d"/>
+ <jar name="snmp-adaptor.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="d28a4de1b4bf932339388a1a81ea7406"/>
+ <jar name="stax-api.jar" specVersion="1.0" specVendor="JCP-173" specTitle="StAX" implVersion="1.0" implVendor="JCP" implTitle="StAX 1.0 API" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="6e80befe3555090005aba99c18b116f5"/>
+ <jar name="trove.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="f9d5484c75246ff4600f71eff10b570e"/>
+ <jar name="twiddle.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="462d475f5a1d083383129e3f1993e760"/>
+ <jar name="wsdl4j.jar" specVersion="1.2" specVendor="IBM (Java Community Process)" specTitle="JWSDL" implVersion="1.6.2" implVendor="IBM" implTitle="WSDL4J" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="fbb92aeda252f8f0279d79b0fdf99fdd"/>
+ <jar name="wstx.jar" specVersion="1.0" specVendor="http://jcp.org/en/jsr/detail?id=173" specTitle="StAX 1.0 API" implVersion="3.1.1" implVendor="woodstox.codehaus.org" implTitle="WoodSToX XML-processor" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="ccc1e96e7e60f244d1b0bbd3bc060fbc"/>
+ <jar name="xalan.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="60ae939fcac01c9c0e2c1dafbc07e954"/>
+ <jar name="xercesImpl.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="cc0536a7306f8ee5f8562c5c8b1b1719"/>
+ <jar name="xmlentitymgr.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="3881cd3bf95e70e321c4cbff1951916d"/>
+ <jar name="xmlsec.jar" specVersion="4.2.0.GA" specVendor="JBoss (http://www.jboss.org/)" specTitle="JBoss" implVersion="4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)" implVendor="JBoss Inc." implTitle="JBoss [Trinity]" implVendorID="http://www.jboss.org/" implURL="http://www.jboss.org/" sealed="false" md5Digest="8f1e9d3059fedcc4960e6cdb0827c4d9"/>
+</jar-versions>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lgpl.html
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lgpl.html (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lgpl.html 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,350 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head>
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+ <title>Appendix A. GNU Lesser General Public License</title><meta name="generator" content="DocBook XSL Stylesheets V1.69.1a"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="appendix" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="lgpl"></a>GNU Lesser General Public License</h1></div><div><p class="releaseinfo">This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.</p></div><div><p class="copyright">Copyright © 1991, 1999 Free Software Foundation, Inc.</p></div><div><div class="legalnotice"><a name="gpl-legalnotice"></a><p>
+ </p><div class="address"><p>Free Software Foundation, Inc.<br>
+ <span class="street">51 Franklin Street, Fifth Floor</span>,<br>
+ <span class="city">Boston</span>,<br>
+ <span class="state">MA</span><br>
+ <span class="postcode">02110-1301</span><br>
+ <span class="country">USA</span><br>
+ </p></div><p>
+ </p><p>Everyone is permitted to copy and distribute verbatim
+ copies of this license document, but changing it is not
+ allowed.</p></div></div><div><p class="pubdate">Version 2.1, February 1999</p></div></div></div>
+<div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lgpl-1"></a>Preamble</h2></div></div></div><p>The licenses for most software are designed to take away your
+ freedom to share and change it. By contrast, the GNU General Public
+ Licenses are intended to guarantee your freedom to share and change
+ free software--to make sure the software is free for all its users.</p><p>This license, the Lesser General Public License, applies to some
+ specially designated software packages--typically libraries--of the
+ Free Software Foundation and other authors who decide to use it. You
+ can use it too, but we suggest you first think carefully about whether
+ this license or the ordinary General Public License is the better
+ strategy to use in any particular case, based on the explanations below.</p><p>When we speak of free software, we are referring to freedom of use,
+ not price. Our General Public Licenses are designed to make sure that
+ you have the freedom to distribute copies of free software (and charge
+ for this service if you wish); that you receive source code or can get
+ it if you want it; that you can change the software and use pieces of
+ it in new free programs; and that you are informed that you can do
+ these things.</p><p>To protect your rights, we need to make restrictions that forbid
+ distributors to deny you these rights or to ask you to surrender these
+ rights. These restrictions translate to certain responsibilities for
+ you if you distribute copies of the library or if you modify it.</p><p>For example, if you distribute copies of the library, whether gratis
+ or for a fee, you must give the recipients all the rights that we gave
+ you. You must make sure that they, too, receive or can get the source
+ code. If you link other code with the library, you must provide
+ complete object files to the recipients, so that they can relink them
+ with the library after making changes to the library and recompiling
+ it. And you must show them these terms so they know their rights.</p><p>We protect your rights with a two-step method:
+ </p><div class="orderedlist"><ol type="1"><li><p>we copyright the library, and</p></li><li><p>we offer you this license, which gives you legal
+ permission to copy, distribute and/or modify the library.</p></li></ol></div><p>
+ </p><p>To protect each distributor, we want to make it very clear that
+ there is no warranty for the free library. Also, if the library is
+ modified by someone else and passed on, the recipients should know
+ that what they have is not the original version, so that the original
+ author's reputation will not be affected by problems that might be
+ introduced by others.</p><p>Finally, software patents pose a constant threat to the existence of
+ any free program. We wish to make sure that a company cannot
+ effectively restrict the users of a free program by obtaining a
+ restrictive license from a patent holder. Therefore, we insist that
+ any patent license obtained for a version of the library must be
+ consistent with the full freedom of use specified in this license.</p><p>Most GNU software, including some libraries, is covered by the
+ ordinary GNU General Public License. This license, the GNU Lesser
+ General Public License, applies to certain designated libraries, and
+ is quite different from the ordinary General Public License. We use
+ this license for certain libraries in order to permit linking those
+ libraries into non-free programs.</p><p>When a program is linked with a library, whether statically or using
+ a shared library, the combination of the two is legally speaking a
+ combined work, a derivative of the original library. The ordinary
+ General Public License therefore permits such linking only if the
+ entire combination fits its criteria of freedom. The Lesser General
+ Public License permits more lax criteria for linking other code with
+ the library.</p><p>We call this license the <span class="emphasis"><em>Lesser</em></span> General Public License because it
+ does Less to protect the user's freedom than the ordinary General
+ Public License. It also provides other free software developers Less
+ of an advantage over competing non-free programs. These disadvantages
+ are the reason we use the ordinary General Public License for many
+ libraries. However, the Lesser license provides advantages in certain
+ special circumstances.</p><p>For example, on rare occasions, there may be a special need to
+ encourage the widest possible use of a certain library, so that it becomes
+ a de-facto standard. To achieve this, non-free programs must be
+ allowed to use the library. A more frequent case is that a free
+ library does the same job as widely used non-free libraries. In this
+ case, there is little to gain by limiting the free library to free
+ software only, so we use the Lesser General Public License.</p><p>In other cases, permission to use a particular library in non-free
+ programs enables a greater number of people to use a large body of
+ free software. For example, permission to use the GNU C Library in
+ non-free programs enables many more people to use the whole GNU
+ operating system, as well as its variant, the GNU/Linux operating
+ system.</p><p>Although the Lesser General Public License is Less protective of the
+ users' freedom, it does ensure that the user of a program that is
+ linked with the Library has the freedom and the wherewithal to run
+ that program using a modified version of the Library.</p><p>The precise terms and conditions for copying, distribution and
+ modification follow. Pay close attention to the difference between a
+ “<span class="quote">work based on the library</span>” and a “<span class="quote">work that uses the library</span>”. The
+ former contains code derived from the library, whereas the latter must
+ be combined with the library in order to run.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lgpl-2"></a>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-0"></a>Section 0</h3></div></div></div><p>This License Agreement applies to any software library or other
+ program which contains a notice placed by the copyright holder or
+ other authorized party saying it may be distributed under the terms of
+ this Lesser General Public License (also called “<span class="quote">this License</span>”).
+ Each licensee is addressed as “<span class="quote">you</span>”.</p><p>A “<span class="quote">library</span>” means a collection of software functions and/or data
+ prepared so as to be conveniently linked with application programs
+ (which use some of those functions and data) to form executables.</p><p>The “<span class="quote">Library</span>”, below, refers to any such software library or work
+ which has been distributed under these terms. A “<span class="quote">work based on the
+ Library</span>” means either the Library or any derivative work under
+ copyright law: that is to say, a work containing the Library or a
+ portion of it, either verbatim or with modifications and/or translated
+ straightforwardly into another language. (Hereinafter, translation is
+ included without limitation in the term “<span class="quote">modification</span>”.)</p><p>“<span class="quote">Source code</span>” for a work means the preferred form of the work for
+ making modifications to it. For a library, complete source code means
+ all the source code for all modules it contains, plus any associated
+ interface definition files, plus the scripts used to control compilation
+ and installation of the library.</p><p>Activities other than copying, distribution and modification are not
+ covered by this License; they are outside its scope. The act of
+ running a program using the Library is not restricted, and output from
+ such a program is covered only if its contents constitute a work based
+ on the Library (independent of the use of the Library in a tool for
+ writing it). Whether that is true depends on what the Library does
+ and what the program that uses the Library does.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-1"></a>Section 1</h3></div></div></div><p>You may copy and distribute verbatim copies of the Library's
+ complete source code as you receive it, in any medium, provided that
+ you conspicuously and appropriately publish on each copy an
+ appropriate copyright notice and disclaimer of warranty; keep intact
+ all the notices that refer to this License and to the absence of any
+ warranty; and distribute a copy of this License along with the
+ Library.</p><p>You may charge a fee for the physical act of transferring a copy,
+ and you may at your option offer warranty protection in exchange for a
+ fee.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-2"></a>Section 2</h3></div></div></div><p>You may modify your copy or copies of the Library or any portion
+ of it, thus forming a work based on the Library, and copy and
+ distribute such modifications or work under the terms of <a href="#lgpl-2-1" title="Section 1">Section 1</a>
+ above, provided that you also meet all of these conditions:
+ </p><div class="orderedlist"><ol type="a"><li><p>The modified work must itself be a software library.</p></li><li><p>You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.</p></li><li><p>You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.</p></li><li><p><a name="lgpl-2-2-d"></a>If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.</p><p>(For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, <a href="#lgpl-2-2-d">Subsection 2d</a> requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)</p></li></ol></div><p>
+ </p><p>These requirements apply to the modified work as a whole. If
+ identifiable sections of that work are not derived from the Library,
+ and can be reasonably considered independent and separate works in
+ themselves, then this License, and its terms, do not apply to those
+ sections when you distribute them as separate works. But when you
+ distribute the same sections as part of a whole which is a work based
+ on the Library, the distribution of the whole must be on the terms of
+ this License, whose permissions for other licensees extend to the
+ entire whole, and thus to each and every part regardless of who wrote
+ it.</p><p>Thus, it is not the intent of this section to claim rights or contest
+ your rights to work written entirely by you; rather, the intent is to
+ exercise the right to control the distribution of derivative or
+ collective works based on the Library.</p><p>In addition, mere aggregation of another work not based on the Library
+ with the Library (or with a work based on the Library) on a volume of
+ a storage or distribution medium does not bring the other work under
+ the scope of this License.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-3"></a>Section 3</h3></div></div></div><p>You may opt to apply the terms of the ordinary GNU General Public
+ License instead of this License to a given copy of the Library. To do
+ this, you must alter all the notices that refer to this License, so
+ that they refer to the ordinary GNU General Public License, version 2,
+ instead of to this License. (If a newer version than version 2 of the
+ ordinary GNU General Public License has appeared, then you can specify
+ that version instead if you wish.) Do not make any other change in
+ these notices.</p><p>Once this change is made in a given copy, it is irreversible for
+ that copy, so the ordinary GNU General Public License applies to all
+ subsequent copies and derivative works made from that copy.</p><p>This option is useful when you wish to copy part of the code of
+ the Library into a program that is not a library.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-4"></a>Section 4</h3></div></div></div><p>You may copy and distribute the Library (or a portion or
+ derivative of it, under <a href="#lgpl-2-2" title="Section 2">Section 2</a>) in object code or executable form
+ under the terms of <a href="#lgpl-2-1" title="Section 1">Sections 1</a> and <a href="#lgpl-2-2" title="Section 2">2</a> above provided that you accompany
+ it with the complete corresponding machine-readable source code, which
+ must be distributed under the terms of <a href="#lgpl-2-1" title="Section 1">Sections 1</a> and <a href="#lgpl-2-2" title="Section 2">2</a> above on a
+ medium customarily used for software interchange.</p><p>If distribution of object code is made by offering access to copy
+ from a designated place, then offering equivalent access to copy the
+ source code from the same place satisfies the requirement to
+ distribute the source code, even though third parties are not
+ compelled to copy the source along with the object code.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-5"></a>Section 5</h3></div></div></div><p>A program that contains no derivative of any portion of the
+ Library, but is designed to work with the Library by being compiled or
+ linked with it, is called a “<span class="quote">work that uses the Library</span>”. Such a
+ work, in isolation, is not a derivative work of the Library, and
+ therefore falls outside the scope of this License.</p><p>However, linking a “<span class="quote">work that uses the Library</span>” with the Library
+ creates an executable that is a derivative of the Library (because it
+ contains portions of the Library), rather than a “<span class="quote">work that uses the
+ library</span>”. The executable is therefore covered by this License.
+ <a href="#lgpl-2-6" title="Section 6">Section 6</a> states terms for distribution of such executables.</p><p>When a “<span class="quote">work that uses the Library</span>” uses material from a header file
+ that is part of the Library, the object code for the work may be a
+ derivative work of the Library even though the source code is not.
+ Whether this is true is especially significant if the work can be
+ linked without the Library, or if the work is itself a library. The
+ threshold for this to be true is not precisely defined by law.</p><p>If such an object file uses only numerical parameters, data
+ structure layouts and accessors, and small macros and small inline
+ functions (ten lines or less in length), then the use of the object
+ file is unrestricted, regardless of whether it is legally a derivative
+ work. (Executables containing this object code plus portions of the
+ Library will still fall under <a href="#lgpl-2-6" title="Section 6">Section 6</a>.)</p><p>Otherwise, if the work is a derivative of the Library, you may
+ distribute the object code for the work under the terms of <a href="#lgpl-2-6" title="Section 6">Section 6</a>.
+ Any executables containing that work also fall under <a href="#lgpl-2-6" title="Section 6">Section 6</a>,
+ whether or not they are linked directly with the Library itself.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-6"></a>Section 6</h3></div></div></div><p>As an exception to the Sections above, you may also combine or
+ link a “<span class="quote">work that uses the Library</span>” with the Library to produce a
+ work containing portions of the Library, and distribute that work
+ under terms of your choice, provided that the terms permit
+ modification of the work for the customer's own use and reverse
+ engineering for debugging such modifications.</p><p>You must give prominent notice with each copy of the work that the
+ Library is used in it and that the Library and its use are covered by
+ this License. You must supply a copy of this License. If the work
+ during execution displays copyright notices, you must include the
+ copyright notice for the Library among them, as well as a reference
+ directing the user to the copy of this License. Also, you must do one
+ of these things:
+ </p><div class="orderedlist"><ol type="a"><li><p><a name="lgpl-2-6-a"></a>Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ <a href="#lgpl-2-1" title="Section 1">Sections 1</a> and <a href="#lgpl-2-2" title="Section 2">2</a> above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable “<span class="quote">work that
+ uses the Library</span>”, as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)</p></li><li><p>Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (1) uses at run time a
+ copy of the library already present on the user's computer system,
+ rather than copying library functions into the executable, and (2)
+ will operate properly with a modified version of the library, if
+ the user installs one, as long as the modified version is
+ interface-compatible with the version that the work was made with.</p></li><li><p>Accompany the work with a written offer, valid for at
+ least three years, to give the same user the materials
+ specified in <a href="#lgpl-2-6-a">Subsection 6a</a>, above, for a charge no more
+ than the cost of performing this distribution.</p></li><li><p>If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.</p></li><li><p>Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.</p></li></ol></div><p>
+ </p><p>For an executable, the required form of the “<span class="quote">work that uses the
+ Library</span>” must include any data and utility programs needed for
+ reproducing the executable from it. However, as a special exception,
+ the materials to be distributed need not include anything that is
+ normally distributed (in either source or binary form) with the major
+ components (compiler, kernel, and so on) of the operating system on
+ which the executable runs, unless that component itself accompanies
+ the executable.</p><p>It may happen that this requirement contradicts the license
+ restrictions of other proprietary libraries that do not normally
+ accompany the operating system. Such a contradiction means you cannot
+ use both them and the Library together in an executable that you
+ distribute.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-7"></a>Section 7</h3></div></div></div><p>You may place library facilities that are a work based on the
+ Library side-by-side in a single library together with other library
+ facilities not covered by this License, and distribute such a combined
+ library, provided that the separate distribution of the work based on
+ the Library and of the other library facilities is otherwise
+ permitted, and provided that you do these two things:
+ </p><div class="orderedlist"><ol type="a"><li><p>Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.</p></li><li><p>Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.</p></li></ol></div><p>
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-8"></a>Section 8</h3></div></div></div><p>You may not copy, modify, sublicense, link with, or distribute
+ the Library except as expressly provided under this License. Any
+ attempt otherwise to copy, modify, sublicense, link with, or
+ distribute the Library is void, and will automatically terminate your
+ rights under this License. However, parties who have received copies,
+ or rights, from you under this License will not have their licenses
+ terminated so long as such parties remain in full compliance.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-9"></a>Section 9</h3></div></div></div><p>You are not required to accept this License, since you have not
+ signed it. However, nothing else grants you permission to modify or
+ distribute the Library or its derivative works. These actions are
+ prohibited by law if you do not accept this License. Therefore, by
+ modifying or distributing the Library (or any work based on the
+ Library), you indicate your acceptance of this License to do so, and
+ all its terms and conditions for copying, distributing or modifying
+ the Library or works based on it.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-10"></a>Section 10</h3></div></div></div><p>Each time you redistribute the Library (or any work based on the
+ Library), the recipient automatically receives a license from the
+ original licensor to copy, distribute, link with or modify the Library
+ subject to these terms and conditions. You may not impose any further
+ restrictions on the recipients' exercise of the rights granted herein.
+ You are not responsible for enforcing compliance by third parties with
+ this License.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-11"></a>Section 11</h3></div></div></div><p>If, as a consequence of a court judgment or allegation of patent
+ infringement or for any other reason (not limited to patent issues),
+ conditions are imposed on you (whether by court order, agreement or
+ otherwise) that contradict the conditions of this License, they do not
+ excuse you from the conditions of this License. If you cannot
+ distribute so as to satisfy simultaneously your obligations under this
+ License and any other pertinent obligations, then as a consequence you
+ may not distribute the Library at all. For example, if a patent
+ license would not permit royalty-free redistribution of the Library by
+ all those who receive copies directly or indirectly through you, then
+ the only way you could satisfy both it and this License would be to
+ refrain entirely from distribution of the Library.</p><p>If any portion of this section is held invalid or unenforceable under any
+ particular circumstance, the balance of the section is intended to apply,
+ and the section as a whole is intended to apply in other circumstances.</p><p>It is not the purpose of this section to induce you to infringe any
+ patents or other property right claims or to contest validity of any
+ such claims; this section has the sole purpose of protecting the
+ integrity of the free software distribution system which is
+ implemented by public license practices. Many people have made
+ generous contributions to the wide range of software distributed
+ through that system in reliance on consistent application of that
+ system; it is up to the author/donor to decide if he or she is willing
+ to distribute software through any other system and a licensee cannot
+ impose that choice.</p><p>This section is intended to make thoroughly clear what is believed to
+ be a consequence of the rest of this License.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-12"></a>Section 12</h3></div></div></div><p>If the distribution and/or use of the Library is restricted in
+ certain countries either by patents or by copyrighted interfaces, the
+ original copyright holder who places the Library under this License may add
+ an explicit geographical distribution limitation excluding those countries,
+ so that distribution is permitted only in or among countries not thus
+ excluded. In such case, this License incorporates the limitation as if
+ written in the body of this License.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-13"></a>Section 13</h3></div></div></div><p>The Free Software Foundation may publish revised and/or new
+ versions of the Lesser General Public License from time to time.
+ Such new versions will be similar in spirit to the present version,
+ but may differ in detail to address new problems or concerns.</p><p>Each version is given a distinguishing version number. If the Library
+ specifies a version number of this License which applies to it and
+ “<span class="quote">any later version</span>”, you have the option of following the terms and
+ conditions either of that version or of any later version published by
+ the Free Software Foundation. If the Library does not specify a
+ license version number, you may choose any version ever published by
+ the Free Software Foundation.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-14"></a>Section 14</h3></div></div></div><p>If you wish to incorporate parts of the Library into other free
+ programs whose distribution conditions are incompatible with these,
+ write to the author to ask for permission. For software which is
+ copyrighted by the Free Software Foundation, write to the Free
+ Software Foundation; we sometimes make exceptions for this. Our
+ decision will be guided by the two goals of preserving the free status
+ of all derivatives of our free software and of promoting the sharing
+ and reuse of software generally.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-15"></a>NO WARRANTY Section 15</h3></div></div></div><p>BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+ WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+ EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+ OTHER PARTIES PROVIDE THE LIBRARY “<span class="quote">AS IS</span>” WITHOUT WARRANTY OF ANY
+ KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+ LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+ THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="lgpl-2-16"></a>Section 16</h3></div></div></div><p>IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+ WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+ AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+ FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+ CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+ LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+ RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+ FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+ SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+ DAMAGES.</p><p>END OF TERMS AND CONDITIONS</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="lgpl-3"></a>How to Apply These Terms to Your New Libraries</h2></div></div></div><p>If you develop a new library, and you want it to be of the greatest
+ possible use to the public, we recommend making it free software that
+ everyone can redistribute and change. You can do so by permitting
+ redistribution under these terms (or, alternatively, under the terms of the
+ ordinary General Public License).</p><p>To apply these terms, attach the following notices to the library. It is
+ safest to attach them to the start of each source file to most effectively
+ convey the exclusion of warranty; and each file should have at least the
+ “<span class="quote">copyright</span>” line and a pointer to where the full notice is found.</p><p><one line to give the library's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author></p><p>This library is free software; you can redistribute it and/or
+ modify it under the terms of the GNU Lesser General Public
+ License as published by the Free Software Foundation; either
+ version 2.1 of the License, or (at your option) any later version.</p><p>This library is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ Lesser General Public License for more details.</p><p>You should have received a copy of the GNU Lesser General Public
+ License along with this library; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA</p><p>Also add information on how to contact you by electronic and paper mail.</p><p>You should also get your employer (if you work as a programmer) or your
+ school, if any, to sign a “<span class="quote">copyright disclaimer</span>” for the library, if
+ necessary. Here is a sample; alter the names:</p><p>Yoyodyne, Inc., hereby disclaims all copyright interest in the
+ library `Frob' (a library for tweaking knobs) written by James Random Hacker.</p><p><signature of Ty Coon>, 1 April 1990
+ Ty Coon, President of Vice</p><p>That's all there is to it!</p></div></div></body></html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/commons-codec.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/commons-codec.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/commons-httpclient.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/commons-httpclient.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/commons-logging.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/commons-logging.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/concurrent.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/concurrent.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/endorsed/serializer.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/endorsed/serializer.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/endorsed/xalan.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/endorsed/xalan.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/endorsed/xercesImpl.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/endorsed/xercesImpl.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/getopt.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/getopt.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-common.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-common.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-jmx.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-jmx.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-system.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-system.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-xml-binding.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/jboss-xml-binding.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/log4j-boot.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/lib/log4j-boot.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/readme.html
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/readme.html (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/readme.html 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,604 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<!-- $Id: readme.html,v 1.1.2.36 2006/05/13 15:42:36 dimitris Exp $ -->
+<html>
+
+<head>
+ <meta content="text/html" http-equiv="content-type"/>
+ <meta content="JBoss Inc." name="author"/>
+ <title>JBoss 4.2.0.GA Readme</title>
+</head>
+
+<body>
+<a href="http://www.jboss.com"><img
+ src='http://www.jboss.org/themes/jbosstheme/img/logo.gif'
+ alt="JBoss Inc."></a>
+
+<h1>JBoss AS 4.2.0.GA Release Notes</h1>
+
+<p>This is the final release of JBoss Application Server v4.2.0.
+<a href="http://labs.jboss.com/jbossas/">JBoss AS</a> 4.2 is a stepping
+stone from JBoss 4.0 to JBoss 5.0. It combines a lot (but not all) of the
+exciting new features of JBoss 5, but based on the stable 4.x MicroKernel
+architecture.</p>
+<p>JBoss 4.2 is also used as the basis for the<a href="http://www.redhat.com/jboss/platforms/application/">
+JBoss Enterprise Application Platform.</a> The <i>platform</i> bundles<a href="http://labs.jboss.com/jbossas/">
+JBoss AS </a>4.2 and <a href="http://labs.jboss.com/jbossseam/">JBoss Seam</a>
+and it constitutes the software for which commercial support is offered by
+JBoss/Red Hat. Please read
+<a href="http://blogs.jboss.com/blog/slabourey/2007/04/24/New+Development,+Distribution+and+Support+Model+for+JBoss.txt">
+Sacha's blog</a> if you are interested to learn more about the new development,
+distribution and support model for JBoss.</p>
+<p>For
+ information on the APIs that make up Java EE 1.4, see <a href='http://java.sun.com/j2ee/1.4/docs/index.html'>
+ Java EE v1.4 Documentation</a>.
+ For a comprehensive tutorial on Java EE 1.4, see <a href='http://java.sun.com/j2ee/1.4/docs/tutorial-update2/doc/index.html'>
+ The Java EE™ 1.4 Tutorial</a>.
+ A jboss-4.2.x getting started guide that is based on contents from the tutorial
+ can be found in <a href='http://labs.jboss.com/portal/jbossas/docs'>JBoss Application Server Documentation Library</a></p>
+<p>
+ <em>Note: The 4.2.x release of the JBoss Application Server provides support for certain JavaEE5
+ features, such as EJB3, but it is not Java EE5 certified.</em></p>
+
+<h2>Overview</h2>
+<ul>
+ <li><a href="#Highlights">Highlights</a></li>
+ <li><a href="#Compatibility">Known Compatibility Issues</a></li>
+ <li><a href="#Configuration">Known Configuration Issues</a></li>
+ <li><a href="#Library Updates">JBoss/Thirdparty Library Updates</a></li>
+ <li><a href="#Details">Detailed Release Notes</a></li>
+ <li><a href="#Documentation">Additional Docs and Help</a></li>
+ <li><a href="#Licenses">Licenses</a></li>
+ <li><a href="#About">About JBoss</a></li>
+</ul>
+
+<h2><a name="Highlights">Highlights</a></h2>
+<ul>
+ <li>JDK5 is *required* to run JBossAS 4.2.x. The decision was based on the
+ fact that JDK1.4 is phased out and the reality that a lot of people like
+ Java Annotations support and want to combine EJB3 and
+ <a href="http://www.jboss.com/products/seam">JBoss Seam</a> components with
+ JBossAS. JDK6 is not formally supported yet, although you may be able to
+ start the server with it. JDK6 support will come with JBossAS 5.x.</li>
+ <li><a href="http://labs.jboss.org/portal/jbossejb3">JBoss EJB3</a> is now
+ deployed *by default* in JBossAS 4.2.x The fact that we base on JDK5 makes
+ our life easier in this regard, meaning we don't have to maintain jdk5 code
+ retro-weaved for jdk1.4 runtimes, and we can include by default components
+ that require jdk5 to run.</li>
+ <li><a href="http://www.jboss.com/products/jbossweb">JBoss Web</a> v2.x is
+ the web container in JBossAS 4.2, an implementation based on Apache Tomcat
+ that includes the Apache Portable Runtime (APR) and Tomcat native
+ technologies to achieve scalability and performance characteristics that
+ match and exceed the Apache Http server. In the absence of the native
+ libraries in the JBoss classpath, JBoss Web falls back to the standard non-native connector mode.
+ The native libraries need to be downloaded and installed separately.</li>
+ <li><a href="http://www.jboss.com/products/transactions">JBoss Transactions</a>
+ v4.2 is the default transaction manager for JBossAS 4.2. JBoss Transactions
+ is founded on industry proven technology and 18 year history as a leader in
+ distributed transactions, and is one of the most interoperable
+ implementations available. The JTA version of JBoss Transactions included
+ with the server provides for fully recoverable transactions. For distributed
+ transaction support the JTS version of JBoss Transactions will need to be
+ used. Furthermore, it is always possible to fall back to the legacy JBossTM
+ fast in-memory transaction manager implementation, if necessary.</li>
+ <li><a href="http://labs.jboss.com/portal/jbossws">JBossWS</a> is the web
+ services stack for JBoss 4.2 providing Java EE compatible web services. It
+ has been upgraded to v1.2.1.GA</li>
+ <li><a href="http://labs.jboss.com/portal/jgroups">JGroups</a>/<a href="http://www.jboss.org/products/jbosscache">JBossCache</a>
+ were upgraded to the latest releases. The server is already configured to
+ support channel multiplexing, when it becomes available.</li>
+ <li><a href="http://labs.jboss.com/jbossremoting/">JBoss Remoting</a> was
+ upgraded to the latest stable 2.2.x version. This was done in order to align
+ dependencies with the thirdparty libraries required by the new
+ <a href="http://labs.jboss.com/jbossmessaging/">JBoss Messaging</a>, which
+ means that, if you want, you can replace the default
+ <a href="http://www.jboss.org/wiki/Wiki.jsp?page=JBossMQ">JBossMQ</a>
+ messaging provider with JBoss Messaging, without having to revert to a
+ scoped deployment.</li>
+</ul>
+<p>Minor feature additions.</p>
+<ul>
+ <li>Remote access to MBeanInfo of JMX mbeans with non-serializable attributes
+ over the InvokerAdaptorService,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-1955">JBAS-1955</a>.</li>
+ <li>More options for externalizing LoginModule secrets,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-2895">JBAS-2895</a>.</li>
+ <li>New quartz JCA inflow adapter,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-3206">JBAS-3206</a>.</li>
+ <li>Support of transaction timeouts for MDBs,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-3321">JBAS-3321</a>.</li>
+ <li>Extenstions in the BarrierController to allow wider lifecycle control
+ options, <a href="http://jira.jboss.com/jira/browse/JBAS-3469">JBAS-3469</a>.</li>
+ <li>Configurable policies for determining the master node for HASingletons,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-2499">JBAS-2499</a>.</li>
+ <li>Fast datasource failover, when using the highly available datasource
+ resource adapter, <a href="http://jira.jboss.com/jira/browse/JBAS-3851">
+ JBAS-3851</a>.</li>
+ <li>The higly available (HA) version of the local and xa resource adapters
+ (jboss-ha-local-jdbc.rar, jboss-ha-xa-jdbc.rar), are now consider production
+ quality.</li>
+ <li>The JBoss javax.management.timer.Timer implementation has been cloned
+ into a difference package for use with a JDK5 runtime,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-3870">JBAS-3870</a>.</li>
+ <li>.EAR files support ./lib directory,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-4037">JBAS-4037</a>.</li>
+ <li>Support of value classes in EJBQLToSQL92Compiler,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-3975">JBAS-3975</a>.</li>
+ <li>Allow configuration of the table used for storing EJB Timers,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-4042">JBAS-4042</a>.</li>
+ <li>Allow developers to bundle their own JSF implementation. For details see<a href="http://jira.jboss.com/jira/browse/JBAS-4383">
+ JBAS-4383</a>, but do note that this configuration is not officially
+ supported by JBoss. It was added to allow legacy applications written
+ against MyFaces to work on JBoss 4.2.</li>
+</ul>
+<p>Plus more than 100 bug fixes, see the <a href="#Details">Detailed Release Notes</a>
+section for the full details.</p>
+<h2><a name="Compatibility">Compatibility Issues</a></h2>
+This lists the changes that could affect compatibility.
+<ul>
+ <li>A JavaSE 5 runtime is required to run JBossAS 4.2. A full JDK with
+ tools.jar support is no longer needed by jboss, since JBoss Web packages the
+ eclipse JDT compiler for compiling JSP pages and javassist has its own
+ internal compiler. JAVA_HOME can point to a JRE,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-4161">JBAS-4161</a>.</li>
+ <li>According to our
+ <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning">product versioning rules</a>,
+ JBossAS 4.2 is a minor upgrade against JBoss AS 4.0. The various JBoss APIs
+ should be stable but backwards compatibility for individual component
+ implementations may not be guaranteed, e.g. interoperating with another
+ JBoss instance that uses an older version of JGroups.</li>
+ <li>Tomcat 6 is now bundled as part of JBoss Web.
+ deploy/jbossweb-tomcat55.sar has been replaced by deploy/jboss-web.deployer.</li>
+ <li>conf/log4j.xml has been renamed to conf/jboss-log4j.xml, to allow
+ log4j.properties override from scoped deployments,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-1853">JBAS-1853</a>.</li>
+ <li>log4j and commons-logging have both been upgraded. commons-logging is
+ patched in addition, <a href="http://jira.jboss.com/jira/browse/JBAS-2823">
+ JBAS-2823</a>.</li>
+ <li>Since the latest log4j includes a trace level, there is no need to
+ reference the custom jboss TRACE level in conf/jboss-log4j.xml configs,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-4163">JBAS-4163</a>.<br>
+ Instead of: <category name="org.jboss.system"><priority value="TRACE"
+ class="org.jboss.logging.XLevel"/></category><br>
+ you can use: <category name="org.jboss.system"><priority
+ value="TRACE"/></category></li>
+ <li>Better integration with WebSphere MQ 5.x,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-3183">JBAS-3183</a>.</li>
+ <li>The MyFaces JSF implementation has been replaced by the Glassfish JSF
+ 1.2 one, <a href="http://jira.jboss.com/jira/browse/JBAS-3897">JBAS-3897</a>.</li>
+ <li>Hibernate, hibernate-annotations and hibernate-entity-manager have all
+ been upgraded. to v3.2.1.</li>
+ <li>The default invoker for EJBs has been changed from the rmi-invoker to
+ the unified-invoker, provided by JBoss Remoting,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-3950">JBAS-3950</a>.</li>
+ <li>Apache commons http-client and apache-codec were removed from
+ jbossall-client.jar, <a href="http://jira.jboss.com/jira/browse/JBAS-4365">
+ JBAS-4365</a>.</li>
+ <li>The address that is stored in the host portion of the RMI codebase URL
+ can now be set correctly,<a href="http://jira.jboss.com/jira/browse/JBAS-3325">
+ JBAS-3325</a>.</li>
+ <li>The java2ClassLoadingCompliance setting in jboss-web.xml was ignored;
+ this has been fixed, <a href="http://jira.jboss.com/jira/browse/JBAS-3047">
+ JBAS-3047</a>.</li>
+ <li>In JBoss 4.2 the unified invokers based on JBoss Remoting are the
+ default transport for accessing EJBs. Using the unified invokers JBoss 4.2
+ can interoperate safely with JBoss AS 4.0.4.GA/4.0.5.GA, using the flag
+ -Djboss.remoting.pre_2_0_compatible=true on the JBoss 4.2.x side. For
+ interoperating with older JBoss AS versions (3.2.8.SP1 to 4.0.3.SP1) the
+ legacy rmi or pooled invokers need to be used. See
+ <a href="http://jira.jboss.com/jira/browse/JBAS-4407">JBAS-4407</a> and the
+ wiki page on
+ <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossVersionCompatibilityMatrix">
+ JBoss Version Compatibility</a>.</li>
+</ul>
+<h2><a name="Configuration">Configuration Issues</a></h2>This lists the changes that could affect configuration.<ul>
+ <li>JBossAS now binds its services to localhost (127.0.0.1) *by default*,
+ instead of binding to all available interfaces (0.0.0.0). This was primarily
+ done for security reasons because of concerns of users going to production
+ without having s<a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureJBoss">ecured
+ their servers properly</a>. To enable remote access by binding JBoss
+ services to a particular interface, simply run jboss with the -b option, but
+ be aware you still need to
+ <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureJBoss">secure you
+ server properly</a>.</li>
+ <li>There now distinct properties to configure the various mcast ports,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-4021">JBAS-4021</a>.</li>
+ <li>When running under linux, run.sh forces the use of IPv4, due to a jdk
+ bug, <a href="http://jira.jboss.com/jira/browse/JBAS-4332">JBAS-4332</a>.</li>
+ <li>JBoss EJB3 is now included by default. If you don't need/want EJB3
+ support, simply remove deploy/ejb3.deployer.</li>
+ <li>When using native libraries for JBoss Web store them in
+ JBOSS_HOME/bin/native, which is automatically included in the classpath,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-4162">JBAS-4162</a>.</li>
+ <li>JBoss Transactions is the new default transaction manager in JBoss. It
+ is configured in conf/jboss-service.xml and has additional properties
+ defined in conf/jbossjta-properties.xml. The transaction log is stored by
+ default at server/default/data/tx-object-store.</li>
+ <li>If you are on redhat linux, check out the changes in bin/jboss_init_redhat.sh,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-4041">JBAS-4041</a>.</li>
+ <li>The JBossAS distributions usually include the installer (.jar), the sources
+ (.tar.gz) and the canonical binary release (.zip). Unzipping the binary
+ distribution (.zip) with a native unzip utility will restore correctly the
+ executable permission in the /bin/*.sh files. However, unzipping using the
+ JDK jar utility ignores the executable bit, so this need to be set manually.</li>
+ <li>bin/shutdown.sh no longer sources run.conf,
+ <a href="http://jira.jboss.com/jira/browse/JBAS-4155">JBAS-4155</a>.</li>
+</ul>
+<h2><a name="Library Updates">Library Updates</a></h2>
+Against JBossAS 4.0.5.GA
+<h3>JBoss Library Updates</h3>
+<ul>
+ <li>hibernate, upgraded to v3.2.3.GA (from v3.2.0.GA)</li>
+ <li>hibernate-annotations upgraded to v3.2.1.GA (from v3.2.0.GA)</li>
+ <li>hibernate-entitymanager upgraded to v3.2.1.GA (from v3.2.0.GA)</li>
+ <li>javassist, upgraded to v3.5.0.GA (from v3.3.0.GA)</li>
+ <li>jboss-aop, upgraded to v1.5.5.GA (from v1.5.2.GA)</li>
+ <li>jboss-backport-concurrent v2.1.0.GA removed</li>
+ <li>jboss-cache, upgraded to v1.4.1.SP3 (from v1.4.0.SP1)</li>
+ <li>jboss-common, upgraded to v1.2.0.GA (from v1.0.0.GA)</li>
+ <li>jboss-ts14, introduced at v4.2.3.SP3</li>
+ <li>jboss-retro-rt, v1.0.3.GA removed</li>
+ <li>jbossws, upgraded to v1.2.1.GA (from v1.0.3.SP1)</li>
+ <li>jboss-we4ee, v4.0.4.SP1 removed</li>
+ <li>jbossxb, upgraded to v1.0.0.GA (from v1.0.0.CR6)</li>
+ <li>jboss-remoting, upgraded to v2.2.0.SP4 (from v1.4.3.GA)</li>
+ <li>jboss-vfs, introduced at v1.0.0.GA</li>
+ <li>jboss-web, introduced at v2.0.0.GA</li>
+ <li>jgroups, upgraded to v2.4.1.SP3 (from v2.2.7.SP1)</li>
+</ul>
+<h3>Thirdparty Library Updates</h3>
+<ul>
+ <li>apache-addressing, at v7-19, removed</li>
+ <li>apache-digester, upgraded to v1.7 (from v1.6)</li>
+ <li>apache-discovery, upgraded to v0.4 (from v0.2)</li>
+ <li>apache-fileupload, upgraded to v1.1.1 (from v1.0)</li>
+ <li>apache-httpclient, upgraded to v3.0.1 (from v2.0.2)</li>
+ <li>apache-log4j, upgraded to v1.2.14 (from v1.2.8)</li>
+ <li>apache-logging, upgraded to v1.1.0.jboss (from v1.0.5-jboss)</li>
+ <li>apache-myfaces, v1.1.4 removed</li>
+ <li>apache-slide, upgrade to v2.1 (from v1.0.16)</li>
+ <li>apache-tomcat, upgraded to v5.5.20 removed</li>
+ <li>apache-wss4j, v7-19, removed</li>
+ <li>apache-xalan, upgraded to v2.7.0.patch01 (from v2.7.0)</li>
+ <li>gnu-getopt, upgraded to v1.0.12 (from v1.0.10)</li>
+ <li>jaxen, upgraded to v1.1 (from v1.1-beta9)</li>
+ <li>junit, upgraded to v3.8.2 (from v3.8.1)</li>
+ <li>junitejb v1.4 removed</li>
+ <li>qdox upgraded to v1.6.1 (from v1.4)</li>
+ <li>sleepycat at v1.5.2 removed</li>
+ <li>stax-api, introduced at v1.0</li>
+ <li>sun-jsf, introduced at v1.2_04_P01</li>
+ <li>sun-jstl, introduced at v1.2</li>
+ <li>sun-servlet, upgraded to v2.5 (from v2.4)</li>
+ <li>woodstox, introduced at v3.1.1</li>
+ <li>wutka-dtdparser at v1.2.1 removed</li>
+ <li>xdoclet, upgraded to v1.2.3 (from v1.2b3)</li>
+ <li>xml-sax, at v2.0.x removed</li>
+</ul>
+
+<h1><a name="Details">Detailed Release Notes</a></h1>
+
+<h3>Includes versions: JBossAS-4.2.0.CR1, JBossAS-4.2.0.CR2, JBossAS-4.2.0.GA</h3>
+
+<hr/>
+
+<h2>Feature Request</h2>
+<ul>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-1824">JBAS-1824</a> ] JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-1955">JBAS-1955</a> ] XMBean Interceptor for InvokerAdaptorService to deal with NonSerializableExceptions </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2249">JBAS-2249</a> ] Cleanup the org.jboss.naming packaging </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2523">JBAS-2523</a> ] Add a multi-thread option to JndiLoginInitialContextFactory. </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2895">JBAS-2895</a> ] Extend SecureIdentityLoginModule to externalize the secret </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2909">JBAS-2909</a> ] Testcase infra structure for MemoryLeaks </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3206">JBAS-3206</a> ] Quartz resource adaptor integration </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3321">JBAS-3321</a> ] Support for "method-attributes" including "transaction-timeout" for MDBs </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3400">JBAS-3400</a> ] JaasSecurityManagerService can show security provider/JCA algorithm information </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3469">JBAS-3469</a> ] Enhance the BarrierController with the ability to destroy/re-create the Barrier </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3675">JBAS-3675</a> ] Add LockOwnerName to ThreadDump output from ServerInfo </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3769">JBAS-3769</a> ] JBossMail Adapter needs logging improvements </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3846">JBAS-3846</a> ] add mail.smtp.port property to mail-service.xml </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3847">JBAS-3847</a> ] Extend EJBContext.getRollbackOnly to cover transactions which have been asynchronously rolled back </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3851">JBAS-3851</a> ] Slow DataSource Failover - JCA Stale Connection Detection </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3870">JBAS-3870</a> ] Clone the JBossMX javax.management.timer.Timer implementation, to a jboss package </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3966">JBAS-3966</a> ] Add a VersionNumber attribute on the jboss.system:type=Server mbean </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3975">JBAS-3975</a> ] support value classes in EJBQLToSQL92Compiler </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4037">JBAS-4037</a> ] Add support for ear lib directory </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4042">JBAS-4042</a> ] Allow configuration of timers table name (and schema) </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4047">JBAS-4047</a> ] PooledInvokerProxy.getPooledConnection() could hold a lock for shorter period of time </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4077">JBAS-4077</a> ] Full programmatic login integration with web container </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4120">JBAS-4120</a> ] modify testsuite start/stop management </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4127">JBAS-4127</a> ] Need an example datasource for MSSQL 2005 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4236">JBAS-4236</a> ] Upgrade to JSF RI 1.2_04 P01 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4251">JBAS-4251</a> ] JMS persistance configuration for db2 (db2-jdbc2-service.xml) </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4268">JBAS-4268</a> ] Provide web-facesconfig_1_2.xsd in $JBOSS_HOME/docs/schema </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4289">JBAS-4289</a> ] Provide persistence_1_0.xsd and orm_1_0.xsd in $JBOSS_HOME/docs/schema </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4297">JBAS-4297</a> ] expose flush operation on table cache MBean's </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4340">JBAS-4340</a> ] Key generators for StoreManager2 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4341">JBAS-4341</a> ] Double index creation in alterTable </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4383">JBAS-4383</a> ] Allow a different JSF implementation to be packaged in the WAR </li>
+</ul>
+<h2>Bug</h2>
+<ul>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-1537">JBAS-1537</a> ] When Tomcat error handler is invoked, JBossGenericPrincipal is returned instead of custom principal </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4183">JBAS-4183</a> ] Failed to update attributes through JMX console </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2113">JBAS-2113</a> ] Tables creation problem on Oracle </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2215">JBAS-2215</a> ] Datasource deployments should only depend on a jrmp invoker when use-java-context is true </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2731">JBAS-2731</a> ] JndiLoginInitialContextFactory still extends org.jnp.interfaces.NamingContextFactory </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3047">JBAS-3047</a> ] WebApps ignore java2ClassLoadingCompliance in jboss-web.xml </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3071">JBAS-3071</a> ] MemoryLeak (redeployment) on EJB3 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3924">JBAS-3924</a> ] InvlidationManager$InvlidationGroupImpl produces incorrect log4j DEBGU level setting </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3198">JBAS-3198</a> ] Problems with separated ClassLoaders for EARs and pooled invoker (PooledInvokerHA). </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3265">JBAS-3265</a> ] Problem with empty classname in classloader </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3268">JBAS-3268</a> ] FormAuthenticator has copy/paste error </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3316">JBAS-3316</a> ] outdated log4j.jar causes UndeclaredThrowableException </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3325">JBAS-3325</a> ] Fix the handling of BindAddress and Host in org.jboss.web.WebService </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3352">JBAS-3352</a> ] Provide better validation of the redelivery parameters on JBossMQ queues and topics </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3398">JBAS-3398</a> ] Non exploded sar containing war cannot undeploy the war file properly </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3691">JBAS-3691</a> ] NoClassDefFoundError performing remote lookup of dynamic proxy using IBM JDK </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3703">JBAS-3703</a> ] Update JRMPInvoker to not cast exported object to RemoteStub </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3721">JBAS-3721</a> ] Clustered SSO entries not properly cleaned up if a server crashes </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3746">JBAS-3746</a> ] org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCase.testValidAttribute failure </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3780">JBAS-3780</a> ] Deploying empty file to farm directory causes ScannerThread to hang </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3781">JBAS-3781</a> ] Stateful SB Instance Interceptor should not push SubjectContext if RunAsIdentity present </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3784">JBAS-3784</a> ] derby-jdbc2-service.xml not updated to jboss 4.x </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3785">JBAS-3785</a> ] Syntax Error in derby-jdbc2-service.xml </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3800">JBAS-3800</a> ] EJBQLToSQL92Compiler should use only searchable columns with DISTINCT </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3805">JBAS-3805</a> ] Validation problem with jboss-web_4_0.dtd's replication-field-batch-mode element </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3821">JBAS-3821</a> ] Uncatch JMSException in receive() methods in SpyMessageConsumer.java </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3828">JBAS-3828</a> ] spelling mistake in xml tag </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3833">JBAS-3833</a> ] Cannot unregister HAMembershipListener </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3838">JBAS-3838</a> ] ServerInfo does not check response from getThreadInfo for null </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3840">JBAS-3840</a> ] StackTrace appears on stderr when session.processSessionRepl() failed without tx </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3849">JBAS-3849</a> ] Duplicating _$$_javassist_ classes after remote - call - OutOfMemory: PermGen </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3855">JBAS-3855</a> ] org.jboss.invocation.InvocationStatistics are not serializable and cannot be queried by twiddle </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3860">JBAS-3860</a> ] XAManagedConnection should implement LocalTransaction to clean up hanging LocalTransaction </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3861">JBAS-3861</a> ] DeploymentFileRepository can be used to write/remove arbitrary files in the filesystem </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3917">JBAS-3917</a> ] The JMS JCA adapter's DLQMaxResent is set by default to 0, causing messages to go straight to DLQ </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3941">JBAS-3941</a> ] JBossCacheService fails in start if context path contains '/' </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3947">JBAS-3947</a> ] JConsole throws exception on connect post JBoss4.0.3SP1 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3953">JBAS-3953</a> ] OracleDatabasePersistencePlugin does not override selectTimers(ObjectName containerId) - selecting persisted timers fails at startup </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3956">JBAS-3956</a> ] JACC PolicyContextHandler usage leaks ThreadLocal values </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3963">JBAS-3963</a> ] JBoss AS security test case(CustomSecurityManagerTestCase) failed </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3964">JBAS-3964</a> ] DeployerInterceptorEJB3 depends on jboss.ejb3:service=EJB3Deployer </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3972">JBAS-3972</a> ] incorrect synchronization in JmsServerSessionPool </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4002">JBAS-4002</a> ] JBossWorkManager treats ExecutionContext transaction timeout as milliseconds when it should be seconds are per the API </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4014">JBAS-4014</a> ] timer persistence in afterCompletion </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4033">JBAS-4033</a> ] cache partition index calculation </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4035">JBAS-4035</a> ] BatchReplicationClusteredSessionValve masks exceptions </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4041">JBAS-4041</a> ] jboss_init_redhat.sh is incompatible with a clustered config </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4048">JBAS-4048</a> ] ExternalContext needs to expand its proxy interface collection </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4056">JBAS-4056</a> ] Web Console causes an error when navigating to EJB statistics page (MBeanProxyCreationException) </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4060">JBAS-4060</a> ] NPE in StandardSession.endAccess() </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4067">JBAS-4067</a> ] Collection modifications do not trigger FieldBasedClusteredSession version update </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4072">JBAS-4072</a> ] XAManagedConnectionFactory does not allow for 'is" form of XADataSource properties </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4075">JBAS-4075</a> ] JBossCacheManager.findLocalSessions concurrency issue </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4090">JBAS-4090</a> ] Race condition in Connection.close() can deadlock the JBossMQ's ping thread. </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4097">JBAS-4097</a> ] DummyTransactionManager polluting JNDI in testsuite </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4103">JBAS-4103</a> ] testsuite testcases' reports overwritten </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4114">JBAS-4114</a> ] LdapExtLoginModule needs to mask BIND_CREDENTIAL in trace logging </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4116">JBAS-4116</a> ] JRMPInvokerHA fails with a NPE when no JRMPInvoker is setup on the server </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4118">JBAS-4118</a> ] A truly trivial issue; a typo... </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4121">JBAS-4121</a> ] Race condition in JCA Pool Filler </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4124">JBAS-4124</a> ] Using getDefaultSession istead of getSession in org/jboss/resource/adapter/mail/inflow/MailFolder.java </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4155">JBAS-4155</a> ] run.conf used from other scripts than run.sh </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4158">JBAS-4158</a> ] JACC:WebUserDataPermission creation for unchecked policy should consider excluded constraints </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4163">JBAS-4163</a> ] Interation between custom jboss trace and log4j trace levels </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4170">JBAS-4170</a> ] Background validation for JCA connection pools incorrectly returns destroyed connection </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4178">JBAS-4178</a> ] RunAsListener uses unsupported implementation </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4184">JBAS-4184</a> ] Missing "org.jboss.naming.NamingContextFactory " in jbossall-client.jar </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4187">JBAS-4187</a> ] jsp_2_1.xsd is missing </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4191">JBAS-4191</a> ] ProxyFactory leaks classloader if SFSB is used </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4202">JBAS-4202</a> ] NPE if additional_data is not set </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4204">JBAS-4204</a> ] Don't allow removal of durable topic subscriptions when there are active subscribers or unacknowledged messages </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4216">JBAS-4216</a> ] Out Of Memory Errors </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4218">JBAS-4218</a> ] Incorrect description in connector_1_0.dtd </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4225">JBAS-4225</a> ] Error starting up jbossmq PersistenceManager with Sybase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4226">JBAS-4226</a> ] alternative deployment descriptor resolution fails on unix </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4229">JBAS-4229</a> ] HASingletonController doesn't handle "split brain" correctly. </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4231">JBAS-4231</a> ] JMXOpsAccessControlFilter is Not Thread Safe </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4232">JBAS-4232</a> ] Start up error when installed in path with spaces </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4238">JBAS-4238</a> ] javax.transaction.RollbackException root cause </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4240">JBAS-4240</a> ] SQL error in uuid-key-generator.sar jboss-service.xml against DB2 7.2 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4243">JBAS-4243</a> ] build.bat does not process command line arguments correctly </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4252">JBAS-4252</a> ] Add jboss-web_4_2.dtd to http://www.jboss.org/j2ee/dtd/ and problematic include of service-ref_4_2.dtd </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4257">JBAS-4257</a> ] Jboss fails to start with MySQL due to case sensitive issue </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4278">JBAS-4278</a> ] Timers: PreparedStatement.setNull() should be used for null arguments </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4284">JBAS-4284</a> ] Duplicate 4446 binding in sample-bindings.xml </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4285">JBAS-4285</a> ] HiLoKeyGeneratorFactory.readObject() impl is incomplete </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4286">JBAS-4286</a> ] users.properties file not being correctly located in CustomSecurityManagerTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4291">JBAS-4291</a> ] PeriodTestCase - wrong computation of maxDeviation </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4299">JBAS-4299</a> ] Running version-release target on build/build-release.xml needs dom4j.jar in ${jboss.dist}/lib </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4304">JBAS-4304</a> ] Jboss calls ejbStore "inside" ejbPostCreate on the same entity. </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4305">JBAS-4305</a> ] Add serialVersionUID to org.jboss.console.plugins.EJBModuleLister </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4312">JBAS-4312</a> ] SpyConnectionConsumer should fire asynchFailure if it receives an error </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4316">JBAS-4316</a> ] Minor bug in debug output of HAPartitionImpl.viewAccepted </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4324">JBAS-4324</a> ] Race condition when checking logged on client ids </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4329">JBAS-4329</a> ] LinkRefPair GUID could change due to garbage collection </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4339">JBAS-4339</a> ] QualifiedTableName in EntityBridge2 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4351">JBAS-4351</a> ] url file:/opt/jboss/server/default/deploy/jbossws.sar/activation.jar could not be opened, does it exist? </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4352">JBAS-4352</a> ] Deployment scanner gets FileNotFound Exception </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4354">JBAS-4354</a> ] org.jboss.test.cluster.test.DRMTestCase(Default-TCP) failure </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4366">JBAS-4366</a> ] javax.enterprise.deploy.spi.TargetModuleID.getChildTargetModuleID() should return null when there are no children </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4387">JBAS-4387</a> ] testRetryWithJnpAndAutoDiscovery not finding custom address for autodiscovery </li>
+</ul>
+<h2>Patch</h2>
+<ul>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2026">JBAS-2026</a> ] Wrong placeholder ear created </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3754">JBAS-3754</a> ] ExceptionSorter which marks all exceptions as fatal </li>
+</ul>
+<h2>Task</h2>
+<ul>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-1853">JBAS-1853</a> ] Rename conf/log4j.xml to conf/jboss-log4j.xml to allow log4j.properties override. </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2617">JBAS-2617</a> ] ej3.deployer contains too many jars </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2823">JBAS-2823</a> ] Upgrade commons-logging to v1.1 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2865">JBAS-2865</a> ] Move org.jboss.naming package from server module to naming module </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3162">JBAS-3162</a> ] Testcase to validate set up of a root context web app </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3183">JBAS-3183</a> ] Integration with WebSphere MQ 5.x </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3272">JBAS-3272</a> ] update JBossRemoting to version 2.0.0 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3276">JBAS-3276</a> ] Exception Sorter Implementations should be validated against current RDBMS documentation. </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3437">JBAS-3437</a> ] Get the 3.2-compatibility tests passing </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3582">JBAS-3582</a> ] Get the ejb3-4.2 testsuite passing </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3611">JBAS-3611</a> ] 4.2-testsuite on RHEL4 (sun jdk5) </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3626">JBAS-3626</a> ] Upgrade jbossws to 1.2.0.GA </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3726">JBAS-3726</a> ] Introduce basic twiddle testing in the testsuite </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3776">JBAS-3776</a> ] Update SerialVersionUIDUnitTestCase to test against new versions </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3789">JBAS-3789</a> ] Update JBossORG-EULA.txt </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3842">JBAS-3842</a> ] Upgrade jboss aop to 1.5.4.SP2 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3886">JBAS-3886</a> ] Upgrade jboss and thirdparty dependencies for JBoss 4.2.0 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3899">JBAS-3899</a> ] Get all testsuites passing </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3900">JBAS-3900</a> ] Get the 4.0-compatibility tests passing </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3901">JBAS-3901</a> ] Get the 4.2-compatibility tests passing </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3906">JBAS-3906</a> ] 4.2 testsuite on RHEL4 (JRockit jdk5) </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3922">JBAS-3922</a> ] JBossEntityResolverMgr Mbean example should be included in jboss-4.x\docs\examples </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3971">JBAS-3971</a> ] Add basic classloader leakage tests </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3974">JBAS-3974</a> ] Remove versioned jars </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3993">JBAS-3993</a> ] Test suite should use client libraries for tests' classpaths </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4049">JBAS-4049</a> ] Consider removing Subject mixin from FIELD granularity session Pojos </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4050">JBAS-4050</a> ] Restore the org.jboss.web.tomcat.tc5.session FIELD granularity marker interfaces </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4051">JBAS-4051</a> ] Support the org.jboss.cache.aop marker interfaces for FIELD granularity pojos </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4100">JBAS-4100</a> ] Introduce v4_2 dtds/schemas </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4102">JBAS-4102</a> ] Remove jbossretro-rt.jar and jboss-backport-concurrent.jar dependencies </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4104">JBAS-4104</a> ] Remove namespace.jar from the build </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4119">JBAS-4119</a> ] Consoles and invokers need to accept local connections only </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4144">JBAS-4144</a> ] Remove remaining uses of the legacy ejbunit class (JUnitEJB) </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4147">JBAS-4147</a> ] Include derby-plugin.jar in docs/examples/varia </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4149">JBAS-4149</a> ] Update Jacc Authorization to consider deployment level roles </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4151">JBAS-4151</a> ] Install BPEL in all config </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4159">JBAS-4159</a> ] Create the release notes for 4.2.0.CR1 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4161">JBAS-4161</a> ] run.sh/.bat should not complaint when running with a JRE </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4162">JBAS-4162</a> ] run.bat/.sh should allow loading native libraries from bin/native, if it exists </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4179">JBAS-4179</a> ] Update interfaces for HASingletonEvictionPolicy </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4181">JBAS-4181</a> ] If -b 0.0.0.0 is used, do not pass wildcard addresss through to JGroups </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4182">JBAS-4182</a> ] Upgrade to JBoss Cache 1.4.0.SP3 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4207">JBAS-4207</a> ] tck14 tests require the use of commit option C to pass </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4255">JBAS-4255</a> ] Upgrade to jboss common 1.2.0.GA </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4258">JBAS-4258</a> ] Invoke Channel.down via reflection to allow future upgrade to JGroups 2.5 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4259">JBAS-4259</a> ] Include jbossws-1.2.1.GA </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4260">JBAS-4260</a> ] JBossMQ table schema can not be created within a transaction when using MS SQL Server jdbc driver </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4280">JBAS-4280</a> ] Publish the updated http://www.jboss.org/j2ee dtds/schemas </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4281">JBAS-4281</a> ] Upgrade to hibernate 3.2.3 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4295">JBAS-4295</a> ] throw a 'no transaction' exception instead of NPE </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4325">JBAS-4325</a> ] Create the release notes for 4.2.0.GA </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4331">JBAS-4331</a> ] Create the release notes for 4.2.0.CR2 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4332">JBAS-4332</a> ] bin/run.sh should force IPv4 on Linux systems </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4346">JBAS-4346</a> ] Upgrade jboss remoting to 2.2.0.SP2 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4347">JBAS-4347</a> ] Patch xalan 2.7.0 so that javax.xml.transform.TransformerFactory.newTransformer() does not return null </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4357">JBAS-4357</a> ] Upgrade to JBoss Web 2.0.0.GA </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4360">JBAS-4360</a> ] Upgrade to JGroups 2.4.1.SP3 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4365">JBAS-4365</a> ] Remove commons http-client and codec from jbossall-client.jar </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4371">JBAS-4371</a> ] Upgrade to jbossxb 1.0.0.GA </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4375">JBAS-4375</a> ] Upgrade Javassist to v3.5.0.GA </li>
+</ul>
+<h2>Sub-task</h2>
+<ul>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-2560">JBAS-2560</a> ] Replace the MockHAPartition unit test with one that uses a JGroups GossipRouter </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3612">JBAS-3612</a> ] failing org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3614">JBAS-3614</a> ] failing org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3615">JBAS-3615</a> ] failing test in org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3616">JBAS-3616</a> ] failing test org.jboss.test.jmx.test.RMIAdaptorUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3617">JBAS-3617</a> ] 3 failing tests in org.jboss.test.util.test.PropertyEditorsUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3636">JBAS-3636</a> ] Port HASingletonElectionPolicy to Branch_4_2 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3732">JBAS-3732</a> ] Remove classloader.equals optimization </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3792">JBAS-3792</a> ] Better error reporting when messages "mysteriously" vanish </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3863">JBAS-3863</a> ] Need to properly test the PooledInvoker for scoped invocations </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3887">JBAS-3887</a> ] Upgrade Javassist to v3.5.0.CR1 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3888">JBAS-3888</a> ] Upgrade to EJB3 RC10 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3890">JBAS-3890</a> ] Upgrade to Hibernate 3.2.1 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3891">JBAS-3891</a> ] Upgrade to JBoss Cache 1.4.1.SP2 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3892">JBAS-3892</a> ] Replace TxManager with JBoss Transactions 4.2.3.CR3 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3897">JBAS-3897</a> ] Switch to JSF1.2 Glassfish implementation </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3898">JBAS-3898</a> ] Switch to embedded JBossWeb 2.0.0.CR1 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3920">JBAS-3920</a> ] Upgrade to JGroups 2.4.1 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3939">JBAS-3939</a> ] Upgrade jbossxb to 1.0.0.CR9 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3949">JBAS-3949</a> ] Upgrade to log4j 1.2.14 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3950">JBAS-3950</a> ] Change ejb2 invoker to be the unified invoker </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3955">JBAS-3955</a> ] Upgrade commons-httpclient to v3.0.1 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3987">JBAS-3987</a> ] failing org.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3990">JBAS-3990</a> ] failing org.jboss.test.binding.BindingServiceUnitTestCase(binding-manager) </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3994">JBAS-3994</a> ] Upgrade apache digester to v1.7 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3995">JBAS-3995</a> ] org.jboss.test.classloader.test.UnifiedLoaderUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-3998">JBAS-3998</a> ] failing org.jboss.test.classloader.test.ScopingUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4008">JBAS-4008</a> ] Upgrade jboss-common to 1.0.4.GA </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4011">JBAS-4011</a> ] failing org.jboss.test.tm.test.TxTimeoutUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4013">JBAS-4013</a> ] Add ability to use multiplexer to ClusterPartition </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4015">JBAS-4015</a> ] failing org.jboss.test.invokers.test.MultiInvokersUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4016">JBAS-4016</a> ] failing org.jboss.test.jca.test.BaseConnectionManager{Unit|Stress}TestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4017">JBAS-4017</a> ] failing org.jboss.test.jca.test.XAExceptionUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4018">JBAS-4018</a> ] failing org.jboss.test.jrmp.test.DynLoadingUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4019">JBAS-4019</a> ] failing org.jboss.test.security.test.SRPUnitTestCase - unlimited crypto support needed </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4021">JBAS-4021</a> ] Distinct system properties for mcast_port in each config file </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4023">JBAS-4023</a> ] failing org.jboss.test.securitymgr.test.WebIntegrationUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4024">JBAS-4024</a> ] failing org.jboss.test.txiiop.test.IIOPUserTransactionStressTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4025">JBAS-4025</a> ] failing org.jboss.test.web.test.ssl.SSLUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4026">JBAS-4026</a> ] failing org.jboss.test.web.test.JSFIntegrationUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4031">JBAS-4031</a> ] failing org.jboss.test.jacc.test.* tests </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4058">JBAS-4058</a> ] Use the JDK 5 version of JBoss Cache </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4064">JBAS-4064</a> ] failing org.jboss.test.jacc.test.*(JACC+SecurityMgr) </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4066">JBAS-4066</a> ] failing org.jboss.test.classloader.test.CircularityUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4073">JBAS-4073</a> ] failing org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4074">JBAS-4074</a> ] failing org.jboss.test.jbossmq.test.UIL2JBossMQUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4076">JBAS-4076</a> ] failing org.jboss.test.jca.test.{Contentious|Recycling|Uncontended}*StressTestCase tests </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4079">JBAS-4079</a> ] failing org.jboss.test.tm.test.Simple*LocalStressTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4080">JBAS-4080</a> ] failing org.jboss.test.security.test.CustomPrincipalPropagationUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4081">JBAS-4081</a> ] failing org.jboss.test.security.test.CustomSecurityManagerTestCase(custom-secmgr) </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4082">JBAS-4082</a> ] failing org.jboss.test.naming.test.* tests </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4085">JBAS-4085</a> ] failing org.jboss.test.web.test.WebIntegrationUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4101">JBAS-4101</a> ] Authorization Interceptor throws ClassCastException </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4126">JBAS-4126</a> ] failing org.jboss.test.aop.test tests </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4136">JBAS-4136</a> ] Update XDoclet to an official release </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4137">JBAS-4137</a> ] Update apache-discovery to 0.4 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4139">JBAS-4139</a> ] Update Jaxen to an official release </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4140">JBAS-4140</a> ] Remove sleepycat from thirdpart </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4141">JBAS-4141</a> ] Update apache-slide to v2.1 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4143">JBAS-4143</a> ] remove apache-addressing and apache-wss4j </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4160">JBAS-4160</a> ] failing org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4190">JBAS-4190</a> ] Add EJB2 SFSB and EJB3 Session bean testing to ClassloaderLeakUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4222">JBAS-4222</a> ] Add support for stopping ILs triggering the ExceptionListener - UIL2 </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4230">JBAS-4230</a> ] Be explicit about allowing NULL in the JBossMQ JDBC configuration </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4244">JBAS-4244</a> ] failing org.jboss.test.jca.test.CachedConnectionBankStressTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4245">JBAS-4245</a> ] org.jboss.test.jca.test.TxInflowUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4247">JBAS-4247</a> ] failing org.jboss.test.messagedriven.test.JMSContainerInvokerQueueMessageDrivenUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4248">JBAS-4248</a> ] org.jboss.test.txtimer.test.EntityBeanTestCase / PersistenceTestCase regressions </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4256">JBAS-4256</a> ] Add support for stopping ILs triggering the ExceptionListener - JVMIL </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4270">JBAS-4270</a> ] failing org.jboss.test.jmx.test.RMIAdaptorAuthorizationUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4271">JBAS-4271</a> ] failing org.jboss.test.pooled.test.SSLSocketsUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4272">JBAS-4272</a> ] failing org.jboss.test.classloader.leak.test.Ejb3ClassloaderLeakUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4279">JBAS-4279</a> ] failing org.jboss.test.cmp2.lob.LOBUnitTestCase in jboss-3.2-compatiblity-matrix </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4330">JBAS-4330</a> ] Give meaningful names to the EJB Timer java.util.Timer threads </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4336">JBAS-4336</a> ] Remove XLevel trace example from jboss-log4j.xml as it is not needed anymore. </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4359">JBAS-4359</a> ] Fix the org.jboss.test.classloader.leak.test.ClassloaderLeakUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4373">JBAS-4373</a> ] failing org.jboss.test.securitymgr.test.WebIntegrationUnitTestCase </li>
+<li> [ <a href="http://jira.jboss.com/jira/browse/JBAS-4374">JBAS-4374</a> ] failing org.jboss.test.cluster.test.StateTransferTestCase </li>
+</ul>
+
+<h2><a name="Documentation">Documentation and Help</a></h2>
+Documentation and help may be obtained from the JBoss site.
+<ul>
+ <li><a href="http://labs.jboss.com/portal/jbossas/docs">JBoss AS Documentation</a></li>
+ <li><a href="http://wiki.jboss.org/">JBoss Wiki</a></li>
+ <li><a href="http://jira.jboss.org/">JBoss JIRA</a></li>
+ <li><a href="http://www.jboss.org/index.html?module=bb">JBoss Forums</a></li>
+</ul>
+
+<h2><a name="Licenses">Licenses</a></h2>
+
+<p>JBoss is licensed under the <a href="lgpl.html">LGPL</a>, as explained in the
+ <a href="JBossORG-EULA.txt">JBoss End User License Agreement</a>.
+ The licence texts for JBoss and the thirdparty components it uses may be found in the
+ docs/licenses directory of the distribution. <a href="docs/licenses">Browse Licences</a>
+</p>
+
+<h2><a name="About">About JBoss, a division of RedHat</a></h2>
+
+<p>JBoss, a division of RedHat, is in the business of providing superior technical support
+ to our customers. Our goal is to make Professional Open Source™ the <b>SAFE
+ CHOICE</b>
+ for you. We accomplish this by backing up our open source Java products
+ with technical support services that are delivered by the core
+ developers themselves. We can help you to train your staff and provide
+ you with support at every stage of the application lifecycle - from
+ development and integration through deployment and maintenance. Visit
+ the <a href="http://www.jboss.org/services/index">JBoss Services</a>
+ page for more information.
+</p>
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/readme_j2ee.html
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/readme_j2ee.html (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/readme_j2ee.html 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,71 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <title>JBoss J2EE Certification Readme</title>
+ <meta content="JBoss Inc." name="author">
+ <meta content="Info about the J2EE certification" name="description">
+</head>
+<body>
+To help assure the compatibility of J2EE implementations, Sun
+Microsystems has developed a Technology Compatibility Kit (TCK). In
+addition, Sun offers a branding license to J2EE implementations that
+wish to claim compatibility to the J2EE standards. In November, 2003
+Sun released J2EE 1.4, and with that release for the first time allowed
+open source implementations to license the TCK on a stand alone basis.
+At that time, JBoss, Inc. became a TCK licensee and committed to pass
+the test.<br>
+<br>
+The TCK is an extensive set of over 23,000 tests. The testing takes a
+very large commitment due to the size, lack of automation, and errors
+in a testing package of this size. JBoss enlisted the assistance of our
+J2EE Certification Founding Partners Atos Origin, Borland, Hewlett
+Packard, Iona, Intel, Sonic, Unisys, and webMethods. JBoss began work
+on this effort in January, 2004 and completed the full testing on JBoss
+4.0 by the end of June, 2004, which is a very aggressive timeline. Much
+of the time went into setting up and configuring the tests and
+understanding the nuances of the tests. Not surprisingly, there were
+only relatively minor changes made to the JBoss code base JBoss has
+been used by many customers as a defacto reference implementation for
+several years. The primary areas where new functionality was needed
+were in CSIV2 security for IIOP, a JAXR implementation, and the
+addition of a new web services implementation.<br>
+<br>
+JBoss, Inc. and our J2EE Certification Founding Partners are pleased
+that we have passed this significant milestone becoming the first Open
+Source implementation in the market to pass the J2EE 1.4 TCK. This
+brings our customers and partners and development community the
+assurance that Professional Open Source is a safe choice for deployment
+of your applications. <br>
+<br>
+NOTICE FROM SUN MICROSYSTEMS:
+Any redistributed derivative work of the software licensed hereunder
+must be compatible and branded with the appropriate compatibility logo
+specified by Sun and licensed by Sun pursuant to a separate Trademark
+License required to be executed by you with Sun. Redistribution of the
+software licensed hereunder must retain this notice.<br>
+<br>
+NOTICE FROM JBOSS, INC.
+The notice from Sun Microsystems does not in any way affect the LGPL
+license or impose additional conditions on the LGPL license.<i><font
+ face="Arial" size="2"><span
+ style="font-size: 10pt; font-style: italic; font-family: Arial;"></span></font></i><br>
+<br>
+ADDITIONAL NOTICE FROM SUN MICROSYSTEMS: This version of the JBoss
+Application Server source code is made available in support of the open
+source development process. Some numbered or tagged revisions of this
+source have been tested and found to pass the Java™ 2 Platform,
+Enterprise Edition (J2EE™) Compatibility Test Suite, and you can find
+information on which revisions or tags at <a
+ href="http://www.jboss.com">www.jboss.com</a>. Please note that since
+only binaries can be tested, source code cannot be described as a
+compatible implementation of the J2EE Specification. The different
+build environment on your machine and any changes you may make to this
+code could render your resulting build incompatible. Because of this,
+writing or deploying applications to builds based on this code can lead
+to lack of portability. You should instead consider deploying
+production applications on the pre-built binaries of the JBoss
+Application Server that are available at <a href="http://www.jboss.com">www.jboss.com</a>
+that have been tested and certified to meet the J2EE compatibility
+requirements.
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-log4j.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-log4j.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-log4j.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,297 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- Log4j Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: jboss-log4j.xml 62403 2007-04-18 15:26:43Z dimitris at jboss.org $ -->
+
+<!--
+ | For more configuration infromation and examples see the Jakarta Log4j
+ | owebsite: http://jakarta.apache.org/log4j
+ -->
+
+<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">
+
+ <!-- ================================= -->
+ <!-- Preserve messages in a local file -->
+ <!-- ================================= -->
+
+ <!-- A time/date based rolling appender -->
+ <appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
+ <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+ <param name="File" value="${jboss.server.log.dir}/server.log"/>
+ <param name="Append" value="false"/>
+
+ <!-- Rollover at midnight each day -->
+ <param name="DatePattern" value="'.'yyyy-MM-dd"/>
+
+ <!-- Rollover at the top of each hour
+ <param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
+ -->
+
+ <layout class="org.apache.log4j.PatternLayout">
+ <!-- The default pattern: Date Priority [Category] Message\n -->
+ <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
+
+ <!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
+ <param name="ConversionPattern" value="%d %-5r %-5p [%c] (%t:%x) %m%n"/>
+ -->
+ </layout>
+ </appender>
+
+ <!-- A size based file rolling appender
+ <appender name="FILE" class="org.jboss.logging.appender.RollingFileAppender">
+ <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+ <param name="File" value="${jboss.server.log.dir}/server.log"/>
+ <param name="Append" value="false"/>
+ <param name="MaxFileSize" value="500KB"/>
+ <param name="MaxBackupIndex" value="1"/>
+
+ <layout class="org.apache.log4j.PatternLayout">
+ <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
+ </layout>
+ </appender>
+ -->
+
+ <!-- ============================== -->
+ <!-- Append messages to the console -->
+ <!-- ============================== -->
+
+ <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
+ <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+ <param name="Target" value="System.out"/>
+ <param name="Threshold" value="INFO"/>
+
+ <layout class="org.apache.log4j.PatternLayout">
+ <!-- The default pattern: Date Priority [Category] Message\n -->
+ <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
+ </layout>
+ </appender>
+
+ <!-- ====================== -->
+ <!-- More Appender examples -->
+ <!-- ====================== -->
+
+ <!-- Buffer events and log them asynchronously
+ <appender name="ASYNC" class="org.apache.log4j.AsyncAppender">
+ <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+ <appender-ref ref="FILE"/>
+ <appender-ref ref="CONSOLE"/>
+ <appender-ref ref="SMTP"/>
+ </appender>
+ -->
+
+ <!-- EMail events to an administrator
+ <appender name="SMTP" class="org.apache.log4j.net.SMTPAppender">
+ <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+ <param name="Threshold" value="ERROR"/>
+ <param name="To" value="admin at myhost.domain.com"/>
+ <param name="From" value="nobody at myhost.domain.com"/>
+ <param name="Subject" value="JBoss Sever Errors"/>
+ <param name="SMTPHost" value="localhost"/>
+ <param name="BufferSize" value="10"/>
+ <layout class="org.apache.log4j.PatternLayout">
+ <param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}] %m%n"/>
+ </layout>
+ </appender>
+ -->
+
+ <!-- Syslog events
+ <appender name="SYSLOG" class="org.apache.log4j.net.SyslogAppender">
+ <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+ <param name="Facility" value="LOCAL7"/>
+ <param name="FacilityPrinting" value="true"/>
+ <param name="SyslogHost" value="localhost"/>
+ <layout class="org.apache.log4j.PatternLayout">
+ <param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}] %m%n"/>
+ </layout>
+ </appender>
+ -->
+
+ <!-- Log events to JMS (requires a topic to be created)
+ <appender name="JMS" class="org.apache.log4j.net.JMSAppender">
+ <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+ <param name="Threshold" value="ERROR"/>
+ <param name="TopicConnectionFactoryBindingName" value="java:/ConnectionFactory"/>
+ <param name="TopicBindingName" value="topic/MyErrorsTopic"/>
+ </appender>
+ -->
+
+ <!-- Log events through SNMP
+ <appender name="TRAP_LOG" class="org.apache.log4j.ext.SNMPTrapAppender">
+ <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+ <param name="ImplementationClassName" value="org.apache.log4j.ext.JoeSNMPTrapSender"/>
+ <param name="ManagementHost" value="127.0.0.1"/>
+ <param name="ManagementHostTrapListenPort" value="162"/>
+ <param name="EnterpriseOID" value="1.3.6.1.4.1.24.0"/>
+ <param name="LocalIPAddress" value="127.0.0.1"/>
+ <param name="LocalTrapSendPort" value="161"/>
+ <param name="GenericTrapType" value="6"/>
+ <param name="SpecificTrapType" value="12345678"/>
+ <param name="CommunityString" value="public"/>
+ <param name="ForwardStackTraceWithTrap" value="true"/>
+ <param name="Threshold" value="DEBUG"/>
+ <param name="ApplicationTrapOID" value="1.3.6.1.4.1.24.12.10.22.64"/>
+ <layout class="org.apache.log4j.PatternLayout">
+ <param name="ConversionPattern" value="%d,%p,[%t],[%c],%m%n"/>
+ </layout>
+ </appender>
+ -->
+
+ <!-- Emit events as JMX notifications
+ <appender name="JMX" class="org.jboss.monitor.services.JMXNotificationAppender">
+ <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+
+ <param name="Threshold" value="WARN"/>
+ <param name="ObjectName" value="jboss.system:service=Logging,type=JMXNotificationAppender"/>
+
+ <layout class="org.apache.log4j.PatternLayout">
+ <param name="ConversionPattern" value="%d %-5p [%c] %m"/>
+ </layout>
+ </appender>
+ -->
+
+ <!-- ================ -->
+ <!-- Limit categories -->
+ <!-- ================ -->
+
+ <!-- Limit the org.apache category to INFO as its DEBUG is verbose -->
+ <category name="org.apache">
+ <priority value="INFO"/>
+ </category>
+
+ <!-- Limit the org.jboss.serial (jboss-serialization) to INFO as its DEBUG is verbose -->
+ <category name="org.jboss.serial">
+ <priority value="INFO"/>
+ </category>
+
+ <!-- Limit the org.jgroups category to WARN as its INFO is verbose -->
+ <category name="org.jgroups">
+ <priority value="WARN"/>
+ </category>
+
+ <!-- Limit the jacorb category to WARN as its INFO is verbose -->
+ <category name="jacorb">
+ <priority value="WARN"/>
+ </category>
+
+ <!-- Limit JBoss categories
+ <category name="org.jboss">
+ <priority value="INFO"/>
+ </category>
+ -->
+
+ <!-- Limit the JSR77 categories -->
+ <category name="org.jboss.management">
+ <priority value="INFO"/>
+ </category>
+
+ <!-- Enable JBossWS message tracing
+ <category name="jbossws.SOAPMessage">
+ <priority value="TRACE"/>
+ </category>
+ -->
+
+ <!-- Decrease the priority threshold for the org.jboss.varia category
+ <category name="org.jboss.varia">
+ <priority value="DEBUG"/>
+ </category>
+ -->
+
+ <!-- Show the evolution of the DataSource pool in the logs [inUse/Available/Max]
+ <category name="org.jboss.resource.connectionmanager.JBossManagedConnectionPool">
+ <priority value="TRACE"/>
+ </category>
+ -->
+
+ <!--
+ | An example of enabling the custom TRACE level priority that is used
+ | by the JBoss internals to diagnose low level details. This example
+ | turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
+ | subpackages. This will produce A LOT of logging output.
+ |
+ | Note: since jboss AS 4.2.x, the trace level is supported natively by
+ | log4j, so although the custom org.jboss.logging.XLevel priority will
+ | still work, there is no need to use it. The two examples that follow
+ | will both enable trace logging.
+ <category name="org.jboss.system">
+ <priority value="TRACE" class="org.jboss.logging.XLevel"/>
+ </category>
+ <category name="org.jboss.ejb.plugins">
+ <priority value="TRACE"/>
+ </category>
+ -->
+
+ <!--
+ | Logs these events to SNMP:
+ - server starts/stops
+ - cluster evolution (node death/startup)
+ - When an EJB archive is deployed (and associated verified messages)
+ - When an EAR archive is deployed
+
+ <category name="org.jboss.system.server.Server">
+ <priority value="INFO" />
+ <appender-ref ref="TRAP_LOG"/>
+ </category>
+
+ <category name="org.jboss.ha.framework.interfaces.HAPartition.lifecycle">
+ <priority value="INFO" />
+ <appender-ref ref="TRAP_LOG"/>
+ </category>
+
+ <category name="org.jboss.deployment.MainDeployer">
+ <priority value="ERROR" />
+ <appender-ref ref="TRAP_LOG"/>
+ </category>
+
+ <category name="org.jboss.ejb.EJBDeployer">
+ <priority value="INFO" />
+ <appender-ref ref="TRAP_LOG"/>
+ </category>
+
+ <category name="org.jboss.deployment.EARDeployer">
+ <priority value="INFO" />
+ <appender-ref ref="TRAP_LOG"/>
+ </category>
+
+ -->
+
+ <!-- ======================= -->
+ <!-- Setup the Root category -->
+ <!-- ======================= -->
+
+ <root>
+ <appender-ref ref="CONSOLE"/>
+ <appender-ref ref="FILE"/>
+ </root>
+
+ <!-- Clustering logging -->
+ <!-- Uncomment the following to redirect the org.jgroups and
+ org.jboss.ha categories to a cluster.log file.
+
+ <appender name="CLUSTER" class="org.jboss.logging.appender.RollingFileAppender">
+ <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
+ <param name="File" value="${jboss.server.log.dir}/cluster.log"/>
+ <param name="Append" value="false"/>
+ <param name="MaxFileSize" value="500KB"/>
+ <param name="MaxBackupIndex" value="1"/>
+
+ <layout class="org.apache.log4j.PatternLayout">
+ <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
+ </layout>
+ </appender>
+ <category name="org.jgroups">
+ <priority value="DEBUG" />
+ <appender-ref ref="CLUSTER"/>
+ </category>
+ <category name="org.jboss.ha">
+ <priority value="DEBUG" />
+ <appender-ref ref="CLUSTER"/>
+ </category>
+ -->
+
+</log4j:configuration>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-minimal.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-minimal.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-minimal.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,151 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: jboss-minimal.xml 60298 2007-02-05 16:01:55Z dimitris at jboss.org $ -->
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- A minimal JBoss Server Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<server>
+
+ <!-- Load all jars from the JBOSS_DIST/server/<config>/lib directory. This
+ can be restricted to specific jars by specifying them in the archives
+ attribute.
+ -->
+ <classpath codebase="${jboss.server.lib.url:lib}" archives="*"/>
+
+ <!-- ==================================================================== -->
+ <!-- Log4j Initialization -->
+ <!-- ==================================================================== -->
+ <mbean code="org.jboss.logging.Log4jService"
+ name="jboss.system:type=Log4jService,service=Logging">
+ <attribute name="ConfigurationURL">resource:jboss-log4j.xml</attribute>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Thread Pool -->
+ <!-- ==================================================================== -->
+
+ <!-- A Thread pool service -->
+ <mbean code="org.jboss.util.threadpool.BasicThreadPool"
+ name="jboss.system:service=ThreadPool">
+ <attribute name="Name">JBoss System Threads</attribute>
+ <attribute name="ThreadGroupName">System Threads</attribute>
+ <!-- How long a thread will live without any tasks in MS -->
+ <attribute name="KeepAliveTime">60000</attribute>
+ <!-- The max number of threads in the pool -->
+ <attribute name="MaximumPoolSize">10</attribute>
+ <!-- The max number of tasks before the queue is full -->
+ <attribute name="MaximumQueueSize">1000</attribute>
+ <!-- The behavior of the pool when a task is added and the queue is full.
+ abort - a RuntimeException is thrown
+ run - the calling thread executes the task
+ wait - the calling thread blocks until the queue has room
+ discard - the task is silently discarded without being run
+ discardOldest - check to see if a task is about to complete and enque
+ the new task if possible, else run the task in the calling thread
+ -->
+ <attribute name="BlockingMode">run</attribute>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- JNDI -->
+ <!-- ==================================================================== -->
+
+ <!-- A simple mbean wrapper around the jndi Naming object. This
+ only handles an in memory instance. The NamingService uses this
+ as the JNDI store and exposes it remotely.
+ -->
+ <mbean code="org.jnp.server.NamingBeanImpl"
+ name="jboss:service=NamingBeanImpl"
+ xmbean-dd="resource:xmdesc/NamingBean-xmbean.xml">
+ </mbean>
+
+ <mbean code="org.jboss.naming.NamingService"
+ name="jboss:service=Naming"
+ xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
+ <!-- The call by value mode. true if all lookups are unmarshalled using
+ the caller's TCL, false if in VM lookups return the value by reference.
+ -->
+ <attribute name="CallByValue">false</attribute>
+ <!-- The listening port for the bootstrap JNP service. Set this to -1
+ to run the NamingService without the JNP invoker listening port.
+ -->
+ <attribute name="Port">1099</attribute>
+ <!-- The bootstrap JNP server bind address. This also sets the default
+ RMI service bind address. Empty == all addresses
+ -->
+ <attribute name="BindAddress">${jboss.bind.address}</attribute>
+ <!-- The port of the RMI naming service, 0 == anonymous -->
+ <attribute name="RmiPort">1098</attribute>
+ <!-- The RMI service bind address. Empty == all addresses
+ -->
+ <attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
+ <!-- The thread pool service used to control the bootstrap lookups -->
+ <depends optional-attribute-name="LookupPool"
+ proxy-type="attribute">jboss.system:service=ThreadPool</depends>
+ <!-- An example of using the unifed invoker as the transport.
+ <depends optional-attribute-name="InvokerProxyFactory"
+ proxy-type="attribute">jboss:service=proxyFactory,type=unified,target=Naming</depends>
+ -->
+ <depends optional-attribute-name="Naming"
+ proxy-type="attribute">jboss:service=NamingBeanImpl</depends>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Deployment Scanning -->
+ <!-- ==================================================================== -->
+
+ <!-- An mbean for hot deployment/undeployment of archives.
+ -->
+ <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
+ name="jboss.deployment:type=DeploymentScanner,flavor=URL">
+
+ <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>
+
+ <!-- The URLComparator can be used to specify a deployment ordering
+ for deployments found in a scanned directory. The class specified
+ must be an implementation of java.util.Comparator, it must be able
+ to compare two URL objects, and it must have a no-arg constructor.
+ Two deployment comparators are shipped with JBoss:
+ - org.jboss.deployment.DeploymentSorter
+ Sorts by file extension, as follows:
+ "sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip",
+ "*"
+ - org.jboss.deployment.scanner.PrefixDeploymentSorter
+ If the name portion of the url begins with 1 or more digits, those
+ digits are converted to an int (ignoring leading zeroes), and
+ files are deployed in that order. Files that do not start with
+ any digits will be deployed last, and they will be sorted by
+ extension as above with DeploymentSorter.
+ -->
+ <attribute name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute>
+
+ <!-- The Filter specifies a java.io.FileFilter for scanned
+ directories. Any file not accepted by this filter will not be
+ deployed. The org.jboss.deployment.scanner.DeploymentFilter
+ rejects the following patterns:
+ "#*", "%*", ",*", ".*", "_$*", "*#", "*$", "*%", "*.BAK",
+ "*.old", "*.orig", "*.rej", "*.bak", "*,v", "*~", ".make.state",
+ ".nse_depinfo", "CVS", "CVS.admin", "RCS", "RCSLOG", "SCCS",
+ "TAGS", "core", "tags"
+ -->
+ <attribute name="Filter">org.jboss.deployment.scanner.DeploymentFilter</attribute>
+
+ <attribute name="ScanPeriod">5000</attribute>
+
+ <!-- URLs are comma seperated and unprefixed arguments are considered
+ file URLs and resolve relative to server home(JBOSS_DIST/server/default)
+ unless the given path is absolute. Any referenced directories cannot
+ be unpackaged archives, use the parent directory of the unpacked
+ archive.
+ -->
+ <attribute name="URLs">
+ deploy/
+ </attribute>
+
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jboss-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,696 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: jboss-service.xml 62434 2007-04-19 21:22:50Z dimitris at jboss.org $ -->
+
+<!-- ===================================================================== -->
+<!-- JBoss Server Configuration -->
+<!-- ===================================================================== -->
+
+<server>
+
+ <!-- Load all jars from the JBOSS_DIST/server/<config>/lib directory. This
+ can be restricted to specific jars by specifying them in the archives
+ attribute.
+ -->
+ <classpath codebase="${jboss.server.lib.url:lib}" archives="*"/>
+
+ <!-- ==================================================================== -->
+ <!-- JSR-77 Single JBoss Server Management Domain -->
+ <!-- ==================================================================== -->
+ <mbean code="org.jboss.management.j2ee.LocalJBossServerDomain"
+ name="jboss.management.local:j2eeType=J2EEDomain,name=Manager">
+ <attribute name="MainDeployer">jboss.system:service=MainDeployer</attribute>
+ <attribute name="SARDeployer">jboss.system:service=ServiceDeployer</attribute>
+ <attribute name="EARDeployer">jboss.j2ee:service=EARDeployer</attribute>
+ <attribute name="EJBDeployer">jboss.ejb:service=EJBDeployer</attribute>
+ <attribute name="RARDeployer">jboss.jca:service=RARDeployer</attribute>
+ <attribute name="CMDeployer">jboss.jca:service=ConnectionFactoryDeployer</attribute>
+ <attribute name="WARDeployer">jboss.web:service=WebServer</attribute>
+ <attribute name="CARDeployer">jboss.j2ee:service=ClientDeployer</attribute>
+ <attribute name="MailService">jboss:service=Mail</attribute>
+ <attribute name="JMSService">jboss.mq:service=DestinationManager</attribute>
+ <attribute name="JNDIService">jboss:service=Naming</attribute>
+ <attribute name="JTAService">jboss:service=TransactionManager</attribute>
+ <attribute name="UserTransactionService">jboss:service=ClientUserTransaction</attribute>
+ <attribute name="RMI_IIOPService">jboss:service=CorbaORB</attribute>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- XMBean Persistence -->
+ <!-- ==================================================================== -->
+ <mbean code="org.jboss.system.pm.AttributePersistenceService"
+ name="jboss:service=AttributePersistenceService"
+ xmbean-dd="resource:xmdesc/AttributePersistenceService-xmbean.xml">
+ <!-- the AttributePersistenceService is persistent, itself -->
+
+ <!--
+ <attribute name="AttributePersistenceManagerClass">org.jboss.system.pm.XMLAttributePersistenceManager</attribute>
+ <attribute name="AttributePersistenceManagerConfig">
+ <data-directory>data/xmbean-attrs</data-directory>
+ </attribute>
+ <attribute name="ApmDestroyOnServiceStop">false</attribute>
+ <attribute name="VersionTag"></attribute>
+ -->
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Thread Pool -->
+ <!-- ==================================================================== -->
+
+ <!-- A Thread pool service -->
+ <mbean code="org.jboss.util.threadpool.BasicThreadPool"
+ name="jboss.system:service=ThreadPool">
+ <attribute name="Name">JBoss System Threads</attribute>
+ <attribute name="ThreadGroupName">System Threads</attribute>
+ <!-- How long a thread will live without any tasks in MS -->
+ <attribute name="KeepAliveTime">60000</attribute>
+ <!-- The max number of threads in the pool -->
+ <attribute name="MaximumPoolSize">10</attribute>
+ <!-- The max number of tasks before the queue is full -->
+ <attribute name="MaximumQueueSize">1000</attribute>
+ <!-- The behavior of the pool when a task is added and the queue is full.
+ abort - a RuntimeException is thrown
+ run - the calling thread executes the task
+ wait - the calling thread blocks until the queue has room
+ discard - the task is silently discarded without being run
+ discardOldest - check to see if a task is about to complete and enque
+ the new task if possible, else run the task in the calling thread
+ -->
+ <attribute name="BlockingMode">run</attribute>
+ </mbean>
+
+ <!-- Preload all custom editors for VMs that don't use the thread
+ context class loader when searching for PropertyEditors. Uncomment
+ if your JDK 1.3.0 VM fails to find JBoss PropertyEditors.
+ <mbean code="org.jboss.varia.property.PropertyEditorManagerService"
+ name="jboss:type=Service,name=BootstrapEditors">
+ <attribute name="BootstrapEditors">
+ java.math.BigDecimal=org.jboss.util.propertyeditor.BigDecimalEditor
+ java.lang.Boolean=org.jboss.util.propertyeditor.BooleanEditor
+ java.lang.Class=org.jboss.util.propertyeditor.ClassEditor
+ java.util.Date=org.jboss.util.propertyeditor.DateEditor
+ java.io.File=org.jboss.util.propertyeditor.FileEditor
+ java.net.InetAddress=org.jboss.util.propertyeditor.InetAddressEditor
+ java.lang.Integer=org.jboss.util.propertyeditor.IntegerEditor
+ javax.management.ObjectName=org.jboss.mx.util.propertyeditor.ObjectNameEditor
+ java.util.Properties=org.jboss.util.propertyeditor.PropertiesEditor
+ [Ljava.lang.String;=org.jboss.util.propertyeditor.StringArrayEditor
+ java.net.URL=org.jboss.util.propertyeditor.URLEditor
+ </attribute>
+ </mbean>
+ -->
+
+ <!-- ==================================================================== -->
+ <!-- Log4j Initialization -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.logging.Log4jService"
+ name="jboss.system:type=Log4jService,service=Logging"
+ xmbean-dd="resource:xmdesc/Log4jService-xmbean.xml">
+ <attribute name="ConfigurationURL">resource:jboss-log4j.xml</attribute>
+ <!-- Set the org.apache.log4j.helpers.LogLog.setQuiteMode. As of log4j1.2.8
+ this needs to be set to avoid a possible deadlock on exception at the
+ appender level. See bug#696819.
+ -->
+ <attribute name="Log4jQuietMode">true</attribute>
+ <!-- How frequently in seconds the ConfigurationURL is checked for changes -->
+ <attribute name="RefreshPeriod">60</attribute>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Active Alarm Table -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | The ActiveAlarmTable service is a simple JMX notification listener
+ | that maintains a table with the received notifications (alarms).
+ | The alarms can be acknowledged through the jmx or the web console.
+ | Modify the SubscriptionList below to subscribe for any notification
+ | in the system and treat it as an alarm.
+ | The JMXNotificationAppender is a log4j Appender that can be configured
+ | in log4j.xml, that trasforms logging events to JMX notification so they
+ | can be fed back into the table. By storing the WARN or higher level logging
+ | events you can have a quick view of important system faults.
+ |
+ | The following attributes may be set:
+ |
+ | MaxTableSize (default 1000)
+ | - set an upper limit to the number of stored alarms
+ | LogLevel (default DEBUG)
+ | - the log level to use for received notification, can be set to NONE
+ | ServerId (default jboss)
+ | - used to construct unique alarm ids
+ | SubscriptionList
+ | - subscribe for the notifications to be stored in the table
+
+ <mbean code="org.jboss.monitor.services.ActiveAlarmTable"
+ name="jboss.monitor:service=ActiveAlarmTable">
+ <attribute name="SubscriptionList">
+ <subscription-list>
+ <mbean name="jboss.monitor:*">
+ <notification type="jboss.alarm"/>
+ <notification type="JBOSS_MONITOR_NOTIFICATION"/>
+ </mbean>
+ <mbean name="jboss.system:service=Logging,type=JMXNotificationAppender"/>
+ </subscription-list>
+ </attribute>
+ </mbean>
+ -->
+
+ <!-- ==================================================================== -->
+ <!-- JBoss RMI Classloader - only install when available -->
+ <!-- ==================================================================== -->
+ <mbean code="org.jboss.util.property.jmx.SystemPropertyClassValue"
+ name="jboss.rmi:type=RMIClassLoader">
+ <attribute name="Property">java.rmi.server.RMIClassLoaderSpi</attribute>
+ <attribute name="ClassName">org.jboss.system.JBossRMIClassLoader</attribute>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Service Binding -->
+ <!-- ==================================================================== -->
+
+ <!-- Automatically activated when generatting the clustering environment -->
+ <!-- @TESTSUITE_CLUSTER_CONFIG@ -->
+
+ <!--
+ | Binding service manager for port/host mapping. This is a sample
+ | config that demonstrates a JBoss instances with a server name 'ports-01'
+ | loading its bindings from an XML file using the ServicesStoreFactory
+ | implementation returned by the XMLServicesStoreFactory.
+ |
+ | ServerName: The unique name assigned to a JBoss server instance for
+ | lookup purposes. This allows a single ServicesStore to handle mulitiple
+ | JBoss servers.
+ |
+ | StoreURL: The URL string passed to org.jboss.services.binding.ServicesStore
+ | during initialization that specifies how to connect to the bindings store.
+ | StoreFactory: The org.jboss.services.binding.ServicesStoreFactory interface
+ | implementation to create to obtain the ServicesStore instance.
+
+ <mbean code="org.jboss.services.binding.ServiceBindingManager"
+ name="jboss.system:service=ServiceBindingManager">
+ <attribute name="ServerName">ports-01</attribute>
+ <attribute name="StoreURL">${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml</attribute>
+ <attribute name="StoreFactoryClassName">
+ org.jboss.services.binding.XMLServicesStoreFactory
+ </attribute>
+ </mbean>
+ -->
+
+ <!-- ==================================================================== -->
+ <!-- Class Loading -->
+ <!-- ==================================================================== -->
+
+ <!-- A mini webserver used for dynamic and class and resource loading -->
+ <mbean code="org.jboss.web.WebService"
+ name="jboss:service=WebService">
+ <!-- The Bind address and Port -->
+ <attribute name="BindAddress">${jboss.bind.address}</attribute>
+ <attribute name="Port">8083</attribute>
+ <!-- The address to use for the host portion of the RMI codebase URL -->
+ <attribute name="Host">${java.rmi.server.hostname}</attribute>
+ <!-- Should non-EJB .class files be downloadable -->
+ <attribute name="DownloadServerClasses">true</attribute>
+ <!-- Should resources other than .class files be downloadable. Both
+ DownloadServerClasses and DownloadResources must be true for resources
+ to be downloadable. This is false by default because its generally a
+ bad idea as server configuration files that container security
+ information can be accessed.
+ -->
+ <attribute name="DownloadResources">false</attribute>
+
+ <!-- Use the default thread pool for dynamic class loading -->
+ <depends optional-attribute-name="ThreadPool"
+ proxy-type="attribute">jboss.system:service=ThreadPool</depends>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- JNDI -->
+ <!-- ==================================================================== -->
+
+ <!-- A simple mbean wrapper around the jndi Naming object. This
+ only handles an in memory instance. The NamingService uses this
+ as the JNDI store and exposes it remotely.
+ -->
+ <mbean code="org.jnp.server.NamingBeanImpl"
+ name="jboss:service=NamingBeanImpl"
+ xmbean-dd="resource:xmdesc/NamingBean-xmbean.xml">
+ </mbean>
+
+ <mbean code="org.jboss.naming.NamingService"
+ name="jboss:service=Naming"
+ xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
+ <!-- The call by value mode. true if all lookups are unmarshalled using
+ the caller's TCL, false if in VM lookups return the value by reference.
+ -->
+ <attribute name="CallByValue">false</attribute>
+ <!-- The listening port for the bootstrap JNP service. Set this to -1
+ to run the NamingService without the JNP invoker listening port.
+ -->
+ <attribute name="Port">1099</attribute>
+ <!-- The bootstrap JNP server bind address. This also sets the default
+ RMI service bind address. Empty == all addresses
+ -->
+ <attribute name="BindAddress">${jboss.bind.address}</attribute>
+ <!-- The port of the RMI naming service, 0 == anonymous -->
+ <attribute name="RmiPort">1098</attribute>
+ <!-- The RMI service bind address. Empty == all addresses
+ -->
+ <attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
+ <!-- The thread pool service used to control the bootstrap lookups -->
+ <depends optional-attribute-name="LookupPool"
+ proxy-type="attribute">jboss.system:service=ThreadPool</depends>
+ <!-- An example of using the unifed invoker as the transport.
+ <depends optional-attribute-name="InvokerProxyFactory"
+ proxy-type="attribute">jboss:service=proxyFactory,type=unified,target=Naming</depends>
+ -->
+ <depends optional-attribute-name="Naming"
+ proxy-type="attribute">jboss:service=NamingBeanImpl</depends>
+ </mbean>
+
+ <mbean code="org.jboss.naming.JNDIView"
+ name="jboss:service=JNDIView"
+ xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">
+ <!-- The HANamingService service name -->
+ <attribute name="HANamingService">jboss:service=HAJNDI</attribute>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Security -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.security.plugins.SecurityConfig"
+ name="jboss.security:service=SecurityConfig">
+ <attribute name="LoginConfig">jboss.security:service=XMLLoginConfig</attribute>
+ </mbean>
+ <mbean code="org.jboss.security.auth.login.XMLLoginConfig"
+ name="jboss.security:service=XMLLoginConfig">
+ <attribute name="ConfigResource">login-config.xml</attribute>
+ </mbean>
+
+ <!-- JAAS security manager and realm mapping -->
+ <mbean code="org.jboss.security.plugins.JaasSecurityManagerService"
+ name="jboss.security:service=JaasSecurityManager">
+ <!-- A flag which indicates whether the SecurityAssociation server mode
+ is set on service creation. This is true by default since the
+ SecurityAssociation should be thread local for multi-threaded server
+ operation.
+ -->
+ <attribute name="ServerMode">true</attribute>
+ <attribute name="SecurityManagerClassName">org.jboss.security.plugins.JaasSecurityManager</attribute>
+ <attribute name="DefaultUnauthenticatedPrincipal">anonymous</attribute>
+ <!-- DefaultCacheTimeout: Specifies the default timed cache policy timeout
+ in seconds.
+ If you want to disable caching of security credentials, set this to 0 to
+ force authentication to occur every time. This has no affect if the
+ AuthenticationCacheJndiName has been changed from the default value.
+ -->
+ <attribute name="DefaultCacheTimeout">1800</attribute>
+ <!-- DefaultCacheResolution: Specifies the default timed cache policy
+ resolution in seconds. This controls the interval at which the cache
+ current timestamp is updated and should be less than the DefaultCacheTimeout
+ in order for the timeout to be meaningful. This has no affect if the
+ AuthenticationCacheJndiName has been changed from the default value.
+ -->
+ <attribute name="DefaultCacheResolution">60</attribute>
+ <!-- DeepCopySubjectMode: This set the copy mode of subjects done by the
+ security managers to be deep copies that makes copies of the subject
+ principals and credentials if they are cloneable. It should be set to
+ true if subject include mutable content that can be corrupted when
+ multiple threads have the same identity and cache flushes/logout clearing
+ the subject in one thread results in subject references affecting other
+ threads.
+ -->
+ <attribute name="DeepCopySubjectMode">false</attribute>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Transactions -->
+ <!-- ==================================================================== -->
+
+ <!-- The configurable Xid factory. For use with Oracle, set pad to true -->
+ <mbean code="org.jboss.tm.XidFactory"
+ name="jboss:service=XidFactory">
+ <!--attribute name="Pad">true</attribute-->
+ </mbean>
+
+ <!--
+ | The fast in-memory transaction manager.
+ | Deprecated in JBossAS v4.2. Use JBossTS JTA instead.
+ - ->
+ <mbean code="org.jboss.tm.TransactionManagerService"
+ name="jboss:service=TransactionManager"
+ xmbean-dd="resource:xmdesc/TransactionManagerService-xmbean.xml">
+ <attribute name="TransactionTimeout">300</attribute>
+ <!- - set to false to disable transaction demarcation over IIOP - ->
+ <attribute name="GlobalIdsEnabled">true</attribute>
+ <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
+
+ <!- - Transaction Integrity Checking - ->
+ <!- - Force a rollback if another thread is associated with the transaction at commit - ->
+ <!- - <depends optional-attribute-name="TransactionIntegrityFactory"
+ proxy-type="org.jboss.tm.integrity.TransactionIntegrityFactory">
+ <mbean code="org.jboss.tm.integrity.FailIncompleteTransaction"
+ name="jboss:service=TransactionManager,plugin=TransactionIntegrity"/>
+ </depends> - ->
+ </mbean>
+ -->
+
+ <!-- JBoss Transactions JTA -->
+ <mbean code="com.arjuna.ats.jbossatx.jta.TransactionManagerService"
+ name="jboss:service=TransactionManager">
+ <attribute name="TransactionTimeout">300</attribute>
+ <attribute name="ObjectStoreDir">${jboss.server.data.dir}/tx-object-store</attribute>
+ </mbean>
+
+ <!--
+ | UserTransaction support.
+ -->
+ <mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService"
+ name="jboss:service=ClientUserTransaction"
+ xmbean-dd="resource:xmdesc/ClientUserTransaction-xmbean.xml">
+ <depends>
+ <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
+ name="jboss:service=proxyFactory,target=ClientUserTransactionFactory">
+ <attribute name="InvokerName">jboss:service=invoker,type=jrmp</attribute>
+ <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute>
+ <attribute name="JndiName">UserTransactionSessionFactory</attribute>
+ <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory</attribute>
+ <attribute name="ClientInterceptors">
+ <interceptors>
+ <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
+ <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
+ </interceptors>
+ </attribute>
+ <depends>jboss:service=invoker,type=jrmp</depends>
+ </mbean>
+ </depends>
+ <depends optional-attribute-name="TxProxyName">
+ <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
+ name="jboss:service=proxyFactory,target=ClientUserTransaction">
+ <attribute name="InvokerName">jboss:service=invoker,type=jrmp</attribute>
+ <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute>
+ <attribute name="JndiName"></attribute>
+ <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSession</attribute>
+ <attribute name="ClientInterceptors">
+ <interceptors>
+ <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
+ <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
+ </interceptors>
+ </attribute>
+ <depends>jboss:service=invoker,type=jrmp</depends>
+ </mbean>
+ </depends>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Invokers to the JMX node -->
+ <!-- ==================================================================== -->
+
+ <!-- Unified invoker (based on remoting) -->
+ <mbean code="org.jboss.invocation.unified.server.UnifiedInvoker"
+ name="jboss:service=invoker,type=unified">
+ <!-- To turn on strict RMI exception propagation uncomment block below -->
+ <!-- This will cause the UnifiedInvokerProxy to wrap RemoteExceptions -->
+ <!-- within a ServerException, otherwise will throw root exception -->
+ <!-- (not RemoteException) -->
+ <!-- <attribute name="StrictRMIException">true</attribute> -->
+ <depends>jboss:service=TransactionManager</depends>
+ <depends>jboss.remoting:service=Connector,transport=socket</depends>
+ </mbean>
+
+ <!-- RMI/JRMP invoker -->
+ <mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
+ name="jboss:service=invoker,type=jrmp">
+ <attribute name="RMIObjectPort">4444</attribute>
+ <attribute name="ServerAddress">${jboss.bind.address}</attribute>
+ <!--
+ <attribute name="RMIClientSocketFactory">custom</attribute>
+ <attribute name="RMIServerSocketFactory">custom</attribute>
+ <attribute name="RMIServerSocketAddr">custom</attribute>
+ <attribute name="SecurityDomain">ssl-domain-name</attribute>
+ -->
+ <depends>jboss:service=TransactionManager</depends>
+ </mbean>
+
+ <mbean code="org.jboss.invocation.local.LocalInvoker"
+ name="jboss:service=invoker,type=local">
+
+ <depends>jboss:service=TransactionManager</depends>
+ </mbean>
+
+ <mbean code="org.jboss.invocation.pooled.server.PooledInvoker"
+ name="jboss:service=invoker,type=pooled">
+ <attribute name="NumAcceptThreads">1</attribute>
+ <attribute name="MaxPoolSize">300</attribute>
+ <attribute name="ClientMaxPoolSize">300</attribute>
+ <attribute name="SocketTimeout">60000</attribute>
+ <attribute name="ServerBindAddress">${jboss.bind.address}</attribute>
+ <attribute name="ServerBindPort">4445</attribute>
+ <attribute name="ClientConnectAddress">${jboss.bind.address}</attribute>
+ <attribute name="ClientConnectPort">0</attribute>
+ <attribute name="ClientRetryCount">1</attribute>
+ <attribute name="EnableTcpNoDelay">false</attribute>
+
+ <!-- Customized socket factory attributes
+ <attribute name="ClientSocketFactoryName">custom.client.factory</attribute>
+ <attribute name="ServerSocketFactoryName">custom.server.factory</attribute>
+ <attribute name="SslDomain">java:/jaas/pooledInvoker</attribute>
+ -->
+ <depends optional-attribute-name="TransactionManagerService">jboss:service=TransactionManager</depends>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- Remoting services -->
+ <!-- ==================================================================== -->
+
+ <!-- For detailed description of all these configuration attributes, please see the -->
+ <!-- JBoss Remoting User's Guide or wiki (http://labs.jboss.com/portal/jbossremoting/docs/guide/index.html) -->
+
+ <!-- The NetworkRegistry contains all the local and remote -->
+ <!-- servers that it recognizes. The remote ones registered -->
+ <!-- are dependant on the detectors running and which domains -->
+ <!-- they are configured to identify. -->
+ <mbean code="org.jboss.remoting.network.NetworkRegistry"
+ name="jboss.remoting:service=NetworkRegistry"/>
+
+ <!-- The Connector is the core component of the remoting server service. -->
+ <!-- It binds the remoting invoker (transport protocol, callback configuration, -->
+ <!-- data marshalling, etc.) with the invocation handlers. -->
+ <mbean code="org.jboss.remoting.transport.Connector"
+ name="jboss.remoting:service=Connector,transport=socket"
+ display-name="Socket transport Connector">
+
+ <!-- Can either just specify the InvokerLocator attribute and not the invoker element in the -->
+ <!-- Configuration attribute, or do the full invoker configuration in the in invoker element -->
+ <!-- of the Configuration attribute. -->
+
+ <!-- Remember that if you do use more than one param on the uri, will have to include as a CDATA, -->
+ <!-- otherwise, parser will complain. -->
+ <!-- <attribute name="InvokerLocator"><![CDATA[socket://${jboss.bind.address}:4446/?datatype=invocation]]></attribute> -->
+
+ <attribute name="Configuration">
+ <!-- Using the following <invoker> element instead of the InvokerLocator above because specific attributes needed. -->
+ <!-- If wanted to use any of the parameters below, can just add them as parameters to the url above if wanted use the InvokerLocator attribute. -->
+ <config>
+ <!-- Other than transport type and handler, none of these configurations are required (will just use defaults). -->
+ <invoker transport="socket">
+ <attribute name="dataType" isParam="true">invocation</attribute>
+ <attribute name="marshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationMarshaller</attribute>
+ <attribute name="unmarshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationUnMarshaller</attribute>
+ <!-- This will be port on which the marshall loader port runs on. -->
+ <!-- <attribute name="loaderport" isParam="true">4447</attribute> -->
+ <!-- The following are specific to socket invoker -->
+ <!-- <attribute name="numAcceptThreads">1</attribute>-->
+ <!-- <attribute name="maxPoolSize">303</attribute>-->
+ <!-- <attribute name="clientMaxPoolSize" isParam="true">304</attribute>-->
+ <attribute name="socketTimeout" isParam="true">600000</attribute>
+ <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
+ <attribute name="serverBindPort">4446</attribute>
+ <!-- <attribute name="clientConnectAddress">216.23.33.2</attribute> -->
+ <!-- <attribute name="clientConnectPort">7777</attribute> -->
+ <attribute name="enableTcpNoDelay" isParam="true">true</attribute>
+ <!-- <attribute name="backlog">200</attribute>-->
+ <!-- The following is for callback configuration and is independant of invoker type -->
+ <!-- <attribute name="callbackMemCeiling">30</attribute>-->
+ <!-- indicates callback store by fully qualified class name -->
+ <!-- <attribute name="callbackStore">org.jboss.remoting.CallbackStore</attribute>-->
+ <!-- indicates callback store by object name -->
+ <!-- <attribute name="callbackStore">jboss.remoting:service=CallbackStore,type=Serializable</attribute> -->
+ <!-- config params for callback store. if were declaring callback store via object name, -->
+ <!-- could have specified these config params there. -->
+ <!-- StoreFilePath indicates to which directory to write the callback objects. -->
+ <!-- The default value is the property value of 'jboss.server.data.dir' and if this is not set, -->
+ <!-- then will be 'data'. Will then append 'remoting' and the callback client's session id. -->
+ <!-- An example would be 'data\remoting\5c4o05l-9jijyx-e5b6xyph-1-e5b6xyph-2'. -->
+ <!-- <attribute name="StoreFilePath">callback</attribute>-->
+ <!-- StoreFileSuffix indicates the file suffix to use for the callback objects written to disk. -->
+ <!-- The default value for file suffix is 'ser'. -->
+ <!-- <attribute name="StoreFileSuffix">cst</attribute>-->
+ </invoker>
+
+ <!-- At least one handler is required by the connector. If have more than one, must decalre -->
+ <!-- different subsystem values. Otherwise, all invocations will be routed to the only one -->
+ <!-- that is declared. -->
+ <handlers>
+ <!-- can also specify handler by fully qualified classname -->
+ <handler subsystem="invoker">jboss:service=invoker,type=unified</handler>
+ </handlers>
+ </config>
+ </attribute>
+ <depends>jboss.remoting:service=NetworkRegistry</depends>
+ </mbean>
+
+
+ <!-- <mbean code="org.jboss.remoting.detection.jndi.JNDIDetector"-->
+ <!-- name="jboss.remoting:service=Detector,transport=jndi">-->
+ <!-- host to which the detector will connect to for the JNDI server. -->
+ <!-- <attribute name="Host">localhost</attribute>-->
+ <!-- port to which detector will connect to for the JNDI server. -->
+ <!-- <attribute name="Port">5555</attribute>-->
+ <!-- context factory string used when connecting to the JNDI server. -->
+ <!-- The default is org.jnp.interfaces.NamingContextFactory. -->
+ <!-- <attribute name="ContextFactory">org.acme.NamingContextFactory</attribute> -->
+ <!-- url package string to use when connecting to the JNDI server. -->
+ <!-- The default is org.jboss.naming:org.jnp.interfaces. -->
+ <!-- <attribute name="URLPackage">org.acme.naming</attribute> -->
+ <!-- Sets the number of detection iterations before manually pinging -->
+ <!-- remote server to make sure still alive. This is needed since remote server -->
+ <!-- could crash and yet still have an entry in the JNDI server, -->
+ <!-- thus making it appear that it is still there. The default value is 5. -->
+ <!-- <attribute name="CleanDetectionNumber">20</attribute>-->
+
+ <!-- Specifies the domains in which the detector will recognize -->
+ <!-- detections. If servers are not configured to be in these -->
+ <!-- domains, they will not be added to NetworkRegistry. -->
+ <!-- <attribute name="Configuration">-->
+ <!-- <domains>-->
+ <!-- <domain>roxanne</domain>-->
+ <!-- <domain>sparky</domain>-->
+ <!-- </domains>-->
+ <!-- </attribute>-->
+ <!-- </mbean>-->
+
+
+ <!-- ==================================================================== -->
+ <!-- Monitoring and Management -->
+ <!-- ==================================================================== -->
+
+ <!-- Uncomment to enable JMX monitoring of the bean cache
+ <mbean code="org.jboss.monitor.BeanCacheMonitor"
+ name="jboss.monitor:name=BeanCacheMonitor"/>
+ -->
+
+ <!-- Uncomment to enable JMX monitoring of the entity bean locking
+ <mbean code="org.jboss.monitor.EntityLockMonitor"
+ name="jboss.monitor:name=EntityLockMonitor"/>
+ -->
+
+ <!-- ==================================================================== -->
+ <!-- An MBean that is a registry for JDBC type-mapping metadata -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary"
+ name="jboss.jdbc:service=metadata"/>
+
+ <!-- ==================================================================== -->
+ <!-- Deployment Scanning -->
+ <!-- ==================================================================== -->
+
+ <!-- An mbean for hot deployment/undeployment of archives.
+ -->
+ <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
+ name="jboss.deployment:type=DeploymentScanner,flavor=URL">
+
+ <!-- Uncomment (and comment/remove version below) to enable usage of the
+ DeploymentCache
+ <depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache</depends>
+ -->
+ <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>
+
+ <!-- The URLComparator can be used to specify a deployment ordering
+ for deployments found in a scanned directory. The class specified
+ must be an implementation of java.util.Comparator, it must be able
+ to compare two URL objects, and it must have a no-arg constructor.
+ Two deployment comparators are shipped with JBoss:
+ - org.jboss.deployment.DeploymentSorter
+ Sorts by file extension, as follows:
+ "sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip",
+ "*"
+ - org.jboss.deployment.scanner.PrefixDeploymentSorter
+ If the name portion of the url begins with 1 or more digits, those
+ digits are converted to an int (ignoring leading zeroes), and
+ files are deployed in that order. Files that do not start with
+ any digits will be deployed first, and they will be sorted by
+ extension as above with DeploymentSorter.
+ -->
+ <attribute name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute>
+
+ <!--
+ <attribute name="URLComparator">org.jboss.deployment.scanner.PrefixDeploymentSorter</attribute>
+ -->
+
+ <!-- The FilterInstance specifies a URLLister.URLFilter for scanned
+ directories. This DeploymentFilter is initialized with the given
+ prefixes, suffixes and matches that define which URLs should be
+ ignored.
+ -->
+ <attribute name="FilterInstance"
+ attributeClass="org.jboss.deployment.scanner.DeploymentFilter"
+ serialDataType="javaBean">
+ <!-- Files starting with theses strings are ignored -->
+ <property name="prefixes">#,%,\,,.,_$</property>
+ <!-- Files ending with theses strings are ignored -->
+ <property name="suffixes">#,$,%,~,\,v,.BAK,.bak,.old,.orig,.tmp,.rej,.sh</property>
+ <!-- Files matching with theses strings are ignored -->
+ <property name="matches">.make.state,.nse_depinfo,CVS,CVS.admin,RCS,RCSLOG,SCCS,TAGS,core,tags</property>
+ </attribute>
+
+ <!-- Frequency in milliseconds to rescan the URLs for changes -->
+ <attribute name="ScanPeriod">5000</attribute>
+
+ <!-- A flag to disable the scans -->
+ <attribute name="ScanEnabled">true</attribute>
+
+ <!-- URLs are comma separated and resolve relative to the server home URL
+ unless the given path is absolute. If the URL ends in "/" it is
+ considered a collection and scanned, otherwise it is simply deployed;
+ this follows RFC2518 convention and allows discrimination between
+ collections and directories that are simply unpacked archives.
+
+ URLs may be local (file:) or remote (http:). Scanning is supported
+ for remote URLs but unpacked deployment units are not.
+
+ Example URLs:
+ deploy/
+ scans ${jboss.server.url}/deploy/, which is local or remote
+ depending on the URL used to boot the server
+ ${jboss.server.home}/deploy/
+ scans ${jboss.server.home)/deploy, which is always local
+ file:/var/opt/myapp.ear
+ deploy myapp.ear from a local location
+ file:/var/opt/apps/
+ scans the specified directory
+ http://www.test.com/netboot/myapp.ear
+ deploys myapp.ear from a remote location
+ http://www.test.com/netboot/apps/
+ scans the specified WebDAV location
+ -->
+ <attribute name="URLs">
+ deploy/
+ </attribute>
+
+ <!-- Indicates if the scanner should recursively scan directories that
+ contain no "." in their names. This can be used to group applications
+ and services that must be deployed and that have the same
+ logical function in the same directory i.e.
+ deploy/JMX/
+ deploy/JMS/
+ ...
+ -->
+ <attribute name="RecursiveSearch">True</attribute>
+
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jbossjta-properties.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jbossjta-properties.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jbossjta-properties.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,228 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<transaction-service>
+ <properties depends="common" name="arjuna">
+ <!--
+ Transaction Reaper Timeout (default is 120000 microseconds).
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.coordinator.txReaperTimeout" value="120000"/>
+ <!--
+ Transaction Reaper Mode, can be: NORMAL or DYNAMIC (default is NORMAL).
+ -->
+ <property name="com.arjuna.ats.arjuna.coordinator.txReaperMode" value="NORMAL"/>
+ <!--
+ (default is NO)
+ -->
+ <property name="com.arjuna.ats.arjuna.coordinator.asyncCommit" value="NO"/>
+ <!--
+ (default is NO)
+ -->
+ <property name="com.arjuna.ats.arjuna.coordinator.asyncPrepare" value="NO"/>
+ <!--
+ (default is YES)
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.coordinator.commitOnePhase" value="YES"/>
+ <!--
+ (default is defaultStore)
+ -->
+ <property name="com.arjuna.ats.arjuna.objectstore.localOSRoot" value="defaultStore"/>
+ <!--
+ default is under user.home - must be writeable!)
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.objectstore.objectStoreDir" value="PutObjectStoreDirHere"/>
+ <!--
+ (default is ON)
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.objectstore.objectStoreSync" value="ON"/>
+ <!--
+ (default is ShadowNoFileLockStore)
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.objectstore.objectStoreType" value="ShadowNoFileLockStore"/>
+ <!--
+ (default is 255)
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.objectstore.hashedDirectories" value="255"/>
+ <!--
+ (default is ON)
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.objectstore.transactionSync" value="ON"/>
+ <!--
+ (Must be unique across all Arjuna instances.)
+ -->
+ <property name="com.arjuna.ats.arjuna.xa.nodeIdentifier" value="1"/>
+ <!-- property
+ name="com.arjuna.ats.arjuna.coordinator.actionStore"
+ value="HashedActionStore"
+ value="JDBCActionStore"
+ -->
+ <!-- property
+ name="com.arjuna.ats.arjuna.objectstore.jdbcTxDbAccess"
+ value="JDBCAccess"
+ -->
+ <!-- property
+ name="com.arjuna.ats.arjuna.objectstore.objectStoreType"
+ value="ShadowNoFileLockStore"
+ value="JDBCStore"
+ -->
+ <!-- property
+ name="com.arjuna.ats.arjuna.objectstore.jdbcUserDbAccess"
+ value="JDBCAccess"
+ -->
+ <!-- property
+ name="com.arjuna.ats.arjuna.objectstore.jdbcPoolSizeInitial"
+ value="1"
+ -->
+ <!-- property
+ name="com.arjuna.ats.arjuna.objectstore.jdbcPoolSizeMaximum"
+ value="1"
+ -->
+ <!-- property
+ name="com.arjuna.ats.arjuna.objectstore.jdbcPoolPutConnections"
+ value="false"
+ -->
+ <!-- property
+ name="com.arjuna.ats.arjuna.internal.arjuna.objectstore.cacheStore.size"
+ value=""
+ -->
+ <!-- property
+ name="com.arjuna.ats.arjuna.internal.arjuna.objectstore.cacheStore.period"
+ value=""
+ -->
+ <!--
+ The location for creating temporary files, e.g., Uids.
+ Default is under user.home.
+ IMPORTANT: make sure the directory is lockable, e.g., /tmp on Unix
+ may not be!
+ -->
+ <!--
+ <property
+ name="com.arjuna.ats.arjuna.common.varDir"
+ value="var"/>
+ -->
+ </properties>
+ <properties name="common">
+ <!-- CLF 2.0 properties -->
+ <property name="com.arjuna.common.util.logging.DebugLevel"
+ type="System" value="0x00000000"/>
+ <property name="com.arjuna.common.util.logging.FacilityLevel"
+ type="System" value="0xffffffff"/>
+ <property name="com.arjuna.common.util.logging.VisibilityLevel"
+ type="System" value="0xffffffff"/>
+ <property name="com.arjuna.common.util.logger" type="System" value="log4j"/>
+ </properties>
+ <properties depends="arjuna" name="txoj">
+ <!--
+ (default is LockStore of installation - must be writeable!)
+ -->
+ <!--
+ <property
+ name="com.arjuna.ats.txoj.lockstore.lockStoreDir"
+ value="LockStore"/>
+ -->
+ <!--
+ (default is BasicLockStore)
+ -->
+ <property name="com.arjuna.ats.txoj.lockstore.lockStoreType" value="BasicLockStore"/>
+ <!--
+ (default is NO)
+ -->
+ <property name="com.arjuna.ats.txoj.lockstore.multipleLockStore" value="NO"/>
+ <!--
+ (default is YES)
+ -->
+ <property name="com.arjuna.ats.txoj.lockstore.singleLockStore" value="YES"/>
+ <!--
+ (default is YES)
+ -->
+ <property
+ name="com.arjuna.ats.txoj.lockstore.allowNestedLocking" value="YES"/>
+ </properties>
+ <properties depends="arjuna" name="jta">
+ <!--
+ Support subtransactions in the JTA layer?
+ Default is NO.
+ -->
+ <property name="com.arjuna.ats.jta.supportSubtransactions" value="NO"/>
+ <property name="com.arjuna.ats.jta.jtaTMImplementation" value="com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionManagerImple"/>
+ <!--
+ com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple
+ -->
+ <property name="com.arjuna.ats.jta.jtaUTImplementation" value="com.arjuna.ats.internal.jta.transaction.arjunacore.UserTransactionImple"/>
+ <!--
+ com.arjuna.ats.internal.jta.transaction.jts.UserTransactionImple
+ -->
+ </properties>
+ <properties depends="arjuna,txoj,jta" name="recoverymanager">
+ <!--
+ Properties used only by the RecoveryManager.
+ -->
+ <!--
+ Periodic recovery settings.
+ Time values in this section are in seconds.
+ -->
+ <!--
+ Interval in seconds between initiating the periodic recovery modules.
+ Default is 120 seconds.
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.recovery.periodicRecoveryPeriod" value="120"/>
+ <!--
+ Interval in seconds between first and second pass of periodic recovery.
+ Default is 10 seconds.
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.recovery.recoveryBackoffPeriod" value="10"/>
+ <!--
+ Periodic recovery modules to use. Invoked in sort-order of names.
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.recovery.recoveryExtension1" value="com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule"/>
+ <property
+ name="com.arjuna.ats.arjuna.recovery.recoveryExtension2" value="com.arjuna.ats.internal.txoj.recovery.TORecoveryModule"/>
+ <property
+ name="com.arjuna.ats.arjuna.recovery.recoveryExtension3" value="com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule"/>
+ <!--
+ Expired entry removal
+ -->
+ <!--
+ Expiry scanners to use (order of invocation is random).
+ Names must begin with "com.arjuna.ats.arjuna.recovery.expiryScanner"
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.recovery.expiryScannerTransactionStatusManager" value="com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner"/>
+ <!--
+ Interval, in hours, between running the expiry scanners.
+ This can be quite long. The absolute value determines the interval -
+ if the value is negative, the scan will NOT be run until after one
+ interval has elapsed. If positive the first scan will be immediately
+ after startup. Zero will prevent any scanning.
+ Default = 12 = run immediately, then every 12 hours.
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.recovery.expiryScanInterval" value="12"/>
+ <!--
+ Age, in hours, for removal of transaction status manager item.
+ This should be longer than any ts-using process will remain running.
+ Zero = Never removed. Default is 12.
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.recovery.transactionStatusManagerExpiryTime" value="12"/>
+ <!--
+ Use this to fix the port on which the TransactionStatusManager listens,
+ The default behaviour is to use any free port.
+ -->
+ <property
+ name="com.arjuna.ats.arjuna.recovery.transactionStatusManagerPort" value="0"/>
+ </properties>
+ <properties depends="jta" name="jdbc">
+ <!--
+ property name="com.arjuna.ats.jdbc.isolationLevel" value="TRANSACTION_SERIALIZABLE"/>
+ -->
+ </properties>
+</transaction-service>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jndi.properties
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jndi.properties (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/jndi.properties 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,4 @@
+# DO NOT EDIT THIS FILE UNLESS YOU KNOW WHAT YOU ARE DOING
+#
+java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
+java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/login-config.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/login-config.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/login-config.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,159 @@
+<?xml version='1.0'?>
+<!DOCTYPE policy PUBLIC
+ "-//JBoss//DTD JBOSS Security Config 3.0//EN"
+ "http://www.jboss.org/j2ee/dtd/security_config.dtd">
+
+<!-- The XML based JAAS login configuration read by the
+org.jboss.security.auth.login.XMLLoginConfig mbean. Add
+an application-policy element for each security domain.
+
+The outline of the application-policy is:
+<application-policy name="security-domain-name">
+ <authentication>
+ <login-module code="login.module1.class.name" flag="control_flag">
+ <module-option name = "option1-name">option1-value</module-option>
+ <module-option name = "option2-name">option2-value</module-option>
+ ...
+ </login-module>
+
+ <login-module code="login.module2.class.name" flag="control_flag">
+ ...
+ </login-module>
+ ...
+ </authentication>
+</application-policy>
+
+$Revision: 43749 $
+-->
+
+<policy>
+ <!-- Used by clients within the application server VM such as
+ mbeans and servlets that access EJBs.
+ -->
+ <application-policy name = "client-login">
+ <authentication>
+ <login-module code = "org.jboss.security.ClientLoginModule"
+ flag = "required">
+ <!-- Any existing security context will be restored on logout -->
+ <module-option name="restore-login-identity">true</module-option>
+ </login-module>
+ </authentication>
+ </application-policy>
+
+ <!-- Security domain for JBossMQ -->
+ <application-policy name = "jbossmq">
+ <authentication>
+ <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule"
+ flag = "required">
+ <module-option name = "unauthenticatedIdentity">guest</module-option>
+ <module-option name = "dsJndiName">java:/DefaultDS</module-option>
+ <module-option name = "principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option>
+ <module-option name = "rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option>
+ </login-module>
+ </authentication>
+ </application-policy>
+
+ <!-- Security domain for JBossMQ when using file-state-service.xml
+ <application-policy name = "jbossmq">
+ <authentication>
+ <login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"
+ flag = "required">
+ <module-option name = "unauthenticatedIdentity">guest</module-option>
+ <module-option name = "sm.objectname">jboss.mq:service=StateManager</module-option>
+ </login-module>
+ </authentication>
+ </application-policy>
+ -->
+
+ <!-- Security domains for testing new jca framework -->
+ <application-policy name = "HsqlDbRealm">
+ <authentication>
+ <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule"
+ flag = "required">
+ <module-option name = "principal">sa</module-option>
+ <module-option name = "userName">sa</module-option>
+ <module-option name = "password"></module-option>
+ <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=DefaultDS</module-option>
+ </login-module>
+ </authentication>
+ </application-policy>
+
+ <application-policy name = "JmsXARealm">
+ <authentication>
+ <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule"
+ flag = "required">
+ <module-option name = "principal">guest</module-option>
+ <module-option name = "userName">guest</module-option>
+ <module-option name = "password">guest</module-option>
+ <module-option name = "managedConnectionFactoryName">jboss.jca:service=TxCM,name=JmsXA</module-option>
+ </login-module>
+ </authentication>
+ </application-policy>
+
+ <!-- A template configuration for the jmx-console web application. This
+ defaults to the UsersRolesLoginModule the same as other and should be
+ changed to a stronger authentication mechanism as required.
+ -->
+ <application-policy name = "jmx-console">
+ <authentication>
+ <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
+ flag = "required">
+ <module-option name="usersProperties">props/jmx-console-users.properties</module-option>
+ <module-option name="rolesProperties">props/jmx-console-roles.properties</module-option>
+ </login-module>
+ </authentication>
+ </application-policy>
+
+ <!-- A template configuration for the web-console web application. This
+ defaults to the UsersRolesLoginModule the same as other and should be
+ changed to a stronger authentication mechanism as required.
+ -->
+ <application-policy name = "web-console">
+ <authentication>
+ <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
+ flag = "required">
+ <module-option name="usersProperties">web-console-users.properties</module-option>
+ <module-option name="rolesProperties">web-console-roles.properties</module-option>
+ </login-module>
+ </authentication>
+ </application-policy>
+
+ <!--
+ A template configuration for the JBossWS security domain.
+ This defaults to the UsersRolesLoginModule the same as other and should be
+ changed to a stronger authentication mechanism as required.
+ -->
+ <application-policy name="JBossWS">
+ <authentication>
+ <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
+ flag="required">
+ <module-option name="usersProperties">props/jbossws-users.properties</module-option>
+ <module-option name="rolesProperties">props/jbossws-roles.properties</module-option>
+ <module-option name="unauthenticatedIdentity">anonymous</module-option>
+ </login-module>
+ </authentication>
+ </application-policy>
+
+ <!-- The default login configuration used by any security domain that
+ does not have a application-policy entry with a matching name
+ -->
+ <application-policy name = "other">
+ <!-- A simple server login module, which can be used when the number
+ of users is relatively small. It uses two properties files:
+ users.properties, which holds users (key) and their password (value).
+ roles.properties, which holds users (key) and a comma-separated list of
+ their roles (value).
+ The unauthenticatedIdentity property defines the name of the principal
+ that will be used when a null username and password are presented as is
+ the case for an unuathenticated web client or MDB. If you want to
+ allow such users to be authenticated add the property, e.g.,
+ unauthenticatedIdentity="nobody"
+ -->
+ <authentication>
+ <login-module code = "org.jboss.security.auth.spi.UsersRolesLoginModule"
+ flag = "required" />
+ </authentication>
+ </application-policy>
+
+</policy>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jbossws-roles.properties
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jbossws-roles.properties (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jbossws-roles.properties 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,2 @@
+# A sample roles.properties file for use with the UsersRolesLoginModule
+kermit=friend
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jbossws-users.properties
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jbossws-users.properties (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jbossws-users.properties 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,2 @@
+# A sample users.properties file for use with the UsersRolesLoginModule
+kermit=thefrog
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jmx-console-roles.properties
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jmx-console-roles.properties (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jmx-console-roles.properties 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,2 @@
+# A sample roles.properties file for use with the UsersRolesLoginModule
+admin=JBossAdmin,HttpInvoker
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jmx-console-users.properties
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jmx-console-users.properties (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/props/jmx-console-users.properties 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,2 @@
+# A sample users.properties file for use with the UsersRolesLoginModule
+admin=admin
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/standardjboss.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/standardjboss.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/standardjboss.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1216 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!DOCTYPE jboss PUBLIC
+ "-//JBoss//DTD JBOSS 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">
+
+<!-- ===================================================================== -->
+<!-- Standard JBoss EJB Configurations -->
+<!-- ===================================================================== -->
+<!-- $Id: standardjboss.xml 62053 2007-04-03 21:05:33Z alex.loubyansky at jboss.com $ -->
+
+<jboss>
+ <!--
+ 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>
+
+ <invoker-proxy-bindings>
+
+ <invoker-proxy-binding>
+ <name>entity-unified-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=unified</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.EntityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ <list-entity>
+ <interceptor>org.jboss.proxy.ejb.ListEntityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </list-entity>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>clustered-entity-unified-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=unifiedha</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactoryHA</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.EntityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ <list-entity>
+ <interceptor>org.jboss.proxy.ejb.ListEntityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </list-entity>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>stateless-unified-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=unified</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>clustered-stateless-unified-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=unifiedha</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactoryHA</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>stateful-unified-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=unified</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.StatefulSessionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>clustered-stateful-unified-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=unifiedha</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactoryHA</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.StatefulSessionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>entity-rmi-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=jrmp</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.EntityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ <list-entity>
+ <interceptor>org.jboss.proxy.ejb.ListEntityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </list-entity>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>clustered-entity-rmi-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=jrmpha</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactoryHA</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.EntityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ <list-entity>
+ <interceptor>org.jboss.proxy.ejb.ListEntityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </list-entity>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>stateless-rmi-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=jrmp</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>clustered-stateless-rmi-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=jrmpha</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactoryHA</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>stateful-rmi-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=jrmp</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.StatefulSessionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>clustered-stateful-rmi-invoker</name>
+ <invoker-mbean>jboss:service=invoker,type=jrmpha</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.ProxyFactoryHA</proxy-factory>
+ <proxy-factory-config>
+ <client-interceptors>
+ <home>
+ <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </home>
+ <bean>
+ <interceptor>org.jboss.proxy.ejb.StatefulSessionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.ejb.SingleRetryInterceptor</interceptor>
+ <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
+ <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
+ </bean>
+ </client-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>message-driven-bean</name>
+ <invoker-mbean>default</invoker-mbean>
+ <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
+ <proxy-factory-config>
+ <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
+ <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
+ <CreateJBossMQDestination>true</CreateJBossMQDestination>
+ <!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
+ <MinimumSize>1</MinimumSize>
+ <MaximumSize>15</MaximumSize>
+ <KeepAliveMillis>30000</KeepAliveMillis>
+ <MaxMessages>1</MaxMessages>
+ <MDBConfig>
+ <ReconnectIntervalSec>10</ReconnectIntervalSec>
+ <DLQConfig>
+ <DestinationQueue>queue/DLQ</DestinationQueue>
+ <MaxTimesRedelivered>10</MaxTimesRedelivered>
+ <TimeToLive>0</TimeToLive>
+ </DLQConfig>
+ </MDBConfig>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <!-- Uncomment to use JMS message inflow from jmsra.rar
+ <invoker-proxy-binding>
+ <name>message-driven-bean</name>
+ <invoker-mbean>default</invoker-mbean>
+ <proxy-factory>org.jboss.ejb.plugins.inflow.JBossJMSMessageEndpointFactory</proxy-factory>
+ <proxy-factory-config>
+ <activation-config>
+ <activation-config-property>
+ <activation-config-property-name>providerAdapterJNDI</activation-config-property-name>
+ <activation-config-property-value>DefaultJMSProvider</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>minSession</activation-config-property-name>
+ <activation-config-property-value>1</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>maxSession</activation-config-property-name>
+ <activation-config-property-value>15</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>keepAlive</activation-config-property-name>
+ <activation-config-property-value>60000</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>maxMessages</activation-config-property-name>
+ <activation-config-property-value>1</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>reconnectInterval</activation-config-property-name>
+ <activation-config-property-value>10</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>useDLQ</activation-config-property-name>
+ <activation-config-property-value>true</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>DLQHandler</activation-config-property-name>
+ <activation-config-property-value>org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>DLQJNDIName</activation-config-property-name>
+ <activation-config-property-value>queue/DLQ</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>DLQMaxResent</activation-config-property-name>
+ <activation-config-property-value>10</activation-config-property-value>
+ </activation-config-property>
+ </activation-config>
+ <endpoint-interceptors>
+ <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.inflow.MessageEndpointInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
+ </endpoint-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+ -->
+
+ <invoker-proxy-binding>
+ <name>singleton-message-driven-bean</name>
+ <invoker-mbean>default</invoker-mbean>
+ <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
+ <proxy-factory-config>
+ <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
+ <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
+ <CreateJBossMQDestination>true</CreateJBossMQDestination>
+ <!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
+ <MinimumSize>1</MinimumSize>
+ <MaximumSize>1</MaximumSize>
+ <KeepAliveMillis>30000</KeepAliveMillis>
+ <MaxMessages>1</MaxMessages>
+ <MDBConfig>
+ <ReconnectIntervalSec>10</ReconnectIntervalSec>
+ <DLQConfig>
+ <DestinationQueue>queue/DLQ</DestinationQueue>
+ <MaxTimesRedelivered>10</MaxTimesRedelivered>
+ <TimeToLive>0</TimeToLive>
+ </DLQConfig>
+ </MDBConfig>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>message-inflow-driven-bean</name>
+ <invoker-mbean>default</invoker-mbean>
+ <proxy-factory>org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory</proxy-factory>
+ <proxy-factory-config>
+ <endpoint-interceptors>
+ <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.inflow.MessageEndpointInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
+ </endpoint-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>iiop</name>
+ <invoker-mbean>jboss:service=invoker,type=iiop</invoker-mbean>
+ <proxy-factory>org.jboss.proxy.ejb.IORFactory</proxy-factory>
+ <proxy-factory-config>
+ <web-class-loader>org.jboss.iiop.WebCL</web-class-loader>
+ <poa>per-servant</poa>
+ <register-ejbs-in-jnp-context>true</register-ejbs-in-jnp-context>
+ <jnp-context>iiop</jnp-context>
+ <interface-repository-supported>false</interface-repository-supported>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+
+ <invoker-proxy-binding>
+ <name>jms-message-inflow-driven-bean</name>
+ <invoker-mbean>default</invoker-mbean>
+ <proxy-factory>org.jboss.ejb.plugins.inflow.JBossJMSMessageEndpointFactory</proxy-factory>
+ <proxy-factory-config>
+ <activation-config>
+ <activation-config-property>
+ <activation-config-property-name>providerAdapterJNDI</activation-config-property-name>
+ <activation-config-property-value>DefaultJMSProvider</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>minSession</activation-config-property-name>
+ <activation-config-property-value>1</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>maxSession</activation-config-property-name>
+ <activation-config-property-value>15</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>keepAlive</activation-config-property-name>
+ <activation-config-property-value>60000</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>maxMessages</activation-config-property-name>
+ <activation-config-property-value>1</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>reconnectInterval</activation-config-property-name>
+ <activation-config-property-value>10</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>useDLQ</activation-config-property-name>
+ <activation-config-property-value>true</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>DLQHandler</activation-config-property-name>
+ <activation-config-property-value>org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>DLQJNDIName</activation-config-property-name>
+ <activation-config-property-value>queue/DLQ</activation-config-property-value>
+ </activation-config-property>
+ <activation-config-property>
+ <activation-config-property-name>DLQMaxResent</activation-config-property-name>
+ <activation-config-property-value>10</activation-config-property-value>
+ </activation-config-property>
+ </activation-config>
+ <endpoint-interceptors>
+ <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.inflow.MessageEndpointInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
+ <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
+ </endpoint-interceptors>
+ </proxy-factory-config>
+ </invoker-proxy-binding>
+ </invoker-proxy-bindings>
+
+ <container-configurations>
+
+ <container-configuration>
+ <container-name>Standard CMP 2.x EntityBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>entity-unified-invoker</invoker-proxy-binding-name>
+ <sync-on-commit-only>false</sync-on-commit-only>
+ <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
+ <call-ejb-store-on-clean>true</call-ejb-store-on-clean>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntitySynchronizationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
+ <instance-cache>org.jboss.ejb.plugins.InvalidableEntityInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager>
+ <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
+ <container-cache-conf>
+ <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
+ <cache-policy-conf>
+ <min-capacity>50</min-capacity>
+ <max-capacity>1000000</max-capacity>
+ <overager-period>300</overager-period>
+ <max-bean-age>600</max-bean-age>
+ <resizer-period>400</resizer-period>
+ <max-cache-miss-period>60</max-cache-miss-period>
+ <min-cache-miss-period>1</min-cache-miss-period>
+ <cache-load-factor>0.75</cache-load-factor>
+ </cache-policy-conf>
+ </container-cache-conf>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <commit-option>B</commit-option>
+ </container-configuration>
+
+ <container-configuration>
+ <!--
+ | This is like standard IPT but with global (cross-transactional) row cache behind,
+ | i.e. no locking in EJB layer + global persistence data cache
+ -->
+ <container-name>cmp2.x jdbc2 pm</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>entity-unified-invoker</invoker-proxy-binding-name>
+ <sync-on-commit-only>false</sync-on-commit-only>
+ <insert-after-ejb-post-create>true</insert-after-ejb-post-create>
+ <call-ejb-store-on-clean>true</call-ejb-store-on-clean>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntitySynchronizationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.cmp.jdbc2.RelationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
+ <instance-cache>org.jboss.ejb.plugins.PerTxEntityInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc2.JDBCStoreManager2</persistence-manager>
+ <locking-policy>org.jboss.ejb.plugins.lock.NoLock</locking-policy>
+ <container-cache-conf>
+ <cache-policy-conf>
+ <min-capacity>500</min-capacity>
+ <max-capacity>10000</max-capacity>
+ <!-- uncomment to enable time-based eviction
+ <overager-period>300</overager-period>
+ <max-bean-age>600</max-bean-age> -->
+ </cache-policy-conf>
+ <cache-policy-conf-other>
+ <partitions>10</partitions>
+ <!-- uncomment to use JDBC java.sql.Statement.executeBatch()
+ <batch-commit-strategy/> -->
+ <!-- uncomment to enable cache invalidation <invalidable/> -->
+ </cache-policy-conf-other>
+ </container-cache-conf>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <commit-option>C</commit-option> <!-- don't change, irrelevant, use container-cache-conf -->
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Clustered CMP 2.x EntityBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>clustered-entity-unified-invoker</invoker-proxy-binding-name>
+ <sync-on-commit-only>false</sync-on-commit-only>
+ <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CleanShutdownInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntitySynchronizationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
+ <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager>
+ <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
+ <container-cache-conf>
+ <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
+ <cache-policy-conf>
+ <min-capacity>50</min-capacity>
+ <max-capacity>1000000</max-capacity>
+ <overager-period>300</overager-period>
+ <max-bean-age>600</max-bean-age>
+ <resizer-period>400</resizer-period>
+ <max-cache-miss-period>60</max-cache-miss-period>
+ <min-cache-miss-period>1</min-cache-miss-period>
+ <cache-load-factor>0.75</cache-load-factor>
+ </cache-policy-conf>
+ </container-cache-conf>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <commit-option>B</commit-option>
+ <cluster-config>
+ <partition-name>${jboss.partition.name:DefaultPartition}</partition-name>
+ </cluster-config>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Standard CMP 2.x EntityBean with cache invalidation</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>entity-unified-invoker</invoker-proxy-binding-name>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntitySynchronizationInterceptor</interceptor>
+ <interceptor>org.jboss.cache.invalidation.triggers.EntityBeanCacheBatchInvalidatorInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
+ <instance-cache>org.jboss.ejb.plugins.InvalidableEntityInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager>
+ <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
+ <container-cache-conf>
+ <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
+ <cache-policy-conf>
+ <min-capacity>50</min-capacity>
+ <max-capacity>1000000</max-capacity>
+ <overager-period>300</overager-period>
+ <max-bean-age>600</max-bean-age>
+ <resizer-period>400</resizer-period>
+ <max-cache-miss-period>60</max-cache-miss-period>
+ <min-cache-miss-period>1</min-cache-miss-period>
+ <cache-load-factor>0.75</cache-load-factor>
+ </cache-policy-conf>
+ </container-cache-conf>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <commit-option>A</commit-option>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Instance Per Transaction CMP 2.x EntityBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>entity-unified-invoker</invoker-proxy-binding-name>
+ <sync-on-commit-only>false</sync-on-commit-only>
+ <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntitySynchronizationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
+ <instance-cache>org.jboss.ejb.plugins.PerTxEntityInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager>
+ <locking-policy>org.jboss.ejb.plugins.lock.NoLock</locking-policy>
+ <container-cache-conf/>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <commit-option>C</commit-option>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Standard CMP EntityBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>entity-unified-invoker</invoker-proxy-binding-name>
+ <sync-on-commit-only>false</sync-on-commit-only>
+ <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntitySynchronizationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
+ <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager>
+ <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
+ <container-cache-conf>
+ <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
+ <cache-policy-conf>
+ <min-capacity>50</min-capacity>
+ <max-capacity>1000000</max-capacity>
+ <overager-period>300</overager-period>
+ <max-bean-age>600</max-bean-age>
+ <resizer-period>400</resizer-period>
+ <max-cache-miss-period>60</max-cache-miss-period>
+ <min-cache-miss-period>1</min-cache-miss-period>
+ <cache-load-factor>0.75</cache-load-factor>
+ </cache-policy-conf>
+ </container-cache-conf>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <commit-option>A</commit-option>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Clustered CMP EntityBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>clustered-entity-unified-invoker</invoker-proxy-binding-name>
+ <sync-on-commit-only>false</sync-on-commit-only>
+ <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CleanShutdownInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntitySynchronizationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
+ <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager>
+ <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
+ <container-cache-conf>
+ <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
+ <cache-policy-conf>
+ <min-capacity>50</min-capacity>
+ <max-capacity>1000000</max-capacity>
+ <overager-period>300</overager-period>
+ <max-bean-age>600</max-bean-age>
+ <resizer-period>400</resizer-period>
+ <max-cache-miss-period>60</max-cache-miss-period>
+ <min-cache-miss-period>1</min-cache-miss-period>
+ <cache-load-factor>0.75</cache-load-factor>
+ </cache-policy-conf>
+ </container-cache-conf>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <commit-option>A</commit-option>
+ <cluster-config>
+ <partition-name>${jboss.partition.name:DefaultPartition}</partition-name>
+ </cluster-config>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Instance Per Transaction CMP EntityBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>entity-unified-invoker</invoker-proxy-binding-name>
+ <sync-on-commit-only>false</sync-on-commit-only>
+ <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntitySynchronizationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
+ <instance-cache>org.jboss.ejb.plugins.PerTxEntityInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager>
+ <locking-policy>org.jboss.ejb.plugins.lock.NoLock</locking-policy>
+ <container-cache-conf/>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <commit-option>C</commit-option>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Standard Stateless SessionBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>stateless-unified-invoker</invoker-proxy-binding-name>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <!-- CMT -->
+ <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
+ <!-- BMT -->
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.StatelessSessionInstancePool</instance-pool>
+ <instance-cache></instance-cache>
+ <persistence-manager></persistence-manager>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Clustered Stateless SessionBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>clustered-stateless-unified-invoker</invoker-proxy-binding-name>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CleanShutdownInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <!-- CMT -->
+ <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
+ <!-- BMT -->
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.StatelessSessionInstancePool</instance-pool>
+ <instance-cache></instance-cache>
+ <persistence-manager></persistence-manager>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <cluster-config>
+ <partition-name>${jboss.partition.name:DefaultPartition}</partition-name>
+ </cluster-config>
+ </container-configuration>
+
+
+ <container-configuration>
+ <container-name>Standard Stateful SessionBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>stateful-unified-invoker</invoker-proxy-binding-name>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <!-- CMT -->
+ <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor</interceptor>
+ <!-- BMT -->
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ </container-interceptors>
+ <instance-cache>org.jboss.ejb.plugins.StatefulSessionInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager</persistence-manager>
+ <container-cache-conf>
+ <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-policy>
+ <cache-policy-conf>
+ <min-capacity>50</min-capacity>
+ <max-capacity>1000000</max-capacity>
+ <remover-period>1800</remover-period>
+ <max-bean-life>1800</max-bean-life>
+ <overager-period>300</overager-period>
+ <max-bean-age>600</max-bean-age>
+ <resizer-period>400</resizer-period>
+ <max-cache-miss-period>60</max-cache-miss-period>
+ <min-cache-miss-period>1</min-cache-miss-period>
+ <cache-load-factor>0.75</cache-load-factor>
+ </cache-policy-conf>
+ </container-cache-conf>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Clustered Stateful SessionBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>clustered-stateful-unified-invoker</invoker-proxy-binding-name>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CleanShutdownInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <!-- CMT -->
+ <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor</interceptor>
+ <!-- BMT -->
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.StatefulHASessionSynchronisationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-cache>org.jboss.ejb.plugins.StatefulHASessionInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.StatefulHASessionPersistenceManager</persistence-manager>
+ <container-cache-conf>
+ <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-policy>
+ <cache-policy-conf>
+ <min-capacity>50</min-capacity>
+ <max-capacity>1000000</max-capacity>
+ <remover-period>1800</remover-period>
+ <max-bean-life>1800</max-bean-life>
+ <overager-period>300</overager-period>
+ <max-bean-age>600</max-bean-age>
+ <resizer-period>400</resizer-period>
+ <max-cache-miss-period>60</max-cache-miss-period>
+ <min-cache-miss-period>1</min-cache-miss-period>
+ <cache-load-factor>0.75</cache-load-factor>
+ </cache-policy-conf>
+ </container-cache-conf>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <cluster-config>
+ <partition-name>${jboss.partition.name:DefaultPartition}</partition-name>
+ </cluster-config>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Standard BMP EntityBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>entity-unified-invoker</invoker-proxy-binding-name>
+ <sync-on-commit-only>false</sync-on-commit-only>
+ <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntitySynchronizationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
+ <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.BMPPersistenceManager</persistence-manager>
+ <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
+ <container-cache-conf>
+ <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
+ <cache-policy-conf>
+ <min-capacity>50</min-capacity>
+ <max-capacity>1000000</max-capacity>
+ <overager-period>300</overager-period>
+ <max-bean-age>600</max-bean-age>
+ <resizer-period>400</resizer-period>
+ <max-cache-miss-period>60</max-cache-miss-period>
+ <min-cache-miss-period>1</min-cache-miss-period>
+ <cache-load-factor>0.75</cache-load-factor>
+ </cache-policy-conf>
+ </container-cache-conf>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <commit-option>A</commit-option>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Clustered BMP EntityBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>clustered-entity-unified-invoker</invoker-proxy-binding-name>
+ <sync-on-commit-only>false</sync-on-commit-only>
+ <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CleanShutdownInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntitySynchronizationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
+ <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.BMPPersistenceManager</persistence-manager>
+ <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
+ <container-cache-conf>
+ <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
+ <cache-policy-conf>
+ <min-capacity>50</min-capacity>
+ <max-capacity>1000000</max-capacity>
+ <overager-period>300</overager-period>
+ <max-bean-age>600</max-bean-age>
+ <resizer-period>400</resizer-period>
+ <max-cache-miss-period>60</max-cache-miss-period>
+ <min-cache-miss-period>1</min-cache-miss-period>
+ <cache-load-factor>0.75</cache-load-factor>
+ </cache-policy-conf>
+ </container-cache-conf>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <commit-option>A</commit-option>
+ <cluster-config>
+ <partition-name>${jboss.partition.name:DefaultPartition}</partition-name>
+ </cluster-config>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Instance Per Transaction BMP EntityBean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>entity-unified-invoker</invoker-proxy-binding-name>
+ <sync-on-commit-only>false</sync-on-commit-only>
+ <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor>org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityCreationInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityLockInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityInstanceInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntityReentranceInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.EntitySynchronizationInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
+ <instance-cache>org.jboss.ejb.plugins.PerTxEntityInstanceCache</instance-cache>
+ <persistence-manager>org.jboss.ejb.plugins.BMPPersistenceManager</persistence-manager>
+ <locking-policy>org.jboss.ejb.plugins.lock.NoLock</locking-policy>
+ <container-cache-conf/>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ <commit-option>C</commit-option>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Standard Message Driven Bean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>message-driven-bean</invoker-proxy-binding-name>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor>
+ <!-- CMT -->
+ <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
+ <!-- BMT -->
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool>
+ <instance-cache></instance-cache>
+ <persistence-manager></persistence-manager>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Singleton Message Driven Bean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>singleton-message-driven-bean</invoker-proxy-binding-name>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor>
+ <!-- CMT -->
+ <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
+ <!-- BMT -->
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool>
+ <instance-cache></instance-cache>
+ <persistence-manager></persistence-manager>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ </container-configuration>
+
+ <container-configuration>
+ <container-name>Standard Message Inflow Driven Bean</container-name>
+ <call-logging>false</call-logging>
+ <invoker-proxy-binding-name>message-inflow-driven-bean</invoker-proxy-binding-name>
+ <container-interceptors>
+ <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
+ <interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor>
+ <!-- CMT -->
+ <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
+ <!-- BMT -->
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor>
+ <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
+ <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
+ </container-interceptors>
+ <instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool>
+ <instance-cache></instance-cache>
+ <persistence-manager></persistence-manager>
+ <container-pool-conf>
+ <MaximumSize>100</MaximumSize>
+ </container-pool-conf>
+ </container-configuration>
+
+ </container-configurations>
+
+</jboss>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/standardjbosscmp-jdbc.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/standardjbosscmp-jdbc.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/standardjbosscmp-jdbc.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,3090 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE jbosscmp-jdbc PUBLIC
+ "-//JBoss//DTD JBOSSCMP-JDBC 4.0//EN"
+ "http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_4_0.dtd">
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- Standard JBossCMP-JDBC Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: standardjbosscmp-jdbc.xml 62388 2007-04-18 08:39:43Z alex.loubyansky at jboss.com $ -->
+
+<jbosscmp-jdbc>
+
+ <defaults>
+ <datasource>java:/DefaultDS</datasource>
+ <!-- optional since 4.0 <datasource-mapping>Hypersonic SQL</datasource-mapping> -->
+
+ <create-table>true</create-table>
+ <remove-table>false</remove-table>
+ <read-only>false</read-only>
+ <read-time-out>300000</read-time-out>
+ <row-locking>false</row-locking>
+ <pk-constraint>true</pk-constraint>
+ <fk-constraint>false</fk-constraint>
+ <preferred-relation-mapping>foreign-key</preferred-relation-mapping>
+ <read-ahead>
+ <strategy>on-load</strategy>
+ <page-size>1000</page-size>
+ <eager-load-group>*</eager-load-group>
+ </read-ahead>
+ <list-cache-max>1000</list-cache-max>
+ <clean-read-ahead-on-load>false</clean-read-ahead-on-load>
+
+ <unknown-pk>
+ <key-generator-factory>UUIDKeyGeneratorFactory</key-generator-factory>
+ <unknown-pk-class>java.lang.String</unknown-pk-class>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(32)</sql-type>
+ </unknown-pk>
+
+ <entity-command name="default"/>
+ <ql-compiler>org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler</ql-compiler>
+ <throw-runtime-exceptions>false</throw-runtime-exceptions>
+ </defaults>
+
+ <type-mappings>
+ <type-mapping>
+ <name>FirstSQL/J</name>
+ <row-locking-template/>
+ <pk-constraint-template>PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>substring(?1 FROM ?2 FOR ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>char_length(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>position(?1 IN ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>math.abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>math.sqrt(CAST(?1 AS DOUBLE))</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>TINYINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>TINYINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>BIGINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>REAL</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <!-- or <sql-type>VARCHAR(2147483500)</sql-type> -->
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>DECIMAL</jdbc-type>
+ <sql-type>DECIMAL</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <!-- FirstSQL/J only supports directly serializable objects for classes declared with CREATE CLASS -->
+ <jdbc-type>LONGVARBINARY</jdbc-type>
+ <sql-type>VARCHAR(2147483500)</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>Ingres</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 PRIMARY KEY (?3)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>TRUE</true-mapping>
+ <false-mapping>FALSE</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>concat(?1,?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>left(?1,?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>length(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>locate(?1,?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>sqrt(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <!-- change from bit to integer , 10.12.2002 heb -->
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>INT1</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>INTEGER4</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>FLOAT</jdbc-type>
+ <sql-type>FLOAT4</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>FLOAT8</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>FLOAT8</sql-type>
+ </mapping>
+<!--
+Mapping proposed by Computer Associates, but does not work with JBoss properly
+28.03.2003 hou
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <sql-type>DECIMAL(24,6)</sql-type>
+ </mapping>
+-->
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>LONG VARCHAR</sql-type>
+ </mapping>
+ </type-mapping>
+ <type-mapping>
+ <name>McKoi</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>TRUE</true-mapping>
+ <false-mapping>FALSE</false-mapping>
+
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>BOOLEAN</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>BIGINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>FLOAT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(64)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>JAVA_OBJECT</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>Firebird</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>31</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>SMALLINT default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>SMALLINT default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>NUMERIC(18,0) default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>FLOAT default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE PRECISION default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <!-- The small default length is due to the 128 byte max index key size -->
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(64)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>BLOB</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>InterBase</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>31</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>SMALLINT default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>SMALLINT default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>NUMERIC(18,0) default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>FLOAT default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE PRECISION default 0</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(64)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>VARCHAR(2000)</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>DB2</name>
+ <row-locking-template/>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>18</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>locate(CAST(?1 as VARCHAR(254)),
+ CAST(?2 as VaRCHAR(254)),?3)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <!-- DB2 does not appear to support columns of type "byte"
+ Regrettably, this means they'll be serialized.
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR(1) FOR BIT DATA</sql-type>
+ </mapping>
+ -->
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>BIGINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>REAL</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(254)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <!-- this one gives errors with DB2 V8.1
+ and at least the NET driver
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>BLOB(2000)</sql-type>
+ </mapping>
+ -->
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>VARBINARY</jdbc-type>
+ <sql-type>BLOB(2000)</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>Derby</name>
+ <row-locking-template/>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>18</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substr</function-name>
+ <function-sql>substr(?1, ?2, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>length(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>locate(?2, ?1, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>sqrt(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <sql-type>DECIMAL</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>BOOLEAN</sql-type>
+ </mapping>
+<!-- if someone knows the mapping for byte, please, let us know!
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+-->
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>BIGINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>REAL</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE PRECISION</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>BLOB</jdbc-type>
+ <sql-type>BLOB</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>Oracle9i</name>
+ <!--
+ | Make sure that you have the Oracle 9i version of classes12.jar
+ | or you will suffer
+ -->
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>30</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>substr(?1, ?2, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>length(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>instr(?2, ?1, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>sqrt(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>NUMBER(1)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>NUMBER(3)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <!-- <jdbc-type>SMALLINT</jdbc-type> this resulted in a ClassCastException -->
+ <sql-type>NUMBER(5)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>NUMBER(10)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>NUMBER(19)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>NUMBER(38,7)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>DECIMAL</jdbc-type>
+ <sql-type>NUMBER(38,15)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>NUMBER(38,15)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR2(255)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP(3)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP(9)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>BLOB</jdbc-type>
+ <sql-type>BLOB</sql-type>
+ <!--
+ | Change this from BLOB to RAW(n) if you know your
+ | serialized object will be <= n bytes and n <= 2000
+ -->
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>Oracle8</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>30</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>substr(?1, ?2, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>length(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>instr(?2, ?1, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>sqrt(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>NUMBER(1)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <sql-type>NUMBER(3)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <sql-type>NUMBER(5)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>NUMBER(10)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>NUMBER(19)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>NUMBER(38,7)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>DECIMAL</jdbc-type>
+ <sql-type>NUMBER(38,15)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>NUMBER(38,15)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR2(255)</sql-type>
+ </mapping>
+ <mapping>
+ <!--
+ | Note that you lose granularity here
+ | Use a numeric type and store milliseconds if you really need it
+ -->
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <!--
+ | Note that you lose granularity here
+ | Use a numeric type and store milliseconds if you really need it
+ -->
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>BLOB</jdbc-type>
+ <sql-type>BLOB</sql-type>
+ <!--
+ | Change this from BLOB to RAW(n) if you know your
+ | serialized object will be <= n bytes and n <= 2000
+ -->
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>Oracle7</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>30</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>substr(?1, ?2, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>length(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>instr(?2, ?1, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>sqrt(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>NUMBER(1)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <sql-type>NUMBER(3)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <sql-type>NUMBER(5)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>NUMBER(10)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>NUMBER(19)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>NUMBER(38,7)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>NUMBER(38,15)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR2(255)</sql-type>
+ </mapping>
+ <mapping>
+ <!--
+ | Note that you lose granularity here
+ | Use a numeric type and store milliseconds if you really need it
+ -->
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <!--
+ | Note that you lose granularity here
+ | Use a numeric type and store milliseconds if you really need it
+ -->
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>LONGVARBINARY</jdbc-type>
+ <sql-type>LONG RAW</sql-type>
+ <!--
+ | Change this from LONG RAW to RAW(n) if you know your
+ | serialized object will be <= n bytes and n <= 2000
+ | Oracle only permits one LONG type per table
+ -->
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>Sybase</name>
+ <row-locking-template/>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>30</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>char_length(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>BIT</sql-type>
+ </mapping>
+ <!-- Current Sybase JDBC drivers (jConnect 5.2) don't support
+ byte or short. Unfortunately they'll be serialized.
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>TINYINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ -->
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <sql-type>NUMERIC(38,0)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>REAL</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE PRECISION</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(255)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>SMALLDATETIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>IMAGE</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>PostgreSQL</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <auto-increment-template>?1</auto-increment-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>TRUE</true-mapping>
+ <false-mapping>FALSE</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>substring(?1 FROM ?2 FOR ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>length(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>(CASE position(?1 in substring(?2 from ?3)) WHEN 0 THEN 0 ELSE position(?1 in substring(?2 from ?3)) + ?3 - 1 END)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>sqrt(CAST(?1 AS double precision))</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>BOOLEAN</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>INT2</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>INT2</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INT4</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>INT8</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>FLOAT</jdbc-type>
+ <sql-type>FLOAT(7)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>FLOAT8</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR(1)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>TEXT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP with time zone</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP with time zone</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <sql-type>NUMERIC</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>VARBINARY</jdbc-type>
+ <sql-type>BYTEA</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>PostgreSQL 8.0</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <auto-increment-template>?1</auto-increment-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>TRUE</true-mapping>
+ <false-mapping>FALSE</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>substring(?1 FROM ?2 FOR ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>length(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>(CASE position(?1 in substring(?2 from ?3)) WHEN 0 THEN 0 ELSE position(?1 in substring(?2 from ?3)) + ?3 - 1 END)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>sqrt(CAST(?1 AS double precision))</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BOOLEAN</jdbc-type>
+ <sql-type>BOOLEAN</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>INT2</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>INT2</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INT4</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>INT8</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>FLOAT</jdbc-type>
+ <sql-type>FLOAT(7)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>FLOAT8</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR(1)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>TEXT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <sql-type>NUMERIC</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>VARBINARY</jdbc-type>
+ <sql-type>BYTEA</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>PostgreSQL 7.2</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <auto-increment-template>?1</auto-increment-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>TRUE</true-mapping>
+ <false-mapping>FALSE</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>substring(?1 FROM ?2 FOR ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>length(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>(CASE position(?1 in substring(?2 from ?3)) WHEN 0 THEN 0 ELSE position(?1 in substring(?2 from ?3)) + ?3 - 1 END)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>sqrt(CAST(?1 AS double precision))</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>BOOLEAN</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>INT2</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>INT2</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INT4</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>INT8</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>FLOAT</jdbc-type>
+ <sql-type>FLOAT(7)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>FLOAT8</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR(1)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>TEXT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <sql-type>NUMERIC</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>VARBINARY</jdbc-type>
+ <sql-type>BYTEA</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>Hypersonic SQL</name>
+ <row-locking-template/>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <auto-increment-template>?1 IDENTITY</auto-increment-template>
+ <add-column-template>ALTER TABLE ?1 ADD COLUMN ?2 ?3</add-column-template>
+ <drop-column-template>ALTER TABLE ?1 DROP COLUMN ?2</drop-column-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>(1=1)</true-mapping>
+ <false-mapping>(1=0)</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 || ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>SUBSTRING(?1, ?2, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lcase(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>LENGTH(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>LOCATE(?1, ?2, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>ABS(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>SQRT(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>ucase(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>BIT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <!-- hsqldb only supports directly serializable objects for sql type OBJECT -->
+ <jdbc-type>VARBINARY</jdbc-type>
+ <sql-type>VARBINARY</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>REAL</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>BIGINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>DECIMAL</jdbc-type>
+ <sql-type>DECIMAL</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>PointBase</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>TRUE</true-mapping>
+ <false-mapping>FALSE</false-mapping>
+
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>position(?1 IN ?2)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>FLOAT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>FLOAT</jdbc-type>
+ <sql-type>FLOAT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>BOOLEAN</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>BLOB</jdbc-type>
+ <sql-type>BLOB</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>SOLID</name>
+ <row-locking-template/>
+ <pk-constraint-template>PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>TINYINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>BLOB</jdbc-type>
+ <sql-type>BLOB</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>BIT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>FLOAT</jdbc-type>
+ <sql-type>FLOAT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>BIGINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>mySQL</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <!-- does not work for compound keys <fk-constraint-template>ALTER TABLE ?1 ADD INDEX ind_?3 (?3), ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ -->
+ <fk-constraint-template>ALTER TABLE ?1 ADD INDEX (?3), ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <auto-increment-template>?1 auto_increment</auto-increment-template>
+ <alter-column-template>ALTER TABLE ?1 MODIFY ?2 ?3</alter-column-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>false</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>concat(?1, ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>substring(?1 FROM ?2 FOR ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>length(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>locate(?1, ?2, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>sqrt(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>FLOAT</jdbc-type>
+ <sql-type>FLOAT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>TINYINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>BLOB</jdbc-type>
+ <sql-type>LONGBLOB</sql-type>
+ <!--
+ | Change this from LONGBLOB to BLOB if you know your
+ | serialized object will be <= 2^16 bytes
+ -->
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ <!--
+ | This type is problematical because mysql does not have any
+ | date/time types that store milliseconds. You should avoid it.
+ -->
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>TINYINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>BIGINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(250) BINARY</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ <!--
+ | Note that you lose granularity here
+ | Use a numeric type and store milliseconds if you really need it
+ -->
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>MS SQLSERVER</name>
+ <row-locking-template>SELECT ?1 FROM ?2 with (updlock) WHERE ?3 ORDER BY ?4</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <auto-increment-template>?1 IDENTITY</auto-increment-template>
+ <alter-column-template>ALTER TABLE ?1 ALTER COLUMN ?2 ?3</alter-column-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 + ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>substring(?1, ?2, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>len(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>charindex(?1, ?2, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>sqrt(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>DECIMAL</jdbc-type>
+ <sql-type>DECIMAL(20)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>IMAGE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>TINYINT</sql-type>
+ </mapping>
+ <mapping>
+ <!--
+ | Note that you lose granularity here
+ | Use a numeric type and store milliseconds if you really need it
+ -->
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>BIT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>FLOAT</jdbc-type>
+ <sql-type>FLOAT</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>MS SQLSERVER2000</name>
+ <row-locking-template>SELECT ?1 FROM ?2 with (xlock) WHERE ?3 ORDER BY ?4</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <auto-increment-template>?1 IDENTITY</auto-increment-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>concat</function-name>
+ <function-sql>(?1 + ?2)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>substring</function-name>
+ <function-sql>substring(?1, ?2, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>lcase</function-name>
+ <function-sql>lower(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>length</function-name>
+ <function-sql>len(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>locate</function-name>
+ <function-sql>charindex(?1, ?2, ?3)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>abs</function-name>
+ <function-sql>abs(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>sqrt</function-name>
+ <function-sql>sqrt(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>ucase</function-name>
+ <function-sql>upper(?1)</function-sql>
+ </function-mapping>
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>BIGINT</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>LONGVARBINARY</jdbc-type>
+ <sql-type>IMAGE</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>TINYINT</sql-type>
+ </mapping>
+
+ <mapping>
+ <!--
+ | Note that you lose granularity here
+ | Use a numeric type and store milliseconds if you really need it
+ -->
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATETIME</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>BIT</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>REAL</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>FLOAT</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>DB2/400</name>
+ <row-locking-template/>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>18</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR(1)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+ <!-- Apparent DB2/400 doesn't handle Byte type either
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR(1) FOR BIT DATA</sql-type>
+ </mapping>
+ -->
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>FLOAT</jdbc-type>
+ <sql-type>FLOAT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR(5)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>VARCHAR(4096) FOR BIT DATA</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>SapDB</name>
+ <!-- SapDB 7.3 might require '... UPDATE OF ?1' in the row-locking-template -->
+ <!-- as is works with SapDB 7.4 -->
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD FOREIGN KEY ?2 (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>LONG BYTE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>CHAR BYTE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>BOOLEAN</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>FLOAT</jdbc-type>
+ <sql-type>FLOAT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE PRECISION</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>DECIMAL</jdbc-type>
+ <sql-type>DECIMAL(20)</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>MaxDB</name>
+ <row-locking-template>SELECT ?1 FROM ?2 WHERE ?3 ORDER BY ?4 FOR UPDATE</row-locking-template>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD FOREIGN KEY ?2 (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <auto-increment-template>?1</auto-increment-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>true</true-mapping>
+ <false-mapping>false</false-mapping>
+
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>LONG BYTE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>CHAR BYTE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BOOLEAN</jdbc-type>
+ <sql-type>BOOLEAN</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>FLOAT</jdbc-type>
+ <sql-type>FLOAT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE PRECISION</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>DECIMAL</jdbc-type>
+ <sql-type>DECIMAL(20)</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>Cloudscape</name>
+ <row-locking-template/>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>LONGVARCHAR</jdbc-type>
+ <sql-type>LONG VARCHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>BOOLEAN</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>TINYINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>LONGINT</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>REAL</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE PRECISION</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>LONGVARCHAR</jdbc-type>
+ <sql-type>LONG VARCHAR</sql-type>
+ </mapping>
+ <!-- NOTE: This alternative mapping has been suggested for cloudscape
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(256)</sql-type>
+ </mapping> -->
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>LONG VARBINARY</sql-type>
+ </mapping>
+ </type-mapping>
+
+
+ <type-mapping>
+ <name>InformixDB</name>
+ <row-locking-template>select ?1 from ?2 where ?3 order by ?4 for update</row-locking-template>
+ <pk-constraint-template>PRIMARY KEY (?2) CONSTRAINT ?1</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT FOREIGN KEY (?3) REFERENCES ?4 (?5) CONSTRAINT ?2</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <function-mapping>
+ <function-name>count</function-name>
+ <function-sql>count(?1)</function-sql>
+ </function-mapping>
+
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR(1)</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(255,0)</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.math.BigDecimal</java-type>
+ <jdbc-type>NUMERIC</jdbc-type>
+ <sql-type>DECIMAL</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>NUMERIC(18,0)</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>FLOAT</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE PRECISION</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.util.Date</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATETIME YEAR TO FRACTION(3)</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>DATETIME YEAR TO FRACTION(3)</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>BLOB</jdbc-type>
+ <sql-type>BLOB</sql-type>
+ </mapping>
+ </type-mapping>
+
+ <type-mapping>
+ <name>Mimer SQL</name>
+ <row-locking-template/>
+ <pk-constraint-template>CONSTRAINT ?1 PRIMARY KEY (?2)</pk-constraint-template>
+ <fk-constraint-template>ALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)</fk-constraint-template>
+ <alias-header-prefix>t</alias-header-prefix>
+ <alias-header-suffix>_</alias-header-suffix>
+ <alias-max-length>32</alias-max-length>
+ <subquery-supported>true</subquery-supported>
+ <true-mapping>1</true-mapping>
+ <false-mapping>0</false-mapping>
+
+ <mapping>
+ <java-type>java.lang.Boolean</java-type>
+ <jdbc-type>BIT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Byte</java-type>
+ <jdbc-type>TINYINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Short</java-type>
+ <jdbc-type>SMALLINT</jdbc-type>
+ <sql-type>SMALLINT</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Integer</java-type>
+ <jdbc-type>INTEGER</jdbc-type>
+ <sql-type>INTEGER</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Long</java-type>
+ <jdbc-type>BIGINT</jdbc-type>
+ <sql-type>BIGINT</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Float</java-type>
+ <jdbc-type>REAL</jdbc-type>
+ <sql-type>REAL</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Double</java-type>
+ <jdbc-type>DOUBLE</jdbc-type>
+ <sql-type>DOUBLE PRECISION</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Character</java-type>
+ <jdbc-type>CHAR</jdbc-type>
+ <sql-type>CHAR</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.String</java-type>
+ <jdbc-type>VARCHAR</jdbc-type>
+ <sql-type>VARCHAR(5000)</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.sql.Date</java-type>
+ <jdbc-type>DATE</jdbc-type>
+ <sql-type>DATE</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.sql.Time</java-type>
+ <jdbc-type>TIME</jdbc-type>
+ <sql-type>TIME</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.sql.Timestamp</java-type>
+ <jdbc-type>TIMESTAMP</jdbc-type>
+ <sql-type>TIMESTAMP</sql-type>
+ </mapping>
+
+ <mapping>
+ <java-type>java.lang.Object</java-type>
+ <jdbc-type>JAVA_OBJECT</jdbc-type>
+ <sql-type>VARBINARY(5000)</sql-type>
+ </mapping>
+ </type-mapping>
+ </type-mappings>
+
+ <entity-commands>
+ <!-- default command; doesn't support unknown-pk -->
+ <entity-command name="default"
+ class="org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateEntityCommand"/>
+
+ <!-- variation on default that skips select before insert -->
+ <entity-command name="no-select-before-insert"
+ class="org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateEntityCommand">
+ <attribute name="SQLExceptionProcessor">jboss.jdbc:service=SQLExceptionProcessor</attribute>
+ </entity-command>
+
+ <!-- fetches next key value with the specified sql statement -->
+ <entity-command name="pk-sql"
+ class="org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCPkSqlCreateCommand">
+ <!-- change to define SQL used to obtain key prior to insert -->
+ <attribute name="pk-sql">SELECT CURRENT_TIMESTAMP</attribute>
+ </entity-command>
+
+ <!-- this command requires auto-increment element for unknown-pk -->
+ <entity-command name="mysql-get-generated-keys"
+ class="org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCMySQLCreateCommand"/>
+
+ <!-- this command requires the specified sequence to have been created -->
+ <entity-command name="oracle-sequence"
+ class="org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCOracleCreateCommand">
+ <attribute name="sequence">TEST_SEQUENCE</attribute>
+ </entity-command>
+
+ <!-- this command makes the use of a specific sequence for each table -->
+ <entity-command name="oracle-table-sequence"
+ class="org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCOracleSequenceCreateCommand">
+ <attribute name="sequence_name">%%t_seq</attribute>
+ </entity-command>
+
+ <!-- retrieves generated key of the record inserted into hsql db -->
+ <entity-command name="hsqldb-fetch-key"
+ class="org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCHsqldbCreateCommand">
+ <!-- uncomment to change SQL statement used to obtain identity
+ <attribute name="pk-sql">CALL IDENTITY()</attribute>
+ -->
+ </entity-command>
+
+ <!-- retrieves generated key of the record inserted into sybase db -->
+ <entity-command name="sybase-fetch-key"
+ class="org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCSybaseCreateCommand"/>
+
+ <!-- retrieves generated key of the record inserted into SQLServer db -->
+ <entity-command name="mssql-fetch-key"
+ class="org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCSQLServerCreateCommand">
+ <!-- uncomment for versions prior to SQL Server 2000
+ <attribute name="pk-sql">SELECT @@IDENTITY</attribute>
+ -->
+ </entity-command>
+
+ <!-- retrieves serial value of the record inserted into informix db -->
+ <entity-command name="informix-serial"
+ class="org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCInformixCreateCommand">
+ <!-- uncomment to use with SERIAL8 column
+ <attribute name="method">getSerial8</attribute>
+ -->
+ </entity-command>
+
+ <!-- retrieves the currval of the the sequence associated with a PostgreSQL SERIAL column -->
+ <entity-command name="postgresql-fetch-seq"
+ class="org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCPostgreSQLCreateCommand">
+ <!-- uncomment to change the name of the sequence; default is ${table}_${pkColumn}_seq
+ <attribute name="sequence"></attribute>
+ -->
+ </entity-command>
+
+ <!-- uses key generator to fetch the next key value -->
+ <entity-command name="key-generator"
+ class="org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBCKeyGeneratorCreateCommand">
+ <attribute name="key-generator-factory">UUIDKeyGeneratorFactory</attribute>
+ </entity-command>
+
+ <!-- uses JDBC 3.0 getGeneratedKeys() method -->
+ <entity-command name="get-generated-keys"
+ class="org.jboss.ejb.plugins.cmp.jdbc.keygen.JDBC30GeneratedKeysCreateCommand"/>
+
+ <!-- pk-sql for jdbc2 pm -->
+ <entity-command name="jdbc2pm-pk-sql"
+ class="org.jboss.ejb.plugins.cmp.jdbc2.PkSqlCreateCommand">
+ <!-- change to define SQL used to obtain key prior to insert -->
+ <attribute name="pk-sql">SELECT CURRENT_TIMESTAMP</attribute>
+ </entity-command>
+
+ <!-- retrieves generated key of the record inserted into hsql db for jdbc2 pm -->
+ <entity-command name="jdbc2pm-hsqldb-fetch-key"
+ class="org.jboss.ejb.plugins.cmp.jdbc2.keygen.HsqldbCreateCommand">
+ <!-- uncomment to change SQL statement used to obtain identity
+ <attribute name="pk-sql">CALL IDENTITY()</attribute>
+ -->
+ </entity-command>
+
+ <!-- retrieves the currval of the the sequence associated with a PostgreSQL SERIAL column for jdbc2 pm -->
+ <entity-command name="jdbc2pm-postgresql-fetch-seq"
+ class="org.jboss.ejb.plugins.cmp.jdbc2.keygen.PostgreSQLCreateCommand">
+ <!-- uncomment to change the name of the sequence; default is ${table}_${pkColumn}_seq
+ <attribute name="sequence"></attribute>
+ -->
+ </entity-command>
+ </entity-commands>
+
+ <!-- reserved words that should not be used as table names -->
+ <!-- JBoss will escape them by prepending a 'X' -->
+ <reserved-words>
+ <word>alias</word>
+ <word>alter</word>
+ <word>between</word>
+ <word>char</word>
+ <word>column</word>
+ <word>commit</word>
+ <word>create</word>
+ <word>date</word>
+ <word>default</word>
+ <word>delete</word>
+ <word>drop</word>
+ <word>file</word>
+ <word>from</word>
+ <word>grant</word>
+ <word>group</word>
+ <word>index</word>
+ <word>integer</word>
+ <word>join</word>
+ <word>number</word>
+ <word>on</word>
+ <word>order</word>
+ <word>primary</word>
+ <word>public</word>
+ <word>revoke</word>
+ <word>rollback</word>
+ <word>row</word>
+ <word>select</word>
+ <word>set</word>
+ <word>session</word>
+ <word>size</word>
+ <word>table</word>
+ <word>trigger</word>
+ <word>update</word>
+ <word>unique</word>
+ <word>user</word>
+ <word>varchar</word>
+ <word>view</word>
+ </reserved-words>
+</jbosscmp-jdbc>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/AttributePersistenceService-xmbean.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/AttributePersistenceService-xmbean.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/AttributePersistenceService-xmbean.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,107 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.1//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_1.dtd">
+
+<!-- $Id: AttributePersistenceService-xmbean.xml 23167 2004-08-23 16:57:19Z andd $ -->
+
+<mbean>
+ <!-- MBean Info -->
+ <description>XMBean Attribute Persistence Service</description>
+ <descriptors>
+ <persistence persistPolicy="OnUpdate"
+ persistLocation="${jboss.server.data.dir}/xmbean-attrs"
+ persistName="AttributePersistenceService.ser"/>
+ <persistence-manager value="org.jboss.mx.persistence.ObjectStreamPersistenceManager"/>
+ </descriptors>
+ <class>org.jboss.system.pm.AttributePersistenceService</class>
+
+ <!-- Attributes -->
+ <attribute access="read-write" getMethod="getApmDestroyOnServiceStop" setMethod="setApmDestroyOnServiceStop">
+ <description>Specifies whether to call destroy() on the AttributePersistenceManager implementation, upon service stop</description>
+ <name>ApmDestroyOnServiceStop</name>
+ <type>boolean</type>
+ <descriptors>
+ <descriptor name="persistPolicy" value="Never"/>
+ </descriptors>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getAttributePersistenceManagerClass" setMethod="setAttributePersistenceManagerClass">
+ <description>The actual AttributePersistenceManager implementation</description>
+ <name>AttributePersistenceManagerClass</name>
+ <type>java.lang.String</type>
+ <descriptors>
+ <descriptor name="persistPolicy" value="Never"/>
+ </descriptors>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getAttributePersistenceManagerConfig" setMethod="setAttributePersistenceManagerConfig">
+ <description>The XML configuration that is passed to the AttributePersistenceManager implementation</description>
+ <name>AttributePersistenceManagerConfig</name>
+ <type>org.w3c.dom.Element</type>
+ <descriptors>
+ <descriptor name="persistPolicy" value="Never"/>
+ </descriptors>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getVersionTag" setMethod="setVersionTag">
+ <description>The version tag to use for stored/loaded Attribute data</description>
+ <name>VersionTag</name>
+ <type>java.lang.String</type>
+ <descriptors>
+ <descriptor name="persistPolicy" value="OnUpdate"/>
+ </descriptors>
+ </attribute>
+
+ &defaultAttributes;
+
+ <!-- Operations -->
+ <operation>
+ <description>Factory method returning the active AttributePersistenceManager implementation, for internal usage</description>
+ <name>apmCreate</name>
+ <return-type>org.jboss.mx.persistence.AttributePersistenceManager</return-type>
+ </operation>
+
+ <operation>
+ <description>Delegated to the active APM returns true when a persisted image with this id exists</description>
+ <name>apmExists</name>
+ <parameter>
+ <description>The id of the persisted attribute image</description>
+ <name>id</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>boolean</return-type>
+ </operation>
+
+ <operation>
+ <description>Delegated to the active APM removes the specified persisted attribute image</description>
+ <name>apmRemove</name>
+ <parameter>
+ <description>The id of the persisted attribute image</description>
+ <name>id</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+
+ <operation>
+ <description>Delegated to the active APM removes the persisted attribute images</description>
+ <name>apmRemoveAll</name>
+ <return-type>void</return-type>
+ </operation>
+
+ <operation>
+ <description>Delegated to the active APM it returns a list with the ids of all persisted attribute images</description>
+ <name>apmListAll</name>
+ <return-type>[Ljava.lang.String;</return-type>
+ </operation>
+
+ <operation>
+ <description>Delegated to the active APM it returns a single string with the ids of all persisted attribute images</description>
+ <name>apmListAllAsString</name>
+ <return-type>java.lang.String</return-type>
+ </operation>
+
+ &defaultOperations;
+
+</mbean>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/ClientUserTransaction-xmbean.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/ClientUserTransaction-xmbean.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/ClientUserTransaction-xmbean.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.1//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_1.dtd">
+<!-- $Id: ClientUserTransaction-xmbean.xml 18262 2003-12-20 21:12:07Z pilhuhn $ -->
+<mbean>
+ <description>ClientUserTransaction Service.</description>
+ <class>org.jboss.tm.usertx.server.ClientUserTransactionService</class>
+ &defaultAttributes;
+ <attribute access="write-only" setMethod="setTxProxyName">
+ <description>Set the name of the proxy factory service used for the UserTransactionSession</description>
+ <name>TxProxyName</name>
+ <type>javax.management.ObjectName</type>
+ </attribute>
+
+ <operation>
+ <description>Expose UserTransactionSession and UserTransactionSessionFactory interfaces via JMX to invokers.</description>
+ <name>invoke</name>
+ <parameter>
+ <description>A pointer to the invocation object</description>
+ <name>invocation</name>
+ <type>org.jboss.invocation.Invocation</type>
+ </parameter>
+ <return-type>java.lang.Object</return-type>
+ </operation>
+
+ &defaultOperations;
+ </mbean>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/JNDIView-xmbean.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/JNDIView-xmbean.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/JNDIView-xmbean.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.1//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_1.dtd">
+<!-- The JNDIView service XMBean
+$Id: JNDIView-xmbean.xml 38992 2005-12-13 15:29:35Z jerrygauth $
+-->
+<mbean>
+ <description>JNDIView Service. List deployed application java:comp namespaces,
+ the java: namespace as well as the global InitialContext JNDI namespace.
+ </description>
+ <class>org.jboss.naming.JNDIView</class>
+ &defaultAttributes;
+ <attribute access="read-write" getMethod="getHANamingService" setMethod="setHANamingService">
+ <description>The HANamingService service name</description>
+ <name>HANamingService</name>
+ <type>java.lang.String</type>
+ </attribute>
+ <operation>
+ <description>Output JNDI info as text</description>
+ <name>list</name>
+ <parameter>
+ <description>If true, list the class of each object in addition to its name</description>
+ <name>verbose</name>
+ <type>boolean</type>
+ </parameter>
+ <return-type>java.lang.String</return-type>
+ </operation>
+ <operation>
+ <description>Output JNDI info in XML format</description>
+ <name>listXML</name>
+ <return-type>java.lang.String</return-type>
+ </operation>
+ &defaultOperations;
+ </mbean>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/Log4jService-xmbean.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/Log4jService-xmbean.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/Log4jService-xmbean.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,110 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE mbean PUBLIC "-//JBoss//DTD JBOSS XMBEAN 1.1//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_1.dtd" [
+ <!ATTLIST interceptor
+ proxyName CDATA #IMPLIED
+>
+]>
+<!-- The Log4JService service XMBean
+$Id: Log4jService-xmbean.xml 28573 2005-02-11 13:15:54Z pilhuhn $
+-->
+<mbean>
+ <description>
+ This MBean allows to get and set Log4j specific options.
+See also resource:log4j.xml
+ </description>
+ <class>org.jboss.logging.Log4jService</class>
+ <constructor>
+ <description>The default constructor</description>
+ <name>Log4jService</name>
+ </constructor>
+
+ &defaultAttributes;
+
+ <attribute access="read-write" getMethod="getConfigurationURL" setMethod="setConfigurationURL">
+ <description>The URL of the log4j.xml config file.</description>
+ <name>ConfigurationURL</name>
+ <type>java.net.URL</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getCatchSystemErr" setMethod="setCatchSystemErr">
+ <description>Should data writen to standard error be caught and integrated into the log output.</description>
+ <name>CatchSystemErr</name>
+ <type>boolean</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getCatchSystemOut" setMethod="setCatchSystemOut">
+ <description>Should data writen to standard output be caught and integrated into the log output.</description>
+ <name>CatchSystemOut</name>
+ <type>boolean</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getLog4jQuietMode" setMethod="setLog4jQuietMode">
+ <description>Sets the log4j quite mode. For log4j 1.2.8 this must stay on true.</description>
+ <name>Log4jQuietMode</name>
+ <type>boolean</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getRefreshPeriod" setMethod="setRefreshPeriod">
+ <description>The time in seconds between checking for new config.</description>
+ <name>RefreshPeriod</name>
+ <type>int</type>
+ </attribute>
+ <!-- Operations -->
+ <operation>
+ <description>Displays the log level of a given logger.</description>
+ <name>getLoggerLevel</name>
+ <parameter>
+ <description>The name of the logger to display.</description>
+ <name>logger</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>java.lang.String</return-type>
+ </operation>
+ <operation>
+ <description>Sets the log level for a given logger.</description>
+ <name>setLoggerLevel</name>
+ <parameter>
+ <description>The name of the logger to set.</description>
+ <name>logger</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <parameter>
+ <description>The log level to set.</description>
+ <name>level</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description>Sets the levels of each logger specified by the given comma
+ seperated list of logger names.</description>
+ <name>setLoggerLevels</name>
+ <parameter>
+ <description>The list of loggers</description>
+ <name>loggers</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <parameter>
+ <description>The log level to set</description>
+ <name>level</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description>Force the logging system to reconfigure.</description>
+ <name>reconfigure</name>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description>Force the logging system to reconfigure with the given URL.</description>
+ <name>reconfigure</name>
+ <parameter>
+ <description>The url for the new configuration.</description>
+ <name>url</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+
+
+ &defaultOperations;
+
+</mbean>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/NamingBean-xmbean.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/NamingBean-xmbean.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/NamingBean-xmbean.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.1//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_1.dtd">
+
+<!-- The JNDI Naming XMBean
+ $Id: NamingBean-xmbean.xml 60240 2007-02-03 18:29:53Z scott.stark at jboss.org $
+-->
+<mbean>
+ <description>The JNDI pojo bean</description>
+
+ <class>org.jnp.server.NamingBeanImpl</class>
+
+ <constructor>
+ <description>The default constructor</description>
+ <name>NamingBeanImpl</name>
+ </constructor>
+
+ <attribute access="read-only" getMethod="getNamingInstance">
+ <description>The NamingInstance</description>
+ <name>NamingInstance</name>
+ <type>org.jnp.interfaces.Naming</type>
+ </attribute>
+
+ <!-- Operations -->
+ <operation>
+ <description>The start lifecycle op</description>
+ <name>start</name>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description>The stop lifecycle op</description>
+ <name>stop</name>
+ <return-type>void</return-type>
+ </operation>
+
+</mbean>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/NamingService-xmbean.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/NamingService-xmbean.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/NamingService-xmbean.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,196 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.1//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_1.dtd"
+[
+ <!ATTLIST interceptor proxyName CDATA #IMPLIED>
+]>
+
+<!-- The JNDI Naming service XMBean
+$Id: NamingService-xmbean.xml 60231 2007-02-03 08:00:43Z scott.stark at jboss.org $
+-->
+<mbean>
+ <description>The standard JBoss JNDI naming server with a custom
+ ProxyFactoryInterceptor interceptor that does replacement of NamingContext
+ objects with the detached invoker proxy.
+ </description>
+
+ <descriptors>
+ <interceptors>
+ <!-- Uncomment to enable NamingContext replacement by the detached
+ invoker proxy. You need to set the proxyName attribute correctly.
+ <interceptor code="org.jboss.naming.interceptors.ProxyFactoryInterceptor"
+ proxyName="jboss:service=proxyFactory,type=pooled,target=Naming"/>
+ -->
+ <interceptor code="org.jboss.mx.interceptor.PersistenceInterceptor2" />
+ <interceptor code="org.jboss.mx.interceptor.ModelMBeanInterceptor" />
+ <interceptor code="org.jboss.mx.interceptor.ObjectReferenceInterceptor" />
+ </interceptors>
+ </descriptors>
+
+ <class>org.jboss.naming.NamingService</class>
+
+ <constructor>
+ <description>The default constructor</description>
+ <name>NamingService</name>
+ </constructor>
+
+ &defaultAttributes;
+
+ <attribute access="read-only" getMethod="getMethodMap">
+ <name>MethodMap</name>
+ <type>java.util.Map</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getNaming" setMethod="setNaming">
+ <description>Underlying Naming bean instance</description>
+ <name>Naming</name>
+ <type>org.jnp.server.NamingBean</type>
+ </attribute>
+ <attribute access="read-only" getMethod="getNamingInstance">
+ <description>Underlying Naming bean instance</description>
+ <name>NamingInstance</name>
+ <type>org.jnp.interfaces.Naming</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getCallByValue" setMethod="setCallByValue">
+ <description>The call by value mode. true if all lookups are unmarshalled using
+ the caller's TCL, false if in VM lookups return the value by reference.</description>
+ <name>CallByValue</name>
+ <type>boolean</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getBindAddress" setMethod="setBindAddress">
+ <description>The bind address of the bootstrap lookup socket.</description>
+ <name>BindAddress</name>
+ <type>java.lang.String</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getPort" setMethod="setPort">
+ <description>The listening port for the bootstrap JNP service. Set this to -1
+ to run the NamingService without the JNP invoker listening port.</description>
+ <name>Port</name>
+ <type>int</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getBacklog" setMethod="setBacklog">
+ <description>The bootstrap socket backlog count.</description>
+ <name>Backlog</name>
+ <type>int</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getJNPServerSocketFactory"
+ setMethod="setJNPServerSocketFactory">
+ <description>The bootstrap socket javax.net.ServerSocketFactory class name</description>
+ <name>JNPServerSocketFactory</name>
+ <type>java.lang.String</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getJNPServerSocketFactoryBean"
+ setMethod="setJNPServerSocketFactoryBean">
+ <description>The bootstrap socket javax.net.ServerSocketFactory</description>
+ <name>JNPServerSocketFactoryBean</name>
+ <type>javax.net.ServerSocketFactory</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getRmiPort" setMethod="setRmiPort">
+ <description>The port of the RMI naming service, 0 == anonymous. This
+ is only used if an explicit InvokerProxyFactory has not been set.</description>
+ <name>RmiPort</name>
+ <type>int</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getRmiBindAddress" setMethod="setRmiBindAddress">
+ <description>The RMI service bind address. Empty == all addresses</description>
+ <name>RmiBindAddress</name>
+ <type>java.lang.String</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getClientSocketFactory" setMethod="setClientSocketFactory">
+ <description>The RMI service java.rmi.server.RMIClientSocketFactory class name</description>
+ <name>ClientSocketFactory</name>
+ <type>java.lang.String</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getClientSocketFactoryBean" setMethod="setClientSocketFactoryBean">
+ <description>The RMI service java.rmi.server.RMIServerSocketFactory instance</description>
+ <name>ClientSocketFactoryBean</name>
+ <type>java.rmi.server.RMIClientSocketFactory</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getServerSocketFactory" setMethod="setServerSocketFactory">
+ <description>The RMI service java.rmi.server.RMIServerSocketFactory class name</description>
+ <name>ServerSocketFactory</name>
+ <type>java.lang.String</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getServerSocketFactoryBean" setMethod="setServerSocketFactoryBean">
+ <description>The RMI service java.rmi.server.RMIServerSocketFactory instance</description>
+ <name>ServerSocketFactory</name>
+ <type>java.rmi.server.RMIServerSocketFactory</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getInstallGlobalService"
+ setMethod="setInstallGlobalService">
+ <description>Ghe InstallGlobalService which defines whether the MainMBean's
+ Naming server will be installed as the NamingContext.setLocal global
+ value.</description>
+ <name>InstallGlobalService</name>
+ <type>boolean</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getUseGlobalService"
+ setMethod="setUseGlobalService">
+ <description>The UseGlobalService which defines whether the MainMBean's
+ Naming server will initialized from the existing NamingContext.setLocal global
+ value.</description>
+ <name>UseGlobalService</name>
+ <type>boolean</type>
+ </attribute>
+ <attribute access="write-only" setMethod="setLookupPool">
+ <description>The thread pool service used to control the bootstrap lookups</description>
+ <name>LookupPool</name>
+ <type>org.jboss.util.threadpool.BasicThreadPoolMBean</type>
+ </attribute>
+ <attribute access="write-only" setMethod="setInvokerProxyFactory">
+ <description>The detached invoker proxy factory to use for the naming
+ service transport.</description>
+ <name>InvokerProxyFactory</name>
+ <type>org.jboss.invocation.jrmp.server.JRMPProxyFactoryMBean</type>
+ </attribute>
+
+ <!-- Operations -->
+ <operation>
+ <description>The generic invocation operation used by detached invokers
+ to route requests to the service
+ </description>
+ <name>invoke</name>
+ <parameter>
+ <description>The Naming interface method invocation encapsulation
+ </description>
+ <name>invocation</name>
+ <type>org.jboss.invocation.Invocation</type>
+ </parameter>
+ <return-type>java.lang.Object</return-type>
+ </operation>
+ <operation>
+ <description>Create an alias in jndi
+ </description>
+ <name>createAlias</name>
+ <parameter>
+ <description>The from name
+ </description>
+ <name>fromName</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <parameter>
+ <description>The to name
+ </description>
+ <name>toName</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description>Remove an alias from jndi
+ </description>
+ <name>removeAlias</name>
+ <parameter>
+ <description>The name
+ </description>
+ <name>name</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+
+ &defaultOperations;
+
+</mbean>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/TransactionManagerService-xmbean.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/TransactionManagerService-xmbean.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/TransactionManagerService-xmbean.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.1//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_1.dtd">
+
+<!-- $Id: TransactionManagerService-xmbean.xml 32334 2005-06-17 06:45:59Z adrian $ -->
+<mbean>
+ <description>TransactionManager Service.</description>
+ <class>org.jboss.tm.TransactionManagerService</class>
+ &defaultAttributes;
+ <attribute access="read-write" getMethod="getGlobalIdsEnabled" setMethod="setGlobalIdsEnabled">
+ <description>Should be set to true for transaction demarcation over IIOP</description>
+ <name>GlobalIdsEnabled</name>
+ <type>boolean</type>
+ </attribute>
+ <attribute access="read-write" getMethod="isInterruptThreads" setMethod="setInterruptThreads">
+ <description>Whether to interrupt threads at transaction timeout</description>
+ <name>InterruptThreads</name>
+ <type>boolean</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getTransactionTimeout" setMethod="setTransactionTimeout">
+ <description>The transaction timeout in seconds</description>
+ <name>TransactionTimeout</name>
+ <type>int</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getXidFactory" setMethod="setXidFactory">
+ <description>Name of the xidFactory</description>
+ <name>XidFactory</name>
+ <type>javax.management.ObjectName</type>
+ </attribute>
+ <attribute access="write-only" setMethod="setTransactionIntegrityFactory">
+ <description>Transaction Integrity Policy</description>
+ <name>TransactionIntegrityFactory</name>
+ <type>org.jboss.tm.integrity.TransactionIntegrityFactory</type>
+ </attribute>
+ <attribute access="read-only" getMethod="getTransactionManager">
+ <description>Returns the TransactionManager managed by this service</description>
+ <name>TransactionManager</name>
+ <type>javax.transaction.TransactionManager</type>
+ </attribute>
+ <attribute access="read-only" getMethod="getXATerminator">
+ <description>Returns the XATerminator managed by this service</description>
+ <name>XATerminator</name>
+ <type>org.jboss.tm.JBossXATerminator</type>
+ </attribute>
+ <attribute access="read-only" getMethod="getTransactionCount">
+ <description>Counts the number of active transactions</description>
+ <name>TransactionCount</name>
+ <type>long</type>
+ </attribute>
+ <attribute access="read-only" getMethod="getCommitCount">
+ <description>Counts the number of commited transactions</description>
+ <name>CommitCount</name>
+ <type>long</type>
+ </attribute>
+ <attribute access="read-only" getMethod="getRollbackCount">
+ <description>Counts the number of transactions that have been rolled back</description>
+ <name>RollbackCount</name>
+ <type>long</type>
+ </attribute>
+
+ <operation>
+ <description>Register a XAException Formatter</description>
+ <name>registerXAExceptionFormatter</name>
+ <parameter>
+ <description>The class of the formatter</description>
+ <name>clazz</name>
+ <type>java.lang.Class</type>
+ </parameter>
+ <parameter>
+ <description>A XAExceptionFromatter value</description>
+ <name>formatter</name>
+ <type>org.jboss.tm.XAExceptionFormatter</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description>Unregister a XAException Formatter</description>
+ <name>unregisterXAExceptionFormatter</name>
+ <parameter>
+ <description>The class of the formatter</description>
+ <name>clazz</name>
+ <type>java.lang.Class</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+
+ &defaultOperations;
+ </mbean>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.JARDeployer-xmbean.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.JARDeployer-xmbean.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.JARDeployer-xmbean.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_2.dtd">
+<!-- $Id: org.jboss.deployment.JARDeployer-xmbean.xml 35861 2005-09-11 22:24:37Z dimitris $ -->
+<mbean>
+
+ <description>The JARDeployer adds archives that do not contain META-INF/*.xml
+ files. The pattern of xml files that correspond to deployment descriptors
+ can be specified using the DescriptorNames attribute.
+ </description>
+ <class>org.jboss.deployment.JARDeployer</class>
+
+ <attribute access='read-write' getMethod='getDescriptorNames' setMethod='setDescriptorNames'>
+ <description>The list of suffixes that define deployment descriptors which
+ if found in an archive META-INF directory indicate non-jar deployments
+ which should be ignored by the JARDeployer
+ </description>
+ <name>DescriptorNames</name>
+ <type>[Ljava.lang.String;</type>
+ <!-- This suffix list represents the legacy behavior that ignored all
+ archives with META-INF/*.xml files
+ <descriptors>
+ <value value=".xml"/>
+ </descriptors>
+ -->
+ <!-- Ignore archives with the standard descriptors in META-INF -->
+ <descriptors>
+ <value value="ejb-jar.xml,jboss-service.xml,-ds.xml,ra.xml,application.xml,application-client.xml"/>
+ </descriptors>
+ </attribute>
+
+ <!-- SubDeployerExtMBean attribute -->
+ <attribute access="read-write" getMethod="getEnhancedSuffixes" setMethod="setEnhancedSuffixes">
+ <description>Allow the override of supported suffixes and relative order</description>
+ <name>EnhancedSuffixes</name>
+ <type>[Ljava.lang.String;</type>
+ </attribute>
+
+ &deployerAttributes;
+ &defaultAttributes;
+
+ &deployerOperations;
+ &defaultOperations;
+
+</mbean>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.MainDeployer-xmbean.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.MainDeployer-xmbean.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.MainDeployer-xmbean.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,270 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.1//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_1.dtd">
+
+<!-- $Id: org.jboss.deployment.MainDeployer-xmbean.xml 46368 2006-07-18 15:59:06Z dimitris $ -->
+
+<!-- The MainDeployer XMBean descriptor -->
+<mbean>
+ <description>The Main deployer is the service which acts as the entry
+ point for the deployment/undeployment requests.
+ </description>
+ <class>org.jboss.deployment.MainDeployer</class>
+
+ <attribute access='read-write' setMethod='setCopyFiles' getMethod='getCopyFiles'>
+ <description></description>
+ <name>CopyFiles</name>
+ <type>boolean</type>
+ <descriptors>
+ <value value="true"/>
+ </descriptors>
+ </attribute>
+ <attribute access='write-only' setMethod='setServiceController'>
+ <description></description>
+ <name>ServiceController</name>
+ <type>javax.management.ObjectName</type>
+ </attribute>
+ <attribute access='read-only' getMethod='getServiceName'>
+ <description></description>
+ <name>ServiceName</name>
+ <type>javax.management.ObjectName</type>
+ </attribute>
+ <attribute access='read-only' getMethod='getSuffixOrder'>
+ <description>The suffix order used when sorting deployments, constructed dynamically by registering deployers</description>
+ <name>SuffixOrder</name>
+ <type>[Ljava.lang.String;</type>
+ </attribute>
+ <attribute access='read-write' setMethod='setEnhancedSuffixOrder' getMethod='getEnhancedSuffixOrder'>
+ <description>Allows the override of the suffix order declared by subdeployers, using the syntax [order:]suffix
+ </description>
+ <name>EnhancedSuffixOrder</name>
+ <type>[Ljava.lang.String;</type>
+ <!--
+ Statically set one or more enhanced suffix orders, independent of the value proposed by subdeployers.
+ Some deployers may also allow the suffixes/orders to be set locally, so that's preferable too.
+ For reference, this is the list of enhanced suffixes likely to be set by deployers (it may not
+ be completely up-to-date, or there can be user-defined deployers).
+
+ 050:.deployer,050:-deployer.xml,100:.aop,100:-aop.xml,150:.sar,150:-service.xml,200:.beans,250:.rar,300:-ds.xml,350:.har,400:.jar,400:.ejb3,400:.par,500:.war,600:.wsr,650:.ear,700:.jar,750:.zip,800:.bsh,900:.last
+
+ Until we resolve some startup issues, we'll setup some static enhanced suffix orders bellow
+ and leave the rest of the suffixes contributed dynamically by registering deployers.
+ -->
+ <descriptors>
+ <value value="250:.rar,300:-ds.xml,400:.jar,500:.war,550:.jse,650:.ear,800:.bsh"/>
+ </descriptors>
+ </attribute>
+ <attribute access='read-write' setMethod='setTempDir' getMethod='getTempDir'>
+ <description></description>
+ <name>TempDir</name>
+ <type>java.io.File</type>
+ </attribute>
+ <attribute access='read-only' getMethod='getTempDirString'>
+ <description></description>
+ <name>TempDirString</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ &defaultAttributes;
+
+ <operation>
+ <description></description>
+ <name>addDeployer</name>
+ <parameter>
+ <name>deployer</name>
+ <type>org.jboss.deployment.SubDeployer</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>removeDeployer</name>
+ <parameter>
+ <name>deployer</name>
+ <type>org.jboss.deployment.SubDeployer</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>deploy</name>
+ <parameter>
+ <name>url</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>deploy</name>
+ <parameter>
+ <name>url</name>
+ <type>java.net.URL</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>deploy</name>
+ <parameter>
+ <name>sdi</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description>starts a package identified by a URL</description>
+ <name>start</name>
+ <parameter>
+ <name>urlspec</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description>stops a package identified by a URL</description>
+ <name>stop</name>
+ <parameter>
+ <name>urlspec</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>getDeployment</name>
+ <parameter>
+ <name>url</name>
+ <type>java.net.URL</type>
+ </parameter>
+ <return-type>org.jboss.deployment.DeploymentInfo</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>getWatchUrl</name>
+ <parameter>
+ <name>url</name>
+ <type>java.net.URL</type>
+ </parameter>
+ <return-type>java.net.URL</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>isDeployed</name>
+ <parameter>
+ <name>url</name>
+ <type>java.net.URL</type>
+ </parameter>
+ <return-type>boolean</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>isDeployed</name>
+ <parameter>
+ <name>url</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>boolean</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>listDeployed</name>
+ <return-type>java.util.Collection</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>listDeployedAsString</name>
+ <return-type>java.lang.String</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>listDeployedModules</name>
+ <return-type>java.util.Collection</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>listDeployers</name>
+ <return-type>java.util.Collection</return-type>
+ </operation>
+ <operation>
+ <description>Check the current deployment states and generate a
+ IncompleteDeploymentException if there are mbeans waiting for depedencies.
+ </description>
+ <name>checkIncompleteDeployments</name>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>listIncompletelyDeployed</name>
+ <return-type>java.util.Collection</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>listWaitingForDeployer</name>
+ <return-type>java.util.Collection</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>redeploy</name>
+ <parameter>
+ <name>url</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>redeploy</name>
+ <parameter>
+ <name>url</name>
+ <type>java.net.URL</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>redeploy</name>
+ <parameter>
+ <name>sdi</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>shutdown</name>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>undeploy</name>
+ <parameter>
+ <name>url</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>undeploy</name>
+ <parameter>
+ <name>url</name>
+ <type>java.net.URL</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+ <operation>
+ <description></description>
+ <name>undeploy</name>
+ <parameter>
+ <name>sdi</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+
+ &defaultOperations;
+
+</mbean>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.SARDeployer-xmbean.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.SARDeployer-xmbean.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/conf/xmdesc/org.jboss.deployment.SARDeployer-xmbean.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_2.dtd">
+<!--
+ SARDeployer XMBean descriptor
+
+ $Id: org.jboss.deployment.SARDeployer-xmbean.xml 35861 2005-09-11 22:24:37Z dimitris $
+ -->
+<mbean>
+ <description>The SAR deployer handles the JBoss service archive deployments.</description>
+ <class>org.jboss.deployment.SARDeployer</class>
+
+ <attribute access="read-write" getMethod="getUseNamespaceAwareParser" setMethod="setUseNamespaceAwareParser">
+ <description>A flag passed to the JAXP DocumentBuilderFactory setNamespaceAware method</description>
+ <name>UseNamespaceAwareParser</name>
+ <type>boolean</type>
+ <descriptors>
+ <value value="true"/>
+ </descriptors>
+ </attribute>
+
+ <!-- SubDeployerExtMBean attribute -->
+ <attribute access="read-write" getMethod="getEnhancedSuffixes" setMethod="setEnhancedSuffixes">
+ <description>Allow the override of supported suffixes and relative order</description>
+ <name>EnhancedSuffixes</name>
+ <type>[Ljava.lang.String;</type>
+ <descriptors>
+ <!-- Add "350:har" to the suffixes supported normally by the SARDeployer -->
+ <value value="050:.deployer,050:-deployer.xml,150:.sar,150:-service.xml,350:.har"/>
+ </descriptors>
+ </attribute>
+
+ &deployerAttributes;
+ &defaultAttributes;
+
+ <operation>
+ <description>Get the associated service DeploymentInfo if found, null otherwise</description>
+ <name>getService</name>
+ <parameter>
+ <name>serviceName</name>
+ <type>javax.management.ObjectName</type>
+ </parameter>
+ <return-type>org.jboss.deployment.DeploymentInfo</return-type>
+ </operation>
+
+ &deployerOperations;
+ &defaultOperations;
+
+</mbean>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/bsh-deployer.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/bsh-deployer.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/bsh-deployer.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- The JBoss service configuration file for the BSH deployer service.
+$Id: bsh-deployer.xml 23463 2004-09-05 15:50:37Z starksm $
+-->
+<server>
+ <!-- BSH deployer, remove to disable deployment of bsh scripts as services
+ -->
+ <mbean code="org.jboss.varia.deployment.BeanShellSubDeployer"
+ name="jboss.deployer:service=BSHDeployer">
+ </mbean>
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/cache-invalidation-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/cache-invalidation-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/cache-invalidation-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE server>
+<!-- $Id: cache-invalidation-service.xml 16662 2003-08-27 04:38:22Z patriot1burke $ -->
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- Cache Invalidation Service -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<server>
+
+ <mbean code="org.jboss.cache.invalidation.InvalidationManager"
+ name="jboss.cache:service=InvalidationManager">
+ </mbean>
+
+
+<!--
+ Uncomment if you want to activate the cache invalidation mechanism accross
+ nodes using the JMS bridge
+
+ PropagationMode can be : IN_OUT = 1, IN_ONLY = 2, OUT_ONLY = 3
+
+ You can also set the ProviderUrl attribute to another IP:port setting if you
+ must lookup your JMS information in other JMS trees i.e.
+
+ <attribute name="ProviderUrl">MyOtherNode:1099</attribute>
+
+-->
+<!--
+ <mbean code="org.jboss.mq.server.jmx.Topic"
+ name="jboss.mq.destination:service=Topic,name=JMSCacheInvalidationBridge">
+ <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
+ <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
+ </mbean>
+
+ <mbean code="org.jboss.cache.invalidation.bridges.JMSCacheInvalidationBridge"
+ name="jboss.cache:service=InvalidationBridge,type=JavaGroups">
+ <depends>jboss.cache:service=InvalidationManager</depends>
+ <depends>jboss.mq.destination:service=Topic,name=JMSCacheInvalidationBridge</depends>
+ <attribute name="InvalidationManager">jboss.cache:service=InvalidationManager</attribute>
+ <attribute name="ConnectionFactoryName">java:/ConnectionFactory</attribute>
+ <attribute name="TopicName">topic/JMSCacheInvalidationBridge</attribute>
+ <attribute name="PropagationMode">1</attribute>
+ </mbean>
+-->
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/client-deployer-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/client-deployer-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/client-deployer-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- The J2EE application client deployer service
+$Id: client-deployer-service.xml 36323 2005-09-24 21:49:13Z starksm $
+-->
+<server>
+ <!-- A ClientDeployer configuration with an minimal ebmedded xmbean descriptor
+ -->
+ <mbean code="org.jboss.deployment.ClientDeployer"
+ name="jboss.j2ee:service=ClientDeployer"
+ xmbean-dd="">
+ <xmbean>
+ <description>The J2EE Application Client Deployer</description>
+ <class>org.jboss.deployment.ClientDeployer</class>
+
+ <!-- Attributes -->
+ <attribute access="read-only" getMethod="getStateString">
+ <description>The service state name</description>
+ <name>StateString</name>
+ <type>java.lang.String</type>
+ </attribute>
+ <attribute access="read-only" getMethod="getState">
+ <description>The service state value</description>
+ <name>State</name>
+ <type>int</type>
+ </attribute>
+
+ <!-- Operations -->
+ <operation>
+ <description>The create lifecycle operation</description>
+ <name>create</name>
+ </operation>
+ <operation>
+ <description>The start lifecycle operation</description>
+ <name>start</name>
+ </operation>
+ <operation>
+ <description>The stop lifecycle operation</description>
+ <name>stop</name>
+ </operation>
+ <operation>
+ <description>The destroy lifecycle operation</description>
+ <name>destroy</name>
+ </operation>
+ </xmbean>
+ </mbean>
+
+ <!-- An alternate externalized xmbean configuration that includes more of the
+ standard attributes and operations.
+ <mbean code="org.jboss.deployment.ClientDeployer"
+ name="jboss.j2ee:service=ClientDeployer"
+ xmbean-dd="client-deployer-xmbean.xml" />
+ -->
+</server>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/ear-deployer.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/ear-deployer.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/ear-deployer.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- The JBoss service configuration file for the EAR deployer service.
+$Id: ear-deployer.xml 60679 2007-02-19 21:35:39Z scott.stark at jboss.org $
+-->
+<server>
+ <!-- EAR deployer, remove if you are not using ear deployments -->
+ <mbean code="org.jboss.deployment.EARDeployer"
+ name="jboss.j2ee:service=EARDeployer">
+ <!-- A flag indicating if ear deployments should have their own scoped
+ class loader to isolate their classes from other deployments.
+ -->
+ <attribute name="Isolated">false</attribute>
+ <!-- A flag indicating if the ear components should have in VM call
+ optimization disabled.
+ -->
+ <attribute name="CallByValue">false</attribute>
+ <!-- A flag the enables the default behavior of the ee5 library-directory. If true,
+ the lib contents of an ear are assumed to be the default value for library-directory
+ in the absence of an explicit library-directory. If false, there must be an
+ explicit library-directory.
+ -->
+ <attribute name="EnablelibDirectoryByDefault">true</attribute>
+ </mbean>
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/ejb-deployer.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/ejb-deployer.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/ejb-deployer.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,311 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ The JBoss service configuration file for the EJB deployer service.
+
+ $Id: ejb-deployer.xml 62317 2007-04-13 10:39:22Z dimitris at jboss.org $
+-->
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- J2EE Timer Service -->
+ <!-- ==================================================================== -->
+
+ <!-- An EJB Timer Service that is Tx aware -->
+ <mbean code="org.jboss.ejb.txtimer.EJBTimerServiceImpl"
+ name="jboss.ejb:service=EJBTimerService">
+ <attribute name="RetryPolicy">jboss.ejb:service=EJBTimerService,retryPolicy=fixedDelay</attribute>
+ <attribute name="PersistencePolicy">jboss.ejb:service=EJBTimerService,persistencePolicy=database</attribute>
+ <attribute name="TimerIdGeneratorClassName">org.jboss.ejb.txtimer.BigIntegerTimerIdGenerator</attribute>
+ <attribute name="TimedObjectInvokerClassName">org.jboss.ejb.txtimer.TimedObjectInvokerImpl</attribute>
+ <depends optional-attribute-name="TransactionManagerFactory" proxy-type="org.jboss.tm.TransactionManagerFactory">
+ jboss:service=TransactionManager
+ </depends>
+ </mbean>
+
+ <!-- A retry policy that uses a fixed interval in milli seconds -->
+ <mbean code="org.jboss.ejb.txtimer.FixedDelayRetryPolicy" name="jboss.ejb:service=EJBTimerService,retryPolicy=fixedDelay">
+ <attribute name="Delay">100</attribute>
+ </mbean>
+
+ <!-- A persistence policy that does not persist the timers
+ <mbean code="org.jboss.ejb.txtimer.NoopPersistencePolicy" name="jboss.ejb:service=EJBTimerService,persistencePolicy=noop"/>
+ -->
+
+ <!--
+ A persistence policy that persists timers to a database.
+
+ The 2 supported db persistence plugins are:
+ org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin
+ org.jboss.ejb.txtimer.OracleDatabasePersistencePlugin
+
+ The table name defaults to "TIMERS". It can be overriden using the
+ 'TimersTable' attribute if the persistence plugin supports it.
+ When overriding the timers table, an optional schema can be specified
+ using the syntax [schema.]table
+ -->
+ <mbean code="org.jboss.ejb.txtimer.DatabasePersistencePolicy" name="jboss.ejb:service=EJBTimerService,persistencePolicy=database">
+ <!-- DataSourceBinding ObjectName -->
+ <depends optional-attribute-name="DataSource">jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
+ <!-- The plugin that handles database persistence -->
+ <attribute name="DatabasePersistencePlugin">org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin</attribute>
+ <!-- The timers table name -->
+ <attribute name="TimersTable">TIMERS</attribute>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- EJB Deployer -->
+ <!-- ==================================================================== -->
+
+ <!-- EJB deployer, remove to disable EJB behavior-->
+ <mbean code="org.jboss.ejb.EJBDeployer" name="jboss.ejb:service=EJBDeployer" xmbean-dd="">
+
+ <!-- Inline XMBean Descriptor BEGIN -->
+ <xmbean>
+ <description>The EJBDeployer responsible for ejb jar deployment</description>
+ <descriptors>
+ <interceptors>
+ <!-- comment out DynamicInterceptor to disable dynamic addition of interceptors -->
+ <interceptor code="org.jboss.mx.interceptor.DynamicInterceptor"/>
+ </interceptors>
+ </descriptors>
+ <class>org.jboss.ejb.EJBDeployer</class>
+
+ <!-- ServiceMBean attributes -->
+ <attribute access="read-only" getMethod="getName">
+ <description>The class name of the MBean</description>
+ <name>Name</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-only" getMethod="getState">
+ <description>The status of the MBean</description>
+ <name>State</name>
+ <type>int</type>
+ </attribute>
+
+ <attribute access="read-only" getMethod="getStateString">
+ <description>The status of the MBean in text form</description>
+ <name>StateString</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <!-- SubDeployerMBean attributes -->
+ <attribute access="read-only" getMethod="getServiceName">
+ <description>The JMX ObjectName of the service that provides the SubDeployer</description>
+ <name>ServiceName</name>
+ <type>javax.management.ObjectName</type>
+ </attribute>
+
+ <attribute access="read-only" getMethod="getSuffixes">
+ <description>An array of suffixes of interest to this subdeployer</description>
+ <name>Suffixes</name>
+ <type>[Ljava.lang.String;</type>
+ </attribute>
+
+ <attribute access="read-only" getMethod="getRelativeOrder">
+ <description>The relative order of the specified suffixes</description>
+ <name>RelativeOrder</name>
+ <type>int</type>
+ </attribute>
+
+ <!-- SubDeployerExtMBean attribute -->
+ <attribute access="read-write" getMethod="getEnhancedSuffixes" setMethod="setEnhancedSuffixes">
+ <description>Allow the override of supported suffixes and relative order</description>
+ <name>EnhancedSuffixes</name>
+ <type>[Ljava.lang.String;</type>
+ </attribute>
+
+ <!-- EJBDeployerMBean attributes -->
+ <attribute access="read-write" getMethod="getWebServiceName" setMethod="setWebServiceName">
+ <description>The dynamic class loading simple web server</description>
+ <name>WebServiceName</name>
+ <type>javax.management.ObjectName</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getVerifyDeployments" setMethod="setVerifyDeployments">
+ <description>Control the bean verifier (on/off)</description>
+ <name>VerifyDeployments</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getVerifierVerbose" setMethod="setVerifierVerbose">
+ <description>Control the verbose mode of the bean verifier</description>
+ <name>VerifierVerbose</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getStrictVerifier" setMethod="setStrictVerifier">
+ <description>Control the strictness of the bean verifier</description>
+ <name>StrictVerifier</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="isCallByValue" setMethod="setCallByValue">
+ <description>Enable/disable call-by-value semantics</description>
+ <name>CallByValue</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getValidateDTDs" setMethod="setValidateDTDs">
+ <description>Enable/disable the validation of deployment descriptors</description>
+ <name>ValidateDTDs</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="isMetricsEnabled" setMethod="setMetricsEnabled">
+ <description>Enable/disable the metrics interceptor for containers</description>
+ <name>MetricsEnabled</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getTransactionManagerServiceName" setMethod="setTransactionManagerServiceName">
+ <description>The transaction manager service to use</description>
+ <name>TransactionManagerServiceName</name>
+ <type>javax.management.ObjectName</type>
+ </attribute>
+
+ <!-- EJBDeployerMBean operations -->
+ <operation>
+ <description>List the deployed applications</description>
+ <name>listDeployedApplications</name>
+ <return-type>java.util.Iterator</return-type>
+ </operation>
+
+ <!-- ServiceMBean operations -->
+ <operation>
+ <description>Standard MBean lifecycle method</description>
+ <name>create</name>
+ </operation>
+
+ <operation>
+ <description>The start lifecycle operation</description>
+ <name>start</name>
+ </operation>
+
+ <operation>
+ <description>The stop lifecycle operation</description>
+ <name>stop</name>
+ </operation>
+
+ <operation>
+ <description>The destroy lifecycle operation</description>
+ <name>destroy</name>
+ </operation>
+
+ <operation>
+ <description>The detyped lifecycle operation (for internal use only)</description>
+ <name>jbossInternalLifecycle</name>
+ <parameter>
+ <description>The lifecycle operation</description>
+ <name>method</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+
+ <!-- SubDeployerMBean operations -->
+ <operation>
+ <description>Accept a module for deployment</description>
+ <name>accepts</name>
+ <parameter>
+ <name>info</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ <return-type>boolean</return-type>
+ </operation>
+
+ <operation>
+ <description>Initialize deployment step</description>
+ <name>init</name>
+ <parameter>
+ <name>info</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ </operation>
+
+ <operation>
+ <description>Create deployment step</description>
+ <name>create</name>
+ <parameter>
+ <name>info</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ </operation>
+
+ <operation>
+ <description>Start deployment step</description>
+ <name>start</name>
+ <parameter>
+ <name>info</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ </operation>
+
+ <operation>
+ <description>Stop deployment step</description>
+ <name>stop</name>
+ <parameter>
+ <name>info</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ </operation>
+
+ <operation>
+ <description>Destroy deployment step</description>
+ <name>destroy</name>
+ <parameter>
+ <name>info</name>
+ <type>org.jboss.deployment.DeploymentInfo</type>
+ </parameter>
+ </operation>
+
+ <!-- Interceptable operations -->
+ <operation>
+ <description>Add dynamically an operation interceptor</description>
+ <name>addOperationInterceptor</name>
+ <parameter>
+ <description>The Interceptor</description>
+ <name>interceptor</name>
+ <type>org.jboss.mx.interceptor.Interceptor</type>
+ </parameter>
+ </operation>
+
+ <operation>
+ <description>Remove dynamically an operation interceptor</description>
+ <name>removeOperationInterceptor</name>
+ <parameter>
+ <description>The Interceptor</description>
+ <name>interceptor</name>
+ <type>org.jboss.mx.interceptor.Interceptor</type>
+ </parameter>
+ </operation>
+ </xmbean>
+ <!-- Inline XMBean Descriptor END -->
+
+ <!-- A flag indicating if the deployer should validate the
+ ejb-jar.xml/jboss.xml descriptors and components
+ -->
+ <attribute name="VerifyDeployments">true</attribute>
+ <!-- A flag indicating if the xml parser should validate the descriptor
+ DTDs
+ -->
+ <attribute name="ValidateDTDs">false</attribute>
+ <!-- A flag indicating if the verifier should be verbose about its
+ operation
+ -->
+ <attribute name="VerifierVerbose">true</attribute>
+ <!-- Setting this to 'true' will cause all deployments
+ to fail when the Verifier detected a problem with the contained
+ Beans. If false, warnings/errors will be logged but the deployment
+ will not fail.
+ -->
+ <attribute name="StrictVerifier">true</attribute>
+
+ <!-- The EJBDeployer needs the JTA transaction manager service -->
+ <depends optional-attribute-name="TransactionManagerServiceName">jboss:service=TransactionManager</depends>
+ <!-- The dynamic class loading simple web server -->
+ <depends optional-attribute-name="WebServiceName">jboss:service=WebService</depends>
+
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/hsqldb-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/hsqldb-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/hsqldb-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,113 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- The Hypersonic embedded database JCA connection factory config -->
+
+<!-- $Id: hsqldb-ds.xml 39791 2006-01-10 18:14:42Z dimitris $ -->
+
+<datasources>
+ <local-tx-datasource>
+
+ <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
+ <!-- Datasources are not available outside the virtual machine -->
+ <jndi-name>DefaultDS</jndi-name>
+
+ <!-- For server mode db, allowing other processes to use hsqldb over tcp.
+ This requires the org.jboss.jdbc.HypersonicDatabase mbean.
+ <connection-url>jdbc:hsqldb:hsql://${jboss.bind.address}:1701</connection-url>
+ -->
+ <!-- For totally in-memory db, not saved when jboss stops.
+ The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
+ <connection-url>jdbc:hsqldb:.</connection-url>
+ -->
+ <!-- For in-process persistent db, saved when jboss stops.
+ The org.jboss.jdbc.HypersonicDatabase mbean is required for proper db shutdown
+ -->
+ <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB</connection-url>
+
+ <!-- The driver class -->
+ <driver-class>org.hsqldb.jdbcDriver</driver-class>
+
+ <!-- The login and password -->
+ <user-name>sa</user-name>
+ <password></password>
+
+ <!--example of how to specify class that determines if exception means connection should be destroyed-->
+ <!--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyExceptionSorter</exception-sorter-class-name-->
+
+ <!-- this will be run before a managed connection is removed from the pool for use by a client-->
+ <!--<check-valid-connection-sql>select * from something</check-valid-connection-sql> -->
+
+ <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
+ <min-pool-size>5</min-pool-size>
+
+ <!-- The maximum connections in a pool/sub-pool -->
+ <max-pool-size>20</max-pool-size>
+
+ <!-- The time before an unused connection is destroyed -->
+ <!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout after last use -->
+ <!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads on closed connections -->
+ <idle-timeout-minutes>0</idle-timeout-minutes>
+
+ <!-- sql to call when connection is created
+ <new-connection-sql>some arbitrary sql</new-connection-sql>
+ -->
+
+ <!-- sql to call on an existing pooled connection when it is obtained from pool
+ <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
+ -->
+
+ <!-- example of how to specify a class that determines a connection is valid before it is handed out from the pool
+ <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyValidConnectionChecker</valid-connection-checker-class-name>
+ -->
+
+ <!-- Whether to check all statements are closed when the connection is returned to the pool,
+ this is a debugging feature that should be turned off in production -->
+ <track-statements/>
+
+ <!-- Use the getConnection(user, pw) for logins
+ <application-managed-security/>
+ -->
+
+ <!-- Use the security domain defined in conf/login-config.xml -->
+ <security-domain>HsqlDbRealm</security-domain>
+
+ <!-- Use the security domain defined in conf/login-config.xml or the
+ getConnection(user, pw) for logins. The security domain takes precedence.
+ <security-domain-and-application>HsqlDbRealm</security-domain-and-application>
+ -->
+
+ <!-- HSQL DB benefits from prepared statement caching -->
+ <prepared-statement-cache-size>32</prepared-statement-cache-size>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>Hypersonic SQL</type-mapping>
+ </metadata>
+
+ <!-- When using in-process (standalone) mode -->
+ <depends>jboss:service=Hypersonic,database=localDB</depends>
+ <!-- Uncomment when using hsqldb in server mode
+ <depends>jboss:service=Hypersonic</depends>
+ -->
+ </local-tx-datasource>
+
+ <!-- Uncomment if you want hsqldb accessed over tcp (server mode)
+ <mbean code="org.jboss.jdbc.HypersonicDatabase"
+ name="jboss:service=Hypersonic">
+ <attribute name="Port">1701</attribute>
+ <attribute name="BindAddress">${jboss.bind.address}</attribute>
+ <attribute name="Silent">true</attribute>
+ <attribute name="Database">default</attribute>
+ <attribute name="Trace">false</attribute>
+ <attribute name="No_system_exit">true</attribute>
+ </mbean>
+ -->
+
+ <!-- For hsqldb accessed from jboss only, in-process (standalone) mode -->
+ <mbean code="org.jboss.jdbc.HypersonicDatabase"
+ name="jboss:service=Hypersonic,database=localDB">
+ <attribute name="Database">localDB</attribute>
+ <attribute name="InProcessMode">true</attribute>
+ </mbean>
+
+</datasources>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/META-INF/jboss-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/META-INF/jboss-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/META-INF/jboss-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE server>
+<!-- $Id: jboss-service.xml 26202 2004-11-29 16:54:36Z starksm $ -->
+
+<server>
+
+ <!-- The HTTP invoker service configration
+ -->
+ <mbean code="org.jboss.invocation.http.server.HttpInvoker"
+ name="jboss:service=invoker,type=http">
+ <!-- Use a URL of the form http://<hostname>:8080/invoker/EJBInvokerServlet
+ where <hostname> is InetAddress.getHostname value on which the server
+ is running.
+ -->
+ <attribute name="InvokerURLPrefix">http://</attribute>
+ <attribute name="InvokerURLSuffix">:8080/invoker/EJBInvokerServlet</attribute>
+ <attribute name="UseHostName">true</attribute>
+ </mbean>
+
+ <!-- Expose the Naming service interface via HTTP -->
+ <mbean code="org.jboss.invocation.http.server.HttpProxyFactory"
+ name="jboss:service=invoker,type=http,target=Naming">
+ <!-- The Naming service we are proxying -->
+ <attribute name="InvokerName">jboss:service=Naming</attribute>
+ <!-- Compose the invoker URL from the cluster node address -->
+ <attribute name="InvokerURLPrefix">http://</attribute>
+ <attribute name="InvokerURLSuffix">:8080/invoker/JMXInvokerServlet</attribute>
+ <attribute name="UseHostName">true</attribute>
+ <attribute name="ExportedInterface">org.jnp.interfaces.Naming</attribute>
+ <attribute name="JndiName"></attribute>
+ <attribute name="ClientInterceptors">
+ <interceptors>
+ <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.naming.interceptors.ExceptionInterceptor</interceptor>
+ <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
+ </interceptors>
+ </attribute>
+ </mbean>
+
+ <!-- Expose the Naming service interface via clustered HTTP. This maps
+ to the ReadOnlyJNDIFactory servlet URL
+ -->
+ <mbean code="org.jboss.invocation.http.server.HttpProxyFactory"
+ name="jboss:service=invoker,type=http,target=Naming,readonly=true">
+ <attribute name="InvokerName">jboss:service=Naming</attribute>
+ <attribute name="InvokerURLPrefix">http://</attribute>
+ <attribute name="InvokerURLSuffix">:8080/invoker/readonly/JMXInvokerServlet</attribute>
+ <attribute name="UseHostName">true</attribute>
+ <attribute name="ExportedInterface">org.jnp.interfaces.Naming</attribute>
+ <attribute name="JndiName"></attribute>
+ <attribute name="ClientInterceptors">
+ <interceptors>
+ <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.naming.interceptors.ExceptionInterceptor</interceptor>
+ <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
+ </interceptors>
+ </attribute>
+ </mbean>
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/InvokerServlet$GetCredentialAction.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/InvokerServlet$GetCredentialAction.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/InvokerServlet$GetPrincipalAction.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/InvokerServlet$GetPrincipalAction.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/InvokerServlet.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/InvokerServlet.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/NamingFactoryServlet.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/NamingFactoryServlet.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/ReadOnlyAccessFilter.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/classes/org/jboss/invocation/http/servlet/ReadOnlyAccessFilter.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/jboss-web.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/jboss-web.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/jboss-web.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,3 @@
+<jboss-web>
+ <security-domain>java:/jaas/jmx-console</security-domain>
+</jboss-web>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/web.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/web.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/web.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,174 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE web-app PUBLIC
+ "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
+ "http://java.sun.com/dtd/web-app_2_3.dtd">
+
+<!-- The http-invoker.sar/invoker.war web.xml descriptor
+$Id: web.xml 26202 2004-11-29 16:54:36Z starksm $
+-->
+<web-app>
+ <filter>
+ <filter-name>ReadOnlyAccessFilter</filter-name>
+ <filter-class>org.jboss.invocation.http.servlet.ReadOnlyAccessFilter</filter-class>
+ <init-param>
+ <param-name>readOnlyContext</param-name>
+ <param-value>readonly</param-value>
+ <description>The top level JNDI context the filter will enforce
+ read-only access on. If specified only Context.lookup operations
+ will be allowed on this context. Another other operations or lookups
+ on any other context will fail. Do not associate this filter with the
+ JMXInvokerServlets if you want unrestricted access.
+ </description>
+ </init-param>
+ <init-param>
+ <param-name>invokerName</param-name>
+ <param-value>jboss:service=Naming</param-value>
+ <description>The JMX ObjectName of the naming service mbean
+ </description>
+ </init-param>
+ </filter>
+
+ <filter-mapping>
+ <filter-name>ReadOnlyAccessFilter</filter-name>
+ <url-pattern>/readonly/*</url-pattern>
+ </filter-mapping>
+
+<!-- ### Servlets -->
+ <servlet>
+ <servlet-name>EJBInvokerServlet</servlet-name>
+ <description>The EJBInvokerServlet receives posts containing serlized
+ MarshalledInvocation objects that are routed to the EJB invoker given by
+ the invokerName init-param. The return content is a serialized
+ MarshalledValue containg the return value of the inovocation, or any
+ exception that may have been thrown.
+ </description>
+ <servlet-class>org.jboss.invocation.http.servlet.InvokerServlet</servlet-class>
+ <init-param>
+ <param-name>invokerName</param-name>
+ <param-value>jboss:service=invoker,type=http</param-value>
+ <description>The RMI/HTTP EJB compatible invoker</description>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+ <servlet>
+ <servlet-name>JMXInvokerServlet</servlet-name>
+ <description>The JMXInvokerServlet receives posts containing serlized
+ MarshalledInvocation objects that are routed to the invoker given by
+ the the MBean whose object name hash is specified by the
+ invocation.getObjectName() value. The return content is a serialized
+ MarshalledValue containg the return value of the inovocation, or any
+ exception that may have been thrown.
+ </description>
+ <servlet-class>org.jboss.invocation.http.servlet.InvokerServlet</servlet-class>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>JNDIFactory</servlet-name>
+ <description>A servlet that exposes the JBoss JNDI Naming service stub
+ through http. The return content is a serialized
+ MarshalledValue containg the org.jnp.interfaces.Naming stub. This
+ configuration handles requests for the standard JNDI naming service.
+ </description>
+ <servlet-class>org.jboss.invocation.http.servlet.NamingFactoryServlet</servlet-class>
+ <init-param>
+ <param-name>namingProxyMBean</param-name>
+ <param-value>jboss:service=invoker,type=http,target=Naming</param-value>
+ </init-param>
+ <init-param>
+ <param-name>proxyAttribute</param-name>
+ <param-value>Proxy</param-value>
+ </init-param>
+ <load-on-startup>2</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>ReadOnlyJNDIFactory</servlet-name>
+ <description>A servlet that exposes the JBoss JNDI Naming service stub
+ through http, but only for a single read-only context. The return content
+ is a serialized MarshalledValue containg the org.jnp.interfaces.Naming
+ stub.
+ </description>
+ <servlet-class>org.jboss.invocation.http.servlet.NamingFactoryServlet</servlet-class>
+ <init-param>
+ <param-name>namingProxyMBean</param-name>
+ <param-value>jboss:service=invoker,type=http,target=Naming,readonly=true</param-value>
+ </init-param>
+ <init-param>
+ <param-name>proxyAttribute</param-name>
+ <param-value>Proxy</param-value>
+ </init-param>
+ <load-on-startup>2</load-on-startup>
+ </servlet>
+
+<!-- ### Servlet Mappings -->
+ <servlet-mapping>
+ <servlet-name>JNDIFactory</servlet-name>
+ <url-pattern>/JNDIFactory/*</url-pattern>
+ </servlet-mapping>
+ <!-- A mapping for the NamingFactoryServlet that only allows invocations
+ of lookups under a read-only context. This is enforced by the
+ ReadOnlyAccessFilter
+ -->
+ <servlet-mapping>
+ <servlet-name>ReadOnlyJNDIFactory</servlet-name>
+ <url-pattern>/ReadOnlyJNDIFactory/*</url-pattern>
+ </servlet-mapping>
+ <servlet-mapping>
+ <servlet-name>EJBInvokerServlet</servlet-name>
+ <url-pattern>/EJBInvokerServlet/*</url-pattern>
+ </servlet-mapping>
+ <servlet-mapping>
+ <servlet-name>JMXInvokerServlet</servlet-name>
+ <url-pattern>/JMXInvokerServlet/*</url-pattern>
+ </servlet-mapping>
+ <!-- A mapping for the JMXInvokerServlet that only allows invocations
+ of lookups under a read-only context. This is enforced by the
+ ReadOnlyAccessFilter
+ -->
+ <servlet-mapping>
+ <servlet-name>JMXInvokerServlet</servlet-name>
+ <url-pattern>/readonly/JMXInvokerServlet/*</url-pattern>
+ </servlet-mapping>
+
+ <!-- Alternate mappings that place the servlets under the restricted
+ path to required authentication for access. Remove the unsecure mappings
+ if only authenticated users should be allowed.
+ -->
+ <servlet-mapping>
+ <servlet-name>JNDIFactory</servlet-name>
+ <url-pattern>/restricted/JNDIFactory/*</url-pattern>
+ </servlet-mapping>
+ <servlet-mapping>
+ <servlet-name>JMXInvokerServlet</servlet-name>
+ <url-pattern>/restricted/JMXInvokerServlet/*</url-pattern>
+ </servlet-mapping>
+
+ <!-- An example security constraint that restricts access to the HTTP invoker
+ to users with the role HttpInvoker Edit the roles to what you want and
+ configure the WEB-INF/jboss-web.xml/security-domain element to reference
+ the security domain you want.
+ -->
+ <security-constraint>
+ <web-resource-collection>
+ <web-resource-name>HttpInvokers</web-resource-name>
+ <description>An example security config that only allows users with the
+ role HttpInvoker to access the HTTP invoker servlets
+ </description>
+ <url-pattern>/restricted/*</url-pattern>
+ <http-method>GET</http-method>
+ <http-method>POST</http-method>
+ </web-resource-collection>
+ <auth-constraint>
+ <role-name>HttpInvoker</role-name>
+ </auth-constraint>
+ </security-constraint>
+ <login-config>
+ <auth-method>BASIC</auth-method>
+ <realm-name>JBoss HTTP Invoker</realm-name>
+ </login-config>
+
+ <security-role>
+ <role-name>HttpInvoker</role-name>
+ </security-role>
+</web-app>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/META-INF/jboss-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/META-INF/jboss-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/META-INF/jboss-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: jboss-service.xml 44143 2006-04-24 18:19:21Z kkhan $ -->
+
+<!-- ===================================================================== -->
+<!-- JBoss Server Configuration -->
+<!-- ===================================================================== -->
+
+<server>
+
+ <!-- The code for the service is different for the different run scenarios
+ *** JBoss 4.0
+ * JDK 1.4 - org.jboss.aop.deployment.AspectManagerService
+ * JDK 5 (not using -javaagent switch) - org.jboss.aop.deployment.AspectManagerService
+ * JDK 5 (using -javaagent switch) - org.jboss.aop.deployment.AspectManagerServiceJDK5
+ * BEA JRockit 1.4.2 - org.jboss.aop.deployment.AspectManagerService
+ *** JBoss 3.2
+ * JDK 1.4 - org.jboss.aop.deployment.AspectManagerService32
+ * JDK 5 (not using -javaagent switch) - org.jboss.aop.deployment.AspectManagerService32
+ * JDK 5 (using -javaagent switch) - org.jboss.aop.deployment.AspectManagerService32JDK5
+ * BEA JRockit 1.4.2 - org.jboss.aop.deployment.AspectManagerService32
+ -->
+ <mbean code="org.jboss.aop.deployment.AspectManagerServiceJDK5"
+ name="jboss.aop:service=AspectManager">
+ <attribute name="EnableLoadtimeWeaving">false</attribute>
+ <!-- only relevant when EnableLoadtimeWeaving is true.
+ When transformer is on, every loaded class gets
+ transformed. If AOP can't find the class, then it
+ throws an exception. Sometimes, classes may not have
+ all the classes they reference. So, the Suppressing
+ is needed. (i.e. Jboss cache in the default configuration -->
+ <attribute name="SuppressTransformationErrors">true</attribute>
+ <attribute name="Prune">true</attribute>
+ <attribute name="Include">org.jboss.test, org.jboss.injbossaop</attribute>
+ <attribute name="Exclude">org.jboss.</attribute>
+ <!-- This avoids instrumentation of hibernate cglib enhanced proxies
+ <attribute name="Ignore">*$$EnhancerByCGLIB$$*</attribute> -->
+ <attribute name="Optimized">true</attribute>
+ <attribute name="Verbose">false</attribute>
+ </mbean>
+
+ <mbean code="org.jboss.aop.deployment.AspectDeployer"
+ name="jboss.aop:service=AspectDeployer">
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/base-aop.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/base-aop.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/base-aop.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,133 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE aop PUBLIC
+ "-//JBoss//DTD JBOSS AOP 1.0//EN"
+ "http://labs.jboss.com/portal/jbossaop/dtd/jboss-aop_1_0.dtd">
+
+<aop>
+ <!-- custom configuration for AOP Security -->
+ <metadata-loader tag="security" class="org.jboss.aspects.security.SecurityClassMetaDataLoader"/>
+
+ <stack name="J2EESecurityStack">
+ <interceptor factory="org.jboss.aspects.security.AuthenticationInterceptorFactory" scope="PER_CLASS"/>
+ <interceptor factory="org.jboss.aspects.security.RoleBasedAuthorizationInterceptorFactory" scope="PER_CLASS"/>
+ <interceptor factory="org.jboss.aspects.security.RunAsSecurityInterceptorFactory" scope="PER_CLASS"/>
+ </stack>
+
+ <bind pointcut="all(@security)">
+ <stack-ref name="J2EESecurityStack"/>
+ </bind>
+
+ <bind pointcut="all(@org.jboss.aspects.security.Permissions)">
+ <stack-ref name="J2EESecurityStack"/>
+ </bind>
+
+ <bind pointcut="all(@org.jboss.aspects.security.Unchecked)">
+ <stack-ref name="J2EESecurityStack"/>
+ </bind>
+
+ <bind pointcut="all(@org.jboss.aspects.security.Exclude)">
+ <stack-ref name="J2EESecurityStack"/>
+ </bind>
+
+ <introduction expr="class(@org.jboss.aspects.jmx.MBean)">
+ <mixin>
+ <interfaces>javax.management.DynamicMBean</interfaces>
+ <class>org.jboss.aspects.jmx.JmxIntrospectingMixin</class>
+ <construction>new org.jboss.aspects.jmx.JmxIntrospectingMixin(this)</construction>
+ </mixin>
+ </introduction>
+
+ <!-- asynchronous aspect -->
+ <aspect class="org.jboss.aspects.asynch.AsynchAspect" scope="PER_INSTANCE">
+ <advisor-attribute name="Advisor"/>
+ </aspect>
+
+ <bind pointcut="execution(!static * *->@org.jboss.aspects.asynch.Asynchronous(..))">
+ <advice name="execute" aspect="org.jboss.aspects.asynch.AsynchAspect"/>
+ </bind>
+
+ <introduction expr="has(!static * *->@org.jboss.aspects.asynch.Asynchronous(..))">
+ <mixin>
+ <interfaces>org.jboss.aspects.asynch.AsynchProvider,org.jboss.aspects.asynch.FutureHolder</interfaces>
+ <class>org.jboss.aspects.asynch.AsynchMixin</class>
+ </mixin>
+ </introduction>
+
+ <!-- old asynch aspect from Claude -->
+
+ <aspect class="org.jboss.aspects.asynchronous.aspects.jboss.AsynchronousAspect" scope="PER_VM"/>
+
+ <bind pointcut="execution(* *->@org.jboss.aspects.asynchronous.aspects.jboss.Asynchronous(..))">
+ <advice name="execute" aspect="org.jboss.aspects.asynchronous.aspects.jboss.AsynchronousAspect"/>
+ </bind>
+
+ <introduction expr="has(* *->@org.jboss.aspects.asynchronous.aspects.jboss.Asynchronous(..)) OR class(@org.jboss.aspects.asynchronous.aspects.jboss.Asynchronous)">
+
+ <mixin>
+ <interfaces>
+ org.jboss.aspects.asynchronous.aspects.AsynchronousFacade
+ </interfaces>
+ <class>org.jboss.aspects.asynchronous.aspects.AsynchronousFacadeImpl</class>
+ <construction>new org.jboss.aspects.asynchronous.aspects.AsynchronousFacadeImpl()</construction>
+ </mixin>
+ </introduction>
+
+ <!-- TRANSACTIONS -->
+ <interceptor class="org.jboss.aspects.tx.TxPropagationInterceptor" scope="PER_VM"/>
+ <interceptor factory="org.jboss.aspects.tx.TxInterceptorFactory" scope="PER_CLASS_JOINPOINT"/>
+
+ <bind pointcut="all(@transaction)">
+ <interceptor-ref name="org.jboss.aspects.tx.TxInterceptorFactory"/>
+ </bind>
+
+ <interceptor name="class-txsynchronized" factory="org.jboss.aspects.txlock.TxLockInterceptorFactory" scope="PER_CLASS"/>
+ <interceptor name="instance-txsynchronized" factory="org.jboss.aspects.txlock.TxLockInterceptorFactory" scope="PER_INSTANCE"/>
+
+ <bind pointcut="execution(static * *->@TxSynchronized(..)) OR execution(*->@TxSynchronized(..))">
+ <interceptor-ref name="class-txsynchronized"/>
+ </bind>
+
+ <bind pointcut="execution(!static * *->@TxSynchronized(..))">
+ <interceptor-ref name="instance-txsynchronized"/>
+ </bind>
+
+ <bind pointcut="all(@org.jboss.aspects.tx.Tx)">
+ <interceptor-ref name="org.jboss.aspects.tx.TxInterceptorFactory"/>
+ </bind>
+
+ <bind pointcut="execution(static * *->@org.jboss.aspects.txlock.TxSynchronized(..)) OR execution(*->@org.jboss.aspects.txlock.TxSynchronized(..))">
+ <interceptor-ref name="class-txsynchronized"/>
+ </bind>
+
+ <bind pointcut="execution(!static * *->@org.jboss.aspects.txlock.TxSynchronized(..))">
+ <interceptor-ref name="instance-txsynchronized"/>
+ </bind>
+
+ <!-- injection -->
+ <aspect class="org.jboss.aspects.tx.TransactionInjector"/>
+ <aspect class="org.jboss.aspects.tx.TransactionManagerInjector"/>
+
+ <bind pointcut="field(javax.transaction.Transaction *->@org.jboss.aspects.Current)">
+ <advice name="access" aspect="org.jboss.aspects.tx.TransactionInjector"/>
+ </bind>
+
+ <bind pointcut="field(javax.transaction.TransactionManager *->@org.jboss.aspects.Injected)">
+ <advice name="access" aspect="org.jboss.aspects.tx.TransactionManagerInjector"/>
+ </bind>
+
+ <bind pointcut="execution(*->new(..)) AND hasfield(javax.transaction.TransactionManager *->@org.jboss.aspects.Injected)">
+ <advice name="allocation" aspect="org.jboss.aspects.tx.TransactionManagerInjector"/>
+ </bind>
+
+ <!-- special types -->
+ <aspect class="org.jboss.aspects.ThreadbasedAspect" scope="PER_JOINPOINT"/>
+ <bind pointcut="field(* *->@org.jboss.aspects.Threadbased)">
+ <advice name="access" aspect="org.jboss.aspects.ThreadbasedAspect"/>
+ </bind>
+
+ <aspect class="org.jboss.aspects.tx.TransactionLocalAspect" scope="PER_JOINPOINT"/>
+ <bind pointcut="field(* *->@org.jboss.aspects.tx.TxLocal)">
+ <advice name="access" aspect="org.jboss.aspects.tx.TransactionLocalAspect"/>
+ </bind>
+
+</aop>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aspect-library-jdk50.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aspect-library-jdk50.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/trove.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-aop-jdk50.deployer/trove.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/META-INF/jboss-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/META-INF/jboss-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/META-INF/jboss-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<server>
+
+ <!--
+ The JBoss Bean Deployer
+ -->
+ <mbean code="org.jboss.kernel.deployment.jboss.JBossBeanDeployer"
+ name="jboss.bean:service=JBossBeanDeployer">
+
+ <attribute name="Extension">.beans</attribute>
+ <attribute name="MetaDataURL">META-INF/jboss-beans.xml</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-bean-deployer.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-bean-deployer.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-container.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-container.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-dependency.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-dependency.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-microcontainer.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-bean.deployer/jboss-microcontainer.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-ha-local-jdbc.rar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-ha-local-jdbc.rar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-ha-xa-jdbc.rar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-ha-xa-jdbc.rar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-local-jdbc.rar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-local-jdbc.rar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/META-INF/jboss-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/META-INF/jboss-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/META-INF/jboss-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,175 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: jboss-service.xml 60489 2007-02-12 08:22:28Z scott.stark at jboss.org $ -->
+<server>
+
+ <!-- JBossWeb Service-->
+ <mbean code="org.jboss.web.tomcat.service.JBossWeb"
+ name="jboss.web:service=WebServer" xmbean-dd="META-INF/webserver-xmbean.xml">
+
+ <!-- You can configure a set of authenticators keyed by http-auth method used. This
+ will apply the same set of authenticators across all web applications. You can
+ override the set of authenticators at the web application level by adding
+ <authenticators> element to the respective jboss-web.xml -->
+ <!--
+ -->
+ <attribute name="Authenticators" serialDataType="jbxb">
+ <java:properties xmlns:java="urn:jboss:java-properties"
+ xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
+ xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
+ <java:property>
+ <java:key>BASIC</java:key>
+ <java:value>org.apache.catalina.authenticator.BasicAuthenticator</java:value>
+ </java:property>
+ <java:property>
+ <java:key>CLIENT-CERT</java:key>
+ <java:value>org.apache.catalina.authenticator.SSLAuthenticator</java:value>
+ </java:property>
+ <java:property>
+ <java:key>DIGEST</java:key>
+ <java:value>org.apache.catalina.authenticator.DigestAuthenticator</java:value>
+ </java:property>
+ <java:property>
+ <java:key>FORM</java:key>
+ <java:value>org.apache.catalina.authenticator.FormAuthenticator</java:value>
+ </java:property>
+ <java:property>
+ <java:key>NONE</java:key>
+ <java:value>org.apache.catalina.authenticator.NonLoginAuthenticator</java:value>
+ </java:property>
+ </java:properties>
+ </attribute>
+
+ <!-- The JAAS security domain to use in the absense of an explicit
+ security-domain specification in the war WEB-INF/jboss-web.xml
+ -->
+ <attribute name="DefaultSecurityDomain">java:/jaas/other</attribute>
+
+ <!-- Get the flag indicating if the normal Java2 parent first class
+ loading model should be used over the servlet 2.3 web container first
+ model.
+ -->
+ <attribute name="Java2ClassLoadingCompliance">false</attribute>
+ <!-- A flag indicating if the JBoss Loader should be used. This loader
+ uses a unified class loader as the class loader rather than the tomcat
+ specific class loader.
+ The default is false to ensure that wars have isolated class loading
+ for duplicate jars and jsp files.
+ -->
+ <attribute name="UseJBossWebLoader">false</attribute>
+ <!-- The list of package prefixes that should not be loaded without
+ delegating to the parent class loader before trying the web app
+ class loader. The packages listed here are those tha are used by
+ the web container implementation and cannot be overriden. The format
+ is a comma separated list of the package names. There cannot be any
+ whitespace between the package prefixes.
+ This setting only applies when UseJBossWebLoader=false.
+ -->
+ <attribute name="FilteredPackages">javax.servlet</attribute>
+
+ <attribute name="LenientEjbLink">true</attribute>
+
+ <!--Flag to delete the Work Dir on Context Destroy -->
+ <attribute name="DeleteWorkDirOnContextDestroy">false</attribute>
+
+ <!--
+ Class of the session manager (used if context is marked as 'distributable'. Currently allowed values:
+ - org.jboss.web.tomcat.service.session.JBossCacheManager
+ -->
+ <attribute name="ManagerClass">org.jboss.web.tomcat.service.session.JBossCacheManager</attribute>
+
+ <!-- The name of the request attribute under with the authenticated JAAS
+ Subject is stored on successful authentication. If null or empty then
+ the Subject will not be stored.
+ -->
+ <!--
+ <attribute name="SubjectAttributeName">j_subject</attribute>
+ -->
+
+ <!-- The SessionIdAlphabet is the set of characters used to create a session Id
+ It must be made up of exactly 65 unique characters
+ <attribute name="SessionIdAlphabet">ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+-*</attribute>
+ -->
+
+ <!--
+ *******************************************************
+ ****************** CLUSTERING *************************
+ *******************************************************
+ In order to activate HTTP Session clustering for Tomcat
+ make sure you run JBoss's "all" configuration i.e.
+ "run -c all"
+ (the default configuration doesn't contain clustering)
+
+ Furthermore, you may change SnapshotMode and
+ SnapshotInterval attributes below to indicate when to
+ synchronize changes with the other node(s).
+
+ If you use Apache+mod_jk(2) you will most probably use
+ the AJP1.3 connector below. Thus, if you so wish,
+ you may comment (i.e. deactivate) the HTTP connector
+ as it won't be used anymore.
+
+ *******************************************************
+ *******************************************************
+ *******************************************************
+ -->
+
+ <!--
+ If you are using clustering, the following two attributes
+ define when the sessions are replicated to the other nodes.
+ The default value, "instant", synchronously replicates changes
+ to the other nodes at the end of requests. In this case, the
+ "SnapshotInterval" attribute is not used.
+ The "interval" mode, in association with the "SnapshotInterval"
+ attribute, indicates that modified sessions will only be replicated
+ every "SnapshotInterval" milliseconds at most.
+
+ Note that this attribute is not in effect if the replication-granularity
+ is set to FIELD. If it is FIELD, it will be per http request (that is,
+ "instant" mode.)
+ -->
+ <attribute name="SnapshotMode">instant</attribute> <!-- you may switch to "interval" -->
+ <attribute name="SnapshotInterval">2000</attribute>
+
+ <!--
+ Whether to use MOD_JK(2) for load balancing with sticky session
+ combined with JvmRoute. If set to true, it will insert a JvmRouteFilter
+ to intercept every request and replace the JvmRoute if it detects a
+ failover. In addition, you will need to set the JvmRoute inside
+ Tomcat, e.g.,
+ Engine name="jboss.web" jmvRoute="Node1" defaultHost="localhost"
+ in server.xml.
+
+ For clustering purpose only.
+ -->
+ <attribute name="UseJK">false</attribute>
+
+ <attribute name="Domain">jboss.web</attribute>
+
+ <!-- A mapping to the server security manager service which must be
+ operation compatible with type
+ org.jboss.security.plugins.JaasSecurityManagerServiceMBean. This is only
+ needed if web applications are allowed to flush the security manager
+ authentication cache when the web sessions invalidate.
+ -->
+ <depends optional-attribute-name="SecurityManagerService"
+ proxy-type="attribute">jboss.security:service=JaasSecurityManager
+ </depends>
+
+ <!--
+ Needed if using HTTP Session Clustering or if the
+ ClusteredSingleSignOn valve is enabled in the tomcat server.xml file
+ -->
+ <!--
+ <depends>jboss.cache:service=TomcatClusteringCache</depends>
+ -->
+
+ <depends>jboss:service=TransactionManager</depends>
+
+ <!-- Only needed if the org.jboss.web.tomcat.service.jca.CachedConnectionValve
+ is enabled in the tomcat server.xml file.
+ -->
+ <depends>jboss.jca:service=CachedConnectionManager</depends>
+
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/META-INF/webserver-xmbean.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/META-INF/webserver-xmbean.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/META-INF/webserver-xmbean.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,190 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE mbean PUBLIC
+ "-//JBoss//DTD JBOSS XMBEAN 1.2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss_xmbean_1_2.dtd">
+<!--
+ JBoss Web XMBean descriptor
+
+ $Id: webserver-xmbean.xml 59833 2007-01-19 15:45:42Z dimitris at jboss.org $
+-->
+<mbean>
+ <description>The JBoss Web Deployer responsible for war deployment</description>
+ <descriptors>
+ <interceptors>
+ <!-- comment out DynamicInterceptor to disable dynamic addition of interceptors -->
+ <interceptor code="org.jboss.mx.interceptor.DynamicInterceptor"/>
+ </interceptors>
+ </descriptors>
+ <class>org.jboss.web.tomcat.service.JBossWeb</class>
+
+ <!-- JBossWebMBean attributes -->
+
+ <attribute access="read-write" getMethod="getAuthenticators" setMethod="setAuthenticators">
+ <name>Authenticators</name>
+ <type>java.util.Properties</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getUseJBossWebLoader" setMethod="setUseJBossWebLoader">
+ <name>UseJBossWebLoader</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getAllowSelfPrivilegedWebApps" setMethod="setAllowSelfPrivilegedWebApps">
+ <name>AllowSelfPrivilegedWebApps</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getDeleteWorkDirOnContextDestroy"
+ setMethod="setDeleteWorkDirOnContextDestroy">
+ <name>DeleteWorkDirOnContextDestroy</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getHttpHeaderForSSOAuth"
+ setMethod="setHttpHeaderForSSOAuth">
+ <name>HttpHeaderForSSOAuth</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getSessionCookieForSSOAuth"
+ setMethod="setSessionCookieForSSOAuth">
+ <name>SessionCookieForSSOAuth</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getSubjectAttributeName" setMethod="setSubjectAttributeName">
+ <name>SubjectAttributeName</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getCacheName" setMethod="setCacheName">
+ <name>CacheName</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getUnpackWars" setMethod="setUnpackWars">
+ <name>UnpackWars</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getAcceptNonWarDirs" setMethod="setAcceptNonWarDirs">
+ <name>AcceptNonWarDirs</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getConfig" setMethod="setConfig">
+ <name>Config</name>
+ <type>org.w3c.dom.Element</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getLenientEjbLink" setMethod="setLenientEjbLink">
+ <name>LenientEjbLink</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="isUseJK" setMethod="setUseJK">
+ <name>UseJK</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getDomain" setMethod="setDomain">
+ <name>Domain</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getFilteredPackages" setMethod="setFilteredPackages">
+ <name>FilteredPackages</name>
+ <type>[Ljava.lang.String;</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getJava2ClassLoadingCompliance" setMethod="setJava2ClassLoadingCompliance">
+ <name>Java2ClassLoadingCompliance</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getDefaultSecurityDomain" setMethod="setDefaultSecurityDomain">
+ <name>DefaultSecurityDomain</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getSnapshotMode" setMethod="setSnapshotMode">
+ <name>SnapshotMode</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getSnapshotInterval" setMethod="setSnapshotInterval">
+ <name>SnapshotInterval</name>
+ <type>int</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getConfigFile" setMethod="setConfigFile">
+ <name>ConfigFile</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getUseLocalCache" setMethod="setUseLocalCache">
+ <name>UseLocalCache</name>
+ <type>boolean</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getSessionIdAlphabet" setMethod="setSessionIdAlphabet">
+ <name>SessionIdAlphabet</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getContextMBeanCode" setMethod="setContextMBeanCode">
+ <name>ContextMBeanCode</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-write" getMethod="getManagerClass" setMethod="setManagerClass">
+ <name>ManagerClass</name>
+ <type>java.lang.String</type>
+ </attribute>
+
+ <attribute access="read-only" getMethod="getDeployedApplications">
+ <name>DeployedApplications</name>
+ <type>java.util.Iterator</type>
+ </attribute>
+
+ <attribute access="write-only" setMethod="setSecurityManagerService">
+ <name>SecurityManagerService</name>
+ <type>org.jboss.security.plugins.JaasSecurityManagerServiceMBean</type>
+ </attribute>
+
+ <!-- SubDeployerExt attribute -->
+ <attribute access="read-write" getMethod="getEnhancedSuffixes" setMethod="setEnhancedSuffixes">
+ <description>Allow the override of supported suffixes and relative order</description>
+ <name>EnhancedSuffixes</name>
+ <type>[Ljava.lang.String;</type>
+ </attribute>
+
+ &deployerAttributes;
+ &defaultAttributes;
+
+ <!-- JBossWebMBean operations -->
+ <operation>
+ <description>See if a war is deployed</description>
+ <name>isDeployed</name>
+ <parameter>
+ <name>warUrl</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>boolean</return-type>
+ </operation>
+
+ <operation>
+ <description>Start all connectors of the Domain</description>
+ <name>startConnectors</name>
+ </operation>
+
+ <operation>
+ <description>Stop all connectors of the Domain</description>
+ <name>stopConnectors</name>
+ </operation>
+
+ &deployerOperations;
+ &defaultOperations;
+ &interceptable;
+
+</mbean>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/WEB-INF/web.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/WEB-INF/web.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/WEB-INF/web.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!DOCTYPE web-app
+ PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
+ "http://java.sun.com/dtd/web-app_2_3.dtd">
+
+<web-app>
+ <display-name>Welcome to JBoss</display-name>
+ <description>
+ Welcome to JBoss
+ </description>
+ <servlet>
+ <servlet-name>Status Servlet</servlet-name>
+ <servlet-class>org.jboss.web.tomcat.service.StatusServlet</servlet-class>
+ </servlet>
+ <servlet-mapping>
+ <servlet-name>Status Servlet</servlet-name>
+ <url-pattern>/status</url-pattern>
+ </servlet-mapping>
+</web-app>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/favicon.ico
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/favicon.ico
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/index.html
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/index.html (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/index.html 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <title>Welcome to JBoss™</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link rel="StyleSheet" href="jboss.css" type="text/css"/>
+</head>
+
+<body>
+<!-- header begin -->
+ <a href="http://www.jboss.org">
+ <img src="logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ </a>
+ <div id="header"> </div>
+ <div id="navigation_bar"></div>
+<!-- header end -->
+
+ <h3>JBoss Online Resources</h3>
+ <ul>
+ <li><a href="http://www.jboss.org/products/jbossas/docs">JBoss Documentation</a></li>
+ <li><a href="http://wiki.jboss.org/">JBoss Wiki</a></li>
+ <li><a href="http://jira.jboss.org/">JBoss JIRA</a></li>
+ <li><a href="http://www.jboss.org/index.html?module=bb">JBoss Forums</a></li>
+ </ul>
+
+ <h3>JBoss Management</h3>
+ <ul>
+ <li><a href="/status">Tomcat status</a>
+ <a href="/status?full=true">(full)</a>
+ <a href="/status?XML=true">(XML)</a></li>
+ <li><a href="/jmx-console/">JMX Console</a></li>
+ <li><a href="/web-console/">JBoss Web Console</a></li>
+ </ul>
+
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Application Server</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/jboss.css
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/jboss.css (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/jboss.css 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,143 @@
+body {
+ margin: 13px 0px 10px 0px;
+ background-color: #ffffff;
+ font-size: 10px;
+ font-family: verdana, arial, "sans-serif";
+ color: #606060;
+ }
+img {
+ border: 0px;
+ }
+#header {
+ background-color: #003D6E;
+ background-repeat: no-repeat;
+ width: 100%;
+ height: 80px;
+ }
+#header #banner {
+ float: right;
+ margin: 8px 5px 0px 0px;
+ }
+#logo {
+ position: absolute;
+ top: 2px;
+ left: 4px;
+ z-index: 200;
+}
+#navigation_bar {
+ background-color: #f0f0f0;
+ border-bottom: 1px dotted #999999;
+ height: 20px;
+ }
+#items {
+ font-size: 12px;
+ width: 600px;
+ margin: 5px 5px 5px 170px;
+ position: relative;
+ z-index: 300;
+ }
+#items .item {
+ margin-right: 10px;
+ }
+.side_block {
+ margin: 15px 5px 10px 5px;
+ background-color: #fbfbfb;
+ border: 1px solid #f0f0f0;
+ }
+.side_block h3 {
+ font-size: 11px;
+ font-weight: 100;
+ width: 100%;
+ margin: 0px 0px 5px 0px;
+ padding: 4px 4px 4px 10x;
+ background-color: #f0f0f0;
+ }
+.side_block h4 {
+ font-size: 11px;
+ color: #003D6E;
+ font-weight: bold;
+ margin: 10px 5px 4px 5px;
+ }
+.side_block p {
+ margin: 5px 5px 3px 5px;
+ }
+.side_block form {
+ margin: 0px 0px 0px 5px;
+ }
+.side_block #login {
+ font-size: 9px;
+ }
+.side_block p img {
+ text-align: center;
+ }
+#content {
+ width: 90%;
+ margin: 10px auto;
+ }
+#left {
+ float: left;
+ width: 14%;
+ }
+#right {
+ float: right;
+ width: 14%;
+ }
+.content_block {
+ text-align: justify;
+ border: 1px solid #999999;
+ margin: 5px;
+ width: 31%;
+ float: left;
+ }
+.content_block p {
+ margin: 0px 5px 3px 5px;
+ }
+.content_block h3 {
+ font-size: 11px;
+ font-weight: bold;
+ color: #000000;
+ margin: 0px 0px 5px 0px;
+ padding: 4px 4px 4px 4x;
+ text-align: center;
+ background-color: #f0f0f0;
+ border-bottom: 1px solid #999999
+ }
+.content_block h4 {
+ font-size: 11px;
+ color: #003D6E;
+ text-align: left;
+ font-weight: bold;
+ margin: 10px 5px 4px 5px;
+ }
+#footer {
+ clear: both;
+ border-top: 1px dotted #999999;
+ }
+#credits {
+ background-color: #f0f0f0;
+ padding: 5px;
+ text-align: center;
+ }
+#footer_bar {
+ height: 20px;
+ width: 100%;
+ background-color: #003D6E;
+ }
+.hide {
+ display: none;
+ }
+.spacer {
+ clear: both;
+ }
+.spacer hr {
+ display: none;
+ }
+.center {
+ text-align: center;
+ }
+#youcandoit {
+ background-image: url("youcandoit.jpg");
+ background-repeat: repeat-x;
+ height: 165px;
+ margin: 0px 30px 0px 30px;
+ }
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/logo.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/logo.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/manager/xform.xsl
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/manager/xform.xsl (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/ROOT.war/manager/xform.xsl 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,96 @@
+<?xml version="1.0"?>
+
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ version="1.0">
+
+ <!-- Output method -->
+ <xsl:output encoding="iso-8859-1"
+ indent="no"/>
+
+ <xsl:template match="status">
+ <html>
+ <head>
+ <TITLE>Tomcat Status</TITLE>
+ <STYLE type="text/css">
+ body, table, tr, td, a, div, span {
+ vertical-align : top;
+ }
+ </STYLE>
+ </head>
+ <body>
+ <div style='font-size:20px;'>Tomcat Status</div>
+
+ <xsl:apply-templates select="jvm"/>
+ <xsl:apply-templates select="connector"/>
+ </body>
+ </html>
+ </xsl:template>
+
+ <xsl:template match="jvm">
+ <xsl:apply-templates select="memory"/>
+ </xsl:template>
+
+ <xsl:template match="memory">
+ <table><tr>
+ <td><b>JVM:</b></td>
+ <td><b>free:</b> <xsl:value-of select="@free"/></td>
+ <td><b>total:</b> <xsl:value-of select="@total"/></td>
+ <td><b>max:</b> <xsl:value-of select="@max"/></td>
+ </tr>
+ </table><hr />
+ </xsl:template>
+
+ <xsl:template match="connector">
+ <b>Connector -- </b> <xsl:value-of select="@name"/><br />
+
+ <xsl:apply-templates select="threadInfo"/>
+ <xsl:apply-templates select="requestInfo"/>
+ <xsl:apply-templates select="workers"/>
+ </xsl:template>
+
+ <xsl:template match="threadInfo">
+ <table><tr>
+ <td><b>threadInfo </b></td>
+ <td><b>maxThreads:</b> <xsl:value-of select="@maxThreads"/></td>
+ <td><b>minSpareThreads:</b> <xsl:value-of select="@minSpareThreads"/></td>
+ <td><b>maxSpareThreads:</b> <xsl:value-of select="@maxSpareThreads"/></td>
+ <td><b>currentThreadCount:</b> <xsl:value-of select="@currentThreadCount"/></td>
+ <td><b>currentThreadsBusy:</b> <xsl:value-of select="@currentThreadsBusy"/></td>
+ </tr>
+ </table><hr />
+ </xsl:template>
+
+ <xsl:template match="requestInfo">
+ <table><tr>
+ <td><b>requestInfo </b></td>
+ <td><b>maxTime:</b> <xsl:value-of select="@maxTime"/></td>
+ <td><b>processingTime:</b> <xsl:value-of select="@processingTime"/></td>
+ <td><b>requestCount:</b> <xsl:value-of select="@requestCount"/></td>
+ <td><b>errorCount:</b> <xsl:value-of select="@errorCount"/></td>
+ <td><b>bytesReceived:</b> <xsl:value-of select="@bytesReceived"/></td>
+ <td><b>bytesSent:</b> <xsl:value-of select="@bytesSent"/></td>
+ </tr>
+ </table><hr />
+ </xsl:template>
+
+ <xsl:template match="workers">
+ <table>
+ <tr><th>Stage</th><th>Time</th><th>B Sent</th><th>B Recv</th><th>Client</th><th>VHost</th><th>Request</th></tr>
+ <xsl:apply-templates select="worker"/>
+
+ </table><hr />
+ </xsl:template>
+
+ <xsl:template match="worker">
+ <tr>
+ <td><xsl:value-of select="@stage"/></td>
+ <td><xsl:value-of select="@requestProcessingTime"/></td>
+ <td><xsl:value-of select="@requestBytesSent"/></td>
+ <td><xsl:value-of select="@requestBytesReceived"/></td>
+ <td><xsl:value-of select="@remoteAddr"/></td>
+ <td><xsl:value-of select="@virtualHost"/></td>
+ <td><xsl:value-of select="@method"/> <xsl:value-of select="@currentUri"/>?<xsl:value-of select="@currentQueryString"/> <xsl:value-of select="@protocol"/></td>
+ </tr>
+ </xsl:template>
+
+</xsl:stylesheet>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/conf/web.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/conf/web.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/conf/web.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,1230 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
+ version="2.4">
+
+ <!-- ======================== Introduction ============================== -->
+ <!-- This document defines default values for *all* web applications -->
+ <!-- loaded into this instance of Tomcat. As each application is -->
+ <!-- deployed, this file is processed, followed by the -->
+ <!-- "/WEB-INF/web.xml" deployment descriptor from your own -->
+ <!-- applications. -->
+ <!-- -->
+ <!-- WARNING: Do not configure application-specific resources here! -->
+ <!-- They should go in the "/WEB-INF/web.xml" file in your application. -->
+
+ <!-- =========== Common Context Params ================================== -->
+ <!-- JBossInjectionProvider provides resource injection for managed beans. -->
+ <!-- See JSF 1.2 spec section 5.4 for details. -->
+ <context-param>
+ <param-name>com.sun.faces.injectionProvider</param-name>
+ <param-value>org.jboss.web.jsf.integration.injection.JBossInjectionProvider</param-value>
+ </context-param>
+
+ <!-- ================== Common filter Configuration ==================== -->
+ <filter>
+ <filter-name>CommonHeadersFilter</filter-name>
+ <filter-class>org.jboss.web.tomcat.filters.ReplyHeaderFilter</filter-class>
+ <init-param>
+ <param-name>X-Powered-By</param-name>
+ <param-value>Servlet 2.4; JBoss-4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)/Tomcat-5.5</param-value>
+ </init-param>
+ </filter>
+
+ <filter-mapping>
+ <filter-name>CommonHeadersFilter</filter-name>
+ <url-pattern>/*</url-pattern>
+ </filter-mapping>
+
+ <!-- ================== Common Listener Configuration ==================== -->
+ <listener>
+ <listener-class>org.jboss.web.tomcat.security.SecurityFlushSessionListener</listener-class>
+ </listener>
+
+ <!-- Configures JSF for a web application if the javax.faces.webapp.FacesServlet is declared -->
+ <!-- in web.xml. -->
+ <listener>
+ <listener-class>org.jboss.web.jsf.integration.config.JBossJSFConfigureListener</listener-class>
+ </listener>
+
+ <!-- Listens to all web app lifecycle events so that @PreDestroy can be called on -->
+ <!-- JSF managed beans that go out of scope. You can comment this out if you -->
+ <!-- don't use JSF or you don't use annotations on your managed beans. -->
+ <listener>
+ <listener-class>com.sun.faces.application.WebappLifecycleListener</listener-class>
+ </listener>
+
+
+ <!-- ================== Built In Servlet Definitions ==================== -->
+
+
+ <!-- The default servlet for all web applications, that serves static -->
+ <!-- resources. It processes all requests that are not mapped to other -->
+ <!-- servlets with servlet mappings (defined either here or in your own -->
+ <!-- web.xml file. This servlet supports the following initialization -->
+ <!-- parameters (default values are in square brackets): -->
+ <!-- -->
+ <!-- debug Debugging detail level for messages logged -->
+ <!-- by this servlet. [0] -->
+ <!-- -->
+ <!-- fileEncoding Encoding to be used to read static resources -->
+ <!-- [platform default] -->
+ <!-- -->
+ <!-- input Input buffer size (in bytes) when reading -->
+ <!-- resources to be served. [2048] -->
+ <!-- -->
+ <!-- listings Should directory listings be produced if there -->
+ <!-- is no welcome file in this directory? [false] -->
+ <!-- WARNING: Listings for directories with many -->
+ <!-- entries can be slow and may consume -->
+ <!-- significant proportions of server resources. -->
+ <!-- -->
+ <!-- output Output buffer size (in bytes) when writing -->
+ <!-- resources to be served. [2048] -->
+ <!-- -->
+ <!-- readonly Is this context "read only", so HTTP -->
+ <!-- commands like PUT and DELETE are -->
+ <!-- rejected? [true] -->
+ <!-- -->
+ <!-- readmeFile File name to display with the directory -->
+ <!-- contents. [null] -->
+ <!-- -->
+ <!-- sendfileSize If the connector used supports sendfile, this -->
+ <!-- represents the minimal file size in KB for -->
+ <!-- which sendfile will be used. Use a negative -->
+ <!-- value to always disable sendfile. [48] -->
+ <!-- -->
+ <!-- For directory listing customization. Checks localXsltFile, then -->
+ <!-- globalXsltFile, then defaults to original behavior. -->
+ <!-- -->
+ <!-- localXsltFile Make directory listings an XML doc and -->
+ <!-- pass the result to this style sheet residing -->
+ <!-- in that directory. This overrides -->
+ <!-- globalXsltFile[null] -->
+ <!-- -->
+ <!-- globalXsltFile Site wide configuration version of -->
+ <!-- localXsltFile This argument is expected -->
+ <!-- to be a physical file. [null] -->
+ <!-- -->
+ <!-- -->
+
+ <servlet>
+ <servlet-name>default</servlet-name>
+ <servlet-class>org.apache.catalina.servlets.DefaultServlet</servlet-class>
+ <init-param>
+ <param-name>debug</param-name>
+ <param-value>0</param-value>
+ </init-param>
+ <init-param>
+ <param-name>listings</param-name>
+ <param-value>false</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+
+ <!-- The "invoker" servlet, which executes anonymous servlet classes -->
+ <!-- that have not been defined in a web.xml file. Traditionally, this -->
+ <!-- servlet is mapped to the URL pattern "/servlet/*", but you can map -->
+ <!-- it to other patterns as well. The extra path info portion of such a -->
+ <!-- request must be the fully qualified class name of a Java class that -->
+ <!-- implements Servlet (or extends HttpServlet), or the servlet name -->
+ <!-- of an existing servlet definition. This servlet supports the -->
+ <!-- following initialization parameters (default values are in square -->
+ <!-- brackets): -->
+ <!-- -->
+ <!-- debug Debugging detail level for messages logged -->
+ <!-- by this servlet. [0] -->
+
+<!--
+ <servlet>
+ <servlet-name>invoker</servlet-name>
+ <servlet-class>
+ org.apache.catalina.servlets.InvokerServlet
+ </servlet-class>
+ <init-param>
+ <param-name>debug</param-name>
+ <param-value>0</param-value>
+ </init-param>
+ <load-on-startup>2</load-on-startup>
+ </servlet>
+-->
+
+
+ <!-- The JSP page compiler and execution servlet, which is the mechanism -->
+ <!-- used by Tomcat to support JSP pages. Traditionally, this servlet -->
+ <!-- is mapped to the URL pattern "*.jsp". This servlet supports the -->
+ <!-- following initialization parameters (default values are in square -->
+ <!-- brackets): -->
+ <!-- -->
+ <!-- checkInterval If development is false and checkInterval is -->
+ <!-- greater than zero, background compilations are -->
+ <!-- enabled. checkInterval is the time in seconds -->
+ <!-- between checks to see if a JSP page needs to -->
+ <!-- be recompiled. [0] -->
+ <!-- -->
+ <!-- modificationTestInterval -->
+ <!-- Causes a JSP (and its dependent files) to not -->
+ <!-- be checked for modification during the -->
+ <!-- specified time interval (in seconds) from the -->
+ <!-- last time the JSP was checked for -->
+ <!-- modification. A value of 0 will cause the JSP -->
+ <!-- to be checked on every access. -->
+ <!-- Used in development mode only. [4] -->
+ <!-- -->
+ <!-- compiler Which compiler Ant should use to compile JSP -->
+ <!-- pages. See the Ant documentation for more -->
+ <!-- information. -->
+ <!-- -->
+ <!-- classdebuginfo Should the class file be compiled with -->
+ <!-- debugging information? [true] -->
+ <!-- -->
+ <!-- classpath What class path should I use while compiling -->
+ <!-- generated servlets? [Created dynamically -->
+ <!-- based on the current web application] -->
+ <!-- -->
+ <!-- development Is Jasper used in development mode? If true, -->
+ <!-- the frequency at which JSPs are checked for -->
+ <!-- modification may be specified via the -->
+ <!-- modificationTestInterval parameter. [true] -->
+ <!-- -->
+ <!-- enablePooling Determines whether tag handler pooling is -->
+ <!-- enabled [true] -->
+ <!-- -->
+ <!-- fork Tell Ant to fork compiles of JSP pages so that -->
+ <!-- a separate JVM is used for JSP page compiles -->
+ <!-- from the one Tomcat is running in. [true] -->
+ <!-- -->
+ <!-- ieClassId The class-id value to be sent to Internet -->
+ <!-- Explorer when using <jsp:plugin> tags. -->
+ <!-- [clsid:8AD9C840-044E-11D1-B3E9-00805F499D93] -->
+ <!-- -->
+ <!-- javaEncoding Java file encoding to use for generating java -->
+ <!-- source files. [UTF8] -->
+ <!-- -->
+ <!-- keepgenerated Should we keep the generated Java source code -->
+ <!-- for each page instead of deleting it? [true] -->
+ <!-- -->
+ <!-- mappedfile Should we generate static content with one -->
+ <!-- print statement per input line, to ease -->
+ <!-- debugging? [true] -->
+ <!-- -->
+ <!-- trimSpaces Should white spaces in template text between -->
+ <!-- actions or directives be trimmed? [false] -->
+ <!-- -->
+ <!-- suppressSmap Should the generation of SMAP info for JSR45 -->
+ <!-- debugging be suppressed? [false] -->
+ <!-- -->
+ <!-- dumpSmap Should the SMAP info for JSR45 debugging be -->
+ <!-- dumped to a file? [false] -->
+ <!-- False if suppressSmap is true -->
+ <!-- -->
+ <!-- genStrAsCharArray Should text strings be generated as char -->
+ <!-- arrays, to improve performance in some cases? -->
+ <!-- [false] -->
+ <!-- -->
+ <!-- errorOnUseBeanInvalidClassAttribute -->
+ <!-- Should Jasper issue an error when the value of -->
+ <!-- the class attribute in an useBean action is -->
+ <!-- not a valid bean class? [true] -->
+ <!-- -->
+ <!-- scratchdir What scratch directory should we use when -->
+ <!-- compiling JSP pages? [default work directory -->
+ <!-- for the current web application] -->
+ <!-- -->
+ <!-- xpoweredBy Determines whether X-Powered-By response -->
+ <!-- header is added by generated servlet [false] -->
+ <!-- -->
+ <!-- compilerTargetVM Compiler target VM -->
+ <!-- default is System.properties -->
+ <!-- java.specification.version > 1.4 -->
+ <!-- [1.5] else [1.4] -->
+ <!-- -->
+ <!-- compilerSourceVM Compiler source VM -->
+ <!-- default is System.properties -->
+ <!-- java.specification.version > 1.4 -->
+ <!-- [1.5] else [1.4] -->
+ <!-- -->
+ <!-- If you wish to use Jikes to compile JSP pages: -->
+ <!-- Please see the "Using Jikes" section of the Jasper-HowTo -->
+ <!-- page in the Tomcat documentation. -->
+
+ <servlet>
+ <servlet-name>jsp</servlet-name>
+ <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
+ <init-param>
+ <param-name>fork</param-name>
+ <param-value>false</param-value>
+ </init-param>
+ <init-param>
+ <param-name>xpoweredBy</param-name>
+ <param-value>false</param-value>
+ </init-param>
+
+ <!-- Use a custom options class to allow the shared tag lib descriptors
+ to be loaded from jars in the tomcat sar conf/tlds directory. The
+ standard options implementation can only find taglibs based on the
+ class loader classpath.
+ -->
+ <init-param>
+ <param-name>engineOptionsClass</param-name>
+ <param-value>org.jboss.web.tomcat.service.jasper.JspServletOptions</param-value>
+ </init-param>
+ <!-- Specify the jars relative to the jbossweb-tomcat6.sar that should
+ be scanned for common tag lib descriptors to include in every war
+ deployment.
+ -->
+ <init-param>
+ <description>JSF standard tlds</description>
+ <param-name>tagLibJar0</param-name>
+ <param-value>jsf-libs/jsf-impl.jar</param-value>
+ </init-param>
+ <init-param>
+ <description>JSTL standard tlds</description>
+ <param-name>tagLibJar1</param-name>
+ <param-value>jstl.jar</param-value>
+ </init-param>
+
+ <load-on-startup>3</load-on-startup>
+ </servlet>
+
+
+ <!-- NOTE: An SSI Filter is also available as an alternative SSI -->
+ <!-- implementation. Use either the Servlet or the Filter but NOT both. -->
+ <!-- -->
+ <!-- Server Side Includes processing servlet, which processes SSI -->
+ <!-- directives in HTML pages consistent with similar support in web -->
+ <!-- servers like Apache. Traditionally, this servlet is mapped to the -->
+ <!-- URL pattern "*.shtml". This servlet supports the following -->
+ <!-- initialization parameters (default values are in square brackets): -->
+ <!-- -->
+ <!-- buffered Should output from this servlet be buffered? -->
+ <!-- (0=false, 1=true) [0] -->
+ <!-- -->
+ <!-- debug Debugging detail level for messages logged -->
+ <!-- by this servlet. [0] -->
+ <!-- -->
+ <!-- expires The number of seconds before a page with SSI -->
+ <!-- directives will expire. [No default] -->
+ <!-- -->
+ <!-- isVirtualWebappRelative -->
+ <!-- Should "virtual" paths be interpreted as -->
+ <!-- relative to the context root, instead of -->
+ <!-- the server root? (0=false, 1=true) [0] -->
+ <!-- -->
+ <!-- inputEncoding The encoding to assume for SSI resources if -->
+ <!-- one is not available from the resource. -->
+ <!-- [Platform default] -->
+ <!-- -->
+ <!-- outputEncoding The encoding to use for the page that results -->
+ <!-- from the SSI processing. [UTF-8] -->
+ <!-- -->
+ <!-- -->
+ <!-- IMPORTANT: To use the SSI servlet, you also need to rename the -->
+ <!-- $CATALINA_HOME/server/lib/servlets-ssi.renametojar file -->
+ <!-- to $CATALINA_HOME/server/lib/servlets-ssi.jar -->
+
+<!--
+ <servlet>
+ <servlet-name>ssi</servlet-name>
+ <servlet-class>
+ org.apache.catalina.ssi.SSIServlet
+ </servlet-class>
+ <init-param>
+ <param-name>buffered</param-name>
+ <param-value>1</param-value>
+ </init-param>
+ <init-param>
+ <param-name>debug</param-name>
+ <param-value>0</param-value>
+ </init-param>
+ <init-param>
+ <param-name>expires</param-name>
+ <param-value>666</param-value>
+ </init-param>
+ <init-param>
+ <param-name>isVirtualWebappRelative</param-name>
+ <param-value>0</param-value>
+ </init-param>
+ <load-on-startup>4</load-on-startup>
+ </servlet>
+-->
+
+
+ <!-- Common Gateway Includes (CGI) processing servlet, which supports -->
+ <!-- execution of external applications that conform to the CGI spec -->
+ <!-- requirements. Typically, this servlet is mapped to the URL pattern -->
+ <!-- "/cgi-bin/*", which means that any CGI applications that are -->
+ <!-- executed must be present within the web application. This servlet -->
+ <!-- supports the following initialization parameters (default values -->
+ <!-- are in square brackets): -->
+ <!-- -->
+ <!-- cgiPathPrefix The CGI search path will start at -->
+ <!-- webAppRootDir + File.separator + this prefix. -->
+ <!-- [WEB-INF/cgi] -->
+ <!-- -->
+ <!-- debug Debugging detail level for messages logged -->
+ <!-- by this servlet. [0] -->
+ <!-- -->
+ <!-- executable Name of the exectuable used to run the -->
+ <!-- script. [perl] -->
+ <!-- -->
+ <!-- parameterEncoding Name of parameter encoding to be used with -->
+ <!-- CGI servlet. -->
+ <!-- [System.getProperty("file.encoding","UTF-8")] -->
+ <!-- -->
+ <!-- passShellEnvironment Should the shell environment variables (if -->
+ <!-- any) be passed to the CGI script? [false] -->
+ <!-- -->
+ <!-- IMPORTANT: To use the CGI servlet, you also need to rename the -->
+ <!-- $CATALINA_HOME/server/lib/servlets-cgi.renametojar file -->
+ <!-- to $CATALINA_HOME/server/lib/servlets-cgi.jar -->
+
+<!--
+ <servlet>
+ <servlet-name>cgi</servlet-name>
+ <servlet-class>org.apache.catalina.servlets.CGIServlet</servlet-class>
+ <init-param>
+ <param-name>debug</param-name>
+ <param-value>0</param-value>
+ </init-param>
+ <init-param>
+ <param-name>cgiPathPrefix</param-name>
+ <param-value>WEB-INF/cgi</param-value>
+ </init-param>
+ <load-on-startup>5</load-on-startup>
+ </servlet>
+-->
+
+
+ <!-- ================ Built In Servlet Mappings ========================= -->
+
+
+ <!-- The servlet mappings for the built in servlets defined above. Note -->
+ <!-- that, by default, the CGI and SSI servlets are *not* mapped. You -->
+ <!-- must uncomment these mappings (or add them to your application's own -->
+ <!-- web.xml deployment descriptor) to enable these services -->
+
+ <!-- The mapping for the default servlet -->
+ <servlet-mapping>
+ <servlet-name>default</servlet-name>
+ <url-pattern>/</url-pattern>
+ </servlet-mapping>
+
+ <!-- The mapping for the invoker servlet -->
+<!--
+ <servlet-mapping>
+ <servlet-name>invoker</servlet-name>
+ <url-pattern>/servlet/*</url-pattern>
+ </servlet-mapping>
+-->
+
+ <!-- The mapping for the JSP servlet -->
+ <servlet-mapping>
+ <servlet-name>jsp</servlet-name>
+ <url-pattern>*.jsp</url-pattern>
+ </servlet-mapping>
+
+ <servlet-mapping>
+ <servlet-name>jsp</servlet-name>
+ <url-pattern>*.jspx</url-pattern>
+ </servlet-mapping>
+
+ <!-- The mapping for the SSI servlet -->
+<!--
+ <servlet-mapping>
+ <servlet-name>ssi</servlet-name>
+ <url-pattern>*.shtml</url-pattern>
+ </servlet-mapping>
+-->
+
+ <!-- The mapping for the CGI Gateway servlet -->
+
+<!--
+ <servlet-mapping>
+ <servlet-name>cgi</servlet-name>
+ <url-pattern>/cgi-bin/*</url-pattern>
+ </servlet-mapping>
+-->
+
+
+ <!-- ================== Built In Filter Definitions ===================== -->
+
+ <!-- NOTE: An SSI Servlet is also available as an alternative SSI -->
+ <!-- implementation. Use either the Servlet or the Filter but NOT both. -->
+ <!-- -->
+ <!-- Server Side Includes processing filter, which processes SSI -->
+ <!-- directives in HTML pages consistent with similar support in web -->
+ <!-- servers like Apache. Traditionally, this filter is mapped to the -->
+ <!-- URL pattern "*.shtml", though it can be mapped to "*" as it will -->
+ <!-- selectively enable/disable SSI processing based on mime types. For -->
+ <!-- this to work you will need to uncomment the .shtml mime type -->
+ <!-- definition towards the bottom of this file. -->
+ <!-- The contentType init param allows you to apply SSI processing to JSP -->
+ <!-- pages, javascript, or any other content you wish. This filter -->
+ <!-- supports the following initialization parameters (default values are -->
+ <!-- in square brackets): -->
+ <!-- -->
+ <!-- contentType A regex pattern that must be matched before -->
+ <!-- SSI processing is applied. -->
+ <!-- [text/x-server-parsed-html(;.*)?] -->
+ <!-- -->
+ <!-- debug Debugging detail level for messages logged -->
+ <!-- by this servlet. [0] -->
+ <!-- -->
+ <!-- expires The number of seconds before a page with SSI -->
+ <!-- directives will expire. [No default] -->
+ <!-- -->
+ <!-- isVirtualWebappRelative -->
+ <!-- Should "virtual" paths be interpreted as -->
+ <!-- relative to the context root, instead of -->
+ <!-- the server root? (0=false, 1=true) [0] -->
+ <!-- -->
+ <!-- -->
+ <!-- IMPORTANT: To use the SSI filter, you also need to rename the -->
+ <!-- $CATALINA_HOME/server/lib/servlets-ssi.renametojar file -->
+ <!-- to $CATALINA_HOME/server/lib/servlets-ssi.jar -->
+
+<!--
+ <filter>
+ <filter-name>ssi</filter-name>
+ <filter-class>
+ org.apache.catalina.ssi.SSIFilter
+ </filter-class>
+ <init-param>
+ <param-name>contentType</param-name>
+ <param-value>text/x-server-parsed-html(;.*)?</param-value>
+ </init-param>
+ <init-param>
+ <param-name>debug</param-name>
+ <param-value>0</param-value>
+ </init-param>
+ <init-param>
+ <param-name>expires</param-name>
+ <param-value>666</param-value>
+ </init-param>
+ <init-param>
+ <param-name>isVirtualWebappRelative</param-name>
+ <param-value>0</param-value>
+ </init-param>
+ </filter>
+-->
+
+
+ <!-- ==================== Built In Filter Mappings ====================== -->
+
+ <!-- The mapping for the SSI Filter -->
+<!--
+ <filter-mapping>
+ <filter-name>ssi</filter-name>
+ <url-pattern>*.shtml</url-pattern>
+ </filter-mapping>
+-->
+
+
+ <!-- ==================== Default Session Configuration ================= -->
+ <!-- You can set the default session timeout (in minutes) for all newly -->
+ <!-- created sessions by modifying the value below. -->
+
+ <session-config>
+ <session-timeout>30</session-timeout>
+ </session-config>
+
+
+ <!-- ===================== Default MIME Type Mappings =================== -->
+ <!-- When serving static resources, Tomcat will automatically generate -->
+ <!-- a "Content-Type" header based on the resource's filename extension, -->
+ <!-- based on these mappings. Additional mappings can be added here (to -->
+ <!-- apply to all web applications), or in your own application's web.xml -->
+ <!-- deployment descriptor. -->
+
+ <mime-mapping>
+ <extension>abs</extension>
+ <mime-type>audio/x-mpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>ai</extension>
+ <mime-type>application/postscript</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>aif</extension>
+ <mime-type>audio/x-aiff</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>aifc</extension>
+ <mime-type>audio/x-aiff</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>aiff</extension>
+ <mime-type>audio/x-aiff</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>aim</extension>
+ <mime-type>application/x-aim</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>art</extension>
+ <mime-type>image/x-jg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>asf</extension>
+ <mime-type>video/x-ms-asf</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>asx</extension>
+ <mime-type>video/x-ms-asf</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>au</extension>
+ <mime-type>audio/basic</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>avi</extension>
+ <mime-type>video/x-msvideo</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>avx</extension>
+ <mime-type>video/x-rad-screenplay</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>bcpio</extension>
+ <mime-type>application/x-bcpio</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>bin</extension>
+ <mime-type>application/octet-stream</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>bmp</extension>
+ <mime-type>image/bmp</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>body</extension>
+ <mime-type>text/html</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>cdf</extension>
+ <mime-type>application/x-cdf</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>cer</extension>
+ <mime-type>application/x-x509-ca-cert</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>class</extension>
+ <mime-type>application/java</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>cpio</extension>
+ <mime-type>application/x-cpio</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>csh</extension>
+ <mime-type>application/x-csh</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>css</extension>
+ <mime-type>text/css</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>dib</extension>
+ <mime-type>image/bmp</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>doc</extension>
+ <mime-type>application/msword</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>dtd</extension>
+ <mime-type>application/xml-dtd</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>dv</extension>
+ <mime-type>video/x-dv</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>dvi</extension>
+ <mime-type>application/x-dvi</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>eps</extension>
+ <mime-type>application/postscript</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>etx</extension>
+ <mime-type>text/x-setext</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>exe</extension>
+ <mime-type>application/octet-stream</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>gif</extension>
+ <mime-type>image/gif</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>gtar</extension>
+ <mime-type>application/x-gtar</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>gz</extension>
+ <mime-type>application/x-gzip</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>hdf</extension>
+ <mime-type>application/x-hdf</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>hqx</extension>
+ <mime-type>application/mac-binhex40</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>htc</extension>
+ <mime-type>text/x-component</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>htm</extension>
+ <mime-type>text/html</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>html</extension>
+ <mime-type>text/html</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>hqx</extension>
+ <mime-type>application/mac-binhex40</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>ief</extension>
+ <mime-type>image/ief</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>jad</extension>
+ <mime-type>text/vnd.sun.j2me.app-descriptor</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>jar</extension>
+ <mime-type>application/java-archive</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>java</extension>
+ <mime-type>text/plain</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>jnlp</extension>
+ <mime-type>application/x-java-jnlp-file</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>jpe</extension>
+ <mime-type>image/jpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>jpeg</extension>
+ <mime-type>image/jpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>jpg</extension>
+ <mime-type>image/jpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>js</extension>
+ <mime-type>text/javascript</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>jsf</extension>
+ <mime-type>text/plain</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>jspf</extension>
+ <mime-type>text/plain</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>kar</extension>
+ <mime-type>audio/x-midi</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>latex</extension>
+ <mime-type>application/x-latex</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>m3u</extension>
+ <mime-type>audio/x-mpegurl</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mac</extension>
+ <mime-type>image/x-macpaint</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>man</extension>
+ <mime-type>application/x-troff-man</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mathml</extension>
+ <mime-type>application/mathml+xml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>me</extension>
+ <mime-type>application/x-troff-me</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mid</extension>
+ <mime-type>audio/x-midi</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>midi</extension>
+ <mime-type>audio/x-midi</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mif</extension>
+ <mime-type>application/x-mif</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mov</extension>
+ <mime-type>video/quicktime</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>movie</extension>
+ <mime-type>video/x-sgi-movie</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mp1</extension>
+ <mime-type>audio/x-mpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mp2</extension>
+ <mime-type>audio/x-mpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mp3</extension>
+ <mime-type>audio/x-mpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mpa</extension>
+ <mime-type>audio/x-mpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mpe</extension>
+ <mime-type>video/mpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mpeg</extension>
+ <mime-type>video/mpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mpega</extension>
+ <mime-type>audio/x-mpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mpg</extension>
+ <mime-type>video/mpeg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>mpv2</extension>
+ <mime-type>video/mpeg2</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>ms</extension>
+ <mime-type>application/x-wais-source</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>nc</extension>
+ <mime-type>application/x-netcdf</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>oda</extension>
+ <mime-type>application/oda</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Database -->
+ <extension>odb</extension>
+ <mime-type>application/vnd.oasis.opendocument.database</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Chart -->
+ <extension>odc</extension>
+ <mime-type>application/vnd.oasis.opendocument.chart</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Formula -->
+ <extension>odf</extension>
+ <mime-type>application/vnd.oasis.opendocument.formula</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Drawing -->
+ <extension>odg</extension>
+ <mime-type>application/vnd.oasis.opendocument.graphics</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Image -->
+ <extension>odi</extension>
+ <mime-type>application/vnd.oasis.opendocument.image</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Master Document -->
+ <extension>odm</extension>
+ <mime-type>application/vnd.oasis.opendocument.text-master</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Presentation -->
+ <extension>odp</extension>
+ <mime-type>application/vnd.oasis.opendocument.presentation</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Spreadsheet -->
+ <extension>ods</extension>
+ <mime-type>application/vnd.oasis.opendocument.spreadsheet</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Text -->
+ <extension>odt</extension>
+ <mime-type>application/vnd.oasis.opendocument.text</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>ogg</extension>
+ <mime-type>application/ogg</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Drawing Template -->
+ <extension>otg </extension>
+ <mime-type>application/vnd.oasis.opendocument.graphics-template</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- HTML Document Template -->
+ <extension>oth</extension>
+ <mime-type>application/vnd.oasis.opendocument.text-web</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Presentation Template -->
+ <extension>otp</extension>
+ <mime-type>application/vnd.oasis.opendocument.presentation-template</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Spreadsheet Template -->
+ <extension>ots</extension>
+ <mime-type>application/vnd.oasis.opendocument.spreadsheet-template </mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- OpenDocument Text Template -->
+ <extension>ott</extension>
+ <mime-type>application/vnd.oasis.opendocument.text-template</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>pbm</extension>
+ <mime-type>image/x-portable-bitmap</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>pct</extension>
+ <mime-type>image/pict</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>pdf</extension>
+ <mime-type>application/pdf</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>pgm</extension>
+ <mime-type>image/x-portable-graymap</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>pic</extension>
+ <mime-type>image/pict</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>pict</extension>
+ <mime-type>image/pict</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>pls</extension>
+ <mime-type>audio/x-scpls</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>png</extension>
+ <mime-type>image/png</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>pnm</extension>
+ <mime-type>image/x-portable-anymap</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>pnt</extension>
+ <mime-type>image/x-macpaint</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>ppm</extension>
+ <mime-type>image/x-portable-pixmap</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>ppt</extension>
+ <mime-type>application/powerpoint</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>ps</extension>
+ <mime-type>application/postscript</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>psd</extension>
+ <mime-type>image/x-photoshop</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>qt</extension>
+ <mime-type>video/quicktime</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>qti</extension>
+ <mime-type>image/x-quicktime</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>qtif</extension>
+ <mime-type>image/x-quicktime</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>ras</extension>
+ <mime-type>image/x-cmu-raster</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>rdf</extension>
+ <mime-type>application/rdf+xml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>rgb</extension>
+ <mime-type>image/x-rgb</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>rm</extension>
+ <mime-type>application/vnd.rn-realmedia</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>roff</extension>
+ <mime-type>application/x-troff</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>rtf</extension>
+ <mime-type>application/rtf</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>rtx</extension>
+ <mime-type>text/richtext</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>sh</extension>
+ <mime-type>application/x-sh</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>shar</extension>
+ <mime-type>application/x-shar</mime-type>
+ </mime-mapping>
+<!--
+ <mime-mapping>
+ <extension>shtml</extension>
+ <mime-type>text/x-server-parsed-html</mime-type>
+ </mime-mapping>
+-->
+ <mime-mapping>
+ <extension>smf</extension>
+ <mime-type>audio/x-midi</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>sit</extension>
+ <mime-type>application/x-stuffit</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>snd</extension>
+ <mime-type>audio/basic</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>src</extension>
+ <mime-type>application/x-wais-source</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>sv4cpio</extension>
+ <mime-type>application/x-sv4cpio</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>sv4crc</extension>
+ <mime-type>application/x-sv4crc</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>swf</extension>
+ <mime-type>application/x-shockwave-flash</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>t</extension>
+ <mime-type>application/x-troff</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>tar</extension>
+ <mime-type>application/x-tar</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>tcl</extension>
+ <mime-type>application/x-tcl</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>tex</extension>
+ <mime-type>application/x-tex</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>texi</extension>
+ <mime-type>application/x-texinfo</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>texinfo</extension>
+ <mime-type>application/x-texinfo</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>tif</extension>
+ <mime-type>image/tiff</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>tiff</extension>
+ <mime-type>image/tiff</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>tr</extension>
+ <mime-type>application/x-troff</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>tsv</extension>
+ <mime-type>text/tab-separated-values</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>txt</extension>
+ <mime-type>text/plain</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>ulw</extension>
+ <mime-type>audio/basic</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>ustar</extension>
+ <mime-type>application/x-ustar</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>vxml</extension>
+ <mime-type>application/voicexml+xml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>xbm</extension>
+ <mime-type>image/x-xbitmap</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>xht</extension>
+ <mime-type>application/xhtml+xml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>xhtml</extension>
+ <mime-type>application/xhtml+xml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>xml</extension>
+ <mime-type>application/xml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>xpm</extension>
+ <mime-type>image/x-xpixmap</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>xsl</extension>
+ <mime-type>application/xml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>xslt</extension>
+ <mime-type>application/xslt+xml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>xul</extension>
+ <mime-type>application/vnd.mozilla.xul+xml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>xwd</extension>
+ <mime-type>image/x-xwindowdump</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>wav</extension>
+ <mime-type>audio/x-wav</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>svg</extension>
+ <mime-type>image/svg+xml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>svgz</extension>
+ <mime-type>image/svg+xml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>vsd</extension>
+ <mime-type>application/x-visio</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- Wireless Bitmap -->
+ <extension>wbmp</extension>
+ <mime-type>image/vnd.wap.wbmp</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- WML Source -->
+ <extension>wml</extension>
+ <mime-type>text/vnd.wap.wml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- Compiled WML -->
+ <extension>wmlc</extension>
+ <mime-type>application/vnd.wap.wmlc</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- WML Script Source -->
+ <extension>wmls</extension>
+ <mime-type>text/vnd.wap.wmlscript</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <!-- Compiled WML Script -->
+ <extension>wmlscriptc</extension>
+ <mime-type>application/vnd.wap.wmlscriptc</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>wrl</extension>
+ <mime-type>x-world/x-vrml</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>Z</extension>
+ <mime-type>application/x-compress</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>z</extension>
+ <mime-type>application/x-compress</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>zip</extension>
+ <mime-type>application/zip</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>xls</extension>
+ <mime-type>application/vnd.ms-excel</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>doc</extension>
+ <mime-type>application/vnd.ms-word</mime-type>
+ </mime-mapping>
+ <mime-mapping>
+ <extension>ppt</extension>
+ <mime-type>application/vnd.ms-powerpoint</mime-type>
+ </mime-mapping>
+
+ <!-- ==================== Default Welcome File List ===================== -->
+ <!-- When a request URI refers to a directory, the default servlet looks -->
+ <!-- for a "welcome file" within that directory and, if present, -->
+ <!-- to the corresponding resource URI for display. If no welcome file -->
+ <!-- is present, the default servlet either serves a directory listing, -->
+ <!-- or returns a 404 status, depending on how it is configured. -->
+ <!-- -->
+ <!-- If you define welcome files in your own application's web.xml -->
+ <!-- deployment descriptor, that list *replaces* the list configured -->
+ <!-- here, so be sure that you include any of the default values that -->
+ <!-- you wish to include. -->
+
+ <welcome-file-list>
+ <welcome-file>index.html</welcome-file>
+ <welcome-file>index.htm</welcome-file>
+ <welcome-file>index.jsp</welcome-file>
+ </welcome-file-list>
+
+</web-app>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/context.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/context.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/context.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,17 @@
+<!-- The contents of this file will be loaded for each web application -->
+<Context cookies="true" crossContext="true">
+ <!-- Session persistence is disable by default. To enable for all web
+ apps set the pathname to a non-empty value:
+ <Manager pathname="SESSIONS.ser" />
+
+ To enable session persistence for a single web app, add a
+ WEB-INF/context.xml
+ -->
+ <Manager pathname="" />
+
+ <!-- Install an InstanceListener to handle the establishment of the run-as
+ role for servlet init/destroy events.
+ -->
+ <InstanceListener>org.jboss.web.tomcat.security.RunAsListener</InstanceListener>
+
+</Context>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jasper-jdt.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jasper-jdt.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jbossweb-extras.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jbossweb-extras.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jbossweb-service.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jbossweb-service.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jbossweb.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jbossweb.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jsf-libs/jboss-faces.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jsf-libs/jboss-faces.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jsf-libs/jsf-api.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jsf-libs/jsf-api.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jsf-libs/jsf-impl.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jsf-libs/jsf-impl.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jstl.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/jstl.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/server.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/server.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-web.deployer/server.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,167 @@
+<Server>
+
+ <!--APR library loader. Documentation at /docs/apr.html -->
+ <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
+ <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
+ <Listener className="org.apache.catalina.core.JasperListener" />
+
+ <!-- Use a custom version of StandardService that allows the
+ connectors to be started independent of the normal lifecycle
+ start to allow web apps to be deployed before starting the
+ connectors.
+ -->
+ <Service name="jboss.web">
+
+ <!-- A "Connector" represents an endpoint by which requests are received
+ and responses are returned. Documentation at :
+ Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
+ Java AJP Connector: /docs/config/ajp.html
+ APR (HTTP/AJP) Connector: /docs/apr.html
+ Define a non-SSL HTTP/1.1 Connector on port 8080
+ -->
+ <Connector port="8080" address="${jboss.bind.address}"
+ maxThreads="250" maxHttpHeaderSize="8192"
+ emptySessionPath="true" protocol="HTTP/1.1"
+ enableLookups="false" redirectPort="8443" acceptCount="100"
+ connectionTimeout="20000" disableUploadTimeout="true" />
+
+ <!-- Define a SSL HTTP/1.1 Connector on port 8443
+ This connector uses the JSSE configuration, when using APR, the
+ connector should be using the OpenSSL style configuration
+ described in the APR documentation -->
+ <!--
+ <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
+ maxThreads="150" scheme="https" secure="true"
+ clientAuth="false" sslProtocol="TLS" />
+ -->
+
+ <!-- Define an AJP 1.3 Connector on port 8009 -->
+ <Connector port="8009" address="${jboss.bind.address}" protocol="AJP/1.3"
+ emptySessionPath="true" enableLookups="false" redirectPort="8443" />
+
+ <Engine name="jboss.web" defaultHost="localhost">
+
+ <!-- The JAAS based authentication and authorization realm implementation
+ that is compatible with the jboss 3.2.x realm implementation.
+ - certificatePrincipal : the class name of the
+ org.jboss.security.auth.certs.CertificatePrincipal impl
+ used for mapping X509[] cert chains to a Princpal.
+ - allRolesMode : how to handle an auth-constraint with a role-name=*,
+ one of strict, authOnly, strictAuthOnly
+ + strict = Use the strict servlet spec interpretation which requires
+ that the user have one of the web-app/security-role/role-name
+ + authOnly = Allow any authenticated user
+ + strictAuthOnly = Allow any authenticated user only if there are no
+ web-app/security-roles
+ -->
+ <Realm className="org.jboss.web.tomcat.security.JBossSecurityMgrRealm"
+ certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"
+ allRolesMode="authOnly"
+ />
+ <!-- A subclass of JBossSecurityMgrRealm that uses the authentication
+ behavior of JBossSecurityMgrRealm, but overrides the authorization
+ checks to use JACC permissions with the current java.security.Policy
+ to determine authorized access.
+ - allRolesMode : how to handle an auth-constraint with a role-name=*,
+ one of strict, authOnly, strictAuthOnly
+ + strict = Use the strict servlet spec interpretation which requires
+ that the user have one of the web-app/security-role/role-name
+ + authOnly = Allow any authenticated user
+ + strictAuthOnly = Allow any authenticated user only if there are no
+ web-app/security-roles
+ <Realm className="org.jboss.web.tomcat.security.JaccAuthorizationRealm"
+ certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"
+ allRolesMode="authOnly"
+ />
+ -->
+
+ <Host name="localhost"
+ autoDeploy="false" deployOnStartup="false" deployXML="false"
+ configClass="org.jboss.web.tomcat.security.config.JBossContextConfig"
+ >
+
+ <!-- Uncomment to enable request dumper. This Valve "logs interesting
+ contents from the specified Request (before processing) and the
+ corresponding Response (after processing). It is especially useful
+ in debugging problems related to headers and cookies."
+ -->
+ <!--
+ <Valve className="org.apache.catalina.valves.RequestDumperValve" />
+ -->
+
+ <!-- Access logger -->
+ <!--
+ <Valve className="org.apache.catalina.valves.AccessLogValve"
+ prefix="localhost_access_log." suffix=".log"
+ pattern="common" directory="${jboss.server.home.dir}/log"
+ resolveHosts="false" />
+ -->
+
+ <!-- Uncomment to enable single sign-on across web apps
+ deployed to this host. Does not provide SSO across a cluster.
+
+ If this valve is used, do not use the JBoss ClusteredSingleSignOn
+ valve shown below.
+
+ A new configuration attribute is available beginning with
+ release 4.0.4:
+
+ cookieDomain configures the domain to which the SSO cookie
+ will be scoped (i.e. the set of hosts to
+ which the cookie will be presented). By default
+ the cookie is scoped to "/", meaning the host
+ that presented it. Set cookieDomain to a
+ wider domain (e.g. "xyz.com") to allow an SSO
+ to span more than one hostname.
+ -->
+ <!--
+ <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
+ -->
+
+ <!-- Uncomment to enable single sign-on across web apps
+ deployed to this host AND to all other hosts in the cluster.
+
+ If this valve is used, do not use the standard Tomcat SingleSignOn
+ valve shown above.
+
+ Valve uses a JBossCache instance to support SSO credential
+ caching and replication across the cluster. The JBossCache
+ instance must be configured separately. By default, the valve
+ shares a JBossCache with the service that supports HttpSession
+ replication. See the "jboss-web-cluster-service.xml" file in the
+ server/all/deploy directory for cache configuration details.
+
+ Besides the attributes supported by the standard Tomcat
+ SingleSignOn valve (see the Tomcat docs), this version also
+ supports the following attributes:
+
+ cookieDomain see above
+
+ treeCacheName JMX ObjectName of the JBossCache MBean used to
+ support credential caching and replication across
+ the cluster. If not set, the default value is
+ "jboss.cache:service=TomcatClusteringCache", the
+ standard ObjectName of the JBossCache MBean used
+ to support session replication.
+ -->
+ <!--
+ <Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" />
+ -->
+
+ <!-- Check for unclosed connections and transaction terminated checks
+ in servlets/jsps.
+
+ Important: The dependency on the CachedConnectionManager
+ in META-INF/jboss-service.xml must be uncommented, too
+ -->
+ <Valve className="org.jboss.web.tomcat.service.jca.CachedConnectionValve"
+ cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager"
+ transactionManagerObjectName="jboss:service=TransactionManager" />
+
+ </Host>
+
+ </Engine>
+
+ </Service>
+
+</Server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-xa-jdbc.rar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jboss-xa-jdbc.rar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossjca-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossjca-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossjca-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- JBoss JCA Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<!-- $Id: jbossjca-service.xml 37786 2005-11-02 20:35:46Z adrian $ -->
+
+<!--
+ | This contains configuration for the RARDeployer
+ and some xsl based deployers.
+ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- JBossCX setup, for J2EE connector architecture support -->
+ <!-- The RARDeployer is needed only until xslt based deployment is written.-->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.util.threadpool.BasicThreadPool"
+ name="jboss.jca:service=WorkManagerThreadPool">
+ <!-- The name that appears in thread names -->
+ <attribute name="Name">WorkManager</attribute>
+ <!-- The maximum amount of work in the queue -->
+ <attribute name="MaximumQueueSize">1024</attribute>
+ <!-- The maximum number of active threads -->
+ <attribute name="MaximumPoolSize">100</attribute>
+ <!-- How long to keep threads alive after their last work (default one minute) -->
+ <attribute name="KeepAliveTime">60000</attribute>
+ </mbean>
+
+ <mbean code="org.jboss.resource.work.JBossWorkManager"
+ name="jboss.jca:service=WorkManager">
+ <depends optional-attribute-name="ThreadPoolName">jboss.jca:service=WorkManagerThreadPool</depends>
+ <depends optional-attribute-name="XATerminatorName">jboss:service=TransactionManager</depends>
+ </mbean>
+
+ <mbean code="org.jboss.resource.deployment.RARDeployer"
+ name="jboss.jca:service=RARDeployer">
+ <depends optional-attribute-name="WorkManagerName">jboss.jca:service=WorkManager</depends>
+ <depends optional-attribute-name="XATerminatorName">jboss:service=TransactionManager</depends>
+ </mbean>
+
+ <mbean code="org.jboss.deployment.XSLSubDeployer" name="jboss.jca:service=ConnectionFactoryDeployer">
+ <attribute name="DdSuffix">-ds.xml</attribute>
+ <attribute name="EnhancedSuffixes">300:-ds.xml</attribute>
+ <attribute name="XslUrl">stylesheets/ConnectionFactoryTemplate.xsl</attribute>
+ <attribute name="ValidateDTDs">false</attribute>
+ </mbean>
+
+ <!--
+ | The CachedConnectionManager is used partly to relay started UserTransactions to
+ | open connections so they may be enrolled in the new tx.
+ -->
+ <mbean code="org.jboss.resource.connectionmanager.CachedConnectionManager"
+ name="jboss.jca:service=CachedConnectionManager">
+ <depends optional-attribute-name="TransactionManagerServiceName">jboss:service=TransactionManager</depends>
+
+ <!-- Enable connection close debug monitoring -->
+ <attribute name="Debug">true</attribute>
+
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/MANIFEST.MF
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/MANIFEST.MF (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/MANIFEST.MF 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,12 @@
+Manifest-Version: 1.0
+Ant-Version: Apache Ant 1.6.5
+Created-By: 1.5.0_09-b03 (Sun Microsystems Inc.)
+Specification-Title: JBossWS
+Specification-Version: jbossws-1.2
+Specification-Vendor: JBoss (http://www.jboss.org)
+Implementation-Title: JBoss Web Services (JBossWS)
+Implementation-URL: http://www.jboss.org/products/jbossws
+Implementation-Version: jbossws-1.2.1.GA (build=200704151756)
+Implementation-Vendor: JBoss Inc.
+Implementation-Vendor-Id: http://www.jboss.org
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/jboss-service-no-ejb3.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/jboss-service-no-ejb3.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/jboss-service-no-ejb3.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: jboss-service-no-ejb3.xml 2598 2007-03-12 10:11:14Z thomas.diesler at jboss.com $ -->
+
+<server>
+
+ <!--
+ A deployer service for JSE endpoints.
+ -->
+ <mbean name="jboss.ws:service=WebServiceDeployerJSE" code="org.jboss.ws.integration.jboss42.DeployerInterceptorJSE">
+ <depends-list optional-attribute-name="Interceptables">
+ <depends-list-element>jboss.web:service=WebServer</depends-list-element>
+ </depends-list>
+ </mbean>
+
+ <!--
+ A deployer service for EJB2.1 endpoints.
+ -->
+ <mbean name="jboss.ws:service=DeployerInterceptorEJB21" code="org.jboss.ws.integration.jboss42.DeployerInterceptorEJB21">
+ <depends-list optional-attribute-name="Interceptables">
+ <depends-list-element>jboss.ejb:service=EJBDeployer</depends-list-element>
+ </depends-list>
+ </mbean>
+
+ <!--
+ A deployer service for EJB3 endpoints.
+ <mbean name="jboss.ws:service=DeployerInterceptorEJB3" code="org.jboss.ws.integration.jboss42.DeployerInterceptorEJB3">
+ <depends-list optional-attribute-name="Interceptables">
+ <depends-list-element>jboss.ejb3:service=EJB3Deployer</depends-list-element>
+ </depends-list>
+ </mbean>
+ -->
+
+ <!--
+ A deployer service for JSE endpoints that are nested in service archives (sar).
+ -->
+ <mbean name="jboss.ws:service=DeployerInterceptorNestedJSE" code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
+ <depends optional-attribute-name="MainDeployer" proxy-type="attribute">jboss.system:service=MainDeployer</depends>
+ <depends>jboss.ws:service=WebServiceDeployerJSE</depends>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/jboss-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/jboss-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/jboss-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: jboss-service.xml 2598 2007-03-12 10:11:14Z thomas.diesler at jboss.com $ -->
+
+<server>
+
+ <!--
+ A deployer service for JSE endpoints.
+ -->
+ <mbean name="jboss.ws:service=WebServiceDeployerJSE" code="org.jboss.ws.integration.jboss42.DeployerInterceptorJSE">
+ <depends-list optional-attribute-name="Interceptables">
+ <depends-list-element>jboss.web:service=WebServer</depends-list-element>
+ </depends-list>
+ </mbean>
+
+ <!--
+ A deployer service for EJB2.1 endpoints.
+ -->
+ <mbean name="jboss.ws:service=DeployerInterceptorEJB21" code="org.jboss.ws.integration.jboss42.DeployerInterceptorEJB21">
+ <depends-list optional-attribute-name="Interceptables">
+ <depends-list-element>jboss.ejb:service=EJBDeployer</depends-list-element>
+ </depends-list>
+ </mbean>
+
+ <!--
+ A deployer service for EJB3 endpoints.
+ -->
+ <mbean name="jboss.ws:service=DeployerInterceptorEJB3" code="org.jboss.ws.integration.jboss42.DeployerInterceptorEJB3">
+ <depends-list optional-attribute-name="Interceptables">
+ <depends-list-element>jboss.ejb3:service=EJB3Deployer</depends-list-element>
+ </depends-list>
+ </mbean>
+
+ <!--
+ A deployer service for JSE endpoints that are nested in service archives (sar).
+ -->
+ <mbean name="jboss.ws:service=DeployerInterceptorNestedJSE" code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
+ <depends optional-attribute-name="MainDeployer" proxy-type="attribute">jboss.system:service=MainDeployer</depends>
+ <depends>jboss.ws:service=WebServiceDeployerJSE</depends>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxrpc-client-config.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxrpc-client-config.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxrpc-client-config.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: standard-jaxrpc-client-config.xml 2324 2007-02-09 16:14:15Z heiko.braun at jboss.com $ -->
+
+<jaxrpc-config xmlns="urn:jboss:jaxrpc-config:2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xsi:schemaLocation="urn:jboss:jaxrpc-config:2.0 jaxrpc-config_2_0.xsd">
+
+ <client-config>
+ <config-name>Standard Client</config-name>
+ </client-config>
+
+ <client-config>
+ <config-name>Standard MTOM client</config-name>
+ <feature>http://org.jboss.ws/mtom</feature>
+ </client-config>
+
+ <client-config>
+ <config-name>Standard WSAddressing Client</config-name>
+ <post-handler-chain>
+ <handler-chain-name>WSAddressing Handlers</handler-chain-name>
+ <handler>
+ <j2ee:handler-name>WSAddressingClientHandler</j2ee:handler-name>
+ <j2ee:handler-class>org.jboss.ws.extensions.addressing.jaxrpc.WSAddressingClientHandler</j2ee:handler-class>
+ </handler>
+ </post-handler-chain>
+ </client-config>
+
+ <client-config>
+ <config-name>Standard WSSecurity Client</config-name>
+ <post-handler-chain>
+ <handler-chain-name>WSSecurity Handlers</handler-chain-name>
+ <handler>
+ <j2ee:handler-name>WSSecurityHandlerOutbound</j2ee:handler-name>
+ <j2ee:handler-class>org.jboss.ws.extensions.security.jaxrpc.WSSecurityHandlerOutbound</j2ee:handler-class>
+ </handler>
+ </post-handler-chain>
+ </client-config>
+
+</jaxrpc-config>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxrpc-endpoint-config.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxrpc-endpoint-config.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxrpc-endpoint-config.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: standard-jaxrpc-endpoint-config.xml 2324 2007-02-09 16:14:15Z heiko.braun at jboss.com $ -->
+
+<jaxrpc-config xmlns="urn:jboss:jaxrpc-config:2.0"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
+ xsi:schemaLocation="urn:jboss:jaxrpc-config:2.0 jaxrpc-config_2_0.xsd">
+
+ <endpoint-config>
+ <config-name>Standard Endpoint</config-name>
+ </endpoint-config>
+
+ <endpoint-config>
+ <config-name>Standard MTOM Endpoint</config-name>
+ <feature>http://org.jboss.ws/mtom</feature>
+ </endpoint-config>
+
+ <endpoint-config>
+ <config-name>Standard WSAddressing Endpoint</config-name>
+ <pre-handler-chain>
+ <handler-chain-name>WSAddressing Handlers</handler-chain-name>
+ <handler>
+ <j2ee:handler-name>WSAddressing Handler</j2ee:handler-name>
+ <j2ee:handler-class>org.jboss.ws.extensions.addressing.jaxrpc.WSAddressingServerHandler</j2ee:handler-class>
+ </handler>
+ </pre-handler-chain>
+ </endpoint-config>
+
+ <endpoint-config>
+ <config-name>Standard WSSecurity Endpoint</config-name>
+ <pre-handler-chain>
+ <handler-chain-name>WSSecurity Handlers</handler-chain-name>
+ <handler>
+ <j2ee:handler-name>WSSecurityHandlerInbound</j2ee:handler-name>
+ <j2ee:handler-class>org.jboss.ws.extensions.security.jaxrpc.WSSecurityHandlerInbound</j2ee:handler-class>
+ </handler>
+ </pre-handler-chain>
+ </endpoint-config>
+
+</jaxrpc-config>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-client-config.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-client-config.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-client-config.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: standard-jaxws-client-config.xml 2785 2007-04-10 16:20:15Z heiko.braun at jboss.com $ -->
+
+<jaxws-config xmlns="urn:jboss:jaxws-config:2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd">
+
+ <client-config>
+ <config-name>Standard Client</config-name>
+ <feature>http://org.jboss.ws/dispatch/validate</feature>
+ </client-config>
+
+ <client-config>
+ <config-name>Standard WSAddressing Client</config-name>
+ <post-handler-chains>
+ <javaee:handler-chain>
+ <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
+ <javaee:handler>
+ <javaee:handler-name>WSAddressing Handler</javaee:handler-name>
+ <javaee:handler-class>org.jboss.ws.extensions.addressing.jaxws.WSAddressingClientHandler</javaee:handler-class>
+ </javaee:handler>
+ </javaee:handler-chain>
+ </post-handler-chains>
+ </client-config>
+
+ <client-config>
+ <config-name>Standard WSSecurity Client</config-name>
+ <post-handler-chains>
+ <javaee:handler-chain>
+ <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
+ <javaee:handler>
+ <javaee:handler-name>WSSecurityHandlerOutbound</javaee:handler-name>
+ <javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient</javaee:handler-class>
+ </javaee:handler>
+ </javaee:handler-chain>
+ </post-handler-chains>
+ </client-config>
+
+</jaxws-config>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-endpoint-config.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-endpoint-config.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-endpoint-config.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: standard-jaxws-endpoint-config.xml 2631 2007-03-16 19:18:35Z thomas.diesler at jboss.com $ -->
+
+<jaxws-config xmlns="urn:jboss:jaxws-config:2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:javaee="http://java.sun.com/xml/ns/javaee"
+ xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd">
+
+ <endpoint-config>
+ <config-name>Standard Endpoint</config-name>
+ </endpoint-config>
+
+ <endpoint-config>
+ <config-name>Standard WSAddressing Endpoint</config-name>
+ <post-handler-chains>
+ <javaee:handler-chain>
+ <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
+ <javaee:handler>
+ <javaee:handler-name>WSAddressing Handler</javaee:handler-name>
+ <javaee:handler-class>org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler</javaee:handler-class>
+ </javaee:handler>
+ </javaee:handler-chain>
+ </post-handler-chains>
+ </endpoint-config>
+
+ <endpoint-config>
+ <config-name>Standard WSSecurity Endpoint</config-name>
+ <post-handler-chains>
+ <javaee:handler-chain>
+ <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings>
+ <javaee:handler>
+ <javaee:handler-name>WSSecurity Handler</javaee:handler-name>
+ <javaee:handler-class>org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer</javaee:handler-class>
+ </javaee:handler>
+ </javaee:handler-chain>
+ </post-handler-chains>
+ </endpoint-config>
+
+</jaxws-config>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jaxb-api.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jaxb-api.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jaxb-impl.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jaxb-impl.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jboss-jaxws.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jboss-jaxws.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws-context.war
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws-context.war
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws-core.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws-core.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws-jboss42-integration.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws-jboss42-integration.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="urn:jboss:bean-deployer bean-deployer_1_0.xsd"
+ xmlns="urn:jboss:bean-deployer">
+
+ <bean name="KernelLocator" class="org.jboss.ws.integration.KernelLocator">
+ <property name="kernel"><inject bean="jboss.kernel:service=Kernel"/></property>
+ </bean>
+
+ <bean name="ServiceEndpointManager" class="org.jboss.ws.core.server.ServiceEndpointManager">
+
+ <!--
+ The WSDL, that is a required deployment artifact for an endpoint, has a <soap:address>
+ element which points to the location of the endpoint. JBoss supports rewriting of that SOAP address.
+
+ If the content of <soap:address> is a valid URL, JBossWS will not rewrite it unless 'alwaysModifySOAPAddress' is true.
+ If the content of <soap:address> is not a valid URL, JBossWS will rewrite it using the attribute values given below.
+
+ If next line (webServiceHost) is commented, JBossWS uses requesters protocolo, host and port when rewriting the <soap:address>.
+ -->
+ <property name="webServiceHost">${jboss.bind.address}</property>
+ <property name="alwaysModifySOAPAddress">true</property>
+
+ <!--
+ Set these properties to explicitly define the ports that will be used for rewriting the SOAP address.
+ Otherwise the ports will be identified by querying the list of installed connectors.
+ If multiple connectors are found the port of the first connector is used.
+ <property name="webServiceSecurePort">8443</property>
+ <property name="webServicePort">8080</property>
+ -->
+
+ <property name="serviceEndpointInvokerJSE">org.jboss.ws.core.server.ServiceEndpointInvokerJSE</property>
+ <property name="serviceEndpointInvokerEJB3">org.jboss.ws.integration.jboss42.ServiceEndpointInvokerEJB3</property>
+ <property name="serviceEndpointInvokerEJB21">org.jboss.ws.integration.jboss42.ServiceEndpointInvokerEJB21</property>
+ <property name="serviceEndpointInvokerMDB">org.jboss.ws.integration.jboss42.ServiceEndpointInvokerMDB</property>
+ </bean>
+
+ <bean name="ServiceEndpointDeployer" class="org.jboss.ws.core.server.ServiceEndpointDeployer">
+ <property name="serviceEndpointManager">
+ <inject bean="ServiceEndpointManager"/>
+ </property>
+ </bean>
+
+ <bean name="ServiceEndpointPublisher" class="org.jboss.ws.integration.jboss42.ServiceEndpointPublisher">
+ <property name="serviceEndpointServlet">org.jboss.ws.integration.jboss42.JBossServiceEndpointServlet</property>
+ </bean>
+
+ <!-- Bind Service objects in client environment context -->
+ <bean name="ServiceRefHandler" class="org.jboss.ws.core.client.ServiceRefHandlerImpl"/>
+
+ <!-- A subscription manager for WS-Eventing -->
+ <bean name="SubscriptionManager" class="org.jboss.ws.extensions.eventing.mgmt.SubscriptionManager"/>
+
+ <bean name="ServerConfig" class="org.jboss.ws.integration.jboss42.ServerConfigImpl"/>
+
+ <bean name="DeploymentInfoAdapter" class="org.jboss.ws.integration.jboss42.DeploymentInfoAdapter">
+ <property name="applicationMetaDataAdapter">
+ <inject bean="ApplicationMetaDataAdapter"/>
+ </property>
+ <property name="webMetaDataAdapter">
+ <inject bean="WebMetaDataAdapter"/>
+ </property>
+ </bean>
+ <bean name="ApplicationMetaDataAdapter" class="org.jboss.ws.integration.jboss42.ApplicationMetaDataAdapter"/>
+ <bean name="WebMetaDataAdapter" class="org.jboss.ws.integration.jboss42.WebMetaDataAdapter"/>
+
+</deployment>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/policy.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/policy.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/stax-api.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/stax-api.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/wsdl4j.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/wsdl4j.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/xmlsec.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jbossws.sar/xmlsec.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/hsqldb-jdbc-state-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/hsqldb-jdbc-state-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/hsqldb-jdbc-state-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: hsqldb-jdbc-state-service.xml 61572 2007-03-22 14:32:18Z adrian at jboss.org $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- JBossMQ State Management using HSQLDB -->
+ <!-- See docs/examples/jms for other configurations -->
+ <!-- ==================================================================== -->
+
+ <!-- A Statemanager that stores state in the database -->
+ <mbean code="org.jboss.mq.sm.jdbc.JDBCStateManager"
+ name="jboss.mq:service=StateManager">
+ <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
+ <attribute name="SqlProperties">
+ CREATE_TABLES_ON_STARTUP = TRUE
+ CREATE_USER_TABLE = CREATE TABLE JMS_USERS (USERID VARCHAR(32) NOT NULL, PASSWD VARCHAR(32) NOT NULL, \
+ CLIENTID VARCHAR(128) NULL, PRIMARY KEY(USERID))
+ CREATE_ROLE_TABLE = CREATE TABLE JMS_ROLES (ROLEID VARCHAR(32) NOT NULL, USERID VARCHAR(32) NOT NULL, \
+ PRIMARY KEY(USERID, ROLEID))
+ CREATE_SUBSCRIPTION_TABLE = CREATE TABLE JMS_SUBSCRIPTIONS (CLIENTID VARCHAR(128) NOT NULL, \
+ SUBNAME VARCHAR(128) NOT NULL, TOPIC VARCHAR(255) NOT NULL, \
+ SELECTOR VARCHAR(255) NULL, PRIMARY KEY(CLIENTID, SUBNAME))
+ GET_SUBSCRIPTION = SELECT TOPIC, SELECTOR FROM JMS_SUBSCRIPTIONS WHERE CLIENTID=? AND SUBNAME=?
+ LOCK_SUBSCRIPTION = SELECT TOPIC, SELECTOR FROM JMS_SUBSCRIPTIONS WHERE CLIENTID=? AND SUBNAME=?
+ GET_SUBSCRIPTIONS_FOR_TOPIC = SELECT CLIENTID, SUBNAME, SELECTOR FROM JMS_SUBSCRIPTIONS WHERE TOPIC=?
+ INSERT_SUBSCRIPTION = INSERT INTO JMS_SUBSCRIPTIONS (CLIENTID, SUBNAME, TOPIC, SELECTOR) VALUES(?,?,?,?)
+ UPDATE_SUBSCRIPTION = UPDATE JMS_SUBSCRIPTIONS SET TOPIC=?, SELECTOR=? WHERE CLIENTID=? AND SUBNAME=?
+ REMOVE_SUBSCRIPTION = DELETE FROM JMS_SUBSCRIPTIONS WHERE CLIENTID=? AND SUBNAME=?
+ GET_USER_BY_CLIENTID = SELECT USERID, PASSWD, CLIENTID FROM JMS_USERS WHERE CLIENTID=?
+ GET_USER = SELECT PASSWD, CLIENTID FROM JMS_USERS WHERE USERID=?
+ POPULATE.TABLES.01 = INSERT INTO JMS_USERS (USERID, PASSWD) VALUES ('guest', 'guest')
+ POPULATE.TABLES.02 = INSERT INTO JMS_USERS (USERID, PASSWD) VALUES ('j2ee', 'j2ee')
+ POPULATE.TABLES.03 = INSERT INTO JMS_USERS (USERID, PASSWD, CLIENTID) VALUES ('john', 'needle', 'DurableSubscriberExample')
+ POPULATE.TABLES.04 = INSERT INTO JMS_USERS (USERID, PASSWD) VALUES ('nobody', 'nobody')
+ POPULATE.TABLES.05 = INSERT INTO JMS_USERS (USERID, PASSWD) VALUES ('dynsub', 'dynsub')
+ POPULATE.TABLES.06 = INSERT INTO JMS_ROLES (ROLEID, USERID) VALUES ('guest','guest')
+ POPULATE.TABLES.07 = INSERT INTO JMS_ROLES (ROLEID, USERID) VALUES ('j2ee','guest')
+ POPULATE.TABLES.08 = INSERT INTO JMS_ROLES (ROLEID, USERID) VALUES ('john','guest')
+ POPULATE.TABLES.09 = INSERT INTO JMS_ROLES (ROLEID, USERID) VALUES ('subscriber','john')
+ POPULATE.TABLES.10 = INSERT INTO JMS_ROLES (ROLEID, USERID) VALUES ('publisher','john')
+ POPULATE.TABLES.11 = INSERT INTO JMS_ROLES (ROLEID, USERID) VALUES ('publisher','dynsub')
+ POPULATE.TABLES.12 = INSERT INTO JMS_ROLES (ROLEID, USERID) VALUES ('durpublisher','john')
+ POPULATE.TABLES.13 = INSERT INTO JMS_ROLES (ROLEID, USERID) VALUES ('durpublisher','dynsub')
+ POPULATE.TABLES.14 = INSERT INTO JMS_ROLES (ROLEID, USERID) VALUES ('noacc','nobody')
+ </attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/hsqldb-jdbc2-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/hsqldb-jdbc2-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/hsqldb-jdbc2-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: hsqldb-jdbc2-service.xml 38669 2005-12-02 02:51:48Z adrian $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Persistence and caching using HSQLDB -->
+ <!-- See docs/examples/jms for other configurations -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | The destination manager is the core service within JBossMQ
+ -->
+ <mbean code="org.jboss.mq.server.jmx.DestinationManager" name="jboss.mq:service=DestinationManager">
+ <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>
+ <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>
+ <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>
+ <depends optional-attribute-name="ThreadPool">jboss.mq:service=ThreadPool</depends>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+
+ <!--
+ | The MessageCache decides where to put JBossMQ message that
+ | are sitting around waiting to be consumed by a client.
+ |
+ | The memory marks are in Megabytes. Once the JVM memory usage hits
+ | the high memory mark, the old messages in the cache will start getting
+ | stored in the DataDirectory. As memory usage gets closer to the
+ | Max memory mark, the amount of message kept in the memory cache aproaches 0.
+ -->
+ <mbean code="org.jboss.mq.server.MessageCache"
+ name="jboss.mq:service=MessageCache">
+ <attribute name="HighMemoryMark">50</attribute>
+ <attribute name="MaxMemoryMark">60</attribute>
+ <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>
+ </mbean>
+
+ <!--
+ | The jdbc2 PersistenceManager is the new improved JDBC implementation.
+ | This implementation allows you to control how messages are stored in
+ | the database.
+ |
+ | Use this PM if you want the reliablity a relational database can offer
+ | you. The default configuration is known to work with hsqldb, other
+ | databases will requrie teaking of the SqlProperties e.g. changing table
+ | colum definitions to database supported types.
+ |
+ | Take care that the selected blob column type in jms_messages can store
+ | all message data. Some databases (e.g. mySQL) offer blob types with
+ | different maximum capacity (e.g. mySQL-type BLOB=64K, LONGBLOB=2G).
+ |
+ | If you encouter problems with the configured BLOB_TYPE try a different
+ | setting. Valid settings are OBJECT_BLOB, BINARYSTREAM_BLOB and BYTES_BLOB.
+ -->
+ <mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager"
+ name="jboss.mq:service=PersistenceManager">
+ <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
+ <attribute name="SqlProperties">
+ BLOB_TYPE=OBJECT_BLOB
+ INSERT_TX = INSERT INTO JMS_TRANSACTIONS (TXID) values(?)
+ INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
+ SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
+ SELECT_MAX_TX = SELECT MAX(TXID) TXID FROM (SELECT MAX(TXID) AS TXID FROM JMS_TRANSACTIONS UNION SELECT MAX(TXID) AS TXID FROM JMS_MESSAGES)
+ DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS
+ SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE_KEYS_IN_DEST = SELECT MESSAGEID FROM JMS_MESSAGES WHERE DESTINATION=?
+ SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
+ UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
+ UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
+ DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES WHERE TXOP=? AND JMS_MESSAGES.TXID IN (SELECT TXID FROM JMS_TRANSACTIONS)
+ DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?
+ DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?
+ DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T'
+ DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
+ CREATE_MESSAGE_TABLE = CREATE CACHED TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \
+ DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \
+ MESSAGEBLOB OBJECT, PRIMARY KEY (MESSAGEID, DESTINATION) )
+ CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX JMS_MESSAGES_TXOP_TXID ON JMS_MESSAGES (TXOP, TXID)
+ CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_MESSAGES_DESTINATION ON JMS_MESSAGES (DESTINATION)
+ CREATE_TX_TABLE = CREATE CACHED TABLE JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) )
+ CREATE_TABLES_ON_STARTUP = TRUE
+ </attribute>
+ <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
+ <!--attribute name="RecoveryTimeout">0</attribute-->
+ <!-- The number of blobs to load at once during message recovery -->
+ <attribute name="RecoverMessagesChunk">0</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-destinations-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-destinations-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-destinations-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: jbossmq-destinations-service.xml 25907 2004-11-16 04:32:39Z ejort $ -->
+
+<!--
+ | This file defines the default Queues and Topics that JBossMQ
+ | ships with. The default Queues and Topics are used by the
+ | JBoss test suite and by the sample jms programs.
+ |
+ | You can add other destinations to this file, or you can create other
+ | *-service.xml files to contain your application's destinations.
+ -->
+
+<server>
+ <!-- Destination without a configured SecurityManager or without a
+ a SecurityConf will default to role guest with read=true, write=true,
+ create=false.
+ -->
+ <mbean code="org.jboss.mq.server.jmx.Topic"
+ name="jboss.mq.destination:service=Topic,name=testTopic">
+ <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
+ <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
+ <attribute name="SecurityConf">
+ <security>
+ <role name="guest" read="true" write="true"/>
+ <role name="publisher" read="true" write="true" create="false"/>
+ <role name="durpublisher" read="true" write="true" create="true"/>
+ </security>
+ </attribute>
+ </mbean>
+
+ <mbean code="org.jboss.mq.server.jmx.Topic"
+ name="jboss.mq.destination:service=Topic,name=securedTopic">
+ <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
+ <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
+ <attribute name="SecurityConf">
+ <security>
+ <role name="publisher" read="true" write="true" create="false"/>
+ </security>
+ </attribute>
+ </mbean>
+
+ <mbean code="org.jboss.mq.server.jmx.Topic"
+ name="jboss.mq.destination:service=Topic,name=testDurableTopic">
+ <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
+ <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
+ <attribute name="SecurityConf">
+ <security>
+ <role name="guest" read="true" write="true"/>
+ <role name="publisher" read="true" write="true" create="false"/>
+ <role name="durpublisher" read="true" write="true" create="true"/>
+ </security>
+ </attribute>
+ </mbean>
+
+ <mbean code="org.jboss.mq.server.jmx.Queue"
+ name="jboss.mq.destination:service=Queue,name=testQueue">
+ <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
+ <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
+ <attribute name="MessageCounterHistoryDayLimit">-1</attribute>
+ <attribute name="SecurityConf">
+ <security>
+ <role name="guest" read="true" write="true"/>
+ <role name="publisher" read="true" write="true" create="false"/>
+ <role name="noacc" read="false" write="false" create="false"/>
+ </security>
+ </attribute>
+ </mbean>
+ <mbean code="org.jboss.mq.server.jmx.Queue"
+ name="jboss.mq.destination:service=Queue,name=A">
+ <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
+ </mbean>
+ <mbean code="org.jboss.mq.server.jmx.Queue"
+ name="jboss.mq.destination:service=Queue,name=B">
+ <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
+ </mbean>
+ <mbean code="org.jboss.mq.server.jmx.Queue"
+ name="jboss.mq.destination:service=Queue,name=C">
+ <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
+ </mbean>
+ <mbean code="org.jboss.mq.server.jmx.Queue"
+ name="jboss.mq.destination:service=Queue,name=D">
+ <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
+ </mbean>
+ <mbean code="org.jboss.mq.server.jmx.Queue"
+ name="jboss.mq.destination:service=Queue,name=ex">
+ <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/META-INF/MANIFEST.MF
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/META-INF/MANIFEST.MF (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/META-INF/MANIFEST.MF 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,4 @@
+Manifest-Version: 1.0
+Ant-Version: Apache Ant 1.6.2
+Created-By: 1.5.0_11-b03 (Sun Microsystems Inc.)
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/META-INF/jboss-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/META-INF/jboss-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/META-INF/jboss-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE server>
+<server>
+ <mbean code="org.jboss.mq.il.http.HTTPServerILService"
+ name="jboss.mq:service=InvocationLayer,type=HTTP">
+ <depends optional-attribute-name="Invoker">jboss.mq:service=Invoker</depends>
+ <depends>jboss.web:service=WebServer</depends>
+ <attribute name="ConnectionFactoryJNDIRef">HTTPConnectionFactory</attribute>
+ <attribute name="XAConnectionFactoryJNDIRef">HTTPXAConnectionFactory</attribute>
+ <attribute name="PingPeriod">0</attribute>
+ <attribute name="TimeOut">60</attribute>
+ <attribute name="RestInterval">0</attribute>
+ </mbean>
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/META-INF/MANIFEST.MF
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/META-INF/MANIFEST.MF (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/META-INF/MANIFEST.MF 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,4 @@
+Manifest-Version: 1.0
+Ant-Version: Apache Ant 1.6.2
+Created-By: 1.5.0_11-b03 (Sun Microsystems Inc.)
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/classes/org/jboss/mq/il/http/servlet/HTTPServerILServlet.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/classes/org/jboss/mq/il/http/servlet/HTTPServerILServlet.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/jboss-web.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/jboss-web.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/jboss-web.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,4 @@
+<jboss-web>
+ <security-domain>java:/jaas/jbossmq</security-domain>
+</jboss-web>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/web.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/web.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/web.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,77 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!DOCTYPE web-app
+ PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
+ "http://java.sun.com/dtd/web-app_2_3.dtd">
+
+<web-app>
+ <servlet>
+ <servlet-name>HTTPServerILServlet</servlet-name>
+ <display-name>JBossMQ HTTP-IL Servlet</display-name>
+ <description>Provides and HTTP invocation layer for JBossMQ</description>
+ <servlet-class>org.jboss.mq.il.http.servlet.HTTPServerILServlet</servlet-class>
+ <init-param>
+ <param-name>Invoker</param-name>
+ <param-value>jboss.mq:service=Invoker</param-value>
+ </init-param>
+ </servlet>
+ <servlet-mapping>
+ <servlet-name>HTTPServerILServlet</servlet-name>
+ <url-pattern>/HTTPServerILServlet/*</url-pattern>
+ </servlet-mapping>
+
+ <!-- Alternate mappings that place the servlets under the restricted
+ path to required authentication for access. Remove the unsecure mappings
+ if only authenticated users should be allowed.
+ -->
+ <servlet-mapping>
+ <servlet-name>HTTPServerILServlet</servlet-name>
+ <url-pattern>/restricted/HTTPServerILServlet/*</url-pattern>
+ </servlet-mapping>
+
+ <!-- An example security constraint that restricts access to the HTTP invoker
+ to users with the role HttpInvoker Edit the roles to what you want and
+ configure the WEB-INF/jboss-web.xml/security-domain element to reference
+ the security domain you want.
+ -->
+ <security-constraint>
+ <web-resource-collection>
+ <web-resource-name>HTTPServerILServlet</web-resource-name>
+ <description>An example security config that only allows users with the
+ role JBossMqHttpIl to access the HTTP-IL servlet
+ </description>
+ <url-pattern>/restricted/*</url-pattern>
+ <http-method>GET</http-method>
+ <http-method>POST</http-method>
+ </web-resource-collection>
+ <auth-constraint>
+ <role-name>durpublisher</role-name>
+ <role-name>publisher</role-name>
+ <role-name>guest</role-name>
+ <role-name>j2ee</role-name>
+ <role-name>subscriber</role-name>
+ </auth-constraint>
+ </security-constraint>
+ <login-config>
+ <auth-method>BASIC</auth-method>
+ <realm-name>JBossMQ</realm-name>
+ </login-config>
+
+ <security-role>
+ <role-name>durpublisher</role-name>
+ </security-role>
+ <security-role>
+ <role-name>publisher</role-name>
+ </security-role>
+ <security-role>
+ <role-name>guest</role-name>
+ </security-role>
+ <security-role>
+ <role-name>j2ee</role-name>
+ </security-role>
+ <security-role>
+ <role-name>subscriber</role-name>
+ </security-role>
+
+
+</web-app>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jbossmq-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,80 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: jbossmq-service.xml 38187 2005-11-16 23:55:44Z adrian $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- JBossMQ -->
+ <!-- ==================================================================== -->
+
+
+ <!-- ==================================================================== -->
+ <!-- JBossMQ Interceptor chain configuration -->
+ <!-- ==================================================================== -->
+ <!-- To tune performance, you can have the Invoker skip over the TracingInterceptor -->
+ <!-- and/or the SecurityManager, but then you loose the ability to trace and/or enforce security. -->
+ <mbean code="org.jboss.mq.server.jmx.Invoker" name="jboss.mq:service=Invoker">
+ <depends optional-attribute-name="NextInterceptor">jboss.mq:service=TracingInterceptor</depends>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+
+ <mbean code="org.jboss.mq.server.jmx.InterceptorLoader" name="jboss.mq:service=TracingInterceptor">
+ <attribute name="InterceptorClass">org.jboss.mq.server.TracingInterceptor</attribute>
+ <depends optional-attribute-name="NextInterceptor">jboss.mq:service=SecurityManager</depends>
+ </mbean>
+
+ <mbean code="org.jboss.mq.security.SecurityManager" name="jboss.mq:service=SecurityManager">
+ <attribute name="DefaultSecurityConfig">
+ <security>
+ <role name="guest" read="true" write="true" create="true"/>
+ </security>
+ </attribute>
+ <attribute name="SecurityDomain">java:/jaas/jbossmq</attribute>
+ <depends optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager</depends>
+ </mbean>
+
+ <!--
+ | The ClientMonitorInterceptor disconnects clients that have been idle for to long.
+ | This interceptor is not enabled by default since the server might disconnect clients
+ | when the it is under high load.
+ -->
+ <!--
+ <mbean code="org.jboss.mq.server.jmx.ClientMonitorInterceptor" name="jboss.mq:service=ClientMonitorInterceptor">
+ <attribute name="ClientTimeout">80000</attribute>
+ <depends optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager</depends>
+ </mbean>
+ -->
+
+ <!-- A Thread pool service -->
+ <mbean code="org.jboss.util.threadpool.BasicThreadPool"
+ name="jboss.mq:service=ThreadPool">
+ <attribute name="Name">JMSThread</attribute>
+ <attribute name="ThreadGroupName">JBossMQ Server Threads</attribute>
+ <!-- The max number of threads in the pool -->
+ <attribute name="MaximumPoolSize">10</attribute>
+ <!-- The max number of tasks before the queue is full -->
+ <attribute name="MaximumQueueSize">1000</attribute>
+ <!-- The behavior of the pool when a task is added and the queue is full.
+ abort - a RuntimeException is thrown
+ run - the calling thread executes the task
+ wait - the calling thread blocks until the queue has room
+ discard - the task is silently discarded without being run
+ discardOldest - check to see if a task is about to complete and enque
+ the new task if possible, else run the task in the calling thread
+ -->
+ <attribute name="BlockingMode">run</attribute>
+ </mbean>
+
+ <!-- ==================================================================== -->
+ <!-- System Destinations -->
+ <!-- ==================================================================== -->
+
+ <!-- Dead Letter Queue -->
+ <mbean code="org.jboss.mq.server.jmx.Queue"
+ name="jboss.mq.destination:service=Queue,name=DLQ">
+ <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
+ <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jms-ds.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jms-ds.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jms-ds.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<connection-factories>
+
+ <!-- ==================================================================== -->
+ <!-- JMS Stuff -->
+ <!-- ==================================================================== -->
+
+ <!-- The JMS provider loader -->
+ <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
+ name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
+ <attribute name="ProviderName">DefaultJMSProvider</attribute>
+ <attribute name="ProviderAdapterClass">
+ org.jboss.jms.jndi.JNDIProviderAdapter
+ </attribute>
+ <!-- The combined connection factory -->
+ <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
+ <!-- The queue connection factory -->
+ <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
+ <!-- The topic factory -->
+ <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
+ <!-- Uncomment to use HAJNDI to access JMS
+ <attribute name="Properties">
+ java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
+ java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
+ java.naming.provider.url=localhost:1100
+ </attribute>
+ -->
+ </mbean>
+
+ <!-- The server session pool for Message Driven Beans -->
+ <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
+ name="jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool">
+ <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
+ <attribute name="PoolName">StdJMSPool</attribute>
+ <attribute name="PoolFactoryClass">
+ org.jboss.jms.asf.StdServerSessionPoolFactory
+ </attribute>
+ </mbean>
+
+ <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
+ <tx-connection-factory>
+ <jndi-name>JmsXA</jndi-name>
+ <xa-transaction/>
+ <rar-name>jms-ra.rar</rar-name>
+ <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
+ <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
+ <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
+ <max-pool-size>20</max-pool-size>
+ <security-domain-and-application>JmsXARealm</security-domain-and-application>
+ </tx-connection-factory>
+
+</connection-factories>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jms-ra.rar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jms-ra.rar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jvm-il-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jvm-il-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/jvm-il-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: jvm-il-service.xml 16662 2003-08-27 04:38:22Z patriot1burke $ -->
+
+<server>
+
+ <!-- JBossMQ in memory "communication -->
+
+ <mbean code="org.jboss.mq.il.jvm.JVMServerILService"
+ name="jboss.mq:service=InvocationLayer,type=JVM">
+ <depends optional-attribute-name="Invoker">jboss.mq:service=Invoker</depends>
+ <attribute name="ConnectionFactoryJNDIRef">java:/ConnectionFactory</attribute>
+ <attribute name="XAConnectionFactoryJNDIRef">java:/XAConnectionFactory</attribute>
+ <attribute name="PingPeriod">0</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/uil2-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/uil2-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jms/uil2-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,85 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: uil2-service.xml 35297 2005-08-25 15:03:20Z starksm $ -->
+
+<server>
+
+ <!-- JBossMQ using the Unified Invocation Layer
+ All communication uses one socket connection -->
+
+ <mbean code="org.jboss.mq.il.uil2.UILServerILService"
+ name="jboss.mq:service=InvocationLayer,type=UIL2">
+
+ <!-- The server chain -->
+ <depends optional-attribute-name="Invoker">jboss.mq:service=Invoker</depends>
+ <!-- JNDI binding -->
+ <attribute name="ConnectionFactoryJNDIRef">ConnectionFactory</attribute>
+ <!-- JNDI binding for XA -->
+ <attribute name="XAConnectionFactoryJNDIRef">XAConnectionFactory</attribute>
+ <!-- The bind address -->
+ <attribute name="BindAddress">${jboss.bind.address}</attribute>
+ <!-- The bind port -->
+ <attribute name="ServerBindPort">8093</attribute>
+ <!-- The ping period in millis -->
+ <attribute name="PingPeriod">60000</attribute>
+ <!-- Whether tcp/ip does not wait for buffer fills -->
+ <attribute name="EnableTcpNoDelay">true</attribute>
+ <!-- Used to disconnect the client on the serverside if there is no activity -->
+ <!-- Ensure this is greater than the ping period -->
+ <attribute name="ReadTimeout">120000</attribute>
+ <!-- Used to disconnect the client on the clientside if there is no activity -->
+ <!-- Ensure this is greater than the ping period -->
+ <attribute name="ClientReadTimeout">120000</attribute>
+ <!-- The size of the buffer (in bytes) wrapping the socket -->
+ <!-- The buffer is flushed after each request -->
+ <attribute name="BufferSize">2048</attribute>
+ <!-- Large messages may block the ping/pong -->
+ <!-- A pong is simulated after each chunk (in bytes) for both reading and writing -->
+ <!-- It must be larger than the buffer size -->
+ <attribute name="ChunkSize">1000000</attribute>
+ </mbean>
+
+ <!-- Aliases UIL -> UIL2 for backwards compatibility
+ the deprecated UIL deployment can be found in docs/examples/jca -->
+ <mbean code="org.jboss.naming.NamingAlias" name="jboss.mq:service=InvocationLayer,type=UIL">
+ <attribute name="FromName">UILConnectionFactory</attribute>
+ <attribute name="ToName">ConnectionFactory</attribute>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+ <mbean code="org.jboss.naming.NamingAlias" name="jboss.mq:service=InvocationLayer,type=UILXA">
+ <attribute name="FromName">UILXAConnectionFactory</attribute>
+ <attribute name="ToName">XAConnectionFactory</attribute>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+ <mbean code="org.jboss.naming.NamingAlias"
+ name="jboss.mq:service=InvocationLayer,type=UIL2,alias=UIL2ConnectionFactory">
+ <attribute name="FromName">UIL2ConnectionFactory</attribute>
+ <attribute name="ToName">ConnectionFactory</attribute>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+ <mbean code="org.jboss.naming.NamingAlias"
+ name="jboss.mq:service=InvocationLayer,type=UIL2XA,alias=UIL2XAConnectionFactory">
+ <attribute name="FromName">UIL2XAConnectionFactory</attribute>
+ <attribute name="ToName">XAConnectionFactory</attribute>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+
+ <!--
+ Two JNDI bindings that act like jms client connections remotely
+ but have j2ee defined semantics inside JBoss
+ -->
+ <mbean code="org.jboss.naming.LinkRefPairService"
+ name="jboss.jms:alias=QueueConnectionFactory">
+ <attribute name="JndiName">QueueConnectionFactory</attribute>
+ <attribute name="RemoteJndiName">ConnectionFactory</attribute>
+ <attribute name="LocalJndiName">java:/JmsXA</attribute>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+ <mbean code="org.jboss.naming.LinkRefPairService"
+ name="jboss.jms:alias=TopicConnectionFactory">
+ <attribute name="JndiName">TopicConnectionFactory</attribute>
+ <attribute name="RemoteJndiName">ConnectionFactory</attribute>
+ <attribute name="LocalJndiName">java:/JmsXA</attribute>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/META-INF/MANIFEST.MF
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/META-INF/MANIFEST.MF (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/META-INF/MANIFEST.MF 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,4 @@
+Manifest-Version: 1.0
+Ant-Version: Apache Ant 1.6.2
+Created-By: 1.5.0_11-b03 (Sun Microsystems Inc.)
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/AddressPort.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/AddressPort.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/AttrResultInfo.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/AttrResultInfo.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/OpResultInfo.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/OpResultInfo.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/Server.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/control/Server.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/html/ClusteredConsoleServlet.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/html/ClusteredConsoleServlet.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/html/HtmlAdaptorServlet.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/html/HtmlAdaptorServlet.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/html/JMXOpsAccessControlFilter.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/html/JMXOpsAccessControlFilter.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/model/DomainData.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/model/DomainData.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/model/MBeanData.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/classes/org/jboss/jmx/adaptor/model/MBeanData.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/jboss-web.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/jboss-web.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/jboss-web.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,7 @@
+<jboss-web>
+ <!-- Uncomment the security-domain to enable security. You will
+ need to edit the htmladaptor login configuration to setup the
+ login modules used to authentication users.
+ <security-domain>java:/jaas/jmx-console</security-domain>
+ -->
+</jboss-web>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/web.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/web.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/WEB-INF/web.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,109 @@
+<?xml version="1.0"?>
+<!DOCTYPE web-app PUBLIC
+ "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
+ "http://java.sun.com/dtd/web-app_2_3.dtd">
+
+<web-app>
+ <description>The standard web descriptor for the html adaptor</description>
+ <!--
+ <filter>
+ <filter-name>JmxOpsAccessControlFilter</filter-name>
+ <filter-class>org.jboss.jmx.adaptor.html.JMXOpsAccessControlFilter</filter-class>
+ <init-param>
+ <param-name>updateAttributes</param-name>
+ <param-value>UpdateAttributeRole</param-value>
+ <description>Comma-delimited Roles that define the JMX Operation denoting updation of Attributes</description>
+ </init-param>
+ <init-param>
+ <param-name>invokeOp</param-name>
+ <param-value>InvokeOpRole</param-value>
+ <description>Comma-delimited Roles that define the JMX Operation denoting Invocation of Operations</description>
+ </init-param>
+ </filter>
+ <filter-mapping>
+ <filter-name>JmxOpsAccessControlFilter</filter-name>
+ <servlet-name>HtmlAdaptor</servlet-name>
+ </filter-mapping>
+ -->
+ <servlet>
+ <servlet-name>HtmlAdaptor</servlet-name>
+ <servlet-class>org.jboss.jmx.adaptor.html.HtmlAdaptorServlet</servlet-class>
+ </servlet>
+ <servlet>
+ <servlet-name>ClusteredConsoleServlet</servlet-name>
+ <servlet-class>org.jboss.jmx.adaptor.html.ClusteredConsoleServlet</servlet-class>
+ <init-param>
+ <param-name>jgProps</param-name>
+ <param-value>UDP(ip_mcast=true;ip_ttl=16;loopback=false;mcast_addr=${jboss.partition.udpGroup:228.1.2.3};mcast_port=${jboss.partition.udpPort:45566}):
+org.jboss.jmx.adaptor.control.FindView
+ </param-value>
+ <description>The JGroups protocol stack config</description>
+ </init-param>
+ </servlet>
+ <servlet>
+ <servlet-name>DisplayMBeans</servlet-name>
+ <jsp-file>/displayMBeans.jsp</jsp-file>
+ </servlet>
+ <servlet>
+ <servlet-name>InspectMBean</servlet-name>
+ <jsp-file>/inspectMBean.jsp</jsp-file>
+ </servlet>
+ <servlet>
+ <servlet-name>DisplayOpResult</servlet-name>
+ <jsp-file>/displayOpResult.jsp</jsp-file>
+ </servlet>
+ <servlet>
+ <servlet-name>ClusterView</servlet-name>
+ <jsp-file>/cluster/clusterView.jsp</jsp-file>
+ </servlet>
+
+ <servlet-mapping>
+ <servlet-name>HtmlAdaptor</servlet-name>
+ <url-pattern>/HtmlAdaptor</url-pattern>
+ </servlet-mapping>
+ <servlet-mapping>
+ <servlet-name>ClusteredConsoleServlet</servlet-name>
+ <url-pattern>/cluster/ClusteredConsole</url-pattern>
+ </servlet-mapping>
+ <servlet-mapping>
+ <servlet-name>DisplayMBeans</servlet-name>
+ <url-pattern>/DisplayMBeans</url-pattern>
+ </servlet-mapping>
+ <servlet-mapping>
+ <servlet-name>InspectMBean</servlet-name>
+ <url-pattern>/InspectMBean</url-pattern>
+ </servlet-mapping>
+ <servlet-mapping>
+ <servlet-name>DisplayOpResult</servlet-name>
+ <url-pattern>/DisplayOpResult</url-pattern>
+ </servlet-mapping>
+
+ <!-- A security constraint that restricts access to the HTML JMX console
+ to users with the role JBossAdmin. Edit the roles to what you want and
+ uncomment the WEB-INF/jboss-web.xml/security-domain element to enable
+ secured access to the HTML JMX console.
+ <security-constraint>
+ <web-resource-collection>
+ <web-resource-name>HtmlAdaptor</web-resource-name>
+ <description>An example security config that only allows users with the
+ role JBossAdmin to access the HTML JMX console web application
+ </description>
+ <url-pattern>/*</url-pattern>
+ <http-method>GET</http-method>
+ <http-method>POST</http-method>
+ </web-resource-collection>
+ <auth-constraint>
+ <role-name>JBossAdmin</role-name>
+ </auth-constraint>
+ </security-constraint>
+ -->
+
+ <login-config>
+ <auth-method>BASIC</auth-method>
+ <realm-name>JBoss JMX Console</realm-name>
+ </login-config>
+
+ <security-role>
+ <role-name>JBossAdmin</role-name>
+ </security-role>
+</web-app>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/checkJNDI.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/checkJNDI.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/checkJNDI.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,112 @@
+<%@page contentType="text/html"
+ import="java.net.*,java.util.*,javax.naming.*,java.io.*"
+%>
+<html>
+<head>
+ <title>JBoss JNDI Check</title>
+ <link rel="stylesheet" href="style_master.css" type="text/css">
+ <meta http-equiv="cache-control" content="no-cache">
+</head>
+<body>
+<table width="100%">
+ <table>
+ <tr>
+ <td><img src="images/logo.gif" align="left" border="0" alt="JBoss"></td>
+ <td valign="middle">
+ <%
+ String hostname = "<<Unknown - see log/server.log>>";
+ try
+ {
+ hostname = InetAddress.getLocalHost().getHostName();
+ }
+ catch(IOException e)
+ {
+ e.printStackTrace();
+ }
+ %>
+ <h1>JNDI Checking for host <code><%= hostname %></code></h1>
+ </td>
+ </tr>
+ </table>
+<hr>
+<table border='1'>
+ <tr>
+ <td><h2>Test</h2></td>
+ <td><h2>Result</h2></td>
+ </tr>
+ <tr>
+ <td>InitialContext properites</td>
+ <td><table border='1'>
+ <%
+ try
+ {
+ InitialContext ctx = new InitialContext();
+ Hashtable props = ctx.getEnvironment();
+ for (Iterator i = props.keySet().iterator(); i.hasNext();)
+ {
+ Object key = i.next();
+ out.print("<tr><td>");
+ out.print(key);
+ out.print('=');
+ out.print(props.get(key));
+ out.print("</td></tr>");
+ }
+ }
+ catch (NamingException e)
+ {
+ out.print(e.toString());
+ }
+ %>
+ </table></td>
+ </tr>
+ <tr>
+ <td>jndi.properties locations</td>
+ <td><table border='1'>
+ <%
+ ClassLoader loader = Thread.currentThread().getContextClassLoader();
+ for (Enumeration e = loader.getResources("jndi.properties"); e.hasMoreElements();)
+ {
+ out.print("<tr><td>");
+ out.print(e.nextElement());
+ out.print("</td></tr>");
+ }
+ %>
+ </table></td>
+ </tr>
+ <tr>
+ <td>Global bindings</td>
+ <td><table border='1'>
+ <%
+ try
+ {
+ for (Enumeration e = new InitialContext().listBindings(""); e.hasMoreElements();)
+ {
+ out.print("<tr><td>");
+ out.print(e.nextElement());
+ out.print("</td></tr>");
+ }
+ }
+ catch (NamingException ignored) {}
+ %>
+ </table></td>
+ </tr>
+ <tr>
+ <td>JVM local bindings</td>
+ <td><table border='1'>
+ <%
+ try
+ {
+ for (Enumeration e = new InitialContext().listBindings("java:"); e.hasMoreElements();)
+ {
+ out.print("<tr><td>");
+ out.print(e.nextElement());
+ out.print("</td></tr>");
+ }
+ }
+ catch (NamingException ignored) {}
+ %>
+ </table></td>
+ </tr>
+</table>
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/bootstrap.html
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/bootstrap.html (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/bootstrap.html 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,69 @@
+<html>
+<head>
+ <title>Cluster View Bootstrap</title>
+ <link rel="stylesheet" href="../style_master.css" type="text/css">
+</head>
+
+<table>
+ <tr>
+ <td width="250" ><img src="../images/logo.gif" align="left" border="0" alt=""></td>
+ <td><h1>JBoss Cluster Bootstrap</h1></td>
+ </tr>
+</table>
+<hr>
+<body>
+The cluster nodes to view need to be specified via some bootstrap mechanism.
+This can be done using any of the following methods.
+
+<h1>Bootstrap Using Naming Discovery</h1>
+This determines the cluster entry point by doing an HAJNDI naming service
+discovery query. The query may be restricted to a given partition name by
+specifying the name in the PartitionName field.
+If not specified than the first partition to respond will be choosen.
+<form action="ClusteredConsole?action=bootstrap" method="post" target="ClusterIndex">
+ <input type="hidden" name="bootstrap" value="discovery">
+ <table cellspacing="2" cellpadding="2" border="0">
+ <tr>
+ <td>PartitionName:</td><td><input type="text" name="partition" size="40"></td>
+ </tr>
+ <tr>
+ <td>DiscoveryName:</td><td><input type="text" name="discoveryGroup" size="40" value="230.0.0.4"></td>
+ </tr>
+ <tr>
+ <td>DiscoveryPort:</td><td><input type="text" name="discoveryPort" size="40" value="1102"></td>
+ </tr>
+ <tr>
+ <td>DiscoveryTimeout:</td><td><input type="text" name="discoveryTimeout" size="40" value="5000"></td>
+ </tr>
+ <tr>
+ <td><input type="reset" name="reset" value="Clear"></td>
+ <td><input type="submit" name="submit" value="Bootstrap"></td>
+ </tr>
+ </table>
+</form>
+
+<h1>Bootstrap Using a Hostname</h1>
+This determines the cluster entry point(s) by querying the JNDI service
+on the indicated server for the available cluster paritition services.
+Any cluster to which the server belongs will serve as an entry point for
+determining the members of the cluster. To query the server hosting the
+jmx-console application use "locahost" for the hostname.
+<form action="ClusteredConsole" method="post" target="ClusterIndex">
+ <input type="hidden" name="bootstrap" value="byhost">
+ <table cellspacing="2" cellpadding="2" border="0">
+ <tr>
+ <td>Hostname:</td><td><input type="text" name="hostname" value="localhost" size="40"></td>
+ </tr>
+ <tr>
+ <td>Port:</td><td><input type="text" name="port" value="1099" size="40"></td>
+ </tr>
+ <tr>
+ <td><input type="reset" name="reset" value="Clear"></td>
+ <td><input type="submit" name="submit" value="Bootstrap"></td>
+ </tr>
+ </table>
+</form>
+
+</body>
+</html>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/clusterView.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/clusterView.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/clusterView.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,44 @@
+<%@page contentType="text/html"
+ import="java.net.*,java.io.*"
+%>
+<html>
+<head><title>Clustered JBoss Management Console</title>
+<link rel="stylesheet" href="../style_master.css" type="text/css">
+</head>
+<body>
+<table>
+<tr><td>
+<h2>Cluster View Bootstrap</h2>
+<a href="bootstrap.html" target="ClusterNodeView">Reinvoke Bootstrap</a>
+
+<h2>Loaded Clusters</h2>
+<%
+ String partition = (String) request.getAttribute("partition");
+%>
+ <h3 class='DomainName'><%= partition %></h2>
+ <ul class='MBeanList'>
+<%
+ String[] partitionHosts = (String[]) request.getAttribute("partitionHosts");
+ for(int h = 0; h < partitionHosts.length; h ++)
+ {
+ String host = partitionHosts[h];
+ String hostname = "";
+
+ try
+ {
+ hostname = InetAddress.getByName(host).getHostName();
+ }
+ catch(IOException e) {}
+
+ String hostURL = "http://"+host+":8080/jmx-console//HtmlAdaptor?action=displayMBeans";
+%>
+ <li><a href="<%= hostURL%>" target="ClusterNodeView"><%= hostname %></a></li>
+<%
+ }
+%>
+ </ul>
+</td></tr>
+</table>
+
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/index.html
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/index.html (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/cluster/index.html 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,6 @@
+<!-- frames -->
+<frameset cols="20%, *">
+ <frame name="ClusterIndex" src="ClusteredConsole?action=index" marginwidth="10" marginheight="10" scrolling="auto" frameborder="0">
+ <frame name="ClusterNodeView" src="bootstrap.html" marginwidth="10" marginheight="10" scrolling="auto" frameborder="0">
+ <noframes>A frames enabled browser is required for the cluster view</noframes>
+</frameset>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/displayMBeans.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/displayMBeans.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/displayMBeans.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,59 @@
+<%@page contentType="text/html"
+ import="java.net.*,java.util.*,org.jboss.jmx.adaptor.model.*,java.io.*"
+%>
+<html>
+<head>
+ <title>JBoss JMX Management Console</title>
+ <link rel="stylesheet" href="style_master.css" type="text/css">
+ <meta http-equiv="cache-control" content="no-cache">
+</head>
+<body>
+<table width="100%">
+ <table>
+ <tr>
+ <td><img src="images/logo.gif" align="left" border="0" alt="JBoss"></td>
+ <td valign="middle">
+ <%
+ String hostname = "";
+ try
+ {
+ hostname = InetAddress.getLocalHost().getHostName();
+ }
+ catch(IOException e) {}
+ %>
+ <h1>JMX Agent View <code><%= hostname %></code></h1>
+ </td>
+ </tr>
+ </table>
+<hr>
+<form action="HtmlAdaptor?action=displayMBeans" method="post" name="applyFilter" id="applyFilter">
+ObjectName Filter (e.g. "jboss:*", "*:service=invoker,*") :<input type="text" name="filter" size="40" value="<%= request.getAttribute("filter")%>"> <input type="submit" name="apply" value="ApplyFilter">
+</form>
+<hr>
+<%
+ Iterator mbeans = (Iterator) request.getAttribute("mbeans");
+ while( mbeans.hasNext() )
+ {
+ DomainData domainData = (DomainData) mbeans.next();
+%>
+ <h2 class='DomainName'><%= domainData.getDomainName() %></h2>
+ <ul class='MBeanList'>
+<%
+ MBeanData[] data = domainData.getData();
+ for(int d = 0; d < data.length; d ++)
+ {
+ String name = data[d].getObjectName().toString();
+ String properties = data[d].getNameProperties();
+%>
+ <li><a href="HtmlAdaptor?action=inspectMBean&name=<%= URLEncoder.encode(name) %>"><%= URLDecoder.decode(properties) %></a></li>
+<%
+ }
+%>
+ </ul>
+<%
+ }
+%>
+</td></tr>
+</table>
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/displayOpResult.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/displayOpResult.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/displayOpResult.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,74 @@
+<%@page contentType="text/html"
+ import="java.net.*"
+%>
+<html>
+<head>
+ <title>Operation Results</title>
+ <link rel="stylesheet" href="style_master.css" type="text/css">
+ <meta http-equiv="cache-control" content="no-cache">
+</head>
+<body>
+
+<jsp:useBean id='opResultInfo' type='org.jboss.jmx.adaptor.control.OpResultInfo' scope='request'/>
+
+<table width="100%">
+ <table>
+ <tr>
+ <td><img src="images/logo.gif" align="left" border="0" alt="JBoss"></td>
+ <td valign="middle"><h1>JMX MBean Operation Result <code><%= opResultInfo.name%>()</code></h1></td>
+ <tr/>
+ </table>
+
+<tr><td>
+
+
+<table cellpadding="5">
+ <tr>
+ <td><a href='HtmlAdaptor?action=displayMBeans'>Back to Agent View</a></td>
+ <td>
+ <td><a href='HtmlAdaptor?action=inspectMBean&name=<%= URLEncoder.encode(request.getParameter("name")) %>'>Back to MBean View</a></td>
+ <td>
+ <td><a href=
+<%
+ out.print("'HtmlAdaptor?action=invokeOpByName");
+ out.print("&name=" + URLEncoder.encode(request.getParameter("name")));
+ out.print("&methodName=" + opResultInfo.name );
+
+ for (int i=0; i<opResultInfo.args.length; i++)
+ {
+ out.print("&argType=" + opResultInfo.signature[i]);
+ out.print("&arg" + i + "=" + opResultInfo.args[i]);
+ }
+
+ out.println("'>Reinvoke MBean Operation");
+%>
+ </a></td>
+ </tr>
+</table>
+
+
+<hr>
+ <span class='OpResult'>
+<%
+ if( opResultInfo.result == null )
+ {
+%>
+ Operation completed successfully without a return value.
+<%
+ }
+ else
+ {
+ String opResultString = opResultInfo.result.toString();
+ boolean hasPreTag = opResultString.startsWith("<pre>");
+ if( hasPreTag == false )
+ out.println("<pre>");
+ out.println(opResultString);
+ if( hasPreTag == false )
+ out.println("</pre>");
+ }
+%>
+ </span>
+</td></tr>
+</table>
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/images/logo.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/images/logo.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/index.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/index.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/index.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,2 @@
+<%@page contentType="text/html"%>
+<jsp:forward page="/HtmlAdaptor?action=displayMBeans" />
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/inspectMBean.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/inspectMBean.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/inspectMBean.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,331 @@
+<%@page contentType="text/html"
+ import="java.net.*,java.util.*,
+ javax.management.*,javax.management.modelmbean.*,
+ org.jboss.jmx.adaptor.control.Server,
+ org.jboss.jmx.adaptor.control.AttrResultInfo,
+ org.jboss.jmx.adaptor.model.*,
+ java.lang.reflect.Array,
+ org.jboss.util.propertyeditor.PropertyEditors"
+%>
+<%!
+ public String fixDescription(String desc)
+ {
+ if (desc == null || desc.equals(""))
+ {
+ return "(no description)";
+ }
+ return desc;
+ }
+ public String quoteName(String name)
+ {
+ String sname = name.replace("\"", """);
+ sname = name.replace("\'", "'");
+ return sname;
+ }
+%>
+<html>
+<head>
+ <title>MBean Inspector</title>
+ <link rel="stylesheet" href="style_master.css" type="text/css">
+ <meta http-equiv="cache-control" content="no-cache">
+</head>
+<body>
+
+<jsp:useBean id='mbeanData' class='org.jboss.jmx.adaptor.model.MBeanData' scope='request'/>
+
+<%
+ ObjectName objectName = mbeanData.getObjectName();
+ String objectNameString = mbeanData.getName();
+ String quotedObjectNameString = quoteName(mbeanData.getName());
+ MBeanInfo mbeanInfo = mbeanData.getMetaData();
+ MBeanAttributeInfo[] attributeInfo = mbeanInfo.getAttributes();
+ MBeanOperationInfo[] operationInfo = mbeanInfo.getOperations();
+%>
+
+<table width="100%">
+ <table>
+ <tr>
+ <td><img src="images/logo.gif" align="left" border="0" alt="JBoss"></td>
+ <td valign="middle"><h1>JMX MBean View</h1></td>
+ <tr/>
+ </table>
+ <ul>
+ <table>
+ <tr>
+ <td>MBean Name:</td>
+ <td><b>Domain Name:</b></td>
+ <td><%= objectName.getDomain() %></td>
+ </tr>
+<%
+ Hashtable properties = objectName.getKeyPropertyList();
+ Iterator it = properties.keySet().iterator();
+ while( it.hasNext() )
+ {
+ String key = (String) it.next();
+ String value = (String) properties.get( key );
+%>
+ <tr><td></td><td><b><%= key %>: </b></td><td><%= value %></td></tr>
+<%
+ }
+%>
+ <tr><td>MBean Java Class:</td><td colspan="3"><jsp:getProperty name='mbeanData' property='className'/></td></tr>
+ </table>
+</ul>
+<table cellpadding="5">
+ <tr>
+ <td><a href='HtmlAdaptor?action=displayMBeans'>Back to Agent View</a></td>
+ <td>
+ <td><a href='HtmlAdaptor?action=inspectMBean&name=<%= URLEncoder.encode(request.getParameter("name")) %>'>Refresh MBean View</a></td>
+ </tr>
+</table>
+
+<hr>
+<h3>MBean description:</h3>
+<%= fixDescription(mbeanInfo.getDescription())%>
+
+<hr>
+<h3>List of MBean attributes:</h3>
+
+<form method="post" action="HtmlAdaptor">
+ <input type="hidden" name="action" value="updateAttributes">
+ <input type="hidden" name="name" value='<%= quotedObjectNameString %>'>
+ <table cellspacing="1" cellpadding="1" border="1">
+ <tr class="AttributesHeader">
+ <th>Name</th>
+ <th>Type</th>
+ <th>Access</th>
+ <th>Value</th>
+ <th>Description</th>
+ </tr>
+<%
+ boolean hasWriteable = false;
+ for(int a = 0; a < attributeInfo.length; a ++)
+ {
+ MBeanAttributeInfo attrInfo = attributeInfo[a];
+ String attrName = attrInfo.getName();
+ String attrType = attrInfo.getType();
+ AttrResultInfo attrResult = Server.getMBeanAttributeResultInfo(objectNameString, attrInfo);
+ String attrValue = attrResult.getAsText();
+ String access = "";
+ if( attrInfo.isReadable() )
+ access += "R";
+ if( attrInfo.isWritable() )
+ {
+ access += "W";
+ hasWriteable = true;
+ }
+ String attrDescription = fixDescription(attrInfo.getDescription());
+%>
+ <tr>
+ <td><%= attrName %></td>
+ <td><%= attrType %></td>
+ <td><%= access %></td>
+ <td>
+<%
+ if( attrInfo.isWritable() )
+ {
+ String readonly = attrResult.editor == null ? "readonly" : "";
+ if( attrType.equals("boolean") || attrType.equals("java.lang.Boolean") )
+ {
+ // Boolean true/false radio boxes
+ Boolean value = attrValue == null || "".equals( attrValue ) ? null : Boolean.valueOf(attrValue);
+ String trueChecked = (value == Boolean.TRUE ? "checked" : "");
+ String falseChecked = (value == Boolean.FALSE ? "checked" : "");
+ String naChecked = value == null ? "checked" : "";
+%>
+ <input type="radio" name="<%= attrName %>" value="True" <%=trueChecked%>>True
+ <input type="radio" name="<%= attrName %>" value="False" <%=falseChecked%>>False
+<%
+ // For wrappers, enable a 'null' selection
+ if ( attrType.equals( "java.lang.Boolean" ) && PropertyEditors.isNullHandlingEnabled() )
+ {
+%>
+ <input type="radio" name="<%= attrName %>" value="" <%=naChecked%>>Null
+<%
+ }
+ }
+ else if( attrInfo.isReadable() )
+ { // Text fields for read-write string values
+ String avalue = (attrValue != null ? attrValue : "");
+ if( attrType.equals("javax.management.ObjectName") )
+ avalue = quoteName(avalue);
+%>
+ <input type="text" name="<%= attrName %>" value='<%= avalue %>' <%= readonly %>>
+
+<%
+ }
+ else
+ { // Empty text fields for write-only
+%>
+ <input type="text" name="<%= attrName %>" <%= readonly %>>
+<%
+ }
+ }
+ else
+ {
+ if( attrType.equals("[Ljavax.management.ObjectName;") )
+ {
+ // Array of Object Names
+ ObjectName[] names = (ObjectName[]) Server.getMBeanAttributeObject(objectNameString, attrName);
+ if( names != null )
+ {
+%>
+ <table>
+<%
+ for( int i = 0; i < names.length; i++ )
+ {
+%>
+ <tr><td>
+ <a href="HtmlAdaptor?action=inspectMBean&name=<%= URLEncoder.encode(( names[ i ] + "" )) %>"><%= ( names[ i ] + "" ) %></a>
+ </td></tr>
+<%
+ }
+%>
+ </table>
+<%
+ }
+ }
+ // Array of some objects
+ else if( attrType.endsWith("[]") || attrType.startsWith("[L") )
+ {
+ Object arrayObject = Server.getMBeanAttributeObject(objectNameString, attrName);
+ if (arrayObject != null)
+ {
+%>
+ <table>
+<%
+ for (int i = 0; i < Array.getLength(arrayObject); ++i)
+ {
+%>
+ <tr><td><%=Array.get(arrayObject,i)%></td></tr>
+<%
+ }
+%>
+ </table>
+<%
+ }
+ }
+ else
+ {
+ // Just the value string
+%>
+ <%= attrValue %>
+<%
+ }
+ }
+ if( attrType.equals("javax.management.ObjectName") )
+ {
+ // Add a link to the mbean
+ if( attrValue != null )
+ {
+%>
+ <a href="HtmlAdaptor?action=inspectMBean&name=<%= URLEncoder.encode(attrValue) %>">View MBean</a>
+<%
+ }
+ }
+%>
+ </td>
+ <td><%= attrDescription%></td>
+ </tr>
+<%
+ }
+%>
+ </table>
+<% if( hasWriteable )
+ {
+%>
+ <input type="submit" value="Apply Changes">
+<%
+ }
+%>
+</form>
+
+<hr>
+<h3>List of MBean operations:</h3>
+<%
+ for(int a = 0; a < operationInfo.length; a ++)
+ {
+ MBeanOperationInfo opInfo = operationInfo[a];
+ boolean accept = true;
+ if (opInfo instanceof ModelMBeanOperationInfo)
+ {
+ Descriptor desc = ((ModelMBeanOperationInfo)opInfo).getDescriptor();
+ String role = (String)desc.getFieldValue("role");
+ if ("getter".equals(role) || "setter".equals(role))
+ {
+ accept = false;
+ }
+ }
+ if (accept)
+ {
+ MBeanParameterInfo[] sig = opInfo.getSignature();
+%>
+<form method="post" action="HtmlAdaptor">
+ <input type="hidden" name="action" value="invokeOp">
+ <input type="hidden" name="name" value='<%= quotedObjectNameString %>'>
+ <input type="hidden" name="methodIndex" value="<%= a %>">
+ <hr align='left' width='80'>
+ <h4><%= opInfo.getReturnType() + " " + opInfo.getName() + "()" %></h4>
+ <p><%= fixDescription(opInfo.getDescription())%></p>
+<%
+ if( sig.length > 0 )
+ {
+%>
+ <table cellspacing="2" cellpadding="2" border="1">
+ <tr class="OperationHeader">
+ <th>Param</th>
+ <th>ParamType</th>
+ <th>ParamValue</th>
+ <th>ParamDescription</th>
+ </tr>
+<%
+ for(int p = 0; p < sig.length; p ++)
+ {
+ MBeanParameterInfo paramInfo = sig[p];
+ String pname = paramInfo.getName();
+ String ptype = paramInfo.getType();
+ if( pname == null || pname.length() == 0 || pname.equals(ptype) )
+ {
+ pname = "arg"+p;
+ }
+%>
+ <tr>
+ <td><%= pname %></td>
+ <td><%= ptype %></td>
+ <td>
+<%
+ if( ptype.equals("boolean") || ptype.equals("java.lang.Boolean") )
+ {
+ // Boolean true/false radio boxes
+%>
+ <input type="radio" name="arg<%= p%>" value="True"checked>True
+ <input type="radio" name="arg<%= p%>" value="False">False
+<%
+ }
+ else
+ {
+%>
+ <input type="text" name="arg<%= p%>">
+<%
+ }
+%>
+ </td>
+ <td><%= fixDescription(paramInfo.getDescription())%></td>
+ </tr>
+<%
+ }
+%>
+ </table>
+<%
+ }
+%>
+ <input type="submit" value="Invoke">
+</form>
+<%
+ }
+ }
+%>
+</td></tr>
+</table>
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/jboss.css
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/jboss.css (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/jboss.css 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,146 @@
+body {
+ margin: 13px 0px 10px 0px;
+ background-color: #ffffff;
+ font-size: 12px;
+ font-family: verdana, arial, "sans-serif";
+ color: #606060;
+ }
+td {
+ font-size: 12px;
+ font-family: verdana, arial, "sans-serif";
+ color: #606060;
+ }
+input {
+ font-size: 13px;
+ font-family: verdana, arial, "sans-serif";
+ color: #FF5906;
+ background-color: #f0f0f0;
+ border: 1px solid #cccccc;
+ }
+img {
+ border: 0px;
+ }
+p {
+ margin: 10px 30px 10px 20px
+ }
+h3 {
+ color: #FF5906;
+ font-size: 13px;
+ font-family: verdana, arial, "sans-serif";
+ margin: 10px 30px 10px 20px;
+ }
+h4 {
+ color: #999999;
+ font-size: 13px;
+ font-family: verdana, arial, "sans-serif";
+ margin: 10px 30px 10px 20px;
+ }
+table {
+ border: 0px #999999;
+ }
+a {
+ text-decoration : none;
+ }
+a:link {
+ color: #FF5906;
+ }
+a:visited {
+ color: #FF5906;
+ }
+a:active {
+ background-color:transparent;
+ }
+a:hover {
+ text-decoration : underline;
+ }
+a.soft, a.soft:visited, a.soft:link {
+ TEXT-DECORATION: none;
+ COLOR: #000000;
+ }
+a.soft:hover {
+ TEXT-DECORATION: underline;
+ BACKGROUND-COLOR: transparent;
+ COLOR: #000000
+ }
+#header {
+ background-color: #FF7A22;
+ background-image: url("header_bg.jpg");
+ background-repeat: no-repeat;
+ background-position: 226px 0px;
+ width: 100%;
+ height: 80px;
+ }
+#header #banner {
+ float: right;
+ margin: 8px 5px 0px 0px;
+ }
+#logo {
+ position: absolute;
+ top: 4px;
+ left: 4px;
+ z-index: 200;
+}
+#services {
+ position: absolute;
+ top: 16px;
+ right: 10px;
+ z-index: 200;
+}
+#filter {
+ position: absolute;
+ top: 65px;
+ right: 30px;
+ z-index: 220;
+}
+#filter_label {
+ position: absolute;
+ top: 61px;
+ right: 215px;
+ z-index: 220;
+}
+#apply {
+ position: absolute;
+ top: -5px;
+ right: -30px;
+ z-index: 220;
+ border: none;
+}
+#navigation_bar {
+ background-color: #f0f0f0;
+ border-bottom: 1px dotted #999999;
+ height: 20px;
+ }
+#separator_bar {
+ background-color: #ffffff;
+ border-bottom: 1px dotted #999999;
+ height: 20px;
+ }
+#footer {
+ clear: both;
+ border-top: 1px dotted #999999;
+ }
+#footer_bar {
+ height: 20px;
+ width: 100%;
+ background-color: #FF7A22;
+ }
+.attribute_link a {
+ color: #606060;
+ text-decoration: none;
+ }
+.attribute_link a:hover {
+ color: #606060;
+ border-bottom: 1px dotted #999999;
+ }
+.hide {
+ display: none;
+ }
+.spacer {
+ clear: both;
+ }
+.spacer hr {
+ display: none;
+ }
+.center {
+ text-align: center;
+ }
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/style_master.css
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/style_master.css (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-console.war/style_master.css 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,64 @@
+BODY {
+ font-family: Verdana, Arial, Helvetica, sans-serif;
+ font-size: 14px;
+ background-color : White;
+}
+
+H1{
+ font-family: Verdana, Arial, Helvetica, sans-serif;
+ font-size: 25px;
+ font-weight: bold;
+ color: #000099}
+H2 {
+ font-family: Verdana, Arial, Helvetica, sans-serif;
+ font-size: 20px;
+ font-weight: bold;
+ color: #000000
+}
+H3 {
+ font-family: Verdana, Arial, Helvetica, sans-serif;
+ font-size: 17px;
+ font-weight: bold;
+ color: #000000
+}
+TH {
+ background-color : #000099;
+ color: #DEB887;
+ font-weight: bold;
+}.bg_table {
+ background-color : #DEB887;
+}
+}.bg_cell{
+ background-color : #ffffff;
+}
+A:ACTIVE {
+ font-family: Arial, Helvetica, sans-serif;
+ font-size: 14px;
+ color:Red;
+ background-color: #DEB887;
+ text-decoration : underline;
+ font-weight:bold;
+}
+ A:HOVER {
+ font-family:Arial, Helvetica, sans-serif;
+ font-size: 14px;
+ color:Red;
+ text-decoration : underline;
+ font-weight:bold;
+}
+ A:LINK {
+ font-family: Arial, Helvetica, sans-serif;
+ font-size: 14px;
+ color:#000099;
+ text-decoration : underline;
+ font-weight:bold;
+}
+ A:VISITED {
+ font-family: Arial, Helvetica, sans-serif;
+ font-size: 14px;
+ color:Purple;
+ text-decoration : underline;
+ font-weight:bold;
+}
+
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-invoker-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-invoker-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jmx-invoker-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,131 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: jboss-service.xml 59448 2007-01-09 19:05:54Z dimitris at jboss.org $ -->
+<server>
+
+ <!-- The JRMP invoker proxy configuration for the InvokerAdaptorService -->
+ <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
+ name="jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory">
+ <!-- Use the standard JRMPInvoker from conf/jboss-service.xxml -->
+ <depends optional-attribute-name="InvokerName">jboss:service=invoker,type=jrmp</depends>
+ <!-- The target MBean is the InvokerAdaptorService configured below -->
+ <depends optional-attribute-name="TargetName">jboss.jmx:type=adaptor,name=Invoker</depends>
+ <!-- Where to bind the RMIAdaptor proxy -->
+ <attribute name="JndiName">jmx/invoker/RMIAdaptor</attribute>
+ <!-- The RMI compabitle MBeanServer interface -->
+ <attribute name="ExportedInterfaces">org.jboss.jmx.adaptor.rmi.RMIAdaptor,
+ org.jboss.jmx.adaptor.rmi.RMIAdaptorExt
+ </attribute>
+ <attribute name="ClientInterceptors">
+ <interceptors>
+ <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
+ <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
+ <interceptor>org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor</interceptor>
+ <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
+ </interceptors>
+ </attribute>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+
+ <!--
+ Choose the remote proxy to expose mbean proxies over
+ -->
+ <mbean code="org.jboss.jmx.connector.invoker.MBeanProxyRemote"
+ name="jboss.jmx:type=adaptor,name=MBeanProxyRemote,protocol=jrmp">
+ <depends optional-attribute-name="MBeanServerConnection">jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory</depends>
+ </mbean>
+
+ <!-- Create a mapping from the legacy jmx-rmi-adaptor.sar binding to the
+ jmx-invoker-adaptor-server.sar JndiName specified above for backwards
+ portability.
+ -->
+ <mbean code="org.jboss.naming.NamingAlias" name="jboss.jmx:alias=jmx/rmi/RMIAdaptor">
+ <attribute name="FromName">jmx/rmi/RMIAdaptor</attribute>
+ <attribute name="ToName">jmx/invoker/RMIAdaptor</attribute>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+
+ <!-- This is the service that handles the RMIAdaptor invocations by routing
+ them to the MBeanServer the service is deployed under. -->
+ <mbean code="org.jboss.jmx.connector.invoker.InvokerAdaptorService"
+ name="jboss.jmx:type=adaptor,name=Invoker"
+ xmbean-dd="">
+ <xmbean>
+ <description>The JMX Detached Invoker Service</description>
+ <class>org.jboss.jmx.connector.invoker.InvokerAdaptorService</class>
+
+ <!-- Attributes -->
+ <attribute access="read-only" getMethod="getName">
+ <description>The class name of the MBean</description>
+ <name>Name</name>
+ <type>java.lang.String</type>
+ </attribute>
+ <attribute access="read-only" getMethod="getState">
+ <description>The status of the MBean</description>
+ <name>State</name>
+ <type>int</type>
+ </attribute>
+ <attribute access="read-only" getMethod="getStateString">
+ <description>The status of the MBean in text form</description>
+ <name>StateString</name>
+ <type>java.lang.String</type>
+ </attribute>
+ <attribute access="read-write" getMethod="getExportedInterfaces" setMethod="setExportedInterfaces">
+ <description>The interfaces the invoker proxy supports</description>
+ <name>ExportedInterfaces</name>
+ <type>[Ljava.lang.Class;</type>
+ </attribute>
+ <attribute access="read-only" getMethod="getMethodMap">
+ <description>Map(Long hash, Method) of the proxy interface methods</description>
+ <name>MethodMap</name>
+ <type>java.util.Map</type>
+ </attribute>
+ <!-- Operations -->
+ <operation>
+ <description>The start lifecycle operation</description>
+ <name>start</name>
+ </operation>
+ <operation>
+ <description>The stop lifecycle operation</description>
+ <name>stop</name>
+ </operation>
+ <operation>
+ <description>The detyped lifecycle operation (for internal use only)</description>
+ <name>jbossInternalLifecycle</name>
+ <parameter>
+ <description>The lifecycle operation</description>
+ <name>method</name>
+ <type>java.lang.String</type>
+ </parameter>
+ <return-type>void</return-type>
+ </operation>
+
+ <operation>
+ <description>The detached invoker entry point</description>
+ <name>invoke</name>
+ <parameter>
+ <description>The method invocation context</description>
+ <name>invocation</name>
+ <type>org.jboss.invocation.Invocation</type>
+ </parameter>
+ <return-type>java.lang.Object</return-type>
+ <descriptors>
+ <interceptors>
+ <!-- Uncomment to require authenticated users
+ <interceptor code="org.jboss.jmx.connector.invoker.AuthenticationInterceptor"
+ securityDomain="java:/jaas/jmx-console"/>
+ -->
+ <!-- Interceptor that deals with non-serializable results -->
+ <interceptor code="org.jboss.jmx.connector.invoker.SerializableInterceptor"
+ policyClass="StripModelMBeanInfoPolicy"/>
+ </interceptors>
+ </descriptors>
+ </operation>
+ </xmbean>
+
+ <attribute name="ExportedInterfaces">org.jboss.jmx.adaptor.rmi.RMIAdaptor,
+ org.jboss.jmx.adaptor.rmi.RMIAdaptorExt
+ </attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jsr88-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jsr88-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/jsr88-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,19 @@
+<!-- $Id: jsr88-service.xml 60132 2007-01-31 12:43:12Z thomas.diesler at jboss.com $
+The JSR-88 DeploymentManager support services
+-->
+<server>
+ <mbean code="org.jboss.deployment.services.DeploymentManagerService"
+ name="jboss.management.local:type=JSR88DeploymentManager,name=DefaultManager">
+ <attribute name="EARDeployer">jboss.j2ee:service=EARDeployer</attribute>
+ <attribute name="EJBDeployer">jboss.ejb:service=EJBDeployer</attribute>
+ <attribute name="RARDeployer">jboss.jca:service=RARDeployer</attribute>
+ <attribute name="WARDeployer">jboss.web:service=WebServer</attribute>
+ <attribute name="CARDeployer">jboss.j2ee:service=ClientDeployer</attribute>
+ <attribute name="UploadDir">${jboss.server.temp.dir}/jsr88</attribute>
+ <depends optional-attribute-name="MainDeployer">jboss.system:service=MainDeployer</depends>
+ <!-- If false, the an existing deployment may exist in the upload dir -->
+ <attribute name="FailOnCollision">false</attribute>
+ <!-- If false, the deployment is retained in the upload dir -->
+ <attribute name="DeleteOnUndeploy">false</attribute>
+ </mbean>
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/mail-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/mail-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/mail-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: mail-service.xml 62349 2007-04-15 16:48:15Z dimitris at jboss.org $ -->
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Mail Connection Factory -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.mail.MailService"
+ name="jboss:service=Mail">
+ <attribute name="JNDIName">java:/Mail</attribute>
+ <attribute name="User">nobody</attribute>
+ <attribute name="Password">password</attribute>
+ <attribute name="Configuration">
+ <!-- A test configuration -->
+ <configuration>
+ <!-- Change to your mail server prototocol -->
+ <property name="mail.store.protocol" value="pop3"/>
+ <property name="mail.transport.protocol" value="smtp"/>
+
+ <!-- Change to the user who will receive mail -->
+ <property name="mail.user" value="nobody"/>
+
+ <!-- Change to the mail server -->
+ <property name="mail.pop3.host" value="pop3.nosuchhost.nosuchdomain.com"/>
+
+ <!-- Change to the SMTP gateway server -->
+ <property name="mail.smtp.host" value="smtp.nosuchhost.nosuchdomain.com"/>
+
+ <!-- The mail server port -->
+ <property name="mail.smtp.port" value="25"/>
+
+ <!-- Change to the address mail will be from -->
+ <property name="mail.from" value="nobody at nosuchhost.nosuchdomain.com"/>
+
+ <!-- Enable debugging output from the javamail classes -->
+ <property name="mail.debug" value="false"/>
+ </configuration>
+ </attribute>
+ <depends>jboss:service=Naming</depends>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/META-INF/MANIFEST.MF
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/META-INF/MANIFEST.MF (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/META-INF/MANIFEST.MF 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,4 @@
+Manifest-Version: 1.0
+Ant-Version: Apache Ant 1.6.2
+Created-By: 1.5.0_11-b03 (Sun Microsystems Inc.)
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/META-INF/jboss-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/META-INF/jboss-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/META-INF/jboss-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- Console Service Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<server>
+ <!-- Isolate the console mgr classes from other deployments -->
+ <loader-repository>
+ jboss.console:sar=console-mgr.sar
+ <loader-repository-config>
+ java2ParentDelegation=true
+ </loader-repository-config>
+ </loader-repository>
+
+ <mbean code="org.jboss.console.manager.PluginManager"
+ name="jboss.admin:service=PluginManager">
+ <!-- The RMIAdaptor provider service -->
+ <depends>jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory</depends>
+ <attribute name="MainLogoUrl">/web-console/images/jboss.gif</attribute>
+ <attribute name="MainLinkUrl">/web-console/ServerInfo.jsp</attribute>
+ <attribute name="EnableShutdown">true</attribute>
+ <attribute name="JndiName">console/PluginManager</attribute>
+ </mbean>
+
+ <mbean code="org.jboss.console.manager.DeploymentFileRepository"
+ name="jboss.admin:service=DeploymentFileRepository">
+ <attribute name="BaseDir">./deploy/management</attribute>
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/console-mgr-classes.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/console-mgr-classes.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/jcommon.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/jcommon.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/jfreechart.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/jfreechart.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPBinding.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPBinding.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPBinding.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,71 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,java.util.*,
+ org.jboss.aop.advice.AdviceBinding" %>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String name = request.getParameter("binding");
+ AdviceBinding binding = (AdviceBinding)AspectManager.instance().getBindings().get(name);
+%>
+<hr class="hide"/>
+ <center>
+ <h4 style="text-align: center"><%=name%></h4>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3>Advice Binding</h3>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="2">
+ <p align="left"><font size="1"><b>Pointcut Expression: </b><%=binding.getPointcut().getExpr()%></font></p>
+ <% if (binding.getCFlowString() != null) {
+ %>
+ <p align="left"><font size="1"><b>CFlow Expression: </b><%=binding.getCFlowString()%></font></p>
+ <% } %>
+ </td>
+ </tr>
+
+ </table>
+ <p> </p>
+ <p> </p>
+ <p align="center"> <a href="<%=myUrl%>">Refresh</a></p>
+
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPClassMetaData.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPClassMetaData.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPClassMetaData.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,38 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,java.util.*"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String classname = request.getParameter("classname");
+ String group = request.getParameter("group");
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ HashMap groupAttrs = advisor.getClassMetaData().tag(group);
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3>Metadata for class <%= classname %></h3>
+ <p> </p>
+<%@ include file="AOPMetaData.jsp" %>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorChain.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorChain.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorChain.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,84 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,org.jboss.aop.advice.*,java.util.*,java.lang.reflect.Field,
+ java.lang.reflect.Constructor,
+ org.jboss.console.plugins.AOPLister"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String classname = request.getParameter("classname");
+ int idx = Integer.parseInt(request.getParameter("constructor"));
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ Constructor constructor = advisor.getConstructors()[idx];
+ Interceptor[] interceptors = advisor.getConstructorInterceptors()[idx];
+
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3><%=classname%></h3>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="2">
+ <h4 style="text-align: center"><font size="3">Constructor Chain for <%=AOPLister.shortenConstructor(classname, constructor)%></font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <h4>Type</h4>
+ </td>
+ <td>
+ <h4>Description</h4>
+ </td>
+ </tr>
+<%
+ if (interceptors != null)
+ {
+ String chain = AOPLister.outputChain(interceptors);
+%>
+<%=chain%>
+<% } %>
+ </table>
+ <p> </p>
+ <p align="center"> <a href="<%=myUrl%>">Refresh</a></p>
+
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorConstructorCallerChain.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorConstructorCallerChain.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorConstructorCallerChain.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,91 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,org.jboss.aop.advice.*,java.util.*,java.lang.reflect.Field,
+ java.lang.reflect.Constructor,
+ org.jboss.console.plugins.AOPLister,
+ gnu.trove.TLongObjectHashMap"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String classname = request.getParameter("classname");
+ int idx = Integer.parseInt(request.getParameter("index"));
+ String calledClassname = request.getParameter("calledclassname");
+ long hash = Long.parseLong(request.getParameter("hash"));
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ Constructor constructor = advisor.getConstructors()[idx];
+ HashMap called = advisor.getConCalledByConInterceptors()[idx];
+ TLongObjectHashMap map = (TLongObjectHashMap)called.get(calledClassname);
+ CallerConstructorInfo info = (CallerConstructorInfo)map.get(hash);
+ Interceptor[] interceptors = info.interceptors;
+
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3><%=classname%></h3>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="2">
+ <h4 style="text-align: center"><font size="3">Constructor Caller: <%=AOPLister.shortenConstructor(classname, constructor)%></font></h4>
+ <h4 style="text-align: center"><font size="3">Called Constructor: <%=info.constructor.toString()%></font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <h4>Type</h4>
+ </td>
+ <td>
+ <h4>Description</h4>
+ </td>
+ </tr>
+<%
+ if (interceptors != null)
+ {
+ String chain = AOPLister.outputChain(interceptors);
+%>
+<%=chain%>
+<% } %>
+ </table>
+ <p> </p>
+ <p align="center"> <a href="<%=myUrl%>">Refresh</a></p>
+
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorMetaData.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorMetaData.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorMetaData.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,53 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,java.util.*,java.lang.reflect.*,
+ org.jboss.aop.metadata.ConstructorMetaData"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+
+ String classname = request.getParameter("classname");
+ String group = request.getParameter("group");
+ String con = request.getParameter("constructor");
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ HashMap groupAttrs = new HashMap();
+ ConstructorMetaData metaData = advisor.getConstructorMetaData();
+ Iterator conit = metaData.getConstructors();
+ while (conit.hasNext())
+ {
+ String constructor = (String)conit.next();
+ if (constructor.equals(con))
+ {
+ groupAttrs = metaData.getConstructorMetaData(constructor).tag(group);
+ break;
+ }
+ }
+
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3>Metadata for constructor <%=con%></h3>
+ <p> </p>
+<%@ include file="AOPMetaData.jsp" %>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorMethodCallerChain.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorMethodCallerChain.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPConstructorMethodCallerChain.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,91 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,org.jboss.aop.advice.*,java.util.*,java.lang.reflect.Field,
+ java.lang.reflect.Constructor,
+ org.jboss.console.plugins.AOPLister,
+ gnu.trove.TLongObjectHashMap"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String classname = request.getParameter("classname");
+ int idx = Integer.parseInt(request.getParameter("index"));
+ String calledClassname = request.getParameter("calledclassname");
+ long hash = Long.parseLong(request.getParameter("hash"));
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ Constructor constructor = advisor.getConstructors()[idx];
+ HashMap called = advisor.getMethodCalledByConInterceptors()[idx];
+ TLongObjectHashMap map = (TLongObjectHashMap)called.get(calledClassname);
+ CallerMethodInfo info = (CallerMethodInfo)map.get(hash);
+ Interceptor[] interceptors = info.interceptors;
+
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3><%=classname%></h3>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="2">
+ <h4 style="text-align: center"><font size="3">Constructor Caller: <%=AOPLister.shortenConstructor(classname, constructor)%></font></h4>
+ <h4 style="text-align: center"><font size="3">Called Method: <%=info.method.toString()%></font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <h4>Type</h4>
+ </td>
+ <td>
+ <h4>Description</h4>
+ </td>
+ </tr>
+<%
+ if (interceptors != null)
+ {
+ String chain = AOPLister.outputChain(interceptors);
+%>
+<%=chain%>
+<% } %>
+ </table>
+ <p> </p>
+ <p align="center"> <a href="<%=myUrl%>">Refresh</a></p>
+
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPDefaultMetaData.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPDefaultMetaData.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPDefaultMetaData.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,38 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,java.util.*"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String classname = request.getParameter("classname");
+ String group = request.getParameter("group");
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ HashMap groupAttrs = advisor.getDefaultMetaData().tag(group);
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3><%=classname%> Default MetaData </h3>
+ <p> </p>
+<%@ include file="AOPMetaData.jsp" %>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPFieldChain.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPFieldChain.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPFieldChain.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,84 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,org.jboss.aop.advice.*,java.util.*,java.lang.reflect.Field,
+ org.jboss.console.plugins.AOPLister"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String classname = request.getParameter("classname");
+ int idx = Integer.parseInt(request.getParameter("field"));
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ Field field = advisor.getAdvisedFields()[idx];
+ boolean read = request.getParameter("mode").equals("read");
+ Interceptor[] interceptors = read ? advisor.getFieldReadInterceptors()[idx] : advisor.getFieldWriteInterceptors()[idx];
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3><%=classname%></h3>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="2">
+ <h4 style="text-align: center"><font size="3">Field <%= (read) ? "Read" : "Write" %> Chain for <%=AOPLister.shortenField(classname, field)%></font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <h4>Type</h4>
+ </td>
+ <td>
+ <h4>Description</h4>
+ </td>
+ </tr>
+<%
+ if (interceptors != null)
+ {
+ String chain = AOPLister.outputChain(interceptors);
+%>
+<%=chain%>
+<% } %>
+
+ </table>
+ <p> </p>
+ <p align="center"> <a href="<%=myUrl%>">Refresh</a></p>
+
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPFieldMetaData.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPFieldMetaData.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPFieldMetaData.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,39 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,java.util.*"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String classname = request.getParameter("classname");
+ String group = request.getParameter("group");
+ String field = request.getParameter("field");
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ HashMap groupAttrs = advisor.getFieldMetaData().getFieldMetaData(field).tag(group);
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3>Metadata for field <%=field%></h3>
+ <p> </p>
+<%@ include file="AOPMetaData.jsp" %>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPIntroductionPointcut.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPIntroductionPointcut.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPIntroductionPointcut.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,105 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,java.util.*,
+ org.jboss.aop.introduction.InterfaceIntroduction"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String name = request.getParameter("pointcut");
+ InterfaceIntroduction introduction = AspectManager.instance().getInterfaceIntroduction(name);
+%>
+<hr class="hide"/>
+ <center> <h4 style="text-align: center"><%=name%></h4>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3>Introduction Pointcut</h3>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="2">
+ <p align="left"><font size="1"><b>Class Expression: </b><%=introduction.getClassExpr()%></font></p>
+ </td>
+ </tr>
+<%
+ Iterator mixins = introduction.getMixins().iterator();
+ while (mixins.hasNext()) {
+ InterfaceIntroduction.Mixin mixin = (InterfaceIntroduction.Mixin)mixins.next();
+ String[] interfaces = mixin.getInterfaces();
+ String initializer = (mixin.getConstruction() == null) ? ("new " + mixin.getClassName() + "()") : mixin.getConstruction();
+%>
+ <tr>
+ <td>
+ <p align="left"><h4>Mixin Class</h4></p>
+ <p align="left"><font size="1"><%=mixin.getClassName()%></font></p>
+ <p align="left"><h4>Mixin Initializer</h4></p>
+ <p align="left"><font size="1"><%=initializer%></font></p>
+ </td>
+ <td>
+ <p align="left"><h4>Interfaces</h4></p>
+<%
+ for (int j = 0; j < interfaces.length; j++) {
+%>
+ <p align="left"><font size="1"><%=interfaces[j]%></font></p>
+<% } %>
+ </td>
+ </tr>
+<% } %>
+<%
+ String[] interfaces = introduction.getInterfaces();
+ if (interfaces != null && interfaces.length > 0) {
+%>
+ <tr>
+ <td colspan="2">
+ <p align="left"><h4>Other Interfaces</h4></p>
+<%
+ for (int j = 0; j < interfaces.length; j++) {
+%>
+ <p align="left"><font size="1"><%=interfaces[j]%></font></p>
+<% } %>
+ </td>
+ </tr>
+<% }%>
+
+ </table>
+ <p> </p>
+ <p> </p>
+ <p align="center"> <a href="<%=myUrl%>">Refresh</a></p>
+
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMetaData.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMetaData.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMetaData.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,79 @@
+<%@ page import="java.util.Iterator,
+ java.util.Map,
+ org.jboss.aop.metadata.SimpleMetaData,
+ org.jboss.aop.metadata.MetaDataResolver" %>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="4">
+ <h4 style="text-align: center"><font size="3"><%=group%></font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <h4>Attribute Name</h4>
+ </td>
+ <td>
+ <h4>Type</h4>
+ </td>
+ <td>
+ <h4>Value (as String)</h4>
+ </td>
+ <td>
+ <h4>Serialization</h4>
+ </td>
+ </tr>
+<%
+ boolean hasValues = false;
+
+ Iterator it = groupAttrs.entrySet().iterator();
+ while (it.hasNext())
+ {
+ Map.Entry entry = (Map.Entry)it.next();
+ String attr = (String)entry.getKey();
+ if (!attr.equals(MetaDataResolver.EMPTY_TAG))
+ {
+ hasValues = true;
+ SimpleMetaData.MetaDataValue value = (SimpleMetaData.MetaDataValue)entry.getValue();
+%>
+ <tr>
+ <td><font size="1"><%=attr%></font>
+ <td><font size="1"><%=value.value.getClass().getName()%></font>
+ <td><font size="1"><%=value.value.toString()%></font>
+ <td><font size="1"><%=value.type%></font>
+ </td>
+ </tr>
+<% }
+ }
+
+ if (!hasValues)
+ {
+%>
+ <tr>
+ <td colspan="4">empty</td>
+ </tr>
+<% }
+
+%>
+
+ </table>
+ <p> </p>
+ <p align="center"> <a href="<%=myUrl%>">Refresh</a></p>
+
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodChain.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodChain.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodChain.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,86 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,org.jboss.aop.advice.*,java.util.*,gnu.trove.TLongObjectHashMap,
+ java.lang.reflect.Method,
+ org.jboss.console.plugins.AOPLister"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String classname = request.getParameter("classname");
+ long hash = Long.parseLong(request.getParameter("method"));
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ TLongObjectHashMap methodChains = advisor.getMethodInterceptors();
+ MethodInfo info = (MethodInfo)methodChains.get(hash);
+ Interceptor[] interceptors = info.interceptors;
+ Method method = (Method)advisor.getAdvisedMethods().get(hash);
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3><%=classname%></h3>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="2">
+ <h4 style="text-align: center"><font size="3">Method Chain for <%=AOPLister.shortenMethod(classname, method)%></font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <h4>Type</h4>
+ </td>
+ <td>
+ <h4>Description</h4>
+ </td>
+ </tr>
+<%
+ if (interceptors != null)
+ {
+ String chain = AOPLister.outputChain(interceptors);
+%>
+<%=chain%>
+<% } %>
+
+ </table>
+ <p> </p>
+ <p align="center"> <a href="<%=myUrl%>">Refresh</a></p>
+
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodConstructorCallerChain.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodConstructorCallerChain.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodConstructorCallerChain.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,92 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,org.jboss.aop.advice.*,java.util.*,java.lang.reflect.Field,
+ java.lang.reflect.Constructor,
+ org.jboss.console.plugins.AOPLister,
+ gnu.trove.TLongObjectHashMap,
+ java.lang.reflect.Method"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String classname = request.getParameter("classname");
+ String calledClassname = request.getParameter("calledclassname");
+ long hash = Long.parseLong(request.getParameter("hash"));
+ long callingHash = Long.parseLong(request.getParameter("callinghash"));
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ Method method = (Method)advisor.getAdvisedMethods().get(callingHash);
+ HashMap called = (HashMap)advisor.getConCalledByMethodInterceptors().get(callingHash);
+ TLongObjectHashMap map = (TLongObjectHashMap)called.get(calledClassname);
+ CallerConstructorInfo info = (CallerConstructorInfo)map.get(hash);
+ Interceptor[] interceptors = info.interceptors;
+
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3><%=classname%></h3>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="2">
+ <h4 style="text-align: center"><font size="3">Method Caller: <%=AOPLister.shortenMethod(classname, method)%></font></h4>
+ <h4 style="text-align: center"><font size="3">Called Constructor: <%=info.constructor.toString()%></font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <h4>Type</h4>
+ </td>
+ <td>
+ <h4>Description</h4>
+ </td>
+ </tr>
+<%
+ if (interceptors != null)
+ {
+ String chain = AOPLister.outputChain(interceptors);
+%>
+<%=chain%>
+<% } %>
+ </table>
+ <p> </p>
+ <p align="center"> <a href="<%=myUrl%>">Refresh</a></p>
+
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodMetaData.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodMetaData.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodMetaData.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,39 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,java.util.*"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String classname = request.getParameter("classname");
+ String group = request.getParameter("group");
+ String method = request.getParameter("method");
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ HashMap groupAttrs = advisor.getMethodMetaData().getMethodMetaData(method).tag(group);
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3>Metadata for method <%=method%></h3>
+ <p> </p>
+<%@ include file="AOPMetaData.jsp" %>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodMethodCallerChain.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodMethodCallerChain.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/AOPMethodMethodCallerChain.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,92 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%@ page import="org.jboss.aop.*,org.jboss.aop.advice.*,java.util.*,java.lang.reflect.Field,
+ java.lang.reflect.Constructor,
+ org.jboss.console.plugins.AOPLister,
+ gnu.trove.TLongObjectHashMap,
+ java.lang.reflect.Method"%>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI() + "?" + request.getQueryString());
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - AOP Pointcuts</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link
+</head>
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<%
+ String classname = request.getParameter("classname");
+ String calledClassname = request.getParameter("calledclassname");
+ long hash = Long.parseLong(request.getParameter("hash"));
+ long callingHash = Long.parseLong(request.getParameter("callinghash"));
+ ClassAdvisor advisor = (ClassAdvisor)AspectManager.instance().getAdvisor(classname);
+ Method method = (Method)advisor.getAdvisedMethods().get(callingHash);
+ HashMap called = (HashMap)advisor.getMethodCalledByMethodInterceptors().get(callingHash);
+ TLongObjectHashMap map = (TLongObjectHashMap)called.get(calledClassname);
+ CallerMethodInfo info = (CallerMethodInfo)map.get(hash);
+ Interceptor[] interceptors = info.interceptors;
+
+%>
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%">
+ <h3><%=classname%></h3>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="2">
+ <h4 style="text-align: center"><font size="3">Method Caller: <%=AOPLister.shortenMethod(classname, method)%></font></h4>
+ <h4 style="text-align: center"><font size="3">Called Method: <%=info.method.toString()%></font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <h4>Type</h4>
+ </td>
+ <td>
+ <h4>Description</h4>
+ </td>
+ </tr>
+<%
+ if (interceptors != null)
+ {
+ String chain = AOPLister.outputChain(interceptors);
+%>
+<%=chain%>
+<% } %>
+ </table>
+ <p> </p>
+ <p align="center"> <a href="<%=myUrl%>">Refresh</a></p>
+
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EJB.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EJB.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EJB.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,42 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="ejb" intf="org.jboss.management.j2ee.StatelessSessionBeanMBean" />
+
+<%
+ String ejbName = new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("name");
+ String containerUrl = "jboss.j2ee:service=EJB,jndiName=" + ejbName;
+ containerUrl = java.net.URLEncoder.encode(containerUrl);
+ containerUrl = "../jmx-console/HtmlAdaptor?action=inspectMBean&name=" + containerUrl;
+%>
+<html>
+<META HTTP-EQUIV="expires" CONTENT="0"/>
+<head>
+<title>EJB: <%=ejbName%></title>
+</head>
+
+ <body>
+
+ <h1><center>EJB '<%=ejbName%>'</center></h1>
+
+ <p/>
+ <p/>
+
+ <table border="1">
+ <tr>
+ <td><b>Management Object Name:</b></td>
+ </tr>
+ <tr>
+ <td><%=ejb.getobjectName()%> </td>
+ </tr>
+ <tr>
+ <td><b>Provides Statistics:</b></td>
+ </tr>
+ <tr>
+ <td><%=ejb.isstatisticsProvider()%> </td>
+ </tr>
+ </table>
+
+ <a href="<%=containerUrl%>">Visit associated container MBean...</a>
+
+ </body>
+
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EJBModule.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EJBModule.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EJBModule.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,44 @@
+<%@ page import="javax.management.ObjectName"%>
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="module" intf="org.jboss.management.j2ee.J2EEModuleMBean" />
+
+<%
+ String moduleName = new ObjectName(module.getobjectName()).getKeyProperty ("name");
+%>
+<html>
+<META HTTP-EQUIV="expires" CONTENT="0"/>
+<head>
+<title>EJB-Module: <%=moduleName%></title>
+</head>
+
+ <body>
+
+ <h1><center>EJB-Module '<%=moduleName%>'</center></h1>
+
+ <p/>
+ <p/>
+
+ <table border="1">
+ <tr>
+ <td><b>Management Object Name:</b></td>
+ </tr>
+ <tr>
+ <td><%=module.getobjectName()%></td>
+ </tr>
+ <tr>
+ <td><b>Provides Statistics:</b></td>
+ </tr>
+ <tr>
+ <td><%=module.isstatisticsProvider()%></td>
+ </tr>
+ <tr>
+ <td><b>Deployment Descriptor:</b></td>
+ </tr>
+ <tr>
+ <td><pre><%=org.jboss.console.plugins.helpers.servlet.ServletHelper.filter(module.getdeploymentDescriptor())%></pre></td>
+ </tr>
+ </table>
+
+ </body>
+
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EntityEjb.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EntityEjb.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/EntityEjb.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,231 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="ejb" intf="org.jboss.management.j2ee.EntityBeanMBean" />
+<jb:mbean id="container" mbean='<%=request.getParameter("ContainerObjectName")%>' intf="org.jboss.ejb.ContainerMBean" />
+<%
+ String ejbName = new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("name");
+ String ejbModule = new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("EJBModule");
+ String containerUrl = java.net.URLEncoder.encode(request.getParameter("ContainerObjectName"));
+ containerUrl = "../jmx-console/HtmlAdaptor?action=inspectMBean&name=" + containerUrl;
+
+ org.jboss.invocation.InvocationStatistics invokeStats= container.getInvokeStats ();
+
+ String doReset = request.getParameter("doReset");
+ if (doReset != null && doReset.equals("true"))
+ {
+ ejb.resetStats ();
+ }
+ String doResetInvoc= request.getParameter("doResetInvoc");
+ if (doResetInvoc!= null && doResetInvoc.equals("true"))
+ {
+ invokeStats.resetStats ();
+ }
+
+ String parameters = "&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName"));
+ parameters = parameters + "&ContainerObjectName=" + java.net.URLEncoder.encode(request.getParameter("ContainerObjectName"));
+
+ String resetUrl = response.encodeURL(request.getRequestURI()) + "?doReset=true" + parameters;
+ String resetInvocUrl = response.encodeURL(request.getRequestURI()) + "?doResetInvoc=true" + parameters;
+ String myUrl = response.encodeURL(request.getRequestURI()) + "?" + parameters;
+ org.jboss.metadata.BeanMetaData beanMetaData = container.getBeanMetaData();
+
+%>
+<%!
+public String addStatRow (javax.management.j2ee.statistics.Statistic stat)
+{
+ String start = new java.util.Date(stat.getStartTime ()).toString ();
+ String lastSample = new java.util.Date(stat.getLastSampleTime ()).toString ();
+
+ String result = "<tr><td width=\"25%\"><font size=\"1\">" + stat.getName() + " (unit: " + stat.getUnit () + ")</font></td>" +
+ "<td width=\"25%\"><table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" style=\"border-collapse: collapse\" bordercolor=\"#111111\" width=\"100%\"><tr>";
+
+ if (stat instanceof javax.management.j2ee.statistics.CountStatistic)
+ {
+ result+= "<td width=\"33%\" align=\"center\"><font size=\"1\">" + ((javax.management.j2ee.statistics.CountStatistic)stat).getCount() + "</font></td><td width=\"33%\"></td><td width=\"34%\"></td>";
+ }
+ else if (stat instanceof javax.management.j2ee.statistics.RangeStatistic)
+ {
+ javax.management.j2ee.statistics.RangeStatistic rStat = (javax.management.j2ee.statistics.RangeStatistic)stat;
+
+ result+= "<td width=\"33%\" align=\"center\"><font size=\"1\">" + rStat.getCurrent () + "</font></td><td width=\"33%\" align=\"center\"><font size=\"1\">" + rStat.getLowWaterMark () + "</font></td>" +
+ "<td width=\"34%\" align=\"center\"><font size=\"1\">" + rStat.getHighWaterMark() + "</font></td>";
+ }
+
+ result+= "</tr></table></td><td width=\"25%\"><font size=\"1\">" + start + "</font></td><td width=\"25%\"><font size=\"1\">" + lastSample + "</font> </td></tr>";
+
+ return result;
+
+}
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Entity Bean</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 831; height: 247">
+ <h3>Entity Bean</h3>
+ <h4>Name</h4>
+ <p><%=beanMetaData.getEjbName()%> (JNDI: <%=ejbName%>)</p>
+ <h4>EJB Module</h4>
+ <p><%=ejbModule %></p>
+ <h4>Bean Statistics:</h4>
+ <p> </p>
+<%
+if (ejb.isstatisticsProvider())
+{
+%>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Name</h4>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Value</h4>
+ <table border="0" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="100%" id="AutoNumber3">
+ <tr>
+ <td width="33%">
+ <h4 style="text-align: center">Current</h4>
+ </td>
+ <td width="33%">
+ <h4 style="text-align: center">Low</h4>
+ </td>
+ <td width="34%">
+ <h4 style="text-align: center">High</h4>
+ </td>
+ </tr>
+ </table>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Start Time</h4>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Last Sample Time</h4>
+ </td>
+ </tr>
+ <%
+ javax.management.j2ee.statistics.EntityBeanStats stats = (javax.management.j2ee.statistics.EntityBeanStats)ejb.getstats ();
+%>
+ <%=addStatRow (stats.getCreateCount ()) %>
+ <%=addStatRow (stats.getRemoveCount ()) %>
+ <%=addStatRow (stats.getReadyCount ()) %>
+ <%=addStatRow (stats.getPooledCount ()) %>
+
+ </table>
+ <p align="center"><a href="<%=resetUrl%>">Reset Stats</a> / <a href="<%=myUrl%>">Refresh Stats</a></p>
+<%
+}
+else
+{
+%>
+ <p>none.</p>
+<%
+}
+%>
+ <p> </p>
+ <p> </p>
+ <h4>Invocation Statistics:</h4>
+ <p> </p>
+<%
+ java.util.Iterator iterInvoc = invokeStats.getStats().entrySet().iterator();
+ if (iterInvoc.hasNext())
+ {
+
+%>
+
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td align="center">
+ <h4 style="text-align: center">Method name</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Min (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Max (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Average (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Total (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center"># Invocations</h4>
+ </td>
+ </tr>
+ <%
+ while (iterInvoc.hasNext())
+ {
+ java.util.Map.Entry entry = (java.util.Map.Entry) iterInvoc.next();
+ org.jboss.invocation.InvocationStatistics.TimeStatistic stat = (org.jboss.invocation.InvocationStatistics.TimeStatistic) entry.getValue();
+ %>
+
+ <tr>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=((java.lang.reflect.Method)entry.getKey()).getName()%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.minTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.maxTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=(float)stat.totalTime/(float)stat.count%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.totalTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.count%></h4></font>
+ </td>
+ </tr>
+ <%
+ }
+ %>
+ </table>
+ <p align="center"><a href="<%=resetInvocUrl%>">Reset Stats</a> / <a href="<%=myUrl%>">Refresh Stats</a></p>
+<%
+ }
+ else
+ {
+%>
+ <p>none.</p>
+<%
+ }
+%>
+
+ <p> </p>
+ <p>Actual concurrent invocations: <%=invokeStats.concurrentCalls%> (max: <%=invokeStats.maxConcurrentCalls%>)</p>
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ <p><a href="<%=containerUrl%>">View associated container MBean</a></p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/J2EEApp.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/J2EEApp.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/J2EEApp.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,44 @@
+<%@ page import="javax.management.ObjectName"%>
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="app" intf="org.jboss.management.j2ee.J2EEApplicationMBean" />
+
+<%
+ String appName = new ObjectName(app.getobjectName()).getKeyProperty ("name");
+%>
+<html>
+<META HTTP-EQUIV="expires" CONTENT="0"/>
+<head>
+<title>J2EE Application: <%=appName%></title>
+</head>
+
+ <body>
+
+ <h1><center>J2EE Application '<%=appName%>'</center></h1>
+
+ <p/>
+ <p/>
+
+ <table border="1">
+ <tr>
+ <td><b>Management Object Name:</b></td>
+ </tr>
+ <tr>
+ <td><%=app.getobjectName()%></td>
+ </tr>
+ <tr>
+ <td><b>Provides Statistics:</b></td>
+ </tr>
+ <tr>
+ <td><%=app.isstatisticsProvider()%></td>
+ </tr>
+ <tr>
+ <td><b>Deployment Descriptor:</b></td>
+ </tr>
+ <tr>
+ <td><pre><%=org.jboss.console.plugins.helpers.servlet.ServletHelper.filter(app.getdeploymentDescriptor())%></pre></td>
+ </tr>
+ </table>
+
+ </body>
+
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/JNDIView.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/JNDIView.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/JNDIView.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,38 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="jndiview" intf="org.jboss.naming.JNDIViewMBean" mbean="jboss:service=JNDIView" />
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - JNDI View</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+<link rel="StyleSheet" href="css/dtree.css" type="text/css" />
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <h3>JNDI View</h3>
+ <p> </p>
+
+ <%=org.jboss.console.util.XMLToHTMLTreeBuilder.convertJNDIXML(jndiview.listXML())%>
+
+ <p> </p>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/META-INF/MANIFEST.MF
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/META-INF/MANIFEST.MF (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/META-INF/MANIFEST.MF 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,4 @@
+Manifest-Version: 1.0
+Ant-Version: Apache Ant 1.6.2
+Created-By: 1.5.0_11-b03 (Sun Microsystems Inc.)
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/MdbEjb.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/MdbEjb.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/MdbEjb.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,238 @@
+<%@ page language="java"
+ import="java.util.Map"
+ import="java.util.HashMap"
+ import="java.util.Iterator"
+ import="org.jboss.invocation.InvocationStatistics"
+ import="org.jboss.invocation.InvocationStatistics.*" %>
+
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="ejb" intf="org.jboss.management.j2ee.MessageDrivenBeanMBean" />
+<jb:mbean id="container" mbean='<%=request.getParameter("ContainerObjectName")%>' intf="org.jboss.ejb.ContainerMBean" />
+<%
+ String ejbName = new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("name");
+ String ejbModule = new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("EJBModule");
+ String containerUrl = java.net.URLEncoder.encode(request.getParameter("ContainerObjectName"));
+ containerUrl = "../jmx-console/HtmlAdaptor?action=inspectMBean&name=" + containerUrl;
+
+ org.jboss.invocation.InvocationStatistics invokeStats= container.getInvokeStats ();
+
+ String doReset = request.getParameter("doReset");
+ if (doReset != null && doReset.equals("true"))
+ {
+ ejb.resetStats ();
+ }
+ String doResetInvoc= request.getParameter("doResetInvoc");
+ if (doResetInvoc!= null && doResetInvoc.equals("true"))
+ {
+ invokeStats.resetStats ();
+ }
+
+ String parameters = "&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName"));
+ parameters = parameters + "&ContainerObjectName=" + java.net.URLEncoder.encode(request.getParameter("ContainerObjectName"));
+
+ String resetUrl = response.encodeURL(request.getRequestURI()) + "?doReset=true" + parameters;
+ String resetInvocUrl = response.encodeURL(request.getRequestURI()) + "?doResetInvoc=true" + parameters;
+ String myUrl = response.encodeURL(request.getRequestURI()) + "?" + parameters;
+ org.jboss.metadata.BeanMetaData beanMetaData = container.getBeanMetaData();
+
+%>
+
+ <%!
+public String addStatRow (javax.management.j2ee.statistics.Statistic stat)
+{
+ String start = new java.util.Date(stat.getStartTime ()).toString ();
+ String lastSample = new java.util.Date(stat.getLastSampleTime ()).toString ();
+
+ String result = "<tr><td width=\"25%\"><font size=\"1\">" + stat.getName() + " (unit: " + stat.getUnit () + ")</font></td>" +
+ "<td width=\"25%\"><table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" style=\"border-collapse: collapse\" bordercolor=\"#111111\" width=\"100%\"><tr>";
+
+ if (stat instanceof javax.management.j2ee.statistics.CountStatistic)
+ {
+ result += "<td width=\"33%\" align=\"center\"><font size=\"1\">" + ((javax.management.j2ee.statistics.CountStatistic)stat).getCount() + "</font></td><td width=\"33%\"></td><td width=\"34%\"></td>";
+ }
+ else if (stat instanceof javax.management.j2ee.statistics.RangeStatistic)
+ {
+ javax.management.j2ee.statistics.RangeStatistic rStat = (javax.management.j2ee.statistics.RangeStatistic)stat;
+
+ result += "<td width=\"33%\" align=\"center\"><font size=\"1\">" + rStat.getCurrent () + "</font></td><td width=\"33%\" align=\"center\"><font size=\"1\">" + rStat.getLowWaterMark () + "</font></td>" +
+ "<td width=\"34%\" align=\"center\"><font size=\"1\">" + rStat.getHighWaterMark() + "</font></td>";
+ }
+
+ result += "</tr></table></td><td width=\"25%\"><font size=\"1\">" + start + "</font></td><td width=\"25%\"><font size=\"1\">" + lastSample + "</font> </td></tr>";
+
+ return result;
+}
+%>
+
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Message Driven Bean</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+<img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+<div id="header">
+ </div>
+<div id="navigation_bar">
+</div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 831; height: 247">
+ <h3>Message Driven Bean</h3>
+ <h4>Name</h4>
+ <p><%=beanMetaData.getEjbName()%> (JNDI: <%=ejbName%>)</p>
+ <h4>EJB Module</h4>
+ <p><%=ejbModule %></p>
+ <h4>Bean Statistics:</h4>
+ <p> </p>
+<%
+if (ejb.isstatisticsProvider())
+{
+%>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Name</h4>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Value</h4>
+ <table border="0" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="100%" id="AutoNumber3">
+ <tr>
+ <td width="33%">
+ <h4 style="text-align: center">Current</h4>
+ </td>
+ <td width="33%">
+ <h4 style="text-align: center">Low</h4>
+ </td>
+ <td width="34%">
+ <h4 style="text-align: center">High</h4>
+ </td>
+ </tr>
+ </table>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Start Time</h4>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Last Sample Time</h4>
+ </td>
+ </tr>
+ <%
+ javax.management.j2ee.statistics.MessageDrivenBeanStats stats = (javax.management.j2ee.statistics.MessageDrivenBeanStats)ejb.getstats ();
+%>
+ <%=addStatRow (stats.getCreateCount ()) %>
+ <%=addStatRow (stats.getRemoveCount ()) %>
+ <%=addStatRow (stats.getMessageCount ()) %>
+
+ </table>
+ <p align="center"><a href="<%=resetUrl%>">Reset Stats</a> / <a href="<%=myUrl%>">Refresh Stats</a></p>
+<%
+}
+else
+{
+%>
+ <p>none.</p>
+<%
+}
+%>
+ <p> </p>
+ <p> </p>
+ <h4>Invocation Statistics:</h4>
+ <p> </p>
+<%
+ java.util.Iterator iterInvoc = invokeStats.getStats().entrySet().iterator();
+ if (iterInvoc.hasNext())
+ {
+
+%>
+
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td align="center">
+ <h4 style="text-align: center">Method name</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Min (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Max (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Average (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Total (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center"># Invocations</h4>
+ </td>
+ </tr>
+ <%
+ while (iterInvoc.hasNext())
+ {
+ java.util.Map.Entry entry = (java.util.Map.Entry) iterInvoc.next();
+ org.jboss.invocation.InvocationStatistics.TimeStatistic stat = (org.jboss.invocation.InvocationStatistics.TimeStatistic) entry.getValue();
+ %>
+
+ <tr>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=((java.lang.reflect.Method)entry.getKey()).getName()%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.minTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.maxTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=(float)stat.totalTime/(float)stat.count%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.totalTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.count%></h4></font>
+ </td>
+ </tr>
+ <%
+ }
+ %>
+ </table>
+ <p align="center"><a href="<%=resetInvocUrl%>">Reset Stats</a> / <a href="<%=myUrl%>">Refresh Stats</a></p>
+<%
+ }
+ else
+ {
+%>
+ <p>none.</p>
+<%
+ }
+%>
+
+ <p> </p>
+ <p>Actual concurrent invocations: <%=invokeStats.concurrentCalls%> (max: <%=invokeStats.maxConcurrentCalls%>)</p>
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ <p><a href="<%=containerUrl%>">View associated container MBean</a></p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Queue.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Queue.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Queue.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,119 @@
+<%@ page import="org.jboss.mq.*"%>
+<%@ page import="org.jboss.mq.server.*"%>
+<%@ page import="java.text.DateFormat"%>
+<%@ page import="java.util.Date"%>
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="queue" intf="org.jboss.mq.server.jmx.QueueMBean"/>
+<%
+ String resetUrl = response.encodeURL(request.getRequestURI()) + "?doReset=true&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName"));
+ String myUrl = response.encodeURL(request.getRequestURI()) + "?" + "&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName"));
+ MessageCounter counter = queue.getMessageCounter()[0];
+
+ //check reset first
+ String doReset = request.getParameter("doReset");
+ if (doReset != null && doReset.equals("true"))
+ {
+ counter.resetCounter();
+ }
+
+ String lastModified = "N/A";
+ DateFormat dateFormat = DateFormat.getDateTimeInstance(DateFormat.SHORT, DateFormat.MEDIUM);
+ if (counter.getLastUpdate() > 0)
+ {
+ lastModified = dateFormat.format(new Date(counter.getLastUpdate()));
+ }
+
+
+%>
+
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - JMS Queue</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+
+<!-- content begin -->
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 95%; height: 95%">
+ <h3>JMS Queue</h3>
+ <h4>Name</h4>
+ <p><%=queue.getQueueName()%></p>
+ <h4>JNDI Name</h4>
+ <p><%=queue.getJNDIName()%></p>
+ <h4>Receiver Count</h4>
+ <p><%=queue.getReceiversCount()%></p>
+ <h4>Message statistics:</h4>
+ <table border="1" cellpadding="0" cellspacing="0" class="data_table" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="33%" >
+ <h4>Queue Depth:</h4>
+ </td>
+ <td width="33%" >
+ <h4>Queue Depth Delta:</h4>
+ </td>
+ <td width="33%">
+ <h4>Maximum Depth:</h4>
+ </td>
+ </tr>
+ <tr align="center">
+ <td><%=queue.getQueueDepth()%></td>
+ <td><%=counter.getDepthDelta()%></td>
+ <td><%=queue.getMaxDepth()%></td>
+ </tr>
+ </table>
+ <p> </p>
+ <p> </p>
+ <h4>Message statistics since startup or reset:</h4>
+ <table border="1" cellpadding="0" cellspacing="0" class="data_table" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="33%" >
+ <h4>Message Count:</h4>
+ </td>
+ <td width="33%">
+ <h4>Message Count Delta:</h4>
+ </td>
+ <td width="33%">
+ <h4>Last Message Add Date:</h4>
+ </td>
+ </tr>
+ <tr align="center">
+ <td><%=counter.getCount()%></td>
+ <td><%=counter.getCountDelta()%></td>
+ <td><%=lastModified%></td>
+ </tr>
+ </table>
+ <p align="center"><a href="<%=resetUrl%>">Reset Stats</a> / <a href="<%=myUrl%>">Refresh Stats</a></p>
+ <p> </p>
+ <p> </p>
+
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<!-- header end -->
+<hr class="hide"/>
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/ServerInfo.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/ServerInfo.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/ServerInfo.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,136 @@
+<%--
+ |
+ | Author: Sacha Labourey (sacha at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="server" mbean='jboss.system:type=Server' intf="org.jboss.system.server.ServerImplMBean" />
+<jb:mbean id="serverInfo" mbean='jboss.system:type=ServerInfo' intf="org.jboss.system.server.ServerInfoMBean" />
+<jb:mbean id="serverConfig" mbean='jboss.system:type=ServerConfig' intf="org.jboss.system.server.ServerConfigImplMBean" />
+<%
+ String myUrl = response.encodeURL(request.getRequestURI());
+%>
+<%!
+public String memSize (java.lang.Long lOctets)
+{
+ long octets = lOctets.longValue();
+ int ratio = 3*1024;
+ String unit = "";
+ if (octets > ratio)
+ {
+ unit = "KB";
+ octets/=1024;
+
+ if (octets > ratio)
+ {
+ unit = "MB";
+ octets/=1024;
+
+ if (octets > ratio)
+ {
+ unit = "GB";
+ octets/=1024;
+
+ if (octets > ratio)
+ {
+ unit = "TB";
+ octets/=1024;
+ }
+ }
+ }
+ }
+
+ return octets + " " + unit;
+}
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Server Information</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3>JBoss™ Application Server</h3>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="2">
+ <h4 style="text-align: center"><font size="3">JBoss</font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td width="25%" align="center" valign="top">
+ <h4>Version</h4>
+ <p align="left"><font size="1"><b>Version: </b><%=server.getVersion()%></font></p>
+ <p align="left"><font size="1"><b>Version Name: </b><%=server.getVersionName()%></font></p>
+ <p align="left"><font size="1"><b>Built on: </b><%=server.getBuildDate()%></font>
+ </td>
+ <td width="25%" align="center" valign="top">
+ <h4>Environment</h4>
+ <p align="left"><font size="1"><b>Start date: </b><%=server.getStartDate()%></font></p>
+ <p align="left"><font size="1"><b>Host: </b><%=serverInfo.getHostName()%> (<%=serverInfo.getHostAddress ()%>)</font></p>
+ <p align="left"><font size="1"><b>Base Location: </b><%=serverConfig.getServerBaseURL()%></font></p>
+ <p align="left"><font size="1"><b>Base Location (local): </b><%=serverConfig.getServerBaseDir()%></font></p>
+ <p align="left"><font size="1"><b>Running config: </b>'<%= serverConfig.getServerHomeDir().getName()%>'</font></td>
+ </tr>
+
+ </table>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center" colspan="2">
+ <h4 style="text-align: center"><font size="3">JVM - Hardware</font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td width="25%" align="center" valign="top">
+ <h4>Hardware</h4>
+ <p align="left"><font size="1"><b>#CPU: </b><%=serverInfo.getAvailableProcessors()%></font></p>
+ <p align="left"><font size="1"><b>OS: </b><%=serverInfo.getOSName()%> <%=serverInfo.getOSVersion()%> (<%=serverInfo.getOSArch()%>)</font></td>
+ <td width="25%" align="center" valign="top">
+ <h4>JVM Environment</h4>
+ <p align="left"><font size="1"><b>Free Memory: </b><%=memSize(serverInfo.getFreeMemory())%></font></p>
+ <p align="left"><font size="1"><b>Max Memory: </b><%=memSize(serverInfo.getMaxMemory())%></font></p>
+ <p align="left"><font size="1"><b>Total Memory: </b><%=memSize(serverInfo.getTotalMemory())%></font></p>
+ <p align="left"><font size="1"><b>#Threads: </b><%=serverInfo.getActiveThreadCount()%></font></p>
+ <p align="left"><font size="1"><b>JVM Version: </b><%=serverInfo.getJavaVMVersion()%> (<%=serverInfo.getJavaVMVendor()%>)</font></p>
+ <p align="left"><font size="1"><b>JVM Name: </b><%=serverInfo.getJavaVMName()%></font></td>
+ </tr>
+
+ </table>
+ <p> </p>
+ <p align="center"> <a href="<%=myUrl%>">Refresh</a></p>
+
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Servlet.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Servlet.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Servlet.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,102 @@
+<%@ page import="javax.management.ObjectName,
+ javax.management.j2ee.statistics.ServletStats,
+ javax.management.j2ee.statistics.TimeStatistic"%>
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="servlet" intf="org.jboss.management.j2ee.ServletMBean" />
+<%
+ String doReset = request.getParameter("doReset");
+ if (doReset != null && doReset.equals("true"))
+ {
+ servlet.resetStats();
+ }
+
+ String resetUrl = response.encodeURL(request.getRequestURI()) + "?doReset=true&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName"));
+ String myUrl = response.encodeURL(request.getRequestURI()) + "?" + "&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName"));
+%>
+
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Servlet</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 831; height: 247">
+ <h3>Servlet</h3>
+ <h4>Name</h4>
+ <p><%=new ObjectName(servlet.getobjectName()).getKeyProperty("name")%> </p>
+ <h4>Servlet Statistics:</h4>
+ <p> </p>
+
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td align="center">
+ <h4 style="text-align: center">Min (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Max (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Average (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Total (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center"># Invocations</h4>
+ </td>
+ </tr>
+ <%
+ ServletStats stats = (ServletStats)servlet.getstats();
+ TimeStatistic stat = stats.getServiceTime();
+ %>
+
+ <tr>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.getMinTime()%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.getMaxTime()%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=(float)stat.getTotalTime()/(float)stat.getCount()%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.getTotalTime()%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.getCount()%></h4></font>
+ </td>
+ </tr>
+ </table>
+ <p align="center"><a href="<%=resetUrl%>">Reset Stats</a> / <a href="<%=myUrl%>">Refresh Stats</a></p>
+ <p> </p>
+ <p> </p>
+
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/StatefulEjb.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/StatefulEjb.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/StatefulEjb.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,231 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="ejb" intf="org.jboss.management.j2ee.StatefulSessionBeanMBean" />
+<jb:mbean id="container" mbean='<%=request.getParameter("ContainerObjectName")%>' intf="org.jboss.ejb.ContainerMBean" />
+<%
+ String ejbName = new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("name");
+ String ejbModule = new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("EJBModule");
+ String containerUrl = java.net.URLEncoder.encode(request.getParameter("ContainerObjectName"));
+ containerUrl = "../jmx-console/HtmlAdaptor?action=inspectMBean&name=" + containerUrl;
+
+ org.jboss.invocation.InvocationStatistics invokeStats= container.getInvokeStats ();
+
+ String doReset = request.getParameter("doReset");
+ if (doReset != null && doReset.equals("true"))
+ {
+ ejb.resetStats ();
+ }
+ String doResetInvoc= request.getParameter("doResetInvoc");
+ if (doResetInvoc!= null && doResetInvoc.equals("true"))
+ {
+ invokeStats.resetStats ();
+ }
+
+ String parameters = "&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName"));
+ parameters = parameters + "&ContainerObjectName=" + java.net.URLEncoder.encode(request.getParameter("ContainerObjectName"));
+
+ String resetUrl = response.encodeURL(request.getRequestURI()) + "?doReset=true" + parameters;
+ String resetInvocUrl = response.encodeURL(request.getRequestURI()) + "?doResetInvoc=true" + parameters;
+ String myUrl = response.encodeURL(request.getRequestURI()) + "?" + parameters;
+ org.jboss.metadata.BeanMetaData beanMetaData = container.getBeanMetaData();
+
+%>
+<%!
+public String addStatRow (javax.management.j2ee.statistics.Statistic stat)
+{
+ String start = new java.util.Date(stat.getStartTime ()).toString ();
+ String lastSample = new java.util.Date(stat.getLastSampleTime ()).toString ();
+
+ String result = "<tr><td width=\"25%\"><font size=\"1\">" + stat.getName() + " (unit: " + stat.getUnit () + ")</font></td>" +
+ "<td width=\"25%\"><table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" style=\"border-collapse: collapse\" bordercolor=\"#111111\" width=\"100%\"><tr>";
+
+ if (stat instanceof javax.management.j2ee.statistics.CountStatistic)
+ {
+ result+= "<td width=\"33%\" align=\"center\"><font size=\"1\">" + ((javax.management.j2ee.statistics.CountStatistic)stat).getCount() + "</font></td><td width=\"33%\"></td><td width=\"34%\"></td>";
+ }
+ else if (stat instanceof javax.management.j2ee.statistics.RangeStatistic)
+ {
+ javax.management.j2ee.statistics.RangeStatistic rStat = (javax.management.j2ee.statistics.RangeStatistic)stat;
+
+ result+= "<td width=\"33%\" align=\"center\"><font size=\"1\">" + rStat.getCurrent () + "</font></td><td width=\"33%\" align=\"center\"><font size=\"1\">" + rStat.getLowWaterMark () + "</font></td>" +
+ "<td width=\"34%\" align=\"center\"><font size=\"1\">" + rStat.getHighWaterMark() + "</font></td>";
+ }
+
+ result+= "</tr></table></td><td width=\"25%\"><font size=\"1\">" + start + "</font></td><td width=\"25%\"><font size=\"1\">" + lastSample + "</font> </td></tr>";
+
+ return result;
+
+}
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Stateful Session Bean</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 831; height: 247">
+ <h3>Stateful Session Bean</h3>
+ <h4>Name</h4>
+ <p><%=beanMetaData.getEjbName()%> (JNDI: <%=ejbName%>)</p>
+ <h4>EJB Module</h4>
+ <p><%=ejbModule %></p>
+ <h4>Bean Statistics:</h4>
+ <p> </p>
+<%
+if (ejb.isstatisticsProvider())
+{
+%>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Name</h4>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Value</h4>
+ <table border="0" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="100%" id="AutoNumber3">
+ <tr>
+ <td width="33%">
+ <h4 style="text-align: center">Current</h4>
+ </td>
+ <td width="33%">
+ <h4 style="text-align: center">Low</h4>
+ </td>
+ <td width="34%">
+ <h4 style="text-align: center">High</h4>
+ </td>
+ </tr>
+ </table>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Start Time</h4>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Last Sample Time</h4>
+ </td>
+ </tr>
+ <%
+ javax.management.j2ee.statistics.StatefulSessionBeanStats stats = (javax.management.j2ee.statistics.StatefulSessionBeanStats)ejb.getstats ();
+%>
+ <%=addStatRow (stats.getMethodReadyCount ()) %>
+ <%=addStatRow (stats.getCreateCount ()) %>
+ <%=addStatRow (stats.getRemoveCount ()) %>
+ <%=addStatRow (stats.getPassiveCount ()) %>
+
+ </table>
+ <p align="center"><a href="<%=resetUrl%>">Reset Stats</a> / <a href="<%=myUrl%>">Refresh Stats</a></p>
+<%
+}
+else
+{
+%>
+ <p>none.</p>
+<%
+}
+%>
+ <p> </p>
+ <p> </p>
+ <h4>Invocation Statistics:</h4>
+ <p> </p>
+<%
+ java.util.Iterator iterInvoc = invokeStats.getStats().entrySet().iterator();
+ if (iterInvoc.hasNext())
+ {
+
+%>
+
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td align="center">
+ <h4 style="text-align: center">Method name</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Min (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Max (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Average (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Total (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center"># Invocations</h4>
+ </td>
+ </tr>
+ <%
+ while (iterInvoc.hasNext())
+ {
+ java.util.Map.Entry entry = (java.util.Map.Entry) iterInvoc.next();
+ org.jboss.invocation.InvocationStatistics.TimeStatistic stat = (org.jboss.invocation.InvocationStatistics.TimeStatistic) entry.getValue();
+ %>
+
+ <tr>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=((java.lang.reflect.Method)entry.getKey()).getName()%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.minTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.maxTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=(float)stat.totalTime/(float)stat.count%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.totalTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.count%></h4></font>
+ </td>
+ </tr>
+ <%
+ }
+ %>
+ </table>
+ <p align="center"><a href="<%=resetInvocUrl%>">Reset Stats</a> / <a href="<%=myUrl%>">Refresh Stats</a></p>
+<%
+ }
+ else
+ {
+%>
+ <p>none.</p>
+<%
+ }
+%>
+
+ <p> </p>
+ <p>Actual concurrent invocations: <%=invokeStats.concurrentCalls%> (max: <%=invokeStats.maxConcurrentCalls%>)</p>
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ <p><a href="<%=containerUrl%>">View associated container MBean</a></p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/StatelessEjb.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/StatelessEjb.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/StatelessEjb.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,230 @@
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="ejb" intf="org.jboss.management.j2ee.StatelessSessionBeanMBean" />
+<jb:mbean id="container" mbean='<%=request.getParameter("ContainerObjectName")%>' intf="org.jboss.ejb.ContainerMBean" />
+<%
+ String ejbName = new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("name");
+ String ejbModule = new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("EJBModule");
+ String containerUrl = java.net.URLEncoder.encode(request.getParameter("ContainerObjectName"));
+ containerUrl = "../jmx-console/HtmlAdaptor?action=inspectMBean&name=" + containerUrl;
+
+ org.jboss.invocation.InvocationStatistics invokeStats= container.getInvokeStats ();
+
+ String doReset = request.getParameter("doReset");
+ if (doReset != null && doReset.equals("true"))
+ {
+ ejb.resetStats ();
+ }
+ String doResetInvoc= request.getParameter("doResetInvoc");
+ if (doResetInvoc!= null && doResetInvoc.equals("true"))
+ {
+ invokeStats.resetStats ();
+ }
+
+ String parameters = "&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName"));
+ parameters = parameters + "&ContainerObjectName=" + java.net.URLEncoder.encode(request.getParameter("ContainerObjectName"));
+
+ String resetUrl = response.encodeURL(request.getRequestURI()) + "?doReset=true" + parameters;
+ String resetInvocUrl = response.encodeURL(request.getRequestURI()) + "?doResetInvoc=true" + parameters;
+ String myUrl = response.encodeURL(request.getRequestURI()) + "?" + parameters;
+ org.jboss.metadata.BeanMetaData beanMetaData = container.getBeanMetaData();
+
+%>
+<%!
+public String addStatRow (javax.management.j2ee.statistics.Statistic stat)
+{
+ String start = new java.util.Date(stat.getStartTime ()).toString ();
+ String lastSample = new java.util.Date(stat.getLastSampleTime ()).toString ();
+
+ String result = "<tr><td width=\"25%\"><font size=\"1\">" + stat.getName() + " (unit: " + stat.getUnit () + ")</font></td>" +
+ "<td width=\"25%\"><table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" style=\"border-collapse: collapse\" bordercolor=\"#111111\" width=\"100%\"><tr>";
+
+ if (stat instanceof javax.management.j2ee.statistics.CountStatistic)
+ {
+ result+= "<td width=\"33%\" align=\"center\"><font size=\"1\">" + ((javax.management.j2ee.statistics.CountStatistic)stat).getCount() + "</font></td><td width=\"33%\"></td><td width=\"34%\"></td>";
+ }
+ else if (stat instanceof javax.management.j2ee.statistics.RangeStatistic)
+ {
+ javax.management.j2ee.statistics.RangeStatistic rStat = (javax.management.j2ee.statistics.RangeStatistic)stat;
+
+ result+= "<td width=\"33%\" align=\"center\"><font size=\"1\">" + rStat.getCurrent () + "</font></td><td width=\"33%\" align=\"center\"><font size=\"1\">" + rStat.getLowWaterMark () + "</font></td>" +
+ "<td width=\"34%\" align=\"center\"><font size=\"1\">" + rStat.getHighWaterMark() + "</font></td>";
+ }
+
+ result+= "</tr></table></td><td width=\"25%\"><font size=\"1\">" + start + "</font></td><td width=\"25%\"><font size=\"1\">" + lastSample + "</font> </td></tr>";
+
+ return result;
+
+}
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Stateless Session Bean</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 831; height: 247">
+ <h3>Stateless Session Bean</h3>
+ <h4>Name</h4>
+ <p><%=beanMetaData.getEjbName()%> (JNDI: <%=ejbName%>)</p>
+ <h4>EJB Module</h4>
+ <p><%=ejbModule %></p>
+ <h4>Bean Statistics:</h4>
+ <p> </p>
+<%
+if (ejb.isstatisticsProvider())
+{
+%>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Name</h4>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Value</h4>
+ <table border="0" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="100%" id="AutoNumber3">
+ <tr>
+ <td width="33%">
+ <h4 style="text-align: center">Current</h4>
+ </td>
+ <td width="33%">
+ <h4 style="text-align: center">Low</h4>
+ </td>
+ <td width="34%">
+ <h4 style="text-align: center">High</h4>
+ </td>
+ </tr>
+ </table>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Start Time</h4>
+ </td>
+ <td width="25%" align="center">
+ <h4 style="text-align: center">Last Sample Time</h4>
+ </td>
+ </tr>
+ <%
+ javax.management.j2ee.statistics.StatelessSessionBeanStats stats = (javax.management.j2ee.statistics.StatelessSessionBeanStats)ejb.getstats ();
+%>
+ <%=addStatRow (stats.getMethodReadyCount ()) %>
+ <%=addStatRow (stats.getCreateCount ()) %>
+ <%=addStatRow (stats.getRemoveCount ()) %>
+
+ </table>
+ <p align="center"><a href="<%=resetUrl%>">Reset Stats</a> / <a href="<%=myUrl%>">Refresh Stats</a></p>
+<%
+}
+else
+{
+%>
+ <p>none.</p>
+<%
+}
+%>
+ <p> </p>
+ <p> </p>
+ <h4>Invocation Statistics:</h4>
+ <p> </p>
+<%
+ java.util.Iterator iterInvoc = invokeStats.getStats().entrySet().iterator();
+ if (iterInvoc.hasNext())
+ {
+
+%>
+
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td align="center">
+ <h4 style="text-align: center">Method name</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Min (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Max (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Average (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center">Total (ms)</h4>
+ </td>
+ <td align="center">
+ <h4 style="text-align: center"># Invocations</h4>
+ </td>
+ </tr>
+ <%
+ while (iterInvoc.hasNext())
+ {
+ java.util.Map.Entry entry = (java.util.Map.Entry) iterInvoc.next();
+ org.jboss.invocation.InvocationStatistics.TimeStatistic stat = (org.jboss.invocation.InvocationStatistics.TimeStatistic) entry.getValue();
+ %>
+
+ <tr>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=((java.lang.reflect.Method)entry.getKey()).getName()%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.minTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.maxTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=(float)stat.totalTime/(float)stat.count%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.totalTime%></h4></font>
+ </td>
+ <td ><font size="1">
+ <h4 style="text-align: center"><%=stat.count%></h4></font>
+ </td>
+ </tr>
+ <%
+ }
+ %>
+ </table>
+ <p align="center"><a href="<%=resetInvocUrl%>">Reset Stats</a> / <a href="<%=myUrl%>">Refresh Stats</a></p>
+<%
+ }
+ else
+ {
+%>
+ <p>none.</p>
+<%
+ }
+%>
+
+ <p> </p>
+ <p>Actual concurrent invocations: <%=invokeStats.concurrentCalls%> (max: <%=invokeStats.maxConcurrentCalls%>)</p>
+ <p> </p>
+ <p> </p>
+ <p> </p>
+ <p><a href="<%=containerUrl%>">View associated container MBean</a></p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/SysProperties.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/SysProperties.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/SysProperties.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - System Properties</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <div id="footer">
+ <div id="footer_bar"> </div>
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%;">
+ <h3>JBoss™ System Properties</h3>
+ <p> </p>
+
+ <table border="1" cellpadding="1" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="85%" align="center" id="AutoNumber1">
+<%
+ java.util.Properties props = System.getProperties ();
+ java.util.Iterator iter = props.keySet().iterator();
+
+ while (iter.hasNext())
+ {
+ String key = (String)iter.next();
+ String value = props.getProperty (key);
+%>
+ <tr>
+ <td align="left" valign="top"><font size="1"><%=key%></font> </td>
+ <td align="left" valign="top"><font size="1"><%=value%></font> </td>
+ </tr>
+<%
+ }
+%>
+
+ </table>
+ <br/> <br/>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Topic.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Topic.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/Topic.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,114 @@
+<%@ page import="java.net.URLEncoder,
+ org.jboss.mq.*,
+ org.jboss.mq.server.*"
+%>
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="topic" intf="org.jboss.mq.server.jmx.TopicMBean"/>
+<%
+ String objParameter = "&ObjectName=" + URLEncoder.encode(request.getParameter("ObjectName"));
+ String myUrl = response.encodeURL(request.getRequestURI()) + "?" + objParameter;
+%>
+
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - JMS Topic</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+
+<!-- content begin -->
+ <center>
+ <div id="content">
+ <table width="95%" height="95%" border="0" cellspacing="0" cellpadding="0">
+ <tr align="center" valign="bottom">
+ <td height="24">
+ <jsp:include page="TopicNavigation.jsp" >
+ <jsp:param name="selectedTabName" value="JMS Topic"/>
+ </jsp:include>
+ </td>
+ </tr>
+ <tr>
+ <td colspan="5" valign="top" class="container">
+ <h4>Name</h4>
+ <p><%=topic.getTopicName()%></p>
+ <h4>JNDI Name</h4>
+ <p><%=topic.getJNDIName()%></p>
+ <h4>Message statistics:</h4>
+ <table border="1" cellpadding="0" cellspacing="0" class="data_table" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td>
+ <h4>All Message Count:</h4>
+ </td>
+ <td>
+ <h4>Durable Message Count:</h4>
+ </td>
+ <td>
+ <h4>Non Durable Message Count:</h4>
+ </td>
+ <td>
+ <h4>Maximum Depth:</h4>
+ </td>
+ </tr>
+ <tr align="center">
+ <td><%=topic.getAllMessageCount()%></td>
+ <td><%=topic.getDurableMessageCount()%></td>
+ <td><%=topic.getNonDurableMessageCount()%></td>
+ <td><%=topic.getMaxDepth()%></td>
+ </tr>
+ </table>
+ <p> </p>
+ <p> </p>
+ <h4>Subscription statistics:</h4>
+ <table border="1" cellpadding="0" cellspacing="0" class="data_table" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="33%" >
+ <h4>All Subscriptions Count:</h4>
+ </td>
+ <td width="33%">
+ <h4>Durable Subcriptions Count</h4>
+ </td>
+ <td width="33%">
+ <h4>Non Durable Subscriptions Count:</h4>
+ </td>
+ </tr>
+ <tr align="center">
+ <td><%=topic.getAllSubscriptionsCount()%></td>
+ <td><%=topic.getDurableSubscriptionsCount()%></td>
+ <td><%=topic.getNonDurableSubscriptionsCount()%></td>
+ </tr>
+ </table>
+ <p align="center"><a href="<%=myUrl%>">Refresh</a></p>
+ <p> </p>
+ <p> </p>
+
+ </td>
+ </tr>
+ </table>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<!-- header end -->
+<hr class="hide"/>
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/TopicNavigation.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/TopicNavigation.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/TopicNavigation.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,9 @@
+<%@ page import="java.net.URLEncoder" %>
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<%
+ String objParameter = "ObjectName=" + URLEncoder.encode(request.getParameter("ObjectName"));
+%>
+<jb:navigation selectedTabName="<%=request.getParameter("selectedTabName")%>">
+ <jb:tab name="JMS Topic" href="<%="Topic.jsp?" + objParameter%>" />
+ <jb:tab name="Subscriptions" href="<%="TopicSubscriptions.jsp?" + objParameter%>" />
+</jb:navigation>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/TopicSubscriptions.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/TopicSubscriptions.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/TopicSubscriptions.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,108 @@
+<%@ page import="java.net.URLEncoder,
+ org.jboss.mq.*,
+ org.jboss.mq.server.*,
+ java.util.*,
+ java.text.DateFormat"
+%>
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="topic" intf="org.jboss.mq.server.jmx.TopicMBean"/>
+<%
+ String objParameter = "&ObjectName=" + URLEncoder.encode(request.getParameter("ObjectName"));
+ String myUrl = response.encodeURL(request.getRequestURI()) + "?" + objParameter;
+
+ MessageCounter[] counter = topic.getMessageCounter();
+ DateFormat dateFormat = DateFormat.getDateTimeInstance(DateFormat.SHORT, DateFormat.MEDIUM);
+%>
+
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - JMS Topic</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+
+<!-- content begin -->
+ <center>
+ <div id="content">
+ <table width="95%" height="95%" border="0" cellspacing="0" cellpadding="0">
+ <tr align="center" valign="bottom">
+ <td height="24">
+ <jsp:include page="TopicNavigation.jsp" >
+ <jsp:param name="selectedTabName" value="Subscriptions"/>
+ </jsp:include>
+ </td>
+ </tr>
+ <tr>
+ <td colspan="5" valign="top" class="container">
+ <h4>Name</h4>
+ <p><%=topic.getTopicName()%></p>
+ <h4>Subscriptions:</h4>
+ <table border="1" cellpadding="0" cellspacing="0" class="data_table" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td>
+ <h4>Subscription Name:</h4>
+ </td>
+ <td>
+ <h4>Durable:</h4>
+ </td>
+ <td>
+ <h4>Message Count:</h4>
+ </td>
+ <td>
+ <h4>Message Count Delta:</h4>
+ </td>
+ <td>
+ <h4>Last Message Add Date:</h4>
+ </td>
+ </tr>
+<% for(int i = 0; i < counter.length; i++)
+{
+ String lastModified = "N/A";
+ if (counter[i].getLastUpdate() > 0)
+ {
+ lastModified = dateFormat.format(new Date(counter[i].getLastUpdate()));
+ }
+%>
+ <tr align="center">
+ <td align="left"> <%=counter[i].getDestinationSubscription()%> </td>
+ <td><%=counter[i].getDestinationDurable()%></td>
+ <td><%=counter[i].getDepth()%></td>
+ <td><%=counter[i].getDepthDelta()%></td>
+ <td><%=lastModified%></td>
+ </tr>
+<%}%>
+ </table>
+ <p align="center"><a href="<%=myUrl%>">Refresh</a></p>
+ <p> </p>
+ <p> </p>
+ </td>
+ </tr>
+ </table>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<!-- header end -->
+<hr class="hide"/>
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/Classloaders.bsh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/Classloaders.bsh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/Classloaders.bsh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,83 @@
+import org.jboss.console.manager.interfaces.*;
+import org.jboss.console.manager.interfaces.impl.*;
+import org.jboss.console.plugins.*;
+import org.jboss.console.plugins.helpers.*;
+
+import javax.management.*;
+
+ String getVersion (PluginContext ctx)
+ {
+ return "0.0a";
+ }
+
+ String getName (PluginContext ctx)
+ {
+ return "UCL lister";
+ }
+
+ ResourceTreeNode createUCLSubResource (PluginContext ctx, ObjectInstance instance)
+ {
+ String uclName = instance.getObjectName().getKeyProperty ("UCL");
+ TreeNodeMenuEntry[] menus = ctx.createMenus (new String[]
+ {
+ "Before for UCL="+uclName, "before.html&ucl="+uclName,
+ null,
+ "After", "test.html"
+ });
+
+ return ctx.createResourceNode (
+ "UCL " + uclName, // name
+ "UCL with id " + uclName, // description
+ "arrow.gif", // Icon URL
+ "mapage&ucl=" + uclName, // Default URL
+ menus,
+ null,
+ null,
+ instance.getObjectName().toString(),
+ instance.getClassName () );
+ }
+
+ ResourceTreeNode[] createUCLSubResources (PluginContext ctx)
+ {
+ ObjectInstance[] insts =
+ ctx.getMBeansForClass("jmx.loading:*",
+ "org.jboss.mx.loading.UnifiedClassLoader2");
+ ctx.getLogger().info("TAILLE: " + insts.length);
+ ResourceTreeNode[] result = new ResourceTreeNode[10];//[insts.length];
+ for (int i=0; i<result.length && i<10; i++)
+ {
+ ctx.getLogger().info("ELT: " + insts[i]);
+ result[i] = createUCLSubResource (ctx, insts[i]);
+ }
+
+ return result;
+ }
+
+ TreeNode getTreeForResource(ManageableResource resource,
+ PluginContext ctx)
+ {
+ try
+ {
+ TreeNodeMenuEntry[] menus = ctx.createMenus (new String[]
+ {
+ "Before", "before.html",
+ null,
+ "After", "after.html"
+ });
+
+ return ctx.createTreeNode (
+ "Unified ClassLoaders", // name
+ "Display all JBoss UCLs", // description
+ "http://localhost:8080/web-console/arrow.gif", // Icon URL
+ "http://www.jboss.org/", // Default URL
+ menus,
+ null, // sub nodes
+ createUCLSubResources (ctx) // Sub-Resources
+ );
+ }
+ catch (Exception e)
+ {
+ e.printStackTrace ();
+ return null;
+ }
+ }
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/J2EEFolder.bsh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/J2EEFolder.bsh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/J2EEFolder.bsh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,27 @@
+import org.jboss.console.manager.interfaces.*;
+import org.jboss.console.manager.interfaces.impl.*;
+import org.jboss.console.plugins.*;
+import org.jboss.console.plugins.helpers.*;
+
+
+ TreeNode getTreeForResource(ManageableResource resource,
+ PluginContext ctx)
+ {
+ try
+ {
+ return ctx.createResourceNode (
+ "J2EE", // name
+ "J2EE Management", // description
+ "images/elements32.gif", // Icon URL
+ null, // Default URL
+ null,
+ null,
+ null,
+ new SimpleFolderResource ("ROOT/J2EE")).setVisibility(ResourceTreeNode.INVISIBLE_IF_SUBNODE_EXISTS);
+ }
+ catch (Exception e)
+ {
+ e.printStackTrace ();
+ return null;
+ }
+ }
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/JNDIView.bsh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/JNDIView.bsh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/JNDIView.bsh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,27 @@
+import org.jboss.console.manager.interfaces.*;
+import org.jboss.console.manager.interfaces.impl.*;
+import org.jboss.console.plugins.*;
+import org.jboss.console.plugins.helpers.*;
+
+
+ TreeNode getTreeForResource(ManageableResource resource,
+ PluginContext ctx)
+ {
+ try
+ {
+ return ctx.createResourceNode (
+ "JNDIView", // name
+ "Viewer for JNDI Tree", // description
+ "images/jndiview.gif", // Icon URL
+ "JNDIView.jsp", // Default URL
+ null,
+ null,
+ null,
+ new SimpleFolderResource ("ROOT/JNDIView"));
+ }
+ catch (Exception e)
+ {
+ e.printStackTrace ();
+ return null;
+ }
+ }
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/SystemFolder.bsh
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/SystemFolder.bsh (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/SystemFolder.bsh 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,27 @@
+import org.jboss.console.manager.interfaces.*;
+import org.jboss.console.manager.interfaces.impl.*;
+import org.jboss.console.plugins.*;
+import org.jboss.console.plugins.helpers.*;
+
+
+ TreeNode getTreeForResource(ManageableResource resource,
+ PluginContext ctx)
+ {
+ try
+ {
+ return ctx.createResourceNode (
+ "System", // name
+ "JBoss Kernel Management", // description
+ "images/settings32.gif", // Icon URL
+ "SysProperties.jsp", // Default URL
+ null,
+ null,
+ null,
+ new SimpleFolderResource ("ROOT/System"));
+ }
+ catch (Exception e)
+ {
+ e.printStackTrace ();
+ return null;
+ }
+ }
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-roles.properties
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-roles.properties (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-roles.properties 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,2 @@
+# A sample roles.properties file for use with the UsersRolesLoginModule
+admin=JBossAdmin
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-users.properties
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-users.properties (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-users.properties 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,2 @@
+# A sample users.properties file for use with the UsersRolesLoginModule
+admin=admin
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/jboss-web.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/jboss-web.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/jboss-web.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,17 @@
+<?xml version='1.0' encoding='UTF-8' ?>
+
+<!DOCTYPE jboss-web
+ PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
+
+<jboss-web>
+
+ <!-- Uncomment the security-domain to enable security. You will
+ need to edit the htmladaptor login configuration to setup the
+ login modules used to authentication users.
+ <security-domain>java:/jaas/web-console</security-domain>
+ -->
+
+ <!-- The war depends on the -->
+ <depends>jboss.admin:service=PluginManager</depends>
+</jboss-web>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/tlds/webconsole.tld
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/tlds/webconsole.tld (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/tlds/webconsole.tld 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="ISO-8859-1" ?>
+<!DOCTYPE taglib
+ PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
+ "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
+
+<taglib>
+ <tlibversion>1.0</tlibversion>
+ <jspversion>1.1</jspversion>
+ <shortname>webconsole</shortname>
+
+ <tag>
+ <name>mbean</name>
+ <tagclass>org.jboss.console.plugins.helpers.servlet.MBeanTag</tagclass>
+ <teiclass>org.jboss.console.plugins.helpers.servlet.MBeanTagExtraInfo</teiclass>
+ <bodycontent>JSP</bodycontent>
+ <info>Returns a proxy to an MBean reading the "ObjectName" query parameter</info>
+ <attribute>
+ <name>mbean</name>
+ <required>false</required>
+ <rtexprvalue>true</rtexprvalue>
+ </attribute>
+ <attribute>
+ <name>intf</name>
+ <required>true</required>
+ <rtexprvalue>true</rtexprvalue>
+ </attribute>
+ <attribute>
+ <name>id</name>
+ <required>true</required>
+ <rtexprvalue>false</rtexprvalue>
+ </attribute>
+ </tag>
+
+ <tag>
+ <name>navigation</name>
+ <tagclass>org.jboss.console.plugins.helpers.servlet.NavigationTag</tagclass>
+ <bodycontent>JSP</bodycontent>
+ <attribute>
+ <name>selectedTabName</name>
+ <required>false</required>
+ <rtexprvalue>true</rtexprvalue>
+ </attribute>
+ </tag>
+
+ <tag>
+ <name>tab</name>
+ <tagclass>org.jboss.console.plugins.helpers.servlet.TabTag</tagclass>
+ <bodycontent>JSP</bodycontent>
+ <attribute>
+ <name>name</name>
+ <required>true</required>
+ <rtexprvalue>true</rtexprvalue>
+ </attribute>
+ <attribute>
+ <name>href</name>
+ <rtexprvalue>true</rtexprvalue>
+ </attribute>
+ <attribute>
+ <name>selected</name>
+ <rtexprvalue>true</rtexprvalue>
+ </attribute>
+ </tag>
+
+</taglib>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/web.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/web.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WEB-INF/web.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,367 @@
+<?xml version="1.0"?>
+<!DOCTYPE web-app PUBLIC
+ "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
+ "http://java.sun.com/dtd/web-app_2_3.dtd">
+
+<web-app>
+ <description>Web Admin Console</description>
+ <servlet>
+ <servlet-name>J2EEFolder</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>ScriptName</param-name>
+ <param-value>J2EEFolder.bsh</param-value>
+ </init-param>
+ <init-param>
+ <param-name>IsRootNode</param-name>
+ <param-value>true</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>SystemFolder</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>ScriptName</param-name>
+ <param-value>SystemFolder.bsh</param-value>
+ </init-param>
+ <init-param>
+ <param-name>IsRootNode</param-name>
+ <param-value>true</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>MonitorsFolder</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>WrapperClass</param-name>
+ <param-value>org.jboss.console.plugins.MonitorLister</param-value>
+ </init-param>
+ <init-param>
+ <param-name>IsRootNode</param-name>
+ <param-value>true</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>AOPFolder</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>WrapperClass</param-name>
+ <param-value>org.jboss.console.plugins.AOPLister</param-value>
+ </init-param>
+ <init-param>
+ <param-name>IsRootNode</param-name>
+ <param-value>true</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>JMS Message</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>WrapperClass</param-name>
+ <param-value>org.jboss.console.plugins.JMSLister</param-value>
+ </init-param>
+ <init-param>
+ <param-name>MBeanClass</param-name>
+ <param-value>org.jboss.management.j2ee.JMSResource</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <!--servlet>
+ <servlet-name>UCLs</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>ScriptName</param-name>
+ <param-value>Classloaders.bsh</param-value>
+ </init-param>
+ <init-param>
+ <param-name>FolderName</param-name>
+ <param-value>ROOT/System</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet-->
+
+ <servlet>
+ <servlet-name>UCLs</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>WrapperClass</param-name>
+ <param-value>org.jboss.console.plugins.UCLLister</param-value>
+ </init-param>
+ <init-param>
+ <param-name>FolderName</param-name>
+ <param-value>ROOT/System</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>MBeans</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>WrapperClass</param-name>
+ <param-value>org.jboss.console.plugins.MBeansLister</param-value>
+ </init-param>
+ <init-param>
+ <param-name>FolderName</param-name>
+ <param-value>ROOT/System</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>JSR77 Domains and Servers</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>WrapperClass</param-name>
+ <param-value>org.jboss.console.plugins.JSR77Lister</param-value>
+ </init-param>
+ <init-param>
+ <param-name>FolderName</param-name>
+ <param-value>ROOT/J2EE</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>JSR77 EJBModules and EJBs</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>WrapperClass</param-name>
+ <param-value>org.jboss.console.plugins.EJBModuleLister</param-value>
+ </init-param>
+ <init-param>
+ <param-name>MBeanClass</param-name>
+ <param-value>org.jboss.management.j2ee.EJBModule</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>JSR77 J2EE Apps</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>WrapperClass</param-name>
+ <param-value>org.jboss.console.plugins.J2EEAppLister</param-value>
+ </init-param>
+ <init-param>
+ <param-name>MBeanClass</param-name>
+ <param-value>org.jboss.management.j2ee.J2EEApplication</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>JSR77 WebModule</servlet-name>
+ <servlet-class>org.jboss.console.plugins.helpers.ServletPluginHelper</servlet-class>
+ <init-param>
+ <param-name>WrapperClass</param-name>
+ <param-value>org.jboss.console.plugins.WebModuleLister</param-value>
+ </init-param>
+ <init-param>
+ <param-name>MBeanClass</param-name>
+ <param-value>org.jboss.management.j2ee.WebModule</param-value>
+ </init-param>
+ <init-param>
+ <param-name>ContextName</param-name>
+ <param-value>/web-console</param-value>
+ </init-param>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>HTTP Invocation</servlet-name>
+ <servlet-class>org.jboss.console.remote.InvokerServlet</servlet-class>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>Create Snapshot</servlet-name>
+ <servlet-class>org.jboss.console.plugins.monitor.CreateSnapshotServlet</servlet-class>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>Manage Snapshot</servlet-name>
+ <servlet-class>org.jboss.console.plugins.monitor.ManageSnapshotServlet</servlet-class>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>Create Threshold Monitor</servlet-name>
+ <servlet-class>org.jboss.console.plugins.monitor.CreateThresholdMonitorServlet</servlet-class>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>Manage Threshold Monitor</servlet-name>
+ <servlet-class>org.jboss.console.plugins.monitor.ManageThresholdMonitorServlet</servlet-class>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>Create String Threshold Monitor</servlet-name>
+ <servlet-class>org.jboss.console.plugins.monitor.CreateStringThresholdMonitorServlet</servlet-class>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>Manage String Threshold Monitor</servlet-name>
+ <servlet-class>org.jboss.console.plugins.monitor.ManageStringThresholdMonitorServlet</servlet-class>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>Clear Monitor Alerts</servlet-name>
+ <servlet-class>org.jboss.console.plugins.monitor.ClearMonitorAlertsServlet</servlet-class>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>Acknowledge Active Alarms</servlet-name>
+ <servlet-class>org.jboss.console.plugins.monitor.AcknowledgeActiveAlarmsServlet</servlet-class>
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+
+ <servlet>
+ <servlet-name>Status Servlet</servlet-name>
+ <servlet-class>org.jboss.web.tomcat.service.StatusServlet</servlet-class>
+ </servlet>
+
+ <servlet-mapping>
+ <servlet-name>Status Servlet</servlet-name>
+ <url-pattern>/status</url-pattern>
+ </servlet-mapping>
+
+ <servlet-mapping>
+ <servlet-name>HTTP Invocation</servlet-name>
+ <url-pattern>/Invoker/*</url-pattern>
+ </servlet-mapping>
+
+ <servlet-mapping>
+ <servlet-name>Create Snapshot</servlet-name>
+ <url-pattern>/CreateSnapshot</url-pattern>
+ </servlet-mapping>
+
+ <servlet-mapping>
+ <servlet-name>Manage Snapshot</servlet-name>
+ <url-pattern>/ManageSnapshot</url-pattern>
+ </servlet-mapping>
+
+ <servlet-mapping>
+ <servlet-name>Create Threshold Monitor</servlet-name>
+ <url-pattern>/CreateThresholdMonitor</url-pattern>
+ </servlet-mapping>
+
+ <servlet-mapping>
+ <servlet-name>Manage Threshold Monitor</servlet-name>
+ <url-pattern>/ManageThresholdMonitor</url-pattern>
+ </servlet-mapping>
+
+ <servlet-mapping>
+ <servlet-name>Create String Threshold Monitor</servlet-name>
+ <url-pattern>/CreateStringThresholdMonitor</url-pattern>
+ </servlet-mapping>
+
+ <servlet-mapping>
+ <servlet-name>Manage String Threshold Monitor</servlet-name>
+ <url-pattern>/ManageStringThresholdMonitor</url-pattern>
+ </servlet-mapping>
+
+ <servlet-mapping>
+ <servlet-name>Clear Monitor Alerts</servlet-name>
+ <url-pattern>/ClearMonitorAlerts</url-pattern>
+ </servlet-mapping>
+
+ <servlet-mapping>
+ <servlet-name>Acknowledge Active Alarms</servlet-name>
+ <url-pattern>/AcknowledgeActiveAlarms</url-pattern>
+ </servlet-mapping>
+
+ <taglib>
+ <taglib-uri>/webconsole</taglib-uri>
+ <taglib-location>/WEB-INF/tlds/webconsole.tld</taglib-location>
+ </taglib>
+
+ <!-- A security constraint that restricts access to the HTML JMX console
+ to users with the role JBossAdmin. Edit the roles to what you want and
+ uncomment the WEB-INF/jboss-web.xml/security-domain element to enable
+ secured access to the HTML JMX console.
+
+ <security-constraint>
+ <web-resource-collection>
+ <web-resource-name>HtmlAdaptor</web-resource-name>
+ <description>An example security config that only allows users with the
+ role JBossAdmin to access the HTML JMX console web application
+ </description>
+ <url-pattern>/*</url-pattern>
+ <http-method>GET</http-method>
+ <http-method>POST</http-method>
+ </web-resource-collection>
+ <auth-constraint>
+ <role-name>JBossAdmin</role-name>
+ </auth-constraint>
+ </security-constraint>
+ -->
+
+ <login-config>
+ <auth-method>BASIC</auth-method>
+ <realm-name>JBoss WEB Console</realm-name>
+ </login-config>
+
+ <security-role>
+ <role-name>JBossAdmin</role-name>
+ </security-role>
+</web-app>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WebModule.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WebModule.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/WebModule.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,102 @@
+<%@ page import="javax.management.ObjectName"%>
+ <%--
+ |
+ | Author: Sacha Labourey (sacha at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%@ taglib uri="/webconsole" prefix="jb" %>
+<jb:mbean id="webModule" intf="org.jboss.management.j2ee.WebModuleMBean" />
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Web Module</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3>Web Module: '<%=new ObjectName(webModule.getobjectName()).getKeyProperty("name")%>'</h3>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center">
+ <h4 style="text-align: center"><font size="3">Servlets</font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td width="50%" align="center" valign="top">
+ <h4>This Web Module is composed of the following Servlets:</h4>
+ <%
+ String[] namesStr = webModule.getservlets();
+ ObjectName[] names = null;
+ if (namesStr != null) {
+ names = new ObjectName[namesStr.length];
+ for (int i = 0; i < namesStr.length; i++) {
+ names[i] = new ObjectName(namesStr[i]);
+ }
+ }
+ if (names != null)
+ %>
+ <ul>
+ <%
+ for (int i = 0; i < names.length; i++)
+ {
+ %>
+ <li>
+ <p align="left"><font size="1"><b><%=names[i].getKeyProperty("name")%></b></font></p>
+ </li>
+ <%
+ }
+ %>
+ </ul>
+ <p align="left"><font size="1"><b>Number of Servlets: </b><%=(names!=null?names.length:0)%></font></p>
+ </td>
+ </tr>
+
+ </table>
+ <p> </p>
+ <table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="95%" align="center" id="AutoNumber1">
+ <tr>
+ <td width="50%" align="center">
+ <h4 style="text-align: center"><font size="3">Deployment
+ Descriptor</font></h4>
+ </td>
+ </tr>
+ <tr>
+ <td width="50%" align="left" valign="top"><pre>
+ <%=org.jboss.console.plugins.helpers.servlet.ServletHelper.filter(webModule.getdeploymentDescriptor())%>
+ </pre>
+ </td>
+ </tr>
+
+ </table>
+ <p> </p>
+ <p> </p>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/applet.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/applet.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/applet.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/applet.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/applet.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,24 @@
+<html>
+
+<head>
+</head>
+
+<body>
+
+<p>
+<applet
+ width="100%"
+ height="100%"
+ code="org.jboss.console.navtree.AppletBrowser"
+ archive="applet.jar"
+ >
+ <!-- An empty refresh value disables the background refresh thread -->
+ <param name="RefreshTime" value="">
+ <param name="SessionId" value="<%=request.getSession().getId()%>">
+ <param name="PMJMXName" value="jboss.admin:service=PluginManager">
+</applet>
+</p>
+
+</body>
+
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createSnapshot.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createSnapshot.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createSnapshot.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,98 @@
+<%@ page import="javax.management.MBeanServer,
+ org.jboss.mx.util.MBeanServerLocator,
+ org.jboss.mx.util.InstanceOfQueryExp,
+ java.util.Set,
+ java.util.Iterator,
+ javax.management.ObjectInstance,
+ javax.management.ObjectName,
+ java.util.HashSet"%>
+ <%--
+ |
+ | Author: Bill Burke (bill at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%
+ String error = (String)request.getAttribute("error");
+ String attribute = request.getParameter("attribute");
+ if (attribute == null) attribute = "";
+ String monitorName = request.getParameter("monitorName");
+ if (monitorName == null) monitorName = attribute + " Snapshot";
+ String objectName = request.getParameter("objectName");
+ if (objectName == null) objectName = "";
+ String period = request.getParameter("period");
+ if (period == null) period = "";
+ String maxSize = request.getParameter("maxSize");
+ if (maxSize == null) maxSize = "";
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Create Snapshot</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3>Create Snapshot MBean Monitor</h3>
+ <p> </p>
+<%
+ if (error != null)
+ {
+%>
+ <p><font color="red" size ="-2"><%=error%></font> </p>
+<%
+ }
+%>
+<form action="CreateSnapshot" method="post">
+<table cellspacing="2" cellpadding="2" border="0">
+<tr>
+ <td><b>Monitor Name</b></td>
+ <td><input type="text" name="monitorName" size="35" value="<%=monitorName%>"></td>
+ <td><i>The name of the monitor and how it will be references within web console</i></td>
+</tr>
+<tr>
+ <td><b>Object Name</b></td>
+ <td><input type="text" name="objectName" value="<%=objectName%>" size="35"></td>
+ <td><i>The MBean javax.management.ObjectName of the MBean you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Attribute</b></td>
+ <td><input type="text" name="attribute" value="<%=attribute%>" size="35"></td>
+ <td><i>The MBean Attribute you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Time Period</b></td>
+ <td><input type="text" name="period" size="35" value="<%=period%>"></td>
+ <td><i>How often should threshold be tested.</i></td>
+</tr>
+</table>
+<input type="submit" value="Create">
+</form>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createStringThresholdMonitor.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createStringThresholdMonitor.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createStringThresholdMonitor.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,173 @@
+<%@ page import="javax.management.MBeanServer,
+ org.jboss.mx.util.MBeanServerLocator,
+ org.jboss.mx.util.InstanceOfQueryExp,
+ java.util.Set,
+ java.util.Iterator,
+ javax.management.ObjectInstance,
+ javax.management.ObjectName,
+ java.util.HashSet"%>
+ <%--
+ |
+ | Author: Bill Burke (bill at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%
+ MBeanServer mbeanServer = MBeanServerLocator.locateJBoss();
+ String error = (String)request.getAttribute("error");
+ String monitorName = request.getParameter("monitorName");
+ if (monitorName == null) monitorName = "";
+ String objectName = request.getParameter("objectName");
+ if (objectName == null) objectName = "";
+ String attribute = request.getParameter("attribute");
+ if (attribute == null) attribute = "";
+ String threshold = request.getParameter("threshold");
+ if (threshold == null && objectName != null && attribute != null)
+ {
+ threshold = (String)mbeanServer.getAttribute(new ObjectName(objectName), attribute);
+ }
+ else if (threshold == null) threshold = "";
+
+ String period = request.getParameter("period");
+ if (period == null) period = "";
+ String equality = request.getParameter("equality");
+ if (equality == null) equality = "";
+ else equality = "checked";
+ String enabled = request.getParameter("enabled");
+ if (enabled == null) enabled = "";
+ else enabled = "checked";
+ String[] alertStrings = request.getParameterValues("alerts");
+ HashSet alertSet = null;
+ if (alertStrings != null)
+ {
+ alertSet = new HashSet();
+ for (int i = 0; i < alertStrings.length; i++)
+ {
+ alertSet.add(alertStrings[i]);
+ }
+ }
+
+
+
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Create String Threshold Monitor</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3>Create String Threshold MBean Monitor</h3>
+ <p> </p>
+<%
+ if (error != null)
+ {
+%>
+ <p><font color="red" size ="-2"><%=error%></font> </p>
+<%
+ }
+%>
+<form action="CreateStringThresholdMonitor" method="post">
+<table cellspacing="2" cellpadding="2" border="0">
+<tr>
+ <td><b>Monitor Name</b></td>
+ <td><input type="text" name="monitorName" size="35" value="<%=monitorName%>"></td>
+ <td><i>The name of the monitor and how it will be references within web console</i></td>
+</tr>
+<tr>
+ <td><b>Object Name</b></td>
+ <td><input type="text" name="objectName" value="<%=objectName%>" size="35"></td>
+ <td><i>The MBean javax.management.ObjectName of the MBean you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Attribute</b></td>
+ <td><input type="text" name="attribute" value="<%=attribute%>" size="35"></td>
+ <td><i>The MBean Attribute you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Threshold</b></td>
+ <td><input type="text" name="threshold" size="35" value="<%=threshold%>"></td>
+ <td><i>The value that will trigger an alert when the Comparison Equation is reached for the attribute value</i></td>
+</tr>
+<tr>
+ <td><b>Time Period</b></td>
+ <td><input type="text" name="period" size="35" value="<%=period%>"></td>
+ <td><i>How often should threshold be tested.</i></td>
+</tr>
+<tr>
+ <td><b>Equality Trigger</b></td>
+ <td><input type="checkbox" name="equality" value="" <%=equality%>></td>
+ <td><i>Uncheck this box if you want an alert to trigger when attribute changes from threshold value</i></td>
+</tr>
+<tr>
+ <td><b>Persisted</b></td>
+ <td><input type="checkbox" name="persisted" value="" checked></td>
+ <td><i>Should this monitor be created for next JBoss reboot?</i></td>
+</tr>
+<tr>
+ <td><b>Enable Monitor</b></td>
+ <td><input type="checkbox" name="enabled" value="" <%=enabled%>></td>
+ <td><i>Should this monitor be enabled.</i></td>
+</tr>
+<tr>
+ <td><b>Alerts</b></td>
+ <td>
+<%
+ InstanceOfQueryExp queryExp = null;
+ queryExp = new InstanceOfQueryExp("org.jboss.monitor.alerts.JBossAlertListener");
+ Set alerts = mbeanServer.queryNames(null, queryExp);
+ if (alerts.size() > 0)
+ {
+%>
+ <select name="alerts" id="alerts" size="<%=Integer.toString(alerts.size())%>" multiple>
+<%
+ Iterator it = alerts.iterator();
+ while (it.hasNext())
+ {
+ ObjectName alert = (ObjectName)it.next();
+ String alertName = (String)mbeanServer.getAttribute(alert, "AlertName");
+ String selected = "";
+ if (alertSet != null && alertSet.contains(alert.toString())) selected = "SELECTED";
+%>
+ <option value="<%=alert.toString()%>" <%=selected%>><%=alertName%></option>
+<%
+ }
+ }
+%>
+</select>
+
+ </td>
+ <td><i>Alert Listeners to trigger.</i></td>
+</tr>
+</table>
+<input type="submit" value="Create">
+</form>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createStringThresholdMonitorSummary.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createStringThresholdMonitorSummary.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createStringThresholdMonitorSummary.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,154 @@
+<%@ page import="javax.management.MBeanServer,
+ org.jboss.mx.util.MBeanServerLocator,
+ org.jboss.mx.util.InstanceOfQueryExp,
+ java.util.Set,
+ java.util.Iterator,
+ javax.management.ObjectInstance,
+ javax.management.ObjectName,
+ java.util.HashSet"%>
+ <%--
+ |
+ | Author: Bill Burke (bill at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%
+ String monitorName = request.getParameter("monitorName");
+ if (monitorName == null) monitorName = "";
+ String objectName = request.getParameter("objectName");
+ if (objectName == null) objectName = "";
+ String attribute = request.getParameter("attribute");
+ if (attribute == null) attribute = "";
+ String threshold = request.getParameter("threshold");
+ if (threshold == null) threshold = "";
+ String period = request.getParameter("period");
+ if (period == null) period = "";
+ String equality = request.getParameter("equality");
+ if (equality == null) equality = "";
+ else equality = "checked";
+ String enabled = request.getParameter("enabled");
+ if (enabled == null) enabled = "";
+ else enabled = "checked";
+ String[] alertStrings = request.getParameterValues("alerts");
+ HashSet alertSet = null;
+ if (alertStrings != null)
+ {
+ alertSet = new HashSet();
+ for (int i = 0; i < alertStrings.length; i++)
+ {
+ alertSet.add(alertStrings[i]);
+ }
+ }
+
+
+
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Create String Monitor Summary</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3>String MBean Monitor Created</h3>
+ <p> </p>
+ <p> </p>
+<table cellspacing="2" cellpadding="2" border="0">
+<tr>
+ <td><b>Monitor Name</b></td>
+ <td><input type="text" name="monitorName" size="35" value="<%=monitorName%>" readonly></td>
+ <td><i>The name of the monitor and how it will be references within web console</i></td>
+</tr>
+<tr>
+ <td><b>Object Name</b></td>
+ <td><input type="text" name="objectName" value="<%=objectName%>" size="35" readonly></td>
+ <td><i>The MBean javax.management.ObjectName of the MBean you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Attribute</b></td>
+ <td><input type="text" name="attribute" value="<%=attribute%>" size="35" readonly></td>
+ <td><i>The MBean Attribute you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Threshold</b></td>
+ <td><input type="text" name="threshold" size="35" value="<%=threshold%>" readonly></td>
+ <td><i>The value that will trigger an alert when the Comparison Equation is reached for the attribute value</i></td>
+</tr>
+<tr>
+ <td><b>Time Period</b></td>
+ <td><input type="text" name="period" size="35" value="<%=period%>" readonly></td>
+ <td><i>How often should threshold be tested.</i></td>
+</tr>
+<tr>
+ <td><b>Equality Trigger</b></td>
+ <td><input type="checkbox" name="equality" value="" <%=equality%>></td>
+ <td><i>Uncheck this box if you want an alert to trigger when attribute changes from threshold value</i></td>
+</tr>
+<tr>
+ <td><b>Enable Monitor</b></td>
+ <td><input type="checkbox" name="enabled" value="" <%=enabled%>></td>
+ <td><i>Should this monitor be enabled.</i></td>
+</tr>
+<tr>
+ <td><b>Alerts</b></td>
+ <td>
+<%
+ MBeanServer mbeanServer = MBeanServerLocator.locateJBoss();
+ InstanceOfQueryExp queryExp = null;
+ queryExp = new InstanceOfQueryExp("org.jboss.monitor.alerts.JBossAlertListener");
+ Set alerts = mbeanServer.queryNames(null, queryExp);
+ if (alerts.size() > 0)
+ {
+%>
+ <select name="alerts" id="alerts" size="<%=Integer.toString(alerts.size())%>" multiple readonly>
+<%
+ Iterator it = alerts.iterator();
+ while (it.hasNext())
+ {
+ ObjectName alert = (ObjectName)it.next();
+ if (alertSet.contains(alert.toString()))
+ {
+ String alertName = (String)mbeanServer.getAttribute(alert, "AlertName");
+%>
+ <option value="<%=alert.toString()%>" ><%=alertName%></option>
+<%
+ }
+ }
+ }
+%>
+</select>
+
+ </td>
+ <td><i>Alert Listeners to trigger.</i></td>
+</tr>
+</table>
+</form>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createThresholdMonitor.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createThresholdMonitor.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createThresholdMonitor.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,171 @@
+<%@ page import="javax.management.MBeanServer,
+ org.jboss.mx.util.MBeanServerLocator,
+ org.jboss.mx.util.InstanceOfQueryExp,
+ java.util.Set,
+ java.util.Iterator,
+ javax.management.ObjectInstance,
+ javax.management.ObjectName,
+ java.util.HashSet"%>
+ <%--
+ |
+ | Author: Bill Burke (bill at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%
+ String error = (String)request.getAttribute("error");
+ String monitorName = request.getParameter("monitorName");
+ if (monitorName == null) monitorName = "";
+ String objectName = request.getParameter("objectName");
+ if (objectName == null) objectName = "";
+ String attribute = request.getParameter("attribute");
+ if (attribute == null) attribute = "";
+ String threshold = request.getParameter("threshold");
+ if (threshold == null) threshold = "";
+ String period = request.getParameter("period");
+ if (period == null) period = "";
+ String compare = request.getParameter("compare");
+ if (compare == null) compare = "gt";
+ String enabled = request.getParameter("enabled");
+ if (enabled == null) enabled = "";
+ String[] alertStrings = request.getParameterValues("alerts");
+ HashSet alertSet = null;
+ if (alertStrings != null)
+ {
+ alertSet = new HashSet();
+ for (int i = 0; i < alertStrings.length; i++)
+ {
+ alertSet.add(alertStrings[i]);
+ }
+ }
+
+
+
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Server Information</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3>Create Threshold MBean Monitor</h3>
+ <p> </p>
+<%
+ if (error != null)
+ {
+%>
+ <p><font color="red" size ="-2"><%=error%></font> </p>
+<%
+ }
+%>
+<form action="CreateThresholdMonitor" method="post">
+<table cellspacing="2" cellpadding="2" border="0">
+<tr>
+ <td><b>Monitor Name</b></td>
+ <td><input type="text" name="monitorName" size="35" value="<%=monitorName%>"></td>
+ <td><i>The name of the monitor and how it will be references within web console</i></td>
+</tr>
+<tr>
+ <td><b>Object Name</b></td>
+ <td><input type="text" name="objectName" value="<%=objectName%>" size="35"></td>
+ <td><i>The MBean javax.management.ObjectName of the MBean you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Attribute</b></td>
+ <td><input type="text" name="attribute" value="<%=attribute%>" size="35"></td>
+ <td><i>The MBean Attribute you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Threshold</b></td>
+ <td><input type="text" name="threshold" size="35" value="<%=threshold%>"></td>
+ <td><i>The value that will trigger an alert when the Comparison Equation is reached for the attribute value</i></td>
+</tr>
+<tr>
+ <td><b>Time Period</b></td>
+ <td><input type="text" name="period" size="35" value="<%=period%>"></td>
+ <td><i>How often should threshold be tested.</i></td>
+</tr>
+<tr>
+ <td><b>Comparison Equation</b></td>
+ <td><select name="compare" id="compare" size="1">
+ <option value="gt" <%=compare.equals("gt") ? "SELECTED" : ""%>>></option>
+ <option value="lt" <%=compare.equals("lt") ? "SELECTED" : ""%>><</option>
+ <option value="eq" <%=compare.equals("eq") ? "SELECTED" : ""%>>=</option>
+ </select>
+ </td>
+ <td><i>Boolean expression to use when testing threshold hit.</i></td>
+</tr>
+<tr>
+ <td><b>Persisted</b></td>
+ <td><input type="checkbox" name="persisted" value="" checked></td>
+ <td><i>Should this monitor be created for next JBoss reboot?</i></td>
+</tr>
+<tr>
+ <td><b>Enable Monitor</b></td>
+ <td><input type="checkbox" name="enabled" value="" <%=enabled%>></td>
+ <td><i>Should this monitor be enabled.</i></td>
+</tr>
+<tr>
+ <td><b>Alerts</b></td>
+ <td>
+<%
+ MBeanServer mbeanServer = MBeanServerLocator.locateJBoss();
+ InstanceOfQueryExp queryExp = null;
+ queryExp = new InstanceOfQueryExp("org.jboss.monitor.alerts.JBossAlertListener");
+ Set alerts = mbeanServer.queryNames(null, queryExp);
+ if (alerts.size() > 0)
+ {
+%>
+ <select name="alerts" id="alerts" size="<%=Integer.toString(alerts.size())%>" multiple>
+<%
+ Iterator it = alerts.iterator();
+ while (it.hasNext())
+ {
+ ObjectName alert = (ObjectName)it.next();
+ String alertName = (String)mbeanServer.getAttribute(alert, "AlertName");
+ String selected = "";
+ if (alertSet != null && alertSet.contains(alert.toString())) selected = "SELECTED";
+%>
+ <option value="<%=alert.toString()%>" <%=selected%>><%=alertName%></option>
+<%
+ }
+ }
+%>
+</select>
+
+ </td>
+ <td><i>Alert Listeners to trigger.</i></td>
+</tr>
+</table>
+<input type="submit" value="Create">
+</form>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createThresholdMonitorSummary.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createThresholdMonitorSummary.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/createThresholdMonitorSummary.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,157 @@
+<%@ page import="javax.management.MBeanServer,
+ org.jboss.mx.util.MBeanServerLocator,
+ org.jboss.mx.util.InstanceOfQueryExp,
+ java.util.Set,
+ java.util.Iterator,
+ javax.management.ObjectInstance,
+ javax.management.ObjectName,
+ java.util.HashSet"%>
+ <%--
+ |
+ | Author: Bill Burke (bill at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%
+ String monitorName = request.getParameter("monitorName");
+ if (monitorName == null) monitorName = "";
+ String objectName = request.getParameter("objectName");
+ if (objectName == null) objectName = "";
+ String attribute = request.getParameter("attribute");
+ if (attribute == null) attribute = "";
+ String threshold = request.getParameter("threshold");
+ if (threshold == null) threshold = "";
+ String period = request.getParameter("period");
+ if (period == null) period = "";
+ String compare = request.getParameter("compare");
+ if (compare == null) compare = "gt";
+ String enabled = request.getParameter("enabled");
+ if (enabled == null) enabled = "";
+ String[] alertStrings = request.getParameterValues("alerts");
+ HashSet alertSet = null;
+ if (alertStrings != null)
+ {
+ alertSet = new HashSet();
+ for (int i = 0; i < alertStrings.length; i++)
+ {
+ alertSet.add(alertStrings[i]);
+ }
+ }
+
+
+
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Server Information</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3>Threshold MBean Monitor Created</h3>
+ <p> </p>
+ <p> </p>
+<table cellspacing="2" cellpadding="2" border="0">
+<tr>
+ <td><b>Monitor Name</b></td>
+ <td><input type="text" name="monitorName" size="35" value="<%=monitorName%>" readonly></td>
+ <td><i>The name of the monitor and how it will be references within web console</i></td>
+</tr>
+<tr>
+ <td><b>Object Name</b></td>
+ <td><input type="text" name="objectName" value="<%=objectName%>" size="35" readonly></td>
+ <td><i>The MBean javax.management.ObjectName of the MBean you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Attribute</b></td>
+ <td><input type="text" name="attribute" value="<%=attribute%>" size="35" readonly></td>
+ <td><i>The MBean Attribute you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Threshold</b></td>
+ <td><input type="text" name="threshold" size="35" value="<%=threshold%>" readonly></td>
+ <td><i>The value that will trigger an alert when the Comparison Equation is reached for the attribute value</i></td>
+</tr>
+<tr>
+ <td><b>Time Period</b></td>
+ <td><input type="text" name="period" size="35" value="<%=period%>" readonly></td>
+ <td><i>How often should threshold be tested.</i></td>
+</tr>
+<tr>
+ <td><b>Comparison Equation</b></td>
+ <td><select name="compare" id="compare" size="1">
+ <option value="gt" <%=compare.equals("gt") ? "SELECTED" : ""%>>></option>
+ <option value="lt" <%=compare.equals("lt") ? "SELECTED" : ""%>><</option>
+ <option value="eq" <%=compare.equals("eq") ? "SELECTED" : ""%>>=</option>
+ </select>
+ </td>
+ <td><i>Boolean expression to use when testing threshold hit.</i></td>
+</tr>
+<tr>
+ <td><b>Enable Monitor</b></td>
+ <td><input type="checkbox" name="enabled" value="" <%=enabled%>></td>
+ <td><i>Should this monitor be enabled.</i></td>
+</tr>
+<tr>
+ <td><b>Alerts</b></td>
+ <td>
+<%
+ MBeanServer mbeanServer = MBeanServerLocator.locateJBoss();
+ InstanceOfQueryExp queryExp = null;
+ queryExp = new InstanceOfQueryExp("org.jboss.monitor.alerts.JBossAlertListener");
+ Set alerts = mbeanServer.queryNames(null, queryExp);
+ if (alerts.size() > 0)
+ {
+%>
+ <select name="alerts" id="alerts" size="<%=Integer.toString(alerts.size())%>" multiple readonly>
+<%
+ Iterator it = alerts.iterator();
+ while (it.hasNext())
+ {
+ ObjectName alert = (ObjectName)it.next();
+ if (alertSet.contains(alert.toString()))
+ {
+ String alertName = (String)mbeanServer.getAttribute(alert, "AlertName");
+%>
+ <option value="<%=alert.toString()%>" ><%=alertName%></option>
+<%
+ }
+ }
+ }
+%>
+</select>
+
+ </td>
+ <td><i>Alert Listeners to trigger.</i></td>
+</tr>
+</table>
+</form>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/css/dtree.css
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/css/dtree.css (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/css/dtree.css 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,34 @@
+/*--------------------------------------------------|
+| dTree 2.05 | www.destroydrop.com/javascript/tree/ |
+|---------------------------------------------------|
+| Copyright (c) 2002-2003 Geir Landrö |
+|--------------------------------------------------*/
+
+.dtree {
+ font-family: Verdana, Geneva, Arial, Helvetica, sans-serif;
+ font-size: 11px;
+ color: #666;
+ white-space: nowrap;
+}
+.dtree img {
+ border: 0px;
+ vertical-align: middle;
+}
+.dtree a {
+ color: #333;
+ text-decoration: none;
+}
+.dtree a.node, .dtree a.nodeSel {
+ white-space: nowrap;
+ padding: 1px 2px 1px 2px;
+}
+.dtree a.node:hover, .dtree a.nodeSel:hover {
+ color: #333;
+ text-decoration: underline;
+}
+.dtree a.nodeSel {
+ background-color: #c0d2ec;
+}
+.dtree .clip {
+ overflow: hidden;
+}
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/css/jboss.css
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/css/jboss.css (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/css/jboss.css 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,229 @@
+body {
+ margin: 13px 0px 10px 0px;
+ background-color: #ffffff;
+ font-size: 10px;
+ font-family: verdana, arial, "sans-serif";
+ color: #606060;
+ }
+img {
+ border: 0px;
+ }
+#header {
+ background-color: #003D6E;
+ width: 100%;
+ height: 80px
+ }
+#header #banner {
+ float: right;
+ margin: 8px 5px 0px 0px;
+ }
+#logo {
+ position: absolute;
+ top: 2px;
+ left: 4px;
+ z-index: 200;
+}
+#navigation_bar {
+ background-color: #f0f0f0;
+ border-bottom: 1px dotted #999999;
+ height: 20px;
+ }
+#items {
+ font-size: 12px;
+ width: 600px;
+ margin: 5px 5px 5px 170px;
+ position: relative;
+ z-index: 300;
+ }
+#items .item {
+ margin-right: 10px;
+ }
+.side_block {
+ margin: 15px 5px 10px 5px;
+ background-color: #fbfbfb;
+ border: 1px solid #f0f0f0;
+ }
+.side_block h3 {
+ font-size: 11px;
+ font-weight: 100;
+ width: 100%;
+ margin: 0px 0px 5px 0px;
+ padding: 4px 4px 4px 10x;
+ background-color: #f0f0f0;
+ }
+.side_block h4 {
+ font-size: 11px;
+ color: #003D6E;
+ font-weight: bold;
+ margin: 10px 5px 4px 5px;
+ }
+.side_block p {
+ margin: 5px 5px 3px 5px;
+ }
+.side_block form {
+ margin: 0px 0px 0px 5px;
+ }
+.side_block #login {
+ font-size: 9px;
+ }
+.side_block p img {
+ text-align: center;
+ }
+#content {
+ width: 90%;
+ margin: 10px auto;
+ }
+#left {
+ float: left;
+ width: 14%;
+ }
+#right {
+ float: right;
+ width: 14%;
+ }
+.content_block {
+ text-align: justify;
+ border: 1px solid #999999;
+ margin: 5px;
+ width: 31%;
+ float: left;
+ }
+.content_block p {
+ margin: 0px 5px 3px 5px;
+ }
+.content_block h3 {
+ font-size: 11px;
+ font-weight: bold;
+ color: #000000;
+ margin: 0px 0px 5px 0px;
+ padding: 4px 4px 4px 4x;
+ text-align: center;
+ background-color: #f0f0f0;
+ border-bottom: 1px solid #999999
+ }
+.content_block h4 {
+ font-size: 11px;
+ color: #003D6E;
+ text-align: left;
+ font-weight: bold;
+ margin: 10px 5px 4px 5px;
+ }
+#footer {
+ clear: both;
+ border-top: 1px dotted #999999;
+ }
+#credits {
+ background-color: #f0f0f0;
+ padding: 5px;
+ text-align: center;
+ }
+#footer_bar {
+ height: 20px;
+ width: 100%;
+ background-color: #003D6E;
+ }
+.hide {
+ display: none;
+ }
+.spacer {
+ clear: both;
+ }
+.spacer hr {
+ display: none;
+ }
+.center {
+ text-align: center;
+ }
+#youcandoit {
+ background-image: url('youcandoit.jpg');
+ background-repeat: repeat-x;
+ height: 165px;
+ margin: 0px 30px;
+ }
+.data_table {
+ font-size: 10px;
+ font-family: verdana, arial, "sans-serif";
+ margin: 5px;
+ border-collapse: collapse;
+}
+.data_table h2 {
+ font-size: 11px;
+ margin: 5px 5px 5px 5px;
+ text-align: center
+}
+.data_table h4 {
+ font-size: 11px;
+ color: #003D6E;
+ margin: 5px 5px 5px 5px;
+ text-align: center
+}
+
+.container {
+ border-top-width: 0px;
+ border-right: 1px solid #CCCCCC;
+ border-left: 1px solid #CCCCCC;
+ border-bottom: 1px solid #CCCCCC;
+ text-align: justify;
+ margin: 5px;
+ float: left;
+}
+
+.container p {
+ font-size: 10px;
+ font-family: verdana, arial, "sans-serif";
+ margin: 0px 5px 3px 5px;
+}
+
+.container h3 {
+ font-size: 11px;
+ font-weight: bold;
+ color: #000000;
+ margin: 0px 0px 5px 0px;
+ padding: 4px 4px 4px 4x;
+ text-align: center;
+ background-color: #f0f0f0;
+ border-bottom: 1px solid #999999
+}
+
+.container h4 {
+ font-size: 11px;
+ color: #003D6E;
+ text-align: left;
+ font-weight: bold;
+ margin: 10px 5px 4px 5px;
+}
+
+.tabSpacer {
+ border-bottom: 1px solid #CCCCCC;
+}
+.tabSpacer p {
+ margin: 0px;
+}
+.tab {
+ border-top: 1px solid #CCCCCC;
+ border-right: 1px solid #CCCCCC;
+ border-left: 1px solid #CCCCCC;
+}
+.tabOff {
+ border-top: 1px solid #CCCCCC;
+ border-right: 1px solid #CCCCCC;
+ border-left: 1px solid #CCCCCC;
+ border-bottom: 1px solid #CCCCCC;
+ background-color: #F0F0F0;
+}
+
+.tab p, .tabOff p {
+ padding: 6px 8px;
+ margin: 0px;
+ font-size: 11px;
+ font-weight: bold;
+
+}
+
+.tab p a, .tabOff p a {
+ text-decoration: none;
+ color: #000000;
+}
+.tab p a:hover, .tabOff p a:hover {
+ color: #666666;
+}
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/dtree.js
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/dtree.js (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/dtree.js 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,347 @@
+/*--------------------------------------------------|
+| dTree 2.05 | www.destroydrop.com/javascript/tree/ |
+|---------------------------------------------------|
+| Copyright (c) 2002-2003 Geir Landrö |
+| |
+| This script can be used freely as long as all |
+| copyright messages are intact. |
+| |
+| Updated: 17.04.2003 |
+|--------------------------------------------------*/
+
+// Node object
+function Node(id, pid, name, url, title, target, icon, iconOpen, open) {
+ this.id = id;
+ this.pid = pid;
+ this.name = name;
+ this.url = url;
+ this.title = title;
+ this.target = target;
+ this.icon = icon;
+ this.iconOpen = iconOpen;
+ this._io = open || false;
+ this._is = false;
+ this._ls = false;
+ this._hc = false;
+ this._ai = 0;
+ this._p;
+};
+
+// Tree object
+function dTree(objName) {
+ this.config = {
+ target : null,
+ folderLinks : true,
+ useSelection : true,
+ useCookies : true,
+ useLines : true,
+ useIcons : true,
+ useStatusText : false,
+ closeSameLevel : false,
+ inOrder : false
+ }
+ this.icon = {
+ root : 'img/base.gif',
+ folder : 'img/folder.gif',
+ folderOpen : 'img/folderopen.gif',
+ node : 'img/page.gif',
+ empty : 'img/empty.gif',
+ line : 'img/line.gif',
+ join : 'img/join.gif',
+ joinBottom : 'img/joinbottom.gif',
+ plus : 'img/plus.gif',
+ plusBottom : 'img/plusbottom.gif',
+ minus : 'img/minus.gif',
+ minusBottom : 'img/minusbottom.gif',
+ nlPlus : 'img/nolines_plus.gif',
+ nlMinus : 'img/nolines_minus.gif'
+ };
+ this.obj = objName;
+ this.aNodes = [];
+ this.aIndent = [];
+ this.root = new Node(-1);
+ this.selectedNode = null;
+ this.selectedFound = false;
+ this.completed = false;
+};
+
+// Adds a new node to the node array
+dTree.prototype.add = function(id, pid, name, url, title, target, icon, iconOpen, open) {
+ this.aNodes[this.aNodes.length] = new Node(id, pid, name, url, title, target, icon, iconOpen, open);
+};
+
+// Open/close all nodes
+dTree.prototype.openAll = function() {
+ this.oAll(true);
+};
+dTree.prototype.closeAll = function() {
+ this.oAll(false);
+};
+
+// Outputs the tree to the page
+dTree.prototype.toString = function() {
+ var str = '<div class="dtree">\n';
+ if (document.getElementById) {
+ if (this.config.useCookies) this.selectedNode = this.getSelected();
+ str += this.addNode(this.root);
+ } else str += 'Browser not supported.';
+ str += '</div>';
+ if (!this.selectedFound) this.selectedNode = null;
+ this.completed = true;
+ return str;
+};
+
+// Creates the tree structure
+dTree.prototype.addNode = function(pNode) {
+ var str = '';
+ var n=0;
+ if (this.config.inOrder) n = pNode._ai;
+ for (n; n<this.aNodes.length; n++) {
+ if (this.aNodes[n].pid == pNode.id) {
+ var cn = this.aNodes[n];
+ cn._p = pNode;
+ cn._ai = n;
+ this.setCS(cn);
+ if (!cn.target && this.config.target) cn.target = this.config.target;
+ if (cn._hc && !cn._io && this.config.useCookies) cn._io = this.isOpen(cn.id);
+ if (!this.config.folderLinks && cn._hc) cn.url = null;
+ if (this.config.useSelection && cn.id == this.selectedNode && !this.selectedFound) {
+ cn._is = true;
+ this.selectedNode = n;
+ this.selectedFound = true;
+ }
+ str += this.node(cn, n);
+ if (cn._ls) break;
+ }
+ }
+ return str;
+};
+
+// Creates the node icon, url and text
+dTree.prototype.node = function(node, nodeId) {
+ var str = '<div class="dTreeNode">' + this.indent(node, nodeId);
+ if (this.config.useIcons) {
+ if (!node.icon) node.icon = (this.root.id == node.pid) ? this.icon.root : ((node._hc) ? this.icon.folder : this.icon.node);
+ if (!node.iconOpen) node.iconOpen = (node._hc) ? this.icon.folderOpen : this.icon.node;
+ if (this.root.id == node.pid) {
+ node.icon = this.icon.root;
+ node.iconOpen = this.icon.root;
+ }
+ str += '<img id="i' + this.obj + nodeId + '" src="' + ((node._io) ? node.iconOpen : node.icon) + '" alt="" />';
+ }
+ if (node.url) {
+ str += '<a id="s' + this.obj + nodeId + '" class="' + ((this.config.useSelection) ? ((node._is ? 'nodeSel' : 'node')) : 'node') + '" href="' + node.url + '"';
+ if (node.title) str += ' title="' + node.title + '"';
+ if (node.target) str += ' target="' + node.target + '"';
+ if (this.config.useStatusText) str += ' onmouseover="window.status=\'' + node.name + '\';return true;" onmouseout="window.status=\'\';return true;" ';
+ if (this.config.useSelection && ((node._hc && this.config.folderLinks) || !node._hc))
+ str += ' onclick="javascript: ' + this.obj + '.s(' + nodeId + ');"';
+ str += '>';
+ }
+ else if ((!this.config.folderLinks || !node.url) && node._hc && node.pid != this.root.id)
+ str += '<a href="javascript: ' + this.obj + '.o(' + nodeId + ');" class="node">';
+ str += node.name;
+ if (node.url || ((!this.config.folderLinks || !node.url) && node._hc)) str += '</a>';
+ str += '</div>';
+ if (node._hc) {
+ str += '<div id="d' + this.obj + nodeId + '" class="clip" style="display:' + ((this.root.id == node.pid || node._io) ? 'block' : 'none') + ';">';
+ str += this.addNode(node);
+ str += '</div>';
+ }
+ this.aIndent.pop();
+ return str;
+};
+
+// Adds the empty and line icons
+dTree.prototype.indent = function(node, nodeId) {
+ var str = '';
+ if (this.root.id != node.pid) {
+ for (var n=0; n<this.aIndent.length; n++)
+ str += '<img src="' + ( (this.aIndent[n] == 1 && this.config.useLines) ? this.icon.line : this.icon.empty ) + '" alt="" />';
+ (node._ls) ? this.aIndent.push(0) : this.aIndent.push(1);
+ if (node._hc) {
+ str += '<a href="javascript: ' + this.obj + '.o(' + nodeId + ');"><img id="j' + this.obj + nodeId + '" src="';
+ if (!this.config.useLines) str += (node._io) ? this.icon.nlMinus : this.icon.nlPlus;
+ else str += ( (node._io) ? ((node._ls && this.config.useLines) ? this.icon.minusBottom : this.icon.minus) : ((node._ls && this.config.useLines) ? this.icon.plusBottom : this.icon.plus ) );
+ str += '" alt="" /></a>';
+ } else str += '<img src="' + ( (this.config.useLines) ? ((node._ls) ? this.icon.joinBottom : this.icon.join ) : this.icon.empty) + '" alt="" />';
+ }
+ return str;
+};
+
+// Checks if a node has any children and if it is the last sibling
+dTree.prototype.setCS = function(node) {
+ var lastId;
+ for (var n=0; n<this.aNodes.length; n++) {
+ if (this.aNodes[n].pid == node.id) node._hc = true;
+ if (this.aNodes[n].pid == node.pid) lastId = this.aNodes[n].id;
+ }
+ if (lastId==node.id) node._ls = true;
+};
+
+// Returns the selected node
+dTree.prototype.getSelected = function() {
+ var sn = this.getCookie('cs' + this.obj);
+ return (sn) ? sn : null;
+};
+
+// Highlights the selected node
+dTree.prototype.s = function(id) {
+ if (!this.config.useSelection) return;
+ var cn = this.aNodes[id];
+ if (cn._hc && !this.config.folderLinks) return;
+ if (this.selectedNode != id) {
+ if (this.selectedNode || this.selectedNode==0) {
+ eOld = document.getElementById("s" + this.obj + this.selectedNode);
+ eOld.className = "node";
+ }
+ eNew = document.getElementById("s" + this.obj + id);
+ eNew.className = "nodeSel";
+ this.selectedNode = id;
+ if (this.config.useCookies) this.setCookie('cs' + this.obj, cn.id);
+ }
+};
+
+// Toggle Open or close
+dTree.prototype.o = function(id) {
+ var cn = this.aNodes[id];
+ this.nodeStatus(!cn._io, id, cn._ls);
+ cn._io = !cn._io;
+ if (this.config.closeSameLevel) this.closeLevel(cn);
+ if (this.config.useCookies) this.updateCookie();
+};
+
+// Open or close all nodes
+dTree.prototype.oAll = function(status) {
+ for (var n=0; n<this.aNodes.length; n++) {
+ if (this.aNodes[n]._hc && this.aNodes[n].pid != this.root.id) {
+ this.nodeStatus(status, n, this.aNodes[n]._ls)
+ this.aNodes[n]._io = status;
+ }
+ }
+ if (this.config.useCookies) this.updateCookie();
+};
+
+// Opens the tree to a specific node
+dTree.prototype.openTo = function(nId, bSelect, bFirst) {
+ if (!bFirst) {
+ for (var n=0; n<this.aNodes.length; n++) {
+ if (this.aNodes[n].id == nId) {
+ nId=n;
+ break;
+ }
+ }
+ }
+ var cn=this.aNodes[nId];
+ if (cn.pid==this.root.id || !cn._p) return;
+ cn._io = true;
+ cn._is = bSelect;
+ if (this.completed && cn._hc) this.nodeStatus(true, cn._ai, cn._ls);
+ if (this.completed && bSelect) this.s(cn._ai);
+ else if (bSelect) this._sn=cn._ai;
+ this.openTo(cn._p._ai, false, true);
+};
+
+// Closes all nodes on the same level as certain node
+dTree.prototype.closeLevel = function(node) {
+ for (var n=0; n<this.aNodes.length; n++) {
+ if (this.aNodes[n].pid == node.pid && this.aNodes[n].id != node.id && this.aNodes[n]._hc) {
+ this.nodeStatus(false, n, this.aNodes[n]._ls);
+ this.aNodes[n]._io = false;
+ this.closeAllChildren(this.aNodes[n]);
+ }
+ }
+}
+
+// Closes all children of a node
+dTree.prototype.closeAllChildren = function(node) {
+ for (var n=0; n<this.aNodes.length; n++) {
+ if (this.aNodes[n].pid == node.id && this.aNodes[n]._hc) {
+ if (this.aNodes[n]._io) this.nodeStatus(false, n, this.aNodes[n]._ls);
+ this.aNodes[n]._io = false;
+ this.closeAllChildren(this.aNodes[n]);
+ }
+ }
+}
+
+// Change the status of a node(open or closed)
+dTree.prototype.nodeStatus = function(status, id, bottom) {
+ eDiv = document.getElementById('d' + this.obj + id);
+ eJoin = document.getElementById('j' + this.obj + id);
+ if (this.config.useIcons) {
+ eIcon = document.getElementById('i' + this.obj + id);
+ eIcon.src = (status) ? this.aNodes[id].iconOpen : this.aNodes[id].icon;
+ }
+ eJoin.src = (this.config.useLines)?
+ ((status)?((bottom)?this.icon.minusBottom:this.icon.minus):((bottom)?this.icon.plusBottom:this.icon.plus)):
+ ((status)?this.icon.nlMinus:this.icon.nlPlus);
+ eDiv.style.display = (status) ? 'block': 'none';
+};
+
+
+// [Cookie] Clears a cookie
+dTree.prototype.clearCookie = function() {
+ var now = new Date();
+ var yesterday = new Date(now.getTime() - 1000 * 60 * 60 * 24);
+ this.setCookie('co'+this.obj, 'cookieValue', yesterday);
+ this.setCookie('cs'+this.obj, 'cookieValue', yesterday);
+};
+
+// [Cookie] Sets value in a cookie
+dTree.prototype.setCookie = function(cookieName, cookieValue, expires, path, domain, secure) {
+ document.cookie =
+ escape(cookieName) + '=' + escape(cookieValue)
+ + (expires ? '; expires=' + expires.toGMTString() : '')
+ + (path ? '; path=' + path : '')
+ + (domain ? '; domain=' + domain : '')
+ + (secure ? '; secure' : '');
+};
+
+// [Cookie] Gets a value from a cookie
+dTree.prototype.getCookie = function(cookieName) {
+ var cookieValue = '';
+ var posName = document.cookie.indexOf(escape(cookieName) + '=');
+ if (posName != -1) {
+ var posValue = posName + (escape(cookieName) + '=').length;
+ var endPos = document.cookie.indexOf(';', posValue);
+ if (endPos != -1) cookieValue = unescape(document.cookie.substring(posValue, endPos));
+ else cookieValue = unescape(document.cookie.substring(posValue));
+ }
+ return (cookieValue);
+};
+
+// [Cookie] Returns ids of open nodes as a string
+dTree.prototype.updateCookie = function() {
+ var str = '';
+ for (var n=0; n<this.aNodes.length; n++) {
+ if (this.aNodes[n]._io && this.aNodes[n].pid != this.root.id) {
+ if (str) str += '.';
+ str += this.aNodes[n].id;
+ }
+ }
+ this.setCookie('co' + this.obj, str);
+};
+
+// [Cookie] Checks if a node id is in a cookie
+dTree.prototype.isOpen = function(id) {
+ var aOpen = this.getCookie('co' + this.obj).split('.');
+ for (var n=0; n<aOpen.length; n++)
+ if (aOpen[n] == id) return true;
+ return false;
+};
+
+// If Push and pop is not implemented by the browser
+if (!Array.prototype.push) {
+ Array.prototype.push = function array_push() {
+ for(var i=0;i<arguments.length;i++)
+ this[this.length]=arguments[i];
+ return this.length;
+ }
+};
+if (!Array.prototype.pop) {
+ Array.prototype.pop = function array_pop() {
+ lastElement = this[this.length-1];
+ this.length = Math.max(this.length-1,0);
+ return lastElement;
+ }
+};
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/EspressoMaker.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/EspressoMaker.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/bean.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/bean.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/beans.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/beans.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/card.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/card.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/container.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/container.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/database.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/database.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/elements32.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/elements32.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/flash.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/flash.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/jboss.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/jboss.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/jndiview.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/jndiview.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/logo.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/logo.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/otherimages.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/otherimages.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/recycle.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/recycle.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/rubiks.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/rubiks.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/server.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/server.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/service.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/service.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/serviceset.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/serviceset.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/servinghand.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/servinghand.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/settings32.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/settings32.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/smallnet.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/smallnet.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/spirale.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/spirale.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/spirale32.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/spirale32.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/starfolder.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/images/starfolder.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/base.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/base.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/cd.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/cd.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/empty.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/empty.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/folder.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/folder.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/folderopen.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/folderopen.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/globe.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/globe.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/imgfolder.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/imgfolder.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/join.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/join.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/joinbottom.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/joinbottom.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/line.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/line.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/minus.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/minus.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/minusbottom.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/minusbottom.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/musicfolder.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/musicfolder.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/nolines_minus.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/nolines_minus.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/nolines_plus.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/nolines_plus.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/page.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/page.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/plus.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/plus.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/plusbottom.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/plusbottom.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/question.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/question.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/trash.gif
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/img/trash.gif
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/index.html
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/index.html (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/index.html 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,19 @@
+<html>
+
+<head>
+<title>Administration Console</title>
+</head>
+
+<frameset cols="30%,*">
+ <frame id="left" name="left" src="applet.jsp" scrolling="no" marginwidth="0" marginheight="0" style="padding-left: 8; padding-right: 0; padding-top: 8; padding-bottom: 0">
+ <frame id="right" name="right" src="ServerInfo.jsp" >
+ <noframes>
+ <body>
+
+ <p>Please use a frame-capable browser.</p>
+
+ </body>
+ </noframes>
+</frameset>
+
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/listActiveAlarmTable.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/listActiveAlarmTable.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/listActiveAlarmTable.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,175 @@
+<%@ page import="
+java.net.URLEncoder,
+java.util.Map,
+javax.management.MBeanServer,
+javax.management.ObjectName,
+javax.management.Notification,
+org.jboss.util.Strings,
+org.jboss.mx.util.MBeanServerLocator,
+org.jboss.monitor.alarm.Alarm,
+org.jboss.monitor.alarm.AlarmHelper,
+org.jboss.monitor.alarm.AlarmNotification,
+org.jboss.monitor.alarm.AlarmTableNotification,
+org.jboss.monitor.services.ActiveAlarmTableMBean
+"%>
+ <%--
+ | Show the ActiveAlarmTable
+ |
+ | Author: Dimitris Andreadis (dimitris at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%
+try
+{
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+ <title>JBoss Management Console - Active Alarm Table</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+ <link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header"> </div>
+ <div id="navigation_bar"/>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3>Active Alarm Table</h3>
+<%
+ MBeanServer server = MBeanServerLocator.locateJBoss();
+ ObjectName target = ActiveAlarmTableMBean.OBJECT_NAME;
+ AlarmTableNotification[] altab = (AlarmTableNotification[])server.invoke(target, "fetchAlarmTable", new Object[] {}, new String[] {});
+
+ // get some statistics from the table
+ Map stats = AlarmHelper.getAlarmTableNotificationStats(altab);
+ Integer stateCleared = (Integer)stats.get(AlarmHelper.getStateAsString(Alarm.STATE_CLEARED));
+ Integer stateChanged = (Integer)stats.get(AlarmHelper.getStateAsString(Alarm.STATE_CHANGED));
+ Integer stateCreated = (Integer)stats.get(AlarmHelper.getStateAsString(Alarm.STATE_CREATED));
+ Integer stateNone = (Integer)stats.get(AlarmHelper.getStateAsString(Alarm.STATE_NONE));
+ Integer severityNormal = (Integer)stats.get(AlarmHelper.getSeverityAsString(Alarm.SEVERITY_NORMAL));
+ Integer severityWarning = (Integer)stats.get(AlarmHelper.getSeverityAsString(Alarm.SEVERITY_WARNING));
+ Integer severityMinor = (Integer)stats.get(AlarmHelper.getSeverityAsString(Alarm.SEVERITY_MINOR));
+ Integer severityMajor = (Integer)stats.get(AlarmHelper.getSeverityAsString(Alarm.SEVERITY_MAJOR));
+ Integer severityCritical = (Integer)stats.get(AlarmHelper.getSeverityAsString(Alarm.SEVERITY_CRITICAL));
+ Integer severityUnknown = (Integer)stats.get(AlarmHelper.getSeverityAsString(Alarm.SEVERITY_UNKNOWN));
+ int statefullCount = altab.length - stateNone.intValue();
+%>
+<p> </p>
+<center>
+ Alarm Count: <%=altab.length%><br>
+ (Stateless: <%=stateNone%>, Statefull: <%=statefullCount%>)<br><br>
+ <table class="data_table">
+ <tr>
+ <th width="50%" align="left">Alarm State</th>
+ <th width="50%" align="left">Alarm Severity</th>
+ </tr>
+ <tr>
+ <td>
+ NONE: <%=stateNone%><br>
+ CREATED: <%=stateCreated%><br>
+ CHANGED: <%=stateChanged%><br>
+ CLEARED: <%=stateCleared%>
+ </td>
+ <td>
+ UNKNOWN: <%=severityUnknown%><br>
+ CRITICAL: <%=severityCritical%><br>
+ MAJOR: <%=severityMajor%><br>
+ MINOR: <%=severityMinor%><br>
+ WARNING: <%=severityWarning%><br>
+ NORMAL: <%=severityNormal%>
+ </td>
+ </tr>
+ </table>
+ <form action="listActiveAlarmTable.jsp" method="post" align="middle">
+ <input type="submit" name="action" value="Refresh Table">
+</form>
+</center>
+<table class="data_table" cellspacing="2" cellpadding="2" border="1" >
+<tr>
+ <th width="150">AlarmInfo</th>
+ <th>NotificationInfo</th>
+</tr>
+<%
+ for (int i = 0; i < altab.length; i++)
+ {
+ AlarmTableNotification atn = altab[i];
+
+ String alarmId = atn.getAlarmId();
+ String severity = AlarmHelper.getSeverityAsString(atn.getSeverity());
+ String alarmState = AlarmHelper.getStateAsString(atn.getAlarmState());
+ boolean ackState = atn.getAckState();
+ long ackTime = atn.getAckTime();
+ String ackUser = atn.getAckUser();
+ String ackSystem = atn.getAckSystem();
+
+ Notification n = (Notification)atn.getUserData();
+ Object source = AlarmNotification.getEffectiveSource(n);
+ String sourceLink = "/jmx-console/HtmlAdaptor?action=inspectMBean&name=" + URLEncoder.encode(source.toString());
+ String type = n.getType();
+ long timeStamp = n.getTimeStamp();
+ long sequenceNumber = n.getSequenceNumber();
+ String message = (n.getMessage() != null) ? Strings.subst("\n", "<br>", n.getMessage()) : "null";
+ String userData = (n.getUserData() != null) ? Strings.subst("\n", "<br>", n.getUserData().toString()) : "null";
+%>
+<tr>
+ <td>
+ alarmId: <font color="navy"><%=alarmId%></font><br><br>
+ severity: <font color="fuchsia"><%=severity%></font><br>
+ alarmState: <font color="fuchsia"><%=alarmState%></font><br><br>
+ ackState: <font color="navy"><%=ackState%></font><br><br>
+ actTime: <font color="navy"><%=ackTime%></font><br>
+ ackUser: <font color="navy"><%=ackUser%></font><br>
+ ackSystem: <font color="navy"><%=ackSystem%></font>
+ <form action="AcknowledgeActiveAlarms" method="post">
+ <input type="hidden" name="alarmId" value="<%=alarmId%>">
+ <input type="submit" name="action" value="Ack">
+ </form>
+ </td>
+ <td>
+ source: <a href="<%=sourceLink%>"><%=source%></a><br>
+ type: <font color="navy"><%=type%></font><br>
+ timeStamp: <font color="navy"><%=timeStamp%></font><br>
+ sequenceNumber: <font color="navy"><%=sequenceNumber%></font><br><br>
+ message: <font color="navy"><%=message%></font><br><br>
+ userData: <font color="navy"><%=userData%></font>
+ </td>
+</tr>
+<%
+ }
+%>
+</table>
+<form action="AcknowledgeActiveAlarms" method="post">
+ <input type="hidden" name="alarmId" value="*">
+ <input type="submit" name="action" value="Acknowledge All Alarms">
+</form>
+<%
+}
+catch (Exception ex)
+{
+ %> ERROR in parsing <%
+ ex.printStackTrace();
+}
+%>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+</center>
+<!-- content end -->
+<hr class="hide"/>
+<!-- footer begin -->
+<div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+</div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/listMonitors.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/listMonitors.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/listMonitors.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,142 @@
+<%@ page import="javax.management.MBeanServer,
+ org.jboss.mx.util.MBeanServerLocator,
+ org.jboss.mx.util.InstanceOfQueryExp,
+ java.util.Set,
+ java.util.Iterator,
+ javax.management.ObjectInstance,
+ javax.management.ObjectName,
+ java.util.HashSet,
+ java.util.ArrayList"%>
+ <%--
+ |
+ | Author: Bill Burke (bill at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%
+try
+{
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Manage Monitor</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3>Monitors and Monitor Status</h3>
+ <p> </p>
+<table cellspacing="2" cellpadding="2" border="1">
+<tr>
+ <td><b>Status</b></td>
+ <td><b>Monitor Name</b></td>
+ <td><b>Observed MBean</b></td>
+ <td><b>Observed Attribute</b></td>
+ <td> </td>
+</tr>
+<%
+ MBeanServer mbeanServer = MBeanServerLocator.locateJBoss();
+ InstanceOfQueryExp queryExp = null;
+ queryExp = new InstanceOfQueryExp("org.jboss.monitor.JBossMonitorMBean");
+ Set monitors = mbeanServer.queryNames(null, queryExp);
+ Iterator mbeans = monitors.iterator();
+ boolean someAlertSet = false;
+ while (mbeans.hasNext())
+ {
+ ObjectName moname = (ObjectName)mbeans.next();
+ String monitorName = (String)mbeanServer.getAttribute(moname, "MonitorName");
+ ObjectName observedObject = (ObjectName)mbeanServer.getAttribute(moname, "ObservedObject");
+ String attribute = (String)mbeanServer.getAttribute(moname, "ObservedAttribute");
+ boolean enabled = ((Boolean)mbeanServer.getAttribute(moname, "Enabled")).booleanValue();
+
+ Object[] args = {"monitors", monitorName, "-service.xml"};
+ String[] signature = {"java.lang.String", "java.lang.String", "java.lang.String"};
+ Object rtn = mbeanServer.invoke(new ObjectName("jboss.admin:service=DeploymentFileRepository"), "isStored", args, signature);
+ boolean persisted = ((Boolean)rtn).booleanValue();
+
+ Object[] nullArgs = {};
+ String[] nullSig = {};
+ boolean alerted = ((Boolean)mbeanServer.invoke(moname, "alerted", nullArgs, nullSig)).booleanValue();
+ if (alerted) someAlertSet = true;
+ String color = "black";
+ if (!enabled) color = "grey";
+ String status = "";
+ if (alerted)
+ {
+ status = "<font color=\"red\">ALERT</font>";
+ }
+ else if (!enabled)
+ {
+ status = "<font color=\"grey\"><i>disabled</i></font>";
+ }
+ else
+ {
+ status = "<font color=\"green\">OK</font>";
+ }
+ String link = null;
+ if (persisted)
+ {
+ link = "manageThresholdMonitor.jsp?monitorObjectName=" + java.net.URLEncoder.encode(moname.toString());
+ }
+ else
+ {
+ link = "/jmx-console/HtmlAdaptor?action=inspectMBean&name=" + java.net.URLEncoder.encode(moname.toString());
+ }
+ String observedMbeanLink = "/jmx-console/HtmlAdaptor?action=inspectMBean&name=" + java.net.URLEncoder.encode(observedObject.toString());
+%>
+<tr>
+ <td><%=status%></td>
+ <td><font color="<%=color%>"><%=monitorName%></font></td>
+ <td><font color="<%=color%>"><a href="<%=observedMbeanLink%>"><%=observedObject.toString()%></a></font></td>
+ <td><font color="<%=color%>"><%=attribute%></font></td>
+ <td><a href="<%=link%>">manage</a></td>
+</tr>
+<%
+ }
+ %>
+</table>
+<%
+ if (someAlertSet)
+ {
+%>
+<form action="ClearMonitorAlerts" method="post">
+<input type="submit" name="action" value="Clear All Alerts">
+</form>
+<%
+ }
+}
+catch (Exception ex)
+{
+ %> ERROR in parsing <%
+ ex.printStackTrace();
+}
+%>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageSnapshot.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageSnapshot.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageSnapshot.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,132 @@
+<%@ page import="javax.management.MBeanServer,
+ org.jboss.mx.util.MBeanServerLocator,
+ org.jboss.mx.util.InstanceOfQueryExp,
+ java.util.Set,
+ java.util.Iterator,
+ javax.management.ObjectInstance,
+ javax.management.ObjectName,
+ java.util.HashSet,
+ java.util.ArrayList"%>
+ <%--
+ |
+ | Author: Bill Burke (bill at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%
+try
+{
+ MBeanServer mbeanServer = MBeanServerLocator.locateJBoss();
+ String error = (String)request.getAttribute("error");
+ ObjectName moname = null;
+ String monitorName = null;
+ String monitorObjectName = request.getParameter("monitorObjectName");
+ /*
+ if (monitorObjectName == null) // if we're being routed via
+ {
+ monitorName = (String)request.getAttribute("monitorName");
+ moname = new ObjectName("jboss.snapshot:name=" + monitorName);
+ }
+ */
+ moname = new ObjectName(monitorObjectName);
+ monitorName = (String)mbeanServer.getAttribute(moname, "MonitorName");
+ ObjectName observedObject = (ObjectName)mbeanServer.getAttribute(moname, "ObservedObject");
+ String attribute = (String)mbeanServer.getAttribute(moname, "ObservedAttribute");
+ Long period = (Long)mbeanServer.getAttribute(moname, "Period");
+ boolean recording = ((Boolean)mbeanServer.getAttribute(moname, "Recording")).booleanValue();
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Manage Snapshot</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3>Manage Snapshot</h3>
+ <p> </p>
+<%
+ if (error != null)
+ {
+%>
+ <p><font color="red" size ="-2"><%=error%></font> </p>
+<%
+ }
+%>
+<form action="ManageSnapshot" method="post">
+<input type="hidden" name="monitorObjectName" value="<%=moname.toString()%>">
+<table cellspacing="2" cellpadding="2" border="0">
+<tr>
+ <td><b>Monitor Name</b></td>
+ <td><input type="text" name="monitorName" size="35" value="<%=monitorName%>" readonly></td>
+ <td><i>The name of the monitor and how it will be references within web console</i></td>
+</tr>
+<tr>
+ <td><b>Monitor's Object Name</b></td>
+ <td><input type="text" name="monitorObjectName" size="35" value="<%=monitorObjectName%>" readonly></td>
+ <td><i>The MBean javax.management.ObjectName</i></td>
+</tr>
+<tr>
+ <td><b>Object Name</b></td>
+ <td><input type="text" name="objectName" value="<%=observedObject.toString()%>" size="35" readonly></td>
+ <td><i>The MBean javax.management.ObjectName of the MBean you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Attribute</b></td>
+ <td><input type="text" name="attribute" value="<%=attribute%>" size="35" readonly></td>
+ <td><i>The MBean Attribute you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Time Period</b></td>
+ <td><input type="text" name="period" size="35" value="<%=period%>" readonly></td>
+ <td><i>How often should threshold be tested.</i></td>
+</tr>
+</table>
+<% if (recording)
+ {
+%>
+<input type="submit" name="action" value="Stop Snapshot">
+<% } else {%>
+<input type="submit" name="action" value="Start Snapshot">
+<% } %>
+<input type="submit" name="action" value="Graph Dataset">
+<input type="submit" name="action" value="Clear Dataset">
+<input type="submit" name="action" value="Show Dataset">
+<input type="submit" name="action" value="Remove Snapshot">
+</form>
+<%
+}
+catch (Exception ex)
+{
+ %> ERROR <%
+ ex.printStackTrace();
+}
+%>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageStringThresholdMonitor.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageStringThresholdMonitor.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageStringThresholdMonitor.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,199 @@
+<%@ page import="javax.management.MBeanServer,
+ org.jboss.mx.util.MBeanServerLocator,
+ org.jboss.mx.util.InstanceOfQueryExp,
+ java.util.Set,
+ java.util.Iterator,
+ javax.management.ObjectInstance,
+ javax.management.ObjectName,
+ java.util.HashSet,
+ java.util.ArrayList"%>
+ <%--
+ |
+ | Author: Bill Burke (bill at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%
+try
+{
+ MBeanServer mbeanServer = MBeanServerLocator.locateJBoss();
+ String error = (String)request.getAttribute("error");
+ String monitorObjectName = request.getParameter("monitorObjectName");
+ ObjectName moname = new ObjectName(monitorObjectName);
+ String monitorName = (String)mbeanServer.getAttribute(moname, "MonitorName");
+ ObjectName observedObject = (ObjectName)mbeanServer.getAttribute(moname, "ObservedObject");
+ String attribute = (String)mbeanServer.getAttribute(moname, "ObservedAttribute");
+ String threshold = (String)mbeanServer.getAttribute(moname, "Threshold");
+ Long period = (Long)mbeanServer.getAttribute(moname, "Period");
+ boolean equality = ((Boolean)mbeanServer.getAttribute(moname, "EqualityTriggersAlert")).booleanValue();
+ boolean enabled = ((Boolean)mbeanServer.getAttribute(moname, "Enabled")).booleanValue();
+ ArrayList alerts = (ArrayList)mbeanServer.getAttribute(moname, "AlertListeners");
+
+ Object[] args = {"monitors", monitorName, "-service.xml"};
+ String[] signature = {"java.lang.String", "java.lang.String", "java.lang.String"};
+ Object rtn = mbeanServer.invoke(new ObjectName("jboss.admin:service=DeploymentFileRepository"), "isStored", args, signature);
+ boolean persisted = ((Boolean)rtn).booleanValue();
+
+ Object[] nullArgs = {};
+ String[] nullSig = {};
+ boolean alerted = ((Boolean)mbeanServer.invoke(moname, "alerted", nullArgs, nullSig)).booleanValue();
+ Object triggeredValue = null;
+ if (alerted) triggeredValue = mbeanServer.getAttribute(moname, "TriggeredAttributeValue");
+ String color = alerted ? "red" : "green";
+
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Manage Monitor</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3><font color="<%=color%>">Manage String MBean Monitor</font></h3>
+ <p> </p>
+<%
+ if (error != null)
+ {
+%>
+ <p><font color="red" size ="-2"><%=error%></font> </p>
+<%
+ }
+%>
+<form action="ManageStringThresholdMonitor" method="post">
+<input type="hidden" name="monitorObjectName" value="<%=moname.toString()%>">
+<table cellspacing="2" cellpadding="2" border="0">
+<tr>
+ <td><b>Monitor Name</b></td>
+ <td><input type="text" name="monitorName" size="35" value="<%=monitorName%>" readonly></td>
+ <td><i>The name of the monitor and how it will be references within web console</i></td>
+</tr>
+<tr>
+ <td><b>Monitor's Object Name</b></td>
+ <td><input type="text" name="monitorObjectName" size="35" value="<%=monitorObjectName%>" readonly></td>
+ <td><i>The MBean javax.management.ObjectName</i></td>
+</tr>
+<tr>
+ <td><b>Object Name</b></td>
+ <td><input type="text" name="objectName" value="<%=observedObject.toString()%>" size="35" readonly></td>
+ <td><i>The MBean javax.management.ObjectName of the MBean you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Attribute</b></td>
+ <td><input type="text" name="attribute" value="<%=attribute%>" size="35" readonly></td>
+ <td><i>The MBean Attribute you are monitoring</i></td>
+</tr>
+<%
+ if (alerted)
+ {
+%>
+<tr>
+ <td><font color="red"><b>Triggered Value</b></font></td>
+ <td><input type="text" name="trigger" value="<%=triggeredValue.toString()%>" size="35" readonly></td>
+ <td><i>The attribute value the triggered the threshold.</i></td>
+</tr>
+<% } %>
+<tr>
+ <td><b>Threshold</b></td>
+ <td><input type="text" name="threshold" size="35" value="<%=threshold%>"></td>
+ <td><i>The value that will trigger an alert when the Comparison Equation is reached for the attribute value</i></td>
+</tr>
+<tr>
+ <td><b>Time Period</b></td>
+ <td><input type="text" name="period" size="35" value="<%=period%>"></td>
+ <td><i>How often should threshold be tested.</i></td>
+</tr>
+<tr>
+ <td><b>Persist Changes</b></td>
+ <td><input type="checkbox" name="persisted" value="" checked></td>
+ <td><i>Should changes be reflected in deployment file.</i></td>
+</tr>
+<tr>
+ <td><b>Equality Trigger</b></td>
+ <td><input type="checkbox" name="equality" value="" <%=equality ? "checked" : ""%>></td>
+ <td><i>Uncheck this box if you want an alert to trigger when attribute changes from threshold value</i></td>
+</tr>
+<tr>
+ <td><b>Enable Monitor</b></td>
+ <td><input type="checkbox" name="enabled" value="" <%=enabled ? "checked" : ""%>></td>
+ <td><i>Should this monitor be enabled.</i></td>
+</tr>
+<tr>
+ <td><b>Alerts</b></td>
+ <td>
+<%
+ InstanceOfQueryExp queryExp = null;
+ queryExp = new InstanceOfQueryExp("org.jboss.monitor.alerts.JBossAlertListener");
+ Set allAlertTypes = mbeanServer.queryNames(null, queryExp);
+
+ if (allAlertTypes.size() > 0)
+ {
+%>
+ <select name="alerts" id="alerts" size="<%=Integer.toString(allAlertTypes.size())%>" multiple>
+<%
+ Iterator it = allAlertTypes.iterator();
+ while (it.hasNext())
+ {
+ ObjectName alert = (ObjectName)it.next();
+ String alertName = (String)mbeanServer.getAttribute(alert, "AlertName");
+ String selected = "";
+ if (alerts != null && alerts.contains(alert)) selected = "SELECTED";
+%>
+ <option value="<%=alert.toString()%>" <%=selected%>><%=alertName%></option>
+<%
+ }
+ }
+%>
+</select>
+
+ </td>
+ <td><i>Alert Listeners to trigger.</i></td>
+</tr>
+</table>
+<input type="submit" name="action" value="Update Monitor">
+<input type="submit" name="action" value="Remove Monitor">
+<%
+ if (alerted)
+ {
+%>
+<input type="submit" name="action" value="Clear Alert">
+<%
+ }
+%>
+</form>
+<%
+}
+catch (Exception ex)
+{
+ %> ERROR in parsing <%
+ ex.printStackTrace();
+}
+%>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageThresholdMonitor.jsp
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageThresholdMonitor.jsp (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/manageThresholdMonitor.jsp 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,204 @@
+<%@ page import="javax.management.MBeanServer,
+ org.jboss.mx.util.MBeanServerLocator,
+ org.jboss.mx.util.InstanceOfQueryExp,
+ java.util.Set,
+ java.util.Iterator,
+ javax.management.ObjectInstance,
+ javax.management.ObjectName,
+ java.util.HashSet,
+ java.util.ArrayList"%>
+ <%--
+ |
+ | Author: Bill Burke (bill at jboss.org)
+ |
+ | Distributable under LGPL license.
+ | See terms of license at gnu.org.
+ +--%>
+<%
+try
+{
+ MBeanServer mbeanServer = MBeanServerLocator.locateJBoss();
+ String error = (String)request.getAttribute("error");
+ String monitorObjectName = request.getParameter("monitorObjectName");
+ ObjectName moname = new ObjectName(monitorObjectName);
+ String monitorName = (String)mbeanServer.getAttribute(moname, "MonitorName");
+ ObjectName observedObject = (ObjectName)mbeanServer.getAttribute(moname, "ObservedObject");
+ String attribute = (String)mbeanServer.getAttribute(moname, "ObservedAttribute");
+ String threshold = (String)mbeanServer.getAttribute(moname, "Threshold");
+ Long period = (Long)mbeanServer.getAttribute(moname, "Period");
+ int compare = ((Integer)mbeanServer.getAttribute(moname, "CompareTo")).intValue();
+ boolean enabled = ((Boolean)mbeanServer.getAttribute(moname, "Enabled")).booleanValue();
+ ArrayList alerts = (ArrayList)mbeanServer.getAttribute(moname, "AlertListeners");
+
+ Object[] args = {"monitors", monitorName, "-service.xml"};
+ String[] signature = {"java.lang.String", "java.lang.String", "java.lang.String"};
+ Object rtn = mbeanServer.invoke(new ObjectName("jboss.admin:service=DeploymentFileRepository"), "isStored", args, signature);
+ boolean persisted = ((Boolean)rtn).booleanValue();
+
+ Object[] nullArgs = {};
+ String[] nullSig = {};
+ boolean alerted = ((Boolean)mbeanServer.invoke(moname, "alerted", nullArgs, nullSig)).booleanValue();
+ Object triggeredValue = null;
+ if (alerted) triggeredValue = mbeanServer.getAttribute(moname, "TriggeredAttributeValue");
+ String color = alerted ? "red" : "green";
+
+%>
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>JBoss Management Console - Manage Monitor</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<link rel="StyleSheet" href="css/jboss.css" type="text/css"/>
+</head>
+<body>
+<!-- header begin -->
+ <img src="images/logo.gif" alt="JBoss" id="logo" width="226" height="105" />
+ <div id="header">
+ </div>
+ <div id="navigation_bar">
+ </div>
+<!-- header end -->
+<hr class="hide"/>
+ <center>
+ <div id="content">
+ <div class="content_block" style="width: 100%; height: 247">
+ <h3><font color="<%=color%>">Manage Threshold MBean Monitor</font></h3>
+ <p> </p>
+<%
+ if (error != null)
+ {
+%>
+ <p><font color="red" size ="-2"><%=error%></font> </p>
+<%
+ }
+%>
+<form action="ManageThresholdMonitor" method="post">
+<input type="hidden" name="monitorObjectName" value="<%=moname.toString()%>">
+<table cellspacing="2" cellpadding="2" border="0">
+<tr>
+ <td><b>Monitor Name</b></td>
+ <td><input type="text" name="monitorName" size="35" value="<%=monitorName%>" readonly></td>
+ <td><i>The name of the monitor and how it will be references within web console</i></td>
+</tr>
+<tr>
+ <td><b>Monitor's Object Name</b></td>
+ <td><input type="text" name="monitorObjectName" size="35" value="<%=monitorObjectName%>" readonly></td>
+ <td><i>The MBean javax.management.ObjectName</i></td>
+</tr>
+<tr>
+ <td><b>Object Name</b></td>
+ <td><input type="text" name="objectName" value="<%=observedObject.toString()%>" size="35" readonly></td>
+ <td><i>The MBean javax.management.ObjectName of the MBean you are monitoring</i></td>
+</tr>
+<tr>
+ <td><b>Attribute</b></td>
+ <td><input type="text" name="attribute" value="<%=attribute%>" size="35" readonly></td>
+ <td><i>The MBean Attribute you are monitoring</i></td>
+</tr>
+<%
+ if (alerted)
+ {
+%>
+<tr>
+ <td><font color="red"><b>Triggered Value</b></font></td>
+ <td><input type="text" name="trigger" value="<%=triggeredValue.toString()%>" size="35" readonly></td>
+ <td><i>The attribute value the triggered the threshold.</i></td>
+</tr>
+<% } %>
+<tr>
+ <td><b>Threshold</b></td>
+ <td><input type="text" name="threshold" size="35" value="<%=threshold%>"></td>
+ <td><i>The value that will trigger an alert when the Comparison Equation is reached for the attribute value</i></td>
+</tr>
+<tr>
+ <td><b>Time Period</b></td>
+ <td><input type="text" name="period" size="35" value="<%=period%>"></td>
+ <td><i>How often should threshold be tested.</i></td>
+</tr>
+<tr>
+ <td><b>Comparison Equation</b></td>
+ <td><select name="compare" id="compare" size="1">
+ <option value="gt" <%=compare == -1 ? "SELECTED" : ""%>>></option>
+ <option value="lt" <%=compare == 1 ? "SELECTED" : ""%>><</option>
+ <option value="eq" <%=compare == 0 ? "SELECTED" : ""%>>=</option>
+ </select>
+ </td>
+ <td><i>Boolean expression to use when testing threshold hit.</i></td>
+</tr>
+<tr>
+ <td><b>Persist Changes</b></td>
+ <td><input type="checkbox" name="persisted" value="" checked></td>
+ <td><i>Should changes be reflected in deployment file.</i></td>
+</tr>
+<tr>
+ <td><b>Enable Monitor</b></td>
+ <td><input type="checkbox" name="enabled" value="" <%=enabled ? "checked" : ""%>></td>
+ <td><i>Should this monitor be enabled.</i></td>
+</tr>
+<tr>
+ <td><b>Alerts</b></td>
+ <td>
+<%
+ InstanceOfQueryExp queryExp = null;
+ queryExp = new InstanceOfQueryExp("org.jboss.monitor.alerts.JBossAlertListener");
+ Set allAlertTypes = mbeanServer.queryNames(null, queryExp);
+
+ if (allAlertTypes.size() > 0)
+ {
+%>
+ <select name="alerts" id="alerts" size="<%=Integer.toString(allAlertTypes.size())%>" multiple>
+<%
+ Iterator it = allAlertTypes.iterator();
+ while (it.hasNext())
+ {
+ ObjectName alert = (ObjectName)it.next();
+ String alertName = (String)mbeanServer.getAttribute(alert, "AlertName");
+ String selected = "";
+ if (alerts != null && alerts.contains(alert)) selected = "SELECTED";
+%>
+ <option value="<%=alert.toString()%>" <%=selected%>><%=alertName%></option>
+<%
+ }
+ }
+%>
+</select>
+
+ </td>
+ <td><i>Alert Listeners to trigger.</i></td>
+</tr>
+</table>
+<input type="submit" name="action" value="Update Monitor">
+<input type="submit" name="action" value="Remove Monitor">
+<%
+ if (alerted)
+ {
+%>
+<input type="submit" name="action" value="Clear Alert">
+<%
+ }
+%>
+</form>
+<%
+}
+catch (Exception ex)
+{
+ %> ERROR in parsing <%
+ ex.printStackTrace();
+}
+%>
+ </div>
+ <div class="spacer"><hr/></div>
+ </div>
+ </center>
+<!-- content end -->
+
+<hr class="hide"/>
+<!-- footer begin -->
+ <div id="footer">
+ <div id="credits">JBoss™ Management Console</div>
+ <div id="footer_bar"> </div>
+ </div>
+<!-- footer end -->
+</body>
+</html>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/xform.xsl
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/xform.xsl (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/management/console-mgr.sar/web-console.war/xform.xsl 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,96 @@
+<?xml version="1.0"?>
+
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ version="1.0">
+
+ <!-- Output method -->
+ <xsl:output encoding="iso-8859-1"
+ indent="no"/>
+
+ <xsl:template match="status">
+ <html>
+ <head>
+ <TITLE>Tomcat Status</TITLE>
+ <STYLE type="text/css">
+ body, table, tr, td, a, div, span {
+ vertical-align : top;
+ }
+ </STYLE>
+ </head>
+ <body>
+ <div style='font-size:20px;'>Tomcat Status</div>
+
+ <xsl:apply-templates select="jvm"/>
+ <xsl:apply-templates select="connector"/>
+ </body>
+ </html>
+ </xsl:template>
+
+ <xsl:template match="jvm">
+ <xsl:apply-templates select="memory"/>
+ </xsl:template>
+
+ <xsl:template match="memory">
+ <table><tr>
+ <td><b>JVM:</b></td>
+ <td><b>free:</b> <xsl:value-of select="@free"/></td>
+ <td><b>total:</b> <xsl:value-of select="@total"/></td>
+ <td><b>max:</b> <xsl:value-of select="@max"/></td>
+ </tr>
+ </table><hr />
+ </xsl:template>
+
+ <xsl:template match="connector">
+ <b>Connector -- </b> <xsl:value-of select="@name"/><br />
+
+ <xsl:apply-templates select="threadInfo"/>
+ <xsl:apply-templates select="requestInfo"/>
+ <xsl:apply-templates select="workers"/>
+ </xsl:template>
+
+ <xsl:template match="threadInfo">
+ <table><tr>
+ <td><b>threadInfo </b></td>
+ <td><b>maxThreads:</b> <xsl:value-of select="@maxThreads"/></td>
+ <td><b>minSpareThreads:</b> <xsl:value-of select="@minSpareThreads"/></td>
+ <td><b>maxSpareThreads:</b> <xsl:value-of select="@maxSpareThreads"/></td>
+ <td><b>currentThreadCount:</b> <xsl:value-of select="@currentThreadCount"/></td>
+ <td><b>currentThreadsBusy:</b> <xsl:value-of select="@currentThreadsBusy"/></td>
+ </tr>
+ </table><hr />
+ </xsl:template>
+
+ <xsl:template match="requestInfo">
+ <table><tr>
+ <td><b>requestInfo </b></td>
+ <td><b>maxTime:</b> <xsl:value-of select="@maxTime"/></td>
+ <td><b>processingTime:</b> <xsl:value-of select="@processingTime"/></td>
+ <td><b>requestCount:</b> <xsl:value-of select="@requestCount"/></td>
+ <td><b>errorCount:</b> <xsl:value-of select="@errorCount"/></td>
+ <td><b>bytesReceived:</b> <xsl:value-of select="@bytesReceived"/></td>
+ <td><b>bytesSent:</b> <xsl:value-of select="@bytesSent"/></td>
+ </tr>
+ </table><hr />
+ </xsl:template>
+
+ <xsl:template match="workers">
+ <table>
+ <tr><th>Stage</th><th>Time</th><th>B Sent</th><th>B Recv</th><th>Client</th><th>VHost</th><th>Request</th></tr>
+ <xsl:apply-templates select="worker"/>
+
+ </table><hr />
+ </xsl:template>
+
+ <xsl:template match="worker">
+ <tr>
+ <td><xsl:value-of select="@stage"/></td>
+ <td><xsl:value-of select="@requestProcessingTime"/></td>
+ <td><xsl:value-of select="@requestBytesSent"/></td>
+ <td><xsl:value-of select="@requestBytesReceived"/></td>
+ <td><xsl:value-of select="@remoteAddr"/></td>
+ <td><xsl:value-of select="@virtualHost"/></td>
+ <td><xsl:value-of select="@method"/> <xsl:value-of select="@currentUri"/>?<xsl:value-of select="@currentQueryString"/> <xsl:value-of select="@protocol"/></td>
+ </tr>
+ </xsl:template>
+
+</xsl:stylesheet>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/monitoring-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/monitoring-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/monitoring-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,143 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- $Id: monitoring-service.xml 46248 2006-07-13 15:03:17Z dimitris $ -->
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- User Service Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<server>
+
+ <mbean code="org.jboss.monitor.alerts.ConsoleAlertListener"
+ name="jboss.alerts:service=ConsoleAlertListener">
+ <attribute name="MessageTemplate"><![CDATA[%(MONITOR_NAME) was triggered for attribute %(ATTRIBUTE).]]></attribute>
+ <attribute name="AlertName">Console Alert</attribute>
+ </mbean>
+
+<!-- Enable after filling in correct to, from, and reply to
+
+ <mbean code="org.jboss.monitor.alerts.EmailAlertListener"
+ name="jboss.alerts:service=EmailAlertListener">
+ <depends>jboss:service=Mail</depends>
+ <attribute name="MessageTemplate"><![CDATA[%(MONITOR_NAME) was triggered for attribute %(ATTRIBUTE).]]></attribute>
+ <attribute name="AlertName">Email Alert</attribute>
+ <attribute name="To">somebody at somewhere.org</attribute>
+ <attribute name="From">noreply at nowhere.org</attribute>
+ <attribute name="ReplyTo">noreply at nowhere.org</attribute>
+ <attribute name="SubjectTemplate"><![CDATA[[jboss-alert] %(MONITOR_NAME)]]></attribute>
+ </mbean>
+-->
+
+<!--
+ Example of listening for notifications from JBoss monitors.
+
+ The SubscriptionList attribute provides the specification to which
+ MBeans to subscribe for notifications and for what notification types.
+
+ The DynamicSubscriptions attribute is used to indicate whether to monitor
+ the MBeanServer for new MBeans and subscribe to them if the subscription
+ specification matches.
+
+ The NotificationListener attribute can be set to indicate an external
+ MBean as the receiver of the Notifications.
+
+ The LogLevel attribute can be set to indicate the level to use for
+ logging the received notification, e.g. "WARN", "INFO", "DEBUG", etc.
+-->
+<!--
+ <mbean code="org.jboss.monitor.services.NotificationListener"
+ name="jboss.jmx:service=NotificationListener">
+
+ <attribute name="DynamicSubscriptions">true</attribute>
+ <attribute name="NotificationListener"></attribute>
+ <attribute name="SubscriptionList">
+ <subscription-list>
+ <mbean name="jboss.monitor:*">
+ <notification type="JBOSS_MONITOR_NOTIFICATION"/>
+ </mbean>
+ </subscription-list>
+ </attribute>
+
+ </mbean>
+-->
+
+<!--
+ MemoryMonitor monitors the free JVM memory and emits JMX Notifications
+ (org.jboss.monitor.alarm.AlarmNotification) when certain thresholds
+ are crossed.
+
+ The following attributes may be set:
+
+ FreeMemoryWarningThreshold
+ - e.g. 1048576, or 1000K, or 1M
+ FreeMemoryCriticalThreshold
+ - like above, must be lower
+ SamplingPeriod
+ - e.g. 5000, or 5sec.
+ TriggeringWarningMeasurements
+ - number of measurements in the warning area to trigger a notification
+
+ AlarmNotification carries alarmState and alarmSeverity.
+ alarmSeverity takes the values NORMAL, WARNING, CRITICAL for this monitor.
+ See org.jboss.monitor.alarm.Alarm
+-->
+<!--
+ <mbean code="org.jboss.monitor.services.MemoryMonitor"
+ name="jboss.monitor:service=MemoryMonitor">
+
+ <attribute name="FreeMemoryWarningThreshold">95M</attribute>
+ <attribute name="FreeMemoryCriticalThreshold">80M</attribute>
+ </mbean>
+-->
+
+<!--
+ Example of using the TimerService wrapper to configure a
+ javax.management.timer.Timer mbean, to produce heartbeat
+ notifications.
+
+ Attributes to configure:
+
+ NotificationType
+ - The type of the produced javax.management.timer.TimerNotification
+ Notification Message
+ - The string message to carry in the produced notification
+ Timer Period
+ - Every how often to emit notifications, e.g. 500msec, 10sec, 5min, 1h;
+ - a zero value will produce just one notification
+ Repeatitions
+ - How many timer notifications to emit when the period is not zero;
+ - a zero value produces infinite notifications
+ FixedRate
+ - Whether the periodic notification should be produced at
+ - FixedRate (true) or FixedDelay (false, default)
+ TimerMBean
+ - The ObjectName of the JMX Timer to configure, combined with a dependency
+
+ If you want to see/log the emitted notifications, you can configure
+ a NotificationListener as follows:
+
+ <mbean code="org.jboss.monitor.services.NotificationListener"
+ name="jboss.monitor:service=NotificationListener">
+ <attribute name="SubscriptionList">
+ <subscription-list>
+ <mbean name="jboss.monitor:name=Heartbeat,type=Timer"/>
+ </subscription-list>
+ </attribute>
+ </mbean>
+-->
+<!--
+ <mbean code="org.jboss.monitor.services.TimerService"
+ name="jboss.monitor:name=Heartbeat,type=TimerService">
+ <attribute name="NotificationType">jboss.monitor.heartbeat</attribute>
+ <attribute name="NotificationMessage">JBoss is alive!</attribute>
+ <attribute name="TimerPeriod">5sec</attribute>
+ <depends optional-attribute-name="TimerMBean">
+ <mbean code="javax.management.timer.Timer"
+ name="jboss.monitor:name=Heartbeat,type=Timer"/>
+ </depends>
+ </mbean>
+-->
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/properties-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/properties-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/properties-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE server>
+<!-- $Id: properties-service.xml 16662 2003-08-27 04:38:22Z patriot1burke $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- PropertyEditorManager Service -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | Allows access to the PropertyEditorManager, which is used when setting
+ | MBean attribute values from configuration.
+ -->
+
+ <mbean code="org.jboss.varia.property.PropertyEditorManagerService"
+ name="jboss:type=Service,name=PropertyEditorManager">
+
+ <!--
+ | Register and editor for each of the type_name=editor_type_name listed
+ | in properties file style convetion.
+
+ <attribute name="Editors">
+ java.net.URL=my.project.editors.URLPropertyEditor
+ </attribute>
+
+ -->
+
+ </mbean>
+
+
+ <!-- ==================================================================== -->
+ <!-- System Properties Service -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | Allows rich access to system properties.
+ -->
+
+ <mbean code="org.jboss.varia.property.SystemPropertiesService"
+ name="jboss:type=Service,name=SystemProperties">
+
+ <!--
+ | Load properties from each of the given comma seperated URLs
+
+ <attribute name="URLList">
+ http://somehost/some-location.properties,
+ ./conf/somelocal.properties
+ </attribute>
+
+ -->
+
+ <!--
+ | Set raw properties file style properties.
+
+ <attribute name="Properties">
+
+ my.project.property=This is the value of my property
+ my.project.anotherProperty=This is the value of my other property
+
+ </attribute>
+
+ -->
+
+ </mbean>
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/quartz-ra.rar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/quartz-ra.rar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/schedule-manager-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/schedule-manager-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/schedule-manager-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,119 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: schedule-manager-service.xml 59789 2007-01-18 17:30:15Z dimitris at jboss.org $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Scheduler Service -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | JDK5 javax.management.timer.Timer appears to be using a single
+ | threaded implementation for executing scheduled tasks.
+ | If you want to revert to the JBossMX timer implementation that
+ | uses a dynamically extensible thread pool to execute scheduled
+ | tasks, uncomment the JBossTimer service below. The Scheduler
+ | service will use this, instead of creating a new Timer.
+ - ->
+ <mbean code="org.jboss.mx.timer.JBossTimer"
+ name="jboss:service=Timer">
+ </mbean>
+ <!- - -->
+
+ <!--
+ | This MBean is an example of a Schedule Target
+ - ->
+ <mbean code="org.jboss.varia.scheduler.example.SchedulableMBeanExample"
+ name="jboss:service=SchedulableMBeanExample">
+ </mbean>
+ <!- - -->
+
+ <!--
+ | The Schedule Manager has to be started whenever
+ | schedules are needed.
+ |
+ | The default JMX Timer scheduling behaviour of FixedDelay execution
+ | (as of JDK5 or JBoss v4.0.5) is overriden below using FixedRate true
+ - ->
+ <mbean code="org.jboss.varia.scheduler.ScheduleManager"
+ name="jboss:service=ScheduleManager">
+ <attribute name="StartAtStartup">true</attribute>
+ <attribute name="FixedRate">true</attribute>
+ </mbean>
+ <!- - -->
+
+ <!--
+ | This is a single schedule Provider which works like the
+ | old Scheduler (when a MBean target is used)
+ |
+ | For clustered singleton schedules add the following dependency:
+ | <depends>jboss.ha:service=HASingletonDeployer,type=Barrier</depends>
+ - ->
+ <mbean code="org.jboss.varia.scheduler.SingleScheduleProvider"
+ name="jboss:service=SingleScheduleProvider">
+ <depends optional-attribute-name="ScheduleManagerName">jboss:service=ScheduleManager</depends>
+ <depends optional-attribute-name="TargetName">jboss:service=SchedulableMBeanExample</depends>
+ <attribute name="TargetMethod">hit( NOTIFICATION, DATE, REPETITIONS, SCHEDULER_NAME, java.lang.String )</attribute>
+ <attribute name="DateFormat"></attribute>
+ <attribute name="StartDate">NOW</attribute>
+ <attribute name="Period">10000</attribute>
+ <attribute name="Repetitions">10</attribute>
+ </mbean>
+ <!- - -->
+
+ <!--
+ | This is a Database based schedule Provider. For more
+ | information have a look at the class JavaDoc
+ | For hypersonic
+ | CREATE TABLE Schedule
+ | (
+ | target VARCHAR(100),
+ | method_name VARCHAR(100),
+ | method_signature VARCHAR(100),
+ | start_date VARCHAR(20),
+ | period BIGINT,
+ | repetitions INTEGER,
+ | date_format VARCHAR(20)
+ | )
+ |
+ | For clustered singleton schedules add the following dependency:
+ | <depends>jboss.ha:service=HASingletonDeployer,type=Barrier</depends>
+ - ->
+ <mbean code="org.jboss.varia.scheduler.DBScheduleProvider"
+ name="jboss:service=DBScheduleProvider">
+ <depends optional-attribute-name="ScheduleManagerName">jboss:service=ScheduleManager</depends>
+ <depends>jboss:service=SchedulableMBeanExample</depends>
+ <depends>jboss:service=Hypersonic</depends>
+ <attribute name="DataSourceName">java:DefaultDS</attribute>
+ <attribute name="SQLStatement">SELECT target, method_name, method_signature, start_date, period, repetitions, date_format FROM Schedule</attribute>
+ </mbean>
+ <!- - -->
+
+ <!--
+ | This is a XML based schedule Provider. For more
+ | information have a look at the class JavaDoc
+ |
+ | For clustered singleton schedules add the following dependency:
+ | <depends>jboss.ha:service=HASingletonDeployer,type=Barrier</depends>
+ - ->
+ <mbean code="org.jboss.varia.scheduler.XMLScheduleProvider"
+ name="jboss:service=XMLScheduleProvider">
+ <depends optional-attribute-name="ScheduleManagerName">jboss:service=ScheduleManager</depends>
+ <depends>jboss:service=SchedulableMBeanExample</depends>
+ <attribute name="Schedules">
+ <schedules>
+ <schedule>
+ <target-mbean-name>jboss:service=SchedulableMBeanExample</target-mbean-name>
+ <target-method-name>hit</target-method-name>
+ <target-method-signature>NOTIFICATION, DATE, REPETITIONS, SCHEDULER_NAME, java.lang.String</target-method-signature>
+ <date-format></date-format>
+ <start-date>NOW</start-date>
+ <period>15555</period>
+ <repetitions>55</repetitions>
+ </schedule>
+ </schedules>
+ </attribute>
+ </mbean>
+ <!- - -->
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/scheduler-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/scheduler-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/scheduler-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- $Id: scheduler-service.xml 59789 2007-01-18 17:30:15Z dimitris at jboss.org $ -->
+
+<server>
+
+ <!-- ==================================================================== -->
+ <!-- Scheduler Service -->
+ <!-- ==================================================================== -->
+
+ <!--
+ | JDK5 javax.management.timer.Timer appears to be using a single
+ | threaded implementation for executing scheduled tasks.
+ | If you want to revert to the JBossMX timer implementation that
+ | uses a dynamically extensible thread pool to execute scheduled
+ | tasks, uncomment the JBossTimer service below. The Scheduler
+ | service will use this, instead of creating a new Timer.
+
+ <mbean code="org.jboss.mx.timer.JBossTimer"
+ name="jboss:service=Timer">
+ </mbean>
+ -->
+
+ <!--
+ | This example shows how to use a pluggable Schedulable impl
+
+ <mbean code="org.jboss.varia.scheduler.Scheduler"
+ name=":service=Scheduler">
+ <attribute name="StartAtStartup">true</attribute>
+ <attribute name="SchedulableClass">org.jboss.varia.scheduler.example.SchedulableExample</attribute>
+ <attribute name="SchedulableArguments">Schedulabe Test,12345</attribute>
+ <attribute name="SchedulableArgumentTypes">java.lang.String,int</attribute>
+ <attribute name="InitialStartDate">0</attribute>
+ <attribute name="SchedulePeriod">10000</attribute>
+ <attribute name="InitialRepetitions">-1</attribute>
+ <attribute name="FixedRate">true</attribute>
+ </mbean>
+ -->
+
+ <!--
+ | NOTE: If a Timer service is not already running, the scheduler will create
+ | one with a default object name of jboss:service=Timer. This will not be
+ | redeployed upon redeploying your scheduler. To change the object name
+ | for the Timer service to be created, declare an attribute named TimerName.
+ | For more info on scheduler, see http://www.jboss.org/wiki/Wiki.jsp?page=Scheduler.
+ -->
+
+ <!--
+ | This example shows how to use a target MBean
+
+ <mbean code="org.jboss.varia.scheduler.example.SchedulableMBeanExample"
+ name=":name=SchedulableMBeanExample">
+ </mbean>
+ <mbean code="org.jboss.varia.scheduler.Scheduler"
+ name=":service=Scheduler,name=SchedulableMBeanExample">
+ <attribute name="StartAtStartup">true</attribute>
+ <attribute name="SchedulableMBean">:name=SchedulableMBeanExample</attribute>
+ <attribute name="SchedulableMBeanMethod">hit( NOTIFICATION, DATE, REPETITIONS, SCHEDULER_NAME, java.lang.String )</attribute>
+ <attribute name="InitialStartDate">NOW</attribute>
+ <attribute name="SchedulePeriod">10000</attribute>
+ <attribute name="InitialRepetitions">10</attribute>
+ <attribute name="FixedRate">true</attribute>
+ </mbean>
+ -->
+
+</server>
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/sqlexception-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/sqlexception-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/sqlexception-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<server>
+ <mbean code="org.jboss.ejb.plugins.cmp.jdbc.SQLExceptionProcessor"
+ name="jboss.jdbc:service=SQLExceptionProcessor">
+ </mbean>
+</server>
\ No newline at end of file
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/META-INF/jboss-service.xml
===================================================================
--- labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/META-INF/jboss-service.xml (rev 0)
+++ labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/META-INF/jboss-service.xml 2007-06-06 16:55:52 UTC (rev 12361)
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!-- ===================================================================== -->
+<!-- -->
+<!-- UUID Key Generator Factory Service Configuration -->
+<!-- -->
+<!-- ===================================================================== -->
+
+<server>
+
+ <!-- UUIDKeyGeneratorFactoryService -->
+ <mbean code="org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactoryService"
+ name="jboss:service=KeyGeneratorFactory,type=UUID">
+ </mbean>
+
+ <!-- HiLoKeyGeneratorFactory -->
+ <mbean code="org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory"
+ name="jboss:service=KeyGeneratorFactory,type=HiLo">
+
+ <depends>jboss:service=TransactionManager</depends>
+
+ <!-- Attributes common to HiLo factory instances -->
+
+ <!-- DataSource JNDI name -->
+ <depends optional-attribute-name="DataSource">jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
+
+ <!-- table name -->
+ <attribute name="TableName">HILOSEQUENCES</attribute>
+
+ <!-- Column that contains sequence name -->
+ <attribute name="SequenceColumn">SEQUENCENAME</attribute>
+
+ <!-- Column that contains hi values -->
+ <attribute name="IdColumnName">HIGHVALUES</attribute>
+
+ <!-- Create table DDL - DDL should be in a single line without line breaks to work with DB2 7.2 -->
+ <attribute name="CreateTableDdl">
+ create table HILOSEQUENCES (SEQUENCENAME varchar(50) not null, HIGHVALUES integer not null, constraint hilo_pk primary key (SEQUENCENAME))
+ </attribute>
+
+ <!-- Uncomment to make it cluster-safe: Select current Hi value query (FOR UPDATE is recommended)
+ <attribute name="SelectHiSql">
+ select HIGHVALUES from HILOSEQUENCES where SEQUENCENAME='general' FOR UPDATE
+ </attribute>
+ -->
+
+ <!-- whether the table should be created (if doesn't exist yet) at the start phase -->
+ <attribute name="CreateTable">true</attribute>
+
+ <!-- whether the table should be dropped (if exists) at the stop phase -->
+ <attribute name="DropTable">false</attribute>
+
+ <!-- Instance-specific attributes -->
+
+ <!-- JNDI name -->
+ <attribute name="FactoryName">HiLoKeyGeneratorFactory</attribute>
+
+ <!-- Sequence name which this factory will use -->
+ <attribute name="SequenceName">general</attribute>
+
+ <!-- Block size -->
+ <attribute name="BlockSize">10</attribute>
+ </mbean>
+
+</server>
+
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/hilo/HiLoKeyGenerator.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/hilo/HiLoKeyGenerator.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/hilo/HiLoKeyGeneratorFactory.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/hilo/HiLoKeyGeneratorFactory.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/hilo/HiLoKeyGeneratorFactoryMBean.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/hilo/HiLoKeyGeneratorFactoryMBean.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGenerator.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGenerator.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGeneratorFactory.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGeneratorFactory.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGeneratorFactoryService.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGeneratorFactoryService.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGeneratorFactoryServiceMBean.class
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/deploy/uuid-key-generator.sar/org/jboss/ejb/plugins/keygenerator/uuid/UUIDKeyGeneratorFactoryServiceMBean.class
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/activation.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/activation.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/antlr.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/antlr.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/autonumber-plugin.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/autonumber-plugin.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bcel.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bcel.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bindingservice-plugin.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bindingservice-plugin.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bsf.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bsf.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bsh-deployer.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bsh-deployer.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bsh.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/bsh.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/cglib.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/cglib.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-codec.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-codec.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-collections.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-collections.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-httpclient.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-httpclient.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-logging.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/commons-logging.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/dom4j.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/dom4j.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/ejb3-persistence.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/ejb3-persistence.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/el-api.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/el-api.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hibernate-annotations.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hibernate-annotations.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hibernate-entitymanager.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hibernate-entitymanager.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hibernate3.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hibernate3.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hsqldb-plugin.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hsqldb-plugin.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hsqldb.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/hsqldb.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/javassist.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/javassist.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jaxen.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jaxen.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-cache-jdk50.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-cache-jdk50.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-common-jdbc-wrapper.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-common-jdbc-wrapper.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-ejb3x.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-ejb3x.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-hibernate.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-hibernate.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-j2ee.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-j2ee.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jaxrpc.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jaxrpc.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jca.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jca.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jsr77.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jsr77.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jsr88.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-jsr88.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-management.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-management.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-monitoring.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-monitoring.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-remoting-int.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-remoting-int.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-remoting.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-remoting.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-saaj.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-saaj.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-serialization.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-serialization.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-srp.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-srp.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-transaction.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-transaction.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-vfs.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss-vfs.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jboss.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossjta-integration.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossjta-integration.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossjta.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossjta.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossmq.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossmq.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbosssx.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbosssx.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossts-common.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossts-common.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossws-integration.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jbossws-integration.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jmx-adaptor-plugin.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jmx-adaptor-plugin.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jnpserver.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jnpserver.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/joesnmp.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/joesnmp.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jpl-pattern.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jpl-pattern.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jpl-util.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jpl-util.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jsp-api.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/jsp-api.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/log4j-snmp-appender.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/log4j-snmp-appender.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/log4j.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/log4j.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/mail-plugin.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/mail-plugin.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/mail.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/mail.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/properties-plugin.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/properties-plugin.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/quartz.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/quartz.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/scheduler-plugin-example.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/scheduler-plugin-example.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/scheduler-plugin.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/scheduler-plugin.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/servlet-api.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/servlet-api.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/xmlentitymgr.jar
===================================================================
(Binary files differ)
Property changes on: labs/jbosslabs/trunk/stats-server/binaries/as/to-copy/server/default/lib/xmlentitymgr.jar
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
More information about the jboss-svn-commits
mailing list