| Re: [ice-dev] ICE ConnectCoreAction Usage |
Ram,
Once upon a time, that action was used to connect an ICEClient to an instance of the ICECore other than its own, locally or remotely. I disabled it, but kept the code for reference, because I wanted to move to a full web interface.
This particular code uses the RemoteCoreProxy, which has some bugs related to memory. It is also only partially implemented and does not completely processx workflows. If I were going to do this again today, I would publish the ICECore as a remote OSGI service, which automatically proxies the memory correctly.
So let me know what you are doing exactly and we can look into it. If you are playing, let's fire up the ConnectCoreAction. If you want something that is production quality, let's look at a remote OSGI service.
What do you think?
Jay
Hello ICE-Dev,As part of my work, I am trying to investigate how I can start up an ICEClient and have it connect to an ICECore separately, say, from different machines.I have been looking around in the ICE Source code and I came acrossorg.eclipse.ice.client.common.ConnectCoreAction This seems to have the relevant functions of interest (ConnectCoreAction constructor). But it has references to IWorkbenchWindow and I was wondering how I would trigger this function. I have only used ICE and I am wondering if I should so something specific from the Eclipse Workbench view so that this function is called.Hope this description helps. Please let me know if you need more information.Thanking You,--Ramachandran K. NarayananSoftware EngineerRNET Technologies Inc.240 W.Elmwood Drive, Suite 2010Dayton, OH 45459-4248
_______________________________________________
ice-dev mailing list
ice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-dev