# Send to Java Queue JMS **URL:** \ **Category:** Questions\ **Tags:** erlang, libraries\ **Created:** [July 4, 2019, 12:37pm UTC](https://forum.elixirforum.com/t/send-to-java-queue-jms/23683 "2019-07-04T12:37:07Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![jeremyjh](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/jeremyjh/32/5995_2.png) [@jeremyjh](https://forum.elixirforum.com/u/jeremyjh)\ **Post date:** [July 4, 2019, 1:56pm UTC](https://forum.elixirforum.com/t/send-to-java-queue-jms/23683/6 "2019-07-04T13:56:29Z")
> [@NobbZ](#): > > Never actually used `jinterface` , only now about its existence, but I always assumed it were similar to how one does create NIF bindings to C-ABI compatible libraries… No, its more like [erl\_connect](http://erlang.org/doc/man/erl_connect.html), which is used to build “C Nodes”. Jinterface is used to build “J Nodes”. I’d only do this if there was absolutely no other way as now you’ve introduced a whole separate server process to manage, just to talk to another server. The link you posted tells you this upfront: > [@](#): > > The classes in[Jinterface](http://erlang.org/doc/apps/jinterface/java/com/ericsson/otp/erlang/package-summary.html) support the following: > > - manipulation of data represented as Erlang data types > - conversion of data between Java and Erlang formats > - encoding and decoding of Erlang data types for transmission or storage > - communication between Java nodes and Erlang processe JMS is not a message or wire format so much as it is a Java client API, and all the message broker products that implement it also implement other protocols. --- _[View the full topic](https://forum.elixirforum.com/t/send-to-java-queue-jms/23683)._