Hi Daniel,
> > DS> This seems to be the first problem with the changed
> > DS> look_if_table_already_exists code in the JDBCInitCommand.
> >
> > This error is not very new, the bean works with this error, sorry that
> > was not clear. But the stacktrace is printed for every bean and blows up
> > the log. Is it a problem with the german driver ?
>
> Since every bean has its own table and all tables are maintained by the
> same driver, of course this error happens for every bean.
>
> It is a driver problem. The code we use is 100% spec compatible - some
> jdbc drivers obviously not.
>
> > DS> The InitCommand askes the driver (DatabaseMetaData) if the table it
> > DS> wants to create exists or not. The driver says not but obviously it
> > DS> _does_ exist.
> >
> > DS> Which driver do you use?
> > DS> Aaron, if you read that - is the driver Ingo uses a one we have to
take
> > DS> care of?
> >
> > I am not sure, 8.1.6 or 8.1.7.
>
> I do really have _NO_ experience with Oracle!
> So I dont know if the driver you are using is a good choice. If you have
> the possibility to try an alternative driver, do it!
I have looked at oracle homepage and compared the drivers with the one i
use. I am using the jdbc thin driver Version 8.1.7. This should be an
international driver. Because I have read that only this driver works right
with the new XADataSource I think it is the right driver.
But that is not the problem. The driver works, the beans works, all seems to
be fine :-) But the stacktrace if a table exists is not good for the eyes at
startup from jboss.
CU
---
Ingo Bruell
OBL GmbH ([EMAIL PROTECTED])
Hude (Oldenburg)
Germany
