You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Eoghan Glynn (JIRA)" <ji...@apache.org> on 2007/02/01 15:53:06 UTC
[jira] Created: (CXF-401) Resolve EPRs prior to binding
Resolve EPRs prior to binding
-----------------------------
Key: CXF-401
URL: https://issues.apache.org/jira/browse/CXF-401
Project: CXF
Issue Type: Task
Components: Transports
Reporter: Eoghan Glynn
Assigned To: Eoghan Glynn
In any context in which EPR are being bound, e.g. in a transport Conduit implementation, the potentially abstract EPR should be resolved via the EndpointResolverRegistry Bus extension.
Depends on issude CXF-400 "Pluggable mechanism for resolution/lookup/mapping of EPRs" [https://issues.apache.org/jira/browse/CXF-400]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-401) Resolve EPRs prior to binding
Posted by "Eoghan Glynn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eoghan Glynn resolved CXF-401.
------------------------------
Resolution: Fixed
Commited in revision 516455 on March 9th 2007.
> Resolve EPRs prior to binding
> -----------------------------
>
> Key: CXF-401
> URL: https://issues.apache.org/jira/browse/CXF-401
> Project: CXF
> Issue Type: Task
> Components: Transports
> Reporter: Eoghan Glynn
> Assigned To: Eoghan Glynn
>
> In any context in which EPR are being bound, e.g. in a transport Conduit implementation, the potentially abstract EPR should be resolved via the EndpointResolverRegistry Bus extension.
> Depends on issude CXF-400 "Pluggable mechanism for resolution/lookup/mapping of EPRs" [https://issues.apache.org/jira/browse/CXF-400]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.