You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by zoe slattery <zo...@gmail.com> on 2010/10/27 15:28:43 UTC

Remote services and Web Applications

Hi - I'm trying to use DOSGi for a remote service, the client side of my 
application has a web bundle and pre-reqs the following:

pax-web-extender-war-0.7.2.jar
pax-web-jetty-bundle-0.7.2.jar
pax-web-jsp-0.7.2.jar

As part of the single bundle distribution I think you include:
org.ops4j.pax.web.service_0.5.1

So when I use the single bundle distribution I have two conflicting 
things trying to use port 8080. After some hacking around I think I can 
use the multiple bundle distribution and replace 
org.ops4j.pax.web.service_0.5.1 with the three pax web bundles and 
geronimo-servlet_3.0_spec-1.0.jar.

However there is another problem, in the version of CXF that I'm using 
(revision 1027953) one of the cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT bundle 
won't start and gives the following error:

osgi> start 36
org.osgi.framework.BundleException: The bundle could not be resolved. 
Reason: Package uses conflict: Import-Package: org.apache.cxf; 
version="2.2.0"
     at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
     at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
     at 
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
     at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
     at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
     at 
org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:253)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at 
org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155)
     at 
org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303)
     at 
org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288)
     at 
org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224)
     at java.lang.Thread.run(Thread.java:637)

So - questions:

1) Does the approach to dealing with the port 8080 conflict seem OK?
2) Any idea how to fix the issue with 
cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT - or - do I even need to? Can I just 
exclude it?

Zoe




Re: Remote services and Web Applications

Posted by zoe slattery <zo...@gmail.com>.
On 28/10/2010 11:02, David Bosschaert wrote:
> Hmm, that sounds like a bug then, definitely file a JIRA. Did you try
> the actual release too and/or try it with Felix?
Hi - I just tried with a released version and got the same thing with 
Equinox - however - Felix seems to be fine. I will open a JIRA.
Thanks, Zoe

> Cheers,
>
> David
>
> On 28 October 2010 09:55, zoe slattery<zo...@gmail.com>  wrote:
>> On 28/10/2010 08:42, David Bosschaert wrote:
>>> Hi Zoe,
>>>
>>> Don't know about the second issue - does it happen if you take the
>>> pure multi bundle distro without any modifications?
>> Yes - all I've done is follow the instructions here:
>> http://cxf.apache.org/dosgi-multi-bundle-setup.html to set up the Equinox
>> based version. I'm using an up to date checkout from SVN.
>>
>> Zoe
>>> Cheers,
>>>
>>> David
>>>
>>> On 28 October 2010 08:05, zoe slattery<zo...@gmail.com>    wrote:
>>>> Hi David - excellent - that's what I hoped.
>>>>
>>>> Any thoughts on the second issue - that is actually stopping me getting
>>>> the
>>>> multiple bundle distribution working. It looks like a bug to me - should
>>>> I
>>>> open a Jira?
>>>>
>>>> Z
>>>>> Hi Zoe,
>>>>>
>>>>> Yes, the DOSGi distro contains Pax-Web as a convenience but as far as
>>>>> I can remember this is only used when you are using the HTTP Service
>>>>> to make your CXF services available (via the
>>>>> org.apache.cxf.ws.httpservice.context property, see [1] and [2]). So
>>>>> you should be able to do one of the following two things:
>>>>>
>>>>> * Remove the pax-web-service bundle altogether if you're not using the
>>>>> HTTP service (If you're not sure, you're most likely not using it)
>>>>> * Change the port number that Pax Web uses, using its configuration
>>>>> property: org.osgi.service.http.port
>>>>>
>>>>> Hope this helps,
>>>>>
>>>>> David
>>>>>
>>>>> [1] http://cxf.apache.org/distributed-osgi-reference.html
>>>>> [2]
>>>>>
>>>>> http://coderthoughts.blogspot.com/2009/02/distributed-osgi-powered-ajax-webapp.html
>>>>>
>>>>> On 27 October 2010 20:21, zoe slattery<zo...@gmail.com>      wrote:
>>>>>> Hi Sergey - thanks - but that isn't the problem :-/. Using that port is
>>>>>> fine
>>>>>> but it's still the case that whatever is in CXF grabs port 8080 at the
>>>>>> http
>>>>>> service port.
>>>>>>
>>>>>>> I think there;s a property available there for ws services where you
>>>>>>> can
>>>>>>> specify which port to listen upon,
>>>>>>> probably "org.apache.cxf.ws.port"
>>>>>>>
>>>>>>> cheers, Sergey
>>>>>>>
>>>>>>> On Wed, Oct 27, 2010 at 2:28 PM, zoe
>>>>>>> slattery<zo...@gmail.com>wrote:
>>>>>>>
>>>>>>>> Hi - I'm trying to use DOSGi for a remote service, the client side of
>>>>>>>> my
>>>>>>>> application has a web bundle and pre-reqs the following:
>>>>>>>>
>>>>>>>> pax-web-extender-war-0.7.2.jar
>>>>>>>> pax-web-jetty-bundle-0.7.2.jar
>>>>>>>> pax-web-jsp-0.7.2.jar
>>>>>>>>
>>>>>>>> As part of the single bundle distribution I think you include:
>>>>>>>> org.ops4j.pax.web.service_0.5.1
>>>>>>>>
>>>>>>>> So when I use the single bundle distribution I have two conflicting
>>>>>>>> things
>>>>>>>> trying to use port 8080. After some hacking around I think I can use
>>>>>>>> the
>>>>>>>> multiple bundle distribution and replace
>>>>>>>> org.ops4j.pax.web.service_0.5.1
>>>>>>>> with the three pax web bundles and geronimo-servlet_3.0_spec-1.0.jar.
>>>>>>>>
>>>>>>>> However there is another problem, in the version of CXF that I'm
>>>>>>>> using
>>>>>>>> (revision 1027953) one of the cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT
>>>>>>>> bundle
>>>>>>>> won't start and gives the following error:
>>>>>>>>
>>>>>>>> osgi>        start 36
>>>>>>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>>>>>>> Reason: Package uses conflict: Import-Package: org.apache.cxf;
>>>>>>>> version="2.2.0"
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:253)
>>>>>>>>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>>     at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155)
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303)
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288)
>>>>>>>>     at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224)
>>>>>>>>     at java.lang.Thread.run(Thread.java:637)
>>>>>>>>
>>>>>>>> So - questions:
>>>>>>>>
>>>>>>>> 1) Does the approach to dealing with the port 8080 conflict seem OK?
>>>>>>>> 2) Any idea how to fix the issue with
>>>>>>>> cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT
>>>>>>>> -
>>>>>>>> or - do I even need to? Can I just exclude it?
>>>>>>>>
>>>>>>>> Zoe
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>


Re: Remote services and Web Applications

Posted by David Bosschaert <da...@gmail.com>.
Hmm, that sounds like a bug then, definitely file a JIRA. Did you try
the actual release too and/or try it with Felix?

Cheers,

David

On 28 October 2010 09:55, zoe slattery <zo...@gmail.com> wrote:
> On 28/10/2010 08:42, David Bosschaert wrote:
>>
>> Hi Zoe,
>>
>> Don't know about the second issue - does it happen if you take the
>> pure multi bundle distro without any modifications?
>
> Yes - all I've done is follow the instructions here:
> http://cxf.apache.org/dosgi-multi-bundle-setup.html to set up the Equinox
> based version. I'm using an up to date checkout from SVN.
>
> Zoe
>>
>> Cheers,
>>
>> David
>>
>> On 28 October 2010 08:05, zoe slattery<zo...@gmail.com>  wrote:
>>>
>>> Hi David - excellent - that's what I hoped.
>>>
>>> Any thoughts on the second issue - that is actually stopping me getting
>>> the
>>> multiple bundle distribution working. It looks like a bug to me - should
>>> I
>>> open a Jira?
>>>
>>> Z
>>>>
>>>> Hi Zoe,
>>>>
>>>> Yes, the DOSGi distro contains Pax-Web as a convenience but as far as
>>>> I can remember this is only used when you are using the HTTP Service
>>>> to make your CXF services available (via the
>>>> org.apache.cxf.ws.httpservice.context property, see [1] and [2]). So
>>>> you should be able to do one of the following two things:
>>>>
>>>> * Remove the pax-web-service bundle altogether if you're not using the
>>>> HTTP service (If you're not sure, you're most likely not using it)
>>>> * Change the port number that Pax Web uses, using its configuration
>>>> property: org.osgi.service.http.port
>>>>
>>>> Hope this helps,
>>>>
>>>> David
>>>>
>>>> [1] http://cxf.apache.org/distributed-osgi-reference.html
>>>> [2]
>>>>
>>>> http://coderthoughts.blogspot.com/2009/02/distributed-osgi-powered-ajax-webapp.html
>>>>
>>>> On 27 October 2010 20:21, zoe slattery<zo...@gmail.com>    wrote:
>>>>>
>>>>> Hi Sergey - thanks - but that isn't the problem :-/. Using that port is
>>>>> fine
>>>>> but it's still the case that whatever is in CXF grabs port 8080 at the
>>>>> http
>>>>> service port.
>>>>>
>>>>>> I think there;s a property available there for ws services where you
>>>>>> can
>>>>>> specify which port to listen upon,
>>>>>> probably "org.apache.cxf.ws.port"
>>>>>>
>>>>>> cheers, Sergey
>>>>>>
>>>>>> On Wed, Oct 27, 2010 at 2:28 PM, zoe
>>>>>> slattery<zo...@gmail.com>wrote:
>>>>>>
>>>>>>> Hi - I'm trying to use DOSGi for a remote service, the client side of
>>>>>>> my
>>>>>>> application has a web bundle and pre-reqs the following:
>>>>>>>
>>>>>>> pax-web-extender-war-0.7.2.jar
>>>>>>> pax-web-jetty-bundle-0.7.2.jar
>>>>>>> pax-web-jsp-0.7.2.jar
>>>>>>>
>>>>>>> As part of the single bundle distribution I think you include:
>>>>>>> org.ops4j.pax.web.service_0.5.1
>>>>>>>
>>>>>>> So when I use the single bundle distribution I have two conflicting
>>>>>>> things
>>>>>>> trying to use port 8080. After some hacking around I think I can use
>>>>>>> the
>>>>>>> multiple bundle distribution and replace
>>>>>>> org.ops4j.pax.web.service_0.5.1
>>>>>>> with the three pax web bundles and geronimo-servlet_3.0_spec-1.0.jar.
>>>>>>>
>>>>>>> However there is another problem, in the version of CXF that I'm
>>>>>>> using
>>>>>>> (revision 1027953) one of the cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT
>>>>>>> bundle
>>>>>>> won't start and gives the following error:
>>>>>>>
>>>>>>> osgi>      start 36
>>>>>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>>>>>> Reason: Package uses conflict: Import-Package: org.apache.cxf;
>>>>>>> version="2.2.0"
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:253)
>>>>>>>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>>    at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155)
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303)
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288)
>>>>>>>    at
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224)
>>>>>>>    at java.lang.Thread.run(Thread.java:637)
>>>>>>>
>>>>>>> So - questions:
>>>>>>>
>>>>>>> 1) Does the approach to dealing with the port 8080 conflict seem OK?
>>>>>>> 2) Any idea how to fix the issue with
>>>>>>> cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT
>>>>>>> -
>>>>>>> or - do I even need to? Can I just exclude it?
>>>>>>>
>>>>>>> Zoe
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>
>
>

Re: Remote services and Web Applications

