Ryan Shoemaker - JavaSoft East wrote:
>
> Mark Brouwer wrote:
> >
> > But I must also admit that the way the Class-Path is assembled in the
> > jaxb-xjc.jar is not my way of doing things, but that I guess is the
> > effect of bundling all the XML technologies as part of the JWSDP, which
> > IMHO has been a very bad decision.
> >
>
> I can understand your point of view, but please keep in mind that we are
> providing all of these technologies for free. Aside from the large-ish
> download, we do provide the ability to custom install specific components
> from the JWSDP, so it shouldn't be too much of a burden.
>
Ryan,
I always feel unpleasant having criticism about (free) software. But I
take time to submit bugs and contribute to open source projects, so
believe me when I say I do it to improve things and not to make teams
feel bad about their labor.
I also tend to think that if you provide something for free, your only
reward is the number of happy faces you get from your users.
I can understand the reason for bundling everything together for those
who want to build webservices and want to have the out-of-the-box
experience, but my experience tells me each individual technology is
hindered by it. At least it scares away people who are just looking for
that particular technology and that are confronted with the overhead.
And I really can't see in whose interest that would be.
>
> > While I'm at it, are there any plans to provide maintenance releases or
> > seperate releases of JAXB independent of the JWSDP?
>
> At this point, the plan is to ship maintenance releases with the JWSDP.
>
Well this is exactly what I'm afraid of, but time will tell if I'm right
in my fear. I hope you guys win!
--
Mark Brouwer