Home » Eclipse Projects » Equinox » Headless Equinox 3.1/OSGI Application with ala carte Eclipse 3.1 Plugins
| Headless Equinox 3.1/OSGI Application with ala carte Eclipse 3.1 Plugins [message #53523] |
Sun, 20 November 2005 20:25  |
 jekika
Messages: 3
Registered: July 2009 |
Junior Member |
|
|
I bought Jeff & Jean-Michel's new book, Eclipse RCP (Oct '05) [it's great!]
and read the OSGI Spec V3.0, and went over the Eclipse and Equinox sites.
Huge amount of great code to puruse - please point me in the right
direction.
Want to add the OSGI FX [I'm new to this] to our architecture to enable
installing and updating dozens of non-Eclipse tools from a BEA WebLogic
AppServer to a JBuilder application on the Clients. Our requirements
include: a single, shared, persistent JVM on the Client [OSGI}; JBuilder
Enterprise IDE [not Eclipse]; BEA WebLogic AppServer [OSGI deploy issue?];
packaging/deploying 3rd party vendor tools [think I got this]; and no user
interaction for updating [possible?].
OSGI Spec says you need a Remote Manager/Client Side Management Agent for
deployment/updating. Was going to use Java WebStart, but SUN tech support
said that each update download starts up its own instance of a JVM and waits
to load the new version until the user starts it up again. Quest
DeployDirector had the same scenario. If OSGI says the updates are done
behind the scenes at the class level in a single, shared JVM; and Eclipse
uses WebStart as a deployment strategy - what am I not catching on to? As
all our tools are running in a single JVM, if one tool goes down or restarts
the JVM, everything goes down.
I'm trying to figure out how much Eclipse libs [loosely coupled to Eclipse
IDE?] I can use on top of the Equinox implementation of OSGI within
JBuilder. Since I'm stuck using JBuilder, I want to bring in Eclipse libs
ala carte (like update). Can you do a headless update?
Can you put THE APP implementation of IPlatformRunnable in the JBuilder app?
Would have tried this by now, but EIT has not yet installed JB (been
weeks!).
Thanks for any, and all, thoughts,
Jessica
|
|
|
| Re: Headless Equinox 3.1/OSGI Application with ala carte Eclipse 3.1 Plugins [message #54009 is a reply to message #53523] |
Fri, 02 December 2005 02:18  |
Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
Jessica,
Thanks for the book plug :-)
I'm actually having a bit of trouble following what you are asking. Seems
like there are a lot of things mixed together here. Can you break it down a
bit?
Jeff
"Jekika" <jascough@harris.com> wrote in message
news:dlqm3q$j5$1@news.eclipse.org...
> I bought Jeff & Jean-Michel's new book, Eclipse RCP (Oct '05) [it's
great!]
> and read the OSGI Spec V3.0, and went over the Eclipse and Equinox sites.
> Huge amount of great code to puruse - please point me in the right
> direction.
>
> Want to add the OSGI FX [I'm new to this] to our architecture to enable
> installing and updating dozens of non-Eclipse tools from a BEA WebLogic
> AppServer to a JBuilder application on the Clients. Our requirements
> include: a single, shared, persistent JVM on the Client [OSGI}; JBuilder
> Enterprise IDE [not Eclipse]; BEA WebLogic AppServer [OSGI deploy issue?];
> packaging/deploying 3rd party vendor tools [think I got this]; and no user
> interaction for updating [possible?].
>
> OSGI Spec says you need a Remote Manager/Client Side Management Agent for
> deployment/updating. Was going to use Java WebStart, but SUN tech support
> said that each update download starts up its own instance of a JVM and
waits
> to load the new version until the user starts it up again. Quest
> DeployDirector had the same scenario. If OSGI says the updates are done
> behind the scenes at the class level in a single, shared JVM; and Eclipse
> uses WebStart as a deployment strategy - what am I not catching on to? As
> all our tools are running in a single JVM, if one tool goes down or
restarts
> the JVM, everything goes down.
>
> I'm trying to figure out how much Eclipse libs [loosely coupled to Eclipse
> IDE?] I can use on top of the Equinox implementation of OSGI within
> JBuilder. Since I'm stuck using JBuilder, I want to bring in Eclipse libs
> ala carte (like update). Can you do a headless update?
>
> Can you put THE APP implementation of IPlatformRunnable in the JBuilder
app?
> Would have tried this by now, but EIT has not yet installed JB (been
> weeks!).
>
> Thanks for any, and all, thoughts,
>
> Jessica
>
>
|
|
|
| Re: Headless Equinox 3.1/OSGI Application with ala carte Eclipse 3.1 Plugins [message #54111 is a reply to message #54009] |
Fri, 02 December 2005 15:36 |
jekika
Messages: 3
Registered: July 2009 |
Junior Member |
|
|
Hey Jeff;
I have dozens of 3rd party tools (delivered to me as JARs) that our main GUI
application (done in JBuilder) must install and update. My goal is to have
this JBuilder main GUI application run on the Equinox Framework and to
bundle the 3rd party tools as OSGI plugins for use.
1) For new tool plugins I'm using the Eclipse 3.2 IDE to bundle them
targeting OSGI Equinox. They run in the console provided by the IDE (very
cool), but do not run on the cmd prompt outside of the IDE
(ClassNotFoundException-invalid Activator class). Also I'm having trouble
getting the "Plugin as a JAR" dir structure (mine doesn't look like the
book's Ch 20, Fig 20-1).
a) I haven't tried wrapping the 3rd party tool plugins yet.
2) For the JBuilder main GUI application, I'm confused how to integrate with
Equinox and the OSGI Framework. I can't get the following options to work
[run versus main].
a) Should the class implementing IRunnablePlatform call the JBuilder
main( ) to launch the JBuilder GUI from its run() method?
b) Or should the JBuilder main( ) call the IRunnablePlatform run( )?
c) For the main application, do you need an activator for the JBuilder
code? or just the IRunnablePlatform implementation?
d) Or am I approaching this wrong? Does the main application need to be
treated as a 3rd party plugin because it was not made with Eclipse IDE?
e) Any options to starting Equinox programmatically from the main
application versus manually on the cmd prompt?
The reason to use Equinox is to be able to have all the tool plugins and app
run in a single JVM and have the plugin install/update features of OSGI.
Eventually, once I get this under control, I'll try to have the AppServer
remotely install and download tool plugin updates to all of the
workstations.
Thank you for your patience, I'm trying to figure out the right questions to
ask.
Jessica
"Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
news:dmoatt$nt8$1@news.eclipse.org...
> Jessica,
>
> Thanks for the book plug :-)
>
> I'm actually having a bit of trouble following what you are asking. Seems
> like there are a lot of things mixed together here. Can you break it down
> a
> bit?
>
> Jeff
>
> "Jekika" <jascough@harris.com> wrote in message
> news:dlqm3q$j5$1@news.eclipse.org...
>> I bought Jeff & Jean-Michel's new book, Eclipse RCP (Oct '05) [it's
> great!]
>> and read the OSGI Spec V3.0, and went over the Eclipse and Equinox sites.
>> Huge amount of great code to puruse - please point me in the right
>> direction.
>>
>> Want to add the OSGI FX [I'm new to this] to our architecture to enable
>> installing and updating dozens of non-Eclipse tools from a BEA WebLogic
>> AppServer to a JBuilder application on the Clients. Our requirements
>> include: a single, shared, persistent JVM on the Client [OSGI}; JBuilder
>> Enterprise IDE [not Eclipse]; BEA WebLogic AppServer [OSGI deploy
>> issue?];
>> packaging/deploying 3rd party vendor tools [think I got this]; and no
>> user
>> interaction for updating [possible?].
>>
>> OSGI Spec says you need a Remote Manager/Client Side Management Agent for
>> deployment/updating. Was going to use Java WebStart, but SUN tech support
>> said that each update download starts up its own instance of a JVM and
> waits
>> to load the new version until the user starts it up again. Quest
>> DeployDirector had the same scenario. If OSGI says the updates are done
>> behind the scenes at the class level in a single, shared JVM; and Eclipse
>> uses WebStart as a deployment strategy - what am I not catching on to? As
>> all our tools are running in a single JVM, if one tool goes down or
> restarts
>> the JVM, everything goes down.
>>
>> I'm trying to figure out how much Eclipse libs [loosely coupled to
>> Eclipse
>> IDE?] I can use on top of the Equinox implementation of OSGI within
>> JBuilder. Since I'm stuck using JBuilder, I want to bring in Eclipse
>> libs
>> ala carte (like update). Can you do a headless update?
>>
>> Can you put THE APP implementation of IPlatformRunnable in the JBuilder
> app?
>> Would have tried this by now, but EIT has not yet installed JB (been
>> weeks!).
>>
>> Thanks for any, and all, thoughts,
>>
>> Jessica
>>
>>
>
>
|
|
|
| Re: Headless Equinox 3.1/OSGI Application with ala carte Eclipse 3.1 Plugins [message #54632 is a reply to message #54111] |
Mon, 12 December 2005 22:58 |
| Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
"Jekika" <jascough@harris.com> wrote in message
news:dmpplh$pol$1@news.eclipse.org...
> Hey Jeff;
>
> I have dozens of 3rd party tools (delivered to me as JARs) that our main
GUI
> application (done in JBuilder) must install and update. My goal is to
have
> this JBuilder main GUI application run on the Equinox Framework and to
> bundle the 3rd party tools as OSGI plugins for use.
>
> 1) For new tool plugins I'm using the Eclipse 3.2 IDE to bundle them
> targeting OSGI Equinox. They run in the console provided by the IDE (very
> cool), but do not run on the cmd prompt outside of the IDE
> (ClassNotFoundException-invalid Activator class).
The CNFE is likely a result of not finding some other class that is needed
by your Activator or you have not packaged it up correctly. Look at you
build.properties to ensure that everything you want in the deployed bundle
is mentioned somehow in the binary section of the build.properties.
> Also I'm having trouble
> getting the "Plugin as a JAR" dir structure (mine doesn't look like the
> book's Ch 20, Fig 20-1).
This is likely related to the build.properties as noted above.
> a) I haven't tried wrapping the 3rd party tool plugins yet.
>
> 2) For the JBuilder main GUI application, I'm confused how to integrate
with
> Equinox and the OSGI Framework. I can't get the following options to work
> [run versus main].
> a) Should the class implementing IRunnablePlatform call the JBuilder
> main( ) to launch the JBuilder GUI from its run() method?
> b) Or should the JBuilder main( ) call the IRunnablePlatform run( )?
> c) For the main application, do you need an activator for the JBuilder
> code? or just the IRunnablePlatform implementation?
Sorry but I don't know what JBuilder does or how it is structured. I would
suggest that you start with a) as this puts OSGi on the bottom.
> d) Or am I approaching this wrong? Does the main application need to be
> treated as a 3rd party plugin because it was not made with Eclipse IDE?
no
> e) Any options to starting Equinox programmatically from the main
> application versus manually on the cmd prompt?
Yes. Look at the class EclipseStarter in the OGSi bundle. It has methods
for starting and stopping the framework. Note that we are redesigning some
of this to make is easier/better.
Jeff
|
|
| |
| Re: Headless Equinox 3.1/OSGI Application with ala carte Eclipse 3.1 Plugins [message #57512 is a reply to message #54922] |
Tue, 24 January 2006 03:37 |
| Eclipse User |
|
|
|
Originally posted by: jeff_nospam_mcaffer.ca.ibm.com
You can list the bundles you want to start by creating a config.ini in the
configuration directory and listing the bundles in the osgi.bundles
property. For examples, look at the config.ini that ships with Eclipse.
Jeff
"Jekika" <jascough@harris.com> wrote in message
news:dnmkdq$a36$1@news.eclipse.org...
> Hey Jeff;
> The following throws a null pointer exception at
> LocationManager.getOSGiConfigurationDir; getConfigurationFile; etc.
>
> String[] s = {"\\LoginViewerPlugin\\jbPlugin.jar"};
>
> try {
> EclipseStarter.startup(s, null);
> } catch (Exception e) {
> e.printStackTrace();
> }
>
> Do I need code to create a config file? I thought that was done
> automatically. If so, where could I find a template for config.ini? If I
> am to use update.configurator, is there any example or tutuorial to get me
> going?
>
> I just want to start the framework and run bundles in that single JVM.
> Being able to update and add new bundles would be a plus. Can you give me
a
> code snippet to work with? I don't know how much of this is done
internally
> by equinox/OSGi or what I need to do.
> ----------------------------------------------------------
> "Jeff McAffer" <jeff_nospam_mcaffer@ca.ibm.com> wrote in message
> news:dnkva7$2gr$1@news.eclipse.org...
> >
> > "Jekika" <jascough@harris.com> wrote in message
> > news:dmpplh$pol$1@news.eclipse.org...
> >> Hey Jeff;
> >>
> >> I have dozens of 3rd party tools (delivered to me as JARs) that our
main
> > GUI
> >> application (done in JBuilder) must install and update. My goal is to
> > have
> >> this JBuilder main GUI application run on the Equinox Framework and to
> >> bundle the 3rd party tools as OSGI plugins for use.
> >>
> >> 1) For new tool plugins I'm using the Eclipse 3.2 IDE to bundle them
> >> targeting OSGI Equinox. They run in the console provided by the IDE
> >> (very
> >> cool), but do not run on the cmd prompt outside of the IDE
> >> (ClassNotFoundException-invalid Activator class).
> >
> > The CNFE is likely a result of not finding some other class that is
needed
> > by your Activator or you have not packaged it up correctly. Look at you
> > build.properties to ensure that everything you want in the deployed
bundle
> > is mentioned somehow in the binary section of the build.properties.
> >
> >> Also I'm having trouble
> >> getting the "Plugin as a JAR" dir structure (mine doesn't look like the
> >> book's Ch 20, Fig 20-1).
> >
> > This is likely related to the build.properties as noted above.
> >
> >> a) I haven't tried wrapping the 3rd party tool plugins yet.
> >>
> >> 2) For the JBuilder main GUI application, I'm confused how to integrate
> > with
> >> Equinox and the OSGI Framework. I can't get the following options to
work
> >> [run versus main].
> >> a) Should the class implementing IRunnablePlatform call the JBuilder
> >> main( ) to launch the JBuilder GUI from its run() method?
> >> b) Or should the JBuilder main( ) call the IRunnablePlatform run( )?
> >> c) For the main application, do you need an activator for the JBuilder
> >> code? or just the IRunnablePlatform implementation?
> >
> > Sorry but I don't know what JBuilder does or how it is structured. I
> > would
> > suggest that you start with a) as this puts OSGi on the bottom.
> >
> >> d) Or am I approaching this wrong? Does the main application need to
be
> >> treated as a 3rd party plugin because it was not made with Eclipse IDE?
> >
> > no
> >
> >> e) Any options to starting Equinox programmatically from the main
> >> application versus manually on the cmd prompt?
> >
> > Yes. Look at the class EclipseStarter in the OGSi bundle. It has
methods
> > for starting and stopping the framework. Note that we are redesigning
> > some
> > of this to make is easier/better.
> >
> > Jeff
> >
> >
>
>
|
|
|
Goto Forum:
Current Time: Fri Apr 26 15:43:38 GMT 2024
Powered by FUDForum. Page generated in 0.04011 seconds |
] 
Search
Help
Register
Login
Home
