Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Riena » Export the Server Module
Export the Server Module [message #542303] Thu, 24 June 2010 13:45 Go to next message
Matthias is currently offline Matthias
Messages: 52
Registered: September 2009
Member
Hi,
i want to export a server module to run it as standalone version outside of Eclipse.
For that i created a product configuration based on my launch configuration file. In the section "Product Definition" i am asked to specify the application (default entry point) - that doesn't exist.
How do i create such an Application?

When exporting one of the example projects e.g. org.eclipse.riena.sample.app.server i don't need to specify anything in the section "Product Definition".

Matthias
Re: Export the Server Module [message #543032 is a reply to message #542303] Mon, 28 June 2010 09:08 Go to previous messageGo to next message
Matthias is currently offline Matthias
Messages: 52
Registered: September 2009
Member
I didn't find a solution yet, but i tried the following that maybe express the problem I'm facing:
I wanted to make a standalone version (product) of the PingPong Server (from the communication ping pong example)
If i run the example with the .launch configuration file the server is initialized and writes this to the console:
osgi> Mon Jun 28 10:42:24 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] org.eclipse.riena.internal.core.Activator No stage information set.
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.core.exception.IExceptionHandlerManager}={service.ranking=-100, service.id=46} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] org.eclipse.riena.internal.core.StartupsSafeRunnable Startup required bundle: 'org.eclipse.equinox.log' already started.
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.communication.sample.pingpong.common.IPingPong}={riena.remote.protocol=hessian, riena.remote.path=/PingPongWS, riena.remote=true, service.id=47} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.communication.core.IRemoteServiceRegistry}={service.ranking=-100, service.id=48} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] org.eclipse.riena.internal.communication.core.ssl.SSLConfiguration No configuration given!.
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.communication.core.progressmonitor.IRemoteProgressMonitorRegistry}={service.id=49} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.communication.core.publisher.IServicePublishBinder}={service.id=50} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] org.eclipse.riena.communication.publisher.ServicePublishBinder no publisher found for protocol hessian
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] org.eclipse.riena.internal.communication.publisher.hessian.Activator start hessian support on server
Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher] org.eclipse.riena.communication.publisher.ServicePublishBinder servicePublish=hessian REGISTER...publishing all services that were waiting for him
Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher] org.eclipse.riena.internal.communication.publisher.hessian.HessianRemoteServicePublisher published web service. protocol=hessian, url=http://10.220.6.236:8080/hessian/PingPongWS, interface=org.eclipse.riena.communication.sample.pingpong.common.IPingPong
Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher] org.eclipse.riena.internal.communication.publisher.hessian.HessianRemoteServicePublisher web service count: 1
Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher] org.eclipse.riena.communication.publisher.ServicePublishBinder service endpoints count: 1
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.communication.core.publisher.IServicePublisher}={service.ranking=-100, riena.protocol=hessian, service.id=51} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher] org.eclipse.riena.communication.publisher.hessian.RienaHessianDispatcherServlet initialized
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.equinox.http.registry.HttpContextExtensionService}={service.id=52} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.osgi.framework.console.CommandProvider}={service.id=53} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null FrameworkEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null FrameworkEvent STARTLEVEL CHANGED


Now i run the product that i have created based on that .launch configuration file and the only thing that is shown is the empty osgi console. The server bundle (see #18) is <<LAZY>>:
osgi> ss

Framework is launched.

id	State       Bundle
0	ACTIVE      org.eclipse.osgi_3.6.0.v20100301
	            Fragments=16, 25
1	ACTIVE      org.eclipse.equinox.common_3.6.0.v20100222
2	ACTIVE      org.eclipse.core.runtime_3.6.0.v20091204
3	RESOLVED    org.junit_3.8.2.v20090203-1005
4	ACTIVE      org.eclipse.core.runtime.compatibility.auth_3.2.100.v20090413
5	RESOLVED    org.eclipse.equinox.log_1.2.100.v20100118
6	ACTIVE      org.eclipse.equinox.registry_3.5.0.v20100301
7	<<LAZY>>    org.eclipse.equinox.http.jetty_2.0.0.v20090520-1800
8	RESOLVED    javax.servlet.jsp_2.0.0.v200806031607
9	<<LAZY>>    org.eclipse.core.contenttype_3.4.100.v20100301
10	RESOLVED    com.caucho.hessian_3.2.0
11	RESOLVED    org.eclipse.riena.server_2.0.0.v20100316_2_0_0_M6
12	<<LAZY>>    org.eclipse.equinox.security_1.0.200.v20100301
	            Fragments=19
13	<<LAZY>>    org.eclipse.core.net_1.2.100.I20091117-0800
14	RESOLVED    org.apache.commons.logging_1.0.4.v200904062259
15	<<LAZY>>    org.eclipse.equinox.http.servlet_1.1.0.v20100201
16	RESOLVED    org.eclipse.equinox.transforms.hook_1.0.200.v20100118
	            Master=0
17	<<LAZY>>    org.eclipse.riena.communication.factory.hessian_2.0.0.v20100316_2_0_0_M6
18	<<LAZY>>    org.eclipse.riena.communication.sample.pingpong.server_2.0.0.v20100316_2_0_0_M6
19	RESOLVED    org.eclipse.equinox.security.win32.x86_1.0.100.v20090520-1800
	            Master=12
20	ACTIVE      org.eclipse.equinox.preferences_3.3.0.v20100307
21	<<LAZY>>    org.eclipse.riena.communication.publisher_2.0.0.v20100316_2_0_0_M6
22	<<LAZY>>    org.eclipse.riena.core_2.0.0.v20100316_2_0_0_M6
23	RESOLVED    org.mortbay.jetty.util_6.1.15.v200905182336
24	RESOLVED    javax.servlet_2.5.0.v200910301333
25	RESOLVED    org.eclipse.equinox.servletbridge.extensionbundle_1.2.0.v20100111
	            Master=0
26	ACTIVE      org.eclipse.core.jobs_3.5.0.v20100304
27	ACTIVE      org.eclipse.equinox.app_1.3.0.v20100304
28	RESOLVED    org.mortbay.jetty.server_6.1.15.v200905151201
29	RESOLVED    org.eclipse.osgi.services_3.2.100.v20100108
30	RESOLVED    org.easymock_2.4.0.v20090202-0900
31	RESOLVED    org.apache.log4j_1.2.13.v200903072027
32	<<LAZY>>    org.eclipse.riena.communication.publisher.hessian_2.0.0.v20100316_2_0_0_M6
33	<<LAZY>>    org.eclipse.core.variables_3.2.300.v20090911
34	<<LAZY>>    org.eclipse.riena.communication.sample.pingpong.common_2.0.0.v20100316_2_0_0_M6
35	RESOLVED    org.eclipse.equinox.http.registry_1.1.0.v20100307
36	<<LAZY>>    org.eclipse.riena.communication.core_2.0.0.v20100316_2_0_0_M6
37	<<LAZY>>    org.eclipse.riena.communication.console_2.0.0.v20100316_2_0_0_M6

osgi>


So, what's the difference about running an osgi framework within Eclipse and running its product?
There are only examples with product definitions for clients not for servers (e.g. Riena Example Client). In the client's product definition an IApplication is specified e.g. SwtApplication. Is that the missing part and is there an equivalent for servers?

[Updated on: Mon, 28 June 2010 09:10]

Report message to a moderator

Re: Export the Server Module [message #543393 is a reply to message #543032] Tue, 29 June 2010 09:49 Go to previous messageGo to next message
Christian Campo is currently offline Christian Campo
Messages: 590
Registered: July 2009
Senior Member
Sorry I didnt answer earlier.....

What you want is run equinox on the server. IApplication is for clients only and of no help on the server.

There is a good page about equinox on the server http://www.eclipse.org/equinox/server/ where you can look for details.

There are two scenarios. One is to run a full blown OSGi Server that has a HTTP Protocol listener for the Remote Service
calls. That is pretty much what you do when run the Server with a .launch directly in the IDE with the Jetty embedded
configuration.

The other is to deploy the service as .WAR file in any web container (Jetty, Tomcat, Websphere, JBoss etc.). For that
you need the BridgetServlet which use is described here http://www.eclipse.org/equinox/server/

There are also new projects like Virgo coming up which offers an enterprise OSGi Server for deploying bundles.
http://www.eclipse.org/virgo/

if you need more let us know

- christian


Am 28.06.10 11:08, schrieb Matthias:
> I didn't find a solution yet, but i tried the following that maybe
> express the problem I'm facing:
> I wanted to make a standalone version (product) of the PingPong Server
> (from the
> http://wiki.eclipse.org/Riena_Example_Applications_and_Code_ Templates#Try_the_communication_ping_pong_example)
>
> If i run the example with the .launch configuration file the server is
> initialized and writes this to the console:
> osgi> Mon Jun 28 10:42:24 CEST 2010 INFO [Framework Event Dispatcher]
> null BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher]
> org.eclipse.riena.internal.core.Activator No stage information set.
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.core.exception.IExceptionHandlerManager}= {service.ranking=-100,
> service.id=46} ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher]
> org.eclipse.riena.internal.core.StartupsSafeRunnable Startup required
> bundle: 'org.eclipse.equinox.log' already started.
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.communication.sample.pingpong.common.IPin gPong}={riena.remote.protocol=hessian,
> riena.remote.path=/PingPongWS, riena.remote=true, service.id=47}
> ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.communication.core.IRemoteServiceRegistry }={service.ranking=-100,
> service.id=48} ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher]
> org.eclipse.riena.internal.communication.core.ssl.SSLConfigu ration No
> configuration given!.
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.communication.core.progressmonitor.IRemot eProgressMonitorRegistry}={service.id=49}
> ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.communication.core.publisher.IServicePubl ishBinder}={service.id=50}
> ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher]
> org.eclipse.riena.communication.publisher.ServicePublishBind er no
> publisher found for protocol hessian
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher]
> org.eclipse.riena.internal.communication.publisher.hessian.A ctivator
> start hessian support on server
> Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher]
> org.eclipse.riena.communication.publisher.ServicePublishBind er
> servicePublish=hessian REGISTER...publishing all services that were
> waiting for him
> Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher]
> org.eclipse.riena.internal.communication.publisher.hessian.H essianRemoteServicePublisher
> published web service. protocol=hessian,
> url=http://10.220.6.236:8080/hessian/PingPongWS,
> interface=org.eclipse.riena.communication.sample.pingpong.co mmon.IPingPong
> Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher]
> org.eclipse.riena.internal.communication.publisher.hessian.H essianRemoteServicePublisher
> web service count: 1
> Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher]
> org.eclipse.riena.communication.publisher.ServicePublishBind er service
> endpoints count: 1
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.communication.core.publisher.IServicePubl isher}={service.ranking=-100,
> riena.protocol=hessian, service.id=51} ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher]
> org.eclipse.riena.communication.publisher.hessian.RienaHessi anDispatcherServlet
> initialized
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.equinox.http.registry.HttpContextExtensionServi ce}={service.id=52}
> ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.osgi.framework.console.CommandProvider}={servic e.id=53}
> ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> FrameworkEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> FrameworkEvent STARTLEVEL CHANGED
>
> Now i run the product that i have created based on that .launch
> configuration file and the only thing that is shown is the osgi console.
> The server bundle (see #18) is <<LAZY>>:
>
> osgi> ss
>
> Framework is launched.
>
> id State Bundle
> 0 ACTIVE org.eclipse.osgi_3.6.0.v20100301
> Fragments=16, 25
> 1 ACTIVE org.eclipse.equinox.common_3.6.0.v20100222
> 2 ACTIVE org.eclipse.core.runtime_3.6.0.v20091204
> 3 RESOLVED org.junit_3.8.2.v20090203-1005
> 4 ACTIVE org.eclipse.core.runtime.compatibility.auth_3.2.100.v2009041 3
> 5 RESOLVED org.eclipse.equinox.log_1.2.100.v20100118
> 6 ACTIVE org.eclipse.equinox.registry_3.5.0.v20100301
> 7 <<LAZY>> org.eclipse.equinox.http.jetty_2.0.0.v20090520-1800
> 8 RESOLVED javax.servlet.jsp_2.0.0.v200806031607
> 9 <<LAZY>> org.eclipse.core.contenttype_3.4.100.v20100301
> 10 RESOLVED com.caucho.hessian_3.2.0
> 11 RESOLVED org.eclipse.riena.server_2.0.0.v20100316_2_0_0_M6
> 12 <<LAZY>> org.eclipse.equinox.security_1.0.200.v20100301
> Fragments=19
> 13 <<LAZY>> org.eclipse.core.net_1.2.100.I20091117-0800
> 14 RESOLVED org.apache.commons.logging_1.0.4.v200904062259
> 15 <<LAZY>> org.eclipse.equinox.http.servlet_1.1.0.v20100201
> 16 RESOLVED org.eclipse.equinox.transforms.hook_1.0.200.v20100118
> Master=0
> 17 <<LAZY>>
> org.eclipse.riena.communication.factory.hessian_2.0.0.v20100 316_2_0_0_M6
> 18 <<LAZY>>
> org.eclipse.riena.communication.sample.pingpong.server_2.0.0 .v20100316_2_0_0_M6
>
> 19 RESOLVED org.eclipse.equinox.security.win32.x86_1.0.100.v20090520-180 0
> Master=12
> 20 ACTIVE org.eclipse.equinox.preferences_3.3.0.v20100307
> 21 <<LAZY>>
> org.eclipse.riena.communication.publisher_2.0.0.v20100316_2_ 0_0_M6
> 22 <<LAZY>> org.eclipse.riena.core_2.0.0.v20100316_2_0_0_M6
> 23 RESOLVED org.mortbay.jetty.util_6.1.15.v200905182336
> 24 RESOLVED javax.servlet_2.5.0.v200910301333
> 25 RESOLVED
> org.eclipse.equinox.servletbridge.extensionbundle_1.2.0.v201 00111
> Master=0
> 26 ACTIVE org.eclipse.core.jobs_3.5.0.v20100304
> 27 ACTIVE org.eclipse.equinox.app_1.3.0.v20100304
> 28 RESOLVED org.mortbay.jetty.server_6.1.15.v200905151201
> 29 RESOLVED org.eclipse.osgi.services_3.2.100.v20100108
> 30 RESOLVED org.easymock_2.4.0.v20090202-0900
> 31 RESOLVED org.apache.log4j_1.2.13.v200903072027
> 32 <<LAZY>>
> org.eclipse.riena.communication.publisher.hessian_2.0.0.v201 00316_2_0_0_M6
> 33 <<LAZY>> org.eclipse.core.variables_3.2.300.v20090911
> 34 <<LAZY>>
> org.eclipse.riena.communication.sample.pingpong.common_2.0.0 .v20100316_2_0_0_M6
>
> 35 RESOLVED org.eclipse.equinox.http.registry_1.1.0.v20100307
> 36 <<LAZY>> org.eclipse.riena.communication.core_2.0.0.v20100316_2_0_0_M 6
> 37 <<LAZY>>
> org.eclipse.riena.communication.console_2.0.0.v20100316_2_0_ 0_M6
>
> osgi>
>
> So, what's the difference about running an osgi framework within Eclipse
> and running its product? There are only examples with product
> definitions for clients not for servers (e.g.
> http://wiki.eclipse.org/Riena_Example_Applications_and_Code_ Templates#Run_the_Riena_Example_Client).
> In the client's product definition an IApplication is specified e.g.
> SwtApplication. Is that the missing part and is there an equivalent for
> servers?
Re: Export the Server Module [message #543662 is a reply to message #543393] Wed, 30 June 2010 08:54 Go to previous messageGo to next message
Matthias is currently offline Matthias
Messages: 52
Registered: September 2009
Member
I read the articles on the page you mentioned. It somehow confuses me:
Quote:
Hint Embed a server in Equinox is the easiest configuration to setup and run. This will allow you to do all your development and debugging. Only when you go to production or in special circumstances will you need to embed Equinox in an existing servlet container.

That means that i have to use a servlet container either way!?

You wrote:
Quote:
One is to run a full blown OSGi Server that has a HTTP Protocol listener for the Remote Service
calls.

In the pingpongserver example there is already a HTTP Protocol listener, isn't there? The article Embedding an HTTP server in Equinox only describes how to run the server via the launch configuration but not standalone.

Let's assume that i want the pingpongserver example to run in a standalone OSGI server.
I tried to export the example as deployable plugin and run it in an OSGI server, jetty seems not to be loaded, the OSGI console is empty. What about the launch arguments e.g. "-Dorg.eclipse.equinox.http.jetty.http.port=8080"? How do i provide them to the OSGI server?

I think i need some start-up aid here.

matthias

[Updated on: Wed, 30 June 2010 09:57]

Report message to a moderator

Re: Export the Server Module [message #543765 is a reply to message #543662] Wed, 30 June 2010 13:57 Go to previous message
Matthias is currently offline Matthias
Messages: 52
Registered: September 2009
Member
Here's how it works:
I easily added all needed plugins to the "Configuration" tab in the Product Definition file and set autostart="true" to all of them. The export mechanism generates the executable OSGi Server, all the bundles are activated.
I don't know if this is the most elegant way, but it works Smile
thx, matthias
Re: Export the Server Module [message #586089 is a reply to message #542303] Mon, 28 June 2010 09:08 Go to previous message
Matthias is currently offline Matthias
Messages: 52
Registered: September 2009
Member
I didn't find a solution yet, but i tried the following that maybe express the problem I'm facing:
I wanted to make a standalone version (product) of the PingPong Server (from the http://wiki.eclipse.org/Riena_Example_Applications_and_Code_ Templates#Try_the_communication_ping_pong_example)
If i run the example with the .launch configuration file the server is initialized and writes this to the console:
osgi> Mon Jun 28 10:42:24 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] org.eclipse.riena.internal.core.Activator No stage information set.
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.core.exception.IExceptionHandlerManager}= {service.ranking=-100, service.id=46} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] org.eclipse.riena.internal.core.StartupsSafeRunnable Startup required bundle: 'org.eclipse.equinox.log' already started.
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.communication.sample.pingpong.common.IPin gPong}={riena.remote.protocol=hessian, riena.remote.path=/PingPongWS, riena.remote=true, service.id=47} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.communication.core.IRemoteServiceRegistry }={service.ranking=-100, service.id=48} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] org.eclipse.riena.internal.communication.core.ssl.SSLConfigu ration No configuration given!.
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.communication.core.progressmonitor.IRemot eProgressMonitorRegistry}={service.id=49} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.communication.core.publisher.IServicePubl ishBinder}={service.id=50} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] org.eclipse.riena.communication.publisher.ServicePublishBind er no publisher found for protocol hessian
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] org.eclipse.riena.internal.communication.publisher.hessian.A ctivator start hessian support on server
Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher] org.eclipse.riena.communication.publisher.ServicePublishBind er servicePublish=hessian REGISTER...publishing all services that were waiting for him
Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher] org.eclipse.riena.internal.communication.publisher.hessian.H essianRemoteServicePublisher published web service. protocol=hessian, url=http://10.220.6.236:8080/hessian/PingPongWS, interface=org.eclipse.riena.communication.sample.pingpong.co mmon.IPingPong
Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher] org.eclipse.riena.internal.communication.publisher.hessian.H essianRemoteServicePublisher web service count: 1
Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher] org.eclipse.riena.communication.publisher.ServicePublishBind er service endpoints count: 1
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.riena.communication.core.publisher.IServicePubl isher}={service.ranking=-100, riena.protocol=hessian, service.id=51} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher] org.eclipse.riena.communication.publisher.hessian.RienaHessi anDispatcherServlet initialized
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.equinox.http.registry.HttpContextExtensionServi ce}={service.id=52} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null {org.eclipse.osgi.framework.console.CommandProvider}={servic e.id=53} ServiceEvent REGISTERED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null BundleEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null FrameworkEvent STARTED
Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null FrameworkEvent STARTLEVEL CHANGED

