Loading...
Home > I O Error > I/o Error Reported By Xml Parser Processing

I/o Error Reported By Xml Parser Processing

I'm working with DTD-based (I know, but that's how it is) XML files that refer to DTD and entities files using relative paths. DITA Open Toolkit member jelovirt commented Feb 26, 2016 @eerohele, does diff --git a/src/main/java/org/dita/dost/writer/ChunkTopicParser.java b/src/main/java/org/dita/dost/writer/ChunkTopicParser.java index 9aa62d1..78ad559 100644 --- a/src/main/java/org/dita/dost/writer/ChunkTopicParser.java +++ b/src/main/java/org/dita/dost/writer/ChunkTopicParser.java @@ -204,7 +204,7 @@ public final class ChunkTopicParser extends jelovirt added P1 and removed xhtml labels Mar 3, 2016 DITA Open Toolkit member jelovirt commented Mar 3, 2016 👍 for making a simple fix on hotfix/2.2.3. Show Thomas Walzer added a comment - 28/Jan/15 15:57 The patch (I hope it works the way I created it) contains a test case to reproduce the issue. http://renderq.net/i-o-error/i-o-error-reported-by-xml-parser-processing-no-protocol.php

Connected to localhost (127.0.0.1) port 9090 (#0) > POST /schematron/validate HTTP/1.1 > Host: localhost:9090 > User-Agent: curl/7.43.0 > Accept: / > Content-Type: application/xml > Content-Length: 358 > upload completely sent off: That seems to return values which contain "\" instead of "/". DITA Open Toolkit member jelovirt commented Feb 29, 2016 Will try to take a look at this. Thomas. http://stackoverflow.com/questions/7236291/saxon-error-with-xslt-import-statement

I can assist in debugging if help is needed. Could you retry the develop branch on Windows to see if it made any difference? RE: Problem with EntityResolver and document() - Added by O'Neil Delpratt over 3 years ago Ok. Could someone try on Windows?

I have asked Claus Ibsen to merge the pull request as I don't have the right privileges to push to master. Best, Ron Re: [saxon] collection() throws malformed URI exception for files referencing other files with relative path From: Michael Kay - 2014-10-31 12:46:24 I have reproduced your results. I will review it and merge it for you. Hide Permalink Johan Mörén added a comment - 09/Aug/16 14:28 - edited I'v been trying some things out and found that a possible way to fix this issue is to allow

Thanks in advance. -Stefan « Return to Saxon XSLT and XQuery Processor | 1 view|%1 views Loading... F:/tést/test.xml) in the path, the transformation fails with following error: > > Error > I/O error reported by XML parser processing file:/F:/tést/test.xml: Path contains invalid character: é > > The culprit Using camel-schematron in an OSGI-application running under Karaf. anchor It chocks up on the newTransformer() method above....

Hide Permalink ayache khettar added a comment - 30/Jun/16 06:43 Hi Thomas Walzer. Thanks Show ayache khettar added a comment - 10/Aug/16 08:51 Hi Johan. Hit '' or 'system:shutdown' to shutdown ServiceMix. Will try to make a pull request.

share|improve this answer answered Jan 29 '14 at 12:24 Michael Kay 78.9k44080 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google But I am confident we will get there Hide Permalink Thomas Walzer added a comment - 03/Jul/16 08:52 Hi Ayache, please do not apologise. I made a small change there to replace windows-like separators with unix like and the test samples were successfully published. So change new StreamSource(X) to new StreamSource(new File(X)) because the "new File()" constructor works with file names. (Internally, the file name will be automatically converted to a URI, but you don't

Yet, as soon as there is a special character (e.g. DITA Open Toolkit member raducoravu commented Feb 29, 2016 In AbstractChunkTopicParser there is a call to a deprecated method called "resolveTopic". Apache ServiceMix (7.0.0.M2) Hit '' for a list of available commands and '[cmd] --help' for help on a specific command. Fix now applied to master.

I tried XsltCompiler, etc and same thing... Please don't fill out this field. It's quite happy to read the file and process it, but when it tries to use it as an absolute URI to resolve the relative URI of the external entity, it Following error is thrown: Error I/O error reported by XML parser processing file:/F:/tést/test.xml: Path contains invalid character I'll illustrate this with following minimal test case (attached): XML source (test.xml):

Following report has been tested with Saxon-HE 9.6.0.1J on Windows-7 Pro 64bit. > > I'm working with DTD-based (I know, but that's how it is) XML files that refer to DTD Best, Ron Thread view [saxon] collection() throws malformed URI exception for files referencing other files with relative path From: - 2014-10-28 03:16:09 Attachments: tést.zip Hi, I'm encountering a problem with I will review it and merge it for you.

See the NOTICE file distributed with * this work for additional information regarding copyright ownership. * The ASF licenses this file to You under the Apache License, Version 2.0 * (the

I'm running version 2.15.3. jelovirt added a commit that referenced this issue Mar 13, 2016 jelovirt Fix href rewrite in chunking

It works perfectly well with another XML editor...However, when I try to open that document with Oxygen in Author mode, it complains about E [ISO Schematron] I/O error reported by XML like this : /** * Licensed to the Apache Software Foundation (ASF) under one or more * contributor license agreements. Hide Permalink Claus Ibsen added a comment - 09/Jan/16 14:37 The patch is only an unit test, not the needed implementation to support includes. Regards Show ayache khettar added a comment - 19/Jan/16 16:27 Hi Johan What version of camel are you using?

If so, what does it state?So could you give me more precise details about your situation? You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is We could fix this in 2.2.4 we decide to release it and if someone actually fixes this for 2.2. Now, the weird part is that my entity resolver is called on half the document() calls, while the other half fail as if it wasn't there at all (first call works,

Is the DTD correct? Join them; it only takes a minute: Sign up Saxon error with XSLT import statement up vote 5 down vote favorite The Saxon processor gives me an error whenever I have Show the code for your URIResolver implementation. –Jim Garrison Aug 29 '11 at 22:21 add a comment| 1 Answer 1 active oldest votes up vote 5 down vote accepted You likely DITA Open Toolkit member jelovirt commented Feb 26, 2016 The @path is supposed to be system path, no an URI.

But I am still getting the following error when I execute the stylesheet: Error on line 1 column 1 SXXP0003: Error reported by XML parser: The markup declarations contained or pointed Base URI {file:/C:/Users/radu_coravu/Des...} is invalid: Invalid relative URI: Illegal character in path at index 2: ..\glossary\named-user.dita: file:/C:/Users/radu_coravu/Desktop/zuzu/temp/xhtml/topics/register-license-key.dita [xslt] Failed to process null BUILD FAILED C:\Users\radu_coravu\Documents\dot-develop\src\main\build.xml:41: The following error occurred while executing [email protected]> [email protected]> [email protected]> [email protected]> [email protected]>Recoverable error on line 472 FODC0002: I/O error reported by XML parser processing null: null Unable to open referenced included file: /tmp/schematron/rules/rules.sch Unable to locate id attribute: Yeah, then it's definitely a regression (although I'd say this could be considered a regression even in cases where the authored content had a backslash).

What would be a proper translation for "Bullshit"? Show Thomas Walzer added a comment - 28/Jun/16 11:40 Hi Ayache, did you manage to look into this? jelovirt added this to the 2.2.3 milestone Feb 26, 2016 DITA Open Toolkit member eerohele commented Feb 26, 2016 @raducoravu Ah, I see — I didn't look at the input files Regards Hide Permalink Johan Mörén added a comment - 19/Jan/16 20:16 Hi Ayache!

Show ASF GitHub Bot added a comment - 15/Aug/16 13:18 GitHub user hutchkintoot opened a pull request: https://github.com/apache/camel/pull/1123 Fix for CAMEL-8287 Allows a user to supply a custom URIResolver to be jar; > C:\bea\wlportal4.0\config\idevDomain\applications\idenApp\idenClasses.jar;C: \bea > \wlportal4.0\config\idevDomain\applications\idenApp\iden\WEB-INF\lib\cdkjava 3500 jar, -d, C:\bea\wlportal4.0\config\idevDomain\applications\Entapp\webapp1\WEB-I NF\_tmp_war_idevDomain_webapp1, C:\bea\wlportal4.0\config\idevDomain\application > s\Entapp\webapp1\WEB-INF\_tmp_war_idevDomain_webapp1\jsp_servlet\__test1.jav a]) find similars weblogic.utils.compiler weblogic.servlet.jsp Atmosphere weblogic weblogic.kernel 0 See more Not finding the right solution? Following catalog (e.g. "test.catalog.xml") works for this example: When this catalog file is stored in the same location as the XML file containing the reference If I remove the import statement, everything works!!

I will update the wiki shortly.