Team. We have been working on developing our JAVA Enterprise Edition CABOOSE product which integrates with Oracle MVC 1.0, Ozark. Over the past weekend, we hand-drafted the CABOOSE site
which is currently a few static XHTML pages that have not been validated. If
one examines these carefully, one will realize that the header and
footer for each page are the same. The only unique content is in the
body of the documents. This "primitive" content can be factored out of
each page which will leave the base template. We can then supply this
template and the appropriate body content when a browser requests that
view.
In other words, the CABOOSE site is a good
candidate for the model-view-controller (MVC) architecture.
Unfortunately, the web hosting package for this site does not support
JAVA Enterprise Edition development; however, it supports the LAMP
technologies. So, we will spin a quick MVC for the CABOOSE site over the
next week using the PHP Hypertext Processor (PHP). We already have the
source since we used PHP as a prototyping language for the CABOOSE
concept when we proposed a JAVA Specification Request (JSR) for a
general-purpose web-script. We shared this PHP prototype with members of the JAVA Community Process(JCP) with a few instructions.
Although not immediately accepted, the way in which CABOOSE project
partition concerns creates a more cognitively accessible development
approach. It also allows for a greater use of existing web standards.
The
current PHP prototype is not highly robust; however, it is reliable
enough for simple view handling. So, we have started making a few entries
on our PHP CABOOSE weblog.
Have a Great Week.
The CABOOSE Team
No comments:
Post a Comment