correction to the above.
the above happens on attempting to load an instance of the bean, NOT on deployment.
Looks like a bug. Can you post a bug report with a simple test case at souce forge?
Dain- I shall prepare a test case now.
(As a matter of interest this is *really easy* to replicate - all you need to do is add a get and set to your entity bean taking a char type,
public abstract char getCharField();
public abstract void setCharField(char c);
and also to the local interface:
public char getCharField();
public void setCharField(char c);
err.. that's it
you don't even need to map the column in ejb-jar.xml or jbosscmp-jdbc.xml!
then try and load the objects through a findAll()