Hia, The checked-in property is 'protected'. I believe that the versioning spec mandates that protected properties must be fetched explicitly. That means, for example, that these properties shouldn't be sent on wildcard reports like the 'allprop report'.
Best regards, Miguel ___ Hi Kiran, Thanks. I didn't see that property when I ran "propgetall" on the file from the CLI client. Is this property just not listed by propgetall? Thanks, Warwick > -----Original Message----- > From: Kiran Patchigolla [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 15, 2004 1:37 PM > To: 'Slide Users Mailing List' > Subject: RE: Finding the history uri of latest rev? > > > The checked-in property will have the latest revision uri. > > -----Original Message----- > From: Warwick Burrows [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 15, 2004 11:25 AM > To: '[EMAIL PROTECTED]' > Subject: Finding the history uri of latest rev? > > Hi, > > Is there a way to fetch the history URI of the latest rev? > Is the latest rev stored in a property somewhere? I was using > the reportMethod() and taking the first entry in the > Enumeration but when I added an 8th version the enumeration > was no longer in order eg. the list now comes back as: > > /slide/history/1/h5/1.7 > /slide/history/1/h5/1.6 > /slide/history/1/h5/1.5 > /slide/history/1/h5/1.4 > /slide/history/1/h5/1.3 > /slide/history/1/h5/1.2 > /slide/history/1/h5/1.1 > /slide/history/1/h5/1.0 > /slide/history/1/h5/1.8 > > With the latest in the last position - not first. I thought > about sorting the uris but this doesn't work when you > consider version 1.2 and version 1.10 which don't sort in the > right order with a string comparison. > > Thanks, > Warwick > > > > ************************************************************** > ********** > > If you have received this e-mail in error, please delete it > and notify the sender as soon as possible. The contents of > this e-mail may be confidential and the unauthorized use, > copying, or dissemination of it and any attachments to it, is > prohibited. > > Internet communications are not secure and Hyperion does not, > therefore, accept legal responsibility for the contents of > this message nor for any damage caused by viruses. The views > expressed here do not necessarily represent those of Hyperion. > > For more information about Hyperion, please visit our Web > site at www.hyperion.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