Now i run the product that i have created based on that .launch configuration file and the only thing that is shown is the osgi console. The server bundle (see #18) is <<LAZY>>:

osgi> ss

Framework is launched.

id State Bundle
0 ACTIVE org.eclipse.osgi_3.6.0.v20100301
Fragments=16, 25
1 ACTIVE org.eclipse.equinox.common_3.6.0.v20100222
2 ACTIVE org.eclipse.core.runtime_3.6.0.v20091204
3 RESOLVED org.junit_3.8.2.v20090203-1005
4 ACTIVE org.eclipse.core.runtime.compatibility.auth_3.2.100.v2009041 3
5 RESOLVED org.eclipse.equinox.log_1.2.100.v20100118
6 ACTIVE org.eclipse.equinox.registry_3.5.0.v20100301
7 <<LAZY>> org.eclipse.equinox.http.jetty_2.0.0.v20090520-1800
8 RESOLVED javax.servlet.jsp_2.0.0.v200806031607
9 <<LAZY>> org.eclipse.core.contenttype_3.4.100.v20100301
10 RESOLVED com.caucho.hessian_3.2.0
11 RESOLVED org.eclipse.riena.server_2.0.0.v20100316_2_0_0_M6
12 <<LAZY>> org.eclipse.equinox.security_1.0.200.v20100301
Fragments=19
13 <<LAZY>> org.eclipse.core.net_1.2.100.I20091117-0800
14 RESOLVED org.apache.commons.logging_1.0.4.v200904062259
15 <<LAZY>> org.eclipse.equinox.http.servlet_1.1.0.v20100201
16 RESOLVED org.eclipse.equinox.transforms.hook_1.0.200.v20100118
Master=0
17 <<LAZY>> org.eclipse.riena.communication.factory.hessian_2.0.0.v20100 316_2_0_0_M6
18 <<LAZY>> org.eclipse.riena.communication.sample.pingpong.server_2.0.0 .v20100316_2_0_0_M6
19 RESOLVED org.eclipse.equinox.security.win32.x86_1.0.100.v20090520-180 0
Master=12
20 ACTIVE org.eclipse.equinox.preferences_3.3.0.v20100307
21 <<LAZY>> org.eclipse.riena.communication.publisher_2.0.0.v20100316_2_ 0_0_M6
22 <<LAZY>> org.eclipse.riena.core_2.0.0.v20100316_2_0_0_M6
23 RESOLVED org.mortbay.jetty.util_6.1.15.v200905182336
24 RESOLVED javax.servlet_2.5.0.v200910301333
25 RESOLVED org.eclipse.equinox.servletbridge.extensionbundle_1.2.0.v201 00111
Master=0
26 ACTIVE org.eclipse.core.jobs_3.5.0.v20100304
27 ACTIVE org.eclipse.equinox.app_1.3.0.v20100304
28 RESOLVED org.mortbay.jetty.server_6.1.15.v200905151201
29 RESOLVED org.eclipse.osgi.services_3.2.100.v20100108
30 RESOLVED org.easymock_2.4.0.v20090202-0900
31 RESOLVED org.apache.log4j_1.2.13.v200903072027
32 <<LAZY>> org.eclipse.riena.communication.publisher.hessian_2.0.0.v201 00316_2_0_0_M6
33 <<LAZY>> org.eclipse.core.variables_3.2.300.v20090911
34 <<LAZY>> org.eclipse.riena.communication.sample.pingpong.common_2.0.0 .v20100316_2_0_0_M6
35 RESOLVED org.eclipse.equinox.http.registry_1.1.0.v20100307
36 <<LAZY>> org.eclipse.riena.communication.core_2.0.0.v20100316_2_0_0_M 6
37 <<LAZY>> org.eclipse.riena.communication.console_2.0.0.v20100316_2_0_ 0_M6

osgi>

So, what's the difference about running an osgi framework within Eclipse and running its product?
There are only examples with product definitions for clients not for servers (e.g. http://wiki.eclipse.org/Riena_Example_Applications_and_Code_ Templates#Run_the_Riena_Example_Client). In the client's product definition an IApplication is specified e.g. SwtApplication. Is that the missing part and is there an equivalent for servers?
Re: Export the Server Module [message #586116 is a reply to message #586089] Tue, 29 June 2010 09:49 Go to previous message
Christian Campo is currently offline Christian Campo
Messages: 590
Registered: July 2009
Senior Member
Sorry I didnt answer earlier.....

What you want is run equinox on the server. IApplication is for clients only and of no help on the server.

There is a good page about equinox on the server http://www.eclipse.org/equinox/server/ where you can look for details.

There are two scenarios. One is to run a full blown OSGi Server that has a HTTP Protocol listener for the Remote Service
calls. That is pretty much what you do when run the Server with a .launch directly in the IDE with the Jetty embedded
configuration.

The other is to deploy the service as .WAR file in any web container (Jetty, Tomcat, Websphere, JBoss etc.). For that
you need the BridgetServlet which use is described here http://www.eclipse.org/equinox/server/

There are also new projects like Virgo coming up which offers an enterprise OSGi Server for deploying bundles.
http://www.eclipse.org/virgo/

if you need more let us know

- christian


Am 28.06.10 11:08, schrieb Matthias:
> I didn't find a solution yet, but i tried the following that maybe
> express the problem I'm facing:
> I wanted to make a standalone version (product) of the PingPong Server
> (from the
> http://wiki.eclipse.org/Riena_Example_Applications_and_Code_ Templates#Try_the_communication_ping_pong_example)
>
> If i run the example with the .launch configuration file the server is
> initialized and writes this to the console:
> osgi> Mon Jun 28 10:42:24 CEST 2010 INFO [Framework Event Dispatcher]
> null BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher]
> org.eclipse.riena.internal.core.Activator No stage information set.
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.core.exception.IExceptionHandlerManager}= {service.ranking=-100,
> service.id=46} ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher]
> org.eclipse.riena.internal.core.StartupsSafeRunnable Startup required
> bundle: 'org.eclipse.equinox.log' already started.
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.communication.sample.pingpong.common.IPin gPong}={riena.remote.protocol=hessian,
> riena.remote.path=/PingPongWS, riena.remote=true, service.id=47}
> ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.communication.core.IRemoteServiceRegistry }={service.ranking=-100,
> service.id=48} ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher]
> org.eclipse.riena.internal.communication.core.ssl.SSLConfigu ration No
> configuration given!.
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.communication.core.progressmonitor.IRemot eProgressMonitorRegistry}={service.id=49}
> ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.communication.core.publisher.IServicePubl ishBinder}={service.id=50}
> ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher]
> org.eclipse.riena.communication.publisher.ServicePublishBind er no
> publisher found for protocol hessian
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher]
> org.eclipse.riena.internal.communication.publisher.hessian.A ctivator
> start hessian support on server
> Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher]
> org.eclipse.riena.communication.publisher.ServicePublishBind er
> servicePublish=hessian REGISTER...publishing all services that were
> waiting for him
> Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher]
> org.eclipse.riena.internal.communication.publisher.hessian.H essianRemoteServicePublisher
> published web service. protocol=hessian,
> url=http://10.220.6.236:8080/hessian/PingPongWS,
> interface=org.eclipse.riena.communication.sample.pingpong.co mmon.IPingPong
> Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher]
> org.eclipse.riena.internal.communication.publisher.hessian.H essianRemoteServicePublisher
> web service count: 1
> Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher]
> org.eclipse.riena.communication.publisher.ServicePublishBind er service
> endpoints count: 1
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.riena.communication.core.publisher.IServicePubl isher}={service.ranking=-100,
> riena.protocol=hessian, service.id=51} ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 DEBUG [Start Level Event Dispatcher]
> org.eclipse.riena.communication.publisher.hessian.RienaHessi anDispatcherServlet
> initialized
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.equinox.http.registry.HttpContextExtensionServi ce}={service.id=52}
> ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Start Level Event Dispatcher] null
> {org.eclipse.osgi.framework.console.CommandProvider}={servic e.id=53}
> ServiceEvent REGISTERED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> BundleEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> FrameworkEvent STARTED
> Mon Jun 28 10:42:29 CEST 2010 INFO [Framework Event Dispatcher] null
> FrameworkEvent STARTLEVEL CHANGED
>
> Now i run the product that i have created based on that .launch
> configuration file and the only thing that is shown is the osgi console.
> The server bundle (see #18) is <<LAZY>>:
>
> osgi> ss
>
> Framework is launched.
>
> id State Bundle
> 0 ACTIVE org.eclipse.osgi_3.6.0.v20100301
> Fragments=16, 25
> 1 ACTIVE org.eclipse.equinox.common_3.6.0.v20100222
> 2 ACTIVE org.eclipse.core.runtime_3.6.0.v20091204
> 3 RESOLVED org.junit_3.8.2.v20090203-1005
> 4 ACTIVE org.eclipse.core.runtime.compatibility.auth_3.2.100.v2009041 3
> 5 RESOLVED org.eclipse.equinox.log_1.2.100.v20100118
> 6 ACTIVE org.eclipse.equinox.registry_3.5.0.v20100301
> 7 <<LAZY>> org.eclipse.equinox.http.jetty_2.0.0.v20090520-1800
> 8 RESOLVED javax.servlet.jsp_2.0.0.v200806031607
> 9 <<LAZY>> org.eclipse.core.contenttype_3.4.100.v20100301
> 10 RESOLVED com.caucho.hessian_3.2.0
> 11 RESOLVED org.eclipse.riena.server_2.0.0.v20100316_2_0_0_M6
> 12 <<LAZY>> org.eclipse.equinox.security_1.0.200.v20100301
> Fragments=19
> 13 <<LAZY>> org.eclipse.core.net_1.2.100.I20091117-0800
> 14 RESOLVED org.apache.commons.logging_1.0.4.v200904062259
> 15 <<LAZY>> org.eclipse.equinox.http.servlet_1.1.0.v20100201
> 16 RESOLVED org.eclipse.equinox.transforms.hook_1.0.200.v20100118
> Master=0
> 17 <<LAZY>>
> org.eclipse.riena.communication.factory.hessian_2.0.0.v20100 316_2_0_0_M6
> 18 <<LAZY>>
> org.eclipse.riena.communication.sample.pingpong.server_2.0.0 .v20100316_2_0_0_M6
>
> 19 RESOLVED org.eclipse.equinox.security.win32.x86_1.0.100.v20090520-180 0
> Master=12
> 20 ACTIVE org.eclipse.equinox.preferences_3.3.0.v20100307
> 21 <<LAZY>>
> org.eclipse.riena.communication.publisher_2.0.0.v20100316_2_ 0_0_M6
> 22 <<LAZY>> org.eclipse.riena.core_2.0.0.v20100316_2_0_0_M6
> 23 RESOLVED org.mortbay.jetty.util_6.1.15.v200905182336
> 24 RESOLVED javax.servlet_2.5.0.v200910301333
> 25 RESOLVED
> org.eclipse.equinox.servletbridge.extensionbundle_1.2.0.v201 00111
> Master=0
> 26 ACTIVE org.eclipse.core.jobs_3.5.0.v20100304
> 27 ACTIVE org.eclipse.equinox.app_1.3.0.v20100304
> 28 RESOLVED org.mortbay.jetty.server_6.1.15.v200905151201
> 29 RESOLVED org.eclipse.osgi.services_3.2.100.v20100108
> 30 RESOLVED org.easymock_2.4.0.v20090202-0900
> 31 RESOLVED org.apache.log4j_1.2.13.v200903072027
> 32 <<LAZY>>
> org.eclipse.riena.communication.publisher.hessian_2.0.0.v201 00316_2_0_0_M6
> 33 <<LAZY>> org.eclipse.core.variables_3.2.300.v20090911
> 34 <<LAZY>>
> org.eclipse.riena.communication.sample.pingpong.common_2.0.0 .v20100316_2_0_0_M6
>
> 35 RESOLVED org.eclipse.equinox.http.registry_1.1.0.v20100307
> 36 <<LAZY>> org.eclipse.riena.communication.core_2.0.0.v20100316_2_0_0_M 6
> 37 <<LAZY>>
> org.eclipse.riena.communication.console_2.0.0.v20100316_2_0_ 0_M6
>
> osgi>
>
> So, what's the difference about running an osgi framework within Eclipse
> and running its product? There are only examples with product
> definitions for clients not for servers (e.g.
> http://wiki.eclipse.org/Riena_Example_Applications_and_Code_ Templates#Run_the_Riena_Example_Client).
> In the client's product definition an IApplication is specified e.g.
> SwtApplication. Is that the missing part and is there an equivalent for
> servers?
Re: Export the Server Module [message #586137 is a reply to message #543393] Wed, 30 June 2010 08:54 Go to previous message
Matthias is currently offline Matthias
Messages: 52
Registered: September 2009
Member
I read the articles on the http://www.eclipse.org/equinox/server/ you mentioned. It somehow confuses me, it seems that there are a lot of different ways to run the server module standalone.

Quote:
> One is to run a full blown OSGi Server that has a HTTP Protocol listener for the Remote Service
> calls.

In the pingpongserver example there is already a HTTP Protocol listener, isn't there? The article http://www.eclipse.org/equinox/server/http_in_equinox.php only describes how to run the server via the launch configuration but not standalone.

Let's assume that i want the pingpongserver example to run in a standalone OSGI server.
I tried to export the example as deployable plugin and run it in an OSGI server, jetty seems not to be loaded, the OSGI console is empty. What about the launch arguments e.g. "-Dorg.eclipse.equinox.http.jetty.http.port=8080"? How do i provide them to the OSGI server?
I think i need some start-up aid here.

matthias
Re: Export the Server Module [message #586144 is a reply to message #543662] Wed, 30 June 2010 13:57 Go to previous message
Matthias is currently offline Matthias
Messages: 52
Registered: September 2009
Member
Here's how it works:
I easily added all needed plugins to the "Configuration" tab in the Product Definition file and set autostart="true" to all of them. The export mechanism generates the executable OSGi Server, all the bundles are activated.
I don't know if this is the most elegant way, but it works :)
thx, matthias
Previous Topic:Toolbar visible function
Next Topic:Unit testing "ordinary" IController implementations
Goto Forum:
  


Current Time: Fri Oct 31 08:38:18 GMT 2014

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

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