Wednesday, October 10, 2012 9:40 AM
To: j-users@xerces.apache.org
Subject: RE: XInclude and xml:lang
I have not understand why I obtain ,
like this :
http://www.w3.org/2001/XInclude";>
It's no very logic.
For example, with XPath, //bar/xml:lang return something like this : &q
I have not understand why I obtain ,
like this :
http://www.w3.org/2001/XInclude";>
It's no very logic.
For example, with XPath, //bar/xml:lang return something like this : "";
so what in fact, the langage's bar is "fr".
Why I haven't or can't obtain something like this :
http://www.w3.
On which element did you get xml:lang=""
David A. Lee
d...@calldei.com
http://www.xmlsh.org
-Original Message-
From: polymorphisme [mailto:webmas...@polymorphisme.org]
Sent: Tuesday, October 09, 2012 2:23 PM
To: j-users@xerces.apache.org
Subject:
Michael Glavassevich schrieb am 31.03.2009 um 10:09:01 (-0400):
> Michael Ludwig wrote on 03/28/2009 12:39:14 PM:
>
> > Gareth Western schrieb am 02.02.2009 um 22:20:40 (+):
> > > Hi,
> > >
> > > I have an application which uses Xerces-J (2.9.0) to parse a large
> > > xml document which I'd l
Hi Michael,
Michael Ludwig wrote on 03/28/2009 12:39:14 PM:
> Gareth Western schrieb am 02.02.2009 um 22:20:40 (+):
> > Hi,
> >
> > I have an application which uses Xerces-J (2.9.0) to parse a large xml
> > document which I'd like to split into several smaller files just to
> > make it easie
Gareth Western schrieb am 02.02.2009 um 22:20:40 (+):
> Hi,
>
> I have an application which uses Xerces-J (2.9.0) to parse a large xml
> document which I'd like to split into several smaller files just to
> make it easier to manage.
> The schema prevents me from including the entire inner fil
Hi Gareth,
Gareth Western wrote on 02/04/2009 03:27:02 PM:
> Oh, I spoke too soon. From [1]: "XOM supports XInclude including the
> XPointer element() scheme and bare name XPointers. It does not support
> the XPointer xpointer() scheme." Which I guess means it's in the same
> boat as Xerces with
Oop. Forgot to reference my [1] in the other email. It's the XOM
Tutorial @ http://www.xom.nu/tutorial.xhtml#d0e1992
On Wed, Feb 4, 2009 at 8:27 PM, Gareth Western wrote:
> Oh, I spoke too soon. From [1]: "XOM supports XInclude including the
> XPointer element() scheme and bare name XPointers. It
Oh, I spoke too soon. From [1]: "XOM supports XInclude including the
XPointer element() scheme and bare name XPointers. It does not support
the XPointer xpointer() scheme." Which I guess means it's in the same
boat as Xerces with respect to what's supported.
Perhaps I'm going about this the wrong
Michael: XOM looks like it might be what I'm looking for. I originally
tried to use the old XIncluder project from sourceforge[1] until I
realised I'd probably need to use XPointers (which XIncluder does not
support either).
Joseph: I had considered that, but the situation is already complex
enoug
> If you need support for other kinds of XPointers then you may want to
> take a look on the net at some of the other XInclude processors that
> are available. e.g. perhaps XOM [4] supports what you're looking for.
Another quick idea: It's possible to implement an XInclude subset as an
XSLT styl
Hi Gareth,
As you've noticed from the FAQ, Xerces' support for XPointer in XInclude is
limited to the XPointer Framework [1] and XPointer element() scheme [2].
This is the minimum support [3] required for a conforming XInclude
processor. There has been no discussion on expanding/enhancing the XPo
> XInclude support in Xerces is only available as a parsing feature.
> If there is some processing you need to do prior to XInclude you
> need to serialize the document (after you've done your
> preprocessing) and then feed it back to the parser.
Alternatively, do the processing and then implem
Hi Olivier,
XInclude support in Xerces is only available as a parsing feature. If there
is some processing you need to do prior to XInclude you need to serialize
the document (after you've done your preprocessing) and then feed it back
to the parser.
Thanks.
Michael Glavassevich
XML Parser Deve
Hi Richard,
There are currently no plans to further enhance the XInclude implementation
in Xerces. I recall one of the issues with schema-determined IDs [1] is
that in order to support them we may have to buffer portions of or the
entire document in memory before being able to determine than an X
Hi Lars,
There are plenty of hex editors around. Take your pick:
http://en.wikipedia.org/wiki/Comparison_of_hex_editors.
Thanks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [EMAIL PROTECTED]
E-mail: [EMAIL PROTECTED]
"Lars Vogel" <[EMAIL PROTECTED]> wrote on 03/12/2008 1
Hi Michael,
Thank you for your response and explanation. I will then try to filter these
special signs (
) out via an XSLT transformation or via a small Java
program.
To your question:No, I didn't look at the byte sequence. How can I do this
(under MS Windows)?
Best regards, Lars
2008/3/12, Mi
Hi Lars,
When you say both files look the same have you actually taken a look at the
byte sequences? If you have you'll see that there are sequences of OD OA
(CR LF) all over the place in JavaScript.java. The XInclude processor is
doing what it's supposed to do: literally including every character
Hi Michael,
so there is no way to avoid this? Best regards, Lars
2008/3/4, Michael Glavassevich <[EMAIL PROTECTED]>:
>
> Lars' example is doing text inclusion:
>
>
> http://www.w3.org/2001/XInclude"; parse="text"
> href="JavaScript.java"/>
>
>
> so the XML 1.0 rules for end-of-line normalization
Lars' example is doing text inclusion:
http://www.w3.org/2001/XInclude"; parse="text"
href="JavaScript.java"/>
so the XML 1.0 rules for end-of-line normalization don't apply here. The
text in "JavaScript.java" is literally included in the document. That
includes any carriage returns. A serializer
is the carriage return character. Some systems use the
sequence to break lines (MS systems among others); some just use
(Unix systems, among others), and there are a few rare cases that use
something else. XML parsers are able to tolerate any of these on input and
will convert them all into
Hi Stuart,
Most likely you've run into this bug [1]. It hasn't been fixed yet.
Thanks.
[1] http://issues.apache.org/jira/browse/XERCESJ-1102
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [EMAIL PROTECTED]
E-mail: [EMAIL PROTECTED]
"Stuart Norton" <[EMAIL PROTECTED]> wrote
Hi Stuart,
"Stuart Norton" <[EMAIL PROTECTED]> wrote on 09/19/2007 04:57:18 PM:
> I have a question about how Xerces handles text entities when they
> are defined in both the parent and child of XInclusion. Are text
> entities supposed to be expanded before or after XIncludes are
> inserted in t
/flyboy/:
Seems to me, that this should pass schema validation, where
xmlns:xi=''http://www.w3.org/2001/XInclude";
Instead, xerces-j 2.9.0 schema validation gives:
'xpointer attribute must be present when href attribute is absent.'
This passes schema validation, but its not valid against th
Michael Glavassevich ca.ibm.com> writes:
>
> Paul Tomsic yahoo.com> wrote on 08/08/2006 06:37:39 PM:
>
> > i'm trying to set up xinclude support while validating
> > a XML doc against it's XSD.
> >
> > neither the javax.xml.validation.Validator nor the
> > SchemaFactory (in jdk 1.4) support t
/Dominic Brügger/:
Where can I set the
system ID for the XML file used as input for the transformation?
There's a |Source.systemId| [1] property. You could set the SAX
|InputSource.systemId| as well as you never know when it might be
needed.
public void processXSLT(String inFile, String[]
Michael Glavassevich wrote:
Dominic Brügger <[EMAIL PROTECTED]> wrote on 08/16/2006 07:56:19 AM:
How can I set up sax to resolve the include relative to the initial xml
file?
Relative URIs require a context for resolution. If you're passing the
parser an InputSource you need to set the syst
Dominic Brügger <[EMAIL PROTECTED]> wrote on 08/16/2006 07:56:19 AM:
> I have set up sax (I'm using Xerces 2.8) to be XInclude aware. It works
> when using an absolute uri but with a relative uri i get the following
> exception:
>
> org.xml.sax.SAXParseException: Include operation failed, rever
Paul Tomsic <[EMAIL PROTECTED]> wrote on 08/08/2006 06:37:39 PM:
> i'm trying to set up xinclude support while validating
> a XML doc against it's XSD.
>
> neither the javax.xml.validation.Validator nor the
> SchemaFactory (in jdk 1.4) support the
> "http://apache.org/xml/features/xinclude";
>
>
Hello,
Try setting the systemId on the LSInput by adding the line
"ret.setSystemId(systemId);" to the resolveResource() method of
TestResolver, just before the return statement. That solved the problem
for me when I ran your test.
Xerces' XIncludeHandler checks for recursive includes by doing
Hi Jan,
Jan Hackel <[EMAIL PROTECTED]> wrote on 07/25/2005 02:48:04 AM:
> Hi Michael,
>
> thanks for the help.
>
> > For Xerces, references property fixup is a no-op. As far as I know,
> > neither SAX or DOM have native support for this property, though the
DOM
> > specification [2] describ
Hi Michael,
thanks for the help.
> For Xerces, references property fixup is a no-op. As far as I know,
> neither SAX or DOM have native support for this property, though the DOM
> specification [2] describes how it can be computed. I'm curious about how
> you were expecting to access this info
Hi Jan,
Section 4.5.3 [1] describes fixup of the [references] property of an
attribute information item. For IDREF/IDREFS the property contains an
ordered list of element information items. Xerces provides no mechanism
for accessing this property nor does it keep an internal representation.
Fo
Hi Gerrard,
Gerrard Drury <[EMAIL PROTECTED]> wrote on 07/14/2005 04:27:17 AM:
> Hi Michael,
>
> Thanks for your response and explanation. I guess this logically leads
> to the next set of questions.
>
> 1. Is Xerces likely to consider adding support for this in the future?
We kicked around a
Hi Michael,
Thanks for your response and explanation. I guess this logically leads
to the next set of questions.
1. Is Xerces likely to consider adding support for this in the future?
2. Do you have any advice for a workaround?
While investigating this further, I also might have come across
Hi Gerrard,
The reason this isn't working for you is that in Xerces, schema validation
is performed on the result infoset produced by the XInclude processor.
(XInclude does not specify a processing order, so this was an
implementation decision.) When the XPointer is processed it isn't known
th
36 matches
Mail list logo
