In-between sessions I started jotting down notes about a concept around creating a series of "junk code" projects. I started to solidfy my thoughts around how best to continue to develop my own skills, but also to be able to share them with the public.
What I came up are "Sample Code Projects" (dubbed "Junk Code" in my JavaOne notes). A sample code project will be a small working example illustrating the usage of technology. They will be detail-oriented providing:
- clear instructions on how to obtain, build and run the project
- describe the folder structure of the project
- clearly commented artifacts (source code, build scripts, etc)
- Leveraging of CDI in Java EE 6 (contexts and dependency injection)
- Expansion and refinement of the command design pattern (both server AND client use command objects; the JavaOne demo did not leverage commands on the client)
- Refined Ant build script that enforces a separate between client-side and server-side code
- More finely-grained and refined project structure
- Castor-based marshaling (the demo app uses JAXB)
- There is no rules engine integration (for simplicity; the JavaOne demo app integrates with Drools)
- There is no UDDI integration (for simplicity; the JavaOne demo app integrations with jUDDI)
In case you're interested, here are my raw notes I took at JavaOne as I was thinking through all this.
![]() | ![]() | ![]() |
![]() | ![]() |




