I first posted this mail to the jwsdp-feedback address but I was asked
by Kohsuke Kawaguchi of Sun Microsystems to redirect it to this list, so
here it is.
--
Thanks for releasing the JAXB 1.0 implementation. Our team depends on
the use of JAXB and is now able to release products based on it, thanks.
However looking into the redistribution terms of the license we are
faced with what we consider a license problem.
The terms of the license dictate:
(i) you distribute the Redistributables complete and unmodified
(unless otherwise specified in the applicable Release Notes file),
and only bundled as part of your Programs,
The Release Notes say:
Redistribution of a component entails the redistribution of all
files comprising the component and any dependent components.
This means that in case of JAXB we have to redistribute a huge amount of
jar files even while a lot of them are not necessary in case of J2SE
1.4, also we don't have the need for the jaxb compiler at runtime.
We like to be able to keep the download size of our Jini services small
and therefore we think it would be great of the release notes would
state that it is also possible to redistribute only the parts you
actually need at runtime.
As an example I would like to refer to the Release Notes of the JavaMail
implementation of Sun that states:
"In some cases it may be desirable to minimize the size of the JavaMail
API code used by an application (e.g., when downloading with an applet).
In this case you might want to include the "mailapi.jar" file, which
includes *no* protocol providers, along with just the jar file for the
protocol provider you need. For example, an applet that only needs to
send mail could use the "mailapi.jar" file and the "smtp.jar" file."
In our case we only need 'jaxb-api.jar, jaxb-ri.jar, jaxb-libs.jar' a
total of 1.1 MB for the correct working of our JAXB functionality and
can leave at home 'jaxb-xjc.jar, jaxp-api.jar, sax.jar, dom.jar,
XercesImpl.jar, xalan.jar, jax-qname.jar, namespace.jar' saving 2.8 MB.
If we really have to redistribute all the jar files, I'm afraid we have
to look for alternatives like JDOM as there are no other JAXB
implementations AFAIK. I can't justify the footprint of the current
organization of the Web Services, I consulted other teams in our company
and they are facing the same problems with technologies like JAX-RPC.
Hope this problem can be solved as I believe it would increase
acceptance of the technology.
Regards,
--
Mark Brouwer