Glassfish + mysql + jsc2 table problems

I'm trying to deploy my app to a glassfish server and having some problems with tables and rowsets.

Situation:

Everything works fine under the development settings on my winxp machine with mysql and the 5.0 beta jdbc driver.

I managed to get jdk1.5 + glassfish + mysql + 5.0jdbc driver installed on my debian system with 2.6.16 kernel.Non-DB test apps deployed by exporting to a j2ee1.4 war file and then importing through the glassfish admin page work fine. DB apps that I've manually added the db access code to in the prerender() section of the page work fine. I can even get tables to work IF I put the code in the prerender section:

publicvoid prerender(){

try{

usersRowSet.setDataSourceName("java:comp/env/jdbc/testcgcbt");

usersRowSet.setCommand("SELECT * FROM users");

usersRowSet.setTableName("users");

usersDataProvider1.setCachedRowSet((javax.sql.rowset.CachedRowSet)getValue("#{Page1.usersRowSet}"));

}catch(Exception e){

error("Error "+e.getMessage());

}

}

But the table displays 'No items found.' with the default db access code in the _init() section:

privatevoid _init()throws Exception{

usersRowSet.setDataSourceName("java:comp/env/jdbc/testcgcbt");

usersRowSet.setCommand("SELECT * FROM users");

usersRowSet.setTableName("users");

usersDataProvider1.setCachedRowSet((javax.sql.rowset.CachedRowSet)getValue("#{Page1.usersRowSet}"));

}

Has anyone run into this before? I don't know if there are some settings in the .xml files to change to make the exported war work properly. I would love to have my app work without having to cut and paste the code into the prerender() sections, I haven't looked through all my pages and I'm not sure that would work for each one.

Thanks in advance.

[2516 byte] By [creonnoir] at [2007-11-26 6:39:40]
# 1

Well, it looks like I've found the problem...

The init() section is not being run when the page is loaded. Once I copied the

try{

_init();

}catch...

section into the start of prerender(), everything worked on both the winxp and debian boxes. Put log code at both the beginning and end of the init() method, neither is being run. I am a little concerned as super.init() is not being called, it doesn't seem to affect the test table app I threw together to check this out but I don't know the long-term effects on my main project. Has anyone else had this problem?

I noticed the jsf-impl.jar lib is put into the war archive, jsf-impl.jar also exists in the glassfish lib directory. Unpacking and reading the manifests of both versions reads: spec 1.1 implementation 2.4.1 for the jsc2 version and spec 1.2 implementation 1.2-b19-FCS for the glassfish version. Could this be part of the problem?

This has been tested on glassfish builds milestone 6(b42) and b44 with the same results.

creonnoir at 2007-7-6 14:51:45 > top of Java-index,Development Tools,Java Tools...