Posted by zoe slattery <zo...@gmail.com>.
On 28/10/2010 08:42, David Bosschaert wrote:
> Hi Zoe,
>
> Don't know about the second issue - does it happen if you take the
> pure multi bundle distro without any modifications?
Yes - all I've done is follow the instructions here: 
http://cxf.apache.org/dosgi-multi-bundle-setup.html to set up the 
Equinox based version. I'm using an up to date checkout from SVN.

Zoe
> Cheers,
>
> David
>
> On 28 October 2010 08:05, zoe slattery<zo...@gmail.com>  wrote:
>> Hi David - excellent - that's what I hoped.
>>
>> Any thoughts on the second issue - that is actually stopping me getting the
>> multiple bundle distribution working. It looks like a bug to me - should I
>> open a Jira?
>>
>> Z
>>> Hi Zoe,
>>>
>>> Yes, the DOSGi distro contains Pax-Web as a convenience but as far as
>>> I can remember this is only used when you are using the HTTP Service
>>> to make your CXF services available (via the
>>> org.apache.cxf.ws.httpservice.context property, see [1] and [2]). So
>>> you should be able to do one of the following two things:
>>>
>>> * Remove the pax-web-service bundle altogether if you're not using the
>>> HTTP service (If you're not sure, you're most likely not using it)
>>> * Change the port number that Pax Web uses, using its configuration
>>> property: org.osgi.service.http.port
>>>
>>> Hope this helps,
>>>
>>> David
>>>
>>> [1] http://cxf.apache.org/distributed-osgi-reference.html
>>> [2]
>>> http://coderthoughts.blogspot.com/2009/02/distributed-osgi-powered-ajax-webapp.html
>>>
>>> On 27 October 2010 20:21, zoe slattery<zo...@gmail.com>    wrote:
>>>> Hi Sergey - thanks - but that isn't the problem :-/. Using that port is
>>>> fine
>>>> but it's still the case that whatever is in CXF grabs port 8080 at the
>>>> http
>>>> service port.
>>>>
>>>>> I think there;s a property available there for ws services where you can
>>>>> specify which port to listen upon,
>>>>> probably "org.apache.cxf.ws.port"
>>>>>
>>>>> cheers, Sergey
>>>>>
>>>>> On Wed, Oct 27, 2010 at 2:28 PM, zoe
>>>>> slattery<zo...@gmail.com>wrote:
>>>>>
>>>>>> Hi - I'm trying to use DOSGi for a remote service, the client side of
>>>>>> my
>>>>>> application has a web bundle and pre-reqs the following:
>>>>>>
>>>>>> pax-web-extender-war-0.7.2.jar
>>>>>> pax-web-jetty-bundle-0.7.2.jar
>>>>>> pax-web-jsp-0.7.2.jar
>>>>>>
>>>>>> As part of the single bundle distribution I think you include:
>>>>>> org.ops4j.pax.web.service_0.5.1
>>>>>>
>>>>>> So when I use the single bundle distribution I have two conflicting
>>>>>> things
>>>>>> trying to use port 8080. After some hacking around I think I can use
>>>>>> the
>>>>>> multiple bundle distribution and replace
>>>>>> org.ops4j.pax.web.service_0.5.1
>>>>>> with the three pax web bundles and geronimo-servlet_3.0_spec-1.0.jar.
>>>>>>
>>>>>> However there is another problem, in the version of CXF that I'm using
>>>>>> (revision 1027953) one of the cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT
>>>>>> bundle
>>>>>> won't start and gives the following error:
>>>>>>
>>>>>> osgi>      start 36
>>>>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>>>>> Reason: Package uses conflict: Import-Package: org.apache.cxf;
>>>>>> version="2.2.0"
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:253)
>>>>>>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>>     at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155)
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303)
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288)
>>>>>>     at
>>>>>>
>>>>>>
>>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224)
>>>>>>     at java.lang.Thread.run(Thread.java:637)
>>>>>>
>>>>>> So - questions:
>>>>>>
>>>>>> 1) Does the approach to dealing with the port 8080 conflict seem OK?
>>>>>> 2) Any idea how to fix the issue with
>>>>>> cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT
>>>>>> -
>>>>>> or - do I even need to? Can I just exclude it?
>>>>>>
>>>>>> Zoe
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>


Re: Remote services and Web Applications

Posted by David Bosschaert <da...@gmail.com>.
Hi Zoe,

Don't know about the second issue - does it happen if you take the
pure multi bundle distro without any modifications?

Cheers,

David

On 28 October 2010 08:05, zoe slattery <zo...@gmail.com> wrote:
> Hi David - excellent - that's what I hoped.
>
> Any thoughts on the second issue - that is actually stopping me getting the
> multiple bundle distribution working. It looks like a bug to me - should I
> open a Jira?
>
> Z
>>
>> Hi Zoe,
>>
>> Yes, the DOSGi distro contains Pax-Web as a convenience but as far as
>> I can remember this is only used when you are using the HTTP Service
>> to make your CXF services available (via the
>> org.apache.cxf.ws.httpservice.context property, see [1] and [2]). So
>> you should be able to do one of the following two things:
>>
>> * Remove the pax-web-service bundle altogether if you're not using the
>> HTTP service (If you're not sure, you're most likely not using it)
>> * Change the port number that Pax Web uses, using its configuration
>> property: org.osgi.service.http.port
>>
>> Hope this helps,
>>
>> David
>>
>> [1] http://cxf.apache.org/distributed-osgi-reference.html
>> [2]
>> http://coderthoughts.blogspot.com/2009/02/distributed-osgi-powered-ajax-webapp.html
>>
>> On 27 October 2010 20:21, zoe slattery<zo...@gmail.com>  wrote:
>>>
>>> Hi Sergey - thanks - but that isn't the problem :-/. Using that port is
>>> fine
>>> but it's still the case that whatever is in CXF grabs port 8080 at the
>>> http
>>> service port.
>>>
>>>> I think there;s a property available there for ws services where you can
>>>> specify which port to listen upon,
>>>> probably "org.apache.cxf.ws.port"
>>>>
>>>> cheers, Sergey
>>>>
>>>> On Wed, Oct 27, 2010 at 2:28 PM, zoe
>>>> slattery<zo...@gmail.com>wrote:
>>>>
>>>>> Hi - I'm trying to use DOSGi for a remote service, the client side of
>>>>> my
>>>>> application has a web bundle and pre-reqs the following:
>>>>>
>>>>> pax-web-extender-war-0.7.2.jar
>>>>> pax-web-jetty-bundle-0.7.2.jar
>>>>> pax-web-jsp-0.7.2.jar
>>>>>
>>>>> As part of the single bundle distribution I think you include:
>>>>> org.ops4j.pax.web.service_0.5.1
>>>>>
>>>>> So when I use the single bundle distribution I have two conflicting
>>>>> things
>>>>> trying to use port 8080. After some hacking around I think I can use
>>>>> the
>>>>> multiple bundle distribution and replace
>>>>> org.ops4j.pax.web.service_0.5.1
>>>>> with the three pax web bundles and geronimo-servlet_3.0_spec-1.0.jar.
>>>>>
>>>>> However there is another problem, in the version of CXF that I'm using
>>>>> (revision 1027953) one of the cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT
>>>>> bundle
>>>>> won't start and gives the following error:
>>>>>
>>>>> osgi>    start 36
>>>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>>>> Reason: Package uses conflict: Import-Package: org.apache.cxf;
>>>>> version="2.2.0"
>>>>>    at
>>>>>
>>>>>
>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
>>>>>    at
>>>>>
>>>>>
>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
>>>>>    at
>>>>>
>>>>>
>>>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
>>>>>    at
>>>>>
>>>>>
>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
>>>>>    at
>>>>>
>>>>>
>>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
>>>>>    at
>>>>>
>>>>>
>>>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:253)
>>>>>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>    at
>>>>>
>>>>>
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>    at
>>>>>
>>>>>
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>    at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>    at
>>>>>
>>>>>
>>>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155)
>>>>>    at
>>>>>
>>>>>
>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303)
>>>>>    at
>>>>>
>>>>>
>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288)
>>>>>    at
>>>>>
>>>>>
>>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224)
>>>>>    at java.lang.Thread.run(Thread.java:637)
>>>>>
>>>>> So - questions:
>>>>>
>>>>> 1) Does the approach to dealing with the port 8080 conflict seem OK?
>>>>> 2) Any idea how to fix the issue with
>>>>> cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT
>>>>> -
>>>>> or - do I even need to? Can I just exclude it?
>>>>>
>>>>> Zoe
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>
>

