Actually, there's a setter in MyBean (setProp) but no corresponding "prop"
attribute in the XML. At runtime, the JVM can't find type SomeType, and
it looks like that causes Digester to not ever call setName(). If I
comment out the first 4 lines of the MyBean class (all the
SomeType/setProp stuff
On Mon, 12 Mar 2001, Zach Thompson wrote:
> Hello,
>
> I just spent quite a bit of time debugging some code that uses a
> Digester, and I'd like to share what I found.
>
> class MyBean {
> SomeType p = new SomeType();
> public void setProp(SomeType p) {
> this.p = p;
> }
>
Regarding your first point, are you saying "There's a name attribute in the
XML, but there's no corresponding setter, so the Digester should flag an
error"? If not, I apologise for putting words in your mouth. :-}
One of the nice things about the Digester is that I can tell it which
pieces of
Sorry - I noticed a confusing mistake in my post. I was never actually
calling "new SomeType()" - that's why there was no runtime error.
Zach Thompson wrote:
> Hello,
>
> I just spent quite a bit of time debugging some code that uses a
> Digester, and I'd like to share what I found.
>
> class
Hello,
I just spent quite a bit of time debugging some code that uses a
Digester, and I'd like to share what I found.
class MyBean {
SomeType p = new SomeType();
public void setProp(SomeType p) {
this.p = p;
}
String name;
public void setName(String name) {
S
5 matches
Mail list logo
