[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [virgo-dev] Starting bundles automatically using plans

Hmmm. Something's gone wrong it seems. Please paste the event log messages or, equivalently the console and we'll take a look.

You may like to look for exceptions in serviceability/logs/log.log too in case of some serious failure.

Regards,
Glyn

On 28 Oct 2010, at 13:33, Florian Waibel wrote:

Reading https://bugs.eclipse.org/bugs/show_bug.cgi?id=324445 I see you are deploying by dropping the plan into pickup. This should start the plan after installing it. What is the state of the plan as shown by:

osgi> plan list


osgi> vsh plan list

Name                                         Version                       State
org.eclipse.virgo.kernel.userregion.springdm 2.1.0                        ACTIVE
vigo-equinox-extensions                      3.6.1                      STARTING
virgo-rap-demo                               1.3.1                      STARTING
virgo-rap-extensions                         1.3.1                      STARTING

STARTING ?!

That's what i did so far:

Add the required bundles and the two plans vi[r]go-*-extensions  :-) into the ${SERVER_HOME}/repository/usr  -
then a third plan containing these three artifacts:

<artifact type="plan" name="vigo-equinox-extensions" version="[3.6.1, 4.0.0)" />
<artifact type="plan" name="virgo-rap-extensions" version="[1.3.1, 2.0.0)" />
<artifact type="bundle" name="org.eclipse.rap.demo" version="[1.3.1, 2.0.0)" />

into the pickup directory.

?

Perhaps this is an effect of lazy start??

Regards,
Glyn

On 28 Oct 2010, at 13:14, Glyn Normington wrote:

Hi Florian

I'm afraid not.

There is no "vsh deploy" subcommand which would achieve the equivalent result to using the admin console in the Virgo web server. so maybe we should add one. Feel free to log an enhancement bug.

However, you can start the plan after installing it:

osgi> vsh plan start <planname> <planversion>

Better than nothing I guess. Shame we don't have tab completion for the Equinox console (extension) yet.

Regards,
Glyn

On 28 Oct 2010, at 12:42, Florian Waibel wrote:

Hi,

today i prepared a plan to run RAP applications on Virgo Kernel. This plan includes

<artifact type="bundle" name="org.eclipse.equinox.http.jetty" version="[2.0.0, 3.0.0)" />

providing an OSGi HTTP Service. After the deployment the bundle is lazy...

osgi> ss
...
33 <<LAZY>>    org.eclipse.equinox.http.jetty_2.0.0.v20100503
...

osgi> services (objectClass=*HttpService)
No registered services.


Starting the HttpService manually works fine. The RAP workbench is now using the HttpService:

osgi> start 33

osgi> services (objectClass=*HttpService)
{org.osgi.service.http.HttpService, org.eclipse.equinox.http.servlet.ExtendedHttpService}={service.description=Equinox Jetty-based Http Service, service.vendor=Eclipse.org, http.port=10081, service.id=74}
Registered by bundle: org.eclipse.equinox.http.servlet_1.1.0.v20100503 [32]
Bundles using service:
  org.eclipse.equinox.http.registry_1.1.0.v20100503 [31]
  org.eclipse.rap.ui.workbench_1.3.1.20100915-2301 [37]


Is there a way to start a bundle during deployment? I can't find
a tag startup="true" or something alike in the documentation.

Thanks a lot,
Florian

<ATT00001..txt>

_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx<mailto:virgo-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/virgo-dev

_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx<mailto:virgo-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/virgo-dev

<ATT00001..txt>