Re: Remote services and Web Applications

Posted by zoe slattery <zo...@gmail.com>.
Hi David - excellent - that's what I hoped.

Any thoughts on the second issue - that is actually stopping me getting 
the multiple bundle distribution working. It looks like a bug to me - 
should I open a Jira?

Z
> Hi Zoe,
>
> Yes, the DOSGi distro contains Pax-Web as a convenience but as far as
> I can remember this is only used when you are using the HTTP Service
> to make your CXF services available (via the
> org.apache.cxf.ws.httpservice.context property, see [1] and [2]). So
> you should be able to do one of the following two things:
>
> * Remove the pax-web-service bundle altogether if you're not using the
> HTTP service (If you're not sure, you're most likely not using it)
> * Change the port number that Pax Web uses, using its configuration
> property: org.osgi.service.http.port
>
> Hope this helps,
>
> David
>
> [1] http://cxf.apache.org/distributed-osgi-reference.html
> [2] http://coderthoughts.blogspot.com/2009/02/distributed-osgi-powered-ajax-webapp.html
>
> On 27 October 2010 20:21, zoe slattery<zo...@gmail.com>  wrote:
>> Hi Sergey - thanks - but that isn't the problem :-/. Using that port is fine
>> but it's still the case that whatever is in CXF grabs port 8080 at the http
>> service port.
>>
>>> I think there;s a property available there for ws services where you can
>>> specify which port to listen upon,
>>> probably "org.apache.cxf.ws.port"
>>>
>>> cheers, Sergey
>>>
>>> On Wed, Oct 27, 2010 at 2:28 PM, zoe
>>> slattery<zo...@gmail.com>wrote:
>>>
>>>> Hi - I'm trying to use DOSGi for a remote service, the client side of my
>>>> application has a web bundle and pre-reqs the following:
>>>>
>>>> pax-web-extender-war-0.7.2.jar
>>>> pax-web-jetty-bundle-0.7.2.jar
>>>> pax-web-jsp-0.7.2.jar
>>>>
>>>> As part of the single bundle distribution I think you include:
>>>> org.ops4j.pax.web.service_0.5.1
>>>>
>>>> So when I use the single bundle distribution I have two conflicting
>>>> things
>>>> trying to use port 8080. After some hacking around I think I can use the
>>>> multiple bundle distribution and replace org.ops4j.pax.web.service_0.5.1
>>>> with the three pax web bundles and geronimo-servlet_3.0_spec-1.0.jar.
>>>>
>>>> However there is another problem, in the version of CXF that I'm using
>>>> (revision 1027953) one of the cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT bundle
>>>> won't start and gives the following error:
>>>>
>>>> osgi>    start 36
>>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>>> Reason: Package uses conflict: Import-Package: org.apache.cxf;
>>>> version="2.2.0"
>>>>     at
>>>>
>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
>>>>     at
>>>>
>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
>>>>     at
>>>>
>>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
>>>>     at
>>>>
>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
>>>>     at
>>>>
>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
>>>>     at
>>>>
>>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:253)
>>>>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>     at
>>>>
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>     at
>>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>     at java.lang.reflect.Method.invoke(Method.java:597)
>>>>     at
>>>>
>>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155)
>>>>     at
>>>>
>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303)
>>>>     at
>>>>
>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288)
>>>>     at
>>>>
>>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224)
>>>>     at java.lang.Thread.run(Thread.java:637)
>>>>
>>>> So - questions:
>>>>
>>>> 1) Does the approach to dealing with the port 8080 conflict seem OK?
>>>> 2) Any idea how to fix the issue with cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT
>>>> -
>>>> or - do I even need to? Can I just exclude it?
>>>>
>>>> Zoe
>>>>
>>>>
>>>>
>>>>
>>


Re: Remote services and Web Applications

Posted by David Bosschaert <da...@gmail.com>.
Hi Zoe,

Yes, the DOSGi distro contains Pax-Web as a convenience but as far as
I can remember this is only used when you are using the HTTP Service
to make your CXF services available (via the
org.apache.cxf.ws.httpservice.context property, see [1] and [2]). So
you should be able to do one of the following two things:

* Remove the pax-web-service bundle altogether if you're not using the
HTTP service (If you're not sure, you're most likely not using it)
* Change the port number that Pax Web uses, using its configuration
property: org.osgi.service.http.port

Hope this helps,

David

[1] http://cxf.apache.org/distributed-osgi-reference.html
[2] http://coderthoughts.blogspot.com/2009/02/distributed-osgi-powered-ajax-webapp.html

On 27 October 2010 20:21, zoe slattery <zo...@gmail.com> wrote:
> Hi Sergey - thanks - but that isn't the problem :-/. Using that port is fine
> but it's still the case that whatever is in CXF grabs port 8080 at the http
> service port.
>
>> I think there;s a property available there for ws services where you can
>> specify which port to listen upon,
>> probably "org.apache.cxf.ws.port"
>>
>> cheers, Sergey
>>
>> On Wed, Oct 27, 2010 at 2:28 PM, zoe
>> slattery<zo...@gmail.com>wrote:
>>
>>> Hi - I'm trying to use DOSGi for a remote service, the client side of my
>>> application has a web bundle and pre-reqs the following:
>>>
>>> pax-web-extender-war-0.7.2.jar
>>> pax-web-jetty-bundle-0.7.2.jar
>>> pax-web-jsp-0.7.2.jar
>>>
>>> As part of the single bundle distribution I think you include:
>>> org.ops4j.pax.web.service_0.5.1
>>>
>>> So when I use the single bundle distribution I have two conflicting
>>> things
>>> trying to use port 8080. After some hacking around I think I can use the
>>> multiple bundle distribution and replace org.ops4j.pax.web.service_0.5.1
>>> with the three pax web bundles and geronimo-servlet_3.0_spec-1.0.jar.
>>>
>>> However there is another problem, in the version of CXF that I'm using
>>> (revision 1027953) one of the cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT bundle
>>> won't start and gives the following error:
>>>
>>> osgi>  start 36
>>> org.osgi.framework.BundleException: The bundle could not be resolved.
>>> Reason: Package uses conflict: Import-Package: org.apache.cxf;
>>> version="2.2.0"
>>>    at
>>>
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
>>>    at
>>>
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
>>>    at
>>>
>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
>>>    at
>>>
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
>>>    at
>>>
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
>>>    at
>>>
>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:253)
>>>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>    at
>>>
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>    at
>>>
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>    at java.lang.reflect.Method.invoke(Method.java:597)
>>>    at
>>>
>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155)
>>>    at
>>>
>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303)
>>>    at
>>>
>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288)
>>>    at
>>>
>>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224)
>>>    at java.lang.Thread.run(Thread.java:637)
>>>
>>> So - questions:
>>>
>>> 1) Does the approach to dealing with the port 8080 conflict seem OK?
>>> 2) Any idea how to fix the issue with cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT
>>> -
>>> or - do I even need to? Can I just exclude it?
>>>
>>> Zoe
>>>
>>>
>>>
>>>
>
>

Re: Remote services and Web Applications

Posted by zoe slattery <zo...@gmail.com>.
Hi Sergey - thanks - but that isn't the problem :-/. Using that port is 
fine but it's still the case that whatever is in CXF grabs port 8080 at 
the http service port.

