Column type mismatch when after adding a findAll() custom finder

[Skye Roseboom]

I am working with a CMP entity bean. I have mapped the oracle table's key, a Number(10,0), to java.math.BigDecimal. The only other cmp managed field is a oracle varchar2 that I have mapped to a java.lang.String. Before adding any custom finder, I can use the findByPrimaryKey home method perfectly. But when I add a custom finder method to find all entries in the table, I get a type mismatch error when I attempt to generate the deploy code. This error only happens if I add a custom finder. If I then remove the custom finder the bean will deploy perfectly again. The type mismatch error is pointing to the java.lang.String mapping to the varchar2. Also I dont have any transformation set for that mapping.
Can anyone shed some light on this problem? Thanks!
skye

[Prasad Thirugnanam]

hi, try creating the EJB from schema (VAJ) and find out what data type is mapped to varchar2. then create ejb and test it. i hope this could help u.
rgds,
Prasad

[Skye Roseboom]

I am using the demo version of WSAD. I dont have VAJ but if I let WSAD do the mapping it will choose java.lang.String to map varchar2 database fields to. Does anyone know if the demo version of WSAD perhaps does not support custom finders?