It depends on what you actually want to do.
If you need to expose your grpc-based Java application as a backend of RESTful APIs, nothing prevents you from combining it with grpc-gateway. Even though grpc-gateway itself is written in Go, it does not actually matter because grpc-gateway works as an independent process by design.
If you need a convenient way to call gRPC methods from command line, you can consider grpc_cli, polyglot, grpcurl, ...
If you need to marshal your payloads not into protobuf but into JSON, and if gRPC wire protocol over HTTP/2 does not actually matter with you,
you can use a custom marshaler in your gRPC server.
Thanks,
Yuki Yugui Sonoda