More cleanup.

immutant · Aug 3, 2015 · f054041 · f054041
1 parent bace6b9
commit f054041
Showing 1 changed file with 18 additions and 18 deletions.
diff --git a/news/2015-08-03-datomic.md b/news/2015-08-03-datomic.md
@@ -19,7 +19,7 @@ working with the current stable release of Immutant ([2.0.2]):
 
 1. Immutant 2.0.x uses the [JMS 2.0] API, which didn't appear in
    HornetQ until 2.4.0, so 2.4.x is required.
-2. The HornetQ transactor is running HornetQ 2.3.x, and a 2.4.x client
+2. The Datomic transactor is running HornetQ 2.3.x, and a 2.4.x client
    can't connect to a 2.3.x server, so 2.3.x is required.
 
 Hence our pickle.
@@ -57,29 +57,28 @@ which isn't great.
 
 ## Option 2 - In WildFly Only
 
-Inside the [WildFly] application server, Immutant doesn't directly use
-any on the HornetQ APIs, and just uses the JMS API to communicate with
-the HornetQ provided by WildFly. That HornetQ is ClassLoader-isolated,
-which means your application can bring in its own version of HornetQ
-(in this case, 2.3.x via Datomic), which can be used without issue.
+An Immutant application [deployed] to a [WildFly] application server
+doesn't directly use any on the HornetQ APIs, and instead uses the JMS
+API to communicate with the HornetQ provided by WildFly. That HornetQ
+is ClassLoader-isolated, which means your application can bring in its
+own version of HornetQ (in this case, 2.3.x via Datomic), which can be
+used without issue.
 
 But this means you have to do all of your development against an
 application running inside WildFly, which isn't a great development
 experience. With our ["dev" war], you can still have a REPL-driven
 process, but it is definitely more painful than out-of-container
 development.
 
-## Option 3 - Use Recent Incrementals/future 2.1.0
+## Option 3 - Use Recent Incrementals, i.e. 2.1.0
 
-For Immutant 2.1.0, we're working on supporting
-[Red Hat JBoss Enterprise Application Platform] \(which is a mouthful,
-so we'll just call it EAP for short). EAP is the commercialized
-version of the open source application server (WildFly), and the
-current version (6.4.0) is based off an older WildFly that uses
-HornetQ 2.3.x. We'll cover what EAP support really means in a future
-blog post - what matters today is that changes we've made in Immutant
-to support EAP allow you to use Immutant messaging with Datomic both
-in and out of WildFly (and soon EAP).
+For the soon-to-be-released Immutant 2.1.0, we're working on
+supporting [Red Hat JBoss Enterprise Application Platform] \(which is
+a mouthful, so we'll just call it EAP). EAP is the commercialized version of Red Hat's open source JBoss Application Server (now known as WildFly), and the current version (6.4.0) is based off an older
+WildFly that uses HornetQ 2.3.x. We'll cover what EAP support really
+means in a future blog post - what matters today is that changes we've
+made in Immutant to support EAP allow you to use Immutant messaging
+with Datomic both in and out of WildFly (and soon EAP).
 
 The only issues with this option is you have to use a recent
 incremental build of Immutant until we release 2.1.0, and do a few
@@ -95,7 +94,7 @@ minimum to get things working is:
                ;; org.immutant/messaging requires this, but Datomic doesn't
                ;; bring it in, so we have to depend on it explicitly
                [org.hornetq/hornetq-jms-server "2.3.17.Final"
-                :exclusions [org.jboss.jbossts.jts/jbossjts-jacorb]]
+                :exclusions [org.jboss.jbossts.jts/jbossjts-jacorb]]]
 </pre>
 
 Now that you have it working, you probably want to get rid of all of
@@ -141,7 +140,8 @@ with Immutant, you can always find us on
 [2.0.2]: /news/2015/06/22/announcing-2-0-2/
 [JMS 2.0]: http://www.oracle.com/technetwork/articles/java/jms20-1947669.html
 [incremental]: /builds/2x/
-[messaging features]: http://immutant.org/documentation/current/apidoc/immutant.messaging.html
+[messaging features]: /documentation/current/apidoc/immutant.messaging.html
+[deployed]: /documentation/current/apidoc/guide-wildfly.html
 [WildFly]: http://wildfly.org/
 ["dev" war]: https://github.com/immutant/lein-immutant/blob/master/docs/deployment.md
 [Red Hat JBoss Enterprise Application Platform]: https://www.redhat.com/en/technologies/jboss-middleware/application-platform