[GitHub] [cxf] dependabot[bot] opened a new pull request, #1204: Bump dependency-check-maven from 8.2.0 to 8.2.1
dependabot[bot] opened a new pull request, #1204: URL: https://github.com/apache/cxf/pull/1204 Bumps [dependency-check-maven](https://github.com/jeremylong/DependencyCheck) from 8.2.0 to 8.2.1. Release notes Sourced from https://github.com/jeremylong/DependencyCheck/releases;>dependency-check-maven's releases. Version 8.2.1 Fixed NullPointerException in MSBuildAnalyzer (https://redirect.github.com/jeremylong/DependencyCheck/issues/5589;>#5589) SQL Syntax for Oracle (https://redirect.github.com/jeremylong/DependencyCheck/issues/5590;>#5590) Use https:// URLs in report templates (https://redirect.github.com/jeremylong/DependencyCheck/issues/5582;>#5582) See the full listing of https://github.com/jeremylong/DependencyCheck/milestone/64?closed=1;>changes. Changelog Sourced from https://github.com/jeremylong/DependencyCheck/blob/main/CHANGELOG.md;>dependency-check-maven's changelog. https://github.com/jeremylong/DependencyCheck/releases/tag/v8.2.1;>Version 8.2.1 (2023-03-23) Fixed NullPointerException in MSBuildAnalyzer (https://redirect.github.com/jeremylong/DependencyCheck/issues/5589;>#5589) SQL Syntax for Oracle (https://redirect.github.com/jeremylong/DependencyCheck/issues/5590;>#5590) Use https:// URLs in report templates (https://redirect.github.com/jeremylong/DependencyCheck/issues/5582;>#5582) See the full listing of https://github.com/jeremylong/DependencyCheck/milestone/64?closed=1;>changes. Commits https://github.com/jeremylong/DependencyCheck/commit/f82364a0f68a6798e0f1864b25f911c1f5ef9d69;>f82364a build: prepare release v8.2.1 https://github.com/jeremylong/DependencyCheck/commit/8d36f32d502e0ceb73fe47b48c993d13e15fa8fe;>8d36f32 docs: prepare release https://github.com/jeremylong/DependencyCheck/commit/3a2828466815bf22c93ea0aea2cfe8a99e1e0466;>3a28284 fix: NullPointerException in MSBuildAnalyzer (https://redirect.github.com/jeremylong/DependencyCheck/issues/5589;>#5589) https://github.com/jeremylong/DependencyCheck/commit/743ccf535a3a6faedd079593284f97f3c976203c;>743ccf5 fix: SQL Syntax for Oracle (https://redirect.github.com/jeremylong/DependencyCheck/issues/5590;>#5590) https://github.com/jeremylong/DependencyCheck/commit/32aa38f1e77e877bddc9a4d05e54c4567b3c0e1d;>32aa38f fix: Use https:// URLs in report templates (https://redirect.github.com/jeremylong/DependencyCheck/issues/5582;>#5582) https://github.com/jeremylong/DependencyCheck/commit/54de904178ce18e4d7bb14ad6aa797f604670c0f;>54de904 build(deps): bump commons-compress from 1.22 to 1.23.0 (https://redirect.github.com/jeremylong/DependencyCheck/issues/5584;>#5584) https://github.com/jeremylong/DependencyCheck/commit/9ca6da02496797e930653e236d48bb6aba79da5d;>9ca6da0 chore: Release 8.2.0 (https://redirect.github.com/jeremylong/DependencyCheck/issues/5576;>#5576) https://github.com/jeremylong/DependencyCheck/commit/ccc942917f86cedf7003a4a5be4eca95fab6be4f;>ccc9429 build: prepare for next development iteration See full diff in https://github.com/jeremylong/DependencyCheck/compare/v8.2.0...v8.2.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or
[GitHub] [cxf-xjc-utils] dependabot[bot] opened a new pull request, #51: Bump maven-core from 3.9.0 to 3.9.1
dependabot[bot] opened a new pull request, #51:
URL: https://github.com/apache/cxf-xjc-utils/pull/51
Bumps [maven-core](https://github.com/apache/maven) from 3.9.0 to 3.9.1.
Release notes
Sourced from https://github.com/apache/maven/releases;>maven-core's
releases.
3.9.1
https://maven.apache.org/docs/3.9.1/release-notes.html;>Release
Notes - Maven - Version 3.9.1
Overview About the Changes
Regression fixes from Maven 3.9.0. General performance and other
fixes.
Potentially Breaking Core Changes (if migrating from 3.8.x)
The Maven Resolver transport has changed from Wagon to “native HTTP”, see
https://maven.apache.org/guides/mini/guide-resolver-transport.html;>Resolver
Transport guide.
Maven 2.x was auto-injecting an ancient version of plexus-utils
dependency into the plugin classpath, and Maven 3.x continued doing this to
preserve backward compatibility. Starting with Maven 3.9, it does not happen
anymore. This change may lead to plugin breakage. The fix for affected plugin
maintainers is to explicitly declare a dependency on plexus-utils. The
workaround for affected plugin users is to add this dependency to plugin
dependencies until issue is fixed by the affected plugin maintainer. See https://issues.apache.org/jira/browse/MNG-6965;>MNG-6965.
Mojos are prevented to boostrap new instance of RepositorySystem (for
example by using deprecated ServiceLocator), they should reuse RepositorySystem
instance provided by Maven instead. See https://issues.apache.org/jira/browse/MNG-7471;>MNG-7471.
Each line in .mvn/maven.config is now interpreted as a single argument.
That is, if the file contains multiple arguments, these must now be placed on
separate lines, see https://issues.apache.org/jira/browse/MNG-7684;>MNG-7684.
Bug
[https://issues.apache.org/jira/browse/MNG-7213;>MNG-7213]
- StackOverflowError when version ranges are unsolvable and graph contains a
cycle
[https://issues.apache.org/jira/browse/MNG-7544;>MNG-7544]
- MavenMetadataSource#retrieve(MetadataResolutionRequest) does not check for
null when reading from project map
[https://issues.apache.org/jira/browse/MNG-7676;>MNG-7676]
- On Maven 3.9.0+ release, sha512 hashes have null classifier
[https://issues.apache.org/jira/browse/MNG-7677;>MNG-7677]
- Maven 3.9.0 is ~10% slower than 3.8.7 in large multi-module builds
[https://issues.apache.org/jira/browse/MNG-7679;>MNG-7679]
- [REGRESSION] Build fails when executing a single mojo without a POM
[https://issues.apache.org/jira/browse/MNG-7685;>MNG-7685]
- Unable to ignore certificate errors with v3.9.0
[https://issues.apache.org/jira/browse/MNG-7693;>MNG-7693]
- NPE in createModelCache, modelCacheFactory is null
[https://issues.apache.org/jira/browse/MNG-7697;>MNG-7697]
- Cannot parse POM that contains an emoji in a comment
[https://issues.apache.org/jira/browse/MNG-7708;>MNG-7708]
- Resolver in Maven 3.9+ no longer retries on a conection failure
[https://issues.apache.org/jira/browse/MNG-7709;>MNG-7709]
- plexus-utils upgrade changes the way configuration is parsed
[https://issues.apache.org/jira/browse/MNG-7710;>MNG-7710]
- Upgrade plexus-utils to 3.5.1
[https://issues.apache.org/jira/browse/MNG-7716;>MNG-7716]
- ConcurrencyDependencyGraph deadlock if no root can be selected
[https://issues.apache.org/jira/browse/MNG-7717;>MNG-7717]
- Maven warns wrongly about ${localRepository} expression
[https://issues.apache.org/jira/browse/MNG-7720;>MNG-7720]
- [REGRESSION] Build order is incorrect and does not respect Reactor Build
Order
[https://issues.apache.org/jira/browse/MNG-7721;>MNG-7721]
- Maven 3.9 resolver ignores proxy configured via MAVEN_OPTS
[https://issues.apache.org/jira/browse/MNG-7726;>MNG-7726]
- Maven 3.9.0 resolves properties in file profile activation incorrectly
[https://issues.apache.org/jira/browse/MNG-7731;>MNG-7731]
- MNG-7520 incorrectly back ported to Maven 3.9.0
Improvement
[https://issues.apache.org/jira/browse/MNG-5185;>MNG-5185]
- Improve missing dependency error message when
_maven.repositories/_remote.repositories contains other repository ids than
requested
[https://issues.apache.org/jira/browse/MNG-7686;>MNG-7686]
- Speed up by replacing non-pattern #replaceAll() with #replace() or
precompiled patterns
[https://issues.apache.org/jira/browse/MNG-7706;>MNG-7706]
- Deprecate ${localRepository} mojo parameter expression
Task
[https://issues.apache.org/jira/browse/MNG-7197;>MNG-7197]
- Simplify exit code handling in Windows command startup script
... (truncated)
Commits
https://github.com/apache/maven/commit/2e178502fcdbffc201671fb2537d0cb4b4cc58f8;>2e17850
[maven-release-plugin] prepare release maven-3.9.1
https://github.com/apache/maven/commit/79100c6b35d29f0b74951b7f7486f259d90f8e97;>79100c6
Update DOAP with Maven 3.8.8
[GitHub] [cxf] reta merged pull request #1202: CXF-8815: Fix org.apache.cxf.transport.http.asyncclient.hc5.AsyncHTTPConduitTest.testResponseSameBufferSize
reta merged PR #1202: URL: https://github.com/apache/cxf/pull/1202 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cxf] karlvr commented on pull request #1201: CXF-8671: Support Jakarta EE 10
karlvr commented on PR #1201: URL: https://github.com/apache/cxf/pull/1201#issuecomment-1481909144 Current test failures that I'm struggling with... I believe all of these failures are related to xml schemas with out a target namespace. It seems that we're not finding the complex type when there's no namespace, but we find it fine when there is. Is anyone able to help understand this? ``` [ERROR] Tests run: 41, Failures: 0, Errors: 12, Skipped: 0, Time elapsed: 3.612 s <<< FAILURE! - in org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest [ERROR] org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testNoTargetNamespace Time elapsed: 0.283 s <<< ERROR! java.lang.RuntimeException: Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' at org.apache.cxf.tools.wadlto.jaxrs.SourceGenerator$InnerErrorListener.error(SourceGenerator.java:2081) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:88) at jdk.proxy2/jdk.proxy2.$Proxy12.error(Unknown Source) at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.error(SchemaCompilerImpl.java:303) at com.sun.tools.xjc.util.ErrorReceiverFilter.error(ErrorReceiverFilter.java:55) at com.sun.xml.xsom.impl.parser.ParserContext$2.error(ParserContext.java:176) at com.sun.xml.xsom.impl.parser.ParserContext$1.reportError(ParserContext.java:154) at com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.reportError(NGCCRuntimeEx.java:149) at com.sun.xml.xsom.impl.parser.DelayedRef.resolve(DelayedRef.java:80) ... [ERROR] Errors: [ERROR] org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testCodeGenDigit [ERROR] Run 1: JAXRSContainerTest.testCodeGenDigit:843 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' [ERROR] Run 2: JAXRSContainerTest.testCodeGenDigit:843 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' [ERROR] Run 3: JAXRSContainerTest.testCodeGenDigit:843 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' [ERROR] Run 4: JAXRSContainerTest.testCodeGenDigit:843 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' [INFO] [ERROR] org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testCodeGenHyphen [ERROR] Run 1: JAXRSContainerTest.testCodeGenHyphen:821 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' [ERROR] Run 2: JAXRSContainerTest.testCodeGenHyphen:821 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' [ERROR] Run 3: JAXRSContainerTest.testCodeGenHyphen:821 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' [ERROR] Run 4: JAXRSContainerTest.testCodeGenHyphen:821 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' [INFO] [ERROR] org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testNoTargetNamespace [ERROR] Run 1: JAXRSContainerTest.testNoTargetNamespace:70 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' [ERROR] Run 2: JAXRSContainerTest.testNoTargetNamespace:70 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' [ERROR] Run 3: JAXRSContainerTest.testNoTargetNamespace:70 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' [ERROR] Run 4: JAXRSContainerTest.testNoTargetNamespace:70 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject' ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: Getting NPE from WebClient#rx with recent 4.0.1-SNAPSHOT artifacts
Hi Francesco, Thanks a lot for heads up, I saw a few commits from @Dan on March 17 [1] related to client side changed, those (potentially) could cause the regression. @Dan if you have time to take a look, would be great, otherwise I should be able to check it over the weekend. Thank you. [1] https://github.com/apache/cxf/commits/main Best Regards, Andriy Redko > Hi all, > since at least three days, the 4.0.1-SNAPSHOT artifacts are causing an NPE > around > https://github.com/apache/syncope/blob/master/common/keymaster/self/client-self/src/main/java/org/apache/syncope/common/keymaster/client/self/SelfKeymasterOps.java#L66 > with message > java.util.concurrent.CompletionException: jakarta.ws.rs.ProcessingException: > java.lang.NullPointerException: Cannot invoke > "org.apache.cxf.configuration.jsse.TLSClientParameters.getSslContext()" > because "clientParameters" is null > at > java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315) > ~[?:?] > at > java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320) > ~[?:?] > at > java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1770) > ~[?:?] > at > java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1760) > ~[?:?] > at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) > ~[?:?] > at > java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) > ~[?:?] > at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) > ~[?:?] > at > java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) ~[?:?] > at > java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165) > ~[?:?] > Caused by: jakarta.ws.rs.ProcessingException: java.lang.NullPointerException: > Cannot invoke > "org.apache.cxf.configuration.jsse.TLSClientParameters.getSslContext()" > because "clientParameters" is null > at > org.apache.cxf.jaxrs.client.AbstractClient.checkClientException(AbstractClient.java:638) > ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] > at > org.apache.cxf.jaxrs.client.AbstractClient.preProcessResult(AbstractClient.java:612) > ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] > at > org.apache.cxf.jaxrs.client.WebClient.doResponse(WebClient.java:1149) > ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] > at > org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1086) > ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] > at > org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:931) > ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] > at > org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:900) > ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] > at org.apache.cxf.jaxrs.client.WebClient.invoke(WebClient.java:460) > ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] > at > org.apache.cxf.jaxrs.client.SyncInvokerImpl.method(SyncInvokerImpl.java:150) > ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] > at > org.apache.cxf.jaxrs.client.CompletionStageRxInvokerImpl.lambda$method$0(CompletionStageRxInvokerImpl.java:147) > ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] > at > java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768) > ~[?:?] > As said, the same code was working fine until 3 days ago. > I suppose this is the consequence of recent commits to CXF master: do we need > to update something on Syncope side or this is something to fix in CXF? > TIA > Regards.
[GitHub] [cxf] karlvr commented on pull request #1201: CXF-8671: Support Jakarta EE 10
karlvr commented on PR #1201: URL: https://github.com/apache/cxf/pull/1201#issuecomment-1481825543 The `org.apache.cxf.jaxrs.impl.RetryAfterHeaderProviderTest` test failure I referenced above was because the test did not correctly account for daylight time. I've pushed a fix for that _test_, which would have broken in the main branch. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cxf] karlvr commented on pull request #1201: CXF-8671: Support Jakarta EE 10
karlvr commented on PR #1201: URL: https://github.com/apache/cxf/pull/1201#issuecomment-1481801926 @amarkevich thank you, that particular problem was resolved in dd20aee697eb61541351a9eb70f08a7984103363. This PR still won't compile due to the `RuntimeDelegateImpl` and `ResponseImplTest` pieces not being done yet. Locally I've implemented with TODOs :-) WIP. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
退订
Getting NPE from WebClient#rx with recent 4.0.1-SNAPSHOT artifacts
Hi all, since at least three days, the 4.0.1-SNAPSHOT artifacts are causing an NPE around https://github.com/apache/syncope/blob/master/common/keymaster/self/client-self/src/main/java/org/apache/syncope/common/keymaster/client/self/SelfKeymasterOps.java#L66 with message java.util.concurrent.CompletionException: jakarta.ws.rs.ProcessingException: java.lang.NullPointerException: Cannot invoke "org.apache.cxf.configuration.jsse.TLSClientParameters.getSslContext()" because "clientParameters" is null at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315) ~[?:?] at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320) ~[?:?] at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1770) ~[?:?] at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1760) ~[?:?] at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) ~[?:?] at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) ~[?:?] at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) ~[?:?] at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) ~[?:?] at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165) ~[?:?] Caused by: jakarta.ws.rs.ProcessingException: java.lang.NullPointerException: Cannot invoke "org.apache.cxf.configuration.jsse.TLSClientParameters.getSslContext()" because "clientParameters" is null at org.apache.cxf.jaxrs.client.AbstractClient.checkClientException(AbstractClient.java:638) ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] at org.apache.cxf.jaxrs.client.AbstractClient.preProcessResult(AbstractClient.java:612) ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] at org.apache.cxf.jaxrs.client.WebClient.doResponse(WebClient.java:1149) ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] at org.apache.cxf.jaxrs.client.WebClient.doChainedInvocation(WebClient.java:1086) ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:931) ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] at org.apache.cxf.jaxrs.client.WebClient.doInvoke(WebClient.java:900) ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] at org.apache.cxf.jaxrs.client.WebClient.invoke(WebClient.java:460) ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] at org.apache.cxf.jaxrs.client.SyncInvokerImpl.method(SyncInvokerImpl.java:150) ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] at org.apache.cxf.jaxrs.client.CompletionStageRxInvokerImpl.lambda$method$0(CompletionStageRxInvokerImpl.java:147) ~[cxf-rt-rs-client-4.0.1-SNAPSHOT.jar:4.0.1.SNAPSHOT] at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768) ~[?:?] As said, the same code was working fine until 3 days ago. I suppose this is the consequence of recent commits to CXF master: do we need to update something on Syncope side or this is something to fix in CXF? TIA Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[GitHub] [cxf] reta merged pull request #1203: Bump dependency-check-maven from 8.1.2 to 8.2.0
reta merged PR #1203: URL: https://github.com/apache/cxf/pull/1203 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cxf-xjc-utils] reta merged pull request #50: Bump maven-compat from 3.9.0 to 3.9.1
reta merged PR #50: URL: https://github.com/apache/cxf-xjc-utils/pull/50 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cxf.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
