Drop

This application was designed and implemented as my first web app following the DDD principles. There are some interesting issues to solve. I had the domain models exposed to the presentation layer. No facade!??? Yeeeeaah, but not exactly. I did not see the similar design at other places yet. Which has no facade in front of domain models, no facade between presentation and business layers. I can imagine the reaction from people who are so used to facade. Spring+AspectJ allow you have this design. Using domain object that has the supporting DAO injected and letting "spring's annotation transaction aspect" handles the transaction. It can work. Although, using Spring+AspectJ can implement this design, it doesn't necessarily mean this design is good for all applications. An evaluation needs to be done. Here are the pros and cons . Pros: Faster development. It accelerates the development. No Facade for the exposed domain model. When a domain object is a natural entry point

Facelets Before knowing this, I can hardly think of a reason to use JSF. There are many benefits from using Facelets with your JSF app. I like the most is the "jsfc" attribute. What it does is converting xml element to another at runtime. With this feature, JSF can finally be "designer friendly". Although I haven't find a way to get the facelets template also friendly to html designers. It's hundred miles better than using bare JSF. From: <input type="text" jsfc="h:inputText" value="#{hello.world}" /> to: <h:inputText value="#{hello.world}" /> Inside Facelets Facelets fits JSF like a glove Developer Doc TestNG I like its annotation, data provider, dependent methods, and some other flexible features. TestNG Doc EasyMock Doesn't matter you are a classical or mockist styles of Test Driven Developer, you will find EasyMock is a good tool in your pocket. Mocks Aren't Stubs EasyMock Doc Shale Ever wondere