You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@cxf.apache.org by ia...@orange-ftgroup.com on 2010/02/03 10:50:58 UTC

Problem Apache CXF DOSGi - Pax Web Extender

I am a user of Apache CXF and I am new in the area,

I have a big problem of compatibility between Pax Web Extender Apache CXF distribution.

I'm using Apache Felix as the OSGi framework version 2.0, pax-runner version 1.3.0, and Maven to compile my project and also to launch pax-runner.

First I want to use Pax Web Extender Module (org.ops4j.pax.web/pax-web-extender-war/0.7.2) to deploy my application "war". And secondly, I use org.apache.cxf.dosgi/cxf-dosgi-ri-singlebundle-distribution/1.1 to manage my web services.

When I deploy the two modules, the Jetty web server stops responding. But when I run one of two modules alone, it works well.

Have you already had this problem? and how to resolve it

Thank you very much

Cordialement, 
Ilyass AHRAZEM 
Ingénieur d'Etude 
Téléphone : 0492945211
ilyass.ahrazem@orange-ftgroup.com 
Groupe SILICOMP - Filiale du Groupe France Telecom 
www.orange-business.com <http://www.orange-business.com/>  



*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************

Re: Problem Apache CXF DOSGi - Pax Web Extender

Posted by David Bosschaert <da...@gmail.com>.

Hi all,

Sorry for chiming in late. I was on leave...

On why these new bundles are part of the 1.1 single bundle distro.
With 1.1 support for distributed discovery was now implemented. The
discovery component uses the OSGi Configuration Admin service so
that's why it was added to the single bundle distro. This distro is
really aimed at getting started quickly, but in cases as described in
this thread the multi-bundle distro is almost always a better choice
as you can leave out bundle for which you already have another version
in your system.

However during the system test work that I did a little while ago I
also experienced that Felix can sometimes be really slow when starting
up with a larger set of bundles. I will share my test case with the
Felix community, it might help them to work on a fix for this.

For the moment there are a couple of things you could do.
* Try using Equinox, if you don't want to switch for real, even just
temporarily. As Sergey suggested this should work. The Felix OBR
should work on Equinox just as well. As you are using pax-runner it
should be easy to switch between Felix and Equinox even just to try it
out.
* You could build your own multibundle distro that doesn't have the
bundles that you are already providing. It's pretty simple to do, have
a look here for a starting point:
http://svn.apache.org/repos/asf/cxf/dosgi/trunk/distribution/single-bundle/pom.xml
Just provide a similar maven module with the dependencies you don't
want removed...

Hope this helps,

David

