I have an Oracle 8.1.7 database. It supports longer table names (longer, anyway, than Oracle used to be happy with, if I remember rightly). The JDBC driver also is happy with longer table names (I use it in Eclipse and everything works fine).
When I try it in JBoss, however, JBoss mangles the names of the databases horribly in realizing EJB-QL when the combined schema.tablename is longer than about 30 (I haven't established the absolute limit yet).
First, why does it do that? If the JDBC driver and Oracle are happy, why should JBoss intrude upon their bliss?
Second, what can I do about it? Can someone point me to a class where I can start poking around and create my own patch for this issue? Is this of interest to anyone else, that I might submit it once done?
I have tested this issue now with various versions of JBoss up to 3.2.1. All act the same. Any ideas?