What's the issue? If you create the primary key via a trigger, that just makes your descriptors easier since you don't put in the autocreation stuff.
Other than that, you just have to specifiy which field is the primary key, and it's type.
Oh, and if the issue is how do you INSERT, just make sure you use a 'null' as the primary field value.
This won't until Oracle releases a JDBC 3.0 driver, and you upgrade to JDK 1.4, which is required for JDBC 3.0.
In a future release, 3.0 final or 3.1, I will add support for "unknown primary key" (see spec), and you will be able to hook this up to a sequence. This is not exactally what you are doing because the value would be filled in by the app server and not the db (from a trigger).
Will that require a JDBC 3 driver?
MySQL doesn't have one yet.
Or will it be a wrapper around JDBC 1/2 drivers?
The stuff I'm going to write will support 1/2 drivers.
In the meantime it will be a good idea to deploy the varia/autonumber EJBs in the default installation of JBoss 3.0.0
The varia build doesn't include a xml deployment descriptor for autonumber, just the entity beans. No session bean either.
I think is a good idea to provide that kind of service in the default installation... until JBoss supports a generic and database independant way to use sequence/autonumber/identity columns.