![Welcome ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (12)
Destacado
Similar a EGL Conference 2011 - Technical Workshop
Similar a EGL Conference 2011 - Technical Workshop (20)
EGL Conference 2011 - Technical Workshop
- 1. Day 2 - Technical Workshops
- 4. EGL Rich UI Architecture Developers use Eclipse-based EGL tools to code, preview, and debug application on their workstations. EGL services are compiled as Java and RUIs are compiled as JavaScript . Preview Rational Business Developer
- 5. EGL Rich UI Architecture Rational Business Developer Web Application Server (Apache Tomcat or WebSphere Application Server) For deployment, RUI code is compiled into HTML and JavaScript , services are compiled into Java as SOAP or REST Web services. Code is then deployed as a JEE application into a Web application server. Deploy as Java, JavaScript, and HTML
- 6. EGL Rich UI Architecture Web Application Server (Apache Tomcat or WebSphere Application Server) Users access the URL for the application using a standard Web browser and the HTML and JavaScript is downloaded to the client. All client/server interaction occurs via REST and SOAP service calls (using Ajax). Services can be also external/third-party. Internet / Intranet
- 7. Lab 1: Mortgage Portal
- 9. Lab 2: Database Access
- 11. Lab 3: ClearBlade Katana Framework
Notas del editor
- Pages are not generated on the fly at runtime – application exists as static HTML and JavaScript. Results in less work happening on the server. Subsequent interactions with the server occurs via Ajax-initiated SOAP and REST services calls. Results in faster response time, less network traffic (good for slow links), and less work on the server.
- Pages are not generated on the fly at runtime – application exists as static HTML and JavaScript. Results in less work happening on the server. Subsequent interactions with the server occurs via Ajax-initiated SOAP and REST services calls. Results in faster response time, less network traffic (good for slow links), and less work on the server.
- Pages are not generated on the fly at runtime – application exists as static HTML and JavaScript. Results in less work happening on the server. Subsequent interactions with the server occurs via Ajax-initiated SOAP and REST services calls. Results in faster response time, less network traffic (good for slow links), and less work on the server.