In this article, I will show you how the combination of Eclipse RCP and EJB3 allow developers to build a rich, performed and distributed application. I will assume that you understand the basics of technologies mentioned above, and I will only explain the architecture used to efficiently handle the communication between the desktop application and the server.
This article is based on previous articles:
- Deploying Java Pet Store 2.0 on JBOSS using Eclipse IDE
- Rich Internet Application: Development Pet Store 2.0 using GWT and ExtJS.
Prerequisites:
To build and run the sample, you need the following software:
High Level Architecture Diagram:
The diagram below details the architecture used for building this sample. It shows the interaction between RCP Application and server side components. Client could discover and lookup services via JNDI as service registry.
Configuration:
Configuration always depends on the application server, but it is quite the same.
I details below the configuration needed to lookup services via JNDI in JBoss server.
- JBoss Client Library : Add jboss-all-client in the classpath.
- PetStore client Interfaces : Add PetStore client libray in the classpath
- JNDI parameters :
+java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
+java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
+ java.naming.provider.url=localhost:1099
Conclusion:
In this article, we have seen together how we can access to distributed components by desktop application built using Eclipse RCP.
Screenshot:
Download:
Aucun commentaire:
Enregistrer un commentaire