| war deployment, configurator and starting services? [message #128088] |
Thu, 16 April 2009 08:55  |
 Kristian Rink
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  |
Rüdiger Herrmann
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
|
|
|
|
Powered by
FUDForum. Page generated in 0.03183 seconds
] 
Search
Help
Register
Login
Home
