If you correctly build it and specify the build was for MSSQL in the torque properties file, then I don't know what's happening. I remember having something like that when trying to read a blob from Oracle.
What's the type of the column under MSSQL ? Is it "BLOB" ? (you can double-check the type with the SQL generated by Torque) If it is, and if you're sure that the psml stored in the binary is ok, could you please try replacing the village jar 1.5.3 by the one currently under CVS (village-2.0-dev-20030625.jar). This one contains a fix for blob columns under Oracle, maybe blob columns under MSSQL where buggy too ? Give it a shot... Who knows ? Another interesting question would be : Did ANYONE ever succesfully deployed jetspeed dbpsml under MSSQL ? Aurelien Sandeep Dixit a �crit : > I am using it from src. > >> Did you build jetspeed from src or did you use the war release ? >> >> Sandeep Dixit a �crit : >> >>> I have jetspeed 1.4 b3, MS SQL 2000 on Windows XP Pro. I have tried >>> replacing BINARY profile fields to IMAGE and TEXT, both created the >>> same error. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