On 11 February 2010 10:57, Sergey Beryozkin <sb...@progress.com> wrote:
> Hi
>
> thanks for the clarification. I does look like a release-time issue which
> caused configadmin and fileinstall being shipped, unless David or Eoghan
> have done it intentionally ?
>
> paxweb issue : I'm wondering, should paxweb be patched so that it checks
> first if another HttpService is already available and thus do not try to
> install another HttpService impl ?
>
> Can Felix OBR just work on Equinox ? Does it actually need the felix-core ?
>
> cheers, Sergey
>
>
> Hi,
>
> See the Response tag
>
>> S.B DOSGI RI does not ship the above two modules
>
> Response : In the distribution single-bundle-1.1, I found in the folder
> "lib" the two bundles
> "org.apache.felix.configadmin-1.0.10.jar" and
> "org.apache.felix.fileinstall-1.0.0.jar". For the first bundle I saw the
> manifest file
> and I found "org.apache.felix.cm.impl.ConfigurationManager" defined as
> Activator. The same thing for the second bundle.
>
>> S.B It may well be deployed but its Activator has not been invoked so no
>> HttpService impl has been registered.
>
> Can you explain again why you need to remove the pax web activator ?
> Response : In my Application, I use pax-web (pax-web-extender) for deploying
> "war" modules (I use the pax profile "war"), and cxf to
> manage webservices module. But I have a conflict between the pax-web and the
> cxf when I deploy the two modules (war and
> webservices).
> So I removed the pax web Activator of cxf and I used the standard HTTP
> service. So it works better but Felix takes a several time to
> start
>
>> S.B :
>
> Try Equinox ?
> Response : I can't because I have dependencies and modules that Equinox
> doesn't have like "OBR"
>
>
> Thanks for your help
>
> Cordialement,
> Ilyass AHRAZEM
> Ingénieur d'Etude
> Téléphone : 0492945211
> ilyass.ahrazem@orange-ftgroup.com
> Groupe SILICOMP - Filiale du Groupe France Telecom
> www.orange-business.com
>
>
> -----Message d'origine-----
> De : Sergey Beryozkin [mailto:sberyozk@progress.com]
> Envoyé : mercredi 10 février 2010 17:45
> À : users@cxf.apache.org
> Cc : zze-SMART IMMO BELHASSINE H ext RD-BIZZ-SOP; SIBILEAU Nathalie
> RD-BIZZ-SOP; HARO Herve RD-BIZZ-SOP
> Objet : Re: Problem Apache CXF DOSGi - Pax Web Extender
>
> Hi
>
> Please see comments with S.B
>
> Hi,
>
> I intend to use the CXF implementation of DOSGI for our webservices. However
> I found problems with the 2 distributions available:
> - The SingleBundle Ditribution: I use in my application, pax-web and
> config-admin, several conflicts appear because this single
> distrubtion already shipped these modules. I tried to retrieve the source
> code for the implementation and I deleted those 3
> Activators of the list:
>
> org.apache.felix.cm.impl.ConfigurationManager
> org.apache.felix.fileinstall.FileInstall
>
>> S.B DOSGI RI does not ship the above two modules
>
> org.ops4j.pax.web.service.internal.Activator
>
> It works better, but I had an exception whenever I deploy my
> WebService-Bundle: org.osgi.service.http.HttpService service is not
> found. But I'm sure that the pax-web modules is deployed and active !!
>
>> S.B It may well be deployed but its Activator has not been invoked so no
>> HttpService impl has been registered.
>
> Can you explain again why you need to remove the pax web activator ?
>
> - MultiBundle Distribution: I can deploy my webservice and use it, but the
> problem that felix take several time on starting because
> dependency resolution step. This behavior has been detected by felix
> community as a bug (https: / /
> issues.apache.org/jira/browse/FELIX-961) who, apparently, was set
>
> I don't know exactly what I can do.
>
>> S.B :
>
> Try Equinox ?
>
> cheers, Sergey
>
> Thanks for your help
>
>
>
> Ilyass AHRAZEM
> Ingénieur d'Etude
> Téléphone : 0492945211
> ilyass.ahrazem@orange-ftgroup.com
> Groupe SILICOMP - Filiale du Groupe France Telecom www.orange-business.com
>
>
>
> *********************************
> This message and any attachments (the "message") are confidential and
> intended solely for the addressees.
> Any unauthorised use or dissemination is prohibited.
> Messages are susceptible to alteration.
> France Telecom Group shall not be liable for the message if altered, changed
> or falsified.
> If you are not the intended addressee of this message, please cancel it
> immediately and inform the sender.
> ********************************
>
>
> *********************************
> This message and any attachments (the "message") are confidential and
> intended solely for the addressees.
> Any unauthorised use or dissemination is prohibited.
> Messages are susceptible to alteration.
> France Telecom Group shall not be liable for the message if altered, changed
> or falsified.
> If you are not the intended addressee of this message, please cancel it
> immediately and inform the sender.
> ********************************
>
>

Re: Problem Apache CXF DOSGi - Pax Web Extender

Posted by Sergey Beryozkin <sb...@progress.com>.

thanks for the clarification. I does look like a release-time issue which caused configadmin and fileinstall being shipped, unless
David or Eoghan have done it intentionally ?

paxweb issue : I'm wondering, should paxweb be patched so that it checks first if another HttpService is already available and thus
do not try to install another HttpService impl ?

Can Felix OBR just work on Equinox ? Does it actually need the felix-core ?

cheers, Sergey

Hi,

See the Response tag

> S.B DOSGI RI does not ship the above two modules
Response : In the distribution single-bundle-1.1, I found in the folder "lib" the two bundles
"org.apache.felix.configadmin-1.0.10.jar" and "org.apache.felix.fileinstall-1.0.0.jar". For the first bundle I saw the manifest file
and I found "org.apache.felix.cm.impl.ConfigurationManager" defined as Activator. The same thing for the second bundle.

