0.75 Hour Hasty OzarkCABOOSE Integration | Kludgy

Team. Below is the link for a NetBeans archive which contains a hybrid Ozark-CABOOSE web application.

OzarkCABOOSE
https://drive.google.com/file/d/0B101EUHMgepNSWlpaU44a1JqMVk/view?usp=sharing

The application is rather kludgy and the support which connected CABOOSE with Hibernate and web-service data sources has been removed. The was simply melded quickly and the fat needs trimming. This is only a draft. Ultimately, the CABOOSE functionality will be bundled in a JAVA archive.

Have a Great Week... The CABOOSE Team

Four Extra Hours of Effort | CABOOSE - Ozark Integration | Early Draft Release for the Ozark Specification (EDR)

Team. Although we have not put the finishing touches on the CABOOSE source and placed it in a JAVA archive for distribution, we are melding the CABOOSE and Ozark products this week with the production of a ViewEngine for "caboose" views. Hopefully, we will have a NetBeans archive available early next week. With the completion of a five month project, an extra four hours of effort have been "freed up" in our work schedule for CABOOSE. This should allow for more weblog entries and development.

We had promised a summary of the first EDR of the Ozark Specification a month or so ago. Well, a second document has been released by Oracle now which exceeds the content of the first. So, we shall start working on a summary of that one.

Enjoy This Weeks Work Efforts...

The CABOOSE Team

CABOOSE Source Draft And "Hello" Example WebApp

Team. We missed celebrating our birthday. Based on the records in this draft source, we started this NetBeans project in mid-October 2014. The development process for this code is in-line in earlier post from 2015 and possibly late 2014. We probably should have placed these NetBean project (*.zip) archives on-line earlier this year. This would have eased creating a working sample of the CABOOSE servlet which we are evolving for service in an Ozark controller. Copy the source from the weblog is a tedious approach. We apologize for the lack of instructions for this, but it should be a breeze if you are comfortable with importing project for NetBeans. Our final goal will be a JAVA archive for use in future web applications. Note: This source is under a copyright as described at http://java.net/projects/caboose.

CABOOSE
https://drive.google.com/file/d/0B101EUHMgepNd19KM1JwU1JZTUE/view?usp=sharing

JAXRSHello
https://drive.google.com/file/d/0B101EUHMgepNQ1l3NWtCbktpNDA/view?usp=sharing

JAXWSHello
https://drive.google.com/file/d/0B101EUHMgepNeDVkUWdnQVZjT2M/view?usp=sharing

These can be imported, compiled, deployed, and run in NetBeans. A fully functional example web app will require completing the table design and configuration for the Hibernate transaction.

We are attracting more web traffic. Thanks for the interest....Hunt, Peck, and Think....

The CABOOSE Team

Bean Validation and Context Dependency Injection - Super Records

Team. We have been doing some reading on Bean Validation (BV) and Context Dependency Injection (CDI) over the past few weeks. We are hoping the we can include some of these features of JAVA in our solution. The constrained parameter list in BV would be very useful in enforcing the programmatic contracts found in our source which we placed in the earlier posts around January 2015. Also, CDI and Beans might prove useful in partitioning and organizing the concerns associated with processing the view directory XML file. This is since each mapping between view, page replacement variable, and rendering method is store-able in a Bean (record).

Super Records

In all honesty, we have not mastered JAVA Beans at the highest level. They are a very novel and interesting approach at processing data and take the place of those "old-fashioned" records found in languages such as COBOL, FORTRAN, and C from the 1970s, 80s, and beyond. In fact, they are "super records" in that a Bean can contain "inspector" methods which supply its properties values or combinations thereof. So, one can incorporate the "business logic" calculations found within an application in a Bean. They are a vital part of the JAVA Persistence Architecture (JPA) and products such as Hibernate. Plus, with bean validation one can apply some of the program correctness measures common in more formal programming approaches quite easily. They might also be found in the common JEE MVCs: Struts, Spring, and Hibernate. We will be working on mastering these concepts before delivering CABOOSE in a JAVA archive (*.jar) form.

Thank you for reading our posts over the past year. We appreciate your interest.

The CABOOSE Team