Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 116120

Summary:	XSD content model does not wrap results returned from cache
Product:	[WebTools] WTP Source Editing	Reporter:	Lawrence Mandel <lmandel>
Component:	wst.xsd	Assignee:	Craig Salter <csalter>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	major
Priority:	P3	CC:	csalter, david_williams, nagrawal
Version:	0.7
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Lawrence Mandel

2005-11-12 17:43:58 EST

From bug 113537, comment #2,

This seems to be the problem while loading XML schema and DTD


I am also seeing this error when trying to create projects which use DTD's

!ENTRY org.eclipse.xsd 2 0 2005-11-01 09:24:24.314
!MESSAGE External entity not found: "file:///D:\Workspaces\WTP8
\.metadata\.plugins\org.eclipse.wst.internet.cache/XMLSchema.dtd".
!STACK 0
java.io.FileNotFoundException: D:\Workspaces\WTP8
\.metadata\.plugins\org.eclipse.wst.internet.cache\XMLSchema.dtd (The system 
cannot find the file specified)
	at org.apache.crimson.parser.Parser2.fatal(Unknown Source)
	at org.apache.crimson.parser.Parser2.externalParameterEntity(Unknown 
Source)
	at org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Unknown Source)
	at org.apache.crimson.parser.Parser2.parseInternal(Unknown Source)
	at org.apache.crimson.parser.Parser2.parse(Unknown Source)
	at org.apache.crimson.parser.XMLReaderImpl.parse(Unknown Source)
	at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(Unknown Source)
	at org.eclipse.xsd.util.XSDResourceImpl.getDocument
(XSDResourceImpl.java:238)
	at org.eclipse.xsd.util.XSDResourceImpl.doLoad
(XSDResourceImpl.java:412)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load
(ResourceImpl.java:977)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load
(ResourceImpl.java:832)
	at org.eclipse.wst.xsd.contentmodel.internal.XSDImpl.buildXSDModel
(XSDImpl.java:205)
	at org.eclipse.wst.xsd.contentmodel.internal.XSDImpl.buildCMDocument
(XSDImpl.java:169)
	at 
org.eclipse.wst.xsd.contentmodel.internal.CMDocumentFactoryXSD.createCMDocument
(CMDocumentFactoryXSD.java:37)
	at 
org.eclipse.wst.xml.core.internal.contentmodel.ContentModelManager.createCMDocu
ment(ContentModelManager.java:56)
	at 
org.eclipse.wst.xml.core.internal.contentmodel.modelqueryimpl.CMDocumentManager
Impl.buildCMDocument(CMDocumentManagerImpl.java:277)
	at 
org.eclipse.wst.xml.core.internal.contentmodel.modelqueryimpl.CMDocumentManager
Impl$AsyncBuildOperation.run(CMDocumentManagerImpl.java:262)
	at 
org.eclipse.wst.xml.core.internal.contentmodel.modelqueryimpl.CMDocumentManager
Impl$1.run(CMDocumentManagerImpl.java:228)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

Looks like the org.eclipse.wst.xsd.contentmodel is not using both the logical
and physical results returned from the resolver.

Comment 1 Craig Salter

2005-11-12 18:13:56 EST

Hey Lawrence, I've got a fix in mind for this so I'll assign it to me.

Comment 2 Craig Salter

2005-11-20 18:37:38 EST

For the most part this bug is a dup of bug 113537.  There is however a small issue that isn't addressed by that fix.  There seems to be a limitation in the XSD model that prevents us from controlling the way XSD->DTD references get resolved. Luckily there's not a lot of XML Schemas written that use this pattern... but they are out there. I've opened bug 117231 on the XSD project to track this.

*** This bug has been marked as a duplicate of 113537 ***

Comment 3 Lawrence Mandel

2005-12-19 13:38:11 EST

Closing duplicate.