> I think there;s a property available there for ws services where you can
> specify which port to listen upon,
> probably "org.apache.cxf.ws.port"
>
> cheers, Sergey
>
> On Wed, Oct 27, 2010 at 2:28 PM, zoe slattery<zo...@gmail.com>wrote:
>
>> Hi - I'm trying to use DOSGi for a remote service, the client side of my
>> application has a web bundle and pre-reqs the following:
>>
>> pax-web-extender-war-0.7.2.jar
>> pax-web-jetty-bundle-0.7.2.jar
>> pax-web-jsp-0.7.2.jar
>>
>> As part of the single bundle distribution I think you include:
>> org.ops4j.pax.web.service_0.5.1
>>
>> So when I use the single bundle distribution I have two conflicting things
>> trying to use port 8080. After some hacking around I think I can use the
>> multiple bundle distribution and replace org.ops4j.pax.web.service_0.5.1
>> with the three pax web bundles and geronimo-servlet_3.0_spec-1.0.jar.
>>
>> However there is another problem, in the version of CXF that I'm using
>> (revision 1027953) one of the cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT bundle
>> won't start and gives the following error:
>>
>> osgi>  start 36
>> org.osgi.framework.BundleException: The bundle could not be resolved.
>> Reason: Package uses conflict: Import-Package: org.apache.cxf;
>> version="2.2.0"
>>     at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
>>     at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
>>     at
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
>>     at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
>>     at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
>>     at
>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:253)
>>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>     at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>     at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>     at java.lang.reflect.Method.invoke(Method.java:597)
>>     at
>> org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155)
>>     at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303)
>>     at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288)
>>     at
>> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224)
>>     at java.lang.Thread.run(Thread.java:637)
>>
>> So - questions:
>>
>> 1) Does the approach to dealing with the port 8080 conflict seem OK?
>> 2) Any idea how to fix the issue with cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT -
>> or - do I even need to? Can I just exclude it?
>>
>> Zoe
>>
>>
>>
>>


Re: Remote services and Web Applications

Posted by Sergey Beryozkin <sb...@gmail.com>.
I think there;s a property available there for ws services where you can
specify which port to listen upon,
probably "org.apache.cxf.ws.port"

cheers, Sergey

On Wed, Oct 27, 2010 at 2:28 PM, zoe slattery <zo...@gmail.com>wrote:

> Hi - I'm trying to use DOSGi for a remote service, the client side of my
> application has a web bundle and pre-reqs the following:
>
> pax-web-extender-war-0.7.2.jar
> pax-web-jetty-bundle-0.7.2.jar
> pax-web-jsp-0.7.2.jar
>
> As part of the single bundle distribution I think you include:
> org.ops4j.pax.web.service_0.5.1
>
> So when I use the single bundle distribution I have two conflicting things
> trying to use port 8080. After some hacking around I think I can use the
> multiple bundle distribution and replace org.ops4j.pax.web.service_0.5.1
> with the three pax web bundles and geronimo-servlet_3.0_spec-1.0.jar.
>
> However there is another problem, in the version of CXF that I'm using
> (revision 1027953) one of the cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT bundle
> won't start and gives the following error:
>
> osgi> start 36
> org.osgi.framework.BundleException: The bundle could not be resolved.
> Reason: Package uses conflict: Import-Package: org.apache.cxf;
> version="2.2.0"
>    at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
>    at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
>    at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
>    at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
>    at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
>    at
> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:253)
>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>    at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>    at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>    at java.lang.reflect.Method.invoke(Method.java:597)
>    at
> org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155)
>    at
> org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:303)
>    at
> org.eclipse.osgi.framework.internal.core.FrameworkConsole.console(FrameworkConsole.java:288)
>    at
> org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:224)
>    at java.lang.Thread.run(Thread.java:637)
>
> So - questions:
>
> 1) Does the approach to dealing with the port 8080 conflict seem OK?
> 2) Any idea how to fix the issue with cxf-dosgi-ri-dsw-cxf_1.3.0.SNAPSHOT -
> or - do I even need to? Can I just exclude it?
>
> Zoe
>
>
>
>