|
WDSC is definitely commercially supported. If you found a problem that ultimately was a bug in Eclipse, I am sure that IBM would work to ensure that the bug was reported and fixed in Eclipse and that fix would make its way back into WDSC as soon as possible. Just as an example, WDSC 5.1.2 comes with Eclipse 2.1.3 (as opposed to 2.1.0). The vast majority of the fixes between 2.1.0 and 2.1.3 were contributed by IBM based on bugs the users of the IBM tools discovered. I think the gray area is when you start moving beyond true bugs into things you just would like to work differently or better. SEU is commercially supported but if you call IBM and say that SEU should have a function key that pops up a list of all variables used in the source and allows you to click on one to go to that line of code they are not going to do much about it for you. Requests that are essentially enhancements to Eclipse would be similar. However, if anything WDSC should be a better product because there are more people using and enhancing that Eclipse foundation. Mark wdsci-l-bounces@xxxxxxxxxxxx wrote on 10/05/2004 12:42:18 PM: > I think Toolbox may be a little different. My understanding of Toolbox (and > someone correct me if I'm wrong) is that IBM ships a version of Toolbox in > the iSeries IFS and supports that version like other IBM products. This > makes Toolbox different than Eclipse. > > >The community behind the open-source product supports it. This in > >itself has good and bad points. A 'normal' product has the same type of > support > >issues. > > Maybe I'm missing something. If I have a problem with WebSphere Application > Server not deploying a Web Module properly (has never happened...just > fictional example), I feel confident I can call IBM and get support, and > they will work on the problem immediately and come up with a solution. When > I actually had this problem with my Tomcat server (Tomcat 5 needed to have > the tools.jar file from my sdk copied into its common\lib directory), I had > to spend hours sifting through Web pages and email lists to find what I > hoped was a working solution. If I hadn't gotten lucky and stumbled across a > solution, well, then what? This seems like a major difference between a > licensed product with paid support and an open source product with > 'community' support. > > Please feel free to enlighten me. :-) > Kelly > > -----Original Message----- > From: wdsci-l-bounces@xxxxxxxxxxxx > [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Scott Johnson > Sent: Tuesday, October 05, 2004 11:17 AM > To: Websphere Development Studio Client for iSeries > Subject: Re: [WDSCI-L] Removing a plug-in > > > If these companies have this mentality then they really don't understand > open-source. The community behind the open-source product supports it. > This in > itself has good and bad points. A 'normal' product has the same type of > support > issues. > > The Java Toolbox for iSeries is also based on an open-source > project(JTOpen). > More direct basis than WDSC to eclipse though. And from what I have heard > and > seen, it is working out great. > > As for WDSC, as far as I know IBM 'picks' a version of Eclipse and builds > the > stuff on top of it. I would also think that if you had a problem with WDSC > that > related back to something in Eclipse, they would fix it. > > -- Scott J > > Kelly Cookson wrote: > > > IBM's choice to put WDSCi on top of an open source product introduces the > > same question that keep companies from going with other open-source > > products: who's going to support it? As long as IBM feels free to not work > > on Eclipse problems, and Eclipse has no obligation to WDSCi users, then > > there's a crack in the support infrastructure. Uninstalling plug-ins is > not > > a mission critical issue. I'm just saying it reflects a less than perfect > > support situation. > > > > Kelly > > > > _______________________________________________ > This is the Websphere Development Studio Client for iSeries (WDSCI-L) > mailing list > To post a message email: WDSCI-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > or email: WDSCI-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/wdsci-l. > _______________________________________________ > This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list > To post a message email: WDSCI-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/wdsci-l > or email: WDSCI-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/wdsci-l. > > _____________________________________________________________________________ > Scanned for SoftLanding Systems, Inc. by IBM Email Security Management > Services powered by MessageLabs. > _____________________________________________________________________________ _____________________________________________________________________________ Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs. _____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.