HybridJava:Is Not

HybridJava is not for those who do not know Java, however knowing only HTML and Java may be enough.

HybridJava is not built on top of JSP or JSP 2.0, but only on top of Servlets.

HybridJava technology is not aggravated with any kind of configuration. In fact, the compiler internally generates configuration based merely on the set of .page , .widget and .java files available. Neither does HybridJava technology camouflage configuration as Java annotations. In particular, HybridJava is XML free.

HybridJava is not a client-side technology though its framework relies on some basic JavaScript. HybridJava is transparent to any client-side technologies (like AJAX or FLEX).

HybridJava is not about data persistence beyond Servlet session scope. Its domain lies strictly within the Presentation Layer. It does not matter if behind the Presentation Layer the application uses Hibernate, EJB or JDBC.

HybridJava is not a "template engine" - it capitalizes upon real compilation and thus upon a deep formalized understanding of the application code.

HybridJava Framework does not include page navigation (workflow) which belongs to some other technology layer. Same is true regarding authentication and authorization.

HybridJava does not provide any predefined widgets. Those included into the release ZIP file are just samples. Our presumption is that a web technology should in many occasions make it easier to write your own set of widgets than to study those predefined. We suggest that the priorities of widget reuse are: firstly reuse widgets within one application, secondly - within a company, and only then between different companies.

JSP specification prescribes implementation to create instances for each custom tag. Besides, instances of JavaBeans type are required for each data transfer within the presentation layer. The latter even results in a special technique of handling data synchronization. In our framework instances are created only for those widgets that really need them because they have state and/or behavior. Pure presentation widgets in HybridJava are truly lightweight: they are compiled to nothing more than parts of the single rendering method of the page. Generated code accesses presentation data directly, so no JavaBeans are used, and no synchronization is needed.

HybridJava does NOT use forward, redirect, XSLT, DTO.

HybridJava does not build DOM at runtime.

HybridJava programmer does not have to manually deal with IDs of components.

HybridJava will never require 800 pages of manual. Not even 40. Thus HybridJava is a Green technology.

Nothing like TagSupport class (JSP) or UIComponentTag class( JSF) is used. There is no such thing as Fragments (Wicket, etc.).

We do not have any special Expression Language. Java is the best EL we know. In HybridJava you simply use Java expressions.