V2.2 and Oracle MessageAttributes...

[Scott Hamilton <sc...@det.nsw.edu.au>]

  I've just downloaded and installed James 2.2.0-a14 the database was
  already using 2.1 so the definition of INBOX was there. So I tried adding
  messageAttributes LONG RAW,  but ofcourse Oracle replied only ONE
  long type column can exist per table.  

  So I'm wondering has anyone actually used 2.2 against Oracle 9i? 

  What I did to resolve the problem was just make it a varchar2(2000)
  but I suspect the data contents may get larger than that... So does
  anyone have a better idea??


  Cheers
      Scott.


**********************************************************************
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

RE: V2.2 and Oracle MessageAttributes...

["Noel J. Bergman" <no...@devtech.com>]

> I've just downloaded and installed James 2.2.0-a14 the database was
> already using 2.1 so the definition of INBOX was there. So I tried
> adding messageAttributes LONG RAW,  but ofcourse Oracle replied only
> ONE long type column can exist per table.

> So I'm wondering has anyone actually used 2.2 against Oracle 9i?

Possibly not.  Vincenzo probably used what was there without realizing that
Oracle is limited.  We don't have a test lab to check each database.
Community testing of builds is important.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org