The Common Architecture

Wow. The Common Architecture Classes we are working with is a huge bundle of seemingly abstract functionality (oxymoron?). Just the small project we are working on this week can be a bit thick to step through. It is pretty neat what they have set up for us to use as a foundation, but it can sure be a head-ache getting everything setup correctly on your machine so that it builds correctly. Now we are working in groups of 2 checking code in and out of a CVS.

This weeks project is pretty straight forward, just add functionality to what is already there. This gives us a chance to really wrap our minds around what is already happening within the system. By the end of this training we should know this stuff in and out (mostly) but for now it is a slow process. There are so many classes up the heirarchy you may have to go up several super-classes to find out what a simple bit of functionality is. In this long run it will be easy to grasp, but for now it is just mind-boggling.

On another note, it is both welcome and regret to be doing this as a web project. Welcome because I am familiar with Web technologies and what goes on, plus I haven't actually worked with any J2EE projects so many of the tools we deploy are new to me in practice. Regret because as mentioned I've done web developement (but not on this scale so that is another plus) and I was looking forward to deploying different types of apps. But to tell you the truth without sounding really redundant, there are so many new tools to use in the J2EE world that it does feel like I'm in new territory. I am looking forward to moving on into the projects and getting more familiar with STRUTS and the other technologies and patterns surrounding it.

Current Recreation: Reading Harry Potter and the Half Blood Prince
Research Shopping list: JUnit/Unit Testing materials, STRUTS references

Until next time,
Les Martin