Benefits of Pajes
JSP is the standard, so why use Pajes instead.
JSP was created in an attempt to counter the influence Microsoft were having in the formative period of dynamic page generation with their Active Server Pages (ASP) technology. It subsequently became the standard approach through widespread adoption rather than design elegance. Both JSP and ASP embed code (Java for JSP, Javascript or VBScript for ASP) inside an HTML page. It's simple for new developers to grasp the approach, and initial return on effort is fast.
But it is also pretty inflexible and developer effort increases with the sophistication of interface.
Mixing HTML and Java together hampers flexibility and makes change and code reuse difficult.
Pajes is also standards based and fits into J2EE in the same place that JSP fills, plus it has a few other benefits:
  • Application and website "skinning"
  • Separation of function from presentation
  • No proprietary application server, Pajes runs anywhere that the 2.3 or later Servlet API runs (and that's just about everywhere)
  • No proprietary tags, scriptlets, applets or markers required at the browser or in the HTML template - just standard HTML and Javascript
  • Built-in, automatic browser detection and abstraction
  • Built-in, automated internationalisation (This is important)
  • Automatic compression (if browser supported)
  • Automatic query parameter obfuscation
  • Query parameter storage in session (reduced net traffic, increased security)
  • Built-in widgets such as tree controls and transparent multi-part file upload support
  • It's tiny and it's fast (check the "getting started" download)
overview pajes and skinning