Version 2.2.0 is released! POJO and J2EE technology stack (JAX-RPC or Web Services, CORBA, EJB, JMS, RMI) support on your client side about 100KB runtime.

JProxy utilizes Aspect Oriented Programming (AOP) for seamless injection of communication, security and session functionality.

Applet can use JProxy to achieve very small footprint, HTTP Tunneling, Callbacks over HTTP and portability.

Regardless of complexity of communication, JProxy Client is always small. JProxy Runtime has logic that discovers client demands in remote functionality. It then passes request to JProxy Server to generate Java Classes (Dynamic or Bytecode stubs) that will be used by the client for communication with Server. JProxy Server behaves as local client for J2EE Server and all J2EE-specific logic stays locally on the server. So there is no need to keep J2EE libraries on the client. JProxy Server takes care about security propagation, session and remote object lifetime.

Any Java objects implementing interface can be remoted by JProxy without violating the default security model of the browser (MSIE, Firefox, Netscape Navigator, Opera, Konqueror). more... This is how JMS is supported. We also successfully enabled JDBC over HTTP. By customizing JProxy properties you may remote your custom interfaces implemented by your POJO.

Download Here JProxy Technical Overview white paper Professional Services

JProxy Major Features Outline

HTTP / HTTPS Tunnelng for JAX-RPC, CORBA, EJB, JMS or RMI Asynchronous message delivery for JMS over HTTP / HTTPS without polling The generic provider-independent communication solution for different EJB, JMS, RMI or CORBA servers By overriding Application Layer of Open Systems Interconnect (OSI) Stack JProxy seamlessly integrates into any Java enterprise software with NO change to your code. Small client-side footprint - 90K, which enables you to utilize power of J2EE APIs from Applets running on a variety of devices - Workstations, Cellular Phones, PDA and other hardware that supports Java The only solution that allows you to employ services of EJB, RMI, JMS and CORBA remote objects via HTTP/HTTPS standard protocol in clients with no support for aforementioned technologies because they're running an older version of Java or Java Micro Edition. Such clients can be wireless devices, cell phones, PDAs and other hardware. A solution to solve scalability or failover for EJB, RMI or CORBA The EJB, RMI, JMS or CORBA support for your custom communication protocols The solution to increase communication performance by utilizing data compression and packaging of multiple independent requests J2EE Client can access all J2EE services from standard secure "sandbox"

Read JProxy Features explained... Take a look at this picture. This is a simplified view of a three-tier architecture with JProxy enabling your application to communicate over the endless Internet networks.

You can use JProxy with ANY J2EE compliant Application Server of your choice. You simply need to deploy an EAR file into the Application Server's deployment directory and possibly modify some JProxy properties in its configuration file. Please read Installation and Configuration for further details.

News Update

JProxy is remoting AGFA's medical imaging software. more... Sun Microsystems names JProxy its Strategic Partner. more... Version 2.2.0 is released! more... FairIssac and Company signs OEM agreement with JProxy, LLC to embed JProxy into their financial software. more... Latest Servlet Engine - Tomcat 4.1.12 seems to have a change in its processing of web.xml deployment descriptor. more... There is a new JProxy Performance sample available online. You can now test JProxy performance in a realistic Internet environment! Also take a look at the results of tests that we ran in or lab