notify-dpml AT lists.ibiblio.org

Subject: DPML Notify

List archive

svn commit: r2546 - in development/central/site/src: docs/about/notepad docs/about/notepad/depot docs/about/notepad/freight resources/images/depot

From: mcconnell AT dpml.net
To: notify-dpml AT lists.ibiblio.org
Subject: svn commit: r2546 - in development/central/site/src: docs/about/notepad docs/about/notepad/depot docs/about/notepad/freight resources/images/depot
Date: Fri, 13 May 2005 19:29:34 +0000

Author: mcconnell AT dpml.net
Date: Fri May 13 19:29:32 2005
New Revision: 2546

Added:
development/central/site/src/docs/about/notepad/depot/
development/central/site/src/docs/about/notepad/depot/index.xml
development/central/site/src/docs/about/notepad/depot/navigation.xml
development/central/site/src/docs/about/notepad/depot/prefs.xml
development/central/site/src/docs/about/notepad/depot/station.xml
development/central/site/src/resources/images/depot/

development/central/site/src/resources/images/depot/add-content-handler.png
(contents, props changed)
development/central/site/src/resources/images/depot/content-dialog.png
(contents, props changed)
development/central/site/src/resources/images/depot/content-handler.png
(contents, props changed)

development/central/site/src/resources/images/depot/resource-host-dialog.png
(contents, props changed)

development/central/site/src/resources/images/depot/transit-cache-dialog.png
(contents, props changed)

development/central/site/src/resources/images/depot/transit-main-dialog.png
(contents, props changed)
Modified:
development/central/site/src/docs/about/notepad/freight/development.xml
development/central/site/src/docs/about/notepad/navigation.xml
Log:
addition of Depot work-in-progress notes

Added: development/central/site/src/docs/about/notepad/depot/index.xml
==============================================================================
--- (empty file)
+++ development/central/site/src/docs/about/notepad/depot/index.xml Fri
May 13 19:29:32 2005
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="mcconnell AT dpml.net">Stephen McConnell</author>
+ <title>DPML Central</title>
+ </properties>
+ <body>
+ <section name="Introducing Depot ...">
+
+ 
+ Depot is an application that provides support for (a) application
+ deployment services, and (b) preferences management for humans.
+ Depot requirements are focused on the management concerns related
+ to <a href="../freight/index.html">Metro FT</a>. Initially this
+ scope is closely related to Transit configuration via
+ <a href="prefs.html">Depot Preferences</a> but is
+ intended to grow to include remotely accessible preference
+ management and ultimately runtime management for FT based
+ applications via <a href="station.html">Depot Station</a>.
+ 
+
+ </section>
+
+ </body>
+
+</document>
+

Added: development/central/site/src/docs/about/notepad/depot/navigation.xml
==============================================================================
--- (empty file)
+++ development/central/site/src/docs/about/notepad/depot/navigation.xml
Fri May 13 19:29:32 2005
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+
+
+<project>
+
+ <title>DPML Central</title>
+
+ <body>
+ <menu>
+ <item name="Depot Preferences" href="prefs.html"/>
+ <item name="Depot Station" href="station.html"/>
+ </menu>
+ </body>
+
+</project>

