Re: Repositories, package dependencies, and domain-flavoured exceptions
- From: "chuck" <cmedcoff@xxxxxxxxxxx>
- Date: 26 Jul 2005 09:30:13 -0700
iamfractal@xxxxxxxxxxx wrote:
> > Question #2: Are Java packages really appropriate to be determining
> > illegal package dependencies?
>
> Oh, good lord, yes, yes, and thrice yes. Java packages (and C#
> namespaces) are absolutely, god-sendingly ideal as a hierarchical
> encapsulation granularity for a large system. It's far more worthwhile
> concentrating on inter-package dependencies than inter-class
> dependencies within a package. You are doing The Right Thing.
Consider doing this analysis at the "binary package" level (aka jar
file for Java and Assembly/DLL for .NET). Issues surrounding division
of development labor, testing, distribution and reuse are typically
related to "binary packaging" not namespaces. Java packages are really
just a namespace mechanism. Of course doing the analysis at a
namespace level might help you determine what namespaces (and their
classes) need to go into what "binary packages" to address whatever
division of development labor, testing, distribution and reuse issues
you need to plan for.
See Martin's papers on (binary) package cohesion and coupling at
http://www.objectmentor.com/resources/articles/granularity.pdf and
http://www.objectmentor.com/resources/articles/stability.pdf.
.
- References:
- Repositories, package dependencies, and domain-flavoured exceptions
- From: Jason Che-han Yip
- Re: Repositories, package dependencies, and domain-flavoured exceptions
- From: iamfractal
- Repositories, package dependencies, and domain-flavoured exceptions
- Prev by Date: Re: Template documents
- 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):
Relevant Pages
|
