You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@poi.apache.org by "Kimmo R. M. Hovi" <ki...@kronodoc.com> on 2006/12/18 13:15:11 UTC
3.0 alpha 3 changelog?
Is the 3.0 alpha3 changelog available somewhere?
We had a "slight" problem with alpha2: Our app, a simply hpsf thingy updating
existing custom properties (Custom properties in the File -> Properties -> Custom
sense, not the CustomProperties sense), every time we ran our app, somehow
the files lost something;
The docfiles in question had MicroSoft FormsObjects, and embedded OLE objects,
that were (surprisingly) tied to macros. After the hpsf app was done, the objects
were dead.
The problem disappeared with alpha3...
I'm just curious if this fix was intentional
--
Kimmo R. M. Hovi | Sinikalliontie 10 | Tel +358 9 229 171
Product Development Manager | 02630 Espoo | GSM +358 40 767 8610
Kronodoc Oy, www.kronodoc.com | Finland | Fax +358 9 348 9036
---------------------------------------------------------------------
To unsubscribe, e-mail: poi-user-unsubscribe@jakarta.apache.org
Mailing List: http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta Poi Project: http://jakarta.apache.org/poi/
Re[2]: 3.0 alpha 3 changelog?
Posted by "Kimmo R. M. Hovi" <ki...@kronodoc.com>.
On Mon, 18 Dec 2006, Yegor Kozlov wrote:
> KRMH> Was this a byproduct of the VBA entry reordering, or is this still present?
> KRMH> (I haven't been able to reproduce the missing macro issue with alpha3)
> It did wrote macros but in the wrong order. As the result Excel or
> Word didn't find the modules in the VBA editor. I guess you got
> "File not found" message when opened such "bad" files passed through alpha 2.
> The point is that the rules for ordering VBA entries are VERY strange
> and unlogical. I'm not 100% sure that the fix covers 100% of cases.
If we did get such errors, they were at least not visible. This issue was
reported by a customer of ours, who I think have a whole department of people
just writing more and more complicated Office files (The test files I had
had at most 400+ macros).
The problem was simply that without any apparent error messages, the Objects
lost their macro connections and went dead. One user reported that he'd managed
to fix some objects by right-clicking them and converting them to FormsObject 2.0
again..
Anyway now using POI 3.0 alpha3, all of the test files were processed
succesfully (Unfortunately, I can't release them to the community as test cases)
Keep up the good work!
--
Kimmo R. M. Hovi | Sinikalliontie 10 | Tel +358 9 229 171
Product Development Manager | 02630 Espoo | GSM +358 40 767 8610
Kronodoc Oy, www.kronodoc.com | Finland | Fax +358 9 348 9036
---------------------------------------------------------------------
To unsubscribe, e-mail: poi-user-unsubscribe@jakarta.apache.org
Mailing List: http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta Poi Project: http://jakarta.apache.org/poi/
Re[2]: 3.0 alpha 3 changelog?
Posted by Yegor Kozlov <ye...@dinom.ru>.
KRMH> Was this a byproduct of the VBA entry reordering, or is this still present?
KRMH> (I haven't been able to reproduce the missing macro issue with alpha3)
It did wrote macros but in the wrong order. As the result Excel or
Word didn't find the modules in the VBA editor. I guess you got
"File not found" message when opened such "bad" files passed through alpha 2.
The point is that the rules for ordering VBA entries are VERY strange
and unlogical. I'm not 100% sure that the fix covers 100% of cases.
Anyway, I'm happy to hear that the fix works and re-saving office
files with VBA doesn't cause problems anymore.
Regards,
Yegor
---------------------------------------------------------------------
To unsubscribe, e-mail: poi-user-unsubscribe@jakarta.apache.org
Mailing List: http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta Poi Project: http://jakarta.apache.org/poi/
Re: 3.0 alpha 3 changelog?
Posted by "Kimmo R. M. Hovi" <ki...@kronodoc.com>.
On Mon, 18 Dec 2006, Yegor Kozlov wrote:
> POIFS changed the order of VBA entries in the internal file system and
> it could lead to errors.
> The fix came right before the alpha 3 release. It's global, i.e. it
> applies to all POI sub-projects - HSSF, HPSF, HSLF, etc.
Thanks. Also noticed that the alpha2 release (seemingly randomly) did not
write certain (empty) macros at all (Doing a "Tools -> Macro -> Macros -> Edit"
to get to macro editor, and "File -> Export" to get the cls file revealed this),
which is what pointed us towards POI in our debugging..
Was this a byproduct of the VBA entry reordering, or is this still present?
(I haven't been able to reproduce the missing macro issue with alpha3)
--
Kimmo R. M. Hovi | Sinikalliontie 10 | Tel +358 9 229 171
Product Development Manager | 02630 Espoo | GSM +358 40 767 8610
Kronodoc Oy, www.kronodoc.com | Finland | Fax +358 9 348 9036
---------------------------------------------------------------------
To unsubscribe, e-mail: poi-user-unsubscribe@jakarta.apache.org
Mailing List: http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta Poi Project: http://jakarta.apache.org/poi/
Re: 3.0 alpha 3 changelog?
Posted by Yegor Kozlov <ye...@dinom.ru>.
Hi,
POIFS changed the order of VBA entries in the internal file system and
it could lead to errors.
The fix came right before the alpha 3 release. It's global, i.e. it
applies to all POI sub-projects - HSSF, HPSF, HSLF, etc.
See more at http://issues.apache.org/bugzilla/show_bug.cgi?id=39234
Yegor
KRMH> Is the 3.0 alpha3 changelog available somewhere?
KRMH> We had a "slight" problem with alpha2: Our app, a simply hpsf thingy updating
KRMH> existing custom properties (Custom properties in the File -> Properties -> Custom
KRMH> sense, not the CustomProperties sense), every time we ran our app, somehow
KRMH> the files lost something;
KRMH> The docfiles in question had MicroSoft FormsObjects, and embedded OLE objects,
KRMH> that were (surprisingly) tied to macros. After the hpsf app was done, the objects
KRMH> were dead.
KRMH> The problem disappeared with alpha3...
KRMH> I'm just curious if this fix was intentional
---------------------------------------------------------------------
To unsubscribe, e-mail: poi-user-unsubscribe@jakarta.apache.org
Mailing List: http://jakarta.apache.org/site/mail2.html#poi
The Apache Jakarta Poi Project: http://jakarta.apache.org/poi/