[Cosmo-dev] Name space convention
Brian Moseley
bcm at osafoundation.org
Thu Aug 10 16:47:30 PDT 2006
On 8/10/06, Vinubalaji Gopal <vinu at osafoundation.org> wrote:
> Say I have a package "a" and package "b" with similar classes, for
> example say "package a" has X.java, Y.java and "b" also has similar
> classes with same functionality as X.java and Y.java. Is it good to name
> the file as bX.java and bY.java in the package b? Right now the cosmo
> convention is to use this kind of approach (I think its there to avoid
> the confusion.
> Eg:
> org.osaf.cosmo.dav.caldav.Caldav*
we use this convention so that when referring to a class it's easy to
understand the context of the class even if the class name is not
package qualified. we also use it to distinguish the class from its
superclass or an interface its implementing (eg DavResource).
More information about the cosmo-dev
mailing list