Details
Description
I've been trying to write some of my own components, taking the file poller example as a starting basis.
Being a newbie, I just ran the test code through my IDE's debugger and noticed that the components' constructors were being called twice.
Also, another time consuming exercise was figuring that the endpoint had to be activated in my code, unlike the code present in the servicemix-component package. According to Sun's doc, the component is normaly meant to inform the engine that it has an active endpoint. What worries me here, is that there could be non-portability across containers. Perhaps the code in the PojoSupport init method could log a warning if the is no activated endpoint ?
Finaly, there seems to be a discrepency between LifeCycleMBean.STARTED in the servicemix-jbi.jar and the javax.jbi.management.LifeCycleMbean.RUNNING token.
Otherwise, keep up the good work ...