Hi, I am playing around with creating purist JBI components. I have noticed that what appears to be some odd behavior with respect to the bootstrap lifecycle and component lifecycle. I've created very basic implementations of the Bootstrap, Component, ComponentLifeCycle, and ServiceUnitManager interfaces. I placed logging statements in each one of the lifecycle methods (init, doInstall, doUninstall, start, stop, shutdown, etc).
When I place my component zip file in the hotdeploy directory I see all the startup related logging messages, as expected. What I don't see is any stop/shutdown related logging messages when I stop servicemix (CTRL-C). Is this normal? If I drop a new version of my component in the hotdeploy directory, I see servicemix attempting to deploy the new version, but never stopping/shutting down the old version. Is this expected behavior? In fact, the only time I see any stop/shutdown messages is when I remove the component from the hotdeploy directory while servicemix is running. If I wanted to write a component that grabbed some resource on startup and needed to free it or clean it up on stop, how would I do it? -- in the purist JBI world. Thanks, Jeff
