The schema is normally implicit when logging in as an oracle user
so it is surprising that a schema name is required in middlegen but it is
definitely required. The problem is that when you deploy under JBoss
the schema qualifier causes a failure. I solved this by filtering
jbosscmp-jdbc.xml to remove the schema prefix on table-name elements and that
worked fine. So you need the schema to generate the code but you have to filter
it out before you deploy to JBoss. That seems to be the situation with
oracle/jboss at least. Sounds like a possible JBoss error?
-----Original Message-----
From: Aslak Hellesøy [mailto:[EMAIL PROTECTED]] Sent: Tue 12/3/2002 3:32 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: Subject: RE: [Middlegen-user] mssql 2000 jdbc driver
|
Title: RE: [Middlegen-user] mssql 2000 jdbc driver
- [Middlegen-user] mssql 2000 jdbc driver [EMAIL PROTECTED]
- RE: [Middlegen-user] mssql 2000 jdbc driver Aslak Hellesøy
- Re: [Middlegen-user] mssql 2000 jdbc driver Kristoffer Moe
- RE: [Middlegen-user] mssql 2000 jdbc driver Rod Macpherson
- RE: [Middlegen-user] mssql 2000 jdbc driver Hal Deadman
- RE: [Middlegen-user] mssql 2000 jdbc driver Aslak Hellesøy
- RE: [Middlegen-user] mssql 2000 jdbc driv... Aslak Hellesøy