[jdom-interest] help
Curley, Thomas
thomas.curley at euroconex.com
Thu Aug 22 01:08:08 PDT 2002
-----Original Message-----
From: jdom-interest-admin at jdom.org [mailto:jdom-interest-admin at jdom.org]
Sent: 22 August 2002 07:08
To: jdom-interest at jdom.org
Subject: jdom-interest digest, Vol 1 #1019 - 5 msgs
Send jdom-interest mailing list submissions to
jdom-interest at jdom.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.denveronline.net/mailman/listinfo/jdom-interest
or, via email, send a message with subject or body 'help' to
jdom-interest-request at jdom.org
You can reach the person managing the list at
jdom-interest-admin at jdom.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of jdom-interest digest..."
Today's Topics:
1. entity problem (Gu Xueying (Shinnie Gu))
2. Setting a adtd at parse time (Akacem Mohammed)
3. RE: Setting a adtd at parse time (Norrman Per)
4. Re: Patches for JDOMSource and JDOMResult (was: Re: [jdom-interest] JDOMResult silently absorbs document fragments) (Markus Pallo)
5. Need some sample code... (Pandia, Rajesh)
--__--__--
Message: 1
From: "Gu Xueying (Shinnie Gu)" <Shinnie.Gu at iuniverse.com.cn>
To: jdom-interest at jdom.org
Date: Wed, 21 Aug 2002 16:15:01 +0800
Subject: [jdom-interest] entity problem
I'm using jdom-b8. In my xml there are ’,&#.....
But I found that after parsed by parser, ’ changed to &#8217;.
Then how can I get ’ in the resutl xml?
Any help is appreciated.
Shinnie Gu
IUniverse(Shanghai)Co.,Ltd.
Tel:8621-58305001 Ext.8701
--__--__--
Message: 2
From: Akacem Mohammed <Mohammed.Akacem at arbeitsamt.de>
To: "'jdom-interest at jdom.org'" <jdom-interest at jdom.org>
Date: Wed, 21 Aug 2002 10:34:16 +0200
Subject: [jdom-interest] Setting a adtd at parse time
Hallo every body,
I want to validate against a schema or a dtd using a config file.
That means I don't want to read the url of the schema or the dtd against which I want to validate from the file I want to parse,
but from a config file, so I need a methode like parser.setSchema(urlschema). I know that there is this methode in the microsoft parser. ( I am using the Jxerces ).
thanks for any hint
Mohammed
--__--__--
Message: 3
From: Norrman Per <per.norrman at canovia.se>
To: "'Akacem Mohammed'" <Mohammed.Akacem at arbeitsamt.de>,
"'jdom-interest at jdom.org'" <jdom-interest at jdom.org>
Subject: RE: [jdom-interest] Setting a adtd at parse time
Date: Wed, 21 Aug 2002 12:33:03 +0200
Hi,
For DTD, use SAXBuilder#setEntityResolver(...)
For schema, use SAXBuilder#setProperty(...), where the property is either
http://apache.org/xml/properties/schema/external-schemaLocation
or
http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation
/pmn
-----Original Message-----
From: Akacem Mohammed [mailto:Mohammed.Akacem at arbeitsamt.de]
Sent: Wednesday, August 21, 2002 10:34 AM
To: 'jdom-interest at jdom.org'
Subject: [jdom-interest] Setting a adtd at parse time
Hallo every body,
I want to validate against a schema or a dtd using a config file. That means
I don't want to read the url of the schema or the dtd against which I want
to validate from the file I want to parse,
but from a config file, so I need a methode like
parser.setSchema(urlschema). I know that there is this methode in the
microsoft parser. ( I am using the Jxerces ).
thanks for any hint
Mohammed
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhos
t.com
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
--__--__--
Message: 4
From: Markus Pallo <pallo at dig.de>
To: Laurent Bihanic <laurent.bihanic at atosorigin.com>
Subject: Re: Patches for JDOMSource and JDOMResult (was: Re: [jdom-interest] JDOMResult silently absorbs document fragments)
Date: Wed, 21 Aug 2002 15:44:45 +0200
Cc: jdom-interest at jdom.org
Hello,
i continued now my tests. It looks like xerces is unable to parse the
document fragment which is created in SAXOutputter dtdEvents(Document
document). Also caucho sax parser tells unable to parse Document.
The root element is missing.
If i add the root element in line 677 of SAXOutputter its working
----------- snip -----
buf.append('>');
String dtdDoc =
buf.append('<').append(docType.getElementName()).append("/>").toString();
----------- end snip -----
But i am not sure, if its correct for the context of fire dtd events.....
Markus
On Tuesday 20 August 2002 17:08, Markus Pallo wrote:
> Hi,
>
> it looks like he checks now the dtd, but crashes later...
> see the stackTrace...
>
> I will continue with the checks tomorrow.
>
> Markus
>
>
>
> java.lang.ArrayIndexOutOfBoundsException
> at org.apache.xerces.impl.dtd.DTDGrammar.endParameterEntity(Unknown
> Source)
> at
> org.apache.xerces.impl.dtd.XMLDTDProcessor.endParameterEntity(Unknown
> Source) at org.apache.xerces.impl.XMLDTDScannerImpl.endEntity(Unknown
> Source) at org.apache.xerces.impl.XMLEntityManager.endEntity(Unknown
> Source) at
> org.apache.xerces.impl.XMLEntityManager$EntityScanner.load(Unknown Source)
> at
> org.apache.xerces.impl.XMLEntityManager$EntityScanner.load(Unknown Source)
> at
> org.apache.xerces.impl.XMLEntityManager$EntityScanner.skipSpaces(Unknown
> Source)
> at org.apache.xerces.impl.XMLDTDScannerImpl.skipSeparator(Unknown
> Source)
> at org.apache.xerces.impl.XMLDTDScannerImpl.scanDecls(Unknown
> Source) at
> org.apache.xerces.impl.XMLDTDScannerImpl.scanDTDExternalSubset(Unknown
> Source) at
> org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknow
>n Source)
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
> at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
> at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
> Source) at org.jdom.output.SAXOutputter.dtdEvents(SAXOutputter.java:680) at
> org.jdom.output.SAXOutputter.output(SAXOutputter.java:597) at
> org.jdom.transform.JDOMSource$DocumentReader.parse(JDOMSource.java:432)
> at
> org.apache.xml.dtm.ref.DTMManagerDefault.getDTM(DTMManagerDefault.java:493)
> at
> org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java
>:590) at
> org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java
>:1054) at
> org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java
>:1032) at
> de.dig.dfc.framework.TransformerService.transformToFop(TransformerService.j
>ava:327) at
> de.dig.dfc.framework.TransformerService.process(TransformerService.java:117
>)
>
> Markus
>
> On Tuesday 20 August 2002 14:12, you wrote:
> > Hi,
> >
> > Attached are 2 patches (full source and cvs diff) for JDOMSource and
> > JDOMResult that fix the following problems:
> >
> > - JDOMSource: Do no allocate a new XMLReader for every call to
> > getXMLReader(). JDOMSource now allocates only one XMLReader and returns
> > this instance for every call to getXMLReader(), thus allowing
> > applications to access the XMLReader instance and configure it prior
> > handing the JDOMSource to the XSL transformer.
> >
> > - JDOMResult: Support for transformation results that are not
> > well-formed XML documents. JDOMResult now accepts node sets as result of
> > transformations and make them available to the applications as a List of
> > JDOM nodes (method getResult()). Existing methods dealing only with
> > Documents have been marked as deprecated.
> >
> > Markus, could you run a quick test to verify that the JDOMSource patch
> > fixes your EntityResolver problem?
> > Elliotte, could you check the new JDOMResult interface and
> > implementation?
> >
> > TIA
> >
> > Laurent
>
> _______________________________________________
> To control your jdom-interest membership:
> http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourho
>st.com
--__--__--
Message: 5
From: "Pandia, Rajesh" <rajesh.pandia at matrixone.com>
To: "JDOM Support (E-mail)" <jdom-interest at jdom.org>
Date: Wed, 21 Aug 2002 18:14:35 -0400
Subject: [jdom-interest] Need some sample code...
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C24960.21D15450
Content-Type: text/plain;
charset="iso-8859-1"
I need some sample code to parse this XML string:
<SyncExpression action="Add">Supplier</SyncExpression>
Please help !
------_=_NextPart_001_01C24960.21D15450
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Need some sample code...</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2 FACE="Arial">I need some sample code to parse this XML string:</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial"><SyncExpression action="Add">Supplier</SyncExpression></FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Please help !</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C24960.21D15450--
--__--__--
_______________________________________________
To control your jdom-interest membership:
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost.com
End of jdom-interest Digest
More information about the jdom-interest
mailing list