ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Nicholson" <>
Subject RE: WL 6.0 EJBC Ant build
Date Wed, 23 May 2001 03:20:58 GMT
Actually you want to make sure the vm knows about the decarlation and you
haven't given the property a value.

Again please read

public static DocumentBuilderFactory newInstance()
Obtain a new instance of a DocumentBuilderFactory. This static method
creates a new factory instance. This method uses the following ordered
lookup procedure to determine the DocumentBuilderFactory implementation
class to load:
Use the javax.xml.parsers.DocumentBuilderFactory system property.
Use the properties file "lib/" 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.parsers.DocumentBuilderFactory in jars
available to the runtime.
Platform default DocumentBuilderFactory instance.
Once an application has obtained a reference to a DocumentBuilderFactory it
can use the factory to configure and obtain parser instances.

FactoryConfigurationError - if the implementation is not available or cannot
be instantiated.
This says that you have to configure the property to to an implementation.

An example would be


or for crimson this would be


Note if you use the crimson jar the META-INF\services already takes care of
it for you.

The idea is that JAXP lets you plug in XML parsers and in order to do that
with a DOM Builder you have to set that property. One way to do this
is by passing -DX=Y where X is the propertyName and Y is it's value
to the java invocation in build.bat

-----Original Message-----
From: Schmoll, Brett x66244 []
Sent: Tuesday, May 22, 2001 7:46 PM
To: ''
Subject: RE: WL 6.0 EJBC Ant build

Okay, I've looked at the docs for Jaxp and I believe that I understand what
needs to occur but I'm still falling short of the mark. I've added the
following property declaration:
                <property name="javax.xml.parsers.DocumentBuilderFactory">
                              <pathelement location="weblogic.jar"/>
Unfortunately, the build still fails with a "FactoryConfigurationError". I
noticed that both the weblogic.jar and ant\lib\jaxp.jar both implement the
DocumentBuilderFactory. Is this causing the build to fail? If I remove the
ant Jaxp.jar, the build immediately fails.
Any ideas?
-----Original Message-----
From: Robert Nicholson []
Sent: Tuesday, May 22, 2001 1:34 PM
Subject: RE: WL 6.0 EJBC Ant build

This is because you don't have a parser set for the jaxp framework to work.
when you run ant define the property
javax.xml.parsers.DocumentBuilderFactory  to point to the
DocumentBuilderFactory you want to use.
For me go and grab jax1.1 and look at the docs for the
newInstance methodo of DocumentBuilderFactory
-----Original Message-----
From: Schmoll, Brett x66244 []
Sent: Tuesday, May 22, 2001 9:42 AM
Subject: WL 6.0 EJBC Ant build

Does anyone have a working Weblogic 6.0 EJBC task that they could share with
me? I'm able to get the EJBC built from a command prompt but don't seem to
be able to get it to work under Ant. Here is the Taskdef I'm using, am I
missing the obvious?
classname="weblogic.ejbc" >
        <arg path="d:\develop\posse_jvm_4_3_1\temp\header.jar" />  Do you
        <arg path="d:\develop\posse_jvm_4_3_1\temp\header4_3_1.jar" />
I receive a "javax.xml.parsers.FactoryConfigurationError:" when this runs
under Ant. I run what I assume to be the equivalent from a command prompt
and it builds fine. Any help would be greatly appreciated.
Brett Schmoll

View raw message