I am poking at JMX component management with MC4J and see some odd
behavior. Using the file-binding example:
after startup and fileSender and filePoller currentState are queried
they report "unknown" even though they are running.
once stopped/started currentState reports fine.
If I stop fileSender but leave filePoller running, fileSender still
gets invoked when filePoller sends message. I would expect once
stopped messages would not not continue to be delivered. Maybe
'cause they're POJOs or is it the routing style?
Other bean attributes like exchangeCount do not appear to be maintained.
Is this all just a todo/incomplete or am I misunderstanding?
Larry
