You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2011/09/14 04:30:09 UTC
[jira] [Resolved] (CXF-402) Refresh target EPR after non-transient
failure detected by transport
[ https://issues.apache.org/jira/browse/CXF-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-402.
-----------------------------
Resolution: Won't Fix
Fix Version/s: Invalid
Assignee: (was: Eoghan Glynn)
This improvement request has been open for over a year and no-one has stepped up to implement it. As such, it does not seems to be a priority for the existing CXF community. If, in the future, someone would like to tackle this, feel free to open is and attach a patch.
> Refresh target EPR after non-transient failure detected by transport
> --------------------------------------------------------------------
>
> Key: CXF-402
> URL: https://issues.apache.org/jira/browse/CXF-402
> Project: CXF
> Issue Type: Task
> Components: Transports
> Reporter: Eoghan Glynn
> Fix For: Invalid
>
>
> When a Conduit detects a non-transient connection-establishment failure, it sould refresh the EPR via the EndpointResolverRegistry bus extension before attempting a transparent rebind.
> The number of rebind attempts and the intra-rebind delay should be configurable at the Bus level, as opposed to per-transport. Thus this logic should be factored out into a component sharable across transports (e.g. in the AbstractConduit).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira