JProxy is generic J2EE client/server communication solution that provides HTTP Tunneling.
JProxy is a servlet based solution and seamlessly integrates with most of Application
Servers. JProxy tunnels J2EE technology stack over HTTP/HTTPS protocols, thus
letting your J2EE systems operate over any firewall, proxy and restrictive
network configurations on the Internet instantaneously. No source code change
required. Use just one 100KB client runtime to access different J2EE Application
Servers. JProxy also remotes Plain Old Java Objects (POJO) so you are not
locked on any J2EE API.
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.
| 
