[Bug 61991] Simple instantiation of XWPFDocument causes reflection warning and method not found exception
https://bz.apache.org/bugzilla/show_bug.cgi?id=61991 Will Greenway changed: What|Removed |Added OS||All --- Comment #1 from Will Greenway --- Many of the examples for OOXML (XWPFDocument) refer to version 3.9. I gathered all the 3.9 jars, recompiled. Code works. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[Bug 61991] Simple instantiation of XWPFDocument causes reflection warning and method not found exception
https://bz.apache.org/bugzilla/show_bug.cgi?id=61991 Will Greenway changed: What|Removed |Added CC||wcgrn...@cox.net OS||Windows 10 -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[Bug 61991] New: Simple instantiation of XWPFDocument causes reflection warning and method not found exception
https://bz.apache.org/bugzilla/show_bug.cgi?id=61991 Bug ID: 61991 Summary: Simple instantiation of XWPFDocument causes reflection warning and method not found exception Product: POI Version: 3.17-FINAL Hardware: PC Status: NEW Severity: blocker Priority: P2 Component: XWPF Assignee: dev@poi.apache.org Reporter: wcgrn...@cox.net Target Milestone: --- This simple code: FileInputStream fis = new FileInputStream(filename); document = new XWPFDocument(fis); Using Tiki the mime of the file being attempted: application/vnd.openxmlformats-officedocument.wordprocessingml.document Generates: WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.apache.poi.openxml4j.util.ZipSecureFile$1 (file:/C:/javadev/workspace/poi-3.17/poi-ooxml-3.17.jar) to field java.io.FilterInputStream.in WARNING: Please consider reporting this to the maintainers of org.apache.poi.openxml4j.util.ZipSecureFile$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release --> the blocker java.lang.NoSuchMethodException: org.openxmlformats.schemas.wordprocessingml.x2006.main.impl.CTPictureBaseImpl.(org.apache.xmlbeans.SchemaType, boolean) Jar files in use: POI Core came from file:/C:/javadev/workspace/poi-3.17/poi-3.17.jar!/org/apache/poi/poifs/filesystem/POIFSFileSystem.class POI OOXML came from file:/C:/javadev/workspace/poi-3.17/poi-ooxml-3.17.jar!/org/apache/poi/POIXMLDocument.class POI Scratchpad came from file:/C:/javadev/workspace/poi-3.17/poi-scratchpad-3.17.jar!/org/apache/poi/hslf/usermodel/HSLFSlideShow.class I have tried work arounds nothing so far successful. I've tried switching between JVMs 1.7,1.8,1.9. Looking for jar dependencies and tried different files. I am building / running in Eclipse version: Oxygen.2 Release (4.7.2) Build id: 20171218-0600 Libraries on build path: dom4j-2.1.0.jar poi-3.17.jar poi-ooxml-3.17.jar poi-ooxml-schemas-3.17.jar poi-scratchpad-3.17.jar stax-api-1.0.1.jar tika-eval-1.17.jar xmlbeans-2.6.0.jar -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
RE: XMLBeans in 4.0.0 release
Bringing xmlbeans out of the attic is my vote. I can be one of the Xmlbeans PMCs if all we are missing is a head count and a couple emails to infra. I don't see taking Xmlbeans out of the attic as a huge support burden. It's a stable, complete product and any future development is probably just small bug fixes. As long as infra is okay with that philosophy, removing Xmlbeans from the attic causes the least confusion for everyone, and may reduce our support load for POI and Tika when users can't get xmlbeans working (even if all it is is linking to the FAQ and PJ's GitHub). Every email we receive probably was the result of 8 hours of struggling to diagnose the problem in their build setup, and several others who gave up without contacting us. On Jan 11, 2018 05:02, "Murphy, Mark" wrote: > If we are going to take on maintenance of XMLBeans, I would suggest that > getting it out of the attic would be the most appropriate course of action. > This would reduce confusion for people trying to find XML Beans as there > would only be a single project to reference rather than one in the attic > and another in the POI project. > > -Original Message- > From: Nick Burch [mailto:apa...@gagravarr.org] > Sent: Thursday, January 11, 2018 12:59 AM > To: POI Developers List > Subject: Re: XMLBeans in 4.0.0 release > > On Wed, 10 Jan 2018, pj.fanning wrote: > > I don't fancy trying to merge the xmlbeans and poi ant builds. I've > > been trying for an hour or more and still getting issues. > > There's no need to do this! > > We'd keep the two codebases separate, and probably release at different > times. (XMLBeans hardly ever, except when we find bugs) All that would > happen is that we'd swap the group ID, add POI to the release names, and > update the readme etc to refer to POI as the PMC providing the oversight > > So, assuming we're releasing it as POI rather than getting it out of the > attic: > * Copy xmlbeans trunk in svn to > https://svn.apache.org/repos/asf/poi/xmlbeans/trunk > * Merge in the fixes > * Update the bin/src packages to have poi in them, eg > xmlbeans-poi-2.6.5-bin.zip > * Update the poms to be under org.apache.poi rather than xmlbeans > * Test, vote, release! > > Or, if we want to take xmlbeans out of the attic, we'd do: > * Vote to take it on > * Wait for attic PMC to confirm > * Get infra to unlock svn for xmlbeans > * Merge in fixes > * Test, vote, release! > > Nick > > - > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional > commands, e-mail: dev-h...@poi.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > For additional commands, e-mail: dev-h...@poi.apache.org > >
[Bug 61989] Wrong result of sheet(0).row(0).cell(0)
https://bz.apache.org/bugzilla/show_bug.cgi?id=61989 Alain Fagot Bearez changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Alain Fagot Bearez --- You should try to use one of the specialized methods to retrieve the cell content. I would suggest to take a look at getStringCellValue() as first try. http://poi.apache.org/apidocs/org/apache/poi/xssf/usermodel/XSSFCell.html#getStringCellValue-- -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[Bug 61832] Unable to create a excel of 500,000 rows and 150 column using SXSSF workbook
https://bz.apache.org/bugzilla/show_bug.cgi?id=61832 --- Comment #20 from PJ Fanning --- There is a Pull Request which uses temp files for constructing the shared strings table. https://github.com/apache/poi/pull/85 -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[Bug 61832] Unable to create a excel of 500,000 rows and 150 column using SXSSF workbook
https://bz.apache.org/bugzilla/show_bug.cgi?id=61832 --- Comment #19 from Thamodharan --- My machine specs, Jboss server RAM 32 GB Heap size allocated to jboss 28 GB Harddisk 1 TB I am good to go with generating excel file upto a limit of 0.3 million X 200 rows with enabling shared string. Ahead such row, i face corrupt file issue when opening the generated excel. The reason for this error as stated by greg woolsey is, the data's are stored as inline string in the disk, thus excel couldn't tolerate putting such large number of inline string, thus repairing it, turning inline to single shared string. As suggested by greg woolsey, its better to go by enabling shared string, which holds unique data in heap space instead of disk space. This idea may aid the application to generate a single excel file in my machine with the above spec, but generating 2 or more excel at same time, will lead to memory out. I guess, writing a patch to store data in disk, rather in heap, will again lead to inline string and same error may occur. Can anyone from apache dev team or other followers, ignite a vice idea to rule this error out ? Waiting a good response Thamodharan B -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
RE: XMLBeans in 4.0.0 release
If we are going to take on maintenance of XMLBeans, I would suggest that getting it out of the attic would be the most appropriate course of action. This would reduce confusion for people trying to find XML Beans as there would only be a single project to reference rather than one in the attic and another in the POI project. -Original Message- From: Nick Burch [mailto:apa...@gagravarr.org] Sent: Thursday, January 11, 2018 12:59 AM To: POI Developers List Subject: Re: XMLBeans in 4.0.0 release On Wed, 10 Jan 2018, pj.fanning wrote: > I don't fancy trying to merge the xmlbeans and poi ant builds. I've > been trying for an hour or more and still getting issues. There's no need to do this! We'd keep the two codebases separate, and probably release at different times. (XMLBeans hardly ever, except when we find bugs) All that would happen is that we'd swap the group ID, add POI to the release names, and update the readme etc to refer to POI as the PMC providing the oversight So, assuming we're releasing it as POI rather than getting it out of the attic: * Copy xmlbeans trunk in svn to https://svn.apache.org/repos/asf/poi/xmlbeans/trunk * Merge in the fixes * Update the bin/src packages to have poi in them, eg xmlbeans-poi-2.6.5-bin.zip * Update the poms to be under org.apache.poi rather than xmlbeans * Test, vote, release! Or, if we want to take xmlbeans out of the attic, we'd do: * Vote to take it on * Wait for attic PMC to confirm * Get infra to unlock svn for xmlbeans * Merge in fixes * Test, vote, release! Nick - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[Bug 61989] Wrong result of sheet(0).row(0).cell(0)
https://bz.apache.org/bugzilla/show_bug.cgi?id=61989 laiwen.li changed: What|Removed |Added Summary|Wrong result of |Wrong result of |row(0).cell(0) |sheet(0).row(0).cell(0) OS||All -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[Bug 61832] Unable to create a excel of 500,000 rows and 150 column using SXSSF workbook
https://bz.apache.org/bugzilla/show_bug.cgi?id=61832 --- Comment #18 from Thamodharan --- Hi mewalig, Kindly help us by explaining the calculation which you stated on your last reply. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[Bug 61989] New: Wrong result of row(0).cell(0)
https://bz.apache.org/bugzilla/show_bug.cgi?id=61989 Bug ID: 61989 Summary: Wrong result of row(0).cell(0) Product: POI Version: 3.17-FINAL Hardware: PC Status: NEW Severity: normal Priority: P2 Component: XSSF Assignee: dev@poi.apache.org Reporter: dhc...@126.com Target Milestone: --- Created attachment 35673 --> https://bz.apache.org/bugzilla/attachment.cgi?id=35673&action=edit The excel to read and Debug Infomation I read the first sheet of the first row of the first cell. but the result is wrong. It gives me the sheetName. Please read the attachment file for the detail information. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[Bug 61874] OperandResolver.parseDouble(String) does not does not work for numeric Strings using a comma as decimal separator.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61874 Carl Salaets changed: What|Removed |Added Status|NEEDINFO|NEW -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
