[ https://issues.apache.org/activemq/browse/SM-702?page=all ]
Guillaume Nodet updated SM-702:
-------------------------------
Fix Version/s: 3.0.1
3.1
> Components instantiated multiple times
> --------------------------------------
>
> Key: SM-702
> URL: https://issues.apache.org/activemq/browse/SM-702
> Project: ServiceMix
> Issue Type: Improvement
> Affects Versions: 3.0
> Environment: Win32 - ServiceMix 3.0-incubating
> Reporter: Andrew Chullikal
> Fix For: 3.0.1, 3.1
>
> Attachments: src.zip
>
>
> 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 ...
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
