Thanks, Alan & Stephane.
I'm a bit surprised at such an quick responses.
Well, I should've introduced myself as a Java newbie.
I fixed my code like the following, and got no compile errors.
NodeImpl testTarget =
(NodeImpl)document.getElementsByTagName("head").item(0);
But, I found something strange.
In DOM2 Events, MutationEvent interface, initMutationEvent(~)
public void initMutationEvent( String typeArg,
boolean canBubbleArg,
boolean cancelableArg,
Node relatedNodeArg,
String prevValueArg,
String newValueArg,
String attrNameArg);
But In Xerces (org.apache.xerces.dom.events.MutationEventImpl),
public void initMutationEvent( String typeArg,
boolean canBubbleArg,
boolean cancelableArg,
Node relatedNodeArg,
String prevValueArg,
String newValueArg,
String attrNameArg
***** short attrChangeArg);
I'm just curious why attrChangeArg parameter is added.
Thanks in advance.
----- Original Message -----
From: "Alan Martin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 22, 2001 12:16 AM
Subject: Re: addEventListener
>
> > I'm xerces newbie so I'm not sure that is correct or not.
>
> So am I, but I know Java. ^_^
>
> > //
> > Node testTarget = document.getElementsByTagName("head").item(0);
> > EventListener TestEventListener = new EventListenerImpl();
> > testTarget.addEventListener( "mutation", TestEventListener, false );
> > //
>
> How about casting to (NodeImpl), addEventListener isn't defined in the
Node
> interface, perhaps its a bug, but thats not your problem. :)
>
> > Please help me, I've never been answered all the question that I posted
> this
> > mailing list. :-(
>
> Yeah but its free, so quit whining. ;)
>
> Voxol
> -Use the source Luke
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
