[jira] Updated: (LOOM-28) Deploy via XML descriptors

The following issue has been updated:

    Updater: peter royal (mailto:[email protected])
       Date: Wed, 14 Apr 2004 8:47 PM
    Changes:
             Fix Version changed to future
             Fix Version changed from 1.1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=LOOM-28&page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=LOOM-28

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: LOOM-28
    Summary: Deploy via XML descriptors
       Type: New Feature

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: loom
   Fix Fors:
             future

   Assignee: 
   Reporter: Mauro Talevi

    Created: Wed, 30 Jul 2003 5:02 AM
    Updated: Wed, 14 Apr 2004 8:47 PM

Description:
t would be useful to have Loom scan the apps directory and deploy applications from xml descriptors as well as the .sar files. The xml descriptor could specify all the required parameters for an application rather than having Loom deduce them from the .sar file.

For example it could look something like

<application name="foo" protected="true">
  <homeDirectory>/some/dir</homeDirectory>
  <workDirectory>/tmp</workDirectory>
  <assembly>/opt/myapp/assembly.xml</assembly>
  <config>/opt/myapp/config.xml</config>
  <environment>/opt/myapp/environment.xml</environment>

  <resources>
    <!-- map some container resources into
         blocks context -->
    <resource key="keyUsedByBlocks"
              name="nameInKernel"
              type="javax.jmx.MBeanServer"/>
  <resources>

  <!-- see excalibur-loader project for format of this -->
  <classpath ... />
</application>

The deployer would then handle either xml files or .sar files.

The advantage of this would be that it makes it easy to allow alternative deployment formats which is useful when you are developing an IDE and don't want to rebuild sar in each development cycle. It is also useful when integrating with existing systems that have particular filesystem requirements.


For an example system that implements something like this have a look at the Tomcat 4.1 product



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira