Re: [VOTE] Apache CXF 3.4.5 and 3.3.12

+1 Thanks! Andy On Wed, Sep 29, 2021 at 8:41 PM Jim Ma wrote: > +1 > > > On Thu, Sep 30, 2021 at 7:46 AM Freeman Fang > wrote: > > > +1 (binding) > > Thanks Dan! > > > > Freeman > > > > On Wed, Sep 29, 2021 at 5:00 PM Daniel Kulp wrote: > > > > > > > > This is a vote to release CXF 3.4.5 and

Re: [VOTE] Apache CXF 3.4.4 and 3.3.11

+1 Thanks! On Sat, Jun 5, 2021 at 4:51 AM Francesco Chicchiriccò wrote: > On 04/06/21 21:41, Daniel Kulp wrote: > > This is a vote to release CXF 3.4.4 and 3.3.11. We have fixed over 26 > issues and it’s been over 2 months since the last releases. > > > > > > Staging repositories: > > https://

Re: CXF-7996 Jakarta EE TCKs and compatibility

Hi Andriy, Do you have a test case that shows the problem with the empty string FormParam? It does look like it might double-decode unless we also add a check later in the method to avoid that case. Thanks for pointing this out. Andy On Sun, Apr 18, 2021 at 9:19 PM Andriy Redko wrote: > Hey

Re: CXF-7996 Jakarta EE TCKs and compatibility

> Do we want another job to build master? Only mention that as I see Andy's PR was merged there. I just backported it to 3.4.x-fixes so that it will show up in 3.4.4. Thanks, Andy On Fri, Apr 16, 2021 at 2:04 PM David Blevins wrote: > > On Apr 16, 2021, at 4:46 AM, Andriy Redko wrote: > > >

Re: @Encoded TCK issue

On Apr 13, 2021, at 9:10 AM, Andy McCright > wrote: > > > > Hi David, > > > > I had to do some digging - but yes, we addressed that issue in our Open > Liberty fork of CXF and I must not have contributed that fix back to the > main CXF fork (apologies for that). &

Re: @Encoded TCK issue

Hi David, I had to do some digging - but yes, we addressed that issue in our Open Liberty fork of CXF and I must not have contributed that fix back to the main CXF fork (apologies for that). Here are the changes I made in the OL fork: https://github.com/OpenLiberty/open-liberty/pull/2504 - basica

Re: [VOTE] Apache CXF 3.4.3 and 3.3.10

+1 Thanks! Andy On Mon, Mar 15, 2021 at 5:17 PM Alexey Markevich wrote: > +1 > > On 3/16/21, Freeman Fang wrote: > > +1 (binding) > > > > Thanks Dan! > > Freeman > > > > On Mon, Mar 15, 2021 at 4:59 PM Daniel Kulp wrote: > > > >> > >> This is a vote to release CXF 3.4.3 and 3.3.10. We have

Re: CXF 3.4.2 soon

Hi Andriy, Colm, The MicroProfile Rest Client 2.0 GA release is currently in staging. We are working through a new process now that MP is formally an Eclipse Working Group. Part of that process is a two-week staging period where steering committee members review and (hopefully) approve the stage

Re: [VOTE] Apache CXF 3.4.1 and 3.3.8

+1 Thanks! On Tue, Nov 3, 2020 at 4:00 PM Freeman Fang wrote: > +1(binding) > > Thanks Dan! > Freeman > > On Tue, Nov 3, 2020 at 4:30 PM Daniel Kulp wrote: > > > > > This is a vote to release CXF 3.3.8 and 3.4.1. We’ve fixed over 20 JIRA > > issues and it’s been over 2 months since the last s

Re: [VOTE] Apache CXF 3.4.0

+1 Thanks! On Mon, Aug 24, 2020 at 2:05 AM Oliver Wulff wrote: > +1 > Thanks Oli > > > > Von meinem Samsung Galaxy Smartphone gesendet. > > > > Ursprüngliche Nachricht > Von: Alessio Soldano > Datum: 22.08.20 18:27 (GMT+01:00) > An: dev@cxf.apache.org > Betreff: Re: [VOTE] Apa

Re: [VOTE] CXF 3.3.7 and 3.2.14

+1 - Thanks! On Tue, Jun 23, 2020 at 5:10 PM Jeff Genender wrote: > +1 > > Jeff > > > > On Jun 23, 2020, at 3:02 PM, Daniel Kulp wrote: > > > > This is a vote to release CXF 3.3.7 and 3.2.14. We’ve fixed over 20 > JIRA issues and it’s been over 2 months since the last set of releases. > > > >

Re: Releases soon?

+1 from me. Thanks Colm! On Thu, Jun 11, 2020 at 11:36 AM Jean-Baptiste Onofre wrote: > It sounds good. > > Regards > JB > > > Le 11 juin 2020 à 13:12, Colm O hEigeartaigh a > écrit : > > > > We should get 3.3.7 and 3.2.14 out soon. Is there anything else to go > into > > these releases? I pro

Re: [VOTE] CXF 3.3.6 and 3.2.13

+1 Thanks! On Wed, Mar 25, 2020 at 2:53 PM Jean-Baptiste Onofre wrote: > +1 (non binding) > > Regards > JB > > > Le 25 mars 2020 à 20:53, Alexey Markevich a écrit : > > > > +1 > > > > On 3/25/20, Freeman Fang wrote: > >> +1(binding) > >> > >> Thanks! > >> Freeman > >> > >> On Wed, Mar 25, 2020

Re: [VOTE] Apache CXF 3.3.5 and 3.2.12

+1 - Thanks! On Mon, Jan 13, 2020 at 7:11 AM Colm O hEigeartaigh wrote: > +1. > > Colm. > > On Mon, Jan 13, 2020 at 7:52 AM Francesco Chicchiriccò < > ilgro...@apache.org> > wrote: > > > On 10/01/20 23:29, Daniel Kulp wrote: > > > After a couple of hiccups due to LDAP downtime, I was finally abl

Re: Votes by end of week?

;> No objections from me for including them, if Andriy is happy with them. >> Otherwise we can leave them for 3.3.6. >> >> Colm. >> >> On Wed, Jan 8, 2020 at 5:19 PM Andy McCright >> wrote: >> >>> Andriy, Colm, >>> >>> I'

Re: Votes by end of week?

Andriy, Colm, I've three pull requests in progress that we could pull in - I'd like to get some more reviews on them, but otherwise I think they are ready to merge. That said, I'm fine with waiting until the next release too. The PRs in question are: https://github.com/apache/cxf/pull/619 - Addi

Re: [VOTE] Apache CXF 3.2.11

+1 Thanks! On Thu, Oct 24, 2019 at 10:34 AM Daniel Kulp wrote: > Colm pointed out to me that we also need a 3.2.11 release. Since that’s > also been 2 months and we fixed 11 JIRA’s, it makes sense. > > It’s been over 2 months since 3.3.3 was released. We fixed 20 JIRAS. > > Staging area: >

Re: [VOTE] Apache CXF 3.3.4

+1 Thanks! On Tue, Oct 22, 2019 at 8:32 AM Alexey Markevich wrote: > +1 > > On Monday, October 21, 2019, Daniel Kulp wrote: > > > It’s been over 2 months since 3.3.3 was released. We fixed 20 JIRAS. > > > > Staging area: > > https://repository.apache.org/content/repositories/orgapachecxf-114

Re: Flip master to 3.4, create 3.3.x-fixes

