Download JAR files tagged by annotations 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.

rpc快速使用，可自动从配置中心获取注册中心、线程池、超时时间等配置， 在rpc调用异常时将异常封装成标准响应对象返回给调用方，并自定义rpc telnet指令供开发测试使用， 业务可使用提供注解进行rpc服务的消费和提供，可实现消费和提供者服务批量管理，提供泛化调用工具 RPC use quickly, and the underlying implementation is currently dubbo, which can automatically obtain configurations such as registration center, thread pool, and timeout time from the configuration center. When dubbo calls an exception, it will encapsulate the exception into a standard response object and return it to the caller, and customize the dubbo telnet command. For development and testing, businesses can use annotations to consume and provide RPC services, realize batch management of consumption and provider services, and provide generalized calling tools

DefaultJ is a powerful Java library that provides default values for any class, offering multiple strategies for obtaining those values. It can be used as a dependency injection utility, similar to Guice. With 14 built-in strategies, DefaultJ can obtain default values through various means such as explicit bindings, annotations, enum values, factory methods, and more. It also supports custom annotations and offers annotation processors for validation. Available on Maven Central, DefaultJ can be easily integrated into Gradle and Maven projects. Contributions and selective usage of the library are encouraged.

DefaultJ is a powerful Java library that provides default values for any class, offering multiple strategies for obtaining those values. It can be used as a dependency injection utility, similar to Guice. With 14 built-in strategies, DefaultJ can obtain default values through various means such as explicit bindings, annotations, enum values, factory methods, and more. It also supports custom annotations and offers annotation processors for validation. Available on Maven Central, DefaultJ can be easily integrated into Gradle and Maven projects. Contributions and selective usage of the library are encouraged.

This is a Java library which provides a flexible and customizable way to bind command line arguments to Java objects, in a similar manner to how JSON, XML, and YAML can be bound to Java objects. You can easily define Java classes that represent the data structure of your command line arguments, and use annotations to specify how those arguments should be parsed and bound to the corresponding fields in your Java object. This allows you to write command line interfaces that are more intuitive and easier to use, while also reducing the amount of boilerplate code that is needed to parse and validate command line arguments.

JPA Security is an Access Control Solution for the Java Persistence API (JPA). With JPA Security your access control can be performed in the database. You may query the database for all objects of a certain type and will receive only the objects you have read access for. This filtering is performed in the database. Unaccessible queried objects will not be loaded into memory. JPA Security enables you to completely remove security-related code from your code-base. All access control may be configured via Annotations or XML. With JPA Security you do not have to change your access control paradigm (but maybe you want to, when you see the great capability of JPA Security). You even can mix access control paradigms easily. JPA Security is not designed to replace current security solutions, but to extend them. It integrates smoothly into the security mechanisms of the Java EE Platform, but may be used with third-party frameworks like Spring Security or in Java SE, too. With the extensibility of JPA Security it is easy to provide your own access control paradigm, access rules storage or login mechanism.