[jboss-cvs] JBossAS SVN: r89231 - branches/Branch_5_x/build/docs.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed May 20 19:54:29 EDT 2009
Author: jason.greene at jboss.com
Date: 2009-05-20 19:54:29 -0400 (Wed, 20 May 2009)
New Revision: 89231
Modified:
branches/Branch_5_x/build/docs/readme.html
Log:
Update release notes
Modified: branches/Branch_5_x/build/docs/readme.html
===================================================================
--- branches/Branch_5_x/build/docs/readme.html 2009-05-20 23:53:14 UTC (rev 89230)
+++ branches/Branch_5_x/build/docs/readme.html 2009-05-20 23:54:29 UTC (rev 89231)
@@ -3,54 +3,19 @@
<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.GA 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.GA 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>Along with many bug fixes and enhancements, this is the first general release to include our new,
+ significantly improved <a href="http://www.jboss.org/embjopr">open-source console</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 +33,21 @@
</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 Web Console</b> - This release includes our new administration console. Several updates
+have been made since the CR1 release, including the introduction of WAR metrics. See the full
+release notes for the console <a href="http://www.jboss.org/community/wiki/EmbeddedJOPR120GAReleaseNotes">here</a>.</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. For more information about Web Beans see the documentation
+<a href="http://docs.jboss.org/webbeans/reference/1.0.0.PREVIEW1/en-US/html">here</a>.</li>
+
+<li><b>Farming Returns</b> - Due to popular demand, the farming service is back! 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.GA.
-<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>
@@ -301,12 +166,6 @@
<h2><a name="Configuration">Configuration Issues</a></h2>
-<ul>
- <li>The ejb3-timer-service.xml has moved from deploy to
-docs/examples/ejb3 to avoid the runtime overhead, since it's not used
-by default. If you want to use it, move it back to the deploy folder
-and set the <span style="font-family: monospace;" class="postbody">org.jboss.ejb3.timerservice.factory </span><span class="postbody">property to </span><span style="font-family: monospace;" class="postbody">org.jboss.ejb3.timerservice.quartz.QuartzTimerServiceFactory.</span></li>
-</ul>
<h4>From 5.0.0.GA</h4>
<p>JBossAS 5.0.0.GA introduces two new configuration, the <span style="font-family: monospace; font-weight: bold;">standard</span><span style="font-weight: bold;"> </span>and the <span style="font-family: monospace; font-weight: bold;">web</span> config.<br>
</p>
@@ -576,344 +435,232 @@
</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
-
+ Release Notes - JBoss Application Server - Version JBossAS-5.1.0.GA
+
<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-5936'>JBAS-5936</a>] - Wrong logging information is shown for components using slf4j (e.g. Hibernate)
</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-6227'>JBAS-6227</a>] - Only way to remove a managedcomponent is to remove its deployment
</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-6310'>JBAS-6310</a>] - Failure in loading classes due to thread stack overflow should be logged as an error.
</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-6500'>JBAS-6500</a>] - JMX View and ManagementView do not consistently reflect J2EE application state after undeployment
</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-6512'>JBAS-6512</a>] - ServiceBindingManagedObjectsTestCase.testPortsDefault regression
</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-6579'>JBAS-6579</a>] - Resolve JBoss AS 5.1.0 Test Suite Issues
</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-6592'>JBAS-6592</a>] - Eliminate duplication of CORBA OTS classes in AS 5.1.0 distribution
</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-6673'>JBAS-6673</a>] - VFS cache should handle main context roots better still an issue in 5.0.1
</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-6677'>JBAS-6677</a>] - Cleanup inactive timer service instances for Entity Beans
</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-6745'>JBAS-6745</a>] - org.jboss.test.cmp2.audit.test.AuditUnitTestCase failing with MySQL - miliseconds not supported
</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-6747'>JBAS-6747</a>] - JaasSecurityManagerService::CallbackHandlerClassName is not being used anywhere
</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-6764'>JBAS-6764</a>] - Embedded Console issues with standard config
</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-6768'>JBAS-6768</a>] - SubjectFactory usage in JCA needs review for the Datasource Encryption usecase
</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-6825'>JBAS-6825</a>] - AS 5 Plugin: User-created Connection Factory status is DOWN after server restart
</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-6832'>JBAS-6832</a>] - JBoss AS JVM Metrics stay the same through the console
</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-6848'>JBAS-6848</a>] - DataSourceDeploymentMetaData doesnt create property "isSameRMOverrideValue"
</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-6858'>JBAS-6858</a>] - SVC* variables in bin\service.bat need to be updated from "5.0" to "5.1"
</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-6860'>JBAS-6860</a>] - ManagedConnectionFactoryDeployment should look for both primitive and wrapper type setters before giving up when setting attributes
</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-6862'>JBAS-6862</a>] - ManagedDeploymentImpl unitMOs does not use name from @ManagementObjectID
</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-6872'>JBAS-6872</a>] - -Djboss.bind.address definition in run.conf ignored
</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-6874'>JBAS-6874</a>] - TimerImpl should set ACTIVE state before scheduling to avoid race condition
</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-6880'>JBAS-6880</a>] - BeanMetaDataICF not finding MetaMapper
</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-6904'>JBAS-6904</a>] - Ban org.hibernate:hibernate in favor of org.hibernate:hibernate-core
</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-6914'>JBAS-6914</a>] - useJBossWebLoader not working when set to true
</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-6921'>JBAS-6921</a>] - cache-invalidation-service.xml includes invalid JMS topic config
</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-6945'>JBAS-6945</a>] - InvocationContext on the serverside needs to use privileged block for getting TCCL
</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-6964'>JBAS-6964</a>] - XSLTServiceBindingValueSourceImpl is missing privileged blocks
</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>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6434'>JBAS-6434</a>] - REGRESSION: org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase
-</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>
-<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>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6497'>JBAS-6497</a>] - Dynamic webservice endpoint deployment doesn't propagate Module in attachments
-</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>
-<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>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6523'>JBAS-6523</a>] - ORB not found message is overly verbose
-</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>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6544'>JBAS-6544</a>] - STREAMING_STATE_TRANSFER configs use deprecated attribute
-</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6561'>JBAS-6561</a>] - Regression: MTTransactionManagerUnitTestCase.testCommitSameTxInTwoThreads() fails
-</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6571'>JBAS-6571</a>] - JDK6 (JMX1.3) ObjectName queries are not working
-</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>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6573'>JBAS-6573</a>] - serialVersionUID mismatch on ManagementViewImpl$ManagedOperationDelegate
-</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>
</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-5992'>JBAS-5992</a>] - Add a ManagedDeployment/ManagedComponent status servlet
</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>[<a href='https://jira.jboss.org/jira/browse/JBAS-6754'>JBAS-6754</a>] - add support for a run.conf equivalent file to run.bat, so environment variable settings can be externalized as they can be for run.sh
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6232'>JBAS-6232</a>] - DeploymentTemplateInfo needs to support a clone
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6785'>JBAS-6785</a>] - add default value to the ManagedProperty interface
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6281'>JBAS-6281</a>] - Use IgnoreUndeployLegacyClusteredSessionNotificationPolicy as the default ClusteredSessionNotificationPolicy
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6828'>JBAS-6828</a>] - Add a description property to ServiceBindingMetadata
</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>[<a href='https://jira.jboss.org/jira/browse/JBAS-6839'>JBAS-6839</a>] - Update slf4j Version, make logger serializable
</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>[<a href='https://jira.jboss.org/jira/browse/JBAS-6849'>JBAS-6849</a>] - extended twiddle functionality
</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>[<a href='https://jira.jboss.org/jira/browse/JBAS-6861'>JBAS-6861</a>] - Allow PKCS11 keystores to be used in JaasSecurityDomain
</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6873'>JBAS-6873</a>] - Explicitly configure JGroups diagnostics
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6876'>JBAS-6876</a>] - Configure binding interface via ServiceBindingManager
+</li>
+<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6927'>JBAS-6927</a>] - Update RuntimeComponentDispatcher
+</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-4154'>JBAS-4154</a>] - Get the server to run under a security manager
</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-6259'>JBAS-6259</a>] - Management interface for ServiceBindingManager
</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-6560'>JBAS-6560</a>] - Port crash recovery plugin in EAP4 to AS 5.1
</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-6642'>JBAS-6642</a>] - Make sure aop deployers work after they have been moved out of the as repo
</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-6772'>JBAS-6772</a>] - Track component updates - 5.1.0.GA
</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-6809'>JBAS-6809</a>] - Update to JBoss Naming 5.0.2.GA and add unit test for JBNAME-27
</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-6819'>JBAS-6819</a>] - The value of "Connections In Use Count" that gets displayed in the embedded console as the result of the "List Formatted Sub Pool Statistics" operation does not get updated after connections are closed
</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-6846'>JBAS-6846</a>] - Create testcase in AS testsuite for discovery disable option
</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-6853'>JBAS-6853</a>] - Pull the ServiceBindingManager out of the bootstrap
</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-6864'>JBAS-6864</a>] - Fix timeout issues in classloader leak test cases
</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-6875'>JBAS-6875</a>] - Have the naming service write its connection URL to a well defined place
</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-6887'>JBAS-6887</a>] - Bring in ejb3-endpoint-deployer into AS through component-matrix
</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-6905'>JBAS-6905</a>] - Test target tests-security-manager should use its own server configuration
</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-6908'>JBAS-6908</a>] - fix ordering of proxy-factory-config in standardjboss.xml
</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-6929'>JBAS-6929</a>] - Make HDScanner a Daemon Thread
</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-6931'>JBAS-6931</a>] - set property xb.builder.useUnorderedSequence in org.jboss.Main
</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-6940'>JBAS-6940</a>] - Reenable Tomcat SSL tests
</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-6946'>JBAS-6946</a>] - ReEnable JACC Security Manager Tests
</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>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6526'>JBAS-6526</a>] - drop the DeploymentPhase from the profileservice-spi
-</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>
-<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>
-<li>[<a href='https://jira.jboss.org/jira/browse/JBAS-6409'>JBAS-6409</a>] - Upgrade to jboss-server-manager 1.0.1.GA
-</li>
-</ul>
-
+
<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-6533'>JBAS-6533</a>] - Update JPA to 1.0.0.GA
</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-6564'>JBAS-6564</a>] - Include JBoss Negotiation 2.0.3.SP1
</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-6621'>JBAS-6621</a>] - Update jboss-managed to 2.1.0.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-6652'>JBAS-6652</a>] - Upgrade AOP to 2.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-6790'>JBAS-6790</a>] - Update JBC to 3.1.0.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-6791'>JBAS-6791</a>] - Upgrade jboss-ha-server-cache-jbc to 2.0.0.GA
</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-6835'>JBAS-6835</a>] - Upgrade JBossWS Native to 3.1.2.GA
</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-6840'>JBAS-6840</a>] - Upgrade JGroups to 2.6.10
</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-6851'>JBAS-6851</a>] - Update to transactions 4.6.1.GA
</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-6863'>JBAS-6863</a>] - Upgrade to jboss-cl 2.0.6.GA
</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-6882'>JBAS-6882</a>] - Upgrade EJB3 to 1.1.5
</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-6890'>JBAS-6890</a>] - Update slf4j to 1.5.6
</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-6891'>JBAS-6891</a>] - Update slf4j-jboss-logging to 1.0.2
</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-6892'>JBAS-6892</a>] - Update common-core to 2.2.14.GA
</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-6893'>JBAS-6893</a>] - Update jboss-ejb3-endpoint-deployers to 0.1.3
</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-6898'>JBAS-6898</a>] - Update jboss-logging-spi, jboss-logging-log4j, jboss-logging-jdk to 2.1.0.GA
</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-6899'>JBAS-6899</a>] - Update JBoss LogManager to 1.0.0.GA
</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-6900'>JBAS-6900</a>] - Update JBoss LogBridge to 1.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-6901'>JBAS-6901</a>] - Update JBoss Threads and JBoss Threads Metadata to 1.0.0.GA
</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-6902'>JBAS-6902</a>] - Update XNIO Metadata to 1.0.0.GA
</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-6903'>JBAS-6903</a>] - Upgrade Naming to 5.0.3.GA
</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-6907'>JBAS-6907</a>] - Update Metadata to 1.0.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>
-<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-5552'>JBAS-5552</a>] - Synchronized deployment repositories across the cluster
</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-6066'>JBAS-6066</a>] - JSR-196 integration for web layer (Client-CERT)
</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-6330'>JBAS-6330</a>] - Hotdeployment management interface
</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-6594'>JBAS-6594</a>] - org.jboss.test.profileservice.test.ServiceBindingManagedObjectsTestCase
</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-6622'>JBAS-6622</a>] - Dynamic creation of vhost managed objects
</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-6623'>JBAS-6623</a>] - Web Application (WAR) additional metrics and operations
</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-6676'>JBAS-6676</a>] - Suport for exposing JMX bean as ManagedObject
</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-6773'>JBAS-6773</a>] - org.jboss.test.jmx.test.UndeployBrokenPackageUnitTestCase
</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-6812'>JBAS-6812</a>] - Handle Path, Privileged and other attributes from context.xml
</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-6823'>JBAS-6823</a>] - Stopping a JMS destination through the console does not change its availability
</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-6836'>JBAS-6836</a>] - org.jboss.test.xml.DynamicLoginConfigUnitTestCase.testJASPIConfig
</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-6850'>JBAS-6850</a>] - Override jms xmbean descriptors
</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-6857'>JBAS-6857</a>] - AS5.1: Password Masking for MC Beans
</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-6869'>JBAS-6869</a>] - types field is null in all RAR ManagedDeployments
</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-6885'>JBAS-6885</a>] - when connected to PS via remote client, calling getComponentsByType(), passing some type that actually is deployed, a "ClassNotFoundException: org.jboss.profileservice.management.ManagedOperationDelegate" is thrown
</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-6894'>JBAS-6894</a>] - PerTxEntityInstanceCache->removeTimerServiceIfAllCancelledOrExpired needs privileged blocks
</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-6895'>JBAS-6895</a>] - org.jboss.test.profileservice.test.ServerManagedObjectsTestCase
</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-6896'>JBAS-6896</a>] - org.jboss.test.tm.test.MTTransactionManagerUnitTestCase(jts)
</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-6897'>JBAS-6897</a>] - tests-security-manager regressions
</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-6906'>JBAS-6906</a>] - Tests containing persistence units fail to deploy due to NoClassDefFoundError
</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-6911'>JBAS-6911</a>] - ManagementView api extensions
</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-6922'>JBAS-6922</a>] - Regressions in compatibility-matrix tests
</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/MODCLUSTER-10'>MODCLUSTER-10</a>] - Define API and SPI for the LoadManager
-</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/MODCLUSTER-11'>MODCLUSTER-11</a>] - Default LoadManager impl
-</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/MODCLUSTER-13'>MODCLUSTER-13</a>] - LoadMetricSource API
-</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/MODCLUSTER-14'>MODCLUSTER-14</a>] - LoadMetricSource impl for gather JBossWeb request metrics
-</li>
-<li>[<a href='https://jira.jboss.org/jira/browse/MODCLUSTER-16'>MODCLUSTER-16</a>] - LoadMetricSource impl for gathering VM metrics
-</li>
</ul>
-
<!-- ======================================================= -->
<hr>
<h2><a name="Documentation">Documentation
More information about the jboss-cvs-commits
mailing list