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
No comments:
Post a Comment