hasAttributes() not implemented: Error compiling

[Carlos Villegas <ca...@uniscope.co.jp>]

Hi,

I got the latest fop 0.14, xalan 1.1 and xerces 1.1.3. Tried
to compile with jdk 1.2.2 (Linux) and I get lots of errors in the 
svg package like the following:

xml-fop/build/src/org/apache/fop/dom/svg/SVGSwitchElementImpl.java:59:
class org.apache.fop.dom.svg.SVGSwitchElementImpl must be declared
abstract. It does not define boolean hasAttributes() from class
org.apache.fop.dom.svg.GraphicElement.
    [javac] public class SVGSwitchElementImpl extends GraphicElement
implements SVGSwitchElement {

I noticed that the class ElementImpl in
org/apache/fop/dom/svg/SVGElementImpl.java
doesn't implement the method boolean hasAttributes() from interface
org.w3c.dom.Node. I noticed also that this method was introduced in
DOM level 2 and that xerces now implements DOM level 2. In other
words I'm guessing an old version of xerces will work. Is that so
or I'm missing something in the build instructions? Maybe my
CLASSPATH is wrong?

Cheers,

Carlos Villegas
Uniscope, Inc.

Re: hasAttributes() not implemented: Error compiling

[Arved Sandstrom <Ar...@chebucto.ns.ca>]

At 02:53 PM 8/19/00 +0900, Carlos Villegas wrote:
>Hi,
>
>I got the latest fop 0.14, xalan 1.1 and xerces 1.1.3. Tried
>to compile with jdk 1.2.2 (Linux) and I get lots of errors in the 
>svg package like the following:
>
>xml-fop/build/src/org/apache/fop/dom/svg/SVGSwitchElementImpl.java:59:
>class org.apache.fop.dom.svg.SVGSwitchElementImpl must be declared
>abstract. It does not define boolean hasAttributes() from class
>org.apache.fop.dom.svg.GraphicElement.
>    [javac] public class SVGSwitchElementImpl extends GraphicElement
>implements SVGSwitchElement {
>
>I noticed that the class ElementImpl in
>org/apache/fop/dom/svg/SVGElementImpl.java
>doesn't implement the method boolean hasAttributes() from interface
>org.w3c.dom.Node. I noticed also that this method was introduced in
>DOM level 2 and that xerces now implements DOM level 2. In other
>words I'm guessing an old version of xerces will work. Is that so
>or I'm missing something in the build instructions? Maybe my
>CLASSPATH is wrong?
>
>Cheers,
>
>Carlos Villegas
>Uniscope, Inc.

Xerces and Xalan are moving pretty quickly and, combined with FOP moving to 
SAX2, we have had some configuration control problems. In future we'll lock 
down Xerces/Xalan versions a few weeks before a release, and document that.

For now I'd suggest trying an older Xerces. After all, all of the releases 
do compile on _some_ version. :-)

Arved

Senior Developer
e-plicity.com (www.e-plicity.com)
Halifax, Nova Scotia
"B2B Wireless in Canada's Ocean Playground"