Download JAR files tagged by sent with all dependencies

Core Java Jexbox connector hooks into Thread.UncaughtExceptionHandler, so any uncaught exceptions in your application will be sent to your Jexbox database. The connector extracts complete exception stack trace, including nested exceptions, error message and system properties

Open Charge Point Protocol (OCPP. The common parts of the different OCPP specifications are handled here. The SOAP and JSON web socket modules communicate with the core via this module. This module also handles the events sent out by the core.

LogDistiller is a logfile merge and sort tool. Log content is classified according to rules configured in an XML file. Classification results go into reports, which are published: simply stored in a file, sent by mail, or even added to a news feed.

JSON Batch Translate library allows you to translate json objects with google translate service and returns back exactly the same json with translated values (keys are kept original, only one request is sent for translation)

As a programmer did you have the experience that when you comes to implement a search page you can only transform the search form into sql manually? If your project have 20 search page like that then you have to write 20 times to implement the sql query. It’s boring and anxious. form-sql-builder-mysql is designed for ease the burden for you. It can help you to transform search or list form sent from browser into query sql automatically.

A simple repository to salt a secret key and verify its authenticity. Developed to be used in mobile applications while communicating with a server side using an Api. Instead of sending an apikey straight on the request, SaltedKey can generate a temporary public key, valid for one time use and during a specific time frame, default time is set to 60 seconds. This public key can be sent on request and on server side SaltedKey can verify its authenticity. The Salt is based on time millis and uses the algorithm SHA-256 to create the temporary public key. The public key base will change every time it exceeds the time frame. This library can increase the API security. Even if the public key used on request is exposed, no one will be able to use it again! As it is a one time use only.

<p> MMBase Utils is a part of MMBase, but can also be used in other projects. It contains several kind of utility classes.</p> <p>Highlights:</p> <ul> <li>An implementation of 'events'. Threads can use this to communicate certain things. Using mmbase-clustering, these events can also be sent to other servers.</li> <li>A logging framework</li> <li>A framework for string and byte array transformeration, plus a whole lot of implemetentations for that.</li> <li>Several java.util like classes (collections, dateparsing)</li> <li>File type recognition ('magicfile')</li> <li>The MMBase resourceloader, a generic fall-back mechanism for configuration files and similar resources.</li> <li>...</li> </ul>

A simple templating system for java codegen. This library includes an object-oriented, fluent source writing api, for a chained, intuitive codegen api. It also includes a template processor which can take java source files formatted with "magic comments", to allow simple mapping of GeneratorClass#generatorMethod() to inject dynamic source content. //@generateWith(GeneratorClass)// -Sets the current generator. You may use as many as you please //generatorMethod(arbitrary-string-data-you-may-want-to-parse)// -invokes the named method on the current injector, with any text (between brackets) sent as a string This allows you to markup default source with hooks where you may want to inject arbitrary code. It is especially useful for generating super-source in gwt compiles; changes to the default class are propagated to overrides.

# Pact Junit 5 Extension ## Overview For writing Pact verification tests with JUnit 5, there is an JUnit 5 Invocation Context Provider that you can use with the `@TestTemplate` annotation. This will generate a test for each interaction found for the pact files for the provider. To use it, add the `@Provider` and one of the pact source annotations to your test class (as per a JUnit 4 test), then add a method annotated with `@TestTemplate` and `@ExtendWith(PactVerificationInvocationContextProvider.class)` that takes a `PactVerificationContext` parameter. You will need to call `verifyInteraction()` on the context parameter in your test template method. For example: ```java @Provider(&quot;myAwesomeService&quot;) @PactFolder(&quot;pacts&quot;) public class ContractVerificationTest { @TestTemplate @ExtendWith(PactVerificationInvocationContextProvider.class) void pactVerificationTestTemplate(PactVerificationContext context) { context.verifyInteraction(); } } ``` For details on the provider and pact source annotations, refer to the [Pact junit runner](../pact-jvm-provider-junit/README.md) docs. ## Test target You can set the test target (the object that defines the target of the test, which should point to your provider) on the `PactVerificationContext`, but you need to do this in a before test method (annotated with `@BeforeEach`). There are three different test targets you can use: `HttpTestTarget`, `HttpsTestTarget` and `AmpqTestTarget`. For example: ```java @BeforeEach void before(PactVerificationContext context) { context.setTarget(HttpTestTarget.fromUrl(new URL(myProviderUrl))); // or something like // context.setTarget(new HttpTestTarget(&quot;localhost&quot;, myProviderPort, &quot;/&quot;)); } ``` ## Provider State Methods Provider State Methods work in the same way as with JUnit 4 tests, refer to the [Pact junit runner](../pact-jvm-provider-junit/README.md) docs. ## Modifying the requests before they are sent **Important Note:** You should only use this feature for things that can not be persisted in the pact file. By modifying the request, you are potentially modifying the contract from the consumer tests! Sometimes you may need to add things to the requests that can&apos;t be persisted in a pact file. Examples of these would be authentication tokens, which have a small life span. The Http and Https test targets support injecting the request that will executed into the test template method. You can then add things to the request before calling the `verifyInteraction()` method. For example to add a header: ```java @TestTemplate @ExtendWith(PactVerificationInvocationContextProvider.class) void testTemplate(PactVerificationContext context, HttpRequest request) { // This will add a header to the request request.addHeader(&quot;X-Auth-Token&quot;, &quot;1234&quot;); context.verifyInteraction(); } ``` ## Objects that can be injected into the test methods You can inject the following objects into your test methods (just like the `PactVerificationContext`). They will be null if injected before the supported phase. | Object | Can be injected from phase | Description | | ------ | --------------- | ----------- | | PactVerificationContext | @BeforeEach | The context to use to execute the interaction test | | Pact | any | The Pact model for the test | | Interaction | any | The Interaction model for the test | | HttpRequest | @TestTemplate | The request that is going to be executed (only for HTTP and HTTPS targets) | | ProviderVerifier | @TestTemplate | The verifier instance that is used to verify the interaction |