[jboss-cvs] JBossAS SVN: r101627 - projects/docs/enterprise/5.0/Installation_Guide/pot.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Sun Feb 28 19:12:52 EST 2010 

Author: benlc
Date: 2010-02-28 19:12:52 -0500 (Sun, 28 Feb 2010)
New Revision: 101627

Added:
   projects/docs/enterprise/5.0/Installation_Guide/pot/Appendix.pot
   projects/docs/enterprise/5.0/Installation_Guide/pot/Installation_Guide.pot
   projects/docs/enterprise/5.0/Installation_Guide/pot/Migration.pot
Log:
'committing additional pot files not added previously'


Added: projects/docs/enterprise/5.0/Installation_Guide/pot/Appendix.pot
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/pot/Appendix.pot	                        (rev 0)
+++ projects/docs/enterprise/5.0/Installation_Guide/pot/Appendix.pot	2010-03-01 00:12:52 UTC (rev 101627)
@@ -0,0 +1,104 @@
+# 
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-02-28T23:45:41\n"
+"PO-Revision-Date: 2010-02-28T23:45:41\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Disabling Authentication"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Authentication is disabled by default when you install your distribution. This appendix enables a user who has previously enabled authentication to disable it for specific services."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "All specified paths in the sections below are relative to <literal>$JBOSS_HOME</literal>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Disabling Authentication for JXM Console:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable authentication for the JMX console, edit the following file and comment out the security-constraint section:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following fragment should be commented out:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Disabling Authentication for Web Console:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable authentication for the Web console, edit the following file to comment out the security-constraint section:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Disabling Authentication for HTTP Invoker:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable authentication for the http invoker, <literal>JNDIFactory</literal>, <literal>EJBInvokerServlet</literal>, and <literal>JMXInvokerServlet</literal> need to be removed from the security realm in the file:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For example, the security-constraint element should look as follows:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Disabling Authentication for JMX Invoker:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable authentication for the JMX invoker, edit the following file to comment out the security interceptor passthrough:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Locate the mbean section with the class <literal>org.jboss.jmx.connector.invoker.InvokerAdaptorService</literal>. In that section comment out the line that relates to authenticated users:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Disabling Authentication for the ProfileService:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable authentication for the <literal>ProfileService</literal>, edit the following file and comment out the contents of the <literal>serverProxyInterceptors</literal> list:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Disabling Authentication for JBossWS:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "To disable authentication for JBossWS, edit the following file and comment out the <literal>security-constraint</literal>:"
+msgstr ""
+

Added: projects/docs/enterprise/5.0/Installation_Guide/pot/Installation_Guide.pot
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/pot/Installation_Guide.pot	                        (rev 0)
+++ projects/docs/enterprise/5.0/Installation_Guide/pot/Installation_Guide.pot	2010-03-01 00:12:52 UTC (rev 101627)
@@ -0,0 +1,14 @@
+# 
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-02-28T23:45:41\n"
+"PO-Revision-Date: 2010-02-28T23:45:41\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+

Added: projects/docs/enterprise/5.0/Installation_Guide/pot/Migration.pot
===================================================================
--- projects/docs/enterprise/5.0/Installation_Guide/pot/Migration.pot	                        (rev 0)
+++ projects/docs/enterprise/5.0/Installation_Guide/pot/Migration.pot	2010-03-01 00:12:52 UTC (rev 101627)
@@ -0,0 +1,1029 @@
+# 
+# AUTHOR <EMAIL at ADDRESS>, YEAR.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: 0\n"
+"POT-Creation-Date: 2010-02-28T23:45:42\n"
+"PO-Revision-Date: 2010-02-28T23:45:42\n"
+"Last-Translator: Automatically generated\n"
+"Language-Team: None\n"
+"MIME-Version: 1.0\n"
+"Content-Type: application/x-publican; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#. Tag: title
+#, no-c-format
+msgid "Migrating to Enterprise Application Platform 5.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This chapter provides information for administrators who plan to move their enterprise servers to the new Enterprise Application Platform 5.0. The first section covers new features available in Enterprise Application Platform 5.0. The second section covers the changes to configuration, administration, and application deployment between Enterprise Application Platform 4.x and Enterprise Application Platform 5.0. If you require further information, refer to the relevant technology guides provided in this release."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What's New in Enterprise Application Platform 5.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This section provides an overview of the components of Enterprise Application Platform 5.0, and the changes to each component between version 4.x and 5.0."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JBoss Application Server 5.1.0.GA"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JBoss Application Server 5 is the next generation of the JBoss Application Server build on top of a new kernel architecture, the <application>JBoss Microcontainer</application>. The JBoss Microcontainer is a lightweight container for managing the deployment, configuration and lifecycle of Plain Old Java Objects (POJOs). While remaining compatible with the 4.x-based JMX kernel, the Microcontainer integrates nicely with the JBoss framework for Aspect Oriented Programming, JBoss AOP. Support for JMX in JBoss 5 remains strong and MBean services written against the old Microkernel should work as expected. Further, it lays the groundwork for Java EE 6 profile-oriented configurations and embedded JBoss AS, which will allow for fine grained selection of services for both unit testing and embedded scenarios."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "ProfileService-based Deployment Configuration"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The definition of the non-kernel deployers and deployment is now defined in a Profile obtained from the ProfileService. The <application>ProfileService</application> replaces JBoss AS 4.x <emphasis>server configuration</emphasis>. In JBoss AS 4.x, a server configuration was a collection of services and applications loaded from the <filename>deploy</filename> directory by the deployment scanner service. Enterprise Application Platform 5.0 uses more active profiles, which may depend on other <emphasis>sub-profiles</emphasis>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The main profile is the <emphasis>root profile</emphasis>, which is based on the <literal>${jboss.server.name}</literal>. This profile has three sub-profiles:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>bootstrap</emphasis> — representing <filename>conf/jboss-service.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>deployers</emphasis> — the <filename>deployers/</filename> directory"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<emphasis>applications</emphasis> — a hot-deployment profile for the <filename>deploy/</filename> and additional user directories"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A profile generally represents a named collection of deployments on a server. A profile can also apply certain behaviours to the deployments that it manages. Some profiles, such as the <literal>application</literal> profile, provide hot-deployment checks and allow remote distribution of deployed applications via the <literal>DeploymentManager</literal>. Other profiles can provide a farming service to distribute deployments over a cluster. The ProfileService also provides the ManagementView for ManagedDeployments/ManagedObjects used by the Enterprise Application Administration Console (admin-console)."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Enterprise Java Beans (EJB) 3.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JBoss EJB 3.0, an implementation of the latest revision of the EJB specification, is a deep overhaul and simplification of earlier versions of the EJB specification achieving its' goals to simplify development, facilitate a test driven approach, and focus more on writing POJOs rather than coding against complex EJB APIs."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Java Enterprise Edition 5 Compliance"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enterprise Application Platform 5.0 is a fully-certified Java EE 5 implementation using the microcontainer to integrate enterprise services together with a Servlet/JSP container, EJB container, deployers and management utilities in order providing a standard Java EE environment with the flexibility to simply deploy additional services on top of Java EE to for the functionality you need. For further certification details, read the <ulink url=\"http://java.sun.com/javaee/overview/compatibility.jsp\">Java EE Compatibility</ulink> page."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Seam 2.2.0.GA"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Seam is an application framework for Enterprise Java. It integrates technologies such as Asynchronous JavaScript and XML (AJAX), JavaServer Faces (JSF), Java Persistence (JPA), Enterprise JavaBeans 3.0 (EJB) and Business Process Management (BPM). Seam enables developers to assemble complex web applications using simple annotated Java classes, a rich set of UI components, and very little XML."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "RESTEasy 1.1.GA"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "RESTEasy provides several frameworks to help you build RESTful Web Services and RESTful Java applications. It is a fully-certified, fully-portable implementation of the <ulink url=\"http://jsr311.dev.java.net/\">JAX-RS</ulink> specification, which defines a Java API for RESTful Web Services over the Hypertext Transfer Protocol (HTTP)."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Enhanced Enterprise GUI Installer"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Enterprise Installer retains the familiar Enterprise Application Platform 4.3 interface but includes enhancements to provide you with a complete Enterprise Application Platform 5.0 installation. This is fully-localized and provides you with secure JMX, Web and Administration consoles."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The new Enterprise Installer will also present users with the opportunity to install the optional Native package, which includes <application>JBoss Native</application> and <application>mod_jk</application>. The Native package helps users who wish to use Tomcat or JBoss Web with the HTTP daemon."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Enterprise Application Platform Administration Console"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A new administration console is being introduced in this Enterprise Application Platform release. The admin-console enables configuration and management of a single Enterprise Application Platform server instance. See Section 2.3 for more information about this new management console."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "JBoss Transactions includes Java Transaction Service"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JBoss Transactions now includes the Java Transaction Service and the XML Transaction Service. The Java Transaction Service handles distributed, interoperable transactions between Enterprise JavaBean containers. The XML Transaction service handles transactions for Web Services."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Distribution with Red Hat Signed Jars"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "With Red Hat signed jars, you can be confident the contents of your product distribution is actually what was shipped by Red Hat."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For the complete technology matrix and information on the revision level of included components please refer to <ulink url=\"http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html\">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Release_Notes/index.html</ulink>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "What's Different in Enterprise Application Server 5.0"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The distribution layout and configuration information in the Enterprise Application Platform 5.0 distribution are similar to the Enterprise Application Platform 4.x series with some notable differences. This section highlights the differences at a glance."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Differences in the Distribution Layout"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The directory structure of <filename>jboss-as</filename> directory is summarized below."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/bin</filename> — starts scripts and <filename>run.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/client</filename> — contains client JARs. <filename>jbossall-client.jar</filename> used to bundle the majority of jboss client libraries. Now they are referenced through the Class-Path manifest entry instead. It requires that you have jbossall-client.jar together with the other client/*.jar libraries so they can be found."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/common/lib</filename> — shared libraries common to various configurations have been moved to this new shared location. This eliminates the need for multiple copies of the same library in the distribution."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The location of the common library directory is controlled with the following properties:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>jboss.common.base.url</literal> — the default value is <literal>${jboss.home.url}/common</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>jboss.common.lib.url</literal> — the default value is <literal>${jboss.common.base.url}/lib</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The common library directory is shared by all configuration types except for the <literal>minimal</literal> configuration. The common library is referenced at the beginning of every configuration's <filename>conf/jboss-service.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <filename>library</filename> directory of the individual directory remains in place, although in some cases (as in <filename>$JBOSS_HOME/server/default/lib/</filename>) it is an empty directory."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/docs</filename> — contains schemas, document type declarations, examples and licenses. Most deployment descriptors now use XML Schema Definitions (XSDs). One exception is <literal>jboss-app</literal>, which uses <filename>jboss-app_5_0.dtd</filename>. JBoss Web uses <filename>jboss-web_5_1.xsd</filename>. For Enterprise JavaBeans 3.0 deployments, <filename>jboss_5_1.xsd</filename> is the recommended schema. Enterprise JavaBeans 2.0 deployments must use <filename>jboss_x_x.dtd</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/lib</filename> — contains the core bootstrap JARs. These have been changed slightly to accomodate the Microcontainer and the division of <filename>jboss-common</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/server</filename> — contains directories for configuring the server:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>xyz</literal> configuration"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/conf</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>bootstrap.xml</filename> — a new kernel bootstrap configuration that refers to other configuration files containing the beans to set up each individual subsystem."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>bindingservice.beans</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/META-INF</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>bindings-jboss-beans.xml</filename> — contains required port bindings."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jboss-bindingservice.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/bootstrap</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>vfs.xml</filename> — initializes the virtual file system"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>classloader.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>aop.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jmx.xml</filename> — legacy JMX support."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>deployers.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>profile-repository.xml</filename> — the ProfileService enabled deployment repository."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jax-ws-catalog.xml</filename> — an Oasis Catalog-driven Schema/DTD namespace configuration file."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jbossts-properties.xml</filename> — contains new JBossTS properties."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jboss-service.xml</filename> — contains legacy static managed beans to retain compatibility."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jndi.properties</filename> — contains JNDI configuration properties."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>log4j.xml</filename> — contains log4j configuration information."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>login-config.xml</filename> — contains JAAS login configuration information."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/props</filename> — contains default JAAS login properties files."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>standardjbosscmp-jdbc.xml</filename> — contains CMP2 configuration information."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>standardjboss.xml</filename> — contains Enterprise JavaBean 2.0 configuration information."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/xmdesc</filename> — contains legacy XML managed bean descriptors."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/deploy</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jca-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>hdscanner-jboss-beans.xml</filename> — contains the hot-deployment scanner."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>legacy-invokers-service.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>profileservice-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>remoting-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>transaction-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>vfs-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/deployers</filename> — contains new VDF deployers."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/bsh-deployer</filename> — contains the beanshell deployer."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>ejb3.deployer</filename> — contains Enterprise JavaBean 3.0 deployers."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jboss-aop-jboss5.deployer</filename> — contains the aspect deployer."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jboss-jca.deployer</filename> — contains the JCA deployers."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jbossweb.deployer</filename> — contains the WAR deployers."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jbossws.deployer</filename> — contains the web service deployers."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>seam.deployer</filename> — contains the Seam deployer."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>clustering-deployers-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>dependency-deployers-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>directory-deployer-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>ear-deployer-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>ejb-deployer-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>hibernate-deployer-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>logbridge-boss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jsr77-deployers-jboss-beans.xml</filename> — contains JSR-77 (J2EE Management) support."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>metadata-deployer-jboss-beans.xml</filename> — contains the metadata handlers."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>messaging-definitions-jboss-beans.xml</filename> — contains data required to map JMS destinations to managed objects."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>security-deployer-jboss-beans.xml</filename> — contains the security deployers."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>xnio.deployer</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jboss-threads.deployer</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>/lib</filename> — contains static library JARs. Some JARs that were previously located in this directory have been moved into the top-level <filename>common/lib</filename> directory."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Standard and Web Configuration"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Two additional server configurations are distributed with Enterprise Application Platform 5.0: <literal>standard</literal> and <literal>web</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>standard</literal> configuration is certified for Java EE 5 compliance. This configuration enables both call-by-value and deployment isolation by default. Support for RMI-IIOP (Remote Method Invocation over the Internet Inter-Orb Protocol) and Java UDDI (Universal Description, Discovery and Integration), as in the <literal>all</literal> configuration type, is also enabled."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The list that follows specifies the changes to particular property files:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>deployers/ear-deployer-jboss-beans.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>conf/jboss-service.xml</filename> <literal>call-by-value</literal> for <literal>jboss:service=Naming</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>conf/jndi.properties</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>conf/jacorb.properties</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>deploy/iiop-service.xml</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>lib/avalon-framework.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>lib/jacorb.jar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>deploy/juddi-service.sar</filename>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>web</literal> configuration is a new lightweight configuration created around JBoss Web and provides the services required for web application deployment and only a subset of Java EE technologies. This profile does not include JBoss Transaction JTS or XTS, Enterprise Java Bean 1.x or 2.x capabilities, JBoss Messaging, JCA, or JBoss IIOP."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Differences in Application Server Configuration Files"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "General"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A reminder that the <filename>rpm</filename> and <filename>zip</filename> distributions of the Enterprise Application Platform are shipped with authentication enabled for the JMX Console, Web Console, JMX Invoker, Administration Console, HTTP Invoker and Profile Service. No user accounts are active by default to assist in preventing default user and password-based attacks."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>shutdown.sh</filename> now accepts a JNDI URL, as follows:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If a user omits the <code>-c</code> option when starting an instance of JBoss Application Server in Enterprise Application Platform 4.x, the <literal>production</literal> configuration was started by default. In Enterprise Application Platform 5.0, <literal>default</literal> configuration is used with <code>-c</code> is omitted."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>bin/run.conf</filename> now uses a Java heap size of 1303 megabytes. This is consistent across all configurations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<ulink url=\"http://www.jboss.org/j2ee/dtd\">http://www.jboss.org/j2ee/dtd</ulink> has been updated with the latest Document Type and Schema Declarations."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If you use Remote Method Invocation (RMI), you will likely want to make Port 8083 on your server accessible to clients. The <literal>production</literal> configuration provided with Enterprise Application Platform 5.0 restricts the classes served on this port. This option can be set in <filename>production/conf/jboss-service.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The cluster-safe UUID generator can now be used from <filename>server/production/deploy/uuid-key-generator.sar/META-INF/jboss-service.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The delay period for <filename>server/production/deploy/hdscanner-jboss-beans.xml</filename> to rescan for deployment changes has been increased to 60 seconds from the previous 5 second delay period."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "J2EE Connector Architecture"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>jboss-ra.xml</filename> can now be used to override the properties specified in <filename>ra.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Support has been added for defining dependencies in J2EE Connector Architecture (JCA) adapters."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>server/production/deploy/jca-jboss-beans.xml</filename> disables debug monitoring of JCA and database connections:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This disables the application server's debug support, which means that the origin of each database connection obtained is not tracked, and connection leaks cannot be tracked, either. Unclosed managed database connections are still returned to the connection pool, regardless of this attribute's value."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Web"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "For JavaServer Pages pages, the default setting for <varname>DeleteWorkDirOnContextDestroy</varname> is <literal>true</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>emptySessionPath=\"true\"</literal> no longer sets the cookie path <filename>/</filename> by default. Instead, the cookie path is set via the <literal>&lt;SessionCookie path=\"/\" /&gt;</literal> in the <varname>Context</varname> element. Session cookies are now scoped to the context by default."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>emptySessionPath</literal> no longer affects whether Session IDs are recycled. This is now handled by the <varname>org.apache.catalina.connector.Request.SESSION_ID_CHECK</varname> system property. If set to <literal>true</literal>, the Servlet container verifies that a Session ID does not yet exist in a particular context before creating a session with that ID."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Clustering"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Clustering configurations have been moved to a new <filename>/deploy/cluster</filename> directory."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A separate cache is now used for Clustered Single Sign-On (SSO)."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "UseJK, snapshot mode and snapshot interval can now be configured on a per-application basis. The default value for UseJK depends upon whether the <varname>jvmRoute</varname> is set."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The default setting for session replication is now <literal>total</literal> replication instead of <literal>buddy</literal> replication."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>loopback</varname> is now set to <literal>true</literal> for all JGroups User Datagram Protocol stacks."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <varname>jboss.jgroups.udp.mcast_port</varname> property is now used to configure the multicast port. The <code>-m</code> option now sets <varname>jboss.jgroups.udp.mcast_port</varname> instead of <varname>jgroups.udp.mcast_port</varname>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<varname>jgroups.udp.mcast_port</varname> is checked internally by JGroups, and is used to override any XML-based configuration. If this parameter is set, two channels with non-shared transports cannot use different ports. The <varname>jboss.jgroups.udp.mcast_port</varname> property substitutes system properties in the default UDP channel configurations."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Transactions"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The transaction manager configuration information has moved from <filename>conf/jboss-service.xml</filename> to <filename>deploy/transaction-service.xml</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Logging"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The default <filename>conf/jboss-log4j.xml</filename> configuration now includes the thread name for <filename>log/server.log</filename> entries."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The new <varname>jboss.server.log.threshold</varname> system property can be used to control the <filename>log/server.log</filename> threshold. The default value is <literal>INFO</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<filename>server.log</filename> is appended, rather than truncated, after a server is restarted."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The following changes apply only to <filename>server/production/conf/jboss-log4j.xml</filename>:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the console logger has been commented out by default."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the async logger is enabled by default."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "a <filename>cluster.log</filename> file has been added to store cluster output."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Security"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "All security-related configuration files are now found in the <filename>deploy/security</filename> directory."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Enterprise JavaBeans"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enterprise JavaBean configuration information is now located in <filename>deployers/ejb3.deployer/META-INF/ejb3-deployers-jboss-beans.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java Persistence API configuration information is now located in <filename>deployers/ejb3.deployer/META-INF/jpa-deployers-jboss-beans.xml</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Administration Console"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The first release of the Enterprise Application Platform Administration Console (<literal>admin-console</literal>) provides the following administrative features:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "configuration information about the system on which the Enterprise Application Platform is running."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "configuration information about the Service Binding Manager."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Deploy, Undeploy and Update Enterprise Applications, including:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Java EE Enterprise Applications (EARs)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Web Applications (WARs)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Resource Adapters (RARs)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enterprise JavaBean JARs (EJB2 and EJB3)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "persistent configuration changes for the following resources:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Data Sources"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Connection Factories"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "JMS Queues and Topics (based on JBoss Messaging)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Control Operations:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "execute scripts to perform tasks against a running instance of the application server."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "stop, start, and restart applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "view resource statistics"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "view resource metric information"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The new <literal>admin-console</literal> provided with Enterprise Application Platform 5.0 retains the JMX and web consoles. <literal>admin-console</literal> supports the <literal>production</literal>, <literal>all</literal>, <literal>web</literal> and <literal>default</literal> configurations out of the box. It has also been tested with <literal>standard</literal> configuration. To use <literal>admin-console</literal> with <literal>standard</literal> configuration, copy the <filename>admin-console.war</filename> directory from the <literal>default</literal> server configuration, as follows:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<literal>admin-console</literal> should work with any custom configuration. Use the above command, replacing <literal>&lt;standard&gt;</literal> with the custom configuration name of your choice."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The Enterprise Application Platform 5.0 Administration Console is not intended for use with the <literal>minimal</literal> configuration provided with the distribution. Custom configurations based on this configuration should not be used with the Administration Console, either."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "When the server has been started, you can use the <literal>admin-console</literal> to perform administrative tasks for your application server. To use the <literal>admin-console</literal>, point your browser to <literal>http://${hostname}:8080/admin-console</literal>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "<!-- The Quick Start Guide for the Enterprise Application Platform 5.0 Administration Console is available at <ulink url=\"http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_Console_Quick_Start_Guide/index.html\">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_Console_Quick_Start_Guide/index.html</ulink>. --> <!-- NOTE TO LAURA: - is there a document on Enterprise Application Platform 5 Admin Console to link to?? --> <!-- Complete reference on use of the Enterprise Application Platform 5.0 Administraton Console, see the link TBD. -->"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Applications"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "As noted earlier, Enterprise Application Platform 5.0 is a fully-compliant implementation of the Java Enterprise Edition 5 (Java EE 5) Platform Specification. Java EE 5 defines the metadata associations of the Java language which can be used to annotate application code and eliminate the need for deployment descriptors wherever possible. Default behavior is also defined with the ability to override as needed. This is known as <emphasis>configuration by exception</emphasis>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Portable Java EE applications running on Enterprise Application Platform 4.x can be deployed to Enterprise Application Platform 5.0 without any changes. However, runtime-specific deployment information may be required when migrating from another vendor's application server to Enterprise Application Platform 5.0."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enterprise Application Platform 5.0 users can take advantage of the simplified packaging and deployment rules defined in the Java EE 5 Platform Specification such as no longer requiring an <filename>application.xml</filename> file in Enterprise Archives (EARs). Additionally, a default library directory (<filename>lib</filename>) in the root directory of an EAR makes the JARs available to all components packaged within the EAR. If an <filename>application.xml</filename> file is included, the <literal>library-directory</literal> element can be used to specify the location of the <filename>lib</filename> directory."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enterprise Application Platform 5.0 also introduces a new deployable unit: the <emphasis>MCBeans archive</emphasis>, after JBoss Microcontainer, which typically takes the <filename>.beans</filename> or <filename>.deployer</filename> suffix. MCBeans archives package a POJO deployment in a JAR file with a <filename>META-INF/jboss-beans.xml</filename> descriptor. This format is common in Enterprise Application Platform deployers."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Application verification for all file types is enabled by default, and can be configured in the <filename>deployers/ear-deployer-jboss-beans.xml</filename> file, specifically:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Enterprise JavaBean 2.0 archive verification remains the same between Enterprise Application Platform 4.x and Enterprise Application Platform 5.0. However, the properties that control verification have been moved from <filename>deploy/ejb-deployer.xml</filename> to <filename>deployers/ejb-deployer.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "If an enterprise archive contains only an application client and refers to EJBs, you must also add the <literal>&lt;/ignore-dependency&gt;</literal> element to the <literal>ejb-ref</literal> or <literal>ejb-local-ref</literal> definitions in the <filename>jboss-client.xml</filename> deployment descriptor. This informs the deployer to deploy the archive without resolving the referenced dependencies."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Classloading"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The new <literal>ClassLoader</literal> is fully backwards compatible, with <ulink url=\"http://www.jboss.org/community/docs/DOC-12840\">one exception that does not affect common use</ulink>. All classloading configurations from JBoss AS 4.x will still work with the new implementation, and most default settings retain the behaviour of the previous version."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The new <literal>ClassLoader</literal> shares many design and implementation details with the original <literal>UnifiedClassLoader</literal>, but makes the following improvements:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "the classloader no longer depends upon JMX, so it can be used in any environment as a standalone."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "it is much easier to implement your own classloader policy."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "increased control over which classloaders your classloader delegates to."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "increased control over which classes are visible to other classloaders."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "heirarchical repositories have been replaced by domains, and can now extend beyond a single level."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "One thing to note. <literal>useJBossWebClassLoader=\"true\"</literal> is not used in Enterprise Application Platform 5.0. All WAR classloaders in Enterprise Application Platform 5.0 are JBoss <literal>ClassLoader</literal>s, so the <literal>WarDeployer</literal> no longer handles the configuration details for web applications."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "There are several methods available to change the classloading configuration of a WAR:"
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Remove the <literal>WarClassLoaderDeployer</literal>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The <literal>WarClassLoaderDeployer</literal> automatically implements the defined classloading rules for WARs. Each WAR is assigned a scoped classloading domain. Its classes are not visible to other applications or to any parent EAR, and where possible the WAR's classes are called first. To remove this behavior and make WAR classloading behave like other deployers, comment out the <literal>WarClassLoaderDeployer</literal> in <filename>deployers/jbossweb.deploy/META-INF/war-deployers-jboss-beans.xml</filename>."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "Define classloading rules explicitly for WAR"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Alternatively, add a <filename>WEB-INF/jboss-classloading.xml</filename> with the following content to your WAR."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "This lets you define how the WAR's classloader is constructed. In this case, the WAR's classloader has been placed in the <literal>DefaultDomain</literal>, which is shared with all other applications that do not define their own domain. <varname>import-all</varname> is enabled, which means the classloader will look at all other classes exported by other applications. <varname>export-all</varname> is set to expose all classes in our application to other classes."
+msgstr ""
+
+#. Tag: title
+#, no-c-format
+msgid "EAR Scoping"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "You can control how class isolation between deployments behave with the <varname>isolated</varname> property in <filename>deployers/ear-deployer-jboss-beans.xml</filename>, as follows:"
+msgstr ""
+

More information about the jboss-cvs-commits mailing list