I would assume that we do NOT want to set this if the attribute does not
exist. I will work on the update.
Scott Sanders
----- Original Message -----
From: "Jason van Zyl" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 21, 2001 4:56 PM
Subject: [digester] attribute bug
> Hi Craig,
>
> I put another version of digester-tester up at
>
> http://www.apache.org/~jvanzyl/digester-tester.tgz
>
> I am not sure if what I have found is desired behaviour or a bug.
>
> When I have an object that has an attribute with a default value:
>
> String buildFile = "build.xml";
>
> If I have the following rule:
>
> addMethodCall("a/b", "setBuildFile", 1);
> addCallParam("a/b", 0, "buildfile");
>
> and something like the following
>
> <a>
> <b attrA1="attrA1"/>
> </a>
>
> where there is *no* attribute named "buildfile" in the block I'm
> processing the value of buildFile in my object is set to null. I would
> assume that if the attribute is not present the method would not be
called.
> Again I don't know if this is a bug or desired behaviour. There is an
> example in the hacky digester-tester.
>
> --
>
> jvz.
>
> Jason van Zyl
>
> http://tambora.zenplex.org
> http://jakarta.apache.org/turbine
> http://jakarta.apache.org/velocity
> http://jakarta.apache.org/alexandria
> http://jakarta.apache.org/commons
>
>
>
