When I step into the

dbFactory.setFeature(ENTITY_RESOLVER_2_ID, true);

function call, I go to a function in DocumentBuilderFactoryImpl.java that
looks like this:

 

    public  void setFeature(String name, boolean value)

    throws ParserConfigurationException{

        

        //Revisit::

        //for now use attributes itself. we just support on feature.

        //If we need to use setFeature in full fledge we should

        //document what is supported by setAttribute

        //and what is by setFeature.

        //user should not use setAttribute("xyz",Boolean.TRUE)

        //instead of setFeature("xyz",true);

        if(attributes == null)

            attributes = new Hashtable();

        if(name.equals(Constants.FEATURE_SECURE_PROCESSING)){

 
attributes.put(Constants.FEATURE_SECURE_PROCESSING,Boolean.valueOf(value));

        } else throw new ParserConfigurationException(

        DOMMessageFormatter.formatMessage(DOMMessageFormatter.DOM_DOMAIN,

        "jaxp_feature_not_supported",

        new Object[] {name}));    

    }

 

This file is in JDK 1.5 in the package
com.sun.org.apache.xerces.internal.jaxp, but it is defined in a jar file
called rt.jar. I downloaded a copy of Xerces-J-tools.2.9.0 and added
xercesImpl.jar to my classpath. Now when I get to the setFeature function
call, I get an error that says

Exception in thread "main" java.lang.AbstractMethodError:
javax.xml.parsers.DocumentBuilderFactory.setFeature(Ljava/lang/String;Z)V

It does look like the version of DocumentBuilderFactoryImpl does not contain
a definition for setFeature and DcoumentBuilderFactory is an abstract class,
so I guess this all makes sense. Did you encounter things like this when you
were setting things up?

Mike

 

  _____  

From: Will Holcomb [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 26, 2007 10:06 AM
To: j-users@xerces.apache.org
Subject: Re: Specifying a DTD file when parsing XML files that don't contain
!DOCTYPE lines

 

Are you using the default jdk parser? I don't really know if there is some
commonly accepted method for doing it, but I have this in my ant build.xml:

<jar destfile="dist/templ-0.1.jar" basedir="build"> 
  <zipfileset src="lib/log4j-1.2.13.jar"/>
  <zipfileset src="lib/xercesImpl.jar"/>
  <manifest>
    <attribute name="Built-By" value="${ user.name <http://user.name> }"/>
    <attribute name="Main-Class" value="org.himinbi.templ.HooksProcessor"/>
  </manifest>
</jar>

This sticks the xerces classes in the jar with my classes. I think though
that you can just include xercesImpl.jar in the classpath. (I started this a
week ago and am still learning myself.)

On 2/25/07, Mike O'Leary < <mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED]> wrote:

When I try this, I get an error that says:

javax.xml.parsers.ParserConfigurationException: jaxp_feature_not_supported:
Feature "http://xml.org/sax/features/use-entity-resolver2 " is not
supported.

What am I doing wrong?

Mike

Reply via email to