hi,
 
this is the correct fix for FieldMolder:
 
public FieldMolder( DatingService ds, ClassMolder eMold, FieldMapping fieldMap )
...

    // Second look up the set/add accessor
    if ( fieldMap.getSetMethod() != null ) {
//     Class methodClass = _colClass!=null? _colClass: javaClass;                                    // BRJ
     Class methodClass = _colClass!=null? _colClass: _defaultReflectService._fClass;        // BRJ
     _defaultReflectService._setMethod = findAccessor( javaClass, fieldMap.getSetMethod(), methodClass, false );
     if ( _defaultReflectService._setMethod == null )
      throw new MappingException( "mapping.accessorNotFound",
        fieldMap.getSetMethod(), _defaultReflectService._fClass, javaClass.getName() );
     if ( _defaultReflectService._fClass == null )
      _defaultReflectService._fClass = _defaultReflectService._setMethod.getParameterTypes()[ 0 ];
    }
...
 
i downloaded the cvs-snapshot of nov. 21. This snapshot still has a bug in FieldMolder when using set-method:
 
    <field name="boss" type="boolean" get-method="isBoss" set-method="setBoss"> 
   <sql name="isBoss" type="char[ft]"/>
    </field>
 

Reply via email to