You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by Jukka Zitting <ju...@gmail.com> on 2009/10/19 11:58:45 UTC
Streamlining the ooxml-schemas jar
Hi,
The OOXML support in POI works really well for Apache Tika, but I'm a
bit annoyed [1] by the size of the ooxml-schemas jar file.
I looked at the compile-ooxml-xsds target that generates the jar, and
the difference in the input and output sizes is pretty amazing:
* input: 220K ooxml-lib/OfficeOpenXML-XMLSchema.zip
* output 14M ooxml-lib/ooxml-schemas-1.0.jar
That's a 62x difference! Are all of the generated code and xsd
snippets in ooxml-schemas needed by POI, or would there be some way to
streamline the jar?
[1] http://jukkaz.wordpress.com/2009/10/16/putting-poi-on-a-diet/
BR,
Jukka Zitting
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: Streamlining the ooxml-schemas jar
Posted by Dave Fisher <da...@jmlafferty.com>.
>> I noticed the size too. The jar looks like it's generated using
>> xmlbeans.
>
> Yup, it is. We're currently statically compiling the XSDs to the
> jar. I guess the ideal thing might be to statically compile the few
> really common ones, and dynamically compile the rest from the XSDs
> if used. Not sure how to do that with xmlbeans though :/
I think that this is a good topic for the Hackathon on Tuesday.
When Josh and I met Jasson Harrop to discuss his docx4j he was really
interested in comparing our marshalling and unmarshalling with
XMLBeans vs. his use of JaxB.
Regards,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: Streamlining the ooxml-schemas jar
Posted by Nick Burch <ni...@torchbox.com>.
On Mon, 19 Oct 2009, Ryan Ackley wrote:
> I noticed the size too. The jar looks like it's generated using
> xmlbeans.
Yup, it is. We're currently statically compiling the XSDs to the jar.
I guess the ideal thing might be to statically compile the few really
common ones, and dynamically compile the rest from the XSDs if used. Not
sure how to do that with xmlbeans though :/
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: Streamlining the ooxml-schemas jar
Posted by Ryan Ackley <ry...@gmail.com>.
I noticed the size too. The jar looks like it's generated using
xmlbeans. You might find some useful information there.
http://xmlbeans.apache.org
On Mon, Oct 19, 2009 at 8:58 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> The OOXML support in POI works really well for Apache Tika, but I'm a
> bit annoyed [1] by the size of the ooxml-schemas jar file.
>
> I looked at the compile-ooxml-xsds target that generates the jar, and
> the difference in the input and output sizes is pretty amazing:
>
> * input: 220K ooxml-lib/OfficeOpenXML-XMLSchema.zip
> * output 14M ooxml-lib/ooxml-schemas-1.0.jar
>
> That's a 62x difference! Are all of the generated code and xsd
> snippets in ooxml-schemas needed by POI, or would there be some way to
> streamline the jar?
>
> [1] http://jukkaz.wordpress.com/2009/10/16/putting-poi-on-a-diet/
>
> BR,
>
> Jukka Zitting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org