my dog learned polymorphism*
The moose likes Java in General and the fly likes Calling Java Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » Java in General
Bookmark "Calling Java" Watch "Calling Java" New topic

Calling Java

ed de jongh

Joined: Nov 27, 2002
Posts: 6
Hi I have a program that does certain validations and returns valid or invalid status. Currently I use CORBA to call this component from anywhere, however I feel that there must be a much simpler method than this. I need to deploy this Jar and have it called from basically any language/client with the least integration/setup hassle possible. I've thought about standard sockets and IO Byte reading, even HTTP. There must be a simpler way. One common factor is that almost every client will be windows based.
I need some lateral alternatives please.
Brian McCallister

Joined: Dec 03, 2002
Posts: 19
If you are familiar with working with CORBA the easiest way is probably to create an RMI/IIOP stub for it and call it that way. IIOP is Java's interface to CORBA. Google for "Java RMI/IIOP Tutorial" and you should come up with some good step throughs.
The easiest way by far though is to use Apache Axis ( ) and make it a SOAP service. RMI/IIOP is easy in Java, but so are SOAP services with Axis. The feasibility of this depends a lot on what exactly you are doing, and how easy making a SOAP client from your non-Java app is.
ed de jongh

Joined: Nov 27, 2002
Posts: 6
Thanks Brian, the IIOP only helps if I have Java clients, which is not necessarily the case, so that route is unfortunately not an option. I thought about an Apache server, but that just makes deployment that much more of an issue for the non tech end user.
The point is I want to make this as easy as possible for anyone to call from any language without the use of CORBA, SOAP etc. as it makes an essentially simple product more complex from the clients perspective. I think I'm going to just go straight Sockets, (readBytes()) on this one as there doesn't seem to be an easier/more generic way for any client to connect without some 3rd party product.
Thanks again
I agree. Here's the link:
subject: Calling Java
Similar Threads
Can my Data class implement an interface which extends the DataAccess interface?
Local Adapter Issue
Head first java - chapter 5 SimpleDotCom game
Security on applet calling web service (different servers)
Java Based Archiving System