Workflow Persistence Problems

I created the example EAR and WAR file from HEAD and they both worked in
JBoss 3.0 with one minor change: had to add osuser.jar to the library
directory since it was not listed as an EAR module and the lib directory
within the EAR is not seen by the classloader.  I want to store the data
in Oracle and the easiest path seemed to be to change the datasource
settings of the jboss sub-task of the ejbdoclet task of the build
script. I hit a sour chord when trying this because OS_USER, OS_GROUP
and OS_MEMBERSHIP are OSUser tables. I assumed I could just rebuild
OSUser but they do not use XDoclet and so we cannot simply change the
datasource in the build script. That would have been nice and we would
have had a pure EJB implementation. I would also point out the HOW-TO in
the README files reference files that do not exist anymore: they ask
that you update osuser.xml in the expanded WAR file for JDBC
persistence. 
 
Are there plans to convert OSUser to use XDoclet and EJBs? In the
meantime can we just update the OS_USER, OS_GROUP and OS_MEMBERSHIP
tables "by hand" or does OSWorkflow have other ropes into OSUser?
Basically my requirements are to use Oracle and JBoss so what is the
simplest strategy in getting there from here? 
 
TIA, 
 
Rod