You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Gyorgy Orban (JIRA)" <ji...@apache.org> on 2007/10/10 18:29:50 UTC
[jira] Created: (CXF-1099) if finalizeConfig in
org.apache.cxf.transport.http.HTTPConduit could be protected or public
if finalizeConfig in org.apache.cxf.transport.http.HTTPConduit could be protected or public
-------------------------------------------------------------------------------------------
Key: CXF-1099
URL: https://issues.apache.org/jira/browse/CXF-1099
Project: CXF
Issue Type: Improvement
Components: Transports
Affects Versions: 2.1
Environment: CXF 20071002 snapshot
Reporter: Gyorgy Orban
finalizeConfig is package private now. It is called from AbstractHTTPTransportFactory.getConduit() after HTTPConduit is initialized. We would like to extend AbstractHTTPTransportFactory and HTTPConduit. Since the initialization process of HTTPConduit involves the calling of finalizeConfig() we either need to put our extension in the same package as HTTPConduit or practically reimplement the whole HTTPConduit class. None of these are very elegant, so it would be really cool if we could do this in a decent way. Of course, if you think we shouldn't extend these classes at all, or extend in a different way, please let us know.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1099) if finalizeConfig in
org.apache.cxf.transport.http.HTTPConduit could be protected or public
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-1099:
-----------------------------
Fix Version/s: 2.0.3
> if finalizeConfig in org.apache.cxf.transport.http.HTTPConduit could be protected or public
> -------------------------------------------------------------------------------------------
>
> Key: CXF-1099
> URL: https://issues.apache.org/jira/browse/CXF-1099
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.1
> Environment: CXF 20071002 snapshot
> Reporter: Gyorgy Orban
> Assignee: Daniel Kulp
> Fix For: 2.0.3
>
>
> finalizeConfig is package private now. It is called from AbstractHTTPTransportFactory.getConduit() after HTTPConduit is initialized. We would like to extend AbstractHTTPTransportFactory and HTTPConduit. Since the initialization process of HTTPConduit involves the calling of finalizeConfig() we either need to put our extension in the same package as HTTPConduit or practically reimplement the whole HTTPConduit class. None of these are very elegant, so it would be really cool if we could do this in a decent way. Of course, if you think we shouldn't extend these classes at all, or extend in a different way, please let us know.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1099) if finalizeConfig in
org.apache.cxf.transport.http.HTTPConduit could be protected or public
Posted by "Gyorgy Orban (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533974 ]
Gyorgy Orban commented on CXF-1099:
-----------------------------------
Thanks, that's perfect.
> if finalizeConfig in org.apache.cxf.transport.http.HTTPConduit could be protected or public
> -------------------------------------------------------------------------------------------
>
> Key: CXF-1099
> URL: https://issues.apache.org/jira/browse/CXF-1099
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.1
> Environment: CXF 20071002 snapshot
> Reporter: Gyorgy Orban
> Assignee: Daniel Kulp
>
> finalizeConfig is package private now. It is called from AbstractHTTPTransportFactory.getConduit() after HTTPConduit is initialized. We would like to extend AbstractHTTPTransportFactory and HTTPConduit. Since the initialization process of HTTPConduit involves the calling of finalizeConfig() we either need to put our extension in the same package as HTTPConduit or practically reimplement the whole HTTPConduit class. None of these are very elegant, so it would be really cool if we could do this in a decent way. Of course, if you think we shouldn't extend these classes at all, or extend in a different way, please let us know.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1099) if finalizeConfig in
org.apache.cxf.transport.http.HTTPConduit could be protected or public
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-1099:
-----------------------------
Affects Version/s: (was: 2.1)
2.0.2
> if finalizeConfig in org.apache.cxf.transport.http.HTTPConduit could be protected or public
> -------------------------------------------------------------------------------------------
>
> Key: CXF-1099
> URL: https://issues.apache.org/jira/browse/CXF-1099
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.0.2
> Environment: CXF 20071002 snapshot
> Reporter: Gyorgy Orban
> Assignee: Daniel Kulp
> Fix For: 2.0.3
>
>
> finalizeConfig is package private now. It is called from AbstractHTTPTransportFactory.getConduit() after HTTPConduit is initialized. We would like to extend AbstractHTTPTransportFactory and HTTPConduit. Since the initialization process of HTTPConduit involves the calling of finalizeConfig() we either need to put our extension in the same package as HTTPConduit or practically reimplement the whole HTTPConduit class. None of these are very elegant, so it would be really cool if we could do this in a decent way. Of course, if you think we shouldn't extend these classes at all, or extend in a different way, please let us know.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1099) if finalizeConfig in
org.apache.cxf.transport.http.HTTPConduit could be protected or public
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-1099.
------------------------------
Resolution: Fixed
> if finalizeConfig in org.apache.cxf.transport.http.HTTPConduit could be protected or public
> -------------------------------------------------------------------------------------------
>
> Key: CXF-1099
> URL: https://issues.apache.org/jira/browse/CXF-1099
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.0.2
> Environment: CXF 20071002 snapshot
> Reporter: Gyorgy Orban
> Assignee: Daniel Kulp
> Fix For: 2.0.3
>
>
> finalizeConfig is package private now. It is called from AbstractHTTPTransportFactory.getConduit() after HTTPConduit is initialized. We would like to extend AbstractHTTPTransportFactory and HTTPConduit. Since the initialization process of HTTPConduit involves the calling of finalizeConfig() we either need to put our extension in the same package as HTTPConduit or practically reimplement the whole HTTPConduit class. None of these are very elegant, so it would be really cool if we could do this in a decent way. Of course, if you think we shouldn't extend these classes at all, or extend in a different way, please let us know.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1099) if finalizeConfig in
org.apache.cxf.transport.http.HTTPConduit could be protected or public
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-1099:
--------------------------------
Assignee: Daniel Kulp
I just changed the method to just "protected" so subclasses can have access to it. Is that enough or are other changes needed?
> if finalizeConfig in org.apache.cxf.transport.http.HTTPConduit could be protected or public
> -------------------------------------------------------------------------------------------
>
> Key: CXF-1099
> URL: https://issues.apache.org/jira/browse/CXF-1099
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.1
> Environment: CXF 20071002 snapshot
> Reporter: Gyorgy Orban
> Assignee: Daniel Kulp
>
> finalizeConfig is package private now. It is called from AbstractHTTPTransportFactory.getConduit() after HTTPConduit is initialized. We would like to extend AbstractHTTPTransportFactory and HTTPConduit. Since the initialization process of HTTPConduit involves the calling of finalizeConfig() we either need to put our extension in the same package as HTTPConduit or practically reimplement the whole HTTPConduit class. None of these are very elegant, so it would be really cool if we could do this in a decent way. Of course, if you think we shouldn't extend these classes at all, or extend in a different way, please let us know.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.