You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Sergey Beryozkin <sb...@gmail.com> on 2011/12/22 11:46:15 UTC

Preparing for DOSGi RI 1.3 release

Hi All,

Dan, myself and David talked about the possibility of releasing DOSGi RI 
1.3 based on Apache CXF.

There are few reasons why we thought it was a good idea to pursue it.

We are seeing a number of users periodically asking DOSGI-related 
questions and it's been unfortunate that some basic bugs have stopped 
users from experimenting with DOSGi and proceeding with the POC 
deployments and such though we believe a number of users have actually 
successfully deployed DOSGI RI in their projects without major problems 
or by fixing bugs locally and submitting patched back to the DOSGi RI 
project.

So helping the community with fixing as many bugs as realistically 
possible in the short term and releasing DOSGi RI 1.3 is important.

DOSGi RI has CXF JAX-WS and JAX-RS frontends operating on the OSGI 
Service registrations and look-ups and hence we hope that it can open up 
more interesting options for users to deploy web services in OSGi and 
therefore stress CXF from a different direction.

I've spent few days on closing the JIRAs reported against DOSGi 1.1 and 
1.2 due to DOSGI 1.3-SNAPSHOT has had its dependencies changed a lot 
(thanks to a major patch from Ancoron Luciferis), with CXF 2.5.1 
supporting it now. I've also resolved a lot of JIRAs containing patches 
or hints on some basic modifications needed to get the issues fixed.

Two modules have been removed, a zookeeper bundle wrapper and the local 
OSGI RemoteAdminService code which is now available in Central.

Here is a complete list:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+DOSGI+AND+resolutiondate+%3E%3D-1w+ORDER+BY+updated+DESC

Here is the list of outstanding issues:

https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+DOSGI+AND+resolutiondate+%3E%3D-1w+ORDER+BY+updated+DESC

IMHO we are nearly good to go with the 1.3 release. What I'd like to do 
is to ask users who are interested in working or experimenting with 
DOSGi to give 1.3-SNAPSHOT a test on the latest Felix or Equinox 
distributions as well as check the list of outstanding issues  and may 
be submit a couple of more patches.

Personally I'd get a pint to anyone who will figure out how to fix
https://issues.apache.org/jira/browse/DOSGI-18 :-) (that works in a 
single bundle case), though in case of JAX-RS the consumers can be the 
browsers.

https://issues.apache.org/jira/browse/DOSGI-106
also seems important enough, though HttpService can be used just fine 
with multi-bundle distros.

So please give it a test, consider fixing a couple of more issues and we 
will be ready to proceed with the release early next year

Thanks, Sergey
-- 
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Blog: http://sberyozkin.blogspot.com

Re: What's the usage of MultipleEndpointObserver

Posted by xuhb <xu...@tongtech.com>.
Thanks Freeman:

It's great, thank you very much;

----- Original Message ----- 
From: "Freeman Fang" <fr...@gmail.com>
To: <de...@cxf.apache.org>
Sent: Wednesday, December 28, 2011 6:14 PM
Subject: Re: What's the usage of MultipleEndpointObserver


Hi,

Yes.

IIRC,  for server side you need write a routingInterceptor to dispatch  
message to different endpoint.
When multiple endpoints publish to same address, those endpoints will  
share same MultipleEndpointObserver, by default, the  
MultipleEndpointObserver will use EndpointSelectionInterceptor to  
select on the proper endpoint based on soap version, this is a typical  
usecase which different endpoints(use soap11 or soap12) get published  
to same uri.
You can replace this routingInterceptor for your purpose, we actually  
have a testcase[1] which demonstrate how it works, the  
routingInterceptor used in this tesecase is[2]
The key code to publish different endpoints on same address and  
register a  MultipleEndpointObserver which use the routingInterceptor  
you want is

         String address = "http://localhost:" + PORT + "/SoapContext/ 
SoapPort";

         Object implementor1 = new GreeterImplMixedStyle(" version1");
         EndpointImpl ep1 = (EndpointImpl) Endpoint.publish(address,  
implementor1);

         ep1.getServer().getEndpoint().put("version", "1");
         ep1.getServer().getEndpoint().put("allow-multiplex-endpoint",  
Boolean.TRUE);

         //Register a MediatorInInterceptor on this dummy service

         Object implementor2 = new GreeterImplMixedStyle(" version2");
         EndpointImpl ep2 = (EndpointImpl) Endpoint.publish(address,  
implementor2);
         ep2.getServer().getEndpoint().put("version", "2");

         MultipleEndpointObserver meo = (MultipleEndpointObserver)
             ep1.getServer().getDestination().getMessageObserver();
         meo.getRoutingInterceptors().clear();
         meo.getRoutingInterceptors().add(new MediatorInInterceptor());


