JProxy

JProxy is a lightweight J2EE client that brings the J2EE technology stack right to your device with just a 90 KB runtime. Pretty neat, right?

What Does JProxy Do?

So, here’s the deal: JProxy uses servlets to connect easily with most application servers out there. It tunnels the J2EE tech stack over HTTP(S), allowing your J2EE systems to work smoothly across firewalls and restrictive networks on the Internet in no time.

No Code Changes Needed!

You won’t have to change any source code. You can access all those cool J2EE technologies from any Java-enabled device without needing a full-on J2EE setup on that device.

Key Features of JProxy

Here are some key features of JProxy:

• HTTP/HTTPS tunneling for services like JAX-RPC, CORBA, EJB, JMS, or RMI.


• Asynchronous message delivery for JMS over HTTP/HTTPS without any polling needed.


• A generic solution that works with different EJB, JMS, RMI, or CORBA servers.


• No code changes required thanks to its integration into the Application Layer of the OSI Stack.


• A tiny client-side footprint of just 90K lets you tap into the power of J2EE APIs from applets on many devices—workstations, cell phones, PDAs—you name it!


• The only solution out there that lets you use EJB, RMI, JMS and CORBA services via standard HTTP/HTTPS on older devices that don’t support those technologies.


• A great fix for scalability or failover issues for EJBs and more!


• Cuts down communication delays by using data compression and grouping multiple requests together.


• Your J2EE Client can reach all services securely from a standard "sandbox" environment.

Requirements

If you're wondering what you need to get started with JProxy, you'll need at least Java Runtime Environment 1.4.1 installed on your system.

Limitations You Should Know About

• This is an evaluation version! At startup, both client and server logs will show a message about it being an evaluation copy.


• You can only have two clients communicating at once using this evaluation version—so keep it small!


• No remote garbage collection means server-side memory might grow over time.


• The data compression feature isn’t included in this version either.


• The communication timeout feature is missing too!


• No failover capabilities are available in this eval version.

If you're interested in trying it out or learning more about it, check out this link here!