On 07/20/2011 08:46 PM, Adam Brons wrote:
Hey Gang,
I was hoping that the masses could help solve a naming problem that
myself a few other leads are having with deciding on a package naming
convention for models and services that are going to be externally
published.
We've thrown around ideas like
"com.example.appname.servicename.api.model",
"com.example.appname.servicename.published.model",
"com.example.appname.servicename.external.model", and
"com.example.appname.servicename.framework.model". We're not stuck on
any of these names, but aren't able to think of anything better or
decide on one we've listed.
This is a complete experience / opinion question see feel free to
weigh in, all comments are welcome.
I personally follow this personal scheme:
com.example.appname.servicename.* for anything that is to be
exported and directly used by client code (API)
com.example.appname.servicename.impl.* for anything that is only a
local, private implementation
com.example.appname.servicename.spi.* for anything that is to be
exported, but not directly used by client code, rather by extensions of
the module to provide alternate implementations
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
[email protected]
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
