Search:

With activemq I usually connect to the broker's JMX url or pid. I'm pretty sure you can turn on JMX in an embedded broker by using the url syntax "vm://localhost?useJmx=true"

I see the same problem running jre 1.4.0_08.
Maybe the example documentation is out of date, but this doesnt seem to work as shown.
I've got some managed beans that extend...

I couldnt get this to work either. The container never sets the NotificationPublisher.
Also, I didn't find spring's notifcation wrappers particularly helpful, so I stuck to pure JMX. Its better not...

I took out the import and added the referenced beans to the context:

ApplicationContext ctx = new ClassPathXmlApplicationContext(
new String[] {
...

If all the resources are part of a single jar, the import works. Why would a classpath resource from another jar be any different?

Importing a resource seems to work, but none of the beans defined in that resource are available:



<beans>
<import resource="classpath*:com/**/EventingBeans.xml"/>

<bean...