Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <29575847.1185863509213.JavaMail.jira@brutus>
Date: Mon, 30 Jul 2007 23:31:49 -0700 (PDT)
From: "Jonas Lim (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQ-424) Make -Dactivemq.check_for_dtd_update
 default to "false", don't try network unless "true"
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/AMQ-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonas Lim resolved AMQ-424.
---------------------------

       Resolution: Cannot Reproduce
    Fix Version/s: 5.x
                   4.1.2

This is no longer applicable as the   ActiveMQDtdResolver is no longer included in activemq. Also, activemq now uses xsd

> Make -Dactivemq.check_for_dtd_update default to "false", don't try network unless "true"
> ----------------------------------------------------------------------------------------
>
>                 Key: AMQ-424
>                 URL: https://issues.apache.org/activemq/browse/AMQ-424
>             Project: ActiveMQ
>          Issue Type: Wish
>          Components: Broker
>    Affects Versions: 3.2.1
>         Environment: Behind firewall, on a slow network, on a disconnected workstation
>            Reporter: Anton Tagunov
>            Assignee: Jonas Lim
>             Fix For: 4.1.2, 5.x
>
>         Attachments: ActiveMQDtdResolver.diff, ActiveMQDtdResolver2.diff
>
>
> 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,

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.