Seems like there is a bug in PutMethod related to this. Turns out this is related to LOCK before PUT. MS Word calls LOCK before it calls PUT. LockMethod will create a NodeRevisionDescriptor for the lock. When the PutMethod is called, it should normally throw an ObjectNotFoundException when content.retrieve( ) is called and the catch clause will fill in the contentType. Because that lock descriptor is there, content.retrieve( ) gets it and updates it to represent the new file. The try block does not set 'getcontenttype' or 'getcontentlanguage' when updating an old descriptor or even when creating a new one. Seems like the PutMethod needs to be a little more discriminating when retrieving an oldRevisionDescriptor and, in the case where a new one is created, needs to add the 'getcontenttype' and 'getcontentlanguage' properties. What do you think? Marty Martin Gronberg wrote: > Env: Slide 1.0.9, Tomcat 3.2.1, Linux RedHat 6.2 > > Problem: When saving a MSWord document from MSWord | Save As... the > file is stored without the 'getcontenttype' and 'getcontentlanguage' > properties. > > When I save a file using the MSWin2K File Explorer all the properties > are created and saved including the 'getcontenttype' and > 'getcontentlanguage' but not when I save using MSWord. I was looking > at the code and it seems like the PutMethod.executeRequest( ) should > always add these properties to the revisionDescriptor for new > objects. Any ideas as to what could be going on? > > Marty
