geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Mulder <>
Subject Re: [core] why org.apache.geronimo.enterprise.deploy.provider package?
Date Tue, 19 Aug 2003 02:40:45 GMT
	The enterprise.deploy package is currently the JSR-88 area.  We 
used enterprise.deploy to distinguish from "deployment", which seems to be 
server component deployment instead of application deployment.

	As for "provider", it's to distinguish it from the tool side,
which will be used for management consoles, etc. and from the objects
(generated by Castor into "common" in the pending patch) that represent
that actual J2EE component metadata (the object representation of the DDs,
in other words) and from the stuff (currently not implemented) that will
actually do the work of deployment on the server side.

	I think the provider stuff should remain separate from
"deployment"  because its only a JSR-88 implementation -- it's the GUI
logic (and potentially widgets) that a tool will use.  It's full of
JavaBeans (particularly if you look at the xxxBeanInfo classes in the
pending patch), and they all have to be packaged together and separately
from most everything else in order to be distributed to tools (the patch
also creates a JAR out of these classes, with a manifest full of bean 
declarations and so on).

	Finally, if you repackage everything without looking at my patch
first, I'll...  I'll...  I'll send it a fourth time!  But if you are going
to repackage it, some of it probably ought to go in a different module,
not just a different package.


On Mon, 18 Aug 2003, Dain Sundstrom wrote:
> Why do we have a org.apache.geronimo.enterprise.deploy.provider 
> package?  Geronimo is an enterprise server, so this is redundant.  I 
> suggest we move provider inside of org.apache.geronimo.deployment.  I 
> am willing to make these changes if no one objects.
> -dain
> /*************************
>   * Dain Sundstrom
>   * Partner
>   * Core Developers Network
>   *************************/

View raw message