DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43247>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43247 ------- Additional Comments From [EMAIL PROTECTED] 2007-09-08 22:51 ------- I'll see if I can get some time to make unit tests for those. I'm not sure if I actually implemented setters so in theory I would only need to check that the getters return the expected values. Only problem is that I'm currently stuck working on something more important (I do all this stuff during office hours, so I can't easily choose to work on unit testing something we don't use ourselves. Since we only actually ended up using the method to get all the objects...) As for the other suggestions... (1) I'm pretty sure you're right about the IDs, since the IDs are small numbers and there is no other obvious way for them to be referenced. The OLE properties are inside the storage itself so any API that goes as far as to allow access to them would need to load the whole filesystem from there. (2) Hmm... might not be a bad idea. I was just following the code done for pictures for this stuff, but in the event where the same object is embedded twice (I'm sure it must be possible since they're referenced by ID) this would allow us to see where they are and eventually render them perhaps. Although with regards to rendering, what I have found is that in the document there is also an EMF snapshop of the OLE object embedded as an ordinary picture. So it may be that it already renders properly if anyone has written a renderer... (3) Yep. Passing that InputStream straight into a POIFSFileSystem results in a working filesystem, which can then be passed into whatever constructor is needed (although what we're doing is writing it to a temporary location first, so that we can potentially read from it multiple times without having to re-get the input stream.) However what I have noticed is that in some cases, saving the InputStream to a file doesn't allow the file to be opened in the actual Office application, even if POI's classes have no problems accessing the contents. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
