Over the last few days, I have been asked several times - "Why EGL?". It's a good question. For those of us that have been around EGL, the answer is obvious: spend more time innovating and less time fighting with technology
- Completely code, test, and debug without deploying anything to an application server. The Preview tab of the EGL editor provides a running version of your application. When you switch to this tab in the editor, your EGL code is compiled on-the-fly. You can also set breakpoints in your code for easier debugging (EGL CE uses the standard Eclipse Debug tools and perspective). Best of all, you don't have to deploy services to a server to debug them.
- Integrating with existing services. EGL supports calling existing SOAP and REST (JSON or XML) services. So, if you already have Web services up and running, you can use EGL to build a new UI. Within your EGL code, input and output to the service is represented as EGL variables or records. In the case of SOAP services, EGL will automatically create the input and output records for you - all you need to do it import the WSDL file.
- Data access. EGL makes interacting with databases simple. EGL provides simple keywords (get, add, delete, etc) to easily work with a database.
- Easy deployment. With EGL, you can fully develop and test your application before ever deploying it to a server. Once you are ready to deploy, however, EGL CE deploys code into a standard Eclipse Dynamic Web project. This project can be run on Apache Tomcat or packaged as a .WAR file and deployed to an external application server.