Hi Dan, No objections from me, but I have a question about the Jakarta dependencies. The Jakarta EE 8 release (due in September) is supposed to be binary compatible with Java EE 8 - i.e. the javax.* packages will still be javax.* (not jakarta.*). Is the plan for 3.4.X to support Jakarta EE 8 (ba

Re: [VOTE] CXF 3.2.10, CXF 3.3.3, and buildutils 3.4.3

+1 - Thanks! On Thu, Aug 8, 2019 at 12:21 PM Freeman Fang wrote: > +1 > > Thanks Dan! > － > Freeman(Yue) Fang > > Red Hat, Inc. > > > > > > > On Aug 8, 2019, at 1:10 PM, Daniel Kulp wrote: > > > > This is vote to release CXF 3.2.10 and CXF 3.3.3. 3.3.3 also required > the release

Re: Dropping JDK9 / JDK10 jobs from Jenkins

+1 Thanks! On Thu, May 23, 2019 at 8:13 AM Freeman Fang wrote: > +1 > Thanks! > － > Freeman(Yue) Fang > > Red Hat, Inc. > > > > > > > On May 22, 2019, at 9:48 PM, Andriy Redko wrote: > > > > Hey guys, > > > > I think we could drop CXF's JDK9 [0] and JDK10 [1] jobs from Jenkins > > s

Re: [VOTE] Apache CXF 3.2.9, CXF 3.3.2, and cxf-build-utils 3.4.2

+1. Thanks! On Fri, May 10, 2019 at 11:05 AM Romain Manni-Bucau wrote: > +1, will just note that ClassUnwrapper got a new method with no default - > not really trivial to impl - so implementations are broken. Don't think it > is a blocker because it is mainly an integrator API and not an user AP

Re: Full Path Template from UriInfo?

James Carman wrote: > log.info("matchedUris: {}", uriInfo.getMatchedURIs()); > > yields: > > matchedUris: [hello/Foo/1, hello] > > On Sat, May 4, 2019 at 10:19 AM Andy McCright > wrote: > > > > Hi James, > > > > I’m a

Re: Full Path Template from UriInfo?

Hi James, I’m away from my computer now, so I cannot say for sure, but I think UriInfo.getMatchedURIs() might get you the unresolved URI - assuming your filter is not annotated with @PreMatch. Can you give that a try? If it doesn’t work I’ll take a closer look on Monday. Thanks, Andy On Sat, M

Re: Question about Apache cxf client compatibility with jersey client

Hi Akshay, I think it _can_ work, but it is a little risky. I believe it works because Jersey's ClientConfig class is an implementation of java.ws.rs.core.Configurable. But in general, mixing implementations can lead to problems - generally in the classloading space. Do you need Jersey at all?

Re: JDK13 build on Jenkins

I should have a fix for the microprofile rest client failures shortly. Thanks! Andy On Wed, Mar 13, 2019 at 10:11 PM Freeman Fang wrote: > Thanks Andriy! > > The result isn’t bad, some failures are in OSGi, that’s kind of expected, > since Karaf 4.2.x not support JDK13 yet. > > Cheers > －－

Re: [VOTE] CXF 3.3.1

+1 Thanks! On Thu, Feb 28, 2019 at 2:39 PM Dennis Kieselhorst wrote: > +1 > > Thanks! > > Am 28. Februar 2019 19:56:36 MEZ schrieb Daniel Kulp : > >This is vote to release 3.3.1. This doesn’t fix a ton of issues (only > >12), but it does fix two relatively important regressions. > > > >Stagin

Re: 3.3.1 tomorrow?

+1 There is also a minor issue where a warning is issued if using MP Rest Client with CDI but without specifying any providers - pretty minor, but would be nice to get that fix out. The fix is part of commit: https://github.com/apache/cxf/commit/d70589ed28942692f86753590fa23712850b3854 Thanks!

Re: [VOTE] CXF 3.2.8

+1 - thanks! On Thu, Jan 24, 2019 at 3:41 PM Andrey Redko wrote: > +1, thanks! > > Best Regards, > Andriy Redko > > On Thu, Jan 24, 2019, 4:36 PM Daniel Kulp > > It’s been 3 months since 3.2.7 so we should do another release. We’ve > > fixed 18 JIRA issues > > > > Staging area: > > https:/

Re: [VOTE] CXF 3.3.0 and CXF XJC Utils 3.3.0

+1 - thanks! On Thu, Jan 24, 2019 at 3:42 PM Andrey Redko wrote: > +1, this is a big one, thanks! > > Best Regards, > Andriy Redko > > On Thu, Jan 24, 2019, 4:33 PM Daniel Kulp > > This is a vote to release Apache CXF 3.3.0 and the XJC Utils 3.3.0 it > > needs. The main new feature is sup

Re: 3.3.0 soon?

Thanks for the reminder Dennis - I just resolved it. On Wed, Jan 23, 2019 at 11:40 AM Dennis Kieselhorst wrote: > > > I was able to get the MP Rest Client 1.2 APIs and TCKs final release done > > on time, so 3.3.0 will support the final release instead of a release > > candidate! > > Great Andy,

Re: 3.3.0 soon?

+1 I was able to get the MP Rest Client 1.2 APIs and TCKs final release done on time, so 3.3.0 will support the final release instead of a release candidate! Thanks, Andy On Wed, Jan 23, 2019 at 9:07 AM jean-frederic clere wrote: > On 21/01/2019 14:06, Dennis Kieselhorst wrote: > > Hi, > > > >

Re: Builds failure

Hi Colm, Thanks for catching this. It looks like a bug in the spec API. The @ClientHeaderParam (singular) annotation has a target of TYPE,METHOD, but the @ClientHeaderParams (plural/repeatable) only has a target of TYPE. I can change this, but it will take a little while before it gets to the Mav

Re: GraphQL Project?

k gives is often more an issue (N+1 queries to cite one > obvious > RMB> common problem) than a solution even if tempting > > RMB> Le jeu. 3 janv. 2019 23:29, Andy McCright < > j.andrew.mccri...@gmail.com> a > RMB> écrit : > > >> Hi All, > > >&

GraphQL Project?

Hi All, I've been involved in an effort to create a MicroProfile GraphQL project that would provide a Java framework for building and deploying GraphQL apps. The API would look similar to JAX-RS (i.e. @Query annotations instead of @GET, etc.). We have a draft project proposal available here: htt

Re: CxfTypeSafeClientBuilderTest failing on JDK9+

Hi Dennis, I most likely introduced this with my fix for CXF-7922 - in that fix, I made some changes to internal JDK classes in ClientProxyImpl's invokeDefaultMethod method. The MP Rest Client (as well as the CXF proxy client) should be able to invoke default methods, and there doesn't seem to be

Re: 3.3.0 soon?

I'm working on an initial implementation of MicroProfile Rest Client 1.2 that I'd like to put in the 3.3.X stream. The spec probably won't be finalized until mid-January or later, but there is a 1.2 milestone (early access) release in Maven central that we could use in a 3.3.0 release. Does anybo

Re: [VOTE] CXF 3.2.7 and xic-utils 3.2.3

+1 Thanks! Andy On Wed, Oct 24, 2018 at 7:53 PM Jeff Genender wrote: > +1 > > Jeff > > > On Oct 24, 2018, at 1:35 PM, Daniel Kulp wrote: > > > > It’s been over two months since we last release a 3.2.x. Thus, it’s > time. We’ve fixed a bunch of bugs, fixed some performance regressions, > ad

Re: [VOTE] - Release Apache CXF 3.1.17

+1 Thanks! Andy On Mon, Oct 1, 2018 at 9:13 AM Alessio Soldano wrote: > +1 > Thanks! > > On Sun, Sep 30, 2018 at 2:33 PM Colm O hEigeartaigh > wrote: > > > This is a vote to release Apache CXF 3.1.17. > > > > Issues fixed: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje

Re: [VOTE] Apache CXF 3.2.6

+1 Thanks! Andy On Thu, Aug 9, 2018 at 3:23 AM Christian Schneider wrote: > +1 (binding) > > Christian > > Am Do., 9. Aug. 2018 um 01:15 Uhr schrieb Daniel Kulp : > > > This is a vote to release CXF 3.2.6. > > > > > > Staging repo: > > https://repository.apache.org/content/repositories/orgapac

Re: Change master to 3.3?

+1 For Java levels, I'd recommend that we skip Java 10 and plan for Java 11. Java 10 support ends in September, whereas Java 11 is a long term support release. http://www.oracle.com/technetwork/java/javase/eol-135779.html Thanks! Andy On Tue, Jun 26, 2018 at 9:49 AM Dennis Kieselhorst wrote: >

Re: [VOTE] CXF 3.2.5/3.1.16

+1 - Thanks! On Mon, Jun 18, 2018 at 6:36 PM Daniel Kulp wrote: > This is a vote to release CXF 3.2.5 and 3.1.16. The 3.2.5 staging area > also include releases of cxf-buildutils and cxf-xjc-utils as they were > needed for the release. > > > Staging repos: > 3.1.16: > https://repository.apache

Re: A few 'Feature' questions

Hi Mark, For #1 - I'll take a look - I've been meaning to ever since I saw the JIRA, but I've been swamped lately. My bad. For #2 - I'd like others to weigh in, but I do think that this is the intended behavior. IIUC, org.apache.cxf.feature.Feature existed before the JAX-RS spec and is used in

Re: [VOTE] CXF 2.3.4

+1. Thanks! On Thu, Mar 22, 2018 at 6:08 PM John D. Ament wrote: > +1 plus this fixes an issue for Romain. > > On Thu, Mar 22, 2018 at 5:18 PM Daniel Kulp wrote: > > > > > This is a vote to release CXF 3.2.4. We only fixed a few issues since > > 3.2.3, but it fixes a severe regression for Syn

Re: [VOTE] Apache CXF 3.2.3

+1 Thanks! Andy On Sat, Mar 17, 2018 at 10:02 AM François Papon < francois.pa...@openobject.fr> wrote: > +1 (non-binding) > > Thanks for the release ! > > François > > Le 17 mars 2018 00:54, Daniel Kulp a écrit : > > > > > > This is a vote to release CXF 3.2.3. We’ve fixed over 27 JIRA issue

Re: [VOTE] - Release Apache CXF 3.1.15

+1 Thanks! Andy On Thu, Mar 8, 2018 at 9:04 AM, Francesco Chicchiriccò wrote: > On 08/03/2018 15:19, Colm O hEigeartaigh wrote: > >> This is a vote to release Apache CXF 3.1.15. >> >> Issued fixed: https://issues.apache.org/jira >> /projects/CXF/versions/12342151 >> >> Artifacts: >> https://re

Web/wiki Access

Hi All, Can I get access to modify the cxf.apache.org website? Through a question on dwAnswers , I learned that a property listed on the page below is incorrect. It is a simple change to correct it - change "org.apache.cxf.jaxrs.servic

Re: Backport Microprofile Client to 3.1.x branch

Hi Roberto, I think it is a good idea. The main drawback is that the 3.1.X stream requires compatibility with Java 7. The MicroProfile spec and Rest Client specifically sets Java 8 as the minimum Java level - and the Rest Client specifically makes use of Java 8 syntax and APIs, like lambdas and

Re: [Dev] GSoC-2018 Project Ideas

Hi Isuranga, I've never done a GSoC project before, but I'd be interested in participating/mentoring. My expertise is more geared toward RESTful services like JAX-RS and the MicroProfile Rest Client. Would you be interested in a project in that area? Thanks, Andy On Tue, Feb 13, 2018 at 6:40

Re: Going offline soon

Hi Sergey, Sorry to see you go. You have definitely been a great mentor for me on this project, and I agree with the sentiments already shared - you will definitely be missed. Best of luck in your new role, and please keep in touch, Andy On Fri, Feb 9, 2018 at 8:47 AM, Sergey Beryozkin wrote:

Re: [VOTE] CXF 3.2.2

+1 On Fri, Feb 2, 2018 at 2:15 PM, Andrey Redko wrote: > +1! > > Andriy > > On Fri, Feb 2, 2018 at 1:57 PM, Daniel Kulp wrote: > > > This is a vote to release CXF 3.2.2. We’ve fixed over 60 JIRA issues, > > definitely time to release it. This also includes releases of > build-utils > > (3.4

Re: MP client test failing

Hi John, Sorry for the delay, but yes, that is an expected validation. Thanks for catching it! Andy On Fri, Dec 22, 2017 at 8:18 AM, John D. Ament wrote: > I pushed up a fix. Andy, whenever you get a chance can you take a look > and confirm this validation is expected as well? > > On 2017-12

Re: Default Priority for built in providers

ter the Json P provider. This would more easily allow > consuming frameworks to add their own providers of slightly higher > priorities. > > John > > On 2017-12-16 21:06, Andy McCright wrote: > > True - we would also need to add default priority to the user-specified > &

Re: Default Priority for built in providers

True - we would also need to add default priority to the user-specified providers (‘Priorities.USER’). On Sat, Dec 16, 2017 at 2:08 PM Romain Manni-Bucau wrote: > Le 16 déc. 2017 20:28, "Andy McCright" a > écrit : > > I don’t have the code in front of me, but I re

Re: Default Priority for built in providers

I don’t have the code in front of me, but I remember that for JAX-RS providers there was a check for a “user”/“custom” boolean - the built-in providers are false, user providers (regardless of priority) are true. That boolean is checked before the ‘@Priority’ annotation. With the new emphasis on u

Re: New Java 9 master

Hi Sergey, I'm in favor of the idea. One thing worth noting is that Java 9 is a very limited support release. According to Oracle's support strategy [1], Java 9 will only be supported until March 2018, then they will be releasing Java 10 (aka 18.3) which also will have a short shelf-life. The n

Re: JIRA Karma?

Hi Dan, Could you grant me the same authority? I think I'm in the same boat that John was - able to commit code changes, but unable to assign JIRAs. Thanks, Andy On Wed, Nov 8, 2017 at 9:39 PM, John D. Ament wrote: > I believe this is resolved. I neglected to respond, but I can confirm I >

Re: [DISCUSS] Status of 3.0.x...

+1 to keeping 3.2 on master until 3.2.1. I also agree with declaring end of support for 3.0.X (barring security vulnerabilities). Good discussion! Thanks! Andy On Wed, Sep 6, 2017 at 2:14 PM Andriy Redko wrote: > I think that keeping 3.2.x on master would make sense, at least till > 3.2.1.

Re: [VOTE] Apache CXF 3.2.0

+1 On Wed, Sep 6, 2017 at 2:06 PM Andriy Redko wrote: > +1! CXF rocks! > > Andriy > > DK> It’s been 2 years since the last major CXF release.We have well > over 100 JIRA’s of new features and > DK> enhancements that are only targeted toward 3.2. Let’s get it out! > > > DK> Staging repo: >

Re: Gitbox

+1 - agreed, low cost and it should make things a little easier. Thanks! On Mon, Jul 31, 2017 at 9:04 AM, Colm O hEigeartaigh wrote: > +1 - makes sense to me. > > Colm. > > On Mon, Jul 31, 2017 at 2:47 PM, Daniel Kulp wrote: > > > > > To move this forward….. > > > > > > From my reading/investi

Re: SSE module missing from CXF 3.2.X snapshot?

Thanks Andriy! On Wed, Jul 19, 2017 at 9:35 PM Andriy Redko wrote: > Hi Andy, > > That would be my fault, my apologies. I will take care of this issue > so SSE module would be included as part of the ZIP distribution. Thanks > for spotting it. > > Best Regards, > Andriy Redko > > AM> Hi All,

SSE module missing from CXF 3.2.X snapshot?

Hi All, I'm starting to play with some of the SSE stuff as part of JAX-RS 2.1, and I've noticed that the rt-rs-sse module is not in the CXF 3.2.X snapshot ZIPs available here: http://repository.apache.org/snapshots/org/apache/cxf/apache-cxf/3.2.0-SNAPSHOT/ I have been able to build the module loc

Re: Enable reflective use of HttpURLConnection by default?

be blocking the thread (at the sync HTTP > Conduit level) and using the internal pool, something like that... > > As far as enabling the reflective use of HttpUrlConnection by default: it > is probably a good idea indeed. > What will happen when CXF is run in a Java 9 VM though ? >

Enable reflective use of HttpURLConnection by default?

Hi All, With more and more people using different HTTP methods (verbs) with the JAX-RS client - particularly PATCH, but really any method they want - is there any objection to making the "use.httpurlconnection.method.reflection" true by default in CXF 3.2.X? Here is some background: Java SE's Htt

Re: [VOTE] Apache CXF 3.1.12 and 3.0.14

+1 Andy On Tue, Jun 27, 2017 at 3:09 PM Andrei Shakirin wrote: > +1 > > Andrei. > > > -Original Message- > > From: Daniel Kulp [mailto:dk...@apache.org] > > Sent: Dienstag, 27. Juni 2017 00:23 > > To: dev@cxf.apache.org > > Subject: [VOTE] Apache CXF 3.1.12 and 3.0.14 > > > > It’s been

Re: [VOTE] Apache CXF 3.1.11 and 3.0.13

+1 On Thu, Apr 6, 2017 at 7:06 AM Christian Schneider wrote: > +1 > > Christian > > On 06.04.2017 01:43, Daniel Kulp wrote: > > It’s been about 2 months since the last release. However, we’ve fixed > over 100 JIRA’s for 3.1.11 which is a large number of fixes. Thus, let’s > get it out. > > > >

Re: Becoming a committer?

017. >>>> >>>> Other than that - have a look please at other CXF JAX-RS or non JAX-RS >>>> issues whenever you get a chance, if you have some opinion on whatever >>>> issues the users are raising, consider contributing, etc. >>>> >>>&

Becoming a committer?

Hi All, I would like to become a committer on CXF. Hopefully over the past few months I've earned some karma with some of the performance and CTS-related fixes - and I'm hoping to contribute more - especially in the JAX-RS 2.1 space. If I'm not quite there as far as contributions, is there anyth

Re: Non-void return types for async methods

of candidates - we would link it to a JAX-RS 2.1 > issue where some extra justifications about the reason why such methods are > still candidates can be sought - please open this JAX-RS 2.1 issue too or I > can open it. > > Does this plan work for you ? > > Thanks, Sergey &g

Non-void return types for async methods

Hi All, When we moved to 3.1.7 a few months ago, we started seeing a test failure in one of our system tests. The tester had a JAX-RS resource with the following method signature: @GET @Produces(MediaType.APPLICATION_JSON) public JSONObject getMessage(@QueryParam("id") int i, @Suspended As

CXF-7070 mixed in with CXF-7075

Sergey, All, While waiting on the performance benchmark results for 7075, I thought I would take a look at 7070. I ended up committing changes to that under the same pull request that is still open for 7075 - different commit, but same PR. I'm still coming up to speed on Git, so there is probabl

Re: Introduction

X stream? Does 3.1.X require Java 8 (or higher)? Thanks, Andy On Wed, Aug 17, 2016 at 10:48 AM, Sergey Beryozkin wrote: > Hi Andy > > Welcome, thanks for the introductions, some comments below > On 17/08/16 15:56, Andy McCright wrote: > >> Hi All, >> >> I wan

Introduction

Hi All, I wanted to introduce myself. My name is Andy McCright and I'll be taking over Iris Deng's role as IBM's advocate for CXF and JAX-RS. I'm planning to join the JSR 370 expert group as well. My background has been mainly in WebSphere development. I've work