What version of JBoss are you using?
JBoss (MX MicroKernel) [3.0.1RC1 Date:200206291622]
and JBoss (MX MicroKernel) [3.1.0alpha Date:200208061141] for looking up your source code to find the "bug?".
In both servers this problem happens. I did a workaround in setting the default page-size in the default constructor of the JDBCReadAheadMetaData class, but this could only be a workaround for devoloping our ejbs, not to deploy them.
Many thanks for your help and let me say you did a great job with the cmp!
Should in JDBCReadAheadMetaData the default value not be overwritten if there is a new value in the standardjbosscmp-jdbc.xml default section?
And I tried to use an EJB specific jbosscmp-jdbc.xml with readahead-values for the EJBs, but this doesn' t work either.
The files are read in correctly, I logged the constructor calls in the JDBCReadAheadMetaData class, and every xml is parsed and a new JDBCReadAheadMetaData instance is created.
but for all the findermethods the JDBCQueryMetaDataFactory.createJDBCQueryMetaData(QueryMetaData queryData) method is used and this one uses the
JDBCQlQueryMetaData(QueryMetaData queryMetaData, Method method) constructor which uses JDBCReadAheadMetaData.DEFAULT as readahead value and this one is the fix value in the class and not a value read in from an xml file.
I hope I understood your code right and thanks for your help!
Can you post this in a detailed bug report at sourceforge?
Sure, I will do it right now.