+
Skip to content

Wildcard mappers should be implicitly handled and value propagated #40997

Open
@mabartos

Description

@mabartos

Before reporting an issue

  • I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

dist/quarkus

Describe the bug

Our wildcard mappers are only handled when they are called. It means, the default values or .mapFrom() are not propagated to the .to() properties implicitly, only when the mapper is called.

It brings a problem for the datasources as these mappers need to be called even when these options are not specified in any config source. To be more specific, when we specify f.e. --db-kind-user-store=postgres, the JDBC URL is not automatically set for the named datasource user-store and there's a failure after that.

We need to find a way of how to automatically call all property mappers for the named datasource user-store. Even across option categories as we would need to also call PM for the transaction XA determination for the datasource.

I'll try to add a suggested approach on how to achieve this.

cc: @shawkins @vmuzikar

Version

999

Regression

  • The issue is a regression

Expected behavior

Wildcard property mappers values are propagated to the final property.

Actual behavior

Wildcard property mappers values are NOT propagated to the final property.

How to Reproduce?

Define additional datasource in persistence.xml file and try to set it up with our datasource options.

Anything else?

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载