Well .... i don't why people are silent.
I'm not a certified architect yet. But from previous postings what i read, i feel that class diagram should as generic as possible. It should be technology independant. As many people indicated, you can put a note to each CustomerProcessor / ReservationProcessor saying that in
J2EE it will be implemented as a stateless / stateful session bean. I guess, no need to include DAO, controllers etc.. in class diagram. That all will go in component diagram. Make your class diagram as generic as possible. That's how i'm implementing actually.
Other ranchers, provide your inputs too.