RE: RE: WDSC With Aldon's A/CMS

 > >  So we took the route of providing 
> > custom integration 
> > for RSE and iSeries.  The TurnOver UI was 100% rewritten for 
> > Eclipse and 
> > you can basically do everything including a lot that you cannot do in 
> > 5250.
> 
> This is what I was trying to say.  Obviously I don't know enough about
> Eclipse, Turnover, or Aldon to go into the details that you have.  But 
from
> your information I guess what I was trying to say is that Aldon's plugin
> uses the SCM UI provided by Eclipse.  Whereas your product provides its 
own.
> 
> Given the current limitations of the Aldon plugin and my belief that the
> limitations have to do with using the Eclipse provided SCM UI;  I'd have 
to
> say your route was the better choice.
> 

The reason I replied is that your wording was very similar to sum FUD 
about this issue that Aldon uses in sales situations.  For example, they 
once said the following in a press release about their offering:

http://www.aldon.com/news/pr_20031007.html

"It is a unique implementation, unleashing the full power and 
functionality of WDSc as it was intended by IBM. By developing a 
WDSc-based Team Repository (rather than a proprietary, outside 
vendor-based perspective)"

This was a clear shot at us, and it was blatantly untrue.  First off, if 
they are using the Team API they are not unique, they are using the same 
technique as the free CVS integration included with WDSC and everyone 
else, including us, that use the Team API.  Second, if that is the way it 
was "intended by IBM" then why doesn't RSE support the Team API for 
iSeries resources? (answer: they can't)  Finally, since RSE does not 
support the Team API for iSeries resources, if Aldon are now providing 
some kind of support for iSeries development, then they are not doing it 
using the Team API, unless they are forcing you to use iSeries Projects 
instead of RSE.  God bless them if they are.

What we did was offer a complete implementation.  We completely rewrote 
our UI in Eclipse offering 100% functionality.  For iSeries development, 
this is all fully integrated with all of the tools IBM provides and is 
100% compatible with our 5250 UI if you have to go back and forth.  For 
doing versioning of Java/Web artifacts we offer a solution that uses the 
Eclipse Team API.

Finally, I would just also point out that we are still the only iSeries CM 
solution that has obtained the "Ready for WebSphere Studio" validation, so 
I think it is safe to say that we are doing what "IBM intended".  It was 
not an easy validation to obtain.

http://www-106.ibm.com/developerworks/websphere/downloads/plugin/

Mark