[jdev] Archive - receive callback archival

Siracusa, David siracusa at sig.com
Wed Jun 9 10:47:24 CDT 2004


1. I need to persist the archive messages in a database.  I can't save
off the whole XML in a blob.  I could really use the maximum (or likely)
sizes encountered in the archive xml route (receive) callback in order
to setup/correct the schema.

My predecessor defined the following:
	route -> direction  		- 	varchar2(16 byte)
not null,
	route -> timestamp   	-	date                    not
	route -> to          	-	varchar2(1024 byte)     not
	route -> type        	-	varchar2(64 byte)       not
	message -> id         	-	varchar2(64 byte)       not
	message -> from        	-	varchar2(1024 byte)     not
	message -> to          	-	varchar2(1024 byte)     not
	message -> type        	- 	varchar2(64 byte)       not
	message -> xmlns       	-	varchar2(1024 byte),
	message -> subject     	-	varchar2(1024 byte),
	message -> thread      	-	varchar2(1024 byte),
	message -> body        	-	varchar2(4000 byte),
	message -> error       	-	varchar2(1024 byte),
	message -> error_code  	-	number(9),

I found
df which helps some.

Some columns seem too big while others too small.  For example I can
send body text greater than 4k from client to client.

Dave Siracusa


A sample xml route transcript looks like:
		to='archive at archive.company.com' 
			from='siracusa at jabber.company.com/Desktop' 
			to='user at jabber.company.com' type='chat' 
			<body>Body Text</body>
			<subject>Message# 1</subject>

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments.  Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited.  Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument.  Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.

More information about the JDev mailing list