Community
Participate
Working Groups
I hate to open so many "blockers", but it appears that fileBufferManager. createEmptyDocument simply does not work for either project locations or absolute file locations. I *think* I'm reading the doc's correctly that you should be able to create a document, even though the resource doesn't exist yet. We certainly have the need to do this ... to create documents, some of them may be eventually saved as resource, but some are intentionally transient. The reason this is so critical is that we need to be able to take advantage of content type registration for DocumentFactories and create empty documents without knowing ahead of time which factories to call. This bug is not dependent on content types, though. I'll attach test case that shows failure for simple non-exising text "file".
Created attachment 11310 [details] patch file adding test case showing above failure
Nevermind ... I see my error in this test case was the 'connect' ... I guess you are not suppose to connect to a file location that does not exist. I had assumed it would sort of "reserve" an empty file buffer, but I'm guessing current design is workable. Sorry for churn. [You're still welcome to the test case, without the "connect" :) ]
