Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » war deployment, configurator and starting services?
war deployment, configurator and starting services? [message #128088] Thu, 16 April 2009 08:55 Go to next message
Kristian Rink is currently offline Kristian RinkFriend
Messages: 64
Registered: July 2009
Member
Folks;

so far I've been using the webappBuilder.xml script in order to get our
application packaged to a .war file and deployed to some app server (running
tomcat at the moment, exporting it as an Eclipse installation using jetty
unfortunately is no option as the target platform is a Sun/Solaris x86
machine which obviously so far is not supported by core Eclipse components
like the Equinox launcher). For what I see, most of this works pretty well,
except for one thing: I see that

org.eclipse.update.configurator@start in config.ini

is responsible for starting the plugins that come with the .war'ed RAP
application. So to ask: Are there any limitations to this approach? In our
environment in example, our RAP app contains Equinox DS and some loosely
coupled services which never seem to be started at all except for
explicitely listing them in config.ini manually, which, as I do had to learn
by now, is a horrid pain even given a small application, as I somehow never
managed to get them started the right order... Is there a way of getting out
of this mess?

TIA and all the best,
Kristian

[1] http://rapblog.innoopract.com/2007/12/rap-deployment-part-2- deploying-your.html
Re: war deployment, configurator and starting services? [message #128484 is a reply to message #128088] Fri, 17 April 2009 14:41 Go to previous messageGo to next message
Rüdiger Herrmann is currently offline Rüdiger HerrmannFriend
Messages: 581
Registered: July 2009
Senior Member
Kristian,

the preferred way is not to use update.configurator but instead
specify all bundles in the config.ini.

Don't forget to list the
org.eclipse.equinox.servletbridge.extensionbundle fragment. It is
generated by the servlet bridge and as far as I recall the reason
why using update.configurator does not work reliably.

Do you specify the start level explicitly? Try it without doing so.
Equinox should resolve the bundles in the right order. I doubt that
DS have extra requirements regarding the start order, though I don't
know for sure. What exactly isn't resolved?

HTH
Rüdiger

Kristian Rink wrote:
> Folks;
>
> so far I've been using the webappBuilder.xml script in order to get our
> application packaged to a .war file and deployed to some app server (running
> tomcat at the moment, exporting it as an Eclipse installation using jetty
> unfortunately is no option as the target platform is a Sun/Solaris x86
> machine which obviously so far is not supported by core Eclipse components
> like the Equinox launcher). For what I see, most of this works pretty well,
> except for one thing: I see that
>
> org.eclipse.update.configurator@start in config.ini
>
> is responsible for starting the plugins that come with the .war'ed RAP
> application. So to ask: Are there any limitations to this approach? In our
> environment in example, our RAP app contains Equinox DS and some loosely
> coupled services which never seem to be started at all except for
> explicitely listing them in config.ini manually, which, as I do had to learn
> by now, is a horrid pain even given a small application, as I somehow never
> managed to get them started the right order... Is there a way of getting out
> of this mess?
>
> TIA and all the best,
> Kristian
>
> [1] http://rapblog.innoopract.com/2007/12/rap-deployment-part-2- deploying-your.html
Re: war deployment, configurator and starting services? [message #132252 is a reply to message #128484] Mon, 11 May 2009 13:41 Go to previous message
Kristian Rink is currently offline Kristian RinkFriend
Messages: 64
Registered: July 2009
Member
Hi Rüdiger;

Rüdiger Herrmann schrieb:
> Don't forget to list the
> org.eclipse.equinox.servletbridge.extensionbundle fragment. It is
> generated by the servlet bridge and as far as I recall the reason why
> using update.configurator does not work reliably.

Using config.ini along with the somewhat arcane ConfigIniCreator class
provided by the demo.feature project seems to have resolved most of my
problems and indeed makes my application deploy and start correctly again.
Thanks for the pointers on that, much appreciated. :)

Cheers,
Kristian
(still hoping for a pain-free way of deploying RAP applications one day...)
Previous Topic:Table right click selection does not set selection
Next Topic:war deployment: java.lang.LinkageError?
Goto Forum:
  


Current Time: Wed Feb 01 23:44:48 GMT 2023

Powered by FUDForum. Page generated in 0.11297 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top