| dtd resolution no longer available [message #141025] |
Wed, 28 September 2005 14:07  |
Eclipse User |
|
|
|
Originally posted by: mark_lybarger.nospam.yahoo.com
recently, our fine folks have instituted a proxy server which the
computers must go through to get to the outside. we weren't given the
proxy server info, only a pac file to set for the browser. thus, i
haven't configured eclipse to use a proxy server for anything.
eclipse is now complaining about the deployment descriptors for my web
application on the web.xml and associated vendor specific deployment
descriptor. eclipse says: "connection timed out: connect".
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
outside of modifying the dd's directly to use local files, how can i get
eclipse to accept that the internet is no longer available?
|
|
|
|
| Re: dtd resolution no longer available [message #141178 is a reply to message #141125] |
Wed, 28 September 2005 20:22  |
| Eclipse User |
|
|
|
Originally posted by: mark_lybarger.nospam.yahoo.com
lmandel@ca.ibm.com wrote:
> Hmm. There are two possibilities here.
> 1. You can register the DTDs with the XML catalog so they can be located
> by the tools. This will allow your deployment descriptors to be validated
> as before but without the internet.
This is rather tedious, especially with perhaps unknown dtd's being used.
> 2. When the DTD is not present the XML validator should probably produce a
> warning instead of an error. If this sounds better to you please open a
> bug against the Web Tools -> wst.xml component and I'll investigate
> further.
Most application servers will resolve the dtds for standard web
definitions internally and not even bother with going out for the dtd.
Would this be an option?
The reason I brought it up was that a clean build takes an annoyingly long
time. The only two files that eclipse displayed as invalid were the
web.xml and jboss-web.xml. I defined these in the XML Catalog as local
file dtds. The files no longer show up as error in eclipse, but the build
process still takes a long time. The progress monitor shows "Validation
of <project> by JSP Syntax Validator has started...", this lasts quite a
while (45 sec?), then the "Validation of <project> by XML Validator has
started..." shows for about the same time. the rest of the build seems to
fly by. These are the two items that seem to crawl.
My project is a very small web application with one servlet and 8
supporting classes including junit classes. Any ideas what could be
causing this would be most appreciated!
Thanks!
~mark
|
|
|
Powered by
FUDForum. Page generated in 0.03056 seconds
] 
Search
Help
Register
Login
Home
