When an interface is marked as @ProxyGen, a class is generated by the compiler to communicate through the event bus. But still, we have to create the code to mount it to a specific eventBus address.
Another interface is generated to access the service on a specific address remotely.
It would be very convenient to add two annotations to cover these use cases :
The interface could be annotated with @Proxify("some.address") which would automatically look for the generated class, instanciate it and mount it like here
Instead of @Service for dependency injection, we could just add @ServiceProxy("some.address") which would inject the proxified service into some class
Service proxies are a great feature of Vert.x 3
@ProxyGen, a class is generated by the compiler to communicate through the event bus. But still, we have to create the code to mount it to a specific eventBus address.Examples :
It would be very convenient to add two annotations to cover these use cases :
@Proxify("some.address")which would automatically look for the generated class, instanciate it and mount it like here@Servicefor dependency injection, we could just add@ServiceProxy("some.address")which would inject the proxified service into some class