Mark Brouwer wrote:
> 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.
>
I completely understand. This type of feedback is just as important to
us as bug reports, so don't hesitate to let us know how we can improve
the process. I'm just a developer on the JAXB team, so I personally don't
have any control over these kinds of decisions, but I can tell you that
the engineering manager for JAXB and for the entire JWSDP also values this
type of feedback. We do in fact have discussions about determining the
best way to release these products. I believe in JWSDP 1.0, it wasn't
even possible to custom install individual components - you had to install
the entire pack. People complained, so we added that option to the installer
in JWSDP 1.1. Perhaps we still have room for improvement, but we're making
incremental steps...
>
>>>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!
Thanks again for your input - I'll make sure to share it with the JWSDP team.
--Ryan