> S.B It may well be deployed but its Activator has not been invoked so no HttpService impl has been registered.
Can you explain again why you need to remove the pax web activator ?
Response : In my Application, I use pax-web (pax-web-extender) for deploying "war" modules (I use the pax profile "war"), and cxf to
manage webservices module. But I have a conflict between the pax-web and the cxf when I deploy the two modules (war and
webservices).
So I removed the pax web Activator of cxf and I used the standard HTTP service. So it works better but Felix takes a several time to
start

> S.B :

Try Equinox ?
Response : I can't because I have dependencies and modules that Equinox doesn't have like "OBR"

Thanks for your help

Cordialement,
Ilyass AHRAZEM
Ingénieur d'Etude
Téléphone : 0492945211
ilyass.ahrazem@orange-ftgroup.com
Groupe SILICOMP - Filiale du Groupe France Telecom
www.orange-business.com

-----Message d'origine-----
De : Sergey Beryozkin [mailto:sberyozk@progress.com]
Envoyé : mercredi 10 février 2010 17:45
À : users@cxf.apache.org
Cc : zze-SMART IMMO BELHASSINE H ext RD-BIZZ-SOP; SIBILEAU Nathalie RD-BIZZ-SOP; HARO Herve RD-BIZZ-SOP
Objet : Re: Problem Apache CXF DOSGi - Pax Web Extender

Please see comments with S.B

Hi,

org.apache.felix.cm.impl.ConfigurationManager
org.apache.felix.fileinstall.FileInstall

> S.B DOSGI RI does not ship the above two modules

org.ops4j.pax.web.service.internal.Activator

It works better, but I had an exception whenever I deploy my WebService-Bundle: org.osgi.service.http.HttpService service is not
found. But I'm sure that the pax-web modules is deployed and active !!

> S.B It may well be deployed but its Activator has not been invoked so no HttpService impl has been registered.
Can you explain again why you need to remove the pax web activator ?

- MultiBundle Distribution: I can deploy my webservice and use it, but the problem that felix take several time on starting because
dependency resolution step. This behavior has been detected by felix community as a bug (https: / /
issues.apache.org/jira/browse/FELIX-961) who, apparently, was set

I don't know exactly what I can do.

> S.B :

Try Equinox ?

cheers, Sergey

Thanks for your help

Ilyass AHRAZEM
Ingénieur d'Etude
Téléphone : 0492945211
ilyass.ahrazem@orange-ftgroup.com
Groupe SILICOMP - Filiale du Groupe France Telecom www.orange-business.com

*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************

RE: Problem Apache CXF DOSGi - Pax Web Extender

Posted by ia...@orange-ftgroup.com.

Hi,

See the Response tag

> S.B DOSGI RI does not ship the above two modules
Response : In the distribution single-bundle-1.1, I found in the folder "lib" the two bundles "org.apache.felix.configadmin-1.0.10.jar" and "org.apache.felix.fileinstall-1.0.0.jar". For the first bundle I saw the manifest file and I found "org.apache.felix.cm.impl.ConfigurationManager" defined as Activator. The same thing for the second bundle.

> S.B It may well be deployed but its Activator has not been invoked so no HttpService impl has been registered.
Can you explain again why you need to remove the pax web activator ?
Response : In my Application, I use pax-web (pax-web-extender) for deploying "war" modules (I use the pax profile "war"), and cxf to manage webservices module. But I have a conflict between the pax-web and the cxf when I deploy the two modules (war and webservices).
So I removed the pax web Activator of cxf and I used the standard HTTP service. So it works better but Felix takes a several time to start

> S.B :

Try Equinox ?
Response : I can't because I have dependencies and modules that Equinox doesn't have like "OBR"

Thanks for your help

Cordialement,
Ilyass AHRAZEM
Ingénieur d'Etude
Téléphone : 0492945211
ilyass.ahrazem@orange-ftgroup.com
Groupe SILICOMP - Filiale du Groupe France Telecom
www.orange-business.com

Please see comments with S.B

Hi,

org.apache.felix.cm.impl.ConfigurationManager
org.apache.felix.fileinstall.FileInstall

> S.B DOSGI RI does not ship the above two modules

org.ops4j.pax.web.service.internal.Activator

It works better, but I had an exception whenever I deploy my WebService-Bundle: org.osgi.service.http.HttpService service is not found. But I'm sure that the pax-web modules is deployed and active !!

> S.B It may well be deployed but its Activator has not been invoked so no HttpService impl has been registered.
Can you explain again why you need to remove the pax web activator ?

- MultiBundle Distribution: I can deploy my webservice and use it, but the problem that felix take several time on starting because dependency resolution step. This behavior has been detected by felix community as a bug (https: / /
issues.apache.org/jira/browse/FELIX-961) who, apparently, was set

I don't know exactly what I can do.

> S.B :

Try Equinox ?

cheers, Sergey

Thanks for your help

Ilyass AHRAZEM
Ingénieur d'Etude
Téléphone : 0492945211
ilyass.ahrazem@orange-ftgroup.com
Groupe SILICOMP - Filiale du Groupe France Telecom www.orange-business.com

Re: Problem Apache CXF DOSGi - Pax Web Extender

Posted by Sergey Beryozkin <sb...@progress.com>.

Please see comments with S.B

Hi,

org.apache.felix.cm.impl.ConfigurationManager
org.apache.felix.fileinstall.FileInstall

> S.B DOSGI RI does not ship the above two modules

org.ops4j.pax.web.service.internal.Activator

It works better, but I had an exception whenever I deploy my WebService-Bundle: org.osgi.service.http.HttpService service is not
found. But I'm sure that the pax-web modules is deployed and active !!

> S.B It may well be deployed but its Activator has not been invoked so no HttpService impl has been registered.
Can you explain again why you need to remove the pax web activator ?

I don't know exactly what I can do.

> S.B :

Try Equinox ?

cheers, Sergey

Thanks for your help

Ilyass AHRAZEM
Ingénieur d'Etude
Téléphone : 0492945211
ilyass.ahrazem@orange-ftgroup.com
Groupe SILICOMP - Filiale du Groupe France Telecom
www.orange-business.com

RE: Problem Apache CXF DOSGi - Pax Web Extender

Posted by ia...@orange-ftgroup.com.

Hi,

I intend to use the CXF implementation of DOSGI for our webservices. However I found problems with the 2 distributions available:
- The SingleBundle Ditribution: I use in my application, pax-web and config-admin, several conflicts appear because this single distrubtion already shipped these modules. I tried to retrieve the source code for the implementation and I deleted those 3 Activators of the list:
org.apache.felix.cm.impl.ConfigurationManager
org.apache.felix.fileinstall.FileInstall
org.ops4j.pax.web.service.internal.Activator
It works better, but I had an exception whenever I deploy my WebService-Bundle: org.osgi.service.http.HttpService service is not found. But I'm sure that the pax-web modules is deployed and active !!

- MultiBundle Distribution: I can deploy my webservice and use it, but the problem that felix take several time on starting because dependency resolution step. This behavior has been detected by felix community as a bug (https: / / issues.apache.org/jira/browse/FELIX-961) who, apparently, was set

I don't know exactly what I can do.

Thanks for your help

Ilyass AHRAZEM
Ingénieur d'Etude
Téléphone : 0492945211
ilyass.ahrazem@orange-ftgroup.com
Groupe SILICOMP - Filiale du Groupe France Telecom
www.orange-business.com

RE: Problem Apache CXF DOSGi - Pax Web Extender

Posted by ia...@orange-ftgroup.com.

Hi Sergey, 

At the beginning, I use an explicit Apache CXF address. After I used HTTP service context for registering the web services. But I still have the same problem

You find below the start method of my class Activator of the web services bundle:

	public void start(BundleContext context) throws Exception {
		Dictionary props = new Hashtable();
		bundleContext = context;

        	props.put("service.exported.interfaces", "*");
        	props.put("service.exported.configs", "org.apache.cxf.ws");

        	props.put("org.apache.cxf.ws.httpservice.context", "/wspartners");
        
        
        registration = context.registerService(WS_DeviceManager.class.getName(), new DeviceManager(), props);

		
	} 


I use maven pax plugin to launch pax runner which the configuration belows

<plugin>
	        <groupId>org.ops4j</groupId>
	        <artifactId>maven-pax-plugin</artifactId>
	        <version>1.4</version>
	        <configuration>
	          <profiles>compendium,log,war,obr,ds,config,event</profiles>
			   <runner>1.3.0</runner>
			   <noDependencies>true</noDependencies>
 			   <args>file:src/test/resources/pax.args</args>
			   <deployURLs>mvn:org.ops4j.pax.confman/pax-confman-propsloader/0.2.2@6,
					   mvn:org.apache.cxf.dosgi/cxf-dosgi-ri-singlebundle-distribution/1.1  
   			   </deployURLs>
            </configuration>
</plugin>


I hope that seems more clear for you.

Thanks for your help.


 
Ilyass AHRAZEM 
Ingénieur d'Etude 
Téléphone : 0492945211
ilyass.ahrazem@orange-ftgroup.com 
Groupe SILICOMP - Filiale du Groupe France Telecom 
www.orange-business.com 


-----Message d'origine-----
De : Sergey Beryozkin [mailto:sberyozk@progress.com] 
Envoyé : mercredi 3 février 2010 17:28
À : users@cxf.apache.org
Objet : Re: Problem Apache CXF DOSGi - Pax Web Extender

Hi

How do you configure your DOSGI services ? You probably do not need to use an explicit  http address but rather use an http context property to ensure no conflicts occur...

cheers, Sergey

----- Original Message -----
From: <ia...@orange-ftgroup.com>
To: <us...@cxf.apache.org>
Sent: Wednesday, February 03, 2010 9:50 AM
Subject: Problem Apache CXF DOSGi - Pax Web Extender



I am a user of Apache CXF and I am new in the area,

I have a big problem of compatibility between Pax Web Extender Apache CXF distribution.

I'm using Apache Felix as the OSGi framework version 2.0, pax-runner version 1.3.0, and Maven to compile my project and also to 
launch pax-runner.

First I want to use Pax Web Extender Module (org.ops4j.pax.web/pax-web-extender-war/0.7.2) to deploy my application "war". And 
secondly, I use org.apache.cxf.dosgi/cxf-dosgi-ri-singlebundle-distribution/1.1 to manage my web services.

When I deploy the two modules, the Jetty web server stops responding. But when I run one of two modules alone, it works well.

Have you already had this problem? and how to resolve it

Thank you very much

Cordialement,
Ilyass AHRAZEM
Ingénieur d'Etude
Téléphone : 0492945211
ilyass.ahrazem@orange-ftgroup.com
Groupe SILICOMP - Filiale du Groupe France Telecom
www.orange-business.com <http://www.orange-business.com/>



*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************



*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************

Re: Problem Apache CXF DOSGi - Pax Web Extender

Posted by Sergey Beryozkin <sb...@progress.com>.

Hi

How do you configure your DOSGI services ? You probably do not need to use an explicit  http address but rather use an http context 
property to ensure no conflicts occur...

cheers, Sergey

----- Original Message ----- 
From: <ia...@orange-ftgroup.com>
To: <us...@cxf.apache.org>
Sent: Wednesday, February 03, 2010 9:50 AM
Subject: Problem Apache CXF DOSGi - Pax Web Extender

I am a user of Apache CXF and I am new in the area,

I have a big problem of compatibility between Pax Web Extender Apache CXF distribution.

I'm using Apache Felix as the OSGi framework version 2.0, pax-runner version 1.3.0, and Maven to compile my project and also to 
launch pax-runner.

First I want to use Pax Web Extender Module (org.ops4j.pax.web/pax-web-extender-war/0.7.2) to deploy my application "war". And 
secondly, I use org.apache.cxf.dosgi/cxf-dosgi-ri-singlebundle-distribution/1.1 to manage my web services.

When I deploy the two modules, the Jetty web server stops responding. But when I run one of two modules alone, it works well.

Have you already had this problem? and how to resolve it

Thank you very much

Cordialement,
Ilyass AHRAZEM
Ingénieur d'Etude
Téléphone : 0492945211
ilyass.ahrazem@orange-ftgroup.com
Groupe SILICOMP - Filiale du Groupe France Telecom
www.orange-business.com <http://www.orange-business.com/>

*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************