2 Replies Latest reply on Sep 21, 2004 5:51 AM by marndt

    DTDs (un)available

    marndt

      Starting up my local JBoss (3.2.3, although ist's not relevant) lead to a deployment error: an url to a dtd could not be resolved. Looking at the dtd-URL I have to say the app-server was right:

      http://www.jboss.org/j2ee/dtd/jboss-ds_1_0.dtd

      Seems that a lot of DTDs have gone over the weekend :-(

      Does anybody know whether this will be fixed in the foreseeable future? Is this the reason why all xml-files in the configurations are published without a DOCTYPE-entry?

        • 1. Re: DTDs (un)available
          starksm64

          Its fixed.
          [starksm@banshee9100 build]$ wget http://www.jboss.org/j2ee/dtd/jboss-ds_1_0.dtd
          --21:58:49-- http://www.jboss.org/j2ee/dtd/jboss-ds_1_0.dtd
          => `jboss-ds_1_0.dtd'
          Resolving www.jboss.org... 216.24.169.35
          Connecting to www.jboss.org[216.24.169.35]:80... connected.
          HTTP request sent, awaiting response... 200 OK
          Length: 13,463 [text/plain]

          100%[====================================>] 13,463 30.72K/s

          21:58:50 (30.72 KB/s) - `jboss-ds_1_0.dtd' saved [13463/13463]

          • 2. Re: DTDs (un)available
            marndt

            And is there a sophisticated configuration switch to tell JBoss not to fail when he can not resolve the URLs? That would make me feel much more safe when deploying to a production server or even just restarting the server... XML-validation is already done in dev-environment.

            Regards, Michael