Re: Problems with org.eclipse.rse.core.subsystemConfigurations

Doug,

of course the activator class of the plugin would be the best place for this
code. The problem is, that in this case method getHosts() in ISystemProfile
doesn`t return the instances of IHost. The array is always empty. Not before
the RSE view will be displayed the method getHosts() will return the
instances of IHost. Therefore I have added a tool item in the RSE view. The
user has to press the tool item once and the subsystems will be created. Not
the best, but more than nothing.

If you want to implement it in the activator class you could at first force
the RSE view to be displayed by
PlatformUI.getWorkbench().getActiveWorkbenchWindow().getActivePage().showVie
w("ID of RSE View"). After this implement the snippet. I havn`t tested this,
but it could work.

Frank




-----Ursprüngliche Nachricht-----
Von: wdsc-plugin-dev-bounces@xxxxxxxxxxxx
[mailto:wdsc-plugin-dev-bounces@xxxxxxxxxxxx] Im Auftrag von Doug Davie
Gesendet: Montag, 19. Januar 2009 15:06
An: WDSC Plugin Developers
Betreff: Re: [Wdsc-Plugin-Dev] Problems with
org.eclipse.rse.core.subsystemConfigurations

Frank,
Where did you put this code?
Is it part of the plugin Activator? Or part of the subsystem extension
element class?
(just looking for suggestions on the best location for it)
Thanks
-doug

On Wed, Jan 7, 2009 at 4:48 PM, Frank Hildebrandt <
frank.hildebrandt@xxxxxxxxxxxxxxx> wrote:

Hi,

here`s a snippet, which checks, if the subsystem exists in a connection.
If not then it will be created programmatically.

ISystemRegistry sr = SystemStartHere.getSystemRegistry();
ISubSystemConfiguration ssc =

sr.getSubSystemConfiguration("de.taskforce.tn5250j.rse.subsystems.TN5250JSub

SystemConfiguration");
ISystemProfile[] sp =
sr.getSystemProfileManager().getSystemProfiles();
for (int idx1 = 0; idx1 < sp.length; idx1 ++) {
IHost[] host = sp[idx1].getHosts();
for (int idx2 = 0; idx2 < host.length; idx2++) {
if

(host[idx2].getSystemType().getId().equals(IRSESystemType.SYSTEMTYPE_ISERIES

_ID)) {
boolean exist = false;
ISubSystem[] ss =
host[idx2].getSubSystems();
for (int idx3 = 0; idx3 <

ss.length;

idx3++) {
if
(ss[idx3].getSubSystemConfiguration() == ssc) {
exist = true;
break;
}
}
if (!exist) {

ssc.createSubSystem(host[idx2], true, null);
sr.fireEvent(new
SystemResourceChangeEvent(host[idx2],
ISystemResourceChangeEvents.EVENT_REFRESH, host[idx2]));
host[idx2].commit();
}
}
}
}



-----Ursprüngliche Nachricht-----
Von: wdsc-plugin-dev-bounces@xxxxxxxxxxxx
[mailto:wdsc-plugin-dev-bounces@xxxxxxxxxxxx] Im Auftrag von Doug Davie
Gesendet: Mittwoch, 7. Januar 2009 21:07
An: WDSC Plugin Developers
Betreff: Re: [Wdsc-Plugin-Dev] Problems with
org.eclipse.rse.core.subsystemConfigurations

Frank,

I've noticed the same behavior... Newly defined subsystems only appear

in

newly created connections, not in existing connections.

What is your alternative solution?


-doug



On Wed, Jan 7, 2009 at 2:59 PM, Frank Hildebrandt <
frank.hildebrandt@xxxxxxxxxxxxxxx> wrote:

Hi David,

my subsystem doesn`t depend on preferences. And the workspace has not

been

migrated.
Perhaps is has something to do, that the subsystem doesn`t support

filters.

I don`t know.
But I have found an alternative solution.

Thanks

Frank



-----Ursprüngliche Nachricht-----
Von: wdsc-plugin-dev-bounces@xxxxxxxxxxxx
[mailto:wdsc-plugin-dev-bounces@xxxxxxxxxxxx] Im Auftrag von David Gibbs
Gesendet: Mittwoch, 7. Januar 2009 20:52
An: WDSC Plugin Developers
Betreff: Re: [Wdsc-Plugin-Dev] Problems with
org.eclipse.rse.core.subsystemConfigurations

Frank Hildebrandt wrote:

When I create a new connection in the RSE View i can see my subsystem

under

the new created connection.

But under the existing connections i cannot see my subsystem.

Does your subsystem depend on any preferences?

When RSE (7.5) migrates preferences of a workspace, it does not migrate

any

preferences for subsystems that are installed AFTER RDI is installed.

david

--
IBM i on Power - 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.

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