[GitHub] [cxf] dependabot[bot] closed pull request #1260: Bump cxf.hibernate.em.version from 6.1.7.Final to 6.2.2.Final
dependabot[bot] closed pull request #1260: Bump cxf.hibernate.em.version from 6.1.7.Final to 6.2.2.Final URL: https://github.com/apache/cxf/pull/1260 -- 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] dependabot[bot] commented on pull request #1260: Bump cxf.hibernate.em.version from 6.1.7.Final to 6.2.2.Final
dependabot[bot] commented on PR #1260: URL: https://github.com/apache/cxf/pull/1260#issuecomment-1553947204 Superseded by #1278. -- 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] dependabot[bot] opened a new pull request, #1278: Bump cxf.hibernate.em.version from 6.1.7.Final to 6.2.3.Final
dependabot[bot] opened a new pull request, #1278: URL: https://github.com/apache/cxf/pull/1278 Bumps `cxf.hibernate.em.version` from 6.1.7.Final to 6.2.3.Final. Updates `hibernate-core` from 6.1.7.Final to 6.2.3.Final Changelog Sourced from https://github.com/hibernate/hibernate-orm/blob/6.2.3/changelog.txt";>hibernate-core's changelog. Changes in 6.2.3.Final (May 18, 2023) https://hibernate.atlassian.net/projects/HHH/versions/32152";>https://hibernate.atlassian.net/projects/HHH/versions/32152 ** Bug * [HHH-16576] - Problem in query involving union on MySQL 5.7, MariaDB and Oracle * [HHH-16573] - Embeddable element collection with updateable = false leads to NullPointerException * [HHH-16555] - Join fetch query in combination with the inheritance pattern not working in hibernate 6 * [HHH-16551] - Schema management: discriminator column of type CHAR should always be of length 1 * [HHH-16549] - NullPointerException when calling LoadQueryInfluencers#isFetchProfileEnabled * [HHH-16545] - PersistenceUtilHelper.MetadataCache is not Thread-Safe * [HHH-16542] - Bad get/is handling with bytecode enhancement * [HHH-16541] - follow-on locking not always handled correctly * [HHH-16533] - Sybase cast, literal and truncation doesn't work with jConnect driver * [HHH-16517] - H6: Problems with flush when batch is ON (without https://github.com/DynamicUpdate";>@DynamicUpdate) * [HHH-16505] - Interpretation of "bare" left-join alias reference in HQL * [HHH-16496] - CLONE - Join fetching nested https://github.com/OneToMany";>@OneToMany collections causes result multiplication * [HHH-16491] - SQM could not correct resolve Generics Embeddable ids * [HHH-16483] - Recursive CTE using Criteria API will throw Already registered a copy: org.hibernate.query.sqm.tree.cte.SqmCteStatement error * [HHH-16472] - Treated left join with restriction on entity results in incorrect query * [HHH-16469] - Hibernate repeatedly issues identical SELECT queries to load an optional one-to-one association * [HHH-16453] - Loading an Entity with two eager collections, produces duplicates when one of the collection is a a bag * [HHH-16447] - Lazy load of collection fails after EntityManager.refresh * [HHH-16425] - Function type resolver doesn't work with anonymous tuple path sources * [HHH-16423] - LazyInitializationException when calling em.refresh() on entity with lazy and eager children * [HHH-16298] - Failure merging a referenced entity * [HHH-15726] - Disjunction with treat results in too restrictive query * [HHH-12981] - Join alias is miscalculated when two descendant entities have same attribute name ** Improvement * [HHH-16580] - Some typos in org.hibernate.query.sqm * [HHH-16546] - Reduce verbosity of logs in a few edge cases * [HHH-16538] - Remove BeanValidationIntegrator#BV_CHECK_CLASS * [HHH-15871] - Update EDB testing to version 15 * [HHH-15160] - Extend Postgis support to distance operators ** Task * [HHH-16631] - Avoid unnecessary INFO logging at bootstrap * [HHH-16630] - Refactor code to avoid frequent lookup of Service MutationExecutorService * [HHH-16625] - Expose enough state from MetadataImpl to allow cloning it Changes in 6.2.2.Final (April 28, 2023) https://hibernate.atlassian.net/projects/HHH/versions/32149";>https://hibernate.atlassian.net/projects/HHH/versions/32149 ** Bug * [HHH-16528] - Revert SybaseDialect NameQualifierSupport to CATALOG only ... (truncated) Commits https://github.com/hibernate/hibernate-orm/commit/73973d34532b9938480ed8fbc562377dd8cdd3c5";>73973d3 Post-steps for release : 6.2.3.Final https://github.com/hibernate/hibernate-orm/commit/5d74ff28051fa83fdb5493f7944b46eeddd2700c";>5d74ff2 Pre-steps for release : 6.2.3.Final https://github.com/hibernate/hibernate-orm/commit/d2939038be3488027ea4b7df9e0b29198dce43c7";>d293903 Add description to hibernate-platform.gradle https://github.com/hibernate/hibernate-orm/commit/9a255a1798a1dd2f93d32d892db6631f3be6b6a5";>9a255a1 HHH-16630 Refactor code to avoid frequent lookup of Service MutationExecutorS... https://github.com/hibernate/hibernate-orm/commit/af86f96f274608f912479c7d9f53c88d6a157649";>af86f96 HHH-16631 Avoid unnecessary INFO logging at bootstrap https://github.com/hibernate/hibernate-orm/commit/296756a6b725632f4f33e3a1c7c08f8eab8af930";>296756a HHH-16625 Introduce a compilation unit among tests to serve as reminder about... https://github.com/hibernate/hibernate-orm/commit/99e5a09b54f2a52af3bdaae7d501f4706ac8e12c";>99e5a09 HHH-16625 Introduce a compilation unit among tests to serve as reminder about... https://github.com/hibernate/hibernate-orm/commit/bca9b51aaa84da16dc9b3a4b567c824ca05a692b";>bca9b51 HHH-16625 Expose enough state from MetadataImpl to allow cloning it https://github.com/hibernate/hibernate-orm/commit/57c2c6e926eae615a16f8ee
[GitHub] [cxf] dependabot[bot] opened a new pull request, #1277: Bump cxf.hazelcast.version from 5.2.3 to 5.3.0
dependabot[bot] opened a new pull request, #1277: URL: https://github.com/apache/cxf/pull/1277 Bumps `cxf.hazelcast.version` from 5.2.3 to 5.3.0. Updates `hazelcast` from 5.2.3 to 5.3.0 Release notes Sourced from https://github.com/hazelcast/hazelcast/releases";>hazelcast's releases. v5.3.0-BETA-2 This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast Platform 5.3-BETA-2 release. The numbers in the square brackets refer to the issues and pull requests in Hazelcast's GitHub repository. New Features Connector for Kafka Connect source: Import data from an external system directly into a Hazelcast data pipeline without the need of a Kafka cluster. Partition-Aware SQL Client: Send the SQL commands only to the members having the relevant data, which reduces the network hops and improves the query performances. Connector for MongoDB: Set up read-through/write-through caching in MongoDB via this connector without writing any code. Breaking Changes Renamed the DataLinkFactory interface as DataConnection. https://redirect.github.com/hazelcast/hazelcast/issues/24224";>#24224 Changed the default cloud coordinator URL from coordinator.hazelcast.cloud to api.viridian.hazelcast.com. The default configuration now connects to https://viridian.hazelcast.com/sign-in?next=/%5BHazelcast";>https://viridian.hazelcast.com/sign-in?next=/[Hazelcast Viridian^] instead of Hazelcast Cloud. If you want to continue accessing your Hazelcast Cloud clusters, you need to set the hazelcast.client.cloud.url property to https://coordinator.hazelcast.cloud in your configuration. https://redirect.github.com/hazelcast/hazelcast/issues/23290";>#23290 Enhancements Cloud Hazelcast was sending requests to Kubernetes API when deploying an application with embedded Hazelcast and service-dns (DNS lookup mode) specified to a Kubernetes cluster. This was causing the requests to be unsuccessful and the application not to start. This mechanism has been improved by creating Kubernetes client only for the DNS lookup mode. https://redirect.github.com/hazelcast/hazelcast/issues/23883";>#23883 When advanced networking is enabled, the Kubernetes discovery plugin might have been discovering several endpoints (per each port) for each member's pod. The discovery plugin now matches only the private IP per endpoint, ignoring the port values. https://redirect.github.com/hazelcast/hazelcast/issues/23766";>#23766 Added support of link:https://aws.amazon.com/about-aws/whats-new/2022/10/amazon-machine-images-support-instance-metadata-service-version-2-default/#:~:text=Posted%20On%3A%20Oct%203%2C%202022,depth%20against%20unauthorized%20metadata%20access.%5BIMDSv2%5E%5D";>https://aws.amazon.com/about-aws/whats-new/2022/10/amazon-machine-images-support-instance-metadata-service-version-2-default/#:~:text=Posted%20On%3A%20Oct%203%2C%202022,depth%20against%20unauthorized%20metadata%20access.[IMDSv2^] for Hazelcast's AWS Discovery plugin. https://redirect.github.com/hazelcast/hazelcast/issues/23545";>#23545 Enhanced the handling of errors coming from the Kubernetes API: ** Not detecting the intent correctly whenever the cluster is shutdown, so the cluster was not restarted successfully. ** Extensive amount of Kubernetes API calls were being logged when Automatic State Management feature is enabled. https://redirect.github.com/hazelcast/hazelcast/issues/23538";>#23538 Added the support of discovering ECS and EC2 members on AWS. See [Deploying a Cluster on Amazon AWS]. https://redirect.github.com/hazelcast/hazelcast/pull/22411%5B#22411%5D(https://redirect.github.com/hazelcast/hazelcast/issues/22411)">hazelcast/hazelcast#22411 Enhanced the experience of using Hazelcast with persistence under Kubernetes by removing requirements for manual interventions. Previously, when there is a restart on such a cluster, the cluster states were needed to be changed manually. For some cases, this might have led to data loss. Now, the shutdown process is automated. See [Configuring Kubernetes] for details. https://redirect.github.com/hazelcast/hazelcast/issues/21844";>#21844 Storage Disk tier option of Tiered Storage is now disabled by default. https://redirect.github.com/hazelcast/hazelcast/issues/23747";>#23747 Distribution Added the Kafka connector to the distribution. https://redirect.github.com/hazelcast/hazelcast/issues/23312";>#23312 Shaded dependencies for Hazelcast Platform have been combined in a dedicated package (com.hazelcast.shaded). https://redirect.github.com/hazelcast/hazelcast/issues/23124";>#23124 Networking Added socket options for per-socket keep-alive configuration: keep-count, keep-idle-seconds, and keep-interval-seconds. You can set these options using either the advanced network configurations or Hazelcast system prope
Re: How to setup multiple JAXRS server endpoints
Hi Jean,
> Am I misinterpreting this statement? It sounds to me that it should work
> with 'queryConfigEnabled=true' instead of 'queryConfigEnabled=false'?
It could be a bit confusing but I will try to explain (please let me know
if it makes sense to you):
- when 'queryConfigEnabled=false', CXF will dynamically replace the URL in
SwaggerUI,
in this respect the value won't be taken from the query string but from
`url` property
of the SwaggerUI configuration
- when 'queryConfigEnabled=true', CXF will do nothing and just forward query
parameters to
SwaggerUI, hoping it will somehow take care of it (basically turns off the
URL replacement),
that needs custom SwaggerUI distribution
I hope it explains the behavior, please let me know if it is still misleading
(so we could
improve the documentation). Thank you.
Best Regards,
Andriy Redko
JPU> Hi andriy,
JPU> I started off with looking at this swagger but prior to that I updated
JPU> framework versions. I am now on:
JPU> - CXF v3.5.6
JPU> - Swagger-UI v4.14.0
JPU> I noticed things changed with respect to the Swagger2Feature and
JPU> SwaggerUiConfig due to https://issues.apache.org/jira/browse/CXF-8636.
JPU> When reading
JPU>
https://cwiki.apache.org/confluence/display/CXF20DOC/Swagger2Feature#Swagger2Feature-ConfiguringSwaggerUI(3.2.7+)
JPU> I
JPU> reconfigured the usage of the swagger features as:
JPU>
JPU> class="org.apache.cxf.jaxrs.swagger.ui.SwaggerUiConfig">
JPU>
JPU>
JPU>
JPU> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
JPU>
JPU>
JPU>
JPU> With this configuration:
JPU> * Retrieving the swagger.yaml specification works with the url:
JPU> http://l-p53-008:8082/idp/rest-services/swagger.yaml ('idp' is the war
JPU> rootpath and 'rest-services' is the CXF-servlet path)
JPU> * Loading the Swagger UI with the url:
JPU> http://l-p53-008:8082/idp/rest-services/api-docs?url=swagger.yaml FAILS ?
It
JPU> loads the petshop store yaml specification.
JPU> When I change above configuration to:
JPU>
JPU> class="org.apache.cxf.jaxrs.swagger.ui.SwaggerUiConfig">
JPU>
JPU>
JPU>
JPU> class="org.apache.cxf.jaxrs.swagger.Swagger2Feature">
JPU>
JPU>
JPU>
JPU> Then:
JPU> * Retrieving the swagger.yaml specification works with the url:
JPU> http://l-p53-008:8082/idp/rest-services/swagger.yaml ('idp' is the war
JPU> rootpath and 'rest-services' is the CXF-servlet path)
JPU> * Loading the Swagger UI with the url:
JPU> http://l-p53-008:8082/idp/rest-services/api-docs?url=swagger.yaml SUCCEEDS
?
JPU> It loads the swagger.yaml specification.
JPU> The confluence WIKI page above specifically mentions:
JPU> "Apache CXF prior to 3.4.6 / 3.5.1 passed Swagger UI configuration (url,
JPU> ...) as query parameters. Starting from Swagger UI 4.1.3, most of query
JPU> parameters are not accepted anymore (due to security concerns), and Apache
JPU> CXF employes different strategy and tries to replace the URL dynamically
JPU> (inside HTML) when serving Swagger UI's front web page. This behaviour
could
JPU> be turned on by setting queryConfigEnabled property of the SwaggerUiConfig
JPU> to true (the default value is false )."
JPU> Am I misinterpreting this statement? It sounds to me that it should work
JPU> with 'queryConfigEnabled=true' instead of 'queryConfigEnabled=false'?
JPU> -Original Message-
JPU> From: Jean Pierre URKENS
JPU> Sent: dinsdag 9 mei 2023 9:25
JPU> To: 'Andriy Redko'
JPU> Subject: RE: How to setup multiple JAXRS server endpoints
JPU> Hi Andriy,
JPU> Both servers have not only differences in 'authorization' but also in
JPU> exception handling regarding mapping and validation errors that's why I
JPU> can't use the same JAX-RS server bean for them. I'll have a look at
JPU> customizing the swagger feature and will come back on it but for now
getting
JPU> the server up-and-running is more important.
JPU> Regards,
JPU> J.P. Urkens
JPU> -Original Message-
JPU> From: Andriy Redko
JPU> Sent: maandag 8 mei 2023 23:15
JPU> To: Jean Pierre URKENS ; CXF Dev List
JPU>
JPU> Subject: Re: How to setup multiple JAXRS server endpoints
JPU> Hi Jean,
JPU> Indeed the way you would like to do that is somewhat tricky.
>> So I tried to keep the @Path declaration on the interface classes but
>> changed them to @Path(“”). That does seems to work except the swagger
>> stuff no longer correctly works.
JPU> This is one of the possible options but OpenAPI/Swagger gets confused for a
JPU> reason: the path is now implicit (not in the spec).
JPU> So how about this option:
JPU> - use only one JAX-RS server (address "/")
JPU> - host both resources but use @Path("accounts") and @Path("resources") on
JPU> them respectively
JPU> I see that for @Path("accounts") you need to apply the
JPU> "kmopA
