openxml4j-devs Mailing List for OpenXML4J - Open XML library for Java
Status: Beta
Brought to you by:
neodante
Menu
▾
▴
openxml4j-devs — OpenXML4J developers mailing list
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Yegor K. <ye...@di...> - 2008-10-27 08:45:55
|
Hi I'm a release manager in Apache POI project, http://poi.apache.org. In about a month time we are going to release POI-3.5-FINAL which will include initial support for SpreadsheetML. OpenXML4J fits very well for our purposes and we are all happy using it. One of the issues to solve before release is making OpenXML4J available on the Maven repository. I went ahead and prepared the artifacts for the latest openxml4j-bin-beta-080728.jar. The groupId is "org.openxml4j", artifactId is "openxml4j", version is "1.0-beta" The artifacts are available for review till Friday, October 31 at the following location: http://people.apache.org/~yegor/maven-ooxml-dependencies/org.openxml4j/ Please review if you are interested. Regards, Yegor Kozlov |
|
From: Rainer S. <rs...@ad...> - 2008-08-23 20:00:04
|
Hi, I ran into a memory critical situation where one aspect of a solution is ability to get rid of the byte[] storage in MemoryPackagePart. Assuming I have a DOM like tree (XmlBeans) of an XML file, I don't really need the additional byte[] in MemoryPackagePart. XmlBeans allows to get an InputStream from an XML node. This can be returned by <PackagePart>.getInputStreamImpl() . In my adjusted version I added a HollowMemoryPackagePart class and among other things added the method PackagePart.makeHollow(...) . The new class effectively requests the InputStream at save time and does not hold its own buffer. MemoryPackagePart is used as default, so unless makeHollow is called, it remains the same. Would it make sense to add such a feature to openxml4j? If yes, I would be glad to provide a patch. Best wishes, Rainer -- |
|
From: Nick B. <ope...@ga...> - 2008-04-03 09:26:28
|
Hi All Just a heads-up that I've ended up largely re-writing this function :/ For .xlsx files, you can have a relation from /xl/worksheets/sheet1.xml to /xl/comments1.xml, which excel stores as a relative path of ../comments1.xml . relativizeURI was incorrectly giving just comments1.xml Unfortunately, my french wasn't up to understanding the comments in the method, to figure out how it was supposed to work, so I ended up replacing it with something hopefully quite a bit simpler. All the old tests for PackagingURIHelper now pass (including the one that failed before), and all the new tests I've added pass too. But, it's quite a major change, so do shout if you spot any problems with it, and I'll endevour to add tests for your uses too! For now though, all the relations generated by poi for .xlsx files are being correctly relativized, which is quite promising! Nick |
|
From: Nick B. <ope...@ga...> - 2008-01-08 14:39:59
|
On Tue, 8 Jan 2008, Nick Burch wrote: > The attached patch defines a common interface (RelationshipSource), and > gets both Package and PackagePart to use it. If it makes sense, any > chance you could apply it? Sorry, just noticed that the changes to Package were missing from that patch (was just PackagePart and RelationshipSource). New patch attached which should have everything Nick |
|
From: Nick B. <ope...@ga...> - 2008-01-08 14:26:23
|
Hi All I've started making use of OpenXml4J to do some simple ooxml parsing with Apache POI. One thing that surprised me was that Package and PackagePart both provide lots of relationship methods, with the same signature, but that isn't done via a common interface. So, you can't just have your own method that works with either for getting relationships. The attached patch defines a common interface (RelationshipSource), and gets both Package and PackagePart to use it. If it makes sense, any chance you could apply it? Otherwise, using the API has been great :) Cheers Nick |
|
From: Guilherme M. <gui...@lt...> - 2007-06-04 17:40:09
|
hello all, me and my teammate started some demos with openXml and java, and started using your package. its a very good project, and if we can help in some form, it will be very pleasant.. For the first demo, we use the opc implementation and the WordProcessingML, we know that the ML's will not be coded until the specification gets finalized.. but for our purposes the already coded part works well... But working with the code, we have to make some workarounds in your API to achieve our goals, I'm sending attached the patch we made from the SVN source code and our basic test code. We will like to know what you think and if it can be resolved using another way . The patch are not commented, so better to explain here what we faced.. First we cant make the generated document opens with Word 2007, its stats a error on the paragraph alignment tag, and we found out that the paragraph alignment tag must use low case text. The other problem we face, its that we cant open a package and close (save) because the code try to delete the file, but the file is open by the ZipPackage class, so we work in an workaround using a temp file. then closing the zip using a not so beautiful way. but we cant find another way lol. trying to close the ziparchive before call save doesn't work as well, because the close(); method of the ZipFile class discards all the inputstreams that were opened and the save methods still read the file. we hope that we can help in some way... many thanks Guilherme Moro |
|
From: Nick B. <ope...@ga...> - 2007-05-18 15:26:57
|
On Fri, 18 May 2007, Julien Chable wrote: > it's seems quite OK for me, however the first release (I hope a beta > release for the next month) will be a focus on the Open Packaging > Convention specifications, so all the implementation concerning Word, > Excel, PowerPoint has not yet begun (nor the decisions about the > architecture etc ...). That's fair enough. I'd say if you were going to prioritise one bit, I'd go for a simple text extractor first - all the lucene users want something to do that :) > So, from my side it's a little too early to take a decision about this > point, however I really like the idea and will contact and discuss this > point thoroughly on the POI mailing list for sure and as soon as > possible ;) >From our perspective, it wouldn't be too bad if we jointly knocked out an interface, but we ended up implementing it before you. So, swing on by poi-dev when you have a moment, and we can work something out. You might even interest another developer or two, but I can't promise anything! Nick |
|
From: Julien C. <ju...@wy...> - 2007-05-18 14:32:40
|
Nick, it's seems quite OK for me, however the first release (I hope a beta = release for the next month) will be a focus on the Open Packaging = Convention specifications, so all the implementation concerning Word, = Excel, PowerPoint has not yet begun (nor the decisions about the = architecture etc ...). So, from my side it's a little too early to take = a decision about this point, however I really like the idea and will = contact and discuss this point thoroughly on the PIO mailing list for = sure and as soon as possible ;) Julien Chable Wygwam France - 1 rue de la Performance - F-59650 Villeneuve d'Ascq - = T=E9l : +33 (0)3 20 82 38 77 Wygwam Belux - 64 rue Victor Corne - B-7700 Mouscron - T=E9l : +32 (0)56 = 33 06 60 Mobile : +33 (0)6 74 28 40 50 http://www.wygwam.com/ Blog : http://blogs.developpeur.org/neodante -----Original Message----- From: Nick Burch [mailto:ope...@ga...]=20 Sent: mercredi 16 mai 2007 15:33 To: Julien Chable Cc: ope...@li... Subject: Re: [Openxml4j-devs] Common API to Apache POI? On Wed, 16 May 2007, Julien Chable wrote: > Sorry for the delay, I have to configure my mail client in order not = to=20 > have mails from the mailing list flagged as spam ;-) :) > Yes, it could be interested to discuss more thoroughly about that = point=20 > ;-) Is it possible for you to send more details about your idea=20 > concerning these common method signatures ? If you're interested, it might be worth shifting the discussions over to = the poi-dev list. We've got quite a few interested developers and users=20 who I'm sure would have a lot to offer. However, my broad idea was: * some sort of common interface defining an excel file, a word file etc (excel is probably the main one for us, it's the area our code is strongest in, and has the most users) * on that common excel interface, define ways to get at sheets, which let you get at rows, which let you get at cells etc * quite possibly a similar (but much simpler) definition to our "user model API", assuming that's a good fit for your code (looked ok from = an initial quick read) http://jakarta.apache.org/poi/hssf/quick-guide.html http://jakarta.apache.org/poi/hssf/how-to.html * worry about powerpoint and word once we've got excel sorted :) What do you think? Nick |
|
From: Nick B. <ope...@ga...> - 2007-05-16 13:33:15
|
On Wed, 16 May 2007, Julien Chable wrote:
> Sorry for the delay, I have to configure my mail client in order not to
> have mails from the mailing list flagged as spam ;-)
:)
> Yes, it could be interested to discuss more thoroughly about that point
> ;-) Is it possible for you to send more details about your idea
> concerning these common method signatures ?
If you're interested, it might be worth shifting the discussions over to
the poi-dev list. We've got quite a few interested developers and users
who I'm sure would have a lot to offer.
However, my broad idea was:
* some sort of common interface defining an excel file, a word file etc
(excel is probably the main one for us, it's the area our code is
strongest in, and has the most users)
* on that common excel interface, define ways to get at sheets, which
let you get at rows, which let you get at cells etc
* quite possibly a similar (but much simpler) definition to our "user
model API", assuming that's a good fit for your code (looked ok from an
initial quick read)
http://jakarta.apache.org/poi/hssf/quick-guide.html
http://jakarta.apache.org/poi/hssf/how-to.html
* worry about powerpoint and word once we've got excel sorted :)
What do you think?
Nick
|
|
From: Julien C. <ju...@wy...> - 2007-05-16 13:28:34
|
Hi Nick, Sorry for the delay, I have to configure my mail client in order not to have mails from the mailing list flagged as spam ;-) Yes, it could be interested to discuss more thoroughly about that point ;-) Is it possible for you to send more details about your idea concerning these common method signatures ? Regards, Julien --- Hi Guys I'm involved in Apache Jakarta's POI project, which is a pure java file=20 format reader for the OLE2 office documents. A few of out users are=20 starting to want to read the Office XML file formats, and openxml4j is=20 what most are going with. I was wondering if it might be worth us trying to come up with some common=20 method signatures that we could both implement, to make it easaier for our=20 users to switch between using OLE2 and OOXML documents in their code.=20 While the file formats are very different, the entities stored within=20 have a lot in common, so it initially seems there might be similar APIs=20 needed for both. What do you think? Nick |
|
From: Nick B. <ope...@ga...> - 2007-05-03 11:30:59
|
Hi Guys I'm involved in Apache Jakarta's POI project, which is a pure java file format reader for the OLE2 office documents. A few of out users are starting to want to read the Office XML file formats, and openxml4j is what most are going with. I was wondering if it might be worth us trying to come up with some common method signatures that we could both implement, to make it easaier for our users to switch between using OLE2 and OOXML documents in their code. While the file formats are very different, the entities stored within have a lot in common, so it initially seems there might be similar APIs needed for both. What do you think? Nick |