Added: development/central/site/src/docs/about/notepad/depot/prefs.xml
==============================================================================
--- (empty file)
+++ development/central/site/src/docs/about/notepad/depot/prefs.xml Fri
May 13 19:29:32 2005
@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="mcconnell AT dpml.net">Stephen McConnell</author>
+ <title>DPML Central</title>
+ </properties>
+ <body>
+ <section name="Depot Preferences ...">
+
+ 
+ To launch the Depot Preferences application enter the following:
+ 
+
+<pre>$ depot</pre>
+
+ <subsection name="Cache and Host Preferences ...">
+
+ 
+ The main Transit panel contains a list of the transit hosts
+ and a button for cache settings.
+ 
+
+ <img src="/images/depot/transit-main-dialog.png"/>
+
+ 
+ Selecting a host and hitting the Edit button (or simply
+ double-clicking on the item) brings up a host dialog box.
+ 
+
+ <img src="/images/depot/resource-host-dialog.png"/>
+
+ 
+ Modification to base url and enabled status will be reflected in
+ running transit instances that are launched with prefs enabled
+ Group, repository layout and credentials settings are not
+ implemented yet (volunteers appreciated).
+ 
+
+ 
+ The cache button returns the following dialog:
+ 
+
+ <img src="/images/depot/transit-cache-dialog.png"/>
+
+ 
+ The change button will bring up a file selection dialog box.
+ Modifications to the cache directory value will effect all
+ running pref-enabled transit instances as such this can be
+ dangerous (running the $ depot -reset command will take you
+ back to factory defaults if you get into trouble).
+ 
+
+ </subsection>
+
+ <subsection name="Content Handler Preferences ...">
+
+ 
+ The content tab contains a controller button and the the list of
+ handlers. The content handler controller button allows you to
+ declare a custom content handler controller (which is optional). If
+ you declare a controller you are telling transit to use your plugin
+ for content management thereby overriding transit default content
+ management.
+ 
+
+ <img src="/images/depot/content-dialog.png"/>
+
+ 
+ You can add content handlers by clicking on the "Add" button.
+ You generally add a contrent handler if you want to access content
+ from a URL (e.g. URL.getContent() ) and you would like to declare
+ the application that will handle this request. The add button brings
+ up a dialog box requesting the name of the content type. A content
+ type name is the same a the type used in Transit artifact references
+ (e.g. "jar", "part", etc.). The following pic shows the creation of
+ a new handler for the "part" content type:
+ 
+
+ <img src="/images/depot/add-content-handler.png"/>
+
+ 
+ After clicking on OK you will presented with the content handler
+ dialog. I've filled in the dialog below to use the
dpml-composition-unit
+ plugin as the controller. In effect I'm telling Transit that when a
client
+ requests the content of an artifact of the type "part", I want
Transit to
+ delegate content resolution requests to the ContentHandler that is
+ established from my plugin. In this example I'm saying that I want
Metro
+ FT to handle all request for content related to the "part" type.
+ 
+
+ <img src="/images/depot/content-handler.png"/>
+
+ 
+ After hitting the "Install" button the "Controller Settings" button
+ will become enabled (if the selected plugin has an associated
control
+ panel). The current control panel for the above uri contains nothing
+ just at the moment - but this where you will be able to declare
default
+ setting form anonymous instances of Metro.
+ 
+
+ </subsection>
+
+ <subsection name="Logging Preferences ...">
+
+ 
+ The logging tab is currently empty and will be used for the default
+ logging configuration. The depot class launching all of this is
actually
+ handling the establishment of a LoggingManager so that we will be
able
+ to centralize logging behavior for all DPML applications.
+ 
+
+ </subsection>
+
+ <subsection name="Application Profiles ...">
+
+ 
+ The profiles tab is for the registration of application profiles.
The
+ aim here is to remove application launch concerns from the Transit
+ system which in turn will let us tighten the focus of Transit as a
+ resource and content management system.
+ 
+
+ 
+ Depot profiles are basically a description of an application - it's
+ main class, classloader entries, system property requirements, etc.
+ stored as user defined preferences. Depot establishes the initial
+ system classloader and populates this with the classpath prior to
+ instance creation. Internally the preferences Swing app is an
example
+ of a application launched by Depot with dependencies on a couple of
+ jar files (transit and depot-station).
+ 
+
+ </subsection>
+
+ </section>
+
+ </body>
+
+</document>
+

