svn commit: r1041950 - /websites/production/activemq/content/activemq-website/58-migration-guide.html

[jbertram]

Author: jbertram
Date: Sat Mar 16 02:56:04 2019
New Revision: 1041950

Log:
Fix table formatting

Modified:
    
websites/production/activemq/content/activemq-website/58-migration-guide.html

Modified: 
websites/production/activemq/content/activemq-website/58-migration-guide.html
==============================================================================
--- 
websites/production/activemq/content/activemq-website/58-migration-guide.html 
(original)
+++ 
websites/production/activemq/content/activemq-website/58-migration-guide.html 
Sat Mar 16 02:56:04 2019
@@ -117,16 +117,18 @@
 <ol>
   <li>New modules may effect your maven pom dependencies<br />
 <code class="highlighter-rouge">activemq-core</code> has been replaced with 
<code class="highlighter-rouge">activemq-client</code> and <code 
class="highlighter-rouge">activemq-broker</code>. The various message stores 
have their own activemq-xx-store module. The uber module <code 
class="highlighter-rouge">activemq-all</code> remains.</li>
-  <li>Changed JMX Mbean ObjectNames will effect scripts or tools that directly 
reference Mbean names<br />
+  <li>
+    <p>Changed JMX Mbean ObjectNames will effect scripts or tools that 
directly reference Mbean names<br />
 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 
/>
-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="highlighter-rouge"><div class="highlight"><pre 
class="highlight"><code>    Type|Old Name|New Name
-    ---|---|---
-    Broker|Type=Broker|type=Broker
-    Destination|Type=Queue\|Topic,Destination=&lt;destination 
identifier&gt;|type=Broker,destinationType=Queue|Topic,destinationName=&lt;destination
 identifier&gt;
-    Connector|Type=Connector|type=Broker,connector=clientConnectors|
-    
NetworkConnector|Type=NetworkConnector|type=Broker,connector=networkConnectors
-    
Connection|Type=Connectiontype=Broker,connector=*,connectionViewType=remoteAddress\|clientId
+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:</p>
+
+    <div class="highlighter-rouge"><div class="highlight"><pre 
class="highlight"><code>Type|Old Name|New Name
+---|---|---
+Broker|Type=Broker|type=Broker
+Destination|Type=Queue\|Topic,Destination=&lt;destination 
identifier&gt;|type=Broker,destinationType=Queue\|Topic,destinationName=&lt;destination
 identifier&gt;
+Connector|Type=Connector|type=Broker,connector=clientConnectors
+NetworkConnector|Type=NetworkConnector|type=Broker,connector=networkConnectors
+Connection|Type=Connection|type=Broker,connector=*,connectionViewType=remoteAddress\|clientId
 </code></pre></div>    </div>
   </li>
   <li>OSGi integration has changed. The full details are at <a 
href="osgi-integration.html">OSGi Integration</a>. In summary: