Skip to content

Making SEMP usage optional #73

@ppawel

Description

@ppawel

In our environment, where many clients use a central broker instance, it is problematic to enable the SEMP functions for everyone. The requirement of SEMP enabled makes it quite hard to use the solace-apache-beam connector even though we would very much like to use - we would have to modify the code ourselves to make it optional.

Is there a reason why SEMP is a strict requirement and not just an option?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions