ClassiX® can also be used as web applications - as so-called InstantWeb applications. The InstantView® code does not change for these InstantWeb applications. The interface just appears no longer on the computer screen where the ClassiX® System is running. Instead it is converted into HTML pages and transmitted to a browser via web server. This makes ClassiX® become an application server, which executes the code without performing the display (here: done by the web browser).
The InstantWeb Generator transfers InstantView® pages computer-based into InstantWeb pages. Afterwards, the developer only needs to refurbish the generated JSP pages. This requires no programming skills - just HTML knowledge, since JSP pages are quite similar to HTML pages.
Since a web browser cannot display a full-fledged ClassiX® application, there are the following constraints:
A web application can be split up into 3 parts: The browser on the user side, a framework based on struts on the web server side and finally the ClassiX® System as the application server. The framework and ClassiX® are not necessarily on the same computer (this is indicated by the gray dashed line):
![]() |
Web Browser |
| Web Server such as Apache Servlet Container such as Tomcat ClassiX® Servlet based on Struts |
|
| ClassiX® |
In simple terms: The DLL cxwnt???.dll controls data traffic between the ClassiX® libraries and the struts framework. Java code connects both parts. This code can be adjusted to individual requirements. If possible, leave the core unchanged to guarantee for correct functionality!
There are 2 InstantWeb-specific DLLs in the bin directory:
Furthermore, there is a directory called "InstantWeb" under the CX_ROOT directory, which contains a batch file for the start and several configuration files (generally just InstantWeb-init.xml). Under this, there is finally a directory "lib", which contains several libraries (for graphic overview).
|
|