Skip to content

Remove MCP startup warning if CDI is not enabled #33554

@Azquelt

Description

@Azquelt

Currently we warn if CDI is not enabled, since this will mean there can be no MCP tools registered.

However, our ServletContextListener fires for lots of internal web-apps as well (such as MP OpenAPI, OAuth, Admin center, pretty much any feature which exposes its own endpoints) and emits a warning for each one.

It could also be the case that several applications are deployed and some of them have MCP tools but some of them don't. In this case we wouldn't want to emit a warning for the ones that don't.

For these reasons, we should remove the CWMCM0017W warning.

Instead, if we don't enable the MCP endpoint for any reason, we should emit event level trace to say why. Include the name from getServletContextName() in the trace message.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions