Distributed OSGi update
Hi all, Just a little update on how things are going wrt to the Distributed OSGi implementation that is currently in the CXF sandbox. Last week Eoghan, Sergey and myself were participating in the OSGi BundleFest in Montpellier (France) where we worked hard on integrating the various parts of Distributed OSGi (also known as OSGi RFC 119 [1]). These parts are: * The Distribution Software (DSW) Reference Implementation, this is what is based on CXF and what currently lives in the CXF sandbox. * The Discovery Service Refence Implementation. * The OSGi TCK test suite. We can't say that everything fully worked yet, because we found bugs in the various parts, but we did achieve the integration. This means that we did manage to get the DSW/Discovery integration working up to a certain level. We also got the RI parts working in the OSGi TCK framework. There is a lot of work that still needs to be done: - We need better test coverage for the DOSGi RI, esp around system tests. - We need better documentation. Obviously RFC 119 contains a lot of information about how to use Distributed OSGi, and the upcoming OSGi Spec (version 4.2) will also contain a lot of info, we need better documentation on how to build, use and configure CXF-specific pieces (such as CXF-specific intents). - There are still a number of open bugs on the DOSGi implementation. Obviously any help on these things will be great! Looking a little more long-term. We are aiming at having the RFC 119 implementations in good shape well in time for OSGiCon/EclipseCon 2009. The next release of the OSGi Specification is also expected to be available some time in 2009. Best regards, David [1] http://www.osgi.org/download/osgi-4.2-early-draft.pdf
Re: [DOSGi] Patch for CXF-1876
Thanks Eoghan! I've submitted a subsequent patch to this bug which contains extra unit tests. Would appreciate if they could be applied too. Cheers, David 2008/10/16 Eoghan Glynn <[EMAIL PROTECTED]>: > > Thanks David, applied. > Cheers, > Eoghan > > -Original Message- > From: David Bosschaert [mailto:[EMAIL PROTECTED] > Sent: Thu 16/10/2008 12:03 > To: dev@cxf.apache.org > Subject: [DOSGi] Patch for CXF-1876 > > Hi all, > > I've attached a patch to https://issues.apache.org/jira/browse/CXF-1876 > Would greatly appreciate if someone could apply the patch. > > Cheers, > > David > >
RE: Distributed OSGi update
Thanks David for this summary! > There is a lot of work that still needs to be done: > ... > - We need better documentation. On the subject of docco for dOSGi, I wrote up a quick "getting started" guide a while back. It would need a bit of updating as it dates from before the donation of the dOSGi code to CXF (so it refers to our internal SVN repos as opposed to the Apache one). Also its in OpenDocument & PDF formats, so it'll need to be wiki-ified to fit in the CXF docco convention. But it could be a useful starting point. Cheers, Eoghan -Original Message- From: David Bosschaert [mailto:[EMAIL PROTECTED] Sent: Mon 20/10/2008 04:38 To: dev@cxf.apache.org Subject: Distributed OSGi update Hi all, Just a little update on how things are going wrt to the Distributed OSGi implementation that is currently in the CXF sandbox. Last week Eoghan, Sergey and myself were participating in the OSGi BundleFest in Montpellier (France) where we worked hard on integrating the various parts of Distributed OSGi (also known as OSGi RFC 119 [1]). These parts are: * The Distribution Software (DSW) Reference Implementation, this is what is based on CXF and what currently lives in the CXF sandbox. * The Discovery Service Refence Implementation. * The OSGi TCK test suite. We can't say that everything fully worked yet, because we found bugs in the various parts, but we did achieve the integration. This means that we did manage to get the DSW/Discovery integration working up to a certain level. We also got the RI parts working in the OSGi TCK framework. There is a lot of work that still needs to be done: - We need better test coverage for the DOSGi RI, esp around system tests. - We need better documentation. Obviously RFC 119 contains a lot of information about how to use Distributed OSGi, and the upcoming OSGi Spec (version 4.2) will also contain a lot of info, we need better documentation on how to build, use and configure CXF-specific pieces (such as CXF-specific intents). - There are still a number of open bugs on the DOSGi implementation. Obviously any help on these things will be great! Looking a little more long-term. We are aiming at having the RFC 119 implementations in good shape well in time for OSGiCon/EclipseCon 2009. The next release of the OSGi Specification is also expected to be available some time in 2009. Best regards, David [1] http://www.osgi.org/download/osgi-4.2-early-draft.pdf
RE: [DOSGi] Patch for CXF-1876
No worries, will do ... /Eoghan -Original Message- From: David Bosschaert [mailto:[EMAIL PROTECTED] Sent: Mon 20/10/2008 06:08 To: dev@cxf.apache.org Subject: Re: [DOSGi] Patch for CXF-1876 Thanks Eoghan! I've submitted a subsequent patch to this bug which contains extra unit tests. Would appreciate if they could be applied too. Cheers, David 2008/10/16 Eoghan Glynn <[EMAIL PROTECTED]>: > > Thanks David, applied. > Cheers, > Eoghan > > -Original Message- > From: David Bosschaert [mailto:[EMAIL PROTECTED] > Sent: Thu 16/10/2008 12:03 > To: dev@cxf.apache.org > Subject: [DOSGi] Patch for CXF-1876 > > Hi all, > > I've attached a patch to https://issues.apache.org/jira/browse/CXF-1876 > Would greatly appreciate if someone could apply the patch. > > Cheers, > > David > >
RE: [VOTE] Release Apache CXF 2.1.3 (2nd try)
+1 /Eoghan -Original Message- From: Willem Jiang [mailto:[EMAIL PROTECTED] Sent: Sat 18/10/2008 11:19 To: dev@cxf.apache.org Subject: [VOTE] Release Apache CXF 2.1.3 (2nd try) Once again, there have been a bunch of bug fixes and enhancements that have been done compared to the 2.1.2 release. Over 52 JIRA issues are resolved for 2.1.3. List of issues: https://issues.apache.org/jira/browse/CXF/fixforversion/12313354 The staging area is at: http://people.apache.org/~ningjiang/stage_cxf/2.1.3 The distributions are in the "dist" directory. The "maven" directory contains the stuff that will by pushed to the central repository. This release is tagged at: http://svn.apache.org/repos/asf/cxf/tags/cxf-2.1.3 Here is my +1. The vote will be open here for at least 72 hours. Willem
Re: [VOTE] Release Apache CXF 2.1.3 (2nd try)
On Oct 18, 2008, at 11:19 AM, Willem Jiang wrote: Once again, there have been a bunch of bug fixes and enhancements that have been done compared to the 2.1.2 release. Over 52 JIRA issues are resolved for 2.1.3. List of issues: https://issues.apache.org/jira/browse/CXF/fixforversion/12313354 The staging area is at: http://people.apache.org/~ningjiang/stage_cxf/2.1.3 The distributions are in the "dist" directory. The "maven" directory contains the stuff that will by pushed to the central repository. This release is tagged at: http://svn.apache.org/repos/asf/cxf/tags/cxf-2.1.3 Here is my +1. The vote will be open here for at least 72 hours. Willem +1
Re: [VOTE] Release Apache CXF 2.1.3 (2nd try)
+1 Dan On Saturday 18 October 2008 11:19:14 am Willem Jiang wrote: > Once again, there have been a bunch of bug fixes and enhancements that > have been done compared to the 2.1.2 release. Over 52 JIRA issues > are resolved for 2.1.3. > > List of issues: > https://issues.apache.org/jira/browse/CXF/fixforversion/12313354 > > The staging area is at: > http://people.apache.org/~ningjiang/stage_cxf/2.1.3 > > The distributions are in the "dist" directory. The "maven" directory > contains the stuff that will by pushed to the central repository. > > This release is tagged at: > http://svn.apache.org/repos/asf/cxf/tags/cxf-2.1.3 > > > Here is my +1. The vote will be open here for at least 72 hours. > > Willem -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog
Re: Aegis versus jaxrs
I'm getting into trouble here now that I'm debugging a test case. readFrom takes Class, not Class. I don't see how the JAXB code could work, as it will try to obtain a type for 'Object.class', which is the only thing in the world of type Class, AFAIK. My code certainly won't work. I note that none of your unit tests ever call the JAXB Element readFrom. I'll look for the systest. Aegis needs some clue about what types are going to be read.
Re: Aegis versus jaxrs
I also note that even the systest never calls the JAXB 'readFrom' routine. You really need a test for that. On Mon, Oct 20, 2008 at 8:20 PM, Benson Margulies <[EMAIL PROTECTED]> wrote: > I'm getting into trouble here now that I'm debugging a test case. > > readFrom takes Class, not Class. I don't see how the JAXB > code could work, as it will try to obtain a type for 'Object.class', > which is the only thing in the world of type Class, AFAIK. My > code certainly won't work. I note that none of your unit tests ever > call the JAXB Element readFrom. I'll look for the systest. Aegis needs > some clue about what types are going to be read. >
