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




Ideally, you can just use 'import package'. For JTOpen
(com.ibm.as400.access), since it is not an Eclipse plugin, multiple plugin
developers have taken it, included it in their plugins, and exported the
packages. To avoid issues, I would suggest using 'require bundle' to RDi's
com.ibm.etools.iseries.toolbox plugin.

Thanks,
Eric





Eric Simpson
Rational Developer for i
IBM Canada Lab
905-413-3226
esimpson@xxxxxxxxxx







From: Mihael <mihael@xxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Date: 09/18/2018 04:18 AM
Subject: Re: [WDSCI-L] iSphere Journal Explorer Error
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



Hi,

using import package is normally the way to go. Require bundle is
considered bad practice in the OSGi world. There should not be two bundles
which exports a package with the same major version number. Split packages
are also a no go which leads to two bundles with duplicate package exports.

Best regards

Mihael

Am 18. September 2018 09:19:16 MESZ schrieb Thomas Raddatz
<thomas.raddatz@xxxxxx>:
Hi Kevin,

I am very confident that, I found and fixed the problem. Usually
Eclipse plug-ins specify dependencies with a "Require-Bundle" entry in
MANIFEST.MF. But for whatever reasons the iSphere Journal Explorer
plug-ins used the "Import-Package" key to import the Java
"com.ibm.as400.access" package.

The problem with "Import-Package" is that it loads the specified
package (com.ibm.as400.access) from whatever plug-in that exports the
package. I do not know the real mechanism but I assume that OSGI takes
the package from the first plug-in that exports it with no order
guaranteed. That could be the reason why it works with my installation
of RDi but not with yours. Most likely you use another plug-in that
exports "com.ibm.as400.access".

However "Require-Bundle" enables a plug-in to use all exported packages
of the specified plug-in (com.ibm.etools.iseries.toolbox). For
simplicity read "plug-in" as "bundle" or vice versa.

I am going to release a new beta version this (late) afternoon. It
would be great if you could download and install 3.5.0.b009 once that
it is available.

Thomas.


-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Raisor, Kevin
Gesendet: Montag, 17. September 2018 20:07
An: 'wdsci-l@xxxxxxxxxxxx'
Betreff: Re: [WDSCI-L] iSphere Journal Explorer Error

Correct.

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
Tools/400
Sent: Monday, September 17, 2018 1:54 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] iSphere Journal Explorer Error

That is exactly what I have. I assume that it is the only entry for
"com.ibm.etools.iseries.toolbox" that you have, right?

Scratching my head.

Thomas.

Am 17.09.2018 um 19:14 schrieb Raisor, Kevin:
8.5.6004.v20180523_1601 is the version number I have.

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
Tools/400
Sent: Monday, September 17, 2018 11:47 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] iSphere Journal Explorer Error

I am not sure which version is loaded for the iSphere plug-in,
because the iSphere plug-in does not specify a version for dependency
"com.ibm.etools.iseries.toolbox" in order to be compatible with RDP 8.0
to RDi 9.6.x.

From what I know I expect RDi to load the latest version for iSphere,
which I expect to be the one shipped with RDi.

Can you please:

a) Start RDi.
b) Goto: Help -> About -> Installation Details -> Plug-ins.
c) Sort the plug-ins by id.
d) Search for id "com.ibm.etools.iseries.toolbox".

How many entries do you find there and what versions do they have?

Sorry, that I cannot guide you through this issue more precisely.
iSphere is available since 2012 and we (Frank and I) never saw that
problem before.

@IBM: Is the someone at IBM who wants to help solving the problem?

Thomas.

Am 17.09.2018 um 17:06 schrieb Raisor, Kevin:
I do find several versions that come up. Do they load in any
particular order or is the order on the screen where I do the
Ctrl+Shift+T? Is there a way to see which one is valid?

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
Thomas Raddatz
Sent: Monday, September 17, 2018 4:50 AM
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries
Subject: Re: [WDSCI-L] iSphere Journal Explorer Error

Kevin,

Sorry for the late reply. I was on vacation last week. I assume that
this message is closely related to your message "Re: [WDSCI-L] iSphere
3.5.0.b007" from August 31th, 2018, 3:52 p.m.

Sadly I still have no idea, why your RDi (apparently) loads a
different version of the IBM Java Toolbox library.

Please let me know, what you get when you try to open the Java type
"ProgramParameter" like this:

a) Start RDi and open the "Plug-in Development" perspective (Window
-> Perspective -> Open Perspective -> Other... -> "Plug-in
Development").
b) Press Ctrl-Shift-T to open the "Open Type" window (or Navigate ->
Open Type...).
c) Enter "ProgramParameter".

Now you should see the list of "ProgramParameter" classes that are
available in your RDi. There should be the following entries:

ProgramParameter - com.ibm.as400.access - c:/Program

Files/IBM/SDPShared/plugins/com.ibm.etools.iseries.toolbox_8.5.6002.v
2 0180411_1437/runtime/jt400.jar ProgramParameter -
com.ibm.as400.access
- iSphere 5250 Emulator Base Plugin (RDi)/lib/jt400.jar

Maybe that it helps to export the Eclipse error log. For that you
should:

a) Delete all entries from the Eclipse error log.
b) Restart RDi.
c) Recreate the error.
d) Export the log.
e) Send the exported log data to me.

Thomas.

-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Raisor, Kevin
Gesendet: Mittwoch, 12. September 2018 14:11
An: 'Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries'
Betreff: [WDSCI-L] iSphere Journal Explorer Error

Sorry, I previously reported this under the wrong title.


I'm receiving the following error when using the Journal Explorer


eclipse.buildId=unknown
java.fullversion=8.0.5.15 - pwa6480sr5fp15-20180502_01(SR5 FP15) JRE
1.8.0 Windows 7 amd64-64 Compressed References 20180425_385365 (JIT
enabled, AOT enabled)
OpenJ9 - a7ffbfe
OMR - a531219
IBM - 59ef3dc
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product
com.ibm.rational.developer.ibmi.product.ide
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product
com.ibm.rational.developer.ibmi.product.ide
biz.isphere.core
Error
Tue Sep 11 10:59:22 EDT 2018
*** Error in method JournalExplorerView.createJournalTab(3) ***

java.lang.NoClassDefFoundError:
com/ibm/as400/access/ProgramParameter
at
biz.isphere.core.internal.api.APIProgramCallDocument.produceIntegerParameter
(APIProgramCallDocument.java:175)
at
biz.isphere.journalexplorer.core.api.retrievefielddescription.IQDBRTVFD.createParameterList
(IQDBRTVFD.java:189)
at
biz.isphere.journalexplorer.core.api.retrievefielddescription.IQDBRTVFD.retrieveFieldDescriptions
(IQDBRTVFD.java:171)
at
biz.isphere.journalexplorer.core.api.retrievefielddescription.IQDBRTVFD.retrieveFieldDescriptions
(IQDBRTVFD.java:145)
at
biz.isphere.journalexplorer.core.api.retrievefielddescription.IQDBRTVFD.retrieveFieldDescriptions
(IQDBRTVFD.java:129)
at
biz.isphere.journalexplorer.core.api.retrievefielddescription.IQDBRTVFD.retrieveFieldDescriptions
(IQDBRTVFD.java:115)
at
biz.isphere.journalexplorer.core.model.dao.MetaTableDAO.retrieveColumnsMetaData
(MetaTableDAO.java:36)
at
biz.isphere.journalexplorer.core.model.MetaDataCache.loadMetadata
(MetaDataCache.java:85)
at
biz.isphere.journalexplorer.core.model.MetaDataCache.loadMetadata
(MetaDataCache.java:54)
at
biz.isphere.journalexplorer.core.model.MetaDataCache.retrieveMetaData
(MetaDataCache.java:39)
at
biz.isphere.journalexplorer.core.model.OutputFile.getType
(OutputFile.java:41)
at
biz.isphere.journalexplorer.core.ui.widgets.JournalEntriesViewerForOutputFiles.createTableViewer
(JournalEntriesViewerForOutputFiles.java:89)
at
biz.isphere.journalexplorer.core.ui.widgets.AbstractJournalEntriesViewer.initializeComponents
(AbstractJournalEntriesViewer.java:80)
at biz.isphere.journalexplorer.core.ui.widgets.
JournalEntriesViewerOutputFiles.<init>
(JournalEntriesViewerForOutputFiles.java:81)
at
biz.isphere.journalexplorer.core.ui.views.JournalExplorerView.createJournalTab
(JournalExplorerView.java:217)
at
biz.isphere.journalexplorer.core.ui.views.JournalExplorerView.access$4
(JournalExplorerView.java:211)
at
biz.isphere.journalexplorer.core.ui.views.JournalExplorerView
$2.postRunAction(JournalExplorerView.java:141)
at
biz.isphere.journalexplorer.core.ui.actions.OpenJournalOutfileAction.run
(OpenJournalOutfileAction.java:45)
at org.eclipse.jface.action.Action.runWithEvent
(Action.java:473)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection
(ActionContributionItem.java:565)
at
org.eclipse.jface.action.ActionContributionItem.lambda$5
(ActionContributionItem.java:436)
at
org.eclipse.jface.action.ActionContributionItem$$Lambda
$43.0000000019C14950.handleEvent(Unknown
Source)
at org.eclipse.swt.widgets.EventTable.sendEvent
(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent
(Display.java:4418)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4236)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824)
at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run
(PartRenderingEngine.java:1121)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault
(Realm.java:336)
at
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run
(PartRenderingEngine.java:1022)
at
org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI
(E4Workbench.java:150)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault
(Realm.java:336)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench
(Workbench.java:610)
at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start
(IDEApplication.java:138)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run
(EclipseAppHandle.java:196)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication
(EclipseAppLauncher.java:134)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start
(EclipseAppLauncher.java:104)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:388)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:90)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.equinox.launcher.Main.invokeFramework
(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)

--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post
a
message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l

or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at

https://archive.midrange.com/wdsci-l
.


--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l

or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at

https://archive.midrange.com/wdsci-l
.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l

or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l
.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution, or
reliance on any of it by anyone else is prohibited and may be a
criminal offence. Please delete if obtained in error and email
confirmation to the sender.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l

or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l
.

--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l

or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l
.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.