Re: CXF Dosgi

2016-03-16 Thread conejo
Sorry, the command is
config:property-set -p cxf-dsw httpBase http://192.168.21.11:8181



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045814.html
Sent from the Karaf - User mailing list archive at Nabble.com.


Re: CXF Dosgi

2016-03-16 Thread conejo
Hi, christian.
With the file does not work:

karaf @ root ()> config: list | grep httpB
httpBase = http://192.168.21.11:8181

But address is 172 in the client.

I have to run the command:
config: property-set -p cxf-DSW httpBase http://192.168.21.11:8181

Now:
karaf @ root ()> config: list | grep httpB
httpBase = http://192.168.21.11:8181
httpBase = http://192.168.21.11:8181

And then it works in the client.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045813.html
Sent from the Karaf - User mailing list archive at Nabble.com.


Re: CXF Dosgi

2016-03-16 Thread Christian Schneider

Create etc/cxf-dsw.cfg with
httpBase=http://192.168.21.11:8181

Christian

On 16.03.2016 08:24, conejo wrote:

Hi, christian.
You were right. I added the lib folder to my distribution and everything
works properly.
However I still need to configure the interface on the client. The scenario
that I have now is the following:

Node 1 (master) with 2 interfaces: 192.168.21.11 and 172.19.30.158. The log
tells me that the service is exported in 172 interface.
Node 2 (client) with 192.168.21.150 interface.

The customer does not find the service because is trying to access the
interface 172.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045804.html
Sent from the Karaf - User mailing list archive at Nabble.com.



--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com



Re: CXF Dosgi

2016-03-16 Thread conejo
Hi, christian.
You were right. I added the lib folder to my distribution and everything
works properly.
However I still need to configure the interface on the client. The scenario
that I have now is the following:

Node 1 (master) with 2 interfaces: 192.168.21.11 and 172.19.30.158. The log
tells me that the service is exported in 172 interface.
Node 2 (client) with 192.168.21.150 interface.

The customer does not find the service because is trying to access the
interface 172.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045804.html
Sent from the Karaf - User mailing list archive at Nabble.com.


Re: CXF Dosgi

2016-03-15 Thread Scott Lewis
ECF fully implements the latest versions of both the OSGi R6 Remote 
Services (1.0) and Remote Service Admin (1.1) specifications.  
Compliance with the specifications is tested daily by running the OSGi 
R6 Compatibility test suite as part of our continuous integration.


ECF also has a 'pluggable distribution provider' approach, and currently 
supports a variety of distribution providers including CXF, Jersey 
Jax-RS, Hazelcast, tcp, JMS, rosgi, websockets, and others [1].


We have a release coming up this week (3.13.0) [3] that among other 
things introduces a simplified API for creating distribution 
providers.   All such providers will be automatically compliant with the 
OSGi R6 specifications, and of course may be done in open source or not 
using whatever transport is desired.


I am working on a tutorial for this new API as we speak, but for a 
preview here is the tutorial codebase [2].


Once it is fully in place, we will also be supporting the Aries 
distribution provider API Christian mentions.


We would very much like to have a Cellar-based distribution provider as 
well.   Perhaps the simplified distribution provider API [2] will assist 
in making this happen.


Scott

[1] http://wiki.eclipse.org/Distribution_Providers
[2] https://github.com/ECF/ExampleRSADistributionProviders
[3] https://projects.eclipse.org/projects/rt.ecf/releases/3.13.0

On 3/15/2016 11:00 AM, Christian Schneider wrote:
CXF-DOSGi and cellar DOSGi are not related till now but they implement 
different specs anyway.

Cellar DOSGi implements the older and simpler Remote Services spec.

JB is planning to create a new Hazelcast transport for Aries RSA that 
then might replace Cellar DOSGi.


Christian

On 15.03.2016 17:39, Leschke, Scott wrote:
I'm curious what the relationship is between CXF DOSGi and Cellar 
DOSGi (feature:install cellar-dosgi)?


Scott

-Original Message-
From: Christian Schneider [mailto:cschneider...@gmail.com] On Behalf 
Of Christian Schneider

Sent: Tuesday, March 15, 2016 11:05 AM
To: user@karaf.apache.org
Subject: Re: CXF Dosgi

The service worked fine for me:
feature:repo-add cxf-dosgi 1.7.0
feature:install cxf-dosgi-discovery-distributed 
cxf-dosgi-zookeeper-server install -s mvn:es.yaroki/service


Log shows:
2016-03-15 17:03:08,157 | INFO  | er])-EventThread |
PublishingEndpointListener   | 53 -
cxf-dosgi-ri-discovery-distributed - 1.7.0 | Local EndpointDescription
added: {endpoint.framework.uuid=8ed1316c-e222-4e37-8135-69be5c92f3f8,
endpoint.id=http://172.20.0.187:8181/cxf/ILblService,
endpoint.package.version.es.yaroki.service=0.0.1,
endpoint.service.id=112, objectClass=[es.yaroki.service.MyService],
org.apache.cxf.ws.address=http://172.20.0.187:8181/cxf/ILblService,
osgi.service.blueprint.compname=serviceBean, service.bundleid=52, 
service.imported=true, service.imported.configs=[org.apache.cxf.ws],

service.intents=[SOAP.1_1, HTTP, SOAP], service.scope=bundle}

and the service is available.

Christian


On 15.03.2016 16:45, conejo wrote:

Try this:

https://github.com/LuisLozano/dosgi



--
View this message in context:
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045793.html
Sent from the Karaf - User mailing list archive at Nabble.com.


--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com








Re: CXF Dosgi

2016-03-15 Thread Christian Schneider
CXF-DOSGi and cellar DOSGi are not related till now but they implement 
different specs anyway.

Cellar DOSGi implements the older and simpler Remote Services spec.

JB is planning to create a new Hazelcast transport for Aries RSA that 
then might replace Cellar DOSGi.


Christian

On 15.03.2016 17:39, Leschke, Scott wrote:

I'm curious what the relationship is between CXF DOSGi and Cellar DOSGi 
(feature:install cellar-dosgi)?

Scott

-Original Message-
From: Christian Schneider [mailto:cschneider...@gmail.com] On Behalf Of 
Christian Schneider
Sent: Tuesday, March 15, 2016 11:05 AM
To: user@karaf.apache.org
Subject: Re: CXF Dosgi

The service worked fine for me:
feature:repo-add cxf-dosgi 1.7.0
feature:install cxf-dosgi-discovery-distributed cxf-dosgi-zookeeper-server 
install -s mvn:es.yaroki/service

Log shows:
2016-03-15 17:03:08,157 | INFO  | er])-EventThread |
PublishingEndpointListener   | 53 -
cxf-dosgi-ri-discovery-distributed - 1.7.0 | Local EndpointDescription
added: {endpoint.framework.uuid=8ed1316c-e222-4e37-8135-69be5c92f3f8,
endpoint.id=http://172.20.0.187:8181/cxf/ILblService,
endpoint.package.version.es.yaroki.service=0.0.1,
endpoint.service.id=112, objectClass=[es.yaroki.service.MyService],
org.apache.cxf.ws.address=http://172.20.0.187:8181/cxf/ILblService,
osgi.service.blueprint.compname=serviceBean, service.bundleid=52, 
service.imported=true, service.imported.configs=[org.apache.cxf.ws],
service.intents=[SOAP.1_1, HTTP, SOAP], service.scope=bundle}

and the service is available.

Christian


On 15.03.2016 16:45, conejo wrote:

Try this:

https://github.com/LuisLozano/dosgi



--
View this message in context:
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045793.html
Sent from the Karaf - User mailing list archive at Nabble.com.


--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com




--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com



Re: CXF Dosgi

2016-03-15 Thread Christian Schneider

I also tried the wsdl link and it worked fine.

I am pretty sure your problem is because of your assembly. Try it in 
karaf like I did. I think you did not use the correct

libs in endorsed and lib. Compare it with a real karaf.

You can give a full address in  org.apache.cxf.ws.address but I would 
not recommend it as you then have to manage ports manually.


Christian

On 15.03.2016 17:53, conejo wrote:

Thanx Christian.

Have you tried the link?
The problem I have it when you access the link /cxf/ILblService?wsdl

If I delete  I can see the wsdl but on port 9000 and the client looks for localhost.
So I wanted to know how to configure the host and port by default.

It's very strange. Can it be due to assembly?



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045798.html
Sent from the Karaf - User mailing list archive at Nabble.com.



--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com



Re: CXF Dosgi

2016-03-15 Thread conejo
Thanx Christian.

Have you tried the link?
The problem I have it when you access the link /cxf/ILblService?wsdl

If I delete  I can see the wsdl but on port 9000 and the client looks for localhost.
So I wanted to know how to configure the host and port by default.

It's very strange. Can it be due to assembly?



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045798.html
Sent from the Karaf - User mailing list archive at Nabble.com.


Re: CXF Dosgi

2016-03-15 Thread Christian Schneider

The service worked fine for me:
feature:repo-add cxf-dosgi 1.7.0
feature:install cxf-dosgi-discovery-distributed cxf-dosgi-zookeeper-server
install -s mvn:es.yaroki/service

Log shows:
2016-03-15 17:03:08,157 | INFO  | er])-EventThread | 
PublishingEndpointListener   | 53 - 
cxf-dosgi-ri-discovery-distributed - 1.7.0 | Local EndpointDescription 
added: {endpoint.framework.uuid=8ed1316c-e222-4e37-8135-69be5c92f3f8, 
endpoint.id=http://172.20.0.187:8181/cxf/ILblService, 
endpoint.package.version.es.yaroki.service=0.0.1, 
endpoint.service.id=112, objectClass=[es.yaroki.service.MyService], 
org.apache.cxf.ws.address=http://172.20.0.187:8181/cxf/ILblService, 
osgi.service.blueprint.compname=serviceBean, service.bundleid=52, 
service.imported=true, service.imported.configs=[org.apache.cxf.ws], 
service.intents=[SOAP.1_1, HTTP, SOAP], service.scope=bundle}


and the service is available.

Christian


On 15.03.2016 16:45, conejo wrote:

Try this:

https://github.com/LuisLozano/dosgi



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045793.html
Sent from the Karaf - User mailing list archive at Nabble.com.



--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com



Re: CXF Dosgi

2016-03-15 Thread conejo
Try this:

https://github.com/LuisLozano/dosgi



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045793.html
Sent from the Karaf - User mailing list archive at Nabble.com.


Re: CXF Dosgi

2016-03-15 Thread conejo
Now I have the following exception:

javax.xml.stream.FactoryConfigurationError: Provider for class
javax.xml.stream.XMLOutputFactory cannot be created
...
... 48 more
Caused by: java.util.ServiceConfigurationError:
javax.xml.stream.XMLOutputFactory: Provider
com.ctc.wstx.stax.WstxOutputFactory not found
at java.util.ServiceLoader.fail(ServiceLoader.java:239)[:1.8.0_31]
at java.util.ServiceLoader.access$300(ServiceLoader.java:185)[:1.8.0_31]
at
java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:372)[:1.8.0_31]
at
java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)[:1.8.0_31]
at java.util.ServiceLoader$1.next(ServiceLoader.java:480)[:1.8.0_31]
at javax.xml.stream.FactoryFinder$1.run(FactoryFinder.java:353)
at java.security.AccessController.doPrivileged(Native Method)[:1.8.0_31]
at
javax.xml.stream.FactoryFinder.findServiceProvider(FactoryFinder.java:341)
... 48 more



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045791.html
Sent from the Karaf - User mailing list archive at Nabble.com.


Re: CXF Dosgi

2016-03-15 Thread Christian Schneider

Please try to also set the service property:
org.apache.cxf.ws.address=/ILblService

Christian

On 15.03.2016 13:56, conejo wrote:

Sorry, but I do not understand.
I am using blueprint and I added the property



int the service and the features of cxf-dosgi in karaf.
I have also defined the org.apache.cxf.dosgi.discovery.zookeeper.server.cfg
files and org.apache.cxf.dosgi.discovery.zookeeper.cfg

Karaf has automatically deployed my service on port 9000 (although the
console is deployed in 8181).
I can see the wsdl in localhost:9000/en/yaroki/service/api/ILblService?wsdl

On the client I added org.apache.cxf.dosgi.discovery.zookeeper.cfg and
features of cxf. The client finds the service (I guess that creates the
proxy), but when trying to use, the log shows me the message said. The
question is:

Where do I configure the service host in the client? because it seems that
it is using localhost.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045789.html
Sent from the Karaf - User mailing list archive at Nabble.com.



--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com



Re: CXF Dosgi

2016-03-15 Thread conejo

Sorry, but I do not understand.
I am using blueprint and I added the property



int the service and the features of cxf-dosgi in karaf.
I have also defined the org.apache.cxf.dosgi.discovery.zookeeper.server.cfg
files and org.apache.cxf.dosgi.discovery.zookeeper.cfg

Karaf has automatically deployed my service on port 9000 (although the
console is deployed in 8181).
I can see the wsdl in localhost:9000/en/yaroki/service/api/ILblService?wsdl

On the client I added org.apache.cxf.dosgi.discovery.zookeeper.cfg and
features of cxf. The client finds the service (I guess that creates the
proxy), but when trying to use, the log shows me the message said. The
question is:

Where do I configure the service host in the client? because it seems that
it is using localhost.



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786p4045789.html
Sent from the Karaf - User mailing list archive at Nabble.com.


Re: CXF Dosgi

2016-03-15 Thread Christian Schneider

You can use
org.apache.cxf.rs.address=/myservice
or
org.apache.cxf.ws.address

If you use a path that starts with "/" then CXF uses the http service. 
So not every service needs it own port.


See this for a full example:
https://github.com/cschneider/Karaf-Tutorial/blob/master/tasklist-ds/service/src/main/java/net/lr/tasklist/service/TaskServiceRest.java

On the client you can not change the url. The idea in DOSGi is that the 
endpoint is published to discovery and the client picks up these settings.


Btw. If you use DOSGi you should also take a look at:
http://aries.apache.org/modules/rsa.html

We just moved the core of CXF-DOSGi to Apache Aries. There is also a new 
transport using java serialization over tcp. So if you
just need transparent remoting then this might be handy as you do not 
have all the CXF deps.


Christian

On 15.03.2016 11:20, conejo wrote:

Good Morning.
When I run a cxf-dosgi service on a remote instance I get the following
output:
java.net.ConnectException: Invoking ConnectException http: // localhost:
9000
...

I guess karaf are using localhost and port 9000 by default.

How I can specify the host and port where the services are?
Both server and client.

Thanx



--
View this message in context: 
http://karaf.922171.n3.nabble.com/CXF-Dosgi-tp4045786.html
Sent from the Karaf - User mailing list archive at Nabble.com.



--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com