Home of: [Atelier "FUJIGURUMA"] >> [PageMixer hosted by SourceForge.net]

SEE "For Readers of English Version",
or Japanese version of this page

What PageMixer is - (7/7)

Appendix

Related links

JUnit

It is one of testing frameworks, and designed for unit test.

HttpUnit

Home page of HttpUnit.

It is one of testing frameworks, and designed for Servlet test. It focuses on testing of HTTP communication and response HTML data.

Jakarta Cuctus

Home page of Cuctus.

It is one of testing frameworks, and designed for Servlet test. It focuses on testing of Controller(of MVC) functions of Servlet.

Macromedia - DreamWeaver

Product home page of Macromedia DreamWeaver.

Around me, it is evaluated as the best "HTML editor" because it esteems code explicitly written by user. However, Emacs is evaluated as the best "HTML editting tool".

Comparisons

Overview

---- JSP PageMixer XMLC
treats page as String sequence(like SAX) tree(as DOM)
design of page is in JSP in HTML in HTML
processing of page is in JSP as Java program as Java program
executable only in Servlet container anywhere anywhere

Processing

---- JSP PageMixer XMLC
processing is defined as Java code/embedded in JSP Class/ "Filter" of sequence Class/processor of DOM
re-use of processing "include" directive(or TagLib/JavaBeans) re-use of "Filter" re-use of processing method(or class)
re-usability of processing low(middle if TagLib/JavaBeans are used ?) high (may be)high

Testability

---- JSP PageMixer XMLC
unit test of processing(stand-alone) difficult easy easy
preparation for unit test ---- easy difficult(DOM tree is needed)
test of HTML generation difficult(needes Servlet envrionment/HTTP connection) easy easy

Design separation

---- JSP PageMixer XMLC
re-use of processing "include" directive(or TagLib/Javabeans) re-use of 'Filter' re-use of tree processing method(or class)
design visibility in processing re-use low(if HTML editor does not support JSP directive) high high
merge of design and processing difficult easy easy
tag element level design check no yes yes

Update page

---- JSP PageMixer XMLC
page representation class(compiled JSP) object(sequence of "Token") class(to create DOM tree)
update of page data Class re-load Object re-read Class re-load
Auto update yes yes yes(????)
customizability of update difficult easy difficult

Performance

---- JSP PageMixer XMLC
page data "String" embedded in compiled class sequence of "Token" DOM tree
page data shareness yes yes no
cost to create page data --- --- high
processing is defined as Java code/embedded in JSP Class/ "Filter" of sequence Class/processor of DOM
page processing shareness yes no yes
cost to create processing units --- low ---
cost to render HTML page low middle(no intermediate string) high(traverse of DOM tree)
cost to create new page low middle(or low) high

Jump to your favorite page from navigator bar at the top/bottom of page