Makes sence to deploy activemq.dtd locally as part of installation.
Makes little sence to update only this thing from online w/o updating anything else.
When I was advocating ActiveMQ today in a Big Co had
a miserable experience - the thing would take 5 MINUTES TO START UP!
Good luck my fellow developers haven't lost faith in me and ActiveMQ so far!
Spent 2/3 working day in a significant stress, without being given a task to do that
sorting out maven-2, maven-1, eclipse integration before I found out that the reason
is that we're behind a corporate firewall and ActiveMQ should not make a call
outside the firewall anyway!
So my suggestions:
1) make sure default value for activemq.check_for_dtd_update is "false" in
http://svn.activemq.org/trunk/activemq/modules/core/src/java/org/activemq/spring/ActiveMQDtdResolver.java
2) make sure that if
- activemq.check_for_dtd_update is not "true"
- no /org/activemq/activemq.dtd has been found no classpath
we do not try to contact network and print a nice error right away
(This situation happened to me today - in Eclipse I didn't have activemq.dtd on classpath)
I'm rising this as Major because despite being miserable technically it has given a VERY BAD
impression in real life corporate environment.
cheers,
Wish
Resolved
Major
Make -Dactivemq.check_for_dtd_update default to "false", don't try network unless "true"
