Download JAR files tagged by scenarios with all dependencies
locator-rest-service from group org.talend.esb.locator.service (version 5.2.0)
Group: org.talend.esb.locator.service Artifact: locator-rest-service
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact locator-rest-service
Group org.talend.esb.locator.service
Version 5.2.0
Last update 25. October 2012
Organization not specified
URL Not specified
License not specified
Dependencies amount 4
Dependencies cxf-api, cxf-rt-frontend-jaxws, cxf-rt-frontend-jaxrs, locator-service-common,
There are maybe transitive dependencies!
Group org.talend.esb.locator.service
Version 5.2.0
Last update 25. October 2012
Organization not specified
URL Not specified
License not specified
Dependencies amount 4
Dependencies cxf-api, cxf-rt-frontend-jaxws, cxf-rt-frontend-jaxrs, locator-service-common,
There are maybe transitive dependencies!
org.talend.esb.job.deployer from group org.talend.esb.job (version 4.2.1)
Group: org.talend.esb.job Artifact: org.talend.esb.job.deployer
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact org.talend.esb.job.deployer
Group org.talend.esb.job
Version 4.2.1
Last update 01. September 2011
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.talend.esb.job
Version 4.2.1
Last update 01. September 2011
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
org.talend.esb.job.converter from group org.talend.esb.job (version 4.2.1)
Group: org.talend.esb.job Artifact: org.talend.esb.job.converter
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact org.talend.esb.job.converter
Group org.talend.esb.job
Version 4.2.1
Last update 01. September 2011
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies bndlib, slf4j-api,
There are maybe transitive dependencies!
Group org.talend.esb.job
Version 4.2.1
Last update 01. September 2011
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies bndlib, slf4j-api,
There are maybe transitive dependencies!
org.talend.esb.job.command from group org.talend.esb.job (version 4.2.1)
Group: org.talend.esb.job Artifact: org.talend.esb.job.command
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact org.talend.esb.job.command
Group org.talend.esb.job
Version 4.2.1
Last update 01. September 2011
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.talend.esb.job
Version 4.2.1
Last update 01. September 2011
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
derby-all from group org.talend.esb (version 10.8.1.2)
2 downloads
Artifact derby-all
Group org.talend.esb
Version 10.8.1.2
Last update 21. June 2011
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.talend.esb
Version 10.8.1.2
Last update 21. June 2011
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
com.sap.conn.jco.sapjco3 from group com.github.easonjim (version 3.0.11)
The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system.
It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java
to SAP System as well as SAP System to Java calls.
- All SAP Connectors are licensed without additional license fees as part of the respective solution or component license.
However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems /
SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed.
- The redistribution of any connector is not allowed.
- All SAP users accessing application functionality through the relevant connector are required to be licensed under a
respective solution or component license.
To use the SAP JCo with the jco-jar project, you need to either install the SAP JCo jar downloaded from SAP to your local
Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b):
(a) mvn install:install-file -DgroupId=com.github.easonjim -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.11 -Dpackaging=jar -Dfile=path/to/sapjco3.jar
(b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=com.github.easonjim -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.11 -Dpackaging=jar -Dfile=path/to/sapjco3.jar
0 downloads
Artifact com.sap.conn.jco.sapjco3
Group com.github.easonjim
Version 3.0.11
Last update 22. May 2019
Organization easonjim@github
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group com.github.easonjim
Version 3.0.11
Last update 22. May 2019
Organization easonjim@github
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
com.sap.conn.jco.sapjco3 from group org.hibersap (version 3.0.0)
The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system.
It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java
to SAP System as well as SAP System to Java calls.
- All SAP Connectors are licensed without additional license fees as part of the respective solution or component license.
However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems /
SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed.
- The redistribution of any connector is not allowed.
- All SAP users accessing application functionality through the relevant connector are required to be licensed under a
respective solution or component license.
To use the SAP JCo with the Hibersap project, you need to either install the SAP JCo jar downloaded from SAP to your local
Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b):
(a) mvn install:install-file -DgroupId=org.hibersap -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.15 -Dpackaging=jar -Dfile=path/to/sapjco3.jar
(b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=org.hibersap -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.15 -Dpackaging=jar -Dfile=sapjco3.jar
Artifact com.sap.conn.jco.sapjco3
Group org.hibersap
Version 3.0.0
Last update 08. March 2017
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hibersap
Version 3.0.0
Last update 08. March 2017
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
sapjco3 from group org.hibersap (version 3.0)
The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system.
It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java
to SAP System as well as SAP System to Java calls.
- All SAP Connectors are licensed without additional license fees as part of the respective solution or component license.
However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems /
SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed.
- The redistribution of any connector is not allowed.
- All SAP users accessing application functionality through the relevant connector are required to be licensed under a
respective solution or component license.
To use the SAP JCo with the Hibersap project, you need to either install the SAP JCo jar downloaded from SAP to your local
Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b):
(a) mvn install:install-file -DgroupId=org.hibersap -DartifactId=sapjco3 -Dversion=3.0.12 -Dpackaging=jar -Dfile=path/to/sapjco3.jar
(b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=org.hibersap -DartifactId=sapjco3 -Dversion=3.0.12 -Dpackaging=jar -Dfile=sapjco3.jar
4219 downloads
Artifact sapjco3
Group org.hibersap
Version 3.0
Last update 06. March 2015
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hibersap
Version 3.0
Last update 06. March 2015
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
hibersap-sapjco3 from group org.hibersap (version 3.0-RC01)
The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system.
It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java
to SAP System as well as SAP System to Java calls.
- All SAP Connectors are licensed without additional license fees as part of the respective solution or component license.
However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems /
SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed.
- The redistribution of any connector is not allowed.
- All SAP users accessing application functionality through the relevant connector are required to be licensed under a
respective solution or component license.
To use the SAP JCo with the Hibersap project, you need to either install the SAP JCo jar downloaded from SAP to your local
Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b):
(a) mvn install:install-file -DgroupId=org.hibersap -DartifactId=sapjco3 -Dversion=3.0 -Dpackaging=jar -Dfile=path/to/sapjco3.jar
(b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=org.hibersap -DartifactId=sapjco3 -Dversion=3.0 -Dpackaging=jar -Dfile=sapjco3.jar
87 downloads
Artifact hibersap-sapjco3
Group org.hibersap
Version 3.0-RC01
Last update 09. April 2014
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group org.hibersap
Version 3.0-RC01
Last update 09. April 2014
Organization akquinet tech@spree GmbH
URL http://service.sap.com/connectors
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
pact-jvm-provider-spring_2.12 from group au.com.dius (version 3.6.15)
# Pact Spring/JUnit runner
## Overview
Library provides ability to play contract tests against a provider using Spring & JUnit.
This library is based on and references the JUnit package, so see the [Pact JUnit 4](../pact-jvm-provider-junit) or [Pact JUnit 5](../pact-jvm-provider-junit5) providers for more details regarding configuration using JUnit.
Supports:
- Standard ways to load pacts from folders and broker
- Easy way to change assertion strategy
- Spring Test MockMVC Controllers and ControllerAdvice using MockMvc standalone setup.
- MockMvc debugger output
- Multiple @State runs to test a particular Provider State multiple times
- **au.com.dius.pact.provider.junit.State** custom annotation - before each interaction that requires a state change,
all methods annotated by `@State` with appropriate the state listed will be invoked.
**NOTE:** For publishing provider verification results to a pact broker, make sure the Java system property `pact.provider.version`
is set with the version of your provider.
## Example of MockMvc test
```java
@RunWith(RestPactRunner.class) // Custom pact runner, child of PactRunner which runs only REST tests
@Provider("myAwesomeService") // Set up name of tested provider
@PactFolder("pacts") // Point where to find pacts (See also section Pacts source in documentation)
public class ContractTest {
//Create an instance of your controller. We cannot autowire this as we're not using (and don't want to use) a Spring test runner.
@InjectMocks
private AwesomeController awesomeController = new AwesomeController();
//Mock your service logic class. We'll use this to create scenarios for respective provider states.
@Mock
private AwesomeBusinessLogic awesomeBusinessLogic;
//Create an instance of your controller advice (if you have one). This will be passed to the MockMvcTarget constructor to be wired up with MockMvc.
@InjectMocks
private AwesomeControllerAdvice awesomeControllerAdvice = new AwesomeControllerAdvice();
//Create a new instance of the MockMvcTarget and annotate it as the TestTarget for PactRunner
@TestTarget
public final MockMvcTarget target = new MockMvcTarget();
@Before //Method will be run before each test of interaction
public void before() {
//initialize your mocks using your mocking framework
MockitoAnnotations.initMocks(this);
//configure the MockMvcTarget with your controller and controller advice
target.setControllers(awesomeController);
target.setControllerAdvice(awesomeControllerAdvice);
}
@State("default", "no-data") // Method will be run before testing interactions that require "default" or "no-data" state
public void toDefaultState() {
target.setRunTimes(3); //let's loop through this state a few times for a 3 data variants
when(awesomeBusinessLogic.getById(any(UUID.class)))
.thenReturn(myTestHelper.generateRandomReturnData(UUID.randomUUID(), ExampleEnum.ONE))
.thenReturn(myTestHelper.generateRandomReturnData(UUID.randomUUID(), ExampleEnum.TWO))
.thenReturn(myTestHelper.generateRandomReturnData(UUID.randomUUID(), ExampleEnum.THREE));
}
@State("error-case")
public void SingleUploadExistsState_Success() {
target.setRunTimes(1); //tell the runner to only loop one time for this state
//you might want to throw exceptions to be picked off by your controller advice
when(awesomeBusinessLogic.getById(any(UUID.class)))
.then(i -> { throw new NotCoolException(i.getArgumentAt(0, UUID.class).toString()); });
}
}
```
## Using a Spring runner (version 3.5.7+)
You can use `SpringRestPactRunner` instead of the default Pact runner to use the Spring test annotations. This will
allow you to inject or mock spring beans.
For example:
```java
@RunWith(SpringRestPactRunner.class)
@Provider("pricing")
@PactBroker(protocol = "https", host = "${pactBrokerHost}", port = "443",
authentication = @PactBrokerAuth(username = "${pactBrokerUser}", password = "${pactBrokerPassword}"))
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.DEFINED_PORT)
public class PricingServiceProviderPactTest {
@MockBean
private ProductClient productClient; // This will replace the bean with a mock in the application context
@TestTarget
@SuppressWarnings(value = "VisibilityModifier")
public final Target target = new HttpTarget(8091);
@State("Product X010000021 exists")
public void setupProductX010000021() throws IOException {
reset(productClient);
ProductBuilder product = new ProductBuilder()
.withProductCode("X010000021");
when(productClient.fetch((Set<String>) argThat(contains("X010000021")), any())).thenReturn(product);
}
@State("the product code X00001 can be priced")
public void theProductCodeX00001CanBePriced() throws IOException {
reset(productClient);
ProductBuilder product = new ProductBuilder()
.withProductCode("X00001");
when(productClient.find((Set<String>) argThat(contains("X00001")), any())).thenReturn(product);
}
}
```
### Using Spring Context Properties (version 3.5.14+)
From version 3.5.14 onwards, the SpringRestPactRunner will look up any annotation expressions (like `${pactBrokerHost}`)
above) from the Spring context. For Springboot, this will allow you to define the properties in the application test properties.
For instance, if you create the following `application.yml` in the test resources:
```yaml
pactbroker:
host: "your.broker.local"
port: "443"
protocol: "https"
auth:
username: "<your broker username>"
password: "<your broker password>"
```
Then you can use the defaults on the `@PactBroker` annotation.
```java
@RunWith(SpringRestPactRunner.class)
@Provider("My Service")
@PactBroker(
authentication = @PactBrokerAuth(username = "${pactbroker.auth.username}", password = "${pactbroker.auth.password}")
)
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
public class PactVerificationTest {
```
### Using a random port with a Springboot test (version 3.5.14+)
If you use a random port in a springboot test (by setting `SpringBootTest.WebEnvironment.RANDOM_PORT`), you can use the
`SpringBootHttpTarget` which will get the application port from the spring application context.
For example:
```java
@RunWith(SpringRestPactRunner.class)
@Provider("My Service")
@PactBroker
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
public class PactVerificationTest {
@TestTarget
public final Target target = new SpringBootHttpTarget();
}
```
Group: au.com.dius Artifact: pact-jvm-provider-spring_2.12
Show all versions Show documentation Show source
Show all versions Show documentation Show source
1 downloads
Artifact pact-jvm-provider-spring_2.12
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 5
Dependencies pact-jvm-provider-junit_2.12, spring-boot-starter-test, spring-webmvc, javax.servlet-api, jackson-datatype-joda,
There are maybe transitive dependencies!
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 5
Dependencies pact-jvm-provider-junit_2.12, spring-boot-starter-test, spring-webmvc, javax.servlet-api, jackson-datatype-joda,
There are maybe transitive dependencies!
Page 23 from 24 (items total 232)