Adding support for resource template

[pascalconfluent]

Motivation and Context

It allows to support resource template as the sdk already supports resources

How Has This Been Tested?

Wrote unit tests

Breaking Changes

I don't think so

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• [XI have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[pascalconfluent]

@tzolov any hope to have this PR reviewed? Let me know if I can do anything to help if needed :)

Thank you so much!

[chemicL]

Thank you for the PR. We are currently refactoring the internals a bit to address #9. The PR will probably have to adapt to the new mode of operation. I'll keep you updated.

[tzolov]

@pascalconfluent , thank your patience.
After the 0.8.x refactoring is complete, could you please rebase your PR on top of main and resolve the possible conflicts.

[pascalconfluent]

@tzolov Done! Let me know if I should change anything.

Thank you!

[tzolov]

Thanks you! Will review it over the weekend

[pascalconfluent]

@tzolov Any update on this PR?

[chemicL]

@pascalconfluent I noticed commented out tests - is this PR a work in progress or was that an accidental omission?

[noear]

This pr is much needed!

[tzolov]

Hi @pascalconfluent, thanks for addressing this.

I finally had time to investigate this issue, and it's more involving than expected.

Our current Resource handling supports both static and template URIs, but this isn't spec-compliant since the spec splits (unnecessarily IMO) these into separate entities (Resource and ResourceTemplate).

Your approach is correct, but due to breaking changes and new transport/server modes, I had to rework it in #576. Could you review it and add any missing bits or tests?

I'd like to make you co-author of #576 if you're agreeable.

[tzolov]

@pascalconfluent we've merged #576 (with you as co-author). It extends your PR with:

• Support for stateless servers
• Enhanced read-resource and auto-completion logic using resource-templates
• Extended runtime resource/resource-template management (list capabilities + replace-on-duplicate logic)

One difference: we're using Map<String, AsyncResourceTemplateSpecification> instead of Map<UriTemplate, AsyncResourceTemplateSpecification> for resourceTemplates, relying on existing McpUriTemplateManagerFactory/McpUriTemplateManager.

Any concerns with UriTemplate vs McpUriTemplateManager implementations? Feel free to open a follow-up PR if needed.

[tzolov]

Closing this PR as replaced by #576 .
Feel free to re-open if something is missing