Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve JMX representation of IPF Camel Objects #65

Closed
4effo opened this issue May 24, 2011 · 1 comment
Closed

Improve JMX representation of IPF Camel Objects #65

4effo opened this issue May 24, 2011 · 1 comment
Assignees
Labels

Comments

@4effo
Copy link
Collaborator

4effo commented May 24, 2011

IPF Camel Objects (Components, Endpoints etc.) use the default Camel naming wrappers for registering beans on the MBeanServer.
This behaviour should be improved to be easier to find them in the JMX Object tree and also to show more details in the JMX client.

@ghost ghost assigned 4effo May 24, 2011
@4effo
Copy link
Collaborator Author

4effo commented May 31, 2011

At this phase the following endpoints will receive more MBean property view:
DefaultItiEndpoint -> ManagedWsItiEndpoint
MllpEndpoint -> ManagedMllpItiEndpoint

@4effo 4effo closed this as completed May 31, 2011
alexandruti pushed a commit to alexandruti/ipf that referenced this issue Apr 1, 2020
krasserm#64: dynamic route extensions will now fail early if the route fails to startup
krasserm#53: alternative way of mllp-dispatch configuration
krasserm#65: expose custom 'mllp' component where HL7v2TransactionConfig and AuditStrategies can be set via parameters
alexandruti pushed a commit to alexandruti/ipf that referenced this issue Apr 1, 2020
alexandruti pushed a commit to alexandruti/ipf that referenced this issue Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant