Spring Extras.
Non-core functionality provided by Spring such as transactions, remoting, data sources, etc..
Here is the list of declaration for mule-module-spring-extras. If you use Maven you can use the following code to add the dependency for this POM file.
<dependency> <groupId>org.mule.modules</groupId> <artifactId>mule-module-spring-extras</artifactId> <version>2.0.0-RC3</version> </dependency>
If you think this Maven repository POM file listing for mule-module-spring-extras is inappropriate, such as containing malicious code/tools or violating the copyright, please email info at java2s dot com, thanks.
The mule-module-spring-extras-2.0.0-RC3 has 7 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 |
---|---|---|
Development | mule-module-builders 2.0.0-RC3 Standard configuration builders for Mule | 5 |
Data Structure | commons-collections 3.2 Types that extend and augment the Java Collections Framework. | 366 |
Development | mule-module-client 2.0.0-RC3 MuleClient is a simple interface for Mule clients to send and receive events from local or remote Mule Servers. | 21 |
The following packages are defined in the mule-module-spring-extras-2.0.0-RC3.jar
org.mule.module.spring.events org.mule.module.spring.i18n org.mule.module.spring.interceptor org.mule.module.spring.remoting org.mule.module.spring.transaction
Here is the content of the POM file.
<?xml version="1.0" encoding="UTF-8"?> <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"> <modelVersion>4.0.0</modelVersion> <parent> <groupId>org.mule.modules</groupId> <artifactId>mule-modules</artifactId> <version>2.0.0-RC3</version> </parent> <artifactId>mule-module-spring-extras</artifactId> <!--<packaging>bundle</packaging>--> <name>Spring Extras</name> <description> Non-core functionality provided by Spring such as transactions, remoting, data sources, etc. </description> <profiles> <profile> <id>osgi</id> <build> <plugins> <plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <configuration> <instructions> <Export-Package> org.mule.module.spring.config, org.mule.module.spring.events, org.mule.module.spring.remoting, org.mule.module.spring.transaction </Export-Package> </instructions> </configuration> </plugin> </plugins> </build> </profile> </profiles> <dependencies> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-aop</artifactId> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-jdbc</artifactId> <exclusions> <exclusion> <groupId>org.springframework</groupId> <artifactId>spring-support</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-jms</artifactId> <exclusions> <exclusion> <artifactId>commons-pool</artifactId> <groupId>commons-pool</groupId> </exclusion> <exclusion> <groupId>org.springframework</groupId> <artifactId>spring-support</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-web</artifactId> </dependency> <!-- Used by MuleEventMulticaster --> <dependency> <groupId>org.mule.modules</groupId> <artifactId>mule-module-builders</artifactId> <version>${version}</version> </dependency> <dependency> <groupId>org.mule.modules</groupId> <artifactId>mule-module-management</artifactId> <version>${version}</version> </dependency> <!-- Used by SpringTransactionFactory --> <!-- TODO: verify whether this dependency is really required. --> <dependency> <groupId>org.apache.geronimo.specs</groupId> <artifactId>geronimo-jms_1.1_spec</artifactId> </dependency> <!-- TODO this is a hack. Duplicate declaration (original is in the top pom.xml) makes Spring happy to compile when run from the project root folder, otherwise it cannot find classes from commons-logging. It seems m2 dependency visibility hierarchy is limited to 1 level deep. --> <dependency> <groupId>commons-collections</groupId> <artifactId>commons-collections</artifactId> <version>3.2</version> </dependency> <!-- For test cases only --> <!-- TODO This can't be in the parent pom.xml because it creates a cyclic dependency: mule-tests-functional -> mule-module-builders -> mule-tests-functional --> <dependency> <groupId>org.mule.tests</groupId> <artifactId>mule-tests-functional</artifactId> <version>${version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.mule.modules</groupId> <artifactId>mule-module-client</artifactId> <version>${version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.mule.transports</groupId> <artifactId>mule-transport-http</artifactId> <version>${version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.mule.transports</groupId> <artifactId>mule-transport-vm</artifactId> <version>${version}</version> <scope>test</scope> </dependency> </dependencies> </project>