Re: [VOTE] Apache CXF 2.3.11/2.4.8/2.5.4/2.6.1
Forgot my +1 Dan On Wednesday, May 30, 2012 02:15:51 PM Daniel Kulp wrote: We've resolved over 90 issues since 2.6.0 was released. We've back ported over 70 of them to 2.5.4 and 40 to 2.4.8 and 25 to 2.3.11. List of issues: 2.3.11: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511; version=12320749 2.4.8: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511; version=12320748 2.5.4: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511; version=12320747 2.6.1: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310511; version=12320746 The Maven staging areas are at: 2.3.12: https://repository.apache.org/content/repositories/orgapachecxf-149/ 2.4.8: https://repository.apache.org/content/repositories/orgapachecxf-159/ 2.5.4: https://repository.apache.org/content/repositories/orgapachecxf-160/ 2.6.1: https://repository.apache.org/content/repositories/orgapachecxf-161/ The distributions are in the org/apache/cxf/apache-cxf/ directory of the Maven staging areas. This releases are tagged at: http://svn.apache.org/repos/asf/cxf/tags/cxf-2.3.11 http://svn.apache.org/repos/asf/cxf/tags/cxf-2.4.8 http://svn.apache.org/repos/asf/cxf/tags/cxf-2.5.4 http://svn.apache.org/repos/asf/cxf/tags/cxf-2.6.1 This vote will be open for at least 72 hours. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
Re: Discussion about using JMS transport with CXFRS
Hi Sergey, I'm trying to create a WebClient instance by setting the address with jms uri to configure the endpoint jms address. But now I have trouble to setup the message context of REQUEST_URI in WebClient as this uri is not jms uri which I used to create the WebClient. How can I set REQUEST_URI without affect the ENDPOINT_ADDRESS by using WebClient API ? If not, I'm going to update the WebClient API for it. On Tue May 29 22:40:34 2012, Willem Jiang wrote: On Tue May 29 22:33:59 2012, Sergey Beryozkin wrote: Hi Willem On 29/05/12 14:53, Willem Jiang wrote: Hi, I just have a chance to go through the missing feature of JMS transport to support cxfrs frontend. Current JMS transport doesn't send out Message.REQUEST_URI and Message.HTTP_REQUEST_METHOD properties as the HTTP transport does. So it hard for use the use the cxfrs frontend with JMS transport. My question is do we need to transfer other properties which could be used by cxfrs frondend? The above properties are defaulted to / and POST respectively but can be customized via JMS properties Thanks, I will try to write some test tomorrow. And The AbstractClient is tend to use HttpConnection to get the headers for build the response, it stops the user to leverage other transports. We may need to update this part of code. +1. I did few changes to address https://issues.apache.org/jira/browse/CXF-3562, but I will prioritize on it after 2.6.1 is out. It is also needed for the future async support, alternative HTTP stacks support, etc, so it's time to start addressing it sounds good. Cheers, Sergey Any thoughts? -- Willem -- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Web: http://www.fusesource.com Blog: http://willemjiang.blogspot.com (English) http://jnn.javaeye.com (Chinese) Twitter: willemjiang Weibo: willemjiang -- Willem -- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Web: http://www.fusesource.com Blog:http://willemjiang.blogspot.com (English) http://jnn.javaeye.com (Chinese) Twitter: willemjiang Weibo: willemjiang
RE: Fediz release
Colm, do you have something similar in mind as for the STS: example: throw new FedizRuntimeException(Error in validating token, ex, FedizRuntimeException.TOKEN_EXPIRED); Thanks Oli -- Oliver Wulff Blog: http://owulff.blogspot.com Solution Architect http://coders.talend.com Talend Application Integration Division http://www.talend.com From: Oliver Wulff [owu...@talend.com] Sent: 04 June 2012 00:01 To: dev@cxf.apache.org; cohei...@apache.org Subject: RE: Fediz release I agree with you colm. I've improved unit testing where test saml tokens are generated as part of unit testing instead of using an rstr (with signed saml token) in a resource file. Any concrete ideas on exception handling? Thanks Oli -- Oliver Wulff Blog: http://owulff.blogspot.com Solution Architect http://coders.talend.com Talend Application Integration Division http://www.talend.com From: Colm O hEigeartaigh [cohei...@apache.org] Sent: 01 June 2012 10:32 To: dev@cxf.apache.org Subject: Re: Fediz release Hi Oli, It's almost there from my POV. I'd like to see better exception handling and (especially) better unit testing of the core plugin before the release goes out. Colm. On Thu, May 31, 2012 at 10:34 PM, Oliver Wulff owu...@talend.com wrote: Hi guys I'd like to get the first release out of Fediz within the next two weeks. There are a few features missing which should get in next week like: - Custom token support - Publish WS-Federation Metadata document What else has to be completed before we can release it? One question from my side. The distribution package can be downloaded here: https://repository.apache.org/content/groups/snapshots/org/apache/cxf/fediz/apache-fediz/1.0.0-SNAPSHOT/ The CXF download page has got the following download links: http://www.apache.org/dyn/closer.cgi?path=/cxf/2.6.0/apache-cxf-2.6.0.zip I assume that the Fediz archives should also be published similar to CXF. How can I get the archives there? Is this an automated process? Thanks Oli -- Oliver Wulff Blog: http://owulff.blogspot.comhttp://owulff.blogspot.com/ Solution Architect http://coders.talend.com http://coders.talend.comTalend Application Integration Division http://www.talend.com -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
