| plugin startup configuration [message #71211] |
Tue, 01 August 2006 16:21  |
Eclipse User |
|
|
|
Originally posted by: duncan.krebsnet.com
Hi,
First I just want to say thank you to the folks who have been working in
the incubator. With some help I've got a working platform that includes a
port of JSF, AXIS as well as a way to define jsp folders off the plugin
root and map the real path to a virtual path in the browser. Now I'm
working on a higher level templating system that can reference jsps by
their virtual paths, good stuff.
One detail however that is really starting to bug me is the fact that the
plugin that handles the jsp mapping always has to be manually started in
the OSGI console using the start command. I've tried everything from
changing the start-level to a lower and higher number, to removing the
eclipse-lazystart property in the manifest, to changing the value in the
launch configuration to say true to launch. But for the life of me, when I
start the OSGI configuration the bundle's initial state is always set to
RESOLVED and not ACTIVE. It seems to be doing this on 2 plugins in my code
and I'm wondering if anyone has any ideas. - Duncan
|
|
|
|
|
| Re: plugin startup configuration [message #71449 is a reply to message #71316] |
Thu, 03 August 2006 14:24  |
| Eclipse User |
|
|
|
Duncan Krebs wrote:
> Thanks, I simply added the @start after the plugin name in the launch
> configuration and it worked. I might be missing something but I could
> not find a way to achieve the @start configuration for a plugin using
> the dialog editor in the Run.. menu. It would either do @:true or
> @1:default if the start level was changed and the start option will set
> true,default or false but never start, although now I don't care!
This sounds like a bug in PDE-UI. Can you please open a bug against
PDE-UI. It should not stick stuff like @1:default or @:true in the
generated config.ini.
Tom.
|
|
|
Powered by
FUDForum. Page generated in 0.07604 seconds
Home