Fix Issue 39

[clauspruefer]

Pull Request

Description

Backend Method Processing logic is sub-optimal / needs refactoring.

Why

• No concrete service call data / backend method mapping exists currently
• Backend methods always must be called after the complete service data mapping (recursion has finished)
• Only one backend method should be definable

Related Issue

Fixes #39

Type of Change

• Refactor

[Copilot]

Pull request overview

This PR refactors backend method execution so that the backend method to be executed is defined in service call metadata rather than only in backend configuration, and ties backend methods to class definitions.

Changes:

• Add ClassMapper.get_class_properties() and refactor ServiceMapper to resolve and invoke a single SYSBackendMethod defined in service call metadata after mapping is complete.
• Remove legacy SYSBackendMethods configuration from PKI service properties and instead specify SYSBackendMethod per call in service_call_metadata.py.
• Minor cleanup in ClassHandler.set_json_dict to keep system keys out of generated JSON.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/microesb.py	Adds get_class_properties, refactors ServiceMapper.__init__ to drive backend method execution from call metadata, and adjusts JSON generation behavior.
example/02-pki-management/service_properties.py	Removes obsolete SYSBackendMethods list; keeps only property and method declarations on classes.
example/02-pki-management/service_call_metadata.py	Declares SYSBackendMethod in each service call item to select which backend method to run for each PKI-related service.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

@clauspruefer I've opened a new pull request, #42, to work on those changes. Once the pull request is ready, I'll request review from you.