![\"coding\"](\"http:\/\/www.lordandrei.com\/blog\/wp-content\/uploads\/2014\/01\/coding-300x225.jpg\")
I’ve been fairly quiet on the blog the past two weeks. This has been because I have been head down in code catching up from the holidays and being sick. I know all to well how abstract and vague I’ve been on what The Project is. I’m still shooting for a grand unveiling upon the ides of March. (March 15 for those who read not the Shakespeare)<\/p>\n
I however do not want to be without any information. So I decided to play the magnifier game. This is the game where you show someone a picture of a common object through a magnifying glass and let them guess what it is they are looking at. Granted, that’s not my intent. I know what I’m showing is intentionally obfuscated to hide The Project’s intent.<\/p>\n
However, I want to show a checkin from one of the classes that I did today to talk about what’s going on.<\/p>\n
I’ve make no secret that this project uses a database to manage the content and Java and Tomcat to serve as a buffer to clients. Today, I am working on the database upload abstract class. In revamping my Java Servlets this past week, I have managed to completely abstract the query command class to the point that I can create any pre-packaged SQL query on the database into a 4 line subclass. This subclass can handle variant queries, compares, subqueries, and most importantly documentation on the return. This work made me very happy.<\/p>\n
In pushing data up to the database there is more work needed. I have to verify that the call is including the correct information. I have to make sure that the subclasses have defined the necessary info to check. (So subclasses will be closer to 10 lines instead of 4)<\/p>\n
Effectively, a push command should identify the table in the database, the usable column names, the required column names. And of course error check and return the response in a consumable way.<\/p>\n
Below is my checkin comments from today’s abstract Class work. (Note there are redactions)<\/p>\n
(Ah, the fun of Java)<\/p>\n
imports java.util.List\r\nadds ivars\r\n\tMUST BE OVERRIDDEN List requiredHeaders\r\n\tMUST BE OVERRIDDEN List usableHeaders\r\n\tString sqlQueryHeaders (for building sql update)\r\n\tString sqlQueryValues (for building sql update)\r\ndoSQLQuery() now doSQL()\r\n\tsetRC not setRS with executeUpdate instead of executeQuery\r\ngoGet()\r\n\tSends a formatted json error response (put, not get)\r\nvalidateSubClass() (new)\r\n\tChecks to see that there is at least 1 usableHeaders\r\n\tChecks to see that there are no more required headers than usable headers\r\n\tChecks that all required Headers are in usable Headers\r\n\tChecks that there is a table conversion equiv in getDbaseTable() {below}\r\n\tThrows Exception (Programming error) if any of these cases fail.\r\nvalidateRequest() (new)\r\n\tVerifies that required headers are in the request http Header\r\n\tReturns first missing required header if failure\r\nprocessHeaderPair() (new)\r\n\texamines each HTTP header pair\r\n\tsearches for headers that are: Package.Command.usableHeader\r\n\tconverts them into caseCorrected usableHeader and Value\r\n\tAppends them into Strings for use in SQL Update request\r\ngetDbaseTable() (new)\r\n\tconverts servlet full DNS name into table in Database\r\n\treturns null if not set.\r\ndoPost() now doPut()\r\n\tAdds failNote as a return from validateRequest()\r\n\tCalls validateSubclass()\r\n\tCalls and evaluates validateRequest()\r\n\tRuns ProcessHeader() while iteration headers\r\n\tBuilds SQLQuery (Should be update)\r\n\tCalls doSQL() and evaluates\r\n\tre-Enables SqlResult display in output\r\n\tErrorIn -> ErrorLoc\r\n\tShows failNote<\/pre>\nOn top of this, since you can’t test a PUT command in a browser; I’ve had to write a mini Putter app on my Mac. Let me assure you, hopping back and forth between Cocoa for OS X in Xcode and Java for Servlets in Eclipse can be a bit of a mind scramble.<\/p>\n
Share this:<\/h3>