Description
- XBeanBrokerService#afterPropertiesSet() method checks the start flag and is annotated as @PostConstruct so it's called at startup
- BrokerService#start() method has the @PostConstruct annotation as well
- There is no way for the BrokerService class to check the 'start' flag in the XBeanBrokerService subclass.
- Spring will call BOTH @PostConstruct methods resulting in the broker being started regardless of the xbean start flag
According to Gary Tully:
That looks like a bug that was introduced in
http://svn.apache.org/viewvc?rev=908182&view=rev the postConstruct on
the start method does invalidate the
XBeanBrokerService#afterPropertiesSet() smarts.
As discussed in:
http://old.nabble.com/XBean-%27start%3Dfalse%27-not-working--td29086727.html
Attachments
Attachments
Issue Links
- is broken by
-
AMQ-2601 Make amq blueprint friendly
- Closed