Start by putting the postgres driver in
server/default/lib and reboot.
Then we can see what is really going on.
Thanks for your quick reply Adrian,
I put the postgresql JAR in the lib directory but I didn't notice any difference in the behaviour. I have attached the serverlog again in case you can spot any difference.
By the way, I have tested a few simple entity bean examples and the link to the database seems to work ok.
Postgres is deploying now,
but jms isn't, you've removed hsqldb
so the persistent manager isn't starting.
For the ClassNotFoundException,
it might be that the bean class uses a class
you haven't deployed?
The error reporting isn't very clear, it just checks
whether it can load the class, it doesn't report
the real error.
You might be able to get more information by
for the EJBDeployer in server/default/conf/jboss-service.xml
You were right. I was missing some other classes which the beans were dependent on. I am past the problems now :)