Download JAR files tagged by because with all dependencies

This project is about configuration of applications and about parameterization of Objects. This library offers annotations (and annotation processors), parsers, typing, observing changes, serialization, cloning and more when working with settings and/or object parameters. Settings and its features can be declared using an xml format. The library offers syntax support for settings and parameters in a loosely coupled manner. You are not restricted to built in syntax, you can provide your own. At runtime this library tracks keys for which a default is used because they are not found in settings. Also it tracks unused keys. You can stack features for settings such as caching, preparing keys and values, readonlyness, threadsafety, helpsupport, reading / parsing from input. You can easily develop your own features for settings.

Fontys Venlo best maven practices. "Up with your competencies" The 'testeasypom' Parent pom that provides all dependencies that you need for modern testing, generating good looking Javadoc and a set of static test reports using spotbugs, pmd, and checkstyle. This is NOT cargo-cult, because NONE of the dependencies in this pom will end up in your final product. This is a continuation of sebipom. Version 4.0.7: update dep and plugin versions. Version 4.0.8: jacaco 0.8.8 for java 17 and 18 support Version 4.0.11: default to java 17 Version 5.1.0: default to java 21 Version 5.2.0: include testfx stuff in fx profile

This project has a lot of business classes to work with genes and related named entities. Genes are part of a GeneDocument and may have gold IDs as well as mapped/predicted IDs. Another large part are species because most (all?) gene ID databases are species specific. So there are also classes or members to represent species mentions and the assignment of species IDs (taxonomy IDs) to genes. There is little to no business logic herein. This project is only useful as building block in other projects dealing with species assignment, gene ID mapping or similar efforts.

ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications. Each time they are implemented there is a lot of work that goes into fixing the bugs and race conditions that are inevitable. Because of the difficulty of implementing these kinds of services, applications initially usually skimp on them ,which make them brittle in the presence of change and difficult to manage. Even when done correctly, different implementations of these services lead to management complexity when the applications are deployed.

This is a plugin to Madura Objects. It provides a rules/constraint engine to assist with validation, deriving new values from user inputs (eg total of invoices entered on this customer) an manipulating metadata (eg because the amount is above X we make some field readonly). Note that the Java that is using the monitored objects is quite unaware of the rules layer implemented here. That means you can change rules without having to go back to your Java code, and it also means you don't have to wonder if everything implemented the same rules. Anything using that Java object has the rules (unless you turn them all off).

This is a demo program that illustrates some of the capabilities of Madura working with Vaadin. Specifically it shows the use of the JPAontainer. The JPAContainer shown here is extended from the one you can find in Vaadin Addons to support Spring's @Transactional notation. It is also using Madura Objects, but that is an interesting incidental because you could use Madura Objects with both. So the objective here is to show a complete working demo of how to configure everything to show a table of data fetched from a database using JPA, including popup edit forms.

Spring JdbcTemplate did very convient and useful, but it also has some disadvantages or in another word “inconvenient”. For example, you can’t just pass an object and tell JdbcTemplate to turn it into a sql and save to database just like hibernate does. Alright, you may say “JdbcTemplate doesn’t need you to write hbm.xml , so it’s understandable”. But is it true that this thing is impossible to achieve? And also you know JdbcTemplate can auto turn the result of a query to a list of persistent object a.k.a PO, but when you want to do this you will meet a problem: “How to ?”.Because you can’t find any function of JdbcTemplate to pass a sql and a PO class as we expected. After you google for it, you’ve been told you can create a BeanPropertyRowMapper to deal with this. But isn’t it could be more easier? Based on those questions I create JdbcTemplateTool which can provide these features.

This is an endorsed version of the original Deployment Client for Oracle GlassFish Open Source Edition. The purpose of the endorsement is to provide a shaded JAR which has the OSGI meta data removed because it causes the original Deployment Client to fail when used within a module running within a GlassFish container due to some class loader configuration conflicts between the container and the deployed module. This issue has been reported to the GlassFish project at https://java.net/jira/browse/GLASSFISH-20856 . It is hoped that it can get fixed so that this workaround project can get deprecated soon.

This module was created to fix issue DIRSHARED-91 where the embedded Felix instance inside the default LdapCodecService implementation was making it very problematic to deploy the ldap-codec inside an RCP (OSGi) environment and hence Apache Directory Studio could not use it. This module is most likely temporary and will disappear once we are fully OSGi enabled. This module is a plain old jar, not a bundle to avoid accidental reuse as an OSGi module because it contains the version of the LdapCodecService that embeds Felix to make controls and extended ops pluggable in the codec.