Added: development/central/site/src/docs/about/notepad/depot/station.xml
==============================================================================
--- (empty file)
+++ development/central/site/src/docs/about/notepad/depot/station.xml Fri
May 13 19:29:32 2005
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="mcconnell AT dpml.net">Stephen McConnell</author>
+ <title>DPML Central</title>
+ </properties>
+ <body>
+ <section name="Depot Station ...">
+
+ <subsection name="Objective ...">
+
+ 
+ The primary object of the Depot Station is to provide a
+ solution for local application deployment and an access
+ point for remote management and monitoring.
+ 
+
+ 
+ Not a lot of discussion has taken place on this yet, although
+ some ideas have been floated concerning JINI and JMX. There is
+ also the potential of bringing together application profiles and
+ the RMI Activation framework as a means of providing an elegant
+ application deployment solution.
+ 
+
+ </subsection>
+
+ <subsection name="Local Application Deployment">
+
+ 
+ The current Depot implementation provides some basic support
+ for the deployment of applications based on a application profile
+ name. Application profiles are maintained under user preferences
+ relative to the key /dpml/depot/lang/profiles/[name]. Each
+ profile declare a main class classname, an application title,
+ and two nested preference nodes - one for the classpath and
+ another for system property declarations.
+ 
+
+ 
+ The Depot CLI script assigns the DepotClassLoader as the system
+ classloader. The DepotClassLoader has an unusual feature of
+ providing support for the late-binding of application URLs. This
+ allows us to setup the initial system classloader during JVM setup
+ following which Depot populates the classloader based on application
+ profile settings. The current implementation is working in that
+ it is handling the setup of the Depot Preferences application,
however
+ it has not been tested on anything more rigorous and I'm expected
+ some more evolution to occur - in particular, classpath URL ordering
+ is significant when dealing with bootstrap resources (e.g. protocol
+ handlers).
+ 
+
+ 
+ Deploying an application using the Depot script is basically
+ the following:
+ 
+
+<pre>$ depot -profile [name] [your-application-args]</pre>
+
+ 
+ Where [name] is the name of a preferences node under the tree
+ /dpml/depot/lang/profiles/.
+ 
+
+ </subsection>
+
+
+ </section>
+
+ </body>
+
+</document>
+

Modified:
development/central/site/src/docs/about/notepad/freight/development.xml
==============================================================================
--- development/central/site/src/docs/about/notepad/freight/development.xml
(original)
+++ development/central/site/src/docs/about/notepad/freight/development.xml
Fri May 13 19:29:32 2005
@@ -153,7 +153,7 @@



- Build time constraints applied to during the Context evaluation
include:
+ Build time constraints applied during the Context evaluation include:


<ol>
@@ -368,7 +368,7 @@
[manager] get[key]ContextManager( [id] ); // return the context manager for
the identified instance
Map get[key]ContextMap( [id] ); // return the context map for the
identified instance
Component get[key]Component( [id] ) // return a model of an identified
Component instance
- Model get[key]Model() // return the Model of an
identified component type
+ Model get[key]Model( [id] ) // return the Model of an
identified component type
</pre>



Modified: development/central/site/src/docs/about/notepad/navigation.xml
==============================================================================
--- development/central/site/src/docs/about/notepad/navigation.xml
(original)
+++ development/central/site/src/docs/about/notepad/navigation.xml Fri
May 13 19:29:32 2005
@@ -26,6 +26,7 @@
<item name="MGR Desktop" href="mgr/index.html"/>
<item name="Registration and Discovery" href="discovery/index.html"/>
<item name="Freight Train" href="freight/index.html"/>
+ <item name="Depot Management" href="depot/index.html"/>
</menu>
</body>

Added:
development/central/site/src/resources/images/depot/add-content-handler.png
==============================================================================
Binary file. No diff available.

Added: development/central/site/src/resources/images/depot/content-dialog.png
==============================================================================
Binary file. No diff available.

Added: development/central/site/src/resources/images/depot/content-handler.png
==============================================================================
Binary file. No diff available.

Added:
development/central/site/src/resources/images/depot/resource-host-dialog.png
==============================================================================
Binary file. No diff available.

Added:
development/central/site/src/resources/images/depot/transit-cache-dialog.png
==============================================================================
Binary file. No diff available.

Added:
development/central/site/src/resources/images/depot/transit-main-dialog.png
==============================================================================
Binary file. No diff available.

svn commit: r2546 - in development/central/site/src: docs/about/notepad docs/about/notepad/depot docs/about/notepad/freight resources/images/depot, mcconnell, 05/13/2005