[1]https://svn.apache.org/repos/asf/cxf/trunk/systests/uncategorized/src/test/java/org/apache/cxf/systest/versioning/ClientServerVersioningTest.java
[2]https://svn.apache.org/repos/asf/cxf/trunk/systests/uncategorized/src/test/java/org/apache/cxf/systest/versioning/MediatorInInterceptor.java

Freeman
On 2011-12-28, at 下午5:51, xuhb wrote:

> Hi:
>    Does anyone know when will  
> org.apache.cxf.transport.MultipleEndpointObserver be used?
>
>    Does it means CXF support a feature: publish multiple endpoint on  
> same address?
>
>    Thanks any suggestion.

---------------------------------------------
Freeman Fang

FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com










Re: What's the usage of MultipleEndpointObserver

Posted by Freeman Fang <fr...@gmail.com>.
Hi,

Yes.

IIRC,  for server side you need write a routingInterceptor to dispatch  
message to different endpoint.
When multiple endpoints publish to same address, those endpoints will  
share same MultipleEndpointObserver, by default, the  
MultipleEndpointObserver will use EndpointSelectionInterceptor to  
select on the proper endpoint based on soap version, this is a typical  
usecase which different endpoints(use soap11 or soap12) get published  
to same uri.
You can replace this routingInterceptor for your purpose, we actually  
have a testcase[1] which demonstrate how it works, the  
routingInterceptor used in this tesecase is[2]
The key code to publish different endpoints on same address and  
register a  MultipleEndpointObserver which use the routingInterceptor  
you want is

         String address = "http://localhost:" + PORT + "/SoapContext/ 
SoapPort";

         Object implementor1 = new GreeterImplMixedStyle(" version1");
         EndpointImpl ep1 = (EndpointImpl) Endpoint.publish(address,  
implementor1);

         ep1.getServer().getEndpoint().put("version", "1");
         ep1.getServer().getEndpoint().put("allow-multiplex-endpoint",  
Boolean.TRUE);

         //Register a MediatorInInterceptor on this dummy service

         Object implementor2 = new GreeterImplMixedStyle(" version2");
         EndpointImpl ep2 = (EndpointImpl) Endpoint.publish(address,  
implementor2);
         ep2.getServer().getEndpoint().put("version", "2");

         MultipleEndpointObserver meo = (MultipleEndpointObserver)
             ep1.getServer().getDestination().getMessageObserver();
         meo.getRoutingInterceptors().clear();
         meo.getRoutingInterceptors().add(new MediatorInInterceptor());


[1]https://svn.apache.org/repos/asf/cxf/trunk/systests/uncategorized/src/test/java/org/apache/cxf/systest/versioning/ClientServerVersioningTest.java
[2]https://svn.apache.org/repos/asf/cxf/trunk/systests/uncategorized/src/test/java/org/apache/cxf/systest/versioning/MediatorInInterceptor.java

Freeman
On 2011-12-28, at 下午5:51, xuhb wrote:

> Hi:
>    Does anyone know when will  
> org.apache.cxf.transport.MultipleEndpointObserver be used?
>
>    Does it means CXF support a feature: publish multiple endpoint on  
> same address?
>
>    Thanks any suggestion.

---------------------------------------------
Freeman Fang

FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com










What's the usage of MultipleEndpointObserver

Posted by xuhb <xu...@tongtech.com>.
Hi:
    Does anyone know when will org.apache.cxf.transport.MultipleEndpointObserver be used?

    Does it means CXF support a feature: publish multiple endpoint on same address?

    Thanks any suggestion.

Re: Preparing for DOSGi RI 1.3 release

Posted by Sergey Beryozkin <sb...@gmail.com>.
I got rid of the references to the remoteadmin and compendium modules,
things seem to be OK, so we are nearly ready to go for 1.3

Sergey

On 25/01/12 07:48, David Bosschaert wrote:
> +1 on including the enterprise jar. It should also replace the
> compendium jar if that's currently mentioned in the project...
>
> Cheers,
>
> David
>
> On 24 January 2012 18:37, jbert<al...@gmail.com>  wrote:
>> I second the need for the enterprise API jar.
>>
>> I would also like to note that the POMs in trunk still need to be changed to
>> point to the org.osgi.enterprise JAR, right now they're still pointing to
>> the remoteadmin project. This means that the current sources cannot be built
>> unless you check out a revision of November and build the remoteadmin
>> project to get a 1.3 SNAPSHOT.
>>
>> If it's not clear what I mean, I could create a simple patch tomorrow.
>>
>>
>> Best regards,
>>
>> Bert
>>
>>
>> --
>> View this message in context: http://cxf.547215.n5.nabble.com/Preparing-for-DOSGi-RI-1-3-release-tp5094303p5324430.html
>> Sent from the cxf-dev mailing list archive at Nabble.com.


