DOSGi deploy failing on Hudson
Hi all, The DOSGi deploy build on Hudson is failing with the following: [INFO] Error deploying artifact: Authorization failed: Access denied to: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remote-service-admin-interfaces-1.0.0.jar See [1]. Anyone an idea what might be causing this or how to resolve it? Thanks! David [1] http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-DOSGi-deploy/81/org.apache.cxf.dosgi$cxf-dosgi-remote-service-admin-interfaces/console
Re: DOSGi deploy failing on Hudson
Hmmm ... smells like a Nexus issue. If I follow that link, I'm redirected to: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remote-service-admin-interfaces-1.0.0.jar with the message: Item not found on path "/org/apache/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remote-service-admin-interfaces-1.0.0.jar" in repository "orgapachecxf-001"!This looks a reference to a temporary staging area created by Nexus, for use for example while a release vote is in motion (so for the recent dOSGi 1.1 release that I cut, the staging area was assigned orgapachecxf-021). Normally when the vote is declared, the staging area would be closed as the artifacts are promoted. I'd expect the backing storage is discarded by Nexus. I don't know why its pointing back to the first CXF staging area ever created in this case (i.e. the "-001" suffix) but that would have long since ceased to exist. Maybe report the issue to the infrastructure folks, or whomever has admin access to Nexus. Cheers, Eoghan 2009/12/18 > Hi all, > > The DOSGi deploy build on Hudson is failing with the following: > > [INFO] Error deploying artifact: Authorization failed: Access denied > to: > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remote-service-admin-interfaces-1.0.0.jar > > See [1]. Anyone an idea what might be causing this or how to resolve it? > > Thanks! > > David > > [1] > http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-DOSGi-deploy/81/org.apache.cxf.dosgi$cxf-dosgi-remote-service-admin-interfaces/console >
Re: svn commit: r892222 - in /cxf/dosgi/trunk/dsw/cxf-dsw/src: main/java/org/apache/cxf/dosgi/dsw/handlers/ test/java/org/apache/cxf/dosgi/dsw/handlers/
Hi David Author: davidb Date: Fri Dec 18 11:16:42 2009 New Revision: 89 URL: http://svn.apache.org/viewvc?rev=89&view=rev Log: Added support for old way of configuring endpoint location back in. The following properties on the exposed services are now equivalents and can be set to a value such as http://localhost:9876/myService endpoint.uri org.apache.cxf.ws.address osgi.remote.configuration.pojo.address The endpoint.uri is a new property that's introduced in the OSGi Remote Service Admin spec. This is now the standard way to configure the endpoint URI. The old properties are still supported for backward compatibility. This endpoint.uri property will work JAXRS services as well ? If we let users have the same OSGI service exposed as SOAP and RESTful services, how will it work with this property being used ? Perhaps in this latter case org.apache.cxf.ws.address and org.apache.cxf.rs.address thanks, Sergey
Re: svn commit: r892222 - in /cxf/dosgi/trunk/dsw/cxf-dsw/src: main/java/org/apache/cxf/dosgi/dsw/handlers/ test/java/org/apache/cxf/dosgi/dsw/handlers/
Hi Sergey, 2009/12/18 Sergey Beryozkin : > Hi David > >> Author: davidb >> Date: Fri Dec 18 11:16:42 2009 >> New Revision: 89 >> >> URL: http://svn.apache.org/viewvc?rev=89&view=rev >> Log: >> Added support for old way of configuring endpoint location back in. The >> following properties on the exposed services are now equivalents and can be >> set to a value such as http://localhost:9876/myService >> endpoint.uri >> org.apache.cxf.ws.address >> osgi.remote.configuration.pojo.address >> The endpoint.uri is a new property that's introduced in the OSGi Remote >> Service Admin spec. This is now the standard way to configure the endpoint >> URI. The old properties are still supported for backward compatibility. > > This endpoint.uri property will work JAXRS services as well ? > > If we let users have the same OSGI service exposed as SOAP and RESTful > services, how will it work with this property being used ? Perhaps in this > latter case org.apache.cxf.ws.address and org.apache.cxf.rs.address > > thanks, Sergey The we haven't refactored the JAX-RS handlers yet, see: http://old.nabble.com/Re%3A-Migrating-CXF-DOSGi-to-be-complaint-with-the-new-OSGi-Remote--Service-Admin-spec-p26826519.html But when we get to JAX-RS, it should also support the endpoint.uri property. If you have a single service that you want to expose through both using SOAP and REST we could make that possible by letting the user set org.apache.cxf.rs.address and org.apache.cxf.ws.address, since there's no overlap with these properties. Would that work for you? Cheers, David
Re: svn commit: r892222 - in /cxf/dosgi/trunk/dsw/cxf-dsw/src: main/java/org/apache/cxf/dosgi/dsw/handlers/ test/java/org/apache/cxf/dosgi/dsw/handlers/
Hi David The endpoint.uri is a new property that's introduced in the OSGi Remote Service Admin spec. This is now the standard way to configure the endpoint URI. The old properties are still supported for backward compatibility. This endpoint.uri property will work JAXRS services as well ? If we let users have the same OSGI service exposed as SOAP and RESTful services, how will it work with this property being used ? Perhaps in this latter case org.apache.cxf.ws.address and org.apache.cxf.rs.address thanks, Sergey The we haven't refactored the JAX-RS handlers yet, see: http://old.nabble.com/Re%3A-Migrating-CXF-DOSGi-to-be-complaint-with-the-new-OSGi-Remote--Service-Admin-spec-p26826519.html But when we get to JAX-RS, it should also support the endpoint.uri property. If you have a single service that you want to expose through both using SOAP and REST we could make that possible by letting the user set org.apache.cxf.rs.address and org.apache.cxf.ws.address, since there's no overlap with these properties. Would that work for you? S.B : yes, it would, I think we're in agreement :-) cheers, Sergey Cheers, David
Re: DOSGi deploy failing on Hudson
The problem is due to: parent/pom.xml: 1.0.0 Thus, the build of dsw/cxf-osgi-remote-service-admin-interfaces/pom.xml is considered a release and is trying to deploy as a release. That version number needs to change to a SNAPSHOT. Dan On Fri December 18 2009 4:35:36 am dav...@apache.org wrote: > Hi all, > > The DOSGi deploy build on Hudson is failing with the following: > > [INFO] Error deploying artifact: Authorization failed: Access denied > to: > https://repository.apache.org/service/local/staging/deploy/maven2/org/apac > he/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remo > te-service-admin-interfaces-1.0.0.jar > > See [1]. Anyone an idea what might be causing this or how to resolve it? > > Thanks! > > David > > [1] > http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-DOSGi-deploy/81/org > .apache.cxf.dosgi$cxf-dosgi-remote-service-admin-interfaces/console > -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
Re: DOSGi deploy failing on Hudson
Ok - I'll take a look. I can't just change it to 1.0.0-SNAPSHOT because these classes are defined by the OSGi Alliance and their version is actually 1.0.0. But maybe we can avoid building this module separately, this module is only an internal artefact for DOSGi... Cheers, David 2009/12/18 Daniel Kulp : > > > The problem is due to: > parent/pom.xml: > 1.0.0 > > > Thus, the build of > dsw/cxf-osgi-remote-service-admin-interfaces/pom.xml > > is considered a release and is trying to deploy as a release. That version > number needs to change to a SNAPSHOT. > > Dan > > > On Fri December 18 2009 4:35:36 am dav...@apache.org wrote: >> Hi all, >> >> The DOSGi deploy build on Hudson is failing with the following: >> >> [INFO] Error deploying artifact: Authorization failed: Access denied >> to: >> https://repository.apache.org/service/local/staging/deploy/maven2/org/apac >> he/cxf/dosgi/cxf-dosgi-remote-service-admin-interfaces/1.0.0/cxf-dosgi-remo >> te-service-admin-interfaces-1.0.0.jar >> >> See [1]. Anyone an idea what might be causing this or how to resolve it? >> >> Thanks! >> >> David >> >> [1] >> http://hudson.zones.apache.org/hudson/view/CXF/job/CXF-DOSGi-deploy/81/org >> .apache.cxf.dosgi$cxf-dosgi-remote-service-admin-interfaces/console >> > > -- > Daniel Kulp > dk...@apache.org > http://www.dankulp.com/blog >
