drVillo, I think once you are really familiar with Seam, extending it to cover
complex situations is a more or less straight point.
Seam manages pretty well to solve most of the dependencies.
I would agree with you if you were talking about advanced application
configuration, but again that's a
gavin, thx for the quick answer, this sounds really good ..
being free to choose and design the overall architecture and not being inforced
by a particular framework is a basic requirement in my opinion.
however, i fully agree to drVillo, it would be great if you could provide some
more docume
This is a topic I have been thinking of opening as well.
It is still unclear to me to which extent using Seam pays off when you have to
deal with multiple presentations for example.
I would like to see something like sun's blueprints for scoping and injecting
Seam into a layered application.
Fo
1) Not quite: Seam makes simpler architectures *possible*, and essentially lets
you layer your application however *you* like. You can certainly follow
whatever architectural patterns you prefer, and in particular you can certainly
have your entity beans have no Seam dependency. Up to you to wei