-- 
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Blog: http://sberyozkin.blogspot.com

Re: Preparing for DOSGi RI 1.3 release

Posted by David Bosschaert <da...@gmail.com>.
+1 on including the enterprise jar. It should also replace the
compendium jar if that's currently mentioned in the project...

Cheers,

David

On 24 January 2012 18:37, jbert <al...@gmail.com> wrote:
> I second the need for the enterprise API jar.
>
> I would also like to note that the POMs in trunk still need to be changed to
> point to the org.osgi.enterprise JAR, right now they're still pointing to
> the remoteadmin project. This means that the current sources cannot be built
> unless you check out a revision of November and build the remoteadmin
> project to get a 1.3 SNAPSHOT.
>
> If it's not clear what I mean, I could create a simple patch tomorrow.
>
>
> Best regards,
>
> Bert
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/Preparing-for-DOSGi-RI-1-3-release-tp5094303p5324430.html
> Sent from the cxf-dev mailing list archive at Nabble.com.

Re: Preparing for DOSGi RI 1.3 release

Posted by jbert <al...@gmail.com>.
I second the need for the enterprise API jar.

I would also like to note that the POMs in trunk still need to be changed to
point to the org.osgi.enterprise JAR, right now they're still pointing to
the remoteadmin project. This means that the current sources cannot be built
unless you check out a revision of November and build the remoteadmin
project to get a 1.3 SNAPSHOT.

If it's not clear what I mean, I could create a simple patch tomorrow.


Best regards,

Bert


--
View this message in context: http://cxf.547215.n5.nabble.com/Preparing-for-DOSGi-RI-1-3-release-tp5094303p5324430.html
Sent from the cxf-dev mailing list archive at Nabble.com.

Re: Preparing for DOSGi RI 1.3 release

Posted by Sergey Beryozkin <sb...@gmail.com>.
I'm thinking that 
org.osgi/org.osgi.enterprise/org.osgi.enterprise-4.2.0.jar needs to be 
included in the single bundle distro (this is a replacement for the 
dosgi ri local copy of the remote admin packages).

As a side note may be we should add a dosgi feature into our CXF Karaf 
profile, as my tests with the Talend distro have shown that DOSGi RI 
CXF-DSW loads fine and supports the deployment of JAXWS & JAXRS 
endpoints. This feature will point to 4 artifacts (OSGI compendium & 
enterprise, cxf-dsw & cxf topology manager) - I will start a new thread 
after DOSGI 1.3 is done in January

Sergey



On 22/12/11 10:46, Sergey Beryozkin wrote:
> Hi All,
>
> Dan, myself and David talked about the possibility of releasing DOSGi RI
> 1.3 based on Apache CXF.
>
> There are few reasons why we thought it was a good idea to pursue it.
>
> We are seeing a number of users periodically asking DOSGI-related
> questions and it's been unfortunate that some basic bugs have stopped
> users from experimenting with DOSGi and proceeding with the POC
> deployments and such though we believe a number of users have actually
> successfully deployed DOSGI RI in their projects without major problems
> or by fixing bugs locally and submitting patched back to the DOSGi RI
> project.
>
> So helping the community with fixing as many bugs as realistically
> possible in the short term and releasing DOSGi RI 1.3 is important.
>
> DOSGi RI has CXF JAX-WS and JAX-RS frontends operating on the OSGI
> Service registrations and look-ups and hence we hope that it can open up
> more interesting options for users to deploy web services in OSGi and
> therefore stress CXF from a different direction.
>
> I've spent few days on closing the JIRAs reported against DOSGi 1.1 and
> 1.2 due to DOSGI 1.3-SNAPSHOT has had its dependencies changed a lot
> (thanks to a major patch from Ancoron Luciferis), with CXF 2.5.1
> supporting it now. I've also resolved a lot of JIRAs containing patches
> or hints on some basic modifications needed to get the issues fixed.
>
> Two modules have been removed, a zookeeper bundle wrapper and the local
> OSGI RemoteAdminService code which is now available in Central.
>
> Here is a complete list:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+DOSGI+AND+resolutiondate+%3E%3D-1w+ORDER+BY+updated+DESC
>
>
> Here is the list of outstanding issues:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+DOSGI+AND+resolutiondate+%3E%3D-1w+ORDER+BY+updated+DESC
>
>
> IMHO we are nearly good to go with the 1.3 release. What I'd like to do
> is to ask users who are interested in working or experimenting with
> DOSGi to give 1.3-SNAPSHOT a test on the latest Felix or Equinox
> distributions as well as check the list of outstanding issues and may be
> submit a couple of more patches.
>
> Personally I'd get a pint to anyone who will figure out how to fix
> https://issues.apache.org/jira/browse/DOSGI-18 :-) (that works in a
> single bundle case), though in case of JAX-RS the consumers can be the
> browsers.
>
> https://issues.apache.org/jira/browse/DOSGI-106
> also seems important enough, though HttpService can be used just fine
> with multi-bundle distros.
>
> So please give it a test, consider fixing a couple of more issues and we
> will be ready to proceed with the release early next year
>
> Thanks, Sergey


-- 
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Blog: http://sberyozkin.blogspot.com

Re: Preparing for DOSGi RI 1.3 release

Posted by Sergey Beryozkin <sb...@gmail.com>.
I'm thinking that 
org.osgi/org.osgi.enterprise/org.osgi.enterprise-4.2.0.jar needs to be 
included in the single bundle distro (this is a replacement for the 
dosgi ri local copy of the remote admin packages).

As a side note may be we should add a dosgi feature into our CXF Karaf 
profile, as my tests with the Talend distro have shown that DOSGi RI 
CXF-DSW loads fine and supports the deployment of JAXWS & JAXRS 
endpoints. This feature will point to 4 artifacts (OSGI compendium & 
enterprise, cxf-dsw & cxf topology manager) - I will start a new thread 
after DOSGI 1.3 is done in January

Sergey



On 22/12/11 10:46, Sergey Beryozkin wrote:
> Hi All,
>
> Dan, myself and David talked about the possibility of releasing DOSGi RI
> 1.3 based on Apache CXF.
>
> There are few reasons why we thought it was a good idea to pursue it.
>
> We are seeing a number of users periodically asking DOSGI-related
> questions and it's been unfortunate that some basic bugs have stopped
> users from experimenting with DOSGi and proceeding with the POC
> deployments and such though we believe a number of users have actually
> successfully deployed DOSGI RI in their projects without major problems
> or by fixing bugs locally and submitting patched back to the DOSGi RI
> project.
>
> So helping the community with fixing as many bugs as realistically
> possible in the short term and releasing DOSGi RI 1.3 is important.
>
> DOSGi RI has CXF JAX-WS and JAX-RS frontends operating on the OSGI
> Service registrations and look-ups and hence we hope that it can open up
> more interesting options for users to deploy web services in OSGi and
> therefore stress CXF from a different direction.
>
> I've spent few days on closing the JIRAs reported against DOSGi 1.1 and
> 1.2 due to DOSGI 1.3-SNAPSHOT has had its dependencies changed a lot
> (thanks to a major patch from Ancoron Luciferis), with CXF 2.5.1
> supporting it now. I've also resolved a lot of JIRAs containing patches
> or hints on some basic modifications needed to get the issues fixed.
>
> Two modules have been removed, a zookeeper bundle wrapper and the local
> OSGI RemoteAdminService code which is now available in Central.
>
> Here is a complete list:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+DOSGI+AND+resolutiondate+%3E%3D-1w+ORDER+BY+updated+DESC
>
>
> Here is the list of outstanding issues:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+DOSGI+AND+resolutiondate+%3E%3D-1w+ORDER+BY+updated+DESC
>
>
> IMHO we are nearly good to go with the 1.3 release. What I'd like to do
> is to ask users who are interested in working or experimenting with
> DOSGi to give 1.3-SNAPSHOT a test on the latest Felix or Equinox
> distributions as well as check the list of outstanding issues and may be
> submit a couple of more patches.
>
> Personally I'd get a pint to anyone who will figure out how to fix
> https://issues.apache.org/jira/browse/DOSGI-18 :-) (that works in a
> single bundle case), though in case of JAX-RS the consumers can be the
> browsers.
>
> https://issues.apache.org/jira/browse/DOSGI-106
> also seems important enough, though HttpService can be used just fine
> with multi-bundle distros.
>
> So please give it a test, consider fixing a couple of more issues and we
> will be ready to proceed with the release early next year
>
> Thanks, Sergey


-- 
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Blog: http://sberyozkin.blogspot.com