Home/ Questions/Q 6675131
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T03:48:57+00:00

I created a command line interface on a small java application I created for

  • 0

I created a command line interface on a small java application I created for personal use.
For the moment the cli is resided in the same project as the original application but I’m planning to extract it into it’s own project, effectively building 2 separate executable jars enabling me to start the cli as needed and query the other running program for information.

I’m trying to figure out the easiest and most lightweight solution to call a remote service, on the same machine.
I looked at spring remoting but many of the provided solutions such as HttpInvoker, Hessian/Burlap, JAX RPC web services are based on HTTP or SOAP and therefore not suited for the job.
JMS also seems like overkill.

This leaves me with RMI, which looks rather heavyweight, and possibly JMX?
Suggestions?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    JMX would use RMI underneath for remote access. JMX is meant for exposing admin apis (monitoring / management) – not intended as a general purpose remoting api.

    RMI with the spring remoting support is fairly lightweight from a development point of view. Even runtime it is the option that adds least overhead compared to the other options you have listed.

    Also with spring remoting support you can easily switch over to a different option if required later.

    Take a look at this artcile, that compares / benchmarks performance of the above options.

    • 0