[xmlc] Re: Re: Re: Re: Re: Accessing the body in a Document
"Jacob Kjome" <[email protected]> Wed, 16 Jun 2010 09:56:20 -0500
| Newsgroups | gmane.comp.java.enhydra.xmlc |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format... ------------=_1276700193-5928-2202 Content-Type: text/plain;charset=iso-8859-1;format="flowed" Content-Transfer-Encoding: quoted-printable On Wed, 16 Jun 2010 11:36:16 +0200 Franck Routier <[email protected]> wrote: > Hi, >=20 >> Which parser are you using? Are you using the XML or HTML parser? >=20 > I am using the xml parser, not NekoHTML. >=20 > I'm not sure though how this is triggered, I think it comes from the > -dom xhtml in my options.xmlc file. >=20 "-dom xhtml" is actually a shortcut for... -domfactory org.enhydra.xml.xhtml.XHTMLDomFactory The one thing I can't remember is whether it changes the default parser?=A0= Can=20 you ensure that you are using a validating parser by specifying?... -parser xerces The other non-validating option (which is, generally, the default) is... -parser nekohtml The other thing that I believe can influence this stuff is.... -docformat [xml | html | auto] When the docformat is "auto" (the default), XMLC checks the document for = the=20 namespace.... xmlns=3D"http://www.w3.org/1999/xhtml" If that exists, then it auto-detects the docformat to be "xml", otherwise= it=20 detects it to be "html".=A0 To be extra sure you are using the validating= XML=20 parser, please specify the following... -dom xhtml -parser xerces -docformat xml > After looking at the documentation of xmlc online > (http://xmlc.ow2.org/doc/doc/xmlc/user-manual/xmlc-command.html) I was = a > bit surprised that this option is not mentionned. Only lazydom and > xerces are mentionned as -dom possible values. >=20 Sorry, those docs way out of date.=A0 They are from before XMLC 2.2.=A0 I= 've made=20 plenty of code updates, just not many doc updates.=A0 Pretty much all rec= ent=20 documentation has been captured in the release notes for each release.=A0= Not=20 ideal, but without help the current situation is unlikely to change much. > What can be the impact of using -dom xhtml versus -dom lazydom or -dom > xerces options ? >=20 "xhtml" indicates to use the custom XHTML DOM that XMLC provides.=A0 "xer= ces"=20 indicates to use the standard XML-based DOM that comes with the Xerces=20 library.=A0 "lazydom" indicates to use the custom XML-based DOM that XMLC= =20 provides.=A0 Some other options trigger a few other things. When "-dom xerces" is combined with "-docformat html" and/or "-parser=20 nekohtml", it will trigger usage of the Xerces HTML DOM.=A0 When "-dom la= zydom"=20 is defined (along with the other mentioned options), the custom HTML-base= d=20 LazyDOM is used. Note that the default DOM in Xerces2 is a deferred node DOM, similar in s= tyle=20 to the custom XMLC LazyDOM, though implemented very differently.=A0 I hav= e not=20 performed tests, but I believe that this reduces the necessity for using=20 XMLC's own LazyDOM. >=20 >Franck > Jake ------------=_1276700193-5928-2202 Content-Type: text/plain; charset="UTF-8"; name="message-footer.txt" Content-Disposition: inline; filename="message-footer.txt" Content-Transfer-Encoding: quoted-printable -- You receive this message as a subscriber of the [email protected] mailing list= . To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=3Dhelp OW2 mailing lists service home page: http://www.ow2.org/wws ------------=_1276700193-5928-2202--