JBossTS jbossjta-integration.
JBossTS - JBoss Transaction Service. JTA, JTS and XTS (WS-AT, WS-BA).
Here is the list of declaration for jbossjta-integration. If you use Maven you can use the following code to add the dependency for this POM file.
<dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossjta-integration</artifactId> <version>4.16.3.Final</version> </dependency>
If you think this Maven repository POM file listing for jbossjta-integration is inappropriate, such as containing malicious code/tools or violating the copyright, please email info at java2s dot com, thanks.
Name:LGPL 2.1
URL: http://www.gnu.org/licenses/lgpl-2.1.html.
The jbossjta-integration-4.16.3.Final has 14 dependencies.The most popular ones are listed in the following table along with their categories and number of artifacts depending on them.
Category | Artifact | Depended By Count |
---|---|---|
JBoss | jboss-corba-ots-spi 6.0.0.CR1 SPI to be implemented by CORBA OTS providers for JBoss 6.0.0 | 5 |
JBoss | jboss-remoting 2.5.3 JBoss Remoting 2 | 5 |
XML | dom4j 1.6.1 dom4j: the flexible XML framework for Java | 343 |
The following plugins are used in the jbossjta-integration-4.16.3.Final.jar
The following packages are defined in the jbossjta-integration-4.16.3.Final.jar
com.arjuna.ats.internal.jbossatx.jta com.arjuna.ats.internal.jbossatx.jta.jca com.arjuna.ats.jbossatx com.arjuna.ats.jbossatx.jta com.arjuna.ats.jbossatx.logging
Here is the content of the POM file.
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <!-- JBoss, Home of Professional Open Source Copyright 2009, Red Hat Middleware LLC, and individual contributors as indicated by the @author tags. See the copyright.txt in the distribution for a full listing of individual contributors. This copyrighted material is made available to anyone wishing to use, modify, copy, or redistribute it subject to the terms and conditions of the GNU Lesser General Public License, v. 2.1. This program is distributed in the hope that it will be useful, but WITHOUT A WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License, v.2.1 along with this distribution; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. (C) 2009, @author JBoss Inc. (jonathan.halliday@redhat.com) --> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossjta-integration</artifactId> <packaging>jar</packaging> <version>4.16.3.Final</version> <name>JBossTS jbossjta-integration</name> <description>JBossTS - JBoss Transaction Service. JTA, JTS and XTS (WS-AT, WS-BA)</description> <url>http://www.jboss.org/jbosstm/</url> <issueManagement> <system>JIRA</system> <url>https://jira.jboss.org/jira/browse/JBTM/</url> </issueManagement> <ciManagement> <system>hudson</system> <url>http://hudson.qa.jboss.com/hudson/view/JBossTS/</url> </ciManagement> <licenses> <license> <name>LGPL 2.1</name> <url>http://www.gnu.org/licenses/lgpl-2.1.html</url> </license> </licenses> <scm> <connection>scm:svn:http://anonsvn.jboss.org/repos/labs/labs/jbosstm/</connection> <developerConnection>scm:svn:https://svn.jboss.org/repos/labs/labs/jbosstm/</developerConnection> <url>http://fisheye.jboss.org/browse/JBossTS/</url> </scm> <repositories> <repository> <id>jboss-public-repository-group</id> <name>JBoss Public Maven Repository Group</name> <url>https://repository.jboss.org/nexus/content/groups/public/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </repository> </repositories> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <configuration> <outputDirectory>@extdir@</outputDirectory> <overWriteReleases>false</overWriteReleases> <overWriteSnapshots>false</overWriteSnapshots> <overWriteIfNewer>true</overWriteIfNewer> <excludeTransitive>true</excludeTransitive> <stripVersion>true</stripVersion> </configuration> </plugin> </plugins> </build> <dependencyManagement> <dependencies> <dependency> <!-- https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/jboss/as/jboss-as-parent/7.1.0.Beta1b/jboss-as-parent-7.1.0.Beta1b.pom --> <groupId>org.jboss.as</groupId> <artifactId>jboss-as-parent</artifactId> <version>7.1.1.Final</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> <dependencies> <!-- We mostly get our dependency *versions* transitively though the AS pom above. Thus dependencies here should not specify a version unless they are not used in the AS or we explicitly need a different version. --> <!-- combined deps for the entire JBossTS. At some point we need to modularize this for different builds --> <!-- XTS also requires commons-codec (transitive via httpclient?) and commons-httpclient to compile the localjunit module. needed for test only, not XTS runtime dep. --> <!--<dependency>--> <!--<groupId>commons-codec</groupId>--> <!--<artifactId>commons-codec</artifactId>--> <!--</dependency>--> <dependency> <groupId>commons-httpclient</groupId> <artifactId>commons-httpclient</artifactId> <version>3.1-jbossorg-1</version> </dependency> <!-- commons-logging, jcl-over-slf4j, slf4j-api, slf4j-simple all just test time deps for localjunit? --> <!--<dependency>--> <!--<groupId>commons-logging</groupId>--> <!--<artifactId>commons-logging</artifactId>--> <!--</dependency>--> <!--<dependency>--> <!--<groupId>org.slf4j</groupId>--> <!--<artifactId>jcl-over-slf4j</artifactId>--> <!--</dependency>--> <!--<dependency>--> <!--<groupId>org.slf4j</groupId>--> <!--<artifactId>slf4j-api</artifactId>--> <!--</dependency>--> <!--<dependency>--> <!--<groupId>org.slf4j</groupId>--> <!--<artifactId>slf4j-simple</artifactId>--> <!--</dependency>--> <!-- JTA (local: ArjunaJTA/jta and remote: ArjunaJTS/jtax) need JTA and JCA (for tx inflow) apis. --> <dependency> <!-- JTA API --> <groupId>org.jboss.spec.javax.transaction</groupId> <artifactId>jboss-transaction-api_1.1_spec</artifactId> </dependency> <dependency> <!-- JCA API --> <groupId>org.jboss.ironjacamar</groupId> <artifactId>ironjacamar-spec-api</artifactId> <scope>provided</scope> </dependency> <!-- unit tests use junit4 and some use byteman --> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <!--<version>4.8.1</version>--> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.byteman</groupId> <artifactId>byteman</artifactId> <version>${byteman-version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.byteman</groupId> <artifactId>byteman-install</artifactId> <version>${byteman-version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.byteman</groupId> <artifactId>byteman-submit</artifactId> <version>${byteman-version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.byteman</groupId> <artifactId>byteman-bmunit</artifactId> <version>${byteman-version}</version> <scope>test</scope> </dependency> <!-- txbridge uses the dtest addon --> <dependency> <groupId>org.jboss.byteman</groupId> <artifactId>byteman-dtest</artifactId> <version>${byteman-version}</version> <scope>test</scope> </dependency> <!-- build system uses emma for code coverage metrics --> <dependency> <groupId>emma</groupId> <artifactId>emma</artifactId> <version>2.0.5312</version> </dependency> <dependency> <groupId>emma</groupId> <artifactId>emma_ant</artifactId> <version>2.0.5312</version> </dependency> <!-- HornetQ Journal based object store requires HornetQ core, at least until HORNETQ-274 is done --> <dependency> <groupId>org.hornetq</groupId> <artifactId>hornetq-core</artifactId> </dependency> <dependency> <groupId>org.jboss.netty</groupId> <artifactId>netty</artifactId> <!--<version>3.2.0.Final</version>--> </dependency> <!-- installation as a service requires the wrapper, but is an optional deployment model --> <dependency> <groupId>tanukisoft</groupId> <artifactId>wrapper</artifactId> <version>3.2.3</version> </dependency> <!-- JTS requires jacorb --> <dependency> <groupId>org.jacorb</groupId> <artifactId>jacorb</artifactId> </dependency> <dependency> <groupId>jacorb</groupId> <artifactId>idl</artifactId> <version>2.3.1jboss.patch01-brew</version><!-- TODO AS7 --> </dependency> <!-- atsintegration (i.e. the JBossAS glue code) requires some app server bits. --> <dependency> <groupId>org.jboss.logmanager</groupId> <artifactId>jboss-logmanager</artifactId> </dependency> <dependency> <groupId>org.jboss</groupId> <artifactId>jboss-transaction-spi</artifactId> </dependency> <dependency> <groupId>org.jboss.integration</groupId> <artifactId>jboss-corba-ots-spi</artifactId> <version>6.0.0.CR1</version><!-- TODO AS7 src includes newer version of this, so its pom does not. --> </dependency> <!-- qa test suite - JBossAS integration code. (no longer used) Also txbrige test suite - replace with org.jboss.as.server.Bootstrap (see AS7 ServerInModuleStartupTestCase for example) or arq --> <dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-server-manager</artifactId> <version>1.0.4.Final</version><!-- TODO AS7 --> </dependency> <dependency> <groupId>org.jboss.spec.javax.ejb</groupId> <artifactId>jboss-ejb-api_3.1_spec</artifactId> </dependency> <!--remoting not actually used except by obsolete qa/as tests? --> <dependency> <groupId>org.jboss.remoting</groupId> <artifactId>jboss-remoting</artifactId> <version>2.5.3</version><!-- TODO AS7 --> </dependency> <!-- naming not actually used? --> <!--<dependency>--> <!--<groupId>org.jboss.naming</groupId>--> <!--<artifactId>jnp-client</artifactId>--> <!--</dependency>--> <!-- XTS: --> <dependency> <groupId>org.jboss.spec.javax.servlet</groupId> <artifactId>jboss-servlet-api_3.0_spec</artifactId> </dependency> <!-- test time dep only - XTS TestRunnerXMLServlet --> <dependency> <groupId>dom4j</groupId> <artifactId>dom4j</artifactId> <version>1.6.1</version> </dependency> <!-- <dependency> <groupId>com.sun.xml.bind</groupId> <artifactId>jaxb-api</artifactId> </dependency> --> <!--<dependency>--> <!--<groupId>org.jboss.logging</groupId>--> <!--<artifactId>jboss-logging-spi</artifactId>--> <!--<version>2.2.0.CR1</version>--> <!--</dependency>--> <!-- https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/logging/jboss-logging/ --> <dependency> <groupId>org.jboss.logging</groupId> <artifactId>jboss-logging</artifactId> </dependency> <!-- https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/logging/jboss-logging-processor/ from beta5 --> <!-- https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/logging/jboss-logging-tools/ --> <dependency> <groupId>org.jboss.logging</groupId> <artifactId>jboss-logging-processor</artifactId> </dependency> <!--<dependency>--> <!--<groupId>stax</groupId>--> <!--<artifactId>stax-api</artifactId>--> <!--</dependency>--> <!--<dependency>--> <!--<groupId>org.jboss.ws.native</groupId>--> <!--<artifactId>jbossws-native-core</artifactId>--> <!--</dependency>--> <dependency> <groupId>org.jboss.ws</groupId> <artifactId>jbossws-api</artifactId> </dependency> <!-- <dependency> <groupId>javax.xml.ws</groupId> <artifactId>jaxws-api</artifactId> </dependency> --> <!-- txbridge demo --> <dependency> <groupId>org.hibernate.javax.persistence</groupId> <artifactId>hibernate-jpa-2.0-api</artifactId> </dependency> </dependencies> <properties> <byteman-version>1.6.0</byteman-version> </properties> </project>