× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Alright, I tried to get my plug-in to run in WDSC.

I did all that I can think of the get the Equnoix plug-ins that are part of
Eclipse 3.3 installed into my WDSC. They seem to install but my plug-in
DOES NOT run.
There are no issues running my plug-in on an Eclipse 3.3 workbench.

Can any IBMers offer suggestions? I have 2 customers that have a
requirement to use WDSC and refactoring my plug-in down to 3.2 is not an
option.

My plug-in uses the following extension points

org.eclipse.core.resources.builders
org.eclipse.core.resources.natures
org.eclipse.core.resources.markers
org.eclipse.ui.popupMenus
org.eclipse.ui.preferencePages
org.eclipse.core.runtime.preferences
org.eclipse.ui.propertyPages
org.eclipse.ui.newWizards
org.eclipse.jdt.ui.classpathContainerPage
org.eclipse.jdt.core.classpathContainerInitializer
org.eclipse.ui.actionSets
org.eclipse.equinox.http.registry.servlets

My plugin has the following dependencies specified:

org.eclipse.ui,
org.eclipse.core.runtime,
org.eclipse.core.resources,
org.eclipse.jdt.core,
org.eclipse.ui.ide,
org.eclipse.jdt.ui,
javax.servlet,
org.eclipse.equinox.http.jetty,
org.eclipse.equinox.http.registry,
org.eclipse.ui.console,
org.eclipse.jdt.launching,
org.apache.ant

-----Original Message-----
From: Christopher Smith [mailto:smitopher@xxxxxxxxx]
Sent: Thursday, March 06, 2008 1:17 PM
To: 'Websphere Development Studio Client for iSeries'
Subject: RE: [WDSCI-L] Is RDi really a "new" product?

Thank you for the link.

While it indicates that it can be plugged into a 3.2 workbench, the 3.3
distribution already includes it AND a Jetty container.

This is NOT simple stuff. While this may have help me awhile ago, 3.3
provided me with all of the stuff on the link. The only things my plug-in
had to extend were already in the supplied distribution. I'm not about to
rework my plug-in into two incompatible versions nor am I going to rework a
WDSC/RDi workbench when 3.3 has been GA since June of last year and 3.4 is
getting close.

Eclipse is free, RDi is not. RDi needs to offer value over what is free and
currently available as well as EVERYTHING in the free and current codebase.
IBM is intimately involved and even running most aspects of the 3.3 and 3.4
development efforts. For the prices charged, their "value added" packages
should always be up to date.

I do appreciate the link. I have no idea why it never popped up in all of
my googleling.

Chris

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Joe Pluta
Sent: Thursday, March 06, 2008 12:49 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Is RDi really a "new" product?

Christopher Smith wrote:
Again, what specifically is required from 3.3?


Again, the Equinox wrapped Jetty servlet container. 3.2 does not provide
a workbench servlet container.

This isn't the project you're referring to?

http://www.eclipse.org/equinox/server/http_in_container.php

Joe

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.