Skip to content

Conversation

@roguexz
Copy link

@roguexz roguexz commented Jan 15, 2026

The microprofile-config integration was missing the beans.xml marker file, which prevented the configuration from being loaded as an alternative bean in Quarkus applications. This file is required for CDI bean discovery.

Fixes #587

The microprofile-config integration was missing the beans.xml marker file,
which prevented the configuration from being loaded as an alternative bean
in Quarkus applications. This file is required for CDI bean discovery.

Fixes a2aproject#587
@gemini-code-assist
Copy link
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@roguexz roguexz changed the title Fix: Add missing META-INF/beans.xml to microprofile-config integration fix: add missing META-INF/beans.xml to microprofile-config integration Jan 15, 2026
@kabir
Copy link
Collaborator

kabir commented Jan 15, 2026

Thanks @roguexz - while an empty beans.xml is fine, to stay consistent with the other ones would you be able to add content similar to the other ones in the project? e.g:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="https://jakarta.ee/xml/ns/jakartaee"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee 
                           https://jakarta.ee/xml/ns/jakartaee/beans_4_0.xsd">
</beans>

As this is an SDK that can be run anywhere, we don't know how lenient the target environment will be :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Microprofile config integration is missing the beans.xml file

2 participants