ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexis Midon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ODE-295) EPR configuration
Date Mon, 09 Jun 2008 13:41:45 GMT

    [ https://issues.apache.org/jira/browse/ODE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603565#action_12603565
] 

Alexis Midon commented on ODE-295:
----------------------------------

patch applied on trunk. I did it myself now that I can commit!

> EPR configuration
> -----------------
>
>                 Key: ODE-295
>                 URL: https://issues.apache.org/jira/browse/ODE-295
>             Project: ODE
>          Issue Type: New Feature
>          Components: BPEL Runtime
>            Reporter: Alexis Midon
>            Assignee: Matthieu Riou
>             Fix For: 1.2
>
>         Attachments: ODE-295_branch_patch#2.txt, ODE-295_patch#1.txt, ODE-295_trunk_patch#1.txt
>
>
> *Abstract:*
> Add support for external services configuration at runtime.
> Some settings (like timeout, proxy, headers etc) may have to be defined dynamically and
on a service-basis.
> This could be done with a property file (per deployment unit).
> *Details:*
> This issue adds a mechanism to pass properties from the ProcessConf to the Integration
Layer, and leverages it to configure external services.
> The ProcessConf interface has a method Map<String, String> getProperties(String...).
> This method is meant to expose properties to the Integration Layer. These properties
have to be specific to the process configuration. It's the implementor responsability to define
what these properties are, what they are used for. The String array received as argument may
be used to specify filters, criteria to get only a subset of the properties.
> Default Implementation
> The default implementation will use the first two parameters as service name and port
name.
> This method is backed by a property file named integration-layer.properties. This file
must be placed in the deployment unit.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message