Hi JB. Did you have any ideas about this? I'm happy to pitch in and help...and submit a patch. But I'm stuck on the problems I mentioned below, and need someone with a little more OSGi expertise to help get me past the problem.
Let me know if I can help. Thanks. --Scott -----Original Message----- From: Jean-Baptiste Onofré [mailto:[email protected]] Sent: Monday, October 17, 2011 11:03 PM To: [email protected] Subject: Re: Apache Poi 3.7 component Hi Scott, I try to take a look today. Regards JB On 10/18/2011 02:59 AM, Scott Came wrote: > I need to process an Excel spreadsheet (version 2007+.xlsx) in one of > my Camel routes running in Servicemix. I plan to do so with Apache Poi. > > I added the existing apache poi component to my Servicemix instance, > and added a dependency on the same version to my project pom. > Unfortunately, the existing poi SMX component does not include the Poi > "ooxml" library, which is necessary to process the 2007+ spreadsheet format > (Office XML). > > Also, version 3.6 of Poi (on which the current component is based) is > a little out of date.the current release is 3.7. > > So my plan is to build a new OSGi bundle that uses the 3.7 version and > includes all of Poi (including the ooxml support). I've spent the > better part of several hours trying to coerce the existing component > pom > (http://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk/poi-3.6 > /pom.xml) into working for Poi 3.7.I made the changes that seemed > obvious. When I attempt to install the resulting bundle, karaf > complains about a missing requirement junit.framework. When I run the > headers command on the bundle, I see several packages in red, > including dom4j, junit.framework, junit.textui, and the > org.openxmlformats.* packages. > > Upon further digging, I noticed that there is a class in Poi > (org.apache.poi.util.OOXMLLite) that has a dependency on junit, so > that's probably what's causing the red import.I've looked at the > source for this class, and nothing else depends on it, so if I can > figure out how to exclude it from the bundle perhaps the junit > dependency problem would go away. > > As for the org.openxmlformats.* dependencies.those baffle me, since I > am including those packages in the uber-jar with shade, and have in > fact verified that they get included. > > I've attached the pom. Any assistance would be most appreciated. > > Thanks. > > --Scott > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
