[jira] Created: (CXF-3121) Upgrade Jetty version 6.1.26
Upgrade Jetty version 6.1.26 Key: CXF-3121 URL: https://issues.apache.org/jira/browse/CXF-3121 Project: CXF Issue Type: Task Reporter: Willem Jiang Assignee: Willem Jiang Priority: Minor Fix For: 2.2.12 Jetty 6.1.26 is out , we need to consider to upgrade it in CXF 2.2.x -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-3121) Upgrade Jetty version 6.1.26
[ https://issues.apache.org/jira/browse/CXF-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-3121. --- Resolution: Fixed > Upgrade Jetty version 6.1.26 > > > Key: CXF-3121 > URL: https://issues.apache.org/jira/browse/CXF-3121 > Project: CXF > Issue Type: Task >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.2.12 > > > Jetty 6.1.26 is out , we need to consider to upgrade it in CXF 2.2.x -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-3119) Jetty http integration does not work anymore
[
https://issues.apache.org/jira/browse/CXF-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931683#action_12931683
]
Stephane Nicoll commented on CXF-3119:
--
I surely would if I was able to quickly. We have built a cxf integration in our
product so I need to extract all the pieces in a test that does not rely on our
framework. It shouldn't be too complicated but I'll be out of the office next
week.
> Jetty http integration does not work anymore
>
>
> Key: CXF-3119
> URL: https://issues.apache.org/jira/browse/CXF-3119
> Project: CXF
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.3.0
> Environment: Spring 2.5.6
>Reporter: Stephane Nicoll
>Assignee: Willem Jiang
>
> A discussion on this topic can be found here:
> http://cxf.547215.n5.nabble.com/cxf-2-3-and-Jetty-7-td3228126.html#a3228126
> I still don't understand the real cause of my problem but at least I can see
> what change caused it.
> In 2.21 the JettyHTTPTransportFactory bean stored in
> cxf-extension-http-jetty.xml is as follows
> {code:xml}
> id="org.apache.cxf.transport.http_jetty.JettyHTTPTransportFactory"
> lazy-init="false"
>
> depends-on="org.apache.cxf.transport.http.ClientOnlyHTTPTransportFactory">
>
>
>
> http://schemas.xmlsoap.org/soap/http
> http://schemas.xmlsoap.org/wsdl/http/
> http://schemas.xmlsoap.org/wsdl/soap/http
> http://www.w3.org/2003/05/soap/bindings/HTTP/
>
> http://cxf.apache.org/transports/http/configuration
> http://cxf.apache.org/bindings/xformat
>
>
>
> {code}
> this is the 2.3.0 version
> {code:xml}
> id="org.apache.cxf.transport.http_jetty.JettyHTTPTransportFactory"
> lazy-init="true">
>
>
>
> http://cxf.apache.org/transports/http
>
> http://cxf.apache.org/transports/http/configuration
> http://schemas.xmlsoap.org/wsdl/http
> http://schemas.xmlsoap.org/wsdl/http/
>
>
>
> {code}
> Two things to notice:
> * Lazy init
> * Transport ids have changed
> Both seem to cause the issue. If I override the bean definition in a CXF 2.3
> env with the 2.2.11 version, my test passes. Flipping only the lazy init or
> the transport itd will not work.
> I don't know what caused this change so let me know so that I can give you
> more information about my environment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CXF-3119) Jetty http integration does not work anymore
[
https://issues.apache.org/jira/browse/CXF-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931683#action_12931683
]
Stephane Nicoll edited comment on CXF-3119 at 11/13/10 10:01 AM:
-
I surely would if I was able to quickly. We have built a cxf integration in our
product so I need to extract all the pieces in a test that does not rely on our
framework. It shouldn't be too complicated but I'll be out of the office next
week.
The interesting part is the rationale behind the change in the config file
since the 2.2.11 version works for me.
was (Author: snicoll):
I surely would if I was able to quickly. We have built a cxf integration in
our product so I need to extract all the pieces in a test that does not rely on
our framework. It shouldn't be too complicated but I'll be out of the office
next week.
> Jetty http integration does not work anymore
>
>
> Key: CXF-3119
> URL: https://issues.apache.org/jira/browse/CXF-3119
> Project: CXF
> Issue Type: Bug
> Components: Transports
>Affects Versions: 2.3.0
> Environment: Spring 2.5.6
>Reporter: Stephane Nicoll
>Assignee: Willem Jiang
>
> A discussion on this topic can be found here:
> http://cxf.547215.n5.nabble.com/cxf-2-3-and-Jetty-7-td3228126.html#a3228126
> I still don't understand the real cause of my problem but at least I can see
> what change caused it.
> In 2.21 the JettyHTTPTransportFactory bean stored in
> cxf-extension-http-jetty.xml is as follows
> {code:xml}
> id="org.apache.cxf.transport.http_jetty.JettyHTTPTransportFactory"
> lazy-init="false"
>
> depends-on="org.apache.cxf.transport.http.ClientOnlyHTTPTransportFactory">
>
>
>
> http://schemas.xmlsoap.org/soap/http
> http://schemas.xmlsoap.org/wsdl/http/
> http://schemas.xmlsoap.org/wsdl/soap/http
> http://www.w3.org/2003/05/soap/bindings/HTTP/
>
> http://cxf.apache.org/transports/http/configuration
> http://cxf.apache.org/bindings/xformat
>
>
>
> {code}
> this is the 2.3.0 version
> {code:xml}
> id="org.apache.cxf.transport.http_jetty.JettyHTTPTransportFactory"
> lazy-init="true">
>
>
>
> http://cxf.apache.org/transports/http
>
> http://cxf.apache.org/transports/http/configuration
> http://schemas.xmlsoap.org/wsdl/http
> http://schemas.xmlsoap.org/wsdl/http/
>
>
>
> {code}
> Two things to notice:
> * Lazy init
> * Transport ids have changed
> Both seem to cause the issue. If I override the bean definition in a CXF 2.3
> env with the 2.2.11 version, my test passes. Flipping only the lazy init or
> the transport itd will not work.
> I don't know what caused this change so let me know so that I can give you
> more information about my environment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
