Oscar, Matt: thanks for your clarifications. Transactions was also
something that came to my mind when I was thinking about what could go
in a service layer. I'll have a look for more info in the list archives.
Ger-Jan
Matt Raible wrote:
Oscar is correct. There's nothing prevent you from usin
Oscar is correct. There's nothing prevent you from using DAOs directly
in your Actions, but I generally use them to aggregate calls to DAOs.
Also, transactions are set to happen at the Manager level rather than
DAOs. There's lots of similar questions on the mailing list - you
might want to do some
Hi,
I think the decoupling dao/service layer is because in the data access layer
you access your data without worrying about your business logic. I always
think of data layer as small bricks and the service layer being composed
with these small bricks.
Also, in the service layer there are annotatio
Hi,
Here's a couple of questions for you architecture boffins:
It is clear that the source tree of Appfuse is neatly organised. I can
see the purpose of having a dao package with interfaces and one or
several dao/impl packages with specific implementations for those dao
classes: it makes it e
