The output is as follows:
in A.<init> intA=42 strA=42
in A.config intA=42 strA=42
in B.config intB=41 strB=41
in B.<init> intB=0 strB=41
finally, intA=42, strA=42
As email@example.com pointed out already:
> calling a virtual config from a ctor seems a bit strange, but it seems to work in java. it may be a boxing issue. decompiling B.class, the ctor has:
> Integer integer = new Integer(0);
> intB = DefaultTypeTransformation.intUnbox(integer);
> in it after the call to super.
So I would state this as a bug. Rather major in my opinion, either.