Re: Repositories, package dependencies, and domain-flavoured exceptions
- From: Jason Che-han Yip <jcyip@xxxxxxxxxxxxxxxx>
- Date: Wed, 27 Jul 2005 19:14:24 +1000
hansewetz@xxxxxxxxxxx wrote:
....
In your case the exceptions belongs to the business object layer. This should not cause a problem since the access layer should only invoke business functionality through business processes. There should be no need to access the business object layer directly from the access layer.
....
In this particular case, the "access layer" needs to be able to access the exceptions in order to determine how to present them. How would you propose to resolve that, given enforced dependency restrictions (access -> business process -> business object) and placing domain-flavoured exceptions in the business object layer?
.
- Follow-Ups:
- References:
- Repositories, package dependencies, and domain-flavoured exceptions
- From: Jason Che-han Yip
- Re: Repositories, package dependencies, and domain-flavoured exceptions
- From: hansewetz
- Repositories, package dependencies, and domain-flavoured exceptions
- Prev by Date: Re: Repositories, package dependencies, and domain-flavoured exceptions
- Next by Date: Re: Repositories, package dependencies, and domain-flavoured exceptions
- Previous by thread: Re: Repositories, package dependencies, and domain-flavoured exceptions
- Next by thread: Re: Repositories, package dependencies, and domain-flavoured exceptions
- Index(es):