Java Application Server
Our Java Application Server is the foundation of many of our WEB and cCommerce solutions. It is a fully
functional WEB and application servers combined. It allows you to run sites and WEB applications of any complexity.
It's written in Java 100% so we can run it on any platform such as Windows, Linux or Mac (or anything else that supports Java).
With its low footprint, easy administration and high performance it is an agile yet solid platform for your applications.
The server was originally developed in early 2000's as an internal tool. Other Java application servers at the time
were fat, complex and slow, mostly supporting J2EE technology (Enterprise Beans) in its early stages. We quickly
realized that our server can be used much more efficiently in our projects and solutions at the time. For instance it could
easily be bundled with installation of a software package and effortlessly installed in a client machine (try to
do it with BEA Weblogic and the challenges would be endless).
The server provides the following main features:
- Hosting any number of WEB sites and applications
- Built-in support for XML beans and XSL transformation
- Secure Socket Layer (SSL)
- Java Server Pages (JSP)
- Built-in background scheduling and processing
- Remote administration
- Integrated authentication (through LDAP)
Although the server supports JSP, we prefer using XML beans especially for complex applications. As you may
know many projects tend to become more and more complex. Plainly put, you write a code that accepts XML input
and produces XML output. All you have to do is to write a logic in between. All the information coming from the
browser including URL, query string and form fields is automatically converted into XML input and therefore is
universally accessible from your code. XML output of one bean or function
can be used as XML input in another, so you can chain them any way you like. At the end, XML output can be
either rendered using XSL transformation and served back to the browser, or sent directly to the client, for example
a system that can consume it.
As you may see, the logic and presentation are separated completely. They can be developed and
tested independently by different groups with different skill sets. For instance, Java developers can work on
XML beans and test the functionality even before the presentation layer (XML) is ready. Meantime, design
team can work in parallel on the presentation creating XSL libraries and testing them with sample XML data.
Natively, you may have many presentation layers (or skins) for your application, switching them via simple
configuration or even during runtime as user preference. This can go far beyond colors, fonts and images. You may
tailor presentation layer to the needs of your application including different customer experience. For
instance you can effortlessly private-label your application or create a mobile version just be switching
previously developed XSL library.
We realize that for some of you it may sound too technical (and that's OK!) and for some too brief. This is why
we want you to contact us and we will be happy to answer any questions and provide