Re: Apps developers - separation of interface and impl

[Paul Hammant]

Stephen,
Looks to me that you are beingh shot down not on the grounds of
seperate jar files - but on the grounds on the introduction of seperation
at the level of package names.  Why do you need different package names
anyway? 
1) package sealing.  
2) implementation hiding : ye olde K/HC/CAPI :-

 CAPI-Impl  HostedComp1  HostedComp2
   |          |             |
   --------------------------
      |
  Client API
      |
   Kernel
As is with servlet (a standard for class visibility defined by sun)....
 Container.jar  App1.war  App2.war
   |             |           |
   ---------------------------
      |
  servlet.jar
      |
   ContianerBootStrap.jar + rt.jar
The point is that the K/HC/CAPI "pattern" exists in may places.  Sun 
defined an example with the servlet spec.  With Phoenix we see multiple 
K/HC/CAPIs in one tree of classloaders (in itself an advanced Java topic).  

e.g. Phoenix mounts a SAR file that is a web server.  It mounts a web 
app.  That is two K/HC/CAPI separtions in one JVM.  With JAMES (and 
Mailets), FtpServer (and Ftplets) and EOB (with beans) there could be 
many more in one JVM.

-ph
--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>