ok thanks. I will probably move my data to a mysql db or and then do the changes. (The work I did back then on Microsoft SQL migration was only for evaluation) Thanks for the list it will be very helpful for the migration process. Once I can start it budgetwise.
Btw. another question, I�m currently looking for a decent OR mapper. I found Hibernate which seems to be excellent (I think the best solution so far functionalitywise and is maintained really well, most users rave about it, almost everyday on the sourceforge top 10 list) but since it uses a load of Apache libaries it might be hard to merge it with jetspeed and other high level projects like Axis due to possible library conflicts. The second option would be Torque thanks to its close binding to the Jetspeed project. Has anyone used it extensively, how does it perform? How is it bugwise and where are the problems? I guess you, David, might be the person who knows most about the thing since you used it extensively in Jetspeed. Btw. a short off topic note: A quick recompilation against Jetspeed b1 and having to replace one or two older apache jars with newer versions (I think the commons were a little bit problematic) revealed that at least a compile against Jetspeed b1s needed libraries was possible. I haven�t had a look if it runs, but since it uses so many apache libraries, merging Hibernate inte Jetspeed is like asking for sure trouble in the long term. Both projects very high level on the libaries and both projects use the jakarta base extensively. (Same goes basically for Axis but since both projects are jakarta projects you can at least expect to be around the same library version level vor the core jakarta libs so that a merge is not that problematic) Anyway I see a jar file hell on the horizon :-( time for Sun to think about a versioning mechanism in the long term. The jar file hell sure will break loose once more and more jakarta libs go into the core JDK, we have the first signs of that already here with users having problems with various Xerces versions (and one being in the core JDK since 1.4) -----Urspr�ngliche Nachricht----- Von: David Sean Taylor [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 11. Dezember 2002 20:30 An: Jetspeed Users List Betreff: RE: Moving from b1 to b2 > -----Original Message----- > From: Werner Punz [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 11, 2002 8:45 AM > To: [EMAIL PROTECTED] > Subject: Moving from b1 to b2 > > > Hi has anyone already successfully moved an existing project from b1 to > b2? > There are three issues that I know of. 1. new column on TURBINE_USER table: PASSWORD_CHANGED TIMESTAMP 2. Torque upgrade. See http://jakarta.apache.org/jetspeed/site/supporting-projects.html 3. if you're using the Hypersonic SQL db, the primary key id columns have been changed to auto-increment -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
