Yes, I confirm this, too.
Basically, xwork does the same as before - automatically use
GenericsObjectTypeDeterminer if found classpath. But from xwork 2.x on,
this does not make sense any more, since it does not longer depend on
additional tiger jar being deployed to activate Java5 support, an
Hi,
I faced the same problem and found the cause.
Prior to Xwork 2.0.3 the objectTypeDeterminer property in XWorkConverter
was initialised using the instance created by the static block in
ObjectTypeDeterminerFactory. This static block determines which
implementation of the ObjectTypeDetermin
