metarhia/jstp-java

JSTP implementation in java

jstp-java's Issues

Create EventHandler annotation for Proxy methods

We should add an @EventHandler annotation for Proxy methods to process incoming events in the way like this:

@EventHandler
void onSomeEvent(List<?> args);

@EventHandler("eventName")
void onSomeEvent(List<?> args);

@EventHandler({"interfaceName", "eventName"})
void onSomeEvent(List<?> args);

With this annotation the generated class for Proxy should be abstract, so that the User'll later implement handlers for methods with @EventHandler annotation.

Migrate JSTPConnection to JSNativeParser

Delegate methods from Connection in generated proxy

Add delegated methods addEventHandler and setCallHandler from Connection to class generated with @Proxy to avoid unneded interactions with the Connection intelf.

Write documentation for ExecutableHandler

Introduced in 8aee294.

conn: remove state packets

Change error code for CALLBACK_LOST error to -1 to be consistent with JS implementation

This error must be local and must not be sent over the connection, thus the negative code value.

Create CallHandler annotation for Proxy methods

We should add a @CallHandler annotation for Proxy methods to process incoming calls in the way like this:

@CallHandler
void onMethodCalled(List<?> args);

@CallHandler("methodName")
void onMethodCalled(List<?> args);

@CallHandler({"interfaceName", "methodName"})
void onMethodCalled(List<?> args);

With this annotation the generated class for Proxy should be abstract, so that the User'll later implement handlers for methods with @CallHandler annotation.

Empty app name on first connect

With current implementation it is possible to call connect with no name but there are no checks for empty internal app name which will in turn lead to sending nothing instead of app name.

This should easily be checked in onConnected()

Write documentation for @Proxy

Introduced in 939cad3.

Allow to set thread to run callbacks

As it stated in title, It'd be better to allow users to choose thread for callbacks (for all ManualHandlers, EventHandlers etc)

Update compiler docs with info on default get

If no method-wide getter is specified jstp-compiler will get value under second key of object and use it as a base. This is not reflected in readme.

Deprecate and remove JSParser (JS hierarchy)

• Remove JS hierarchy and parser (#14 f438eb5)
• Remove docs (#14 b3112e1)
• Remove tests (#14 f438eb5)

Executable handler requires "message" instead of "internal message"

Creating a handler like this:

@Handler(ExecutableHandler.class)
public interface OkErrorHandler {

    @NotNull
    @Object("ok")
    void onOk(List<?> args);

    @NotNull
    @Object("error")
    void onError(@Array(0) Integer errorCode);
}

leads to problems with handler, because run() method requires message, but internalMessage is created instead (generated code fragment):

@Override
public void run() {
    handleOnOk(internalMessage);
    handleOnError(internalMessage);
}

Send handshake automatically after useTransport

As of now you need to call handshake manually if you change transport to the one that has already been connected, hence it'd be better to check that and send handshake if transport is already connected.

This should be easily done in useTransport method.

Queued packet handling upon transport change

When you call connection.useTransport to change underlying transport there is no policy applied to the packages that already are in the queue, it must be defined what's going to happen to them.