Re: [Exist-development] Unexpected Stax dependency....

[Dannes W. <da...@ex...>]

On Sat, Feb 13, 2010 at 2:08 PM, Dmitriy Shabanov <sha...@gm...>wrote:

> On Sat, 2010-02-13 at 12:08 +0100, Dannes Wessels wrote:
> >
> > It is about code not committed into trunk
>
> What do you have here?
>
>
This is the failing code:

XMLOutputFactory outputFactory = XMLOutputFactory.newInstance()

from the javadoc:

*This method uses the following ordered lookup procedure to determine the
XMLOutputFactory implementation class to load: Use the
javax.xml.stream.XMLOutputFactory system property.

Use the properties file "lib/stax.properties" in the JRE directory. This
configuration file is in standard java.util.Properties format and contains
the fully qualified name of the implementation class with the key being the
system property defined above.

Use the Services API (as detailed in the JAR specification), if available,
to determine the classname. The Services API will look for a classname in
the file META-INF/services/javax.xml.stream.XMLOutputFactory in jars
available to the runtime.

Platform default XMLOutputFactory instance. Once an application has obtained
a reference to a XMLOutputFactory it can use the factory to configure and
obtain stream instances. *

regards

Dannes


-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624