[jboss-svn-commits] JBL Code SVN: r33151 - in labs/jbosstm/trunk: ArjunaJTS and 1 other directories.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Fri May 28 13:39:15 EDT 2010
Author: mmusgrov
Date: 2010-05-28 13:39:15 -0400 (Fri, 28 May 2010)
New Revision: 33151
Added:
labs/jbosstm/trunk/rhq-plugin/build.xml
Modified:
labs/jbosstm/trunk/ArjunaJTS/INSTALL
labs/jbosstm/trunk/Build.txt
labs/jbosstm/trunk/build.xml
Log:
JBTM-719 RHQ plugin for the transaction manager
Modified: labs/jbosstm/trunk/ArjunaJTS/INSTALL
===================================================================
--- labs/jbosstm/trunk/ArjunaJTS/INSTALL 2010-05-28 17:37:21 UTC (rev 33150)
+++ labs/jbosstm/trunk/ArjunaJTS/INSTALL 2010-05-28 17:39:15 UTC (rev 33151)
@@ -183,35 +183,32 @@
In any compliant JMX browser (such as jconsole) there should appear an
MBean with the name
- jboss.jta:type=ObjectStore,id=<id>
+ jboss.jta:type=ObjectStore
This MBean corresponds to the object store and provides a naming context
for other MBeans (for example in a JMX client such as jconsole the MBeans
will be displayed in the form of a tree control). The various MBeans
corresponding to this ObjectStore will have names prefixed by this
-'top level' MBean. Each MBean also exposes a 'refresh' operation
-that causes the instrumentation to check whether any new ObjectStore
-records have been created or whether old ones have been removed.
+'top level' MBean.
Note: if this bean does not appear in the JMX browser check that the
been is being initialised in transaction-jboss-beans.xml:
-
- <bean name="ObjectStoreBrowserBean" class="com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBean">
- <constructor factoryClass="com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBean"
- factoryMethod="getObjectStoreBrowserBean"/>
- <demand state="Create">ObjectStoreEnvironmentBean</demand>
+ <bean name="ObjectStoreBrowserBean" class="com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser">
+ ...
</bean>
If JBossTS is deployed in the JBoss application server then JMX
instrumentation of the ObjectStore is enabled by default. It can be disabled
-by setting the property jmxEnabled on the ObjectStoreEnvironmentBean in the
-transaction-jboss-beans.xml file. The property only effects ObjectStore
-MBeans (it will be renamed to something more specific in the next release).
+commenting out the ObjectStoreBrowserBean bean definition in the file
+transaction-jboss-beans.xml file. Furthermore, if the JBossTS JOPR plugin
+(see below for details) is copied to the admin console deploy directory then
+the sam information is available via the JBoss AS Admin Console.
-When JBossTS is deployed stand alone you need to create the 'top level'
-MBean programmatically by calling the following static Java method:
+The JMX instrumentation is also available when running JBossTS in stand-alone
+mode. Simply instantiate an object of type com.hp.mwtests.ts.arjuna.tools.ObjStoreBrowser
+and initialise it with a valid set of types for handling ObjectStore records. These types
+can be set using a setTypes() method via a properties file on the classpath.
+Please refer to the unit tests in the src distribution for more details.
-com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreTypeBean::getObjectStoreBrowserBean()
-
Tools Deployment
----------------
@@ -224,3 +221,7 @@
the JMX console (http://.../jmx-console) and click on the service named
EmbeddedTools.
+Note that the embedded tools will be deprecated in favour of the JOPR plugin
+for JBossTS transaction management. This is available as a jar in the install
+bin directory (jbossts-jopr-plugin.jar) which should be installed in the
+embedded JOPR plugin directory ($JBOSS_HOME/common/deploy/admin-console.war/plugins)
Modified: labs/jbosstm/trunk/Build.txt
===================================================================
--- labs/jbosstm/trunk/Build.txt 2010-05-28 17:37:21 UTC (rev 33150)
+++ labs/jbosstm/trunk/Build.txt 2010-05-28 17:39:15 UTC (rev 33151)
@@ -26,7 +26,8 @@
jbossjta = jta + JBossAS integration code.
jbossjts = jts + JBossAS integration code.
-In addition the XTS (web services transactions) and txbridge (XTS/JTA integration) modules may be built separately.
+In addition the XTS (web services transactions), txbridge (XTS/JTA integration) and rhq-plugin modules may be built
+separately.
See http://jbossts.blogspot.com/2007/07/trying-to-put-jbossts-into-perspective_6770.html or the docs for more
on the module architecture.
@@ -56,4 +57,4 @@
to **/*JDBC4.java instead. This is required as the JDBC3 and 4 APIs are not compatible.
A handful of unit tests build and run as part of the normal build. Most test coverage is in the form of integration
-tests which reside in the qa/ directory. These are built but not run automatically. See qa/README.txt for usage.
\ No newline at end of file
+tests which reside in the qa/ directory. These are built but not run automatically. See qa/README.txt for usage.
Modified: labs/jbosstm/trunk/build.xml
===================================================================
--- labs/jbosstm/trunk/build.xml 2010-05-28 17:37:21 UTC (rev 33150)
+++ labs/jbosstm/trunk/build.xml 2010-05-28 17:39:15 UTC (rev 33151)
@@ -92,6 +92,7 @@
<target name="jbossall" depends="jbossjts">
<ant dir="XTS" target="clean"/>
<ant dir="XTS" target="install"/>
+ <ant dir="rhq-plugin" target="install"/>
</target>
<target name="antbuildsystem" depends="clean">
@@ -120,6 +121,13 @@
</then>
</if>
+ <if>
+ <available file="rhq-plugin"/>
+ <then>
+ <ant dir="rhq-plugin" target="clean"/>
+ </then>
+ </if>
+
<ant dir="atsintegration" target="clean"/>
<delete dir="build"/>
Added: labs/jbosstm/trunk/rhq-plugin/build.xml
===================================================================
--- labs/jbosstm/trunk/rhq-plugin/build.xml (rev 0)
+++ labs/jbosstm/trunk/rhq-plugin/build.xml 2010-05-28 17:39:15 UTC (rev 33151)
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" ?>
+<project name="rhq-plugin" default="maven:package" basedir=".">
+
+ <property name="maven.project.build.directory" value="target"/>
+ <property name="maven.artifactId" value="jbossts-jopr-plugin"/>
+ <property name="pluginjar" value="${basedir}/${maven.project.build.directory}/${maven.artifactId}.jar"/>
+
+ <target name="maven:package" depends="clean">
+ <exec executable="mvn" dir="${basedir}">
+ <arg value="package"/>
+ </exec>
+ </target>
+
+ <target name="install" depends="maven:package">
+ <copy file="${pluginjar}" todir="../install/bin"/>
+ </target>
+
+ <target name="clean">
+ <exec executable="mvn" dir="${basedir}">
+ <arg value="clean"/>
+ </exec>
+ <delete dir="build"/>
+ </target>
+</project>
More information about the jboss-svn-commits
mailing list