Currently scc will detect remote method calls, either when the method is marked with the @Exec annotation as well as when it's in a 'remote layer'. It allows you to use such calls though only in data binding expressions or in code when using the dynamic runtime. For runtimes like Java that support synchronous remote calls, we should also support a transformation so we use a DynUtil.invokeRemote call in the generated code when we encounter a remote method. This would let use the same code base to run in different configurations - local and remote.
Currently scc will detect remote method calls, either when the method is marked with the @Exec annotation as well as when it's in a 'remote layer'. It allows you to use such calls though only in data binding expressions or in code when using the dynamic runtime. For runtimes like Java that support synchronous remote calls, we should also support a transformation so we use a DynUtil.invokeRemote call in the generated code when we encounter a remote method. This would let use the same code base to run in different configurations - local and remote.