You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alexis Midon (JIRA)" <ji...@apache.org> on 2008/04/22 20:53:21 UTC
[jira] Created: (ODE-272) Dynamic config for Axis2 external
services
Dynamic config for Axis2 external services
------------------------------------------
Key: ODE-272
URL: https://issues.apache.org/jira/browse/ODE-272
Project: ODE
Issue Type: New Feature
Components: Axis2 Integration
Affects Versions: 1.1.1
Reporter: Alexis Midon
Fix For: 1.1.1
What for?
One might want to apply specific settings on the external endpoints used by a process. For instance: http timeout, http redirections, or other security settings. ODE Services are not concerned at all.
This page is the place holder for material about this project.
How to?
It seems relevant to reuse Axis2 configuration mechanism for SOAP-bound services. No need to reinvent the wheel. However a home-made mechanism will be implemented for HTTP-bound services.
An Axis2 Service Config file[1] might be dropped in the deployment unit directory for each external service involved in the process.
The file name pattern will be "\{local-service-name\}.axis2".
File changes (creation,deletion,updates) will be polled regularly and applied to the EPR.
[1] http://ws.apache.org/axis2/1_0/axis2config.html#Service_Configuration
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-272) Dynamic config for Axis2 external
services
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou resolved ODE-272.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.1.1)
1.2
Assignee: Matthieu Riou
Applied a few days ago. Resolving.
> Dynamic config for Axis2 external services
> ------------------------------------------
>
> Key: ODE-272
> URL: https://issues.apache.org/jira/browse/ODE-272
> Project: ODE
> Issue Type: New Feature
> Components: Axis2 Integration
> Affects Versions: 1.1.1
> Reporter: Alexis Midon
> Assignee: Matthieu Riou
> Fix For: 1.2
>
> Attachments: ODE-272_1.dynamic_config_for_axis_epr.patch
>
>
> What for?
> One might want to apply specific settings on the external endpoints used by a process. For instance: http timeout, http redirections, or other security settings. ODE Services are not concerned at all.
> This page is the place holder for material about this project.
> How to?
> It seems relevant to reuse Axis2 configuration mechanism for SOAP-bound services. No need to reinvent the wheel. However a home-made mechanism will be implemented for HTTP-bound services.
> An Axis2 Service Config file[1] might be dropped in the deployment unit directory for each external service involved in the process.
> The file name pattern will be "{local-service-name}.axis2".
> File changes (creation,deletion,updates) will be polled regularly and applied to the EPR.
> [1] http://ws.apache.org/axis2/1_0/axis2config.html#Service_Configuration
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-272) Dynamic config for Axis2 external
services
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon updated ODE-272:
-----------------------------
Description:
What for?
One might want to apply specific settings on the external endpoints used by a process. For instance: http timeout, http redirections, or other security settings. ODE Services are not concerned at all.
This page is the place holder for material about this project.
How to?
It seems relevant to reuse Axis2 configuration mechanism for SOAP-bound services. No need to reinvent the wheel. However a home-made mechanism will be implemented for HTTP-bound services.
An Axis2 Service Config file[1] might be dropped in the deployment unit directory for each external service involved in the process.
The file name pattern will be "{local-service-name}.axis2".
File changes (creation,deletion,updates) will be polled regularly and applied to the EPR.
[1] http://ws.apache.org/axis2/1_0/axis2config.html#Service_Configuration
was:
What for?
One might want to apply specific settings on the external endpoints used by a process. For instance: http timeout, http redirections, or other security settings. ODE Services are not concerned at all.
This page is the place holder for material about this project.
How to?
It seems relevant to reuse Axis2 configuration mechanism for SOAP-bound services. No need to reinvent the wheel. However a home-made mechanism will be implemented for HTTP-bound services.
An Axis2 Service Config file[1] might be dropped in the deployment unit directory for each external service involved in the process.
The file name pattern will be "\{local-service-name\}.axis2".
File changes (creation,deletion,updates) will be polled regularly and applied to the EPR.
[1] http://ws.apache.org/axis2/1_0/axis2config.html#Service_Configuration
> Dynamic config for Axis2 external services
> ------------------------------------------
>
> Key: ODE-272
> URL: https://issues.apache.org/jira/browse/ODE-272
> Project: ODE
> Issue Type: New Feature
> Components: Axis2 Integration
> Affects Versions: 1.1.1
> Reporter: Alexis Midon
> Fix For: 1.1.1
>
>
> What for?
> One might want to apply specific settings on the external endpoints used by a process. For instance: http timeout, http redirections, or other security settings. ODE Services are not concerned at all.
> This page is the place holder for material about this project.
> How to?
> It seems relevant to reuse Axis2 configuration mechanism for SOAP-bound services. No need to reinvent the wheel. However a home-made mechanism will be implemented for HTTP-bound services.
> An Axis2 Service Config file[1] might be dropped in the deployment unit directory for each external service involved in the process.
> The file name pattern will be "{local-service-name}.axis2".
> File changes (creation,deletion,updates) will be polled regularly and applied to the EPR.
> [1] http://ws.apache.org/axis2/1_0/axis2config.html#Service_Configuration
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-272) Dynamic config for Axis2 external
services
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon updated ODE-272:
-----------------------------
Attachment: ODE-272_1.dynamic_config_for_axis_epr.patch
use "patch -p1" not "-p0"
> Dynamic config for Axis2 external services
> ------------------------------------------
>
> Key: ODE-272
> URL: https://issues.apache.org/jira/browse/ODE-272
> Project: ODE
> Issue Type: New Feature
> Components: Axis2 Integration
> Affects Versions: 1.1.1
> Reporter: Alexis Midon
> Fix For: 1.1.1
>
> Attachments: ODE-272_1.dynamic_config_for_axis_epr.patch
>
>
> What for?
> One might want to apply specific settings on the external endpoints used by a process. For instance: http timeout, http redirections, or other security settings. ODE Services are not concerned at all.
> This page is the place holder for material about this project.
> How to?
> It seems relevant to reuse Axis2 configuration mechanism for SOAP-bound services. No need to reinvent the wheel. However a home-made mechanism will be implemented for HTTP-bound services.
> An Axis2 Service Config file[1] might be dropped in the deployment unit directory for each external service involved in the process.
> The file name pattern will be "{local-service-name}.axis2".
> File changes (creation,deletion,updates) will be polled regularly and applied to the EPR.
> [1] http://ws.apache.org/axis2/1_0/axis2config.html#Service_Configuration
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.