• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

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

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?
 
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic