https://issues.apache.org/bugzilla/show_bug.cgi?id=48493
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution| |FIXED --- Comment #2 from [email protected] 2010-01-13 11:30:26 UTC --- This bug turned out *not* to be a problem with POI, but with a feature of running the web application using WebLogic Server. The XSSF POI api uses classes contained in the xmlbeans jar file. I *did* have a reference to the (correct) xmlbeans jar file as an “external jar file” referenced in my Weblogic project. But behind the scenes Weblogic Server uses some Weblogic-specific jar files that it searches first during execution. One of those WebLogic-specific jar files includes the same packages that are in the xmlbeans jar file. This produced the reported error results when the application was run. Once I was aware of that problem I achieved error-free execution by adding the correct xmlbeans jar file to the very beginning of the classpath used to run WebLogic Server. For me that jar file is xmlbeans-2.3.0.jar. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
