No, I didn't.
I have tried now, but the same occurs, it seems that this property is
ignored. I tried now with:
props.put("service.exported.interfaces", "*");
props.put("service.exported.configs", "org.apache.cxf.ws");
props.put("org.apache.cxf.ws.httpservice.context", "/SimUtils");
props.put("org.apache.cxf.servlet.base-address",
"http://localhost:8080";);
The problem is that the URI http://localhost:8080/SimUtils does exist,
but it isn't the endpoint of the service but a review of the services.
It indicates that the endpoint address can be found at
http://localhost:9000/bla/bla/bla/SimUtils.
Any other idea?
On 15/05/15 18:16, Sergey Beryozkin wrote:
Hi
Do you configure somewhere an "org.apache.cxf.servlet.base-address"
property ? I can only think of the default CXF HTTP transport using it...
Cheers, Sergey
On 15/05/15 14:03, bminano wrote:
Hi,
I've been using DOSGI CXF from long with a older version and I need to
update.
I changed to version 1.6, but the web service endpoint is not as I
supposed
to be.
My configuration is as following:
props.put("service.exported.interfaces", "*");
props.put("service.exported.configs", "org.apache.cxf.ws");
props.put("org.apache.cxf.ws.httpservice.context",
"/SimUtils");
So I expect the service to be published at
http://localhost:8080/SimUtils?wsdl, but, to my surprise, the URL is a
review of the list of services available and the endpoint set is
http://localhost:9000/bla/bla/bla/SimUtils.
Why does it changes the domain? I need the same domain to avoid CORS
problems.
In version 1.1 it worked as I expected.
Am I missing something?
--
View this message in context:
http://cxf.547215.n5.nabble.com/DOSGI-ws-register-different-domain-tp5757303.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
--
Un saludo,
Borja Miñano
IAC3 - Universitat de les Illes Balears
Mateu Orfila Building. Office F-213.
Cra.Valldemossa km. 7,5 E-07122
Palma de Mallorca. Balears. Spain.
Phone: +34 971 173 000 ext. 1318
