Ported my PSML DB to Microsoft SQL and found a possible bug+otherstuff (Soap related)

[Werner Punz]

Hi, I just ported my jetspeed database into a Microsoft SQL Server
and I found a possible bug regarding
the database drivers.

I had a problem to integrate a custom Microsoft SQL JDBC driver
into the system. There seemed to be now way to integrate
a custom driver cleanly.

I had to alter the DBFactory class of Torque and had to add my driver
to the default list to get it up and running.

Did I miss something there or is there really no way to add
a different driver than to alter DBFactory?

(System:Jetspeed 1.4b1 on Tomcat 4.1)

Another thing was that the sql scripts generated from Torque were a little bit buggy, I don�t know if I had a config problem there,
or if the Torque SQL generator is a little bit buggy towards M$SQL.


...

Another thing a few days ago I posted my Jetspeed+Axis Integration
Web XML and a bunch of added comments in the Jetspeed+Soap thread.
There have been a few people interested, but after posting
it I never got an answer. Are the people in this list still interested in that stuff? Does anyone have problems to merge Axis and Soap?






--
To unsubscribe, e-mail: <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:jetspeed-user-help@;jakarta.apache.org>