[JDEV] Jabberd config file & namespaces
mass at akuma.org
Tue Oct 2 00:54:28 CDT 2001
This is the difference between a document being well-formed, and
validated. Validation within Jabber is pretty impossible, as the server
itself would have to validate all XML sent through it. Also, the rules
for nonvalid XML are the same as parsing XML in general - you stop where
the error happens; you cannot continue. This is inappropriate
considering that a document in the Jabber sense is a collection of
The general rule is that which you don't comprehend, you ignore.
See if you can throw xerces into a non-validating mode, and everything
should be dandy. It might be complaining because there is no handler
registered with the java.net.URLFactory to handle "Jabber:" URIs. (I'm
assuming xerces-j here). I haven't used xerces-J because previous
versions had a quite annoying caching problem which made it totally
unsuitable for Jabber client work.
Franck Mangin wrote:
> Is the jabberd configuration file that ships with the distribution a
>valid XML file?
>According to the w3c spec (http://www.w3.org/TR/REC-xml-names/), it
>seems like namespaces cannot contain ':', so a name such as
>jabber:config:jsm would be invalid (xerces for one chokes on
> Also, I thought you had to declare a namespace before using it - which
>isn't done in jabber.xml?
> I am trying to parse the configuration file using xerces/xpath and
>those namespace issues are causing trouble - if I fix them jabberd won't
>Any suggestion? Thanks!
>jdev mailing list
>jdev at jabber.org
More information about the JDev