× 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.



Hi Eric,

Lo and behold! Without much expectation I started following the steps in
your latest article, but much to my surprise this time it works! I still
don't understand why the original projects did not, but this example is a
lot closer to what I was hoping to achieve (i.e. extending the editor like I
used to do with SEU and CODE). So for now I'm happy.

Joep Beckeringh


----- Original Message -----
From: "Eric Simpson" <esimpson@xxxxxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Tuesday, January 06, 2004 6:30 PM
Subject: RE: [WDSCI-L] Extending the LPEX editor


>
>
>
>
> Joep,
>
> For the build path issue, do you have two entries for LPEX right now?  One
> with jar and one without?  You can delete the one without the jar.  Have
> you used the update classpath action?  I don't think this error would
cause
> the problems you have.
>
> Have you read the latest article?  It is based on 5.1.  Here is the link:
> http://eservercomputing.com/iseries/archives/index.asp?a=1&id=795
> Maybe give it a try and if you still have problems email me
> (esimpson@xxxxxxxxxx) your project and I will take a look.
>
> Eric
>
> Eric Simpson
> WebSphere Development Studio Client, IBM Toronto Lab, D1/140/8200/MKM
> Phone:  (905) 413-3226,  T/L:  969-3226,  Fax: (905) 413-4850,  Email:
> esimpson@xxxxxxxxxx


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.