[jboss-cvs] JBossAS SVN: r87894 - tags/JBoss_5_1_0_CR1/build/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Apr 27 15:40:43 EDT 2009
Author: jason.greene at jboss.com
Date: 2009-04-27 15:40:43 -0400 (Mon, 27 Apr 2009)
New Revision: 87894
Modified:
tags/JBoss_5_1_0_CR1/build/docs/readme.html
Log:
Update release notesi
Modified: tags/JBoss_5_1_0_CR1/build/docs/readme.html
===================================================================
--- tags/JBoss_5_1_0_CR1/build/docs/readme.html 2009-04-27 19:36:59 UTC (rev 87893)
+++ tags/JBoss_5_1_0_CR1/build/docs/readme.html 2009-04-27 19:40:43 UTC (rev 87894)
@@ -3,54 +3,18 @@
<meta content="text/html" http-equiv="content-type">
<meta content="JBoss Inc." name="author">
- <title>JBoss 5.0.1.GA Readme</title>
+ <title>JBoss 5.1.0.CR1 Release Notes</title>
</head>
<body>
<a href="http://www.jboss.com"><img src="http://www.jboss.com/images/common/jbosscorp_logo.png" alt="JBoss - A Division of Red Hat" border="0"></a>
-<h1>JBoss
-5.1.0.Beta1
-Release Notes</h1>
+<h1>JBoss 5.1.0.CR1 Release Notes</h1>
-<p>This is the first beta <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning"><span style="text-decoration: none; font-weight: 700;"></span>release</a> of the <b>JBoss 5.1</b>
-series for the <b>Java
-EE™</b>5
-codebase that fully complies with the
-Java EE 5 conformance testing
-certification requirements. It contains more than 40 bug fixes and
-improvents, including an improved profile service API and a tech
-preview of Web Beans.
+<p>This is the first candidate <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossProductVersioning"><span style="text-decoration: none; font-weight: 700;"></span>release</a> of the <b>JBoss 5.1</b> series. Along with many bug fixes and enhancements, this release includes a first cut of our new, significantly improved <a href="http://www.jboss.org/embjopr">open-source console</a>. We are hoping to get as much feedback as possible to ensure we have a great first version in the eventual 5.1.0.GA release. Please post your feedback to the embedded JOPR forum <a href="http://jboss.org/index.html?module=bb&op=viewforum&f=294">here</a>.
<br>
</p>
-<h4>From 5.0.0.GA</h4>
-This release brings us to the end of a 3+ year
-marathon of redesigning the most popular open-source application server
-over a completely new kernel architecture, the <a href="http://www.jboss.org/jbossmc/">JBoss Microcontainer</a>.
-It also marks the beginning of a new era of innovation for JBoss as we
-will be exploring the capabilities and limitations of the new
-architecture in the releases to come. In our view, JBossAS 5 provides
-a healthy foundation and the most advanced and fully extensible,
-cross component model, aspect integration, server runtime environment.
-For
-information
-on the APIs that
-make up Java EE 5, see
-<a href="http://java.sun.com/javaee/reference/index.jsp">Java
-EE APIs & Docs</a>. A
-tutorial on Java EE 5 can be found
-<a href="http://java.sun.com/javaee/5/docs/tutorial/doc/">here</a>. Please visit also the<a href="http://www.jboss.org/jbossas/docs/"> JBoss AS docs</a> pages as we'll be updating the documents with the latest information, and post your questions to the<a href="http://www.jboss.com/index.html?module=bb&op=viewforum&f=287"> JBossAS 5 User Forum</a>.
-<p>A sample Java EE 5 application
-that can be
-run on top of JBoss 5 and demonstrates many interesting
-technologies is the <b><i>Seam
-Booking Application</i></b>
-available <a href="http://repository.jboss.org/maven2/org/jboss/seam/examples/">here</a>.
-Check out the <a href="http://www.seamframework.org/">JBoss
-Seam</a> framework pages that link to many
-interesting topics for combining Seam with JBossAS 5.</p>
-
<h2>Overview</h2>
<ul>
@@ -68,121 +32,23 @@
</ul>
<h2><a name="Highlights">Highlights</a></h2>
-This release includes a tech preview (beta release) of the new JSR-299 Web Beans RI.
-You can find out more information about Web Beans
-<a href="http://docs.jboss.org/webbeans/reference/1.0.0.BETA1/en-US/html">here</a>.
-<br/><br/>
-
-Also included is improved support for JDK logging, and an improved profile service API.
-
-See the component updates section below for a list of all other updates.
-
-<h4>From 5.0.0.GA</h4>
-JBoss 5 is the next generation
-of the JBoss Application Server
-build on top of the new <a href="http://www.jboss.com/products/jbossmc">JBoss
-Microcontainer</a>. The JBoss
-Microcontainer is a lightweight
-container for managing POJOs, their deployment, configuration and
-lifecycle. It is a standalone project that replaces the famous JBoss
-JMX Microkernel of the 3.x and 4.x JBoss series. The Microcontainer
-integrates nicely with the JBoss framework for Aspect Oriented
-Programming, <a href="http://labs.jboss.com/portal/jbossaop">JBoss
-AOP</a>. Support for JMX in JBoss 5
-remains strong and MBean
-services written against the old Microkernel are expected to work.
-<p>JBoss5 is designed around the
-advanced concept of a
-<a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5DeploymentFramework">Virtual
-Deployment Framework</a> (VDF), that
-takes the aspect oriented
-design of many of the earlier JBoss containers and applies it to the
-deployment layer. Aspectized Deployers operate in a chain over a
-<a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5VirtualFileSystem">Virtual
-File System</a> (VFS), analyze
-deployments and produce metadata
-to be used by the JBoss Microcontainer, which in turn instantiates and
-wires together the various pieces of a deployment, controlling their
-lifecycle and dependencies.</p>
-
-<p>Many key features of JBoss 5
-are provided by integrating other
-standalone JBoss projects:</p>
-
<ul>
+<li><b>New Console</b> - This release includes our new administration console.
+<br/>See the full
+release notes for the console here.</li>
-<li><a href="http://labs.jboss.org/portal/jbossejb3">JBoss
-EJB3</a>
-included with JBoss 5 provides the implementation of the latest
-revision of the Enterprise Java Beans (EJB) specification. EJB 3.0 is a
-deep overhaul and simplification of the EJB specification. EJB 3.0's
-goals are to simplify development, facilitate a test driven approach,
-and focus more on writing plain old java objects (POJOs) rather than
-coding against complex EJB APIs.</li>
-<li><a href="http://www.jboss.com/products/messaging">JBoss
-Messaging</a> is a high performance
-JMS provider in the JBoss
-Enterprise Middleware Stack (JEMS), included with JBoss 5 as the
-default messaging provider. It is also the backbone of the <a href="http://www.jboss.com/products/esb">JBoss ESB</a>
-infrastructure. JBoss Messaging is a complete rewrite of JBossMQ, which
-is the default JMS provider for the JBoss AS 4.x series.</li>
-<li><a href="http://www.jboss.com/products/jbosscache">JBossCache</a> that
-comes in two flavors. A traditional tree-structured node-based
-cache and a <a href="http://labs.jboss.com/file-access/default/members/jbosscache/freezone/docs/2.0.0/PojoCache/en/html/index.html">
-PojoCache</a>, an in-memory,
-transactional, and replicated cache
-system that allows users to operate on simple POJOs transparently
-without active user management of either replication or persistency
-aspects.</li>
-<li><a href="http://labs.jboss.com/portal/jbossws">JBossWS</a>
-is the web services stack for JBoss 5 providing Java EE compatible web
-services, JAX-WS-2.0.</li>
-<li><a href="http://www.jboss.com/products/transactions">JBoss
-Transactions</a> is the default
-transaction manager for JBoss 5.
-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.</li>
-<li><a href="http://www.jboss.com/products/jbossweb">JBoss
-Web</a>
-is the Web container in JBoss 5, 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.</li>
+<li><b>Web Beans Update</b> - In addition, this release includes an updated tech preview of the new JSR-299 Web Beans RI.
+<br/>You can find out more information about Web Beans
+<a href="http://docs.jboss.org/webbeans/reference/1.0.0.PREVIEW1/en-US/html">here</a>.</li>
+
+<li><b>Farming Returnes</b> - Due to popular demand, the farming service is back!
+<br/>See the following wiki
+page <a href="http://www.jboss.org/community/docs/DOC-13616">here</a>.</li>
</ul>
+<h2><a name="Compatibility">Compatibility Issues</a></h2>
-JBoss 5
-includes features and bug fixes,
-many of them carried over upstream from the 4.x codebase. See the <a href="#Details">Detailed Release Notes</a>
-section for
-the full details.
-<p>A common theme
-for JBossAS 5 is the breaking out of internal subsystems into
-stand-alone projects
-and the introduction of SPIs throughout the server
-codebase. Those changes should not affect directly the end
-user but they are an important part of the JBoss strategy for making
-available the various EE services as independent projects, so that they
-can be wired-together and be consumed<b> </b>à la carte inside
-different runtime environments and not only inside the JBoss
-Application Server.
-</p>
+There are no known compatibility issues in 5.1.0.CR1.
-<p>If you are building JBossAS
-from
-source
-you'll notice we are migrating to a maven2 build. At this
-point
-the build is a hybrid one because it declares all JBoss
-dependencies as maven2 artifacts, however after the dependencies are
-resolved/imported the legacy ant based build is used to compile and
-build the distribution. This will change to a full maven build
-at
-some point in time. The jboss maven repo can be found <a href="http://repository.jboss.org/maven2/org/jboss/">here</a>.
-Starting from AS5 CR2, please note how the -sources.jar are also
-downloaded.</p>
-
-<h2><a name="Compatibility">Compatibility Issues</a></h2>
<h4>from 5.0.1.GA</h4>
<ul>
<li>This release resolves issues related to running JBossAS 5 under AIX with an IBM jdk. See JBAS-6506, JBAS-6428.</li>
@@ -576,342 +442,291 @@
</ul>
-<h2><a name="Libraries">Library Updates</a></h2>
-
-For a full list of the JBoss and thirdparty libraries used with JBoss AS 5.0.1.GA
-check the <a style="font-family: monospace;" href="http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_5_0_1_GA/component-matrix/pom.xml">pom.xml</a>
-found in the component-matrix directory of the source code distribution. To see
-the maven dependency tree you can also do a '<span style="font-family: monospace;">mvn dependency:tree</span>'
-from the <span style="font-family: monospace;">thirdparty</span> directory of the source code distro.<br>
-
-<br>
-
-Some rather important utilized jboss project versions are listed below. You are
-encouraged to browse the individual project's documentation and view
-the release notes at <a href="http://www.jboss.org">www.jboss.org</a>.<br>
-
-<ul>
-
-<li>Web Beans 1.0.0.Beta1</li>
-<li>XNIO 1.2.0.GA</li>
-<li>JDK LogBridge 1.0.0.GA<li>
-<li>JBoss
-Transactions, v4.6.0.CR1A</li>
-<li>JBoss WebServices, v3.1.0.GA</li>
-<li>JBoss
-Messaging, v1.4.3.GA</li>
-<li>JBoss Web, v2.1.2.GA</li>
-<li>JBoss
-AOP, v2.0.1.GA</li>
-<li>JBoss EJB3, v1.0.0</li>
-<li>JBoss
-Microcontainer, v2.0.4.GA</li>
-<li>JBoss Security,
-v2.0.2.SP6</li>
-<li>Hibernate, v3.3.1.GA</li>
-<li>Hibernate
-Entity Manager, v3.4.0.GA</li>
-<li>Hibernate Annotations,
-v3.4.0.GA</li>
-<li>JBoss Cache POJO, v3.0.0.GA</li>
-<li>JBoss
-Cache Core, v3.0.2.GA</li><li>JBoss VFS, v2.1.0.GA</li>
- <li>JBoss Remoting, v2.5.0.SP2</li>
-
-<li>JGroups, v.2.6.8.GA</li>
-</ul>
-
<h1><a name="Details">Detailed Release Notes</a></h1>
-
-<h3>Includes versions: JBossAS-5.1.0.Beta1</h3>
- Release Notes - JBoss Application Server - Version JBossAS-5.1.0.Beta1
-
<h2> Bug
</h2>
<ul>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-4569'>JBAS-4569</a>] - ClusterPartition.stopService( ) fails when server is shut down
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5941'>JBAS-5941</a>] - NullPointerException in ClusteredSession
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5302'>JBAS-5302</a>] - StatefulHandleImpl should be able to use legacy invoker method to retrieve EJBObject
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6425'>JBAS-6425</a>] - AbstractSecurityDeployer assumes VFSDeploymentUnit
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5563'>JBAS-5563</a>] - Deployment from deploy-hasingleton broken
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6426'>JBAS-6426</a>] - "jboss_5.0.xsd" of JBoss 5.0GA is invalid
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5682'>JBAS-5682</a>] - Profile service does not include newly added content in getModifiedDeployments()
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6535'>JBAS-6535</a>] - java.lang.LinkageErrors seen during start of JBoss AS 5.1 with admin-console.war deployed
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5713'>JBAS-5713</a>] - NullPointerException in JavaEEComponentHelper with JBoss-5.0
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6553'>JBAS-6553</a>] - java:comp/env isn't available for SessionSynchronization callbacks
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5929'>JBAS-5929</a>] - Sub Pooling in JBossManagedConnectionPool MemoryLeak for sparse CRI coverage
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6574'>JBAS-6574</a>] - Typo in 'Installation And Getting Started Guide'
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6265'>JBAS-6265</a>] - Servlets should not be using the ejb3 user transaction
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6600'>JBAS-6600</a>] - Setting isolated=true on EarClassLoaderDeployer does not work
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6274'>JBAS-6274</a>] - scanning of the deployDir needs to happen after previous phases are deployed.
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6601'>JBAS-6601</a>] - CryptoUtil is missing from jboss-srp-client.jar (or jbosssx-client.jar)
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6276'>JBAS-6276</a>] - JmsConnectionRequestInfo needs have defaults set before doing allocateConnection()
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6606'>JBAS-6606</a>] - Specifying mdb-client-id in jboss.xml causes mdb deployments to fail
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6277'>JBAS-6277</a>] - JmsSessionFactoryImpl should look at MCF for client id when not set by the user
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6617'>JBAS-6617</a>] - Server failure when including aop metadata inside a sar inside a zip
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6282'>JBAS-6282</a>] - Eliminate duplication of servlet APIs in AS 5 distribution
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6618'>JBAS-6618</a>] - Statistic properties are not tied to runtime component
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6283'>JBAS-6283</a>] - Duplicate entry in jsf-api-sources.jar (javax/faces/component/html/package.html)
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6641'>JBAS-6641</a>] - copying all JBAS 4.2 testsuite apps into AS 5.1 deploy dir causes profile service errors and failure of server to start
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6287'>JBAS-6287</a>] - org.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCase fails when run with JDK 6
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6643'>JBAS-6643</a>] - restoring a null managed object fails
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6294'>JBAS-6294</a>] - Use Of IgnoreUndeployLegacyClusteredSessionNotificationPolicy Causes StackOverflow Errors
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6682'>JBAS-6682</a>] - StringIndexOutOfBoundsException in JvmRouteValve
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6298'>JBAS-6298</a>] - Unable to build the AS with IBM JDK 1.6
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6692'>JBAS-6692</a>] - JGroups protocol stacks need to have FC.ignore_synchronous_response set to "true"
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6328'>JBAS-6328</a>] - jmx-console: Back to MBean button causes error
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6694'>JBAS-6694</a>] - java.lang.OutOfMemoryErrors seen during automated Embedded Console testing
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6333'>JBAS-6333</a>] - <database>-persistence-service.xml is dependent on ChannelFactory even on NonClustered
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6705'>JBAS-6705</a>] - AS5 plugin: Creating a new Topic or Queue now results in this error - "java.lang.RuntimeException:Failed to process template"
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6336'>JBAS-6336</a>] - CleanShutdownInterceptor Can Log Container State Incorrectly
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6715'>JBAS-6715</a>] - Redployment intermittently fails
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6343'>JBAS-6343</a>] - JCA adapter inflow does not Roll back messages if using a non-xa connection factory in the JNDIProviderAdapter
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6718'>JBAS-6718</a>] - AS5 plugin: If the "use-java-context" property is left unset when creating a datasource, it now gets set to "false" by default instead of to "true"
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6360'>JBAS-6360</a>] - Multiple redeployments of ear when many 'watched files' are touched in the ear
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6719'>JBAS-6719</a>] - AS5 plugin: After creating a new Topic or Queue, the configuration properties are set to their default values instead of to the values that were specified during creation
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6367'>JBAS-6367</a>] - missing org.codehaus.plexus:plexus-utils:jar:1.5.6
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6736'>JBAS-6736</a>] - List operations for Topics and Queues (eg. List All Messages, List All Subscriptions, etc.) are not producing the correct results
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6373'>JBAS-6373</a>] - VFS cache should handle main context roots better
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6737'>JBAS-6737</a>] - contextRoot of webservicesType in jboss_5_0.xsd and jboss_5_1.xsd is not correct
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6400'>JBAS-6400</a>] - ExecutionContext returns the transaction timeout in seconds, but we use that argument to schedule the thread that is in milliseconds.
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6742'>JBAS-6742</a>] - Updates to managed properties no longer persisting when changes made through embedded console
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6407'>JBAS-6407</a>] - TestResourceAdapterTxInflow can't assume one phase commit
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6755'>JBAS-6755</a>] - Setting ObjectName ManagedProperties (eg. DLQ, serverPeer, expiryQueue) as removed=true causes Topic/Queue creation to fail
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6408'>JBAS-6408</a>] - Add 5_0_0_GA client to compatibility matrix tests
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6792'>JBAS-6792</a>] - callMethodOnPartition on MBeans extending HAServiceMBeanSupport not working
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6410'>JBAS-6410</a>] - JBoss Security (2.0.2.SP3) serialVersionUID breaks interoperability with external tools (e.g. JBoss Tools)
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6793'>JBAS-6793</a>] - IncompleteDeploymentException upon Stop'n'Start or Restart of EAR with nested WAR
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6420'>JBAS-6420</a>] - JBossWebRealm->hasUserDataPermission check with JBoss Security needs Subject
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6799'>JBAS-6799</a>] - Attempting to configure a Topic or Queue that has the "securityConfig" property unset results in an UndeclaredThrowableException
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6428'>JBAS-6428</a>] - HAPartition unable to start with IBM JDK 1.5 - net.jcip.annotations.ThreadSafe not found
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6800'>JBAS-6800</a>] - Ejb3HAPartitionDependencyDeployer adds dependency to non-clustered beans
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6434'>JBAS-6434</a>] - REGRESSION: org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6801'>JBAS-6801</a>] - After creating a Topic or Queue, the value of the "clustered" property is set to "false" even if the user set it to "true" during creation
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6439'>JBAS-6439</a>] - Non-DeploymentManager-based HASingletonDeploymentScanner impl results in deploy-hasingleton content removal
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6805'>JBAS-6805</a>] - java.lang.OutOfMemory: Heap Space during Runtime Discovery Scan
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6493'>JBAS-6493</a>] - AOPLister in web-console doesnt work for JBoss 4.2.* 5.0.*, 5.*, trunk
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6807'>JBAS-6807</a>] - Unable to form a cluster Branch_5_x (flush by coordinator at xyz failed)
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6497'>JBAS-6497</a>] - Dynamic webservice endpoint deployment doesn't propagate Module in attachments
+</ul>
+
+<h2> Feature Request
+</h2>
+<ul>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-2595'>JBAS-2595</a>] - JMX Resolver for JSF
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6501'>JBAS-6501</a>] - org.jboss.tools.SerialVersionUID doesn't use JBOSS_HOME/common/** jars
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5965'>JBAS-5965</a>] - Max file soft limit can not always be set to hard limit on Darwin (OS X)
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6507'>JBAS-6507</a>] - BeanMetaDataICF needs to delegate to AbstractInstanceClassFactory for managed object values
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5993'>JBAS-5993</a>] - Need to add ProfileService failed deployment tests
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6523'>JBAS-6523</a>] - ORB not found message is overly verbose
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6092'>JBAS-6092</a>] - Check and warn if system time is off on joining node
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6534'>JBAS-6534</a>] - Graceful shutdown of JBoss Web service does not wait for accepted requests to complete before stopping dependent services
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6142'>JBAS-6142</a>] - Include a more user friendly management and monitoring tool.
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6544'>JBAS-6544</a>] - STREAMING_STATE_TRANSFER configs use deprecated attribute
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6356'>JBAS-6356</a>] - Configure HA-JNDI automatic discovery socket via ServiceBindingManager
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6561'>JBAS-6561</a>] - Regression: MTTransactionManagerUnitTestCase.testCommitSameTxInTwoThreads() fails
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6629'>JBAS-6629</a>] - Apply ${jboss.server.log.threshold} to root logger
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6571'>JBAS-6571</a>] - JDK6 (JMX1.3) ObjectName queries are not working
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6644'>JBAS-6644</a>] - expose if the ManagementView was reloaded.
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6572'>JBAS-6572</a>] - serialVersionUID mismatch on RegexValidator.class since JSF 1.2_12 upgrade
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6650'>JBAS-6650</a>] - configurable upload dir of a DeploymentRepository
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6573'>JBAS-6573</a>] - serialVersionUID mismatch on ManagementViewImpl$ManagedOperationDelegate
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6653'>JBAS-6653</a>] - Switch to new classpools
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6602'>JBAS-6602</a>] - Log4jService should use the new JDKLevel class when setting log levels
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6678'>JBAS-6678</a>] - Upgrade to Hibvernate Search 3.1.1
</li>
-</ul>
-
-<h2> Feature Request
-</h2>
-<ul>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-1808'>JBAS-1808</a>] - Expose PreparedStatementCache via JMX
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6752'>JBAS-6752</a>] - Include the datasource name when the connection manager reports a ResourceException
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5221'>JBAS-5221</a>] - tx-connection-factory/no-tx-connection-factory need to be completed
-</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6232'>JBAS-6232</a>] - DeploymentTemplateInfo needs to support a clone
-</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6281'>JBAS-6281</a>] - Use IgnoreUndeployLegacyClusteredSessionNotificationPolicy as the default ClusteredSessionNotificationPolicy
-</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6390'>JBAS-6390</a>] - Add support for parsing IPv6 addresses in org.jnp.interfaces.NamingContext
-</li>
</ul>
-
-<h2> Patch
-</h2>
-<ul>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6319'>JBAS-6319</a>] - WAR deployment ObjectName should include virtual host
-</li>
-</ul>
-
-<h2> Quality Risk
-</h2>
-<ul>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6257'>JBAS-6257</a>] - Typo in firebird-ds.xml
-</li>
-</ul>
-
+
<h2> Task
</h2>
<ul>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-2525'>JBAS-2525</a>] - JSR-196: Java Authentication SPI for Container
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-4666'>JBAS-4666</a>] - MBean for new EjbDeployer
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-2602'>JBAS-2602</a>] - Next Generation Security Manager Service
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6038'>JBAS-6038</a>] - Examine use of SessionReplicationContext start/finishCacheActivity
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-3707'>JBAS-3707</a>] - HA/Failover RAR Functionality should be implemented in non-HA RARS.
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6466'>JBAS-6466</a>] - Log as TRACE not being able to find cache entry trying to be removed
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5240'>JBAS-5240</a>] - Log VM arguments in boot.log
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6552'>JBAS-6552</a>] - Track component updates - 5.1.0.CR1
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5246'>JBAS-5246</a>] - Open console support
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6626'>JBAS-6626</a>] - Order .jar before .war
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6156'>JBAS-6156</a>] - Track component updates
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6630'>JBAS-6630</a>] - Change default value for ${jboss.server.log.threshold} to INFO
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6171'>JBAS-6171</a>] - Remove "bootstrap" module from AS into its own Project
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6637'>JBAS-6637</a>] - Disable lock striping in JBoss Cache configs
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6195'>JBAS-6195</a>] - Fix JBossWS Integration
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6648'>JBAS-6648</a>] - provide different profile implementations
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6361'>JBAS-6361</a>] - log write to server.log does not append to the file as expected
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6649'>JBAS-6649</a>] - enable distribution of deployment contents to the deployers dir.
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6371'>JBAS-6371</a>] - Integrate Web Beans RI
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6659'>JBAS-6659</a>] - Create brew build of glassfish-jaxb version 2.1.9 so we can patch
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6375'>JBAS-6375</a>] - PreferredMasterElectionPolicy unnecessarily parses host/port every election
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6667'>JBAS-6667</a>] - Rename managed component subtype on TxConnectionFactoryDeploymentMetaData.java to be "Tx" rather than "XA"
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6411'>JBAS-6411</a>] - Show Java runtime information in boot.log
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6716'>JBAS-6716</a>] - add back securityConfig config property to JMS destination resources
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6417'>JBAS-6417</a>] - Move ejb3-timer-service.xml to docs/examples/ejb3
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6743'>JBAS-6743</a>] - start AS with xb.builder.useUnorderedSequence
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6423'>JBAS-6423</a>] - When JNDI cluster node definition method not available, make it more visible.
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6757'>JBAS-6757</a>] - Reorganize source that populates the server/xxx/conf dir
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6444'>JBAS-6444</a>] - remove commons-httpclient.jar from AS distribution
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6760'>JBAS-6760</a>] - Add extra check for before NPE in JavaEEComponentHelper
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6448'>JBAS-6448</a>] - Removing stale xmbean descriptors
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6780'>JBAS-6780</a>] - Get rid of DistributableSession interface
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6470'>JBAS-6470</a>] - Open console support blockers
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6786'>JBAS-6786</a>] - Update ManagedObjects for JBAS server related components to have unique types
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6492'>JBAS-6492</a>] - Include basic smoke tests of JTS into AS testsuite
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6798'>JBAS-6798</a>] - Change AS Build to not bring in jboss-ejb3-proxy
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6525'>JBAS-6525</a>] - the usage of DeploymentManger should be independent of isCopyContent
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6816'>JBAS-6816</a>] - Reduce verbose FINE logging from sun classes
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6526'>JBAS-6526</a>] - drop the DeploymentPhase from the profileservice-spi
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6830'>JBAS-6830</a>] - Update release notes for 5.1.0.CR1
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6555'>JBAS-6555</a>] - Enhance SerialVersionUIDUnitTestCase
-</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6556'>JBAS-6556</a>] - Remove org.jboss.test.ejb3.servlet.unit.HttpUtils
-</li>
</ul>
-<h2> Thirdparty Change
+<h2><a name="Library%20Updates">Thirdparty Change</a>
</h2>
<ul>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6385'>JBAS-6385</a>] - Upgrade jboss-javaee.jar to 5.0.1.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6739'>JBAS-6739</a>] - Synch with the latest patched jacorb version
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6409'>JBAS-6409</a>] - Upgrade to jboss-server-manager 1.0.1.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6756'>JBAS-6756</a>] - Use the latest patched version of xalan
</li>
</ul>
-<h2> Component Upgrade
+<h2>Component Upgrade
</h2>
<ul>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6334'>JBAS-6334</a>] - Update JBoss Messaging
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6027'>JBAS-6027</a>] - Upgrade jboss-metadata to 1.0.0.CR18
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6341'>JBAS-6341</a>] - Upgrade JBossWS Native to 3.1.0.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6469'>JBAS-6469</a>] - Update to JBossXB 2.0.1.GA
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6370'>JBAS-6370</a>] - Upgrade JGroups to 2.6.8
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6605'>JBAS-6605</a>] - JBoss Security upgrade to 2.0.3.SP1
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6430'>JBAS-6430</a>] - Upgrade EJB3 to 1.1.2
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6633'>JBAS-6633</a>] - Upgrade jboss-ha-server-api to 1.1.1.GA
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6433'>JBAS-6433</a>] - Upgrade JBossTS to 4.6
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6634'>JBAS-6634</a>] - Upgrade JBossWS Native to 3.1.1.GA
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6453'>JBAS-6453</a>] - Update AOP to 2.0.1.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6635'>JBAS-6635</a>] - Upgrade JAXB to 2.1.9.patch
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6454'>JBAS-6454</a>] - Update Web Beans to 1.0.0.BETA1
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6636'>JBAS-6636</a>] - Upgrade JBoss Cache to 3.1.0.CR1
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6455'>JBAS-6455</a>] - Update JBoss Cache to 3.0.2.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6639'>JBAS-6639</a>] - Upgrade JBossXacml 2.0.3
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6458'>JBAS-6458</a>] - Update JPA to 1.0.0-CR1
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6661'>JBAS-6661</a>] - Upgrade Web Beans to 1.0.0.PREVIEW
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6459'>JBAS-6459</a>] - Update VFS to 2.1.0.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6684'>JBAS-6684</a>] - Update EJB 3 to 1.1.3
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6460'>JBAS-6460</a>] - Update MDR to 2.0.1.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6691'>JBAS-6691</a>] - Upgrade JGroups to 2.6.9
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6461'>JBAS-6461</a>] - Update MC Managed to 2.0.0.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6726'>JBAS-6726</a>] - Update XNIO to 1.2.1.GA
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6462'>JBAS-6462</a>] - Update MC Kernel to 2.0.4.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6727'>JBAS-6727</a>] - Update JBoss Threads to 1.0.0.CR3
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6463'>JBAS-6463</a>] - Update CL to 2.0.4.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6729'>JBAS-6729</a>] - Update to JBoss LogBridge 1.0.0CR4
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6464'>JBAS-6464</a>] - Update Deployers to 2.0.5.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6730'>JBAS-6730</a>] - Update to JBoss LogManager 1.0.0.CR3
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6465'>JBAS-6465</a>] - Update Seam-Int to 5.0.2.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6740'>JBAS-6740</a>] - Upgrade JBoss Threads to 1.0.0.CR4
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6467'>JBAS-6467</a>] - Update to Security 2.0.2.SP7
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6761'>JBAS-6761</a>] - Upgrade common-core to 2.2.12
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6468'>JBAS-6468</a>] - Update to JBossXACML 2.0.3.CR1
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6778'>JBAS-6778</a>] - Update ha-server-cache-spi to 2.0.0.GA
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6473'>JBAS-6473</a>] - Update to JBoss Threads 1.0.0.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6779'>JBAS-6779</a>] - Update ha-server-cache-jbc to 2.0.0.CR1
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6474'>JBAS-6474</a>] - Update to XNIO 1.2.0.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6787'>JBAS-6787</a>] - Upgrade Remoting to 2.5.1
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6475'>JBAS-6475</a>] - Update to JDK LogBridge 1.0.0.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6826'>JBAS-6826</a>] - Upgrade to Common Core 2.2.13
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6476'>JBAS-6476</a>] - Update to Bootstrap 1.0.0-Beta-1
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6827'>JBAS-6827</a>] - Upgrade to VFS 2.1.1.GA
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6505'>JBAS-6505</a>] - Upgrade JBoss Cache to 3.0.3.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6837'>JBAS-6837</a>] - Upgrade to JBoss Web 2.1.3
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6542'>JBAS-6542</a>] - Update to jboss-common-core 2.2.11.GA
-</li>
</ul>
<h2> Sub-task
</h2>
<ul>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-2482'>JBAS-2482</a>] - Investigate integration of FORM auth with a SAML style identity provider
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5703'>JBAS-5703</a>] - Make HA-JNDI use wait for first positive response
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-3768'>JBAS-3768</a>] - Define initial persistent format of the profile repository
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6580'>JBAS-6580</a>] - org.jboss.test.web.test.JSFIntegrationUnitTestCase
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5523'>JBAS-5523</a>] - Add Availability functionality. To know when a ManagedComponent is running or stopped, etc
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6582'>JBAS-6582</a>] - org.jboss.test.ejb3.servlet.unit.ServletUnitTestCase
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5529'>JBAS-5529</a>] - Add support for JBAS, JBossWeb and JBossWeb connector components
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6598'>JBAS-6598</a>] - org.jboss.test.profileservice.testsecure.ProfileServiceUnitTestCase
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-5640'>JBAS-5640</a>] - Wars embedded in sars have discrepencies in deployment Name
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6599'>JBAS-6599</a>] - org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6137'>JBAS-6137</a>] - Make sure ProfileService is available remotely in a secured fashion
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6607'>JBAS-6607</a>] - XACMLDeployer to parse xacml config/policies in the deployment
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6218'>JBAS-6218</a>] - "org.jboss.util.NotImplementedException:Use a custom InstanceClassFactory" error occurs when trying to create XA or NoTX Datasource via ManagementView.applyTemplate()
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6608'>JBAS-6608</a>] - ACLDeployer to pick up ACL files
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6219'>JBAS-6219</a>] - ManagementView.getTemplate() should return a new copy of the DeploymentTemplateInfo on every call
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6631'>JBAS-6631</a>] - Make sure JBAS managed object has shutdown operation
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6272'>JBAS-6272</a>] - jrockit - org.jboss.test.jca.test.BaseConnectionManagerUnitTestCase.testAllocationRetryMultiThread
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6647'>JBAS-6647</a>] - "XAConnectionFactoryTemplate" and possibly other templates are missing from ManagementView
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6285'>JBAS-6285</a>] - Expose platform mbeans as ManagedComponents
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6654'>JBAS-6654</a>] - EJBVerifier21 should check messagingType for null
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6286'>JBAS-6286</a>] - Create a ManagedComponent for System properties
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6657'>JBAS-6657</a>] - managementView.load() fails to merge ServerInfo, ThreadPool, GlobalRequestProcessor, and Host ManagedObjects
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6325'>JBAS-6325</a>] - Add index entries
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6662'>JBAS-6662</a>] - Remove unnecessary use of MBeanRegistry/Entry
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6340'>JBAS-6340</a>] - Upgrade JBossWS Native to 3.0.5.GA
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6664'>JBAS-6664</a>] - "config-property" ManagedProperty in all ConnectionFactory and Datasource templates has wrong type
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6413'>JBAS-6413</a>] - Upgrade JBoss Security 2.0.2.SP6
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6668'>JBAS-6668</a>] - for Connection Factories, an extra prop.type config-prop is added to the "config-property" MapCompositeMetaType property every time managementView.updateComponent(connFactoryComponent) is called
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6472'>JBAS-6472</a>] - Update ProfileService spi
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6669'>JBAS-6669</a>] - when new items are added to the "config-property" composite ManagedProperty on a Datasource component, after updateComponent() is called, the items that were added are gone
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6490'>JBAS-6490</a>] - Upgrade Apache XML Security 1.4.2
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6670'>JBAS-6670</a>] - *.type config-props within "config-property" composite ManagedProperty are set to the corresponding connection factory prop's value, rather than its type
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6567'>JBAS-6567</a>] - Update JSF to 1.2_12
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6671'>JBAS-6671</a>] - on Connection Factory components, jndi-name, rar-name, and connection-definition ManagedPropertys should all be mandatory, in both templates and properties on existing components
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6581'>JBAS-6581</a>] - org.jboss.test.ejb3.jbas5713.unit.RefSecondJarUnitTestCase
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6672'>JBAS-6672</a>] - when null values are specified for ManagedProperties, then updateComponent() is called, the values are updated to incorrect defaults (e.g. "0" for integer properties)
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6583'>JBAS-6583</a>] - org.jboss.test.cluster.defaultcfg.test.ClusterPartitionManagedObjectsTestCase(Default-udp)
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6681'>JBAS-6681</a>] - UndeclaredThrowableException:ReflectionException:IllegalArgumentException on call to ManagementViewImpl.updateComponent() on Topic or Queue containing primitive int or boolean property with value of null
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6591'>JBAS-6591</a>] - org.jboss.test.deployers.spaces.test.SpacesUnitTestCase
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6683'>JBAS-6683</a>] - QueueTemplate and TopicTemplate templates are missing most of the ManagedProperties defined by the corresponding ComponentTypes - they only contain the "name" and "JNDIName" properties
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6596'>JBAS-6596</a>] - org.jboss.test.profileservice.override.*.JmsDestinationTestCases
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6686'>JBAS-6686</a>] - Unexpected parameters for JMS Topic managed operations
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/MODCLUSTER-5'>MODCLUSTER-5</a>] - HASingletonElectionPolicy suitable for mod_cluster
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6688'>JBAS-6688</a>] - expose ManagedProperties representing ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/MODCLUSTER-10'>MODCLUSTER-10</a>] - Define API and SPI for the LoadManager
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6689'>JBAS-6689</a>] - add support for activation policy metadata on ManagedProperties
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/MODCLUSTER-11'>MODCLUSTER-11</a>] - Default LoadManager impl
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6701'>JBAS-6701</a>] - DeploymentManager.remove() doesn't work for exploded apps that were deployed via distribute(copyContent=false)
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/MODCLUSTER-13'>MODCLUSTER-13</a>] - LoadMetricSource API
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6703'>JBAS-6703</a>] - XML config files persisted for Topics/Queues created via Profile Service still contain ManagementObjectClass annotation tags
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/MODCLUSTER-14'>MODCLUSTER-14</a>] - LoadMetricSource impl for gather JBossWeb request metrics
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6708'>JBAS-6708</a>] - once DeploymentManager.stop() is called on a WAR deployment, the next time managementView.getDeploymentNamesForType("war") is called, a deployment is no longer returned for that WAR
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/MODCLUSTER-16'>MODCLUSTER-16</a>] - LoadMetricSource impl for gathering VM metrics
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6709'>JBAS-6709</a>] - provide an API to determine the current state (i.e. Stopped/Started/Starting/Stopping/etc.) of a ManagedDeployment
</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6711'>JBAS-6711</a>] - if non-null values are set for ObjectName ManagedProperties (i.e. DLQ, serverPeer, or expiryQueue props) in Topic/Queue templates, applyTemplate() throws "IllegalArgumentException: Not handled value: CompositeValueSupport"
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6721'>JBAS-6721</a>] - a few Topic/Queue ManagedProperties have the wrong ViewUse
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6728'>JBAS-6728</a>] - 'local-transaction' prop is missing from the template for Tx ConnectionFactories
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6733'>JBAS-6733</a>] - Avoid re-reading expired sessions from distributed cache
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6741'>JBAS-6741</a>] - Upgrade jboss-server-manager to 1.0.2.GA and jboss-test to 1.1.4.GA
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6750'>JBAS-6750</a>] - get Admin Console WAR integrated into JBAS 5.1 distribution
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6751'>JBAS-6751</a>] - Need to map org.jboss.jms.message.JBossMessage into simple composite map in destination managed operations
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6762'>JBAS-6762</a>] - org.jboss.test.bootstrapdependencies.jbas5349.test.BootstrapDependenciesTestCase(EJB2Session)
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6765'>JBAS-6765</a>] - Setting ObjectName ManagedProperties (eg. DLQ, serverPeer, expiryQueue) to removed=true and value=null causes NullPointerException in StringObjectNameMetaMapper.unwrapMetaValue()
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6770'>JBAS-6770</a>] - JBoss-AS-5.1.x-compatibilityMatrix - server fails to start
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6774'>JBAS-6774</a>] - Upgrade EJB3 to 1.1.4
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6796'>JBAS-6796</a>] - "java.lang.IllegalArgumentException: Null type." error in DelegatingPersistencePlugin.getPlugin() when updating a Datasource or Connection Factory's properties with 'security-domain' prop with null security deployment type
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6804'>JBAS-6804</a>] - org.jboss.test.jacc.test.*PermissionsValidationTestCase
+</li>
</ul>
<!-- ======================================================= -->
More information about the jboss-cvs-commits
mailing list