Author: buildbot
Date: Wed Apr 10 10:21:52 2013
New Revision: 857967
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/58-migration-guide.html
websites/production/activemq/content/activemq-580-release.html
websites/production/activemq/content/cache/main.pageCache
Modified: websites/production/activemq/content/58-migration-guide.html
==============================================================================
--- websites/production/activemq/content/58-migration-guide.html (original)
+++ websites/production/activemq/content/58-migration-guide.html Wed Apr 10
10:21:52 2013
@@ -72,20 +72,18 @@
<tr>
<td valign="top" width="100%">
<div class="wiki-content maincontent">
-<p>There are two important changes in 5.8 that may require some code change</p>
+<p>There are some changes in 5.8 that may require some code change</p>
<ol><li>New modules may effect your maven pom dependencies<br clear="none">
- <tt>activemq-core</tt> has been replaced with <tt>activemq-client</tt> and
<tt>activemq-broker</tt>. The various message stores have their own
activemq-xx-store module. The uber module <tt>activemq-all</tt>
remains.</li><li>Changed JMX Mbean ObjectNames will effect scripts or tools
that directly reference Mbean names<br clear="none">
- All mbeans now share the type=Broker attribute, which gives them containment.
In this way, consumers hang off of destinations, which hang off the broker.<br
clear="none">
- The different Mbean types are identified by the presence of specific
identifiers in their ObjectNames. The mapping from old to new ObjectName is as
follows:
+<tt>activemq-core</tt> has been replaced with <tt>activemq-client</tt> and
<tt>activemq-broker</tt>. The various message stores have their own
activemq-xx-store module. The uber module <tt>activemq-all</tt>
remains.</li><li>Changed JMX Mbean ObjectNames will effect scripts or tools
that directly reference Mbean names<br clear="none">
+All mbeans now share the type=Broker attribute, which gives them containment.
In this way, consumers hang off of destinations, which hang off the broker.<br
clear="none">
+The different Mbean types are identified by the presence of specific
identifiers in their ObjectNames. The mapping from old to new ObjectName is as
follows:
<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh">Type</th><th colspan="1" rowspan="1"
class="confluenceTh">Old Name</th><th colspan="1" rowspan="1"
class="confluenceTh">New Name</th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">Broker</td><td colspan="1" rowspan="1"
class="confluenceTd">Type=Broker</td><td colspan="1" rowspan="1"
class="confluenceTd">type=Broker</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">Destination</td><td colspan="1" rowspan="1"
class="confluenceTd">Type=Queue|Topic,Destination=<destination
identifier></td><td colspan="1" rowspan="1"
class="confluenceTd">type=Broker,destinationType=Queue|Topic,destinationName=<destination
identifier></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">Connector</td><td colspan="1" rowspan="1"
class="confluenceTd">Type=Connector</td><td colspan="1" rowspan="1"
class="confluenceTd">type=Broker,connector=clientConnectors</td></tr><t
r><td colspan="1" rowspan="1" class="confluenceTd">NetworkConnector</td><td
colspan="1" rowspan="1" class="confluenceTd">Type=NetworkConnector</td><td
colspan="1" rowspan="1"
class="confluenceTd">type=Broker,connector=networkConnectors</td></tr><tr><td></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">Connection</td><td colspan="1"
rowspan="1" class="confluenceTd">Type=Connection</td><td colspan="1"
rowspan="1"
class="confluenceTd">type=Broker,connector=*,connectionViewType=remoteAddress|clientId</td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Old Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> New Name </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> Broker </td><td colspan="1" rowspan="1"
class="confluenceTd"> Type=Broker </td><td colspan="1" rowspan="1"
class="confluenceTd"> type=Broker </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> Destination </td><td colspan="1" rowspan="1"
class="confluenceTd"> Type=Queue|Topic,Destination=<destination
identifier> </td><td colspan="1" rowspan="1" class="confluenceTd">
type=Broker,destinationType=Queue|Topic,destinationName=<destination
identifier> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
Connector </td><td colspan="1" rowspan="1" class="confluenceTd"> Type=Connector
</td><td colspan="1" rowspan="1" class="confluenceTd">
type=Broker,connector=clien
tConnectors </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
NetworkConnector </td><td colspan="1" rowspan="1" class="confluenceTd">
Type=NetworkConnector </td><td colspan="1" rowspan="1" class="confluenceTd">
type=Broker,connector=networkConnectors </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> Connection </td><td colspan="1" rowspan="1"
class="confluenceTd"> Type=Connection </td><td colspan="1" rowspan="1"
class="confluenceTd">
type=Broker,connector=*,connectionViewType=remoteAddress|clientId
</td></tr></tbody></table>
</div>
-</li><li>OSGi integration has changed, so that now much better mechanism using
OSGi managed service factory and possibility to configure broker and web
console using config admin. For more information take a look at <a shape="rect"
href="osgi-integration.html" title="OSGi Integration">OSGi
Integration</a></li></ol>
-
-
-
-
+</li><li>OSGi integration has changed. The full details are at <a shape="rect"
href="osgi-integration.html" title="OSGi Integration">OSGi Integration</a>. In
summary:
+ <ol><li>There is a single uber OSGI bundle</li><li>The broker and
webconsole are now configured via config admin pid files through an OSGi
managed service factory.</li></ol>
+ </li></ol>
</div>
</td>
Modified: websites/production/activemq/content/activemq-580-release.html
==============================================================================
--- websites/production/activemq/content/activemq-580-release.html (original)
+++ websites/production/activemq/content/activemq-580-release.html Wed Apr 10
10:21:52 2013
@@ -80,20 +80,18 @@
<ul><li><a shape="rect" href="amqp.html" title="AMQP">AMQP</a></li><li>new
feature modules and activemq-client module allowing smaller
foorprint</li><li>management via <a shape="rect"
href="rest.html#REST-RESTRestManagement">REST</a> with <a shape="rect"
class="external-link" href="http://www.jolokia.org/"; rel="nofollow">jolokia</a>
jmx to http bridge</li><li>Includes <a shape="rect" class="external-link"
href="http://camel.apache.org/camel-2103-release.html";>Apache Camel
2.10.3</a></li><li>Java 7 support (compiled with jdk6 and validated with
jdk7)</li><li><a shape="rect" href="pure-master-slave.html" title="Pure Master
Slave">Pure Master Slave</a> no longer supported</li></ul>
-<p>There are two important changes in 5.8 that may require some code change</p>
+<p>There are some changes in 5.8 that may require some code change</p>
<ol><li>New modules may effect your maven pom dependencies<br clear="none">
- <tt>activemq-core</tt> has been replaced with <tt>activemq-client</tt> and
<tt>activemq-broker</tt>. The various message stores have their own
activemq-xx-store module. The uber module <tt>activemq-all</tt>
remains.</li><li>Changed JMX Mbean ObjectNames will effect scripts or tools
that directly reference Mbean names<br clear="none">
- All mbeans now share the type=Broker attribute, which gives them containment.
In this way, consumers hang off of destinations, which hang off the broker.<br
clear="none">
- The different Mbean types are identified by the presence of specific
identifiers in their ObjectNames. The mapping from old to new ObjectName is as
follows:
+<tt>activemq-core</tt> has been replaced with <tt>activemq-client</tt> and
<tt>activemq-broker</tt>. The various message stores have their own
activemq-xx-store module. The uber module <tt>activemq-all</tt>
remains.</li><li>Changed JMX Mbean ObjectNames will effect scripts or tools
that directly reference Mbean names<br clear="none">
+All mbeans now share the type=Broker attribute, which gives them containment.
In this way, consumers hang off of destinations, which hang off the broker.<br
clear="none">
+The different Mbean types are identified by the presence of specific
identifiers in their ObjectNames. The mapping from old to new ObjectName is as
follows:
<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh">Type</th><th colspan="1" rowspan="1"
class="confluenceTh">Old Name</th><th colspan="1" rowspan="1"
class="confluenceTh">New Name</th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">Broker</td><td colspan="1" rowspan="1"
class="confluenceTd">Type=Broker</td><td colspan="1" rowspan="1"
class="confluenceTd">type=Broker</td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">Destination</td><td colspan="1" rowspan="1"
class="confluenceTd">Type=Queue|Topic,Destination=<destination
identifier></td><td colspan="1" rowspan="1"
class="confluenceTd">type=Broker,destinationType=Queue|Topic,destinationName=<destination
identifier></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd">Connector</td><td colspan="1" rowspan="1"
class="confluenceTd">Type=Connector</td><td colspan="1" rowspan="1"
class="confluenceTd">type=Broker,connector=clientConnectors</td></tr><t
r><td colspan="1" rowspan="1" class="confluenceTd">NetworkConnector</td><td
colspan="1" rowspan="1" class="confluenceTd">Type=NetworkConnector</td><td
colspan="1" rowspan="1"
class="confluenceTd">type=Broker,connector=networkConnectors</td></tr><tr><td></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd">Connection</td><td colspan="1"
rowspan="1" class="confluenceTd">Type=Connection</td><td colspan="1"
rowspan="1"
class="confluenceTd">type=Broker,connector=*,connectionViewType=remoteAddress|clientId</td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Type </th><th colspan="1" rowspan="1"
class="confluenceTh"> Old Name </th><th colspan="1" rowspan="1"
class="confluenceTh"> New Name </th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> Broker </td><td colspan="1" rowspan="1"
class="confluenceTd"> Type=Broker </td><td colspan="1" rowspan="1"
class="confluenceTd"> type=Broker </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> Destination </td><td colspan="1" rowspan="1"
class="confluenceTd"> Type=Queue|Topic,Destination=<destination
identifier> </td><td colspan="1" rowspan="1" class="confluenceTd">
type=Broker,destinationType=Queue|Topic,destinationName=<destination
identifier> </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
Connector </td><td colspan="1" rowspan="1" class="confluenceTd"> Type=Connector
</td><td colspan="1" rowspan="1" class="confluenceTd">
type=Broker,connector=clien
tConnectors </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
NetworkConnector </td><td colspan="1" rowspan="1" class="confluenceTd">
Type=NetworkConnector </td><td colspan="1" rowspan="1" class="confluenceTd">
type=Broker,connector=networkConnectors </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> Connection </td><td colspan="1" rowspan="1"
class="confluenceTd"> Type=Connection </td><td colspan="1" rowspan="1"
class="confluenceTd">
type=Broker,connector=*,connectionViewType=remoteAddress|clientId
</td></tr></tbody></table>
</div>
-</li><li>OSGi integration has changed, so that now much better mechanism using
OSGi managed service factory and possibility to configure broker and web
console using config admin. For more information take a look at <a shape="rect"
href="osgi-integration.html" title="OSGi Integration">OSGi
Integration</a></li></ol>
-
-
-
-
+</li><li>OSGi integration has changed. The full details are at <a shape="rect"
href="osgi-integration.html" title="OSGi Integration">OSGi Integration</a>. In
summary:
+ <ol><li>There is a single uber OSGI bundle</li><li>The broker and
webconsole are now configured via config admin pid files through an OSGi
managed service factory.</li></ol>
+ </li></ol>
<h2><a shape="rect"
name="ActiveMQ5.8.0Release-GettingtheBinaryDistributions"></a>Getting the
Binary Distributions</h2>
Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
