minjing/uapi

The UAPI Project

uapi's Issues

Familiar with Netty HTTP service API

Check Netty documentation to see how to provide HTTP service.

Add java doc for all interfaces

Add java doc for all interfaces

The framework can handle the lifecyle of the service

Normally the service has a lifecycle: resolved, satisfied, initialized, destroyed.

• Resolved: the service is resolved, but all dependencies is not set, the service can't serve.
• Satisfied: all dependents has been set to the service,
• Initialized: the initialization method of the service has been invoked, the service can serve to outside.
• Destroyed: the service has been destroyed.

Merge feature/restful-refactor to master

Service Profile Feature Scoping

Refactor Restful API based on new HTTP service API

If the ServiceHolder.tryInitService() be invoked multiple times may cause inject same object multiple times

Documentation for Service Profile

Service method invocation mornitoring

It help to find performance issue easily if add support monitor service method invocation time.

Add system shutdown hook

Rewrite old unit tests by Spock

Rewrite old unit tests by Spock

Fix code level issues

Fix issues which were found in https://www.codacy.com/app/min_jing/uapi

A profile to indicate which service can be registered or not

Implementation for async service feature

Http service provider by Netty

Try to Load External Service when Resolve the Dependency Failed

Currently load external services is in Repository.start method and it is invoked only once, the behavior is not good, since if some services are added after start method is invoked then the unresolved dependency can't be loaded by external service loader, it is better that load external service dynamically

Service Defintion

Define a service by Java ServiceLoader, the service be able to define its dependencies.

Support Collection field injection

Support initialize service during program launching

In default, all service are lazy initialized which mean they are initialized when first use, but some service need to initialize at launch time.

The IInjectable interface should be implemented from IService interface

Service Profile Feature Testing

Design for async service feature

Test case for annotation based code generation

Test case for annotation based code generation

The framework parse the command line arguments based on service registration information

Only support below command line option:

• -x: x option with no value
• -x=???: x option with value
• -xtrf: x, t, r, f option with no value

Refactor existing Restful API implementation

ServiceHolder must be multiple thread safe because it may be invoked by multiple threads

Generic Restful service based on consistent HTTP service API

Asynchronous service invocation

Create new branch for Restful service refactor

The branch named - feature/restful-refactor

Service should support lifecycle

Some services use resources to achieve some functionality, for these services we need to provide some methods like onInit, onUnload to make these services can apply resources and free resources when system shut down.

Behavior(actions) definition

Documentation for 0.3

Using Netty to provide HTTP service

Inject annotation without Service annotation will fail build

If the service declare Inject annotation in a field but it does not declare a Service annotation, the annotation build will fail.

The Source of Generated Service should no be packaged in jar file

Event based behavior(actions) framework

The Inject service attribute support optional

Clean old service injection code files

Support custom service parameter and return type

Ignore Service functionality should be removed

Event support, decide using 3rd library or implement it self

Generated Service should be a pretty Class Name

Currently the generated service name construct by extended service class name plus a "_Generated" postfix, it is not good enough, the suggestion is:

• Generate a MD5 code for service class file, so the MD5 code will keep same if the class does not change.
• Extract the first 5 characters as a generated class postfix and connect with "_".

Sample for asynchronous service

Service Profile Feature Implementation

The framework can resolve the service dependenies

The framework can inject the dependencies by service's setter method.
If the dependency does not satisfy, a run-time exception will be thrown out, the launch process should be end.

Service Profile feature Design

Create new branch for async service feature

Merge Service Profile branch to master

Support register service to Consul

Support name attribute and type attribute