cgpSoftware

This will come in handy:

Testing Spring Controllers with Raible - It's not a complete guide, but it does contain a test, which I haven't seen most other places.

I like it when we get a healthy discussion of what certain patterns are. This is a good example, albeit a little bit heavy on the lingo:

* DAO

IOC
* Injection/Inversion of Control/AOP

Doing persistence with JPA and a persistence provider is a straightforward process:

* Struts 2 + Spring + AJAX -- Good example. I got it working, but I did need to add in:

<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-commons-annotations</artifactId>
<version>3.2.5ga</version>
</dependency>

to my maven pom.xml (I also had to download and install a couple of other depedencies but that part was straightforward.
* Getting started with JPA and Spring

* Generating Hibernate POJO classes from DB tables
* Some sort of reference to the annotions of JPA
* Master the New Persistence Paradigm with JPA
* A Followup to Mastering the New Persistence, a little more advanced.
* 90th Percentile, JPA and Spring are the cools
* JPA Annotations Guide
* Advanced JPA with spring
* The hibernate tutorial
* Unitils
* JOTM Transactions In Spring And Hibernate
* Lucene integration with Spring and Hibernate

I've been torn about writing an application to maintain information for within my other love, WWME. I've just been torn about being inspired to do something interesting and different for it. I don't know how to make it interesting. Data entry is a large part of what the application does, but I just don't see people using it to do that, because data entry is boring.

So, what interests me now is how to make that interaction work differently. How to make that interesting. Some ideas I have had:

1. There should be a lot of interaction through email.
2. Highly graphical. Not graphical in the EXT-library sense of the word, but a lot of color and a lot of elegant font usage.