You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Karthick Sankarachary (JIRA)" <ji...@apache.org> on 2009/11/25 22:36:39 UTC
[jira] Created: (ODE-713) Configurable Process Deployment Folder
Configurable Process Deployment Folder
--------------------------------------
Key: ODE-713
URL: https://issues.apache.org/jira/browse/ODE-713
Project: ODE
Issue Type: Improvement
Components: Axis2 Integration, BPEL Runtime
Affects Versions: 1.3.3
Reporter: Karthick Sankarachary
Assignee: Karthick Sankarachary
Fix For: 1.3.4
By default, we assume that processes are deployed under the, you guessed it, "processes" folder of the working directory. The deployment poller and process store work with that assumption.
There are cases, though, where the folder where processes are deployed might change after the fact. For example, if the server were to be relocated to a different machine or if it's version were to be upgraded, then chances are that the path to the deployment folder will have to change. When that happens, the process store will fail to read pre-existing processes because the paths no longer match.
To address this limitation, we will allow users to configure the deployment folder through a configuration property called "ode-axis2.deploy.dir". If it is not set, then it will default to ${ode-axis2.deploy.dir}/processes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-713) Configurable Process Deployment Folder
Posted by "Karthick Sankarachary (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthick Sankarachary resolved ODE-713.
---------------------------------------
Resolution: Fixed
This has been resolved by revision 884284.
> Configurable Process Deployment Folder
> --------------------------------------
>
> Key: ODE-713
> URL: https://issues.apache.org/jira/browse/ODE-713
> Project: ODE
> Issue Type: Improvement
> Components: Axis2 Integration, BPEL Runtime
> Affects Versions: 1.3.3
> Reporter: Karthick Sankarachary
> Assignee: Karthick Sankarachary
> Fix For: 1.3.4
>
>
> By default, we assume that processes are deployed under the, you guessed it, "processes" folder of the working directory. The deployment poller and process store work with that assumption.
> There are cases, though, where the folder where processes are deployed might change after the fact. For example, if the server were to be relocated to a different machine or if it's version were to be upgraded, then chances are that the path to the deployment folder will have to change. When that happens, the process store will fail to read pre-existing processes because the paths no longer match.
> To address this limitation, we will allow users to configure the deployment folder through a configuration property called "ode-axis2.deploy.dir". If it is not set, then it will default to ${ode-axis2.deploy.dir}/processes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-713) Configurable Process Deployment Folder
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782652#action_12782652 ]
Hudson commented on ODE-713:
----------------------------
Integrated in ODE-1.x #21 (See [http://hudson.zones.apache.org/hudson/job/ODE-1.x/21/])
Configurable Process Deployment Folder
> Configurable Process Deployment Folder
> --------------------------------------
>
> Key: ODE-713
> URL: https://issues.apache.org/jira/browse/ODE-713
> Project: ODE
> Issue Type: Improvement
> Components: Axis2 Integration, BPEL Runtime
> Affects Versions: 1.3.3
> Reporter: Karthick Sankarachary
> Assignee: Karthick Sankarachary
> Fix For: 1.3.4
>
>
> By default, we assume that processes are deployed under the, you guessed it, "processes" folder of the working directory. The deployment poller and process store work with that assumption.
> There are cases, though, where the folder where processes are deployed might change after the fact. For example, if the server were to be relocated to a different machine or if it's version were to be upgraded, then chances are that the path to the deployment folder will have to change. When that happens, the process store will fail to read pre-existing processes because the paths no longer match.
> To address this limitation, we will allow users to configure the deployment folder through a configuration property called "ode-axis2.deploy.dir". If it is not set, then it will default to ${ode-axis2.deploy.dir}/processes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.