https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
--- Comment #13 from Javen O'Neal ---
@backwards compatibility: this is backwards compatible with any class using a
logger, but not for classes subclassing POI logger. They will need to change
log to _log and optionally drop the accessibility t
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
Javen O'Neal changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
Nick changed:
What|Removed |Added
Version|3.14-FINAL |unspecified
--- Comment #12 from Nick ---
(In
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
--- Comment #11 from Javen O'Neal ---
I fixed the accidental accessibility elevation from protected to public in the
remaining logging classes in r1761665.
This does not introduce any backwards compatibility issues because log(int,
Object...)
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
--- Comment #10 from Javen O'Neal ---
I think I have fixed this in r1761662. The problem is that the signature of
log(int, Object...) is identical to log(int, Object) or log(int, Object, final
Throwable). We are relying on the visibility of the
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
Nick changed:
What|Removed |Added
Hardware|PC |Other
OS|All
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
--- Comment #8 from Andreas ---
Please consider
- the runtime is Java 8 in a JBoss 6 server environment
- the POILogger class in the DocumentHelper has no public log method (it is
protected) - that leads to an IllegalAccess exception:
priv
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
--- Comment #7 from Andreas ---
You might be right, but in that real case the IllegalAccess error is gone.
The application server run with Java 1.8.0_72 and a JRE runtime error happens -
probably a Oracle bug or a desired behaviour for such ki
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
Dominik Stadler changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #6 from Dominik
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
--- Comment #5 from Andreas ---
Ok, I downloaded the 3.14 source from here:
https://www.apache.org/dyn/closer.lua/poi/release/src/poi-src-3.14.tar.gz
I did a few changes in 2 class files and compiled the source with Java 8, 32
bit.
Fix 1)
T
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
--- Comment #4 from Andreas ---
I tried a bit more debugging and think I found it.
Inspecting the NullLogger object, which is returned in the DocumentHelper
private static POILogger logger =
POILogFactory.getLogger(DocumentHelper.class);
t
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
--- Comment #3 from Nick Burch ---
I added your logger statement to just before the return statement, and re-ran
several of the XSSF unit tests. The logger statement worked just fine
--
You are receiving this mail because:
You are the assigne
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
Andreas changed:
What|Removed |Added
Status|NEEDINFO|NEW
--
You are receiving this mail because:
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
--- Comment #2 from Andreas ---
Ok, you are right, order should be ok.
To keep things simple, put a line before the return statement.
logger.log(POILogger.INFO, "SAX Security Manager setup");
If you see the changed method signature, all s
https://bz.apache.org/bugzilla/show_bug.cgi?id=59933
Nick Burch changed:
What|Removed |Added
OS||All
Status|NEW
15 matches
Mail list logo
