|Eclipse Scout Architecture: Why is there a Web Server / Web Container? [message #808302]
||Mon, 27 February 2012 16:22
| Kai Wähner
Registered: February 2012
After looking at the architecture of Eclipse Scout several times and doing some hello world stuff, I wonder why there is a web server / web container?|
To get a better understanding, can you please explain:
1) Is it a web container or a web server? The examples use a Tomcat Web Container (JEE Servlet Container) - which can also be used as Web Server. The architecture graphics show a Web Server, therefore a "simple" Apache Web Server would be sufficient? Or do you need a Servlet Container?
2) Eclipse RCP can be used without a Web Container, nevertheless you can communicate between a Client and a Server using several protocols, right?
The "Service Tunnel" of Eclipse Scout just uses plain HTTP to transport XML (SOAP) messages. There is no Servlet or JAX-WS usage for this communication?
Therefore, there is no need to deploy on a Web Server / Web Container for just using Eclipse Scout client and server, right?
3) Is a Web Server / Web Container used respectively required for RAP?
4) Is a Web Server / Web Container used respectively required for distributing the Scout client, i.e. the user can download it from the web browser link?
5) Is only question 3 and / or 4 the reason for using a Web Server / Web Container? Or are there other reasons? If not: Could I use Eclispe Scout without Web Server / Web Container if I do not want to use RAP or online distribution of the client?
Thank you in advance for some explanations.
[Updated on: Mon, 27 February 2012 16:35]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01935 seconds