avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@codehaus.org
Subject [jira] Created: (PNIX-48) Deploy via XML descriptors
Date Wed, 23 Apr 2003 07:38:09 GMT
Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=PNIX-48


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

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: phoenix
 Components: 
             Deployer
   Fix Fors:
             5.0
   Versions:
             4.1

   Assignee: 
   Reporter: Peter Donald

    Created: Wed, 23 Apr 2003 2:37 AM
    Updated: Wed, 23 Apr 2003 2:37 AM

Description:
It would be useful to have Phoenix 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 Phoenix 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/Administrators.jspa

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Mime
View raw message