Re: [xwiki-users] upgrade fails..

Thanks Sergiu.. Yea forgot mysql connector.. but that was only part of it. Xwiki-3.0 would not start with the balsamiq mockups jar.. I had to remove it and its configuration mods then tomcat started right up. I'm up and running on 3.0 now .. but some wierdness.. I'm not seeing the Administration page as is displayed in the release notes section.. I can see Administration but there is no structure to it... (No CSS)

just a single column, something like this.. o Configuration o Edit Mode Settings o Localization o Email ..... Not very pretty :-) functional yes but not pretty. What page got botched during the xar import? Is it safe to import the 3.0 xar again over top? ------ thanks kevin.foote On Sat, 16 Apr 2011, Sergiu Dumitriu wrote: -> On 04/15/2011 10:06 PM, Kevin P. Foote wrote: -> > -> > Hi all just no getting around to upgrading xwiki.. This is my first -> > attempt at an xwiki upgrade.. Not a pretty outcome :-( -> > stack below -> > -> > I've copied over my xwiki.cfg, xwiki.properties, and hibernate.cfg.xml -> > from my 2.7.1 xwiki instance. -> -> Did you also copy the database connector jar? -> -> > I verified xwiki.store.migration=1 is set is there any other hibernate -> > things I need to uncomment? I cant see anything in the release notes -> > that I should have done different.. -> > -> -> > SEVERE: Exception loading sessions from persistent storage -> > java.io.InvalidClassException: com.xpn.xwiki.objects.BaseElement; local -> > class incompatible: stream classdesc serialVersionUID = -> > 7375085244707397057, local class serialVersionUID = 8286109986904027210 -> -> This shouldn't affect the startup. It just means that Tomcat tried to -> save the existing user sessions and restore them at startup, but the old -> sessions are not compatible with the new classes. You could try to -> remove the saved sessions, but that really shouldn't cause the -> application to stop working. -> -> -- -> Sergiu Dumitriu -> http://purl.org/net/sergiu/