Thanks for your patch. I have some questions though...
I'm looking at sqlResources.xml, and I see you changed the createTable
procedure, but didn't use the db="sapdb". Something like this should work
as the JDBC driver will clue sql resources into knowing that the db is
"sapdb", and thus use this overridden createTable sql...
<sql name="createTable" db="sapdb">
CREATE TABLE ${table} (
message_name varchar (200) NOT NULL,
repository_name varchar (200) NOT NULL,
message_state varchar (30) NOT NULL ,
error_message varchar (200) NULL ,
sender varchar (200) NULL ,
recipients long NOT NULL ,
remote_host varchar (100) NOT NULL ,
remote_addr varchar (20) NOT NULL ,
message_body long NOT NULL ,
last_updated date NOT NULL,
PRIMARY KEY (message_name, repository_name)
)
</sql>
Does that look correct for the SAPDB?
Also, what about this in JDBCMailStore...
//insertMessage.setBytes(10, headerOut.toByteArray());
insertMessage.setString(10, headerOut.toString());
Is there a reason you did toString instead of toByteArray? I'm not sure how
we could support that with the way the code is designed. And in
MimeMessageJDBCSource you retrieve the header as a String. Does the SAPDB
JDBC driver not support binary data?
I'd like to integrate the code, but our design can't currently incorporate
the String <-> byte[] difference.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
----- Original Message -----
From: "Samuel Franklyn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 04, 2001 8:46 AM
Subject: James with SAPDB
> After several hour of effort I managed to get
> the latest james from CVS to use SAPDB as
> its message store. I have to patch 2 files of James
> and change the config file.
>
> Here is my config and my patch.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
