Problem
Description
The MicroProfile module's MirrorNodeClientImpl has three NFT query methods that throw
RuntimeException("Not implemented"), leaving the MicroProfile client behind the Spring one:
queryNftsByAccount
queryNftsByAccountAndTokenId
queryNftsByTokenId
Additionally, MirrorNodeJsonConverterImpl#toNfts reads the wrong JSON key (transactions
instead of nfts) and throws when the nfts array is empty, causing failures even when a
valid response is returned from the Mirror Node REST API.
Steps to reproduce
- Use the MicroProfile module with a Helidon/Quarkus application.
- Call
NftRepository#findByType, findByOwner, or findByOwnerAndType.
- Observe
RuntimeException: Not implemented at runtime.
Expected behavior
The three methods hit the Mirror Node REST API:
GET /api/v1/accounts/{accountId}/nfts
GET /api/v1/tokens/{tokenId}/nfts
GET /api/v1/tokens/{tokenId}/nfts?account.id={accountId}
Results are parsed correctly, including base64-decoded NFT metadata and empty result sets.
Module
hiero-enterprise-microprofile
Additional context
The Spring module (hiero-enterprise-spring) already implements these correctly.
This is a parity gap between the two framework modules.
Solution
s
Alternatives
No response
Problem
Description
The MicroProfile module's
MirrorNodeClientImplhas three NFT query methods that throwRuntimeException("Not implemented"), leaving the MicroProfile client behind the Spring one:queryNftsByAccountqueryNftsByAccountAndTokenIdqueryNftsByTokenIdAdditionally,
MirrorNodeJsonConverterImpl#toNftsreads the wrong JSON key (transactionsinstead of
nfts) and throws when thenftsarray is empty, causing failures even when avalid response is returned from the Mirror Node REST API.
Steps to reproduce
NftRepository#findByType,findByOwner, orfindByOwnerAndType.RuntimeException: Not implementedat runtime.Expected behavior
The three methods hit the Mirror Node REST API:
GET /api/v1/accounts/{accountId}/nftsGET /api/v1/tokens/{tokenId}/nftsGET /api/v1/tokens/{tokenId}/nfts?account.id={accountId}Results are parsed correctly, including base64-decoded NFT metadata and empty result sets.
Module
hiero-enterprise-microprofileAdditional context
The Spring module (
hiero-enterprise-spring) already implements these correctly.This is a parity gap between the two framework modules.
Solution
s
Alternatives
No response