cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantinos Mavridis <konstantinos.mavri...@live.com>
Subject RE: CXF Distributed OSGi with Blueprint demo
Date Tue, 26 Feb 2013 14:34:39 GMT
The service side appears to function without problems, the WSDL is returned correctly and service
invocation using soapUI is successful. The issue appears to be on the client side.

> From: konstantinos.mavridis@live.com
> To: users@cxf.apache.org
> Subject: CXF Distributed OSGi with Blueprint demo
> Date: Tue, 26 Feb 2013 11:58:54 +0200
> 
> Hi all,
> 
> I have put together an example based on the the "CXF Distributed OSGi with Declarative
Services demo" (http://cxf.apache.org/dosgi-ds-demo-page.html) using Blueprint as the activation
method. Essentially, replacing the DS portions with Blueprint. It is available at https://github.com/Konstantinos-Mavridis/bluCXF-DOSGi.
> 
> However, while the service appears to get published and the client appears to bind to
a host reference, no service invocation takes place. It seems as if the cxf-specific part
never gets triggered.
> 
> Below are the relevant log entries from each side after starting the two Equinox instances
(more info about the setup on Github). Hopefully, this is due to some misconfiguration; if
we can get it working perhaps it could be added along the existing cxf-dosgi samples.
> 
> <snip>
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message