Re: Is RDi really a "new" product?

I think you just answered your own question. The reason to plug 3rd party stuff into WDSC is so that we don't have to push IBM to devote the resources to support it.

For example, IBM is focusing its strategic investments on JSF/EGL, and also on RESTful stuff like that delivered in Project Zero. I don't need IBM to support (for example) Struts, Tapestry, Wicket, Seam, or any number of other frameworks if I can add third-party plugins that provide that support to WDSC/RDi.

You questioned someone last week because they had separate workspaces for EGL and non-EGL work. I don't want to have separate Eclipse instances for IBM-provided and non-IBM-provided plugins.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx on behalf of Joe Pluta
Sent: Thu 3/6/2008 1:46 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Is RDi really a "new" product?

Do you need this for development? Since WDSC already has RSE, why would
you want the OpenRSE plug-in?

Seriously, I understand the attraction of being able to plug things into
WDSC (I just got done writing a series of articles on WDSC plug-ins),
but I do question the need to plug *everything* into it. What is the
benefit you get from OpenRSE? Would others get the same benefit? Does
it make sense for IBM to spend resources doing that rather than, say,
improving the embedded SQL support?

If yours is a legitimate need that you think will benefit the community,
then by all means let's get it to the development team!