I updated the migration document to remove the comment about getTemp and setTemp not being there any longer. I think that was from some old notes that I had made when I was distracted by the Turbine* objects generated by project-om.
I modified the extend user document to correct the syntax error and coding convension issue that you pointed out. I also added a little more information on using the setPerm/getPerm and setTemp/getTemp methods. Thank you for taking the time to look over the documents. If there is anything else that need corrected or could be explained in more detail, please let me know. -----Original Message----- From: Scott Eade [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 7:50 AM To: turbine-dev Subject: Re: Documentation update > From: "Quinton McCombs" <[EMAIL PROTECTED]> > > I have created some documentation for migrating from 2.1 to 2.2 and > updated the Extend User howto. I was hoping some of you could take a > moment to look over what I have done and comment. I did the docs in > xdoc format. The links below are to the generated HTML version. > Depending on feedback, I will submit the patches and new files to the > dev list in the next week. > > Migration: http://blaze.qdog.org/preview/howto/migration-from-2_1.html While I cannot confirm the accuracy of the content (still trying to find time to look at 2.2) I would query whether or not get/setTemp() are no longer available in T2.2, did you perhaps mean get/setPerm()? Even get/setPerm() appear to still be present, although these may just be the mechanism used to store the concrete columns in the TURBINE_USER table (i.e. the OBJECTDATA column that no longer exists). Looking at turbine-schema.xml the OBJECTDATA column still seems to appear, but TurbineUserPeer.buildCriteria() does not seem to populate it. I leave it to you to check the detail. > > Extend User: > http://blaze.qdog.org/preview/howto/extend-user-howto.html I couldn't look at T2.2 without this, but again I cannot confirm the accuracy of the content until I have time to try it. The document does however make reference to the perm and temp hashtables as well as TURBINE_USER.OBJECTDATA - this does not seem consistent with the migration document. Change the line: catch ( Exception e ) to: catch (Exception e) So that it uses the turbine coding standard. Looks like a capitalisation error in the line below: ExtendedUSer user = (ExtendedUSer) data.getUser(); Your solution seems to rely on using the perm hashtable that is stored in the TURBINE_USER.OBJECTDATA column and yet it retains the old discussion that also provided an option to actually create columns for the new user attributes in the TUEBINE_USER database table. IMHO the perm/OBJECTDATA solution is suboptimal as it is difficult to view the additional user attributes directly with SQL or to access them using other tools or via Criteria. Is the concrete column solution still possible under T2.2? > This is good stuff, but a little more work is required to tidy up the issues I mention above. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com -- 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]>
