Menu
▾
▴
Re: [Geoserver-devel] IntelliJ users, how do you handle "Entity resolution disallowed for file:/home/aaime/devel/git-gt/modules/.../*.xsd"
|
From: Ian T. <ijt...@gm...> - 2017-12-14 13:55:55
|
I have the same issue in my big eclipse workspace with both GT and GS in it. I get around it currently by closing the XSD modules and letting eclipse pick the jars up but it would be much easier if in tests we allowed the use of file:// urls. Ian On 14 December 2017 at 13:35, Andrea Aime <and...@ge...> wrote: > Hi, > I'm dabbling with IntelliJ lately and I have both GeoServer and GeoTools > linked in the same big > IntelliJ project. > Works nice as I do a lot of cross project activity, this allows to just > see the effect of changes done > in GT or JAI-Ext without having to rebuild stuff in the middle. > > However I'm getting a lot of failures because the sources of XSD files are > available via file:/ instead > of jar:/... (since projects are directly linked instead of going through > the jar files), with traces like: > > Caused by: org.xml.sax.SAXException: Entity resolution disallowed for > file:/home/aaime/devel/git-gt/modules/extension/xsd/xsd-wps/ > target/classes/org/geotools/wps/wpsAll.xsd > at org.geotools.xml.PreventLocalEntityResolver.resolveEntity( > PreventLocalEntityResolver.java:76) > at org.geotools.xml.PreventLocalEntityResolver.resolveEntity( > PreventLocalEntityResolver.java:101) > at org.geotools.xml.impl.ParserHandler.resolveEntity( > ParserHandler.java:289) > at com.sun.org.apache.xerces.internal.util.EntityResolver2Wrapper. > resolveEntity(EntityResolver2Wrapper.java:177) > at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntity( > XMLEntityManager.java:1081) > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader. > resolveDocument(XMLSchemaLoader.java:657) > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator. > findSchemaGrammar(XMLSchemaValidator.java:2430) > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator. > handleStartElement(XMLSchemaValidator.java:1767) > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator. > startElement(XMLSchemaValidator.java:740) > at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl. > scanStartElement(XMLNSDocumentScannerImpl.java:374) > at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$ > NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:613) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl > $FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3132) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ > PrologDriver.next(XMLDocumentScannerImpl.java:852) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next( > XMLDocumentScannerImpl.java:602) > at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next( > XMLNSDocumentScannerImpl.java:112) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl > .scanDocument(XMLDocumentFragmentScannerImpl.java:505) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse( > XML11Configuration.java:841) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse( > XML11Configuration.java:770) > at com.sun.org.apache.xerces.internal.parsers.XMLParser. > parse(XMLParser.java:141) > at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse( > AbstractSAXParser.java:1213) > at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$ > JAXPSAXParser.parse(SAXParserImpl.java:643) > at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl. > parse(SAXParserImpl.java:327) > at org.geotools.xml.Parser.parse(Parser.java:253) > at org.geotools.xml.Parser.parse(Parser.java:201) > at org.geoserver.wps.xml.v1_0_0.WpsXmlReader.read(WpsXmlReader.java:51) > > How are others handling this issue? > Would it make sense to allow entity resolution in test code, besides the > few that do check the resolution prevention > mechanism? > > Cheers > Andrea > > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions S.A.S. > Via di Montramito 3/A > 55054 Massarosa (LU) > phone: +39 0584 962313 <+39%200584%20962313> > fax: +39 0584 1660272 <+39%200584%20166%200272> > mob: +39 339 8844549 <+39%20339%20884%204549> > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003 > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Geoserver-devel mailing list > Geo...@li... > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > -- Ian Turton |