I took a JavaEE course today and I was presented to the "default" JavaEE architecture, which consists mainly of Entities, Services and DTOs. The guy presenting the course explained that it was indeed a case of anemic models, but however this was the "in facto standard JavaEE architecture".
I am new to JavaEE, but I've head some experience with other languages. The first time I read about beans as components, I thought they would be great to create a DDD-like architecture.
It sounds strange to me that a "standard architecture" has a anemic domain (I, until now, thought it was a "bad smell").
Is there any technical reason or big advantage of using this architecture? Why an architecture that defines its models to be anemic is the current standard?
I asked him and he talked about transaction context, but I have to admit I didn't understood exactly what he meant.