You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by John-M Baker <jo...@db.com> on 2008/03/05 12:48:17 UTC
JIRA CXF-1456
Hello,
Is there a fix to http://issues.apache.org/jira/browse/CXF-1456 for CXF
2.0.4? Or should I ask, when is 2.0.5 going to be released?
Also, on the subject of SSL, this is far too much effort:
HTTPConduit http = (HTTPConduit)cxfClient.getConduit();
TLSClientParameters tlsParams = new TLSClientParameters();
tlsParams.setSecureSocketProtocol("SSL");
http.setTlsClientParameters(tlsParams);
Could CXF not automatically handle SSL in 2.0.5? A URL with https should
not cause CXF to require extra coding!
Thanks,
John Baker
--
Web SSO
IT Infrastructure
Deutsche Bank London
URL: http://websso.cto.gt.intranet.db.com
---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
Re: JIRA CXF-1456
Posted by John-M Baker <jo...@db.com>.
Excellent news. Do you have a timeline for 2.0.5?
John Baker
--
Web SSO
IT Infrastructure
Deutsche Bank London
URL: http://websso.cto.gt.intranet.db.com
Daniel Kulp <dk...@apache.org>
05/03/2008 14:24
Please respond to
cxf-user@incubator.apache.org
To
cxf-user@incubator.apache.org
cc
John-M Baker/ext/dbcom@DBEMEA
Subject
Re: JIRA CXF-1456
On Wednesday 05 March 2008, John-M Baker wrote:
> Is there a fix to http://issues.apache.org/jira/browse/CXF-1456 for
> CXF 2.0.4? Or should I ask, when is 2.0.5 going to be released?
I deployed new snapshots monday night of 2.0.5 that have this fixed. Not
100% positive on the release date yet. Hopefully soon.
> Also, on the subject of SSL, this is far too much effort:
>
> HTTPConduit http = (HTTPConduit)cxfClient.getConduit();
> TLSClientParameters tlsParams = new TLSClientParameters();
> tlsParams.setSecureSocketProtocol("SSL");
> http.setTlsClientParameters(tlsParams);
>
> Could CXF not automatically handle SSL in 2.0.5? A URL with https
> should not cause CXF to require extra coding!
I 100% agree. The snapshot fixes this as well which was what sparked
some of the contriversy.
--
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog
---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
Re: JIRA CXF-1456
Posted by John-M Baker <jo...@db.com>.
Sorry, you did qualify the release date question. I'll try to get 2.0.5
tested here within the next 24 hours.
John Baker
--
Web SSO
IT Infrastructure
Deutsche Bank London
URL: http://websso.cto.gt.intranet.db.com
Daniel Kulp <dk...@apache.org>
05/03/2008 14:24
To
cxf-user@incubator.apache.org
cc
John-M Baker/ext/dbcom@DBEMEA
Subject
Re: JIRA CXF-1456
On Wednesday 05 March 2008, John-M Baker wrote:
> Is there a fix to http://issues.apache.org/jira/browse/CXF-1456 for
> CXF 2.0.4? Or should I ask, when is 2.0.5 going to be released?
I deployed new snapshots monday night of 2.0.5 that have this fixed. Not
100% positive on the release date yet. Hopefully soon.
> Also, on the subject of SSL, this is far too much effort:
>
> HTTPConduit http = (HTTPConduit)cxfClient.getConduit();
> TLSClientParameters tlsParams = new TLSClientParameters();
> tlsParams.setSecureSocketProtocol("SSL");
> http.setTlsClientParameters(tlsParams);
>
> Could CXF not automatically handle SSL in 2.0.5? A URL with https
> should not cause CXF to require extra coding!
I 100% agree. The snapshot fixes this as well which was what sparked
some of the contriversy.
--
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog
---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
Re: JIRA CXF-1456
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday 05 March 2008, John-M Baker wrote:
> Is there a fix to http://issues.apache.org/jira/browse/CXF-1456 for
> CXF 2.0.4? Or should I ask, when is 2.0.5 going to be released?
I deployed new snapshots monday night of 2.0.5 that have this fixed. Not
100% positive on the release date yet. Hopefully soon.
> Also, on the subject of SSL, this is far too much effort:
>
> HTTPConduit http = (HTTPConduit)cxfClient.getConduit();
> TLSClientParameters tlsParams = new TLSClientParameters();
> tlsParams.setSecureSocketProtocol("SSL");
> http.setTlsClientParameters(tlsParams);
>
> Could CXF not automatically handle SSL in 2.0.5? A URL with https
> should not cause CXF to require extra coding!
I 100% agree. The snapshot fixes this as well which was what sparked
some of the contriversy.
--
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog