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



I would like to see an end to end example of developing a LPEX plug-in. I
experimented with writing some myself and didn't get far.

The plug-in is not proprietary and is sort of general would you consider
publishing the plugin and the steps you used to develop it?

Thanks
Bill B





David Gibbs <david@xxxxxxxxxxxx>
08/09/2007 08:38 AM
Please respond to Websphere Development Studio Client for iSeries

To: Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>
cc: (bcc: Bill Blalock/TUS/US/Certegy)
Subject: Re: [WDSCI-L] lpex user profile plugin


Rick Rauterkus wrote:
I finally found the problem. The jar file was being generated as
com.rickr.lpex_1.0.0.jar. I renamed it to com.rickr.lpex.jar and now it

works. I tried removing the version in the editor but then it generated
it
with _0.0.0. Is having to rename the file normal?
Version is important to the plug-in system ... it allows Eclipse to keep
track of what plug-in version is installed (so they can be rolledback if
necessary).
Also, where is the proper place to put these plug-ins? I put it in
C:\Program Files\IBM\SDP70\plugins, but that is a folder that was
created
during the WDSCi install. But it was empty, so I used it.
Check the online help for information on an update site ... that will
give you the ability to have it automatically installed in the correct
location.
david

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.