HybridJava
technology does not do everything.
HybridJava
technology is not aggravated with any kind of configuration (so far). In fact,
the compiler internally generates configuration based merely on the set of .page, .widget and .java files available. Neither does it 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
anything like AJAX or FLEX.
HybridJava is
not about load balancing or 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 persistence 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) or
validation - both belong to some other
technology layers. Same is true about 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.
HybridJava
does NOT use JavaBeans, forward, redirect, XSLT.
HybridJava
does not build DOM at runtime.
HybridJava
programmer does not have to manually deal with indexes 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.).
Java is the best EL we know. In HybridJava
you simply use Java expressions.