You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Dave Bryson <da...@miceda-data.com> on 2001/04/18 02:59:28 UTC
expanding on Sub-apps
Hey everyone,
Here's some thoughts expanding on the sub-application proposal.
* Loading sub-applications:
-- have a Deployer utility or service that monitors a path set in the
Turbine resources file. Any subpplication (Jar or Zip) added to this directory
can be deployed, undeployed, or re-deployed.
-- When the Deployer locates a new or re-deployed Jar it will load it, query
the package Manifest for the application name and package info. and add the
unique name and package info to the application map. An application map is a
map of unique application names to package info. It essentially replaces the
module.package. Package info can be added at runtime by the Deployer.
* Loading classes
-- Create an assembler for loading requested screens, actions, etc.... Given an
application name and class, query the application map for the app name. If the
name is found use the package info to locate the appropriate Jar and try to
load the class.
The directory structure of the subpplication jar could look like this:
|
---- classes
|
---- images
|
---- templates
|
---- MANIFEST.mf
The biggest challenge I see to make this work is how to uniquely
identify each application. I propose for a start that we add a appname after
the Webcontext info in the URL.
For example, If Turbine is configured as a context in your Webserver, then
for a subpplication named myapp the URL would look like this:
http://127.0.0.1/turbine/myapp
This would mean adding the app info to the scriptname in DynamicURI.
The loader via the assemblers would use this appname to locate the jar for the
app ( see loading classes above ).
Does anyone have any other ideas on how to uniquely id the apps?
--
Dave Bryson
daveb@miceda-data.com
----------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org