In the JDeveloper 10.1.2 release and earlier, when building a Swing client interface that is deployed in a 3-tier deployment, the thin client UI works over EJB remoting and works with a dedicated server-side EJB session bean facade that JDeveloper builds for you automatically when you indicate that you want your ADF application module deployed as an EJB session bean. The operative word in the previous sentence is the word dedicated. That is, 50 simultaneous users doing work need 50 instances of their server-side session bean. This is fundamentally different for how ADF-based web applications work, where 50 simultaneous users doing work might be able to be serviced by a server-side pool of only 10 application modules, depending on how much "think time" the users perform between doing actual work against the server.
In JDeveloper 10.1.3, we're introducing a cool, new feature for building much more scalable Swing business application clients. Stated most simply, it allows the Swing client to leverage the same server-side application module pooling infrastructure that today's web-based ADF applications enjoy for scalability. The client can perform changes to its local data (across multiple levels of master/detail information), and then send a whole batch of changes to the server in one round-trip. As is the case in the web scenario, the only persistent state needed across requests is a simple client cookie value that the client uses to "rendezvous" with its pending transaction state on subsequent requests over the life of a complex, multi-step business application transaction. From the point of the EJB container, the only persistent state is that cookie value. The rest of the pending transaction state management is identical to the state management features described in this ADF whitepaper on the subject, meaning that when running in a clustered server configuration there is an absolute minimum of information that the EJB container needs to synchronize across nodes.
We are looking for existing ADF Swing customers (using our JClient bindings) who might be willing to help us do some testing on this new feature, so if you are an existing ADF user building Swing clients and might be interested, send me an email.
12:12:22 PM 
|
|
