Hi Ganga,
In 1.0, we shipped the runtime as a library whereas in 1.0.1 most of it
is part of the generated code. This makes it easier to keep subsequent
releases of the JAXB RI backward compatible with 1.0.1 applications.
Since the size of the runtime is fixed, the relative impact on footprint
depends on the overall size of your generated code. However, if you
compile multiple independent schemas, you'll get a runtime for each. You
can use the -use-runtime switch to xjc to generate code that re-uses an
existing runtime (see
http://java.sun.com/webservices/docs/1.2/jaxb/xjc.html).
Regards,
--
Ed Mooney |Sun Microsystems, Inc.|Time flies like
Java Web Services |UBUR02-201 |an arrow, but
Ed.Mooney_at_Sun.COM |1 Network Drive |fruit flies like
781-442-0459 |Burlington, MA 01803 |a banana. Groucho
Ganga Sah wrote:
> I have sucessfully migrated my application to JAXB
> 1.0.1 but I find that JAXB generated Java files and
> compiled class files have VERY large size compared to
> those in JAXB 1.0.0. This has increased the size of my
> application aprox. 4 times?
> I see this as a serious issue in migrating to
> JAXB1.0.1? Is there a way to fix this problem?
>
> thanks,
> ganga
>
> __________________________________
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com