Thank you Frank.
I thought that I might have to write my own "open member" routine, but I
wanted to avoid that if I could because my skills are not up to scratch
yet.
A question on your source code snippet that you have included: How do I
find the "shell" in the parameters of getISeriesMember? I stumbled over
this point before, and I couldn't get help from WDSC because it thought
I wanted help on unix shells.
Paul.
-----Original Message-----
From: wdsc-plugin-dev-bounces@xxxxxxxxxxxx
[mailto:wdsc-plugin-dev-bounces@xxxxxxxxxxxx] On Behalf Of
frank.hildebrandt@xxxxxxxxxxxxxxx
Sent: 16 April 2008 10:39
To: WDSC Plugin Developers
Subject: Re: [Wdsc-Plugin-Dev] RSE Connection name
Hi,
every iseries member opened in the Lpex editor will be described by
the class "ISeriesMember". This class provides a method to retrieve
the ISeriesConnection witch is assigned to the ISeriesMember.
I assume, that you have created an Lpex action and the doCommand
method provides only the parameter LpexView. And this exactly the
problem. There is no way to get the ISeriesMember witch is assoziated
with the LpexView, if the only information you have is the
LpexView.
I had the same problem. The solution was not to open a member with
the standard RSE menu items. I have written my own class witch opens
the member. Then i store the ISeriesMember in the window object,
witch is assoziated with the LpexView.
Here is the code for the first step.
ISeriesMember member iSeriesConnection.getISeriesMember(shell,
sourceLibrary, sourceFile, member);
member.open();
LpexTextEditor editor = member.getAccess().getEditor();
LpexView view = ISeriesEditorUtilities.getPrimaryLpexView(editor);
LpexWindow window = view.window();
window.setData("*ISeriesMember", member);
When my Lpex action will be processed then i retrieve the ISeriesMember
witch i have previously stored.
Here is the code for the second step.
public void doAction(LpexView view) {
LpexWindow window = view.window();
ISeriesMember member = (ISeriesMember)window.getData("*ISeriesMember");
}
Could be, that this not very pretty, but it works and it is the only
way i have found to solve this problem
Frank
-----Ursprungliche Nachricht-----
Von: wdsc-plugin-dev-bounces@xxxxxxxxxxxx
[mailto:wdsc-plugin-dev-bounces@xxxxxxxxxxxx]Im Auftrag von Bailey Paul
Gesendet: Mittwoch, 16. April 2008 10:26
An: WDSC Plugin Developers
Betreff: Re: [Wdsc-Plugin-Dev] RSE Connection name
Hi David,
No, unfortunately all I have access to from my UserProfile plugin is the
LpexView and associated LpexWindow and LpexParser objects. I have
checked the documentation and there is no mention of any other attached
objects.
I can get the source member name very easily from the "sourceName"
editor parameter, but it seems to be impossible to get to the iSeries
connection (or at least, its name) as well.
Paul.
-----Original Message-----
From: wdsc-plugin-dev-bounces@xxxxxxxxxxxx
[mailto:wdsc-plugin-dev-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: 15 April 2008 18:30
To: WDSC Plugin Developers
Subject: Re: [Wdsc-Plugin-Dev] RSE Connection name
Bailey Paul wrote:
I want to access the RSE Connection that was used to load a source
member into lpex, preferably from an editor action or command, or from
an lpex extension point. I would like to display the connection name
somewhere and I would also like to keep a member filter up to date
with
the currently open source members.
Paul:
What objects do you have at hand to base derive the information from?
Do you have a ISeriesEditableSrcPhysicalFileMember object?
If so, you could probably use the getISeriesConnection() method and then
getSubSystems() on the connection object.
david
--
IBM System i - For when you can't afford to be out of business
--
This is the WDSC Plugin Developers (Wdsc-Plugin-Dev) mailing list
To post a message email: Wdsc-Plugin-Dev@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsc-plugin-dev
or email: Wdsc-Plugin-Dev-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsc-plugin-dev.
--
This is the WDSC Plugin Developers (Wdsc-Plugin-Dev) mailing list
To post a message email: Wdsc-Plugin-Dev@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsc-plugin-dev
or email: Wdsc-Plugin-Dev-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsc-plugin-dev.
midrange.com
