Download JAR files tagged by verifying with all dependencies
camel-crypto from group org.wildfly.swarm (version 2018.5.0)
The crypto component is used for signing and verifying exchanges using the Signature Service of the Java Cryptographic Extension (JCE).
Artifact camel-crypto
Group org.wildfly.swarm
Version 2018.5.0
Last update 02. May 2018
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies camel-crypto, camel-core,
There are maybe transitive dependencies!
Group org.wildfly.swarm
Version 2018.5.0
Last update 02. May 2018
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies camel-crypto, camel-core,
There are maybe transitive dependencies!
edifatto from group org.databene (version 3.0.1)
'Edifatto' is an open source software library for parsing,
generating and verifying EDIFACT and X12 documents written by Volker Bergmann.
Artifact edifatto
Group org.databene
Version 3.0.1
Last update 06. July 2016
Organization Volker Bergmann
URL http://databene.org/edifatto
License Apache License 2.0
Dependencies amount 5
Dependencies databene-commons, databene-formats, swingx-all, freemarker, slf4j-api,
There are maybe transitive dependencies!
Group org.databene
Version 3.0.1
Last update 06. July 2016
Organization Volker Bergmann
URL http://databene.org/edifatto
License Apache License 2.0
Dependencies amount 5
Dependencies databene-commons, databene-formats, swingx-all, freemarker, slf4j-api,
There are maybe transitive dependencies!
sched-assist-spi-caldav-integrationtest from group org.jasig.sched-assist (version 1.1.4)
Module including an integration test for verifying Scheduling Assistant compatibility with a remote CalDAV server.
Group: org.jasig.sched-assist Artifact: sched-assist-spi-caldav-integrationtest
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact sched-assist-spi-caldav-integrationtest
Group org.jasig.sched-assist
Version 1.1.4
Last update 28. September 2012
Organization not specified
URL Not specified
License not specified
Dependencies amount 4
Dependencies sched-assist-mock, sched-assist-spi-caldav, spring-test, junit,
There are maybe transitive dependencies!
Group org.jasig.sched-assist
Version 1.1.4
Last update 28. September 2012
Organization not specified
URL Not specified
License not specified
Dependencies amount 4
Dependencies sched-assist-mock, sched-assist-spi-caldav, spring-test, junit,
There are maybe transitive dependencies!
andromda-cartridge-testsuite from group org.andromda.cartridges (version 3.3)
Provides a Cartridge Test Suite, for testing cartridges throughout the cartridge lifecycle. Tests include verifying actual vs. expected output.
Artifact andromda-cartridge-testsuite
Group org.andromda.cartridges
Version 3.3
Last update 10. December 2009
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies commons-io, junit,
There are maybe transitive dependencies!
Group org.andromda.cartridges
Version 3.3
Last update 10. December 2009
Organization not specified
URL Not specified
License not specified
Dependencies amount 2
Dependencies commons-io, junit,
There are maybe transitive dependencies!
verification-seamless from group com.sinch.android.sdk.verification (version 2.7.0)
Seamless verification allows verifying phone number without any user interaction. Sinch uses mobile telephony provider data to verify the user automatically.
Group: com.sinch.android.sdk.verification Artifact: verification-seamless
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact verification-seamless
Group com.sinch.android.sdk.verification
Version 2.7.0
Last update 31. October 2023
Organization not specified
URL https://www.sinch.com/products/apis/verification/
License The Apache License, Version 2.0
Dependencies amount 1
Dependencies verification-core,
There are maybe transitive dependencies!
Group com.sinch.android.sdk.verification
Version 2.7.0
Last update 31. October 2023
Organization not specified
URL https://www.sinch.com/products/apis/verification/
License The Apache License, Version 2.0
Dependencies amount 1
Dependencies verification-core,
There are maybe transitive dependencies!
xades4j from group com.googlecode.xades4j (version 2.2.2)
The XAdES4j library is a high-level, configurable and extensible Java implementation of XML Advanced
Electronic Signatures (XAdES 1.3.2 and 1.4.1). It enables producing, verifying and extending signatures in the
main XAdES forms: XAdES-BES, XAdES-EPES, XAdES-T and XAdES-C. Also, extended forms are supported through the
enrichment of an existing signature.
284 downloads
Artifact xades4j
Group com.googlecode.xades4j
Version 2.2.2
Last update 17. December 2023
Organization not specified
URL https://github.com/luisgoncalves/xades4j
License GNU Lesser General Public License
Dependencies amount 6
Dependencies guava, guice, xmlsec, bcpkix-jdk18on, bcprov-jdk18on, jakarta.xml.bind-api,
There are maybe transitive dependencies!
Group com.googlecode.xades4j
Version 2.2.2
Last update 17. December 2023
Organization not specified
URL https://github.com/luisgoncalves/xades4j
License GNU Lesser General Public License
Dependencies amount 6
Dependencies guava, guice, xmlsec, bcpkix-jdk18on, bcprov-jdk18on, jakarta.xml.bind-api,
There are maybe transitive dependencies!
xades4j from group org.signserver.xades4j (version 1.3.2-signserver4)
The XAdES4j library is an high-level, configurable and extensible Java implementation of XML Advanced
Electronic Signatures (XAdES 1.3.2 and 1.4.1). It enables producing, verifying and extending signatures in the
main XAdES forms: XAdES-BES, XAdES-EPES, XAdES-T and XAdES-C. Also, extended forms are supported through the
enrichment of an existing signature.
Artifact xades4j
Group org.signserver.xades4j
Version 1.3.2-signserver4
Last update 10. May 2016
Organization not specified
URL https://code.google.com/p/xades4j/
License GNU Lesser General Public License
Dependencies amount 4
Dependencies guice-multibindings, xmlsec, bcpkix-jdk15on, bcprov-jdk15on,
There are maybe transitive dependencies!
Group org.signserver.xades4j
Version 1.3.2-signserver4
Last update 10. May 2016
Organization not specified
URL https://code.google.com/p/xades4j/
License GNU Lesser General Public License
Dependencies amount 4
Dependencies guice-multibindings, xmlsec, bcpkix-jdk15on, bcprov-jdk15on,
There are maybe transitive dependencies!
xades4j from group eu.vitaliy (version 1.2.0)
The XAdES4j library is an high-level, configurable and extensible Java implementation of XML Advanced
Electronic Signatures (XAdES 1.3.2 and 1.4.1). It enables producing, verifying and extending signatures in the
main XAdES forms: XAdES-BES, XAdES-EPES, XAdES-T and XAdES-C. Also, extended forms are supported through the
enrichment of an existing signature.
Artifact xades4j
Group eu.vitaliy
Version 1.2.0
Last update 22. February 2012
Organization not specified
URL https://github.com/VitaliyOliynyk/xades4j
License GNU Lesser General Public License
Dependencies amount 3
Dependencies guice, xmlsec, xalan,
There are maybe transitive dependencies!
Group eu.vitaliy
Version 1.2.0
Last update 22. February 2012
Organization not specified
URL https://github.com/VitaliyOliynyk/xades4j
License GNU Lesser General Public License
Dependencies amount 3
Dependencies guice, xmlsec, xalan,
There are maybe transitive dependencies!
pact-jvm-server_2.12 from group au.com.dius (version 3.6.15)
Pact server
===========
The pact server is a stand-alone interactions recorder and verifier, aimed at clients that are non-JVM or non-Ruby based.
The pact client for that platform will need to be implemented, but it only be responsible for generating the `JSON`
interactions, running the tests and communicating with the server.
The server implements a `JSON` `REST` Admin API with the following endpoints.
/ -> For diagnostics, currently returns a list of ports of the running mock servers.
/create -> For initialising a test server and submitting the JSON interactions. It returns a port
/complete -> For finalising and verifying the interactions with the server. It writes the `JSON` pact file to disk.
## Running the server
### Versions 2.2.6+
Pact server takes the following parameters:
```
Usage: pact-jvm-server [options] [port]
port
port to run on (defaults to 29999)
--help
prints this usage text
-h <value> | --host <value>
host to bind to (defaults to localhost)
-l <value> | --mock-port-lower <value>
lower bound to allocate mock ports (defaults to 20000)
-u <value> | --mock-port-upper <value>
upper bound to allocate mock ports (defaults to 40000)
-d | --daemon
run as a daemon process
-v <value> | --pact-version <value>
pact version to generate for (2 or 3)
-k <value> | --keystore-path <value>
Path to keystore
-p <value> | --keystore-password <value>
Keystore password
-s <value> | --ssl-port <value>
Ssl port the mock server should run on. lower and upper bounds are ignored
--debug
run with debug logging
```
### Using trust store 3.4.0+
Trust store can be used. However, it is limited to a single port for the time being.
### Prior to version 2.2.6
Pact server takes one optional parameter, the port number to listen on. If not provided, it will listen on 29999.
It requires an active console to run.
### Using a distribution archive
You can download a [distribution from maven central](http://search.maven.org/remotecontent?filepath=au/com/dius/pact-jvm-server_2.11/2.2.4/).
There is both a ZIP and TAR archive. Unpack it to a directory of choice and then run the script in the bin directory.
### Building a distribution bundle
You can build an application bundle with gradle by running (for 2.11 version):
$ ./gradlew :pact-jvm-server_2.11:installdist
This will create an app bundle in `build/2.11/install/pact-jvm-server_2.11`. You can then execute it with:
$ java -jar pact-jvm-server/build/2.10/install/pact-jvm-server_2.11/lib/pact-jvm-server_2.11-3.2.11.jar
or with the generated bundle script file:
$ pact-jvm-server/build/2.11/install/pact-jvm-server_2.11/bin/pact-jvm-server_2.11
By default will run on port `29999` but a port number can be optionally supplied.
### Running it with docker
You can use a docker image to execute the mock server as a docker container.
$ docker run -d -p 8080:8080 -p 20000-20010:20000-20010 uglyog/pact-jvm-server
This will run the main server on port 8080, and each created mock server on ports 20000-20010. You can map the ports to
any you require.
## Life cycle
The following actions are expected to occur
* The client calls `/create` to initialise a server with the expected `JSON` interactions and state
* The admin server will start a mock server on a random port and return the port number in the response
* The client will execute its interaction tests against the mock server with the supplied port
* Once finished, the client will call `/complete' on the Admin API, posting the port number
* The pact server will verify the interactions and write the `JSON` `pact` file to disk under `/target`
* The mock server running on the supplied port will be shutdown.
## Endpoints
### /create
The client will need `POST` to `/create` the generated `JSON` interactions, also providing a state as a query parameter
and a path.
For example:
POST http://localhost:29999/create?state=NoUsers&path=/sub/ref/path '{ "provider": { "name": "Animal_Service"}, ... }'
This will create a new running mock service provider on a randomly generated port. The port will be returned in the
`201` response:
{ "port" : 34423 }
But you can also reference the path from `/sub/ref/path` using the server port. The service will not strip
the prefix path, but instead will use it as a differentiator. If your services do not have differences
in the prefix of their path, then you will have to use the port method.
### /complete
Once the client has finished running its tests against the mock server on the supplied port (in this example port
`34423`) the client will need to `POST` to `/complete` the port number of the mock server that was used.
For example:
POST http://localhost:29999/complete '{ "port" : 34423 }'
This will cause the Pact server to verify the interactions, shutdown the mock server running on that port and writing
the pact `JSON` file to disk under the `target` directory.
### /
The `/` endpoint is for diagnostics and to check that the pact server is running. It will return all the currently
running mock servers port numbers.
For example:
GET http://localhost:29999/
'{ "ports": [23443,43232] }'
2 downloads
Artifact pact-jvm-server_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 4
Dependencies pact-jvm-consumer_2.12, logback-core, logback-classic, scopt_2.12,
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 4
Dependencies pact-jvm-consumer_2.12, logback-core, logback-classic, scopt_2.12,
There are maybe transitive dependencies!
pact-jvm-provider_2.12 from group au.com.dius (version 3.6.15)
Pact provider
=============
sub project of https://github.com/DiUS/pact-jvm
The pact provider is responsible for verifying that an API provider adheres to a number of pacts authored by its clients
This library provides the basic tools required to automate the process, and should be usable on its own in many instances.
Framework and build tool specific bindings will be provided in separate libraries that build on top of this core functionality.
### Provider State
Before each interaction is executed, the provider under test will have the opportunity to enter a state.
Generally the state maps to a set of fixture data for mocking out services that the provider is a consumer of (they will have their own pacts)
The pact framework will instruct the test server to enter that state by sending:
POST "${config.stateChangeUrl.url}/setup" { "state" : "${interaction.stateName}" }
### An example of running provider verification with junit
This example uses Groovy, JUnit 4 and Hamcrest matchers to run the provider verification.
As the provider service is a DropWizard application, it uses the DropwizardAppRule to startup the service before running any test.
**Warning:** It only grabs the first interaction from the pact file with the consumer, where there could be many. (This could possibly be solved with a parameterized test)
```groovy
class ReadmeExamplePactJVMProviderJUnitTest {
@ClassRule
public static TestRule startServiceRule = new DropwizardAppRule<DropwizardConfiguration>(
TestDropwizardApplication.class, ResourceHelpers.resourceFilePath("dropwizard/test-config.yaml"))
private static ProviderInfo serviceProvider
private static Pact<RequestResponseInteraction> testConsumerPact
private static ConsumerInfo consumer
@BeforeClass
static void setupProvider() {
serviceProvider = new ProviderInfo("Dropwizard App")
serviceProvider.setProtocol("http")
serviceProvider.setHost("localhost")
serviceProvider.setPort(8080)
serviceProvider.setPath("/")
consumer = new ConsumerInfo()
consumer.setName("test_consumer")
consumer.setPactSource(new UrlSource(
ReadmeExamplePactJVMProviderJUnitTest.getResource("/pacts/zoo_app-animal_service.json").toString()))
testConsumerPact = PactReader.loadPact(consumer.getPactSource()) as Pact<RequestResponseInteraction>
}
@Test
void runConsumerPacts() {
// grab the first interaction from the pact with consumer
Interaction interaction = testConsumerPact.interactions.get(0)
// setup the verifier
ProviderVerifier verifier = setupVerifier(interaction, serviceProvider, consumer)
// setup any provider state
// setup the client and interaction to fire against the provider
ProviderClient client = new ProviderClient(serviceProvider, new HttpClientFactory())
Map<String, Object> failures = new HashMap<>()
verifier.verifyResponseFromProvider(serviceProvider, interaction, interaction.getDescription(), failures, client)
if (!failures.isEmpty()) {
verifier.displayFailures(failures)
}
// Assert all good
assertThat(failures, is(empty()))
}
private ProviderVerifier setupVerifier(Interaction interaction, ProviderInfo provider, ConsumerInfo consumer) {
ProviderVerifier verifier = new ProviderVerifier()
verifier.initialiseReporters(provider)
verifier.reportVerificationForConsumer(consumer, provider)
if (!interaction.getProviderStates().isEmpty()) {
for (ProviderState providerState: interaction.getProviderStates()) {
verifier.reportStateForInteraction(providerState.getName(), provider, consumer, true)
}
}
verifier.reportInteractionDescription(interaction)
return verifier
}
}
```
### An example of running provider verification with spock
This example uses groovy and spock to run the provider verification.
Again the provider service is a DropWizard application, and is using the DropwizardAppRule to startup the service.
This example runs all interactions using spocks Unroll feature
```groovy
class ReadmeExamplePactJVMProviderSpockSpec extends Specification {
@ClassRule @Shared
TestRule startServiceRule = new DropwizardAppRule<DropwizardConfiguration>(TestDropwizardApplication,
ResourceHelpers.resourceFilePath('dropwizard/test-config.yaml'))
@Shared
ProviderInfo serviceProvider
ProviderVerifier verifier
def setupSpec() {
serviceProvider = new ProviderInfo('Dropwizard App')
serviceProvider.protocol = 'http'
serviceProvider.host = 'localhost'
serviceProvider.port = 8080
serviceProvider.path = '/'
serviceProvider.hasPactWith('zoo_app') {
pactSource = new FileSource(new File(ResourceHelpers.resourceFilePath('pacts/zoo_app-animal_service.json')))
}
}
def setup() {
verifier = new ProviderVerifier()
}
def cleanup() {
// cleanup provider state
// ie. db.truncateAllTables()
}
def cleanupSpec() {
// cleanup provider
}
@Unroll
def "Provider Pact - With Consumer #consumer"() {
expect:
verifyConsumerPact(consumer).empty
where:
consumer << serviceProvider.consumers
}
private Map verifyConsumerPact(ConsumerInfo consumer) {
Map failures = [:]
verifier.initialiseReporters(serviceProvider)
verifier.runVerificationForConsumer(failures, serviceProvider, consumer)
if (!failures.empty) {
verifier.displayFailures(failures)
}
failures
}
}
```
3 downloads
Artifact pact-jvm-provider_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 9
Dependencies pact-jvm-model, pact-jvm-pact-broker, pact-jvm-matchers_2.12, commons-io, jansi, httpclient, reflections, pact-jvm-support, scala-java8-compat_2.12,
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 9
Dependencies pact-jvm-model, pact-jvm-pact-broker, pact-jvm-matchers_2.12, commons-io, jansi, httpclient, reflections, pact-jvm-support, scala-java8-compat_2.12,
There are maybe transitive dependencies!
Page 8 from 10 (items total 98)