-
1. Re: Fuse 4.1.3 - cxf-wsdl-first-osgi-package EXAMPLE DOES NOT WORK
theozaf Mar 3, 2011 7:15 AM (in response to theozaf)Just wanted to add that same thing happens with all examples i.e. http://localhost:8080/cxf/HelloWorld?wsdl
I think that my problem is I cannot find the correct port where servicemix should run the deployment. I have also added the .jar files under ./deploy but still nothing happens.
-
2. Re: Fuse 4.1.3 - cxf-wsdl-first-osgi-package EXAMPLE DOES NOT WORK
ubhole Mar 3, 2011 7:53 AM (in response to theozaf)Hi,
The URL should not contain ?wsdl. if you look at the example that comes with Fuse ESB you will see a java client or client.html that can be run against. For starting this example you can simply do features:install examples-cxf-wsdl-first-osgi-package and that shoudl start it.
Regards,
Ulhas Bhole
-
3. Re: Fuse 4.1.3 - cxf-wsdl-first-osgi-package EXAMPLE DOES NOT WORK
theozaf Mar 3, 2011 8:47 AM (in response to ubhole)Hi ubhole, thanks for your advice but I have tried it without the ?wsdl which believe me it should not be a problem as a direct link, it should display the wsdl file. I came to the point that I believe my problem has to do with the port. Although in previous fuse installations whenever I start the serviceMix I can hit the link http://localhost:8181 with this version 4.3.1 I cannot.
All I have done was to unzip the .zip file under a directory without spaces. Should I do anything more?
Edited by: theozaf on Mar 3, 2011 1:46 PM
-
4. Re: Fuse 4.1.3 - cxf-wsdl-first-osgi-package EXAMPLE DOES NOT WORK
ubhole Mar 3, 2011 9:16 AM (in response to theozaf)If you are using default 4.3.1 installation all you need to do is what I mentioned in previous comment. And yes you do need ?wsdl if you want wsdl from browser. I was assuming you are trying to write some client to invoke onto it. In that case you don't want to use ?wsdl.
Default port for out-of-box demo is 8092 and the url specified should work. I just tested it on 4.3.1 and it works without any issue. for testing it just try starting Fuse ESB 4.3.1
1. run features:install examples-cxf-wsdl-first-osgi-package
2. In you browser go to http://localhost:8092/PersonService/?wsdl
3. Alternatively, there is client folder in the same directory where you can run mvn compile exec:java and it should build and run a client aginst it.
Regards,
Ulhas Bhole
-
5. Re: Fuse 4.1.3 - cxf-wsdl-first-osgi-package EXAMPLE DOES NOT WORK
theozaf Mar 3, 2011 9:21 AM (in response to ubhole)Thank you for infrotmation, I found those steps in README file as I already said in my first post. I can see the bundle active correctly, but I cannot bind at any port described 8092, 8181 etc. This is exactly my problem.
-
6. Re: Fuse 4.1.3 - cxf-wsdl-first-osgi-package EXAMPLE DOES NOT WORK
ubhole Mar 3, 2011 9:43 AM (in response to theozaf)Can you check servicemix log in data/log folder?
you should a line like this :
Setting the server's publish address to be http://localhost:8092/PersonService/
Regards,
Ulhas Bhole
-
7. Re: Fuse 4.1.3 - cxf-wsdl-first-osgi-package EXAMPLE DOES NOT WORK
theozaf Mar 3, 2011 9:49 AM (in response to ubhole)no, undortuantelly I cannot see such a line.
-
8. Re: Fuse 4.1.3 - cxf-wsdl-first-osgi-package EXAMPLE DOES NOT WORK
theozaf Mar 3, 2011 10:58 AM (in response to theozaf)I solved my problem and I got it working now, issue was that I had unziped the 4.3.1 version under a directory C:/folder where I already have a previous fuse version 4.1.0.2. Do you or anyone has a single idea why that causes conflicts between the versions?
Edited by: theozaf on Mar 3, 2011 3:58 PM
-
9. Re: Fuse 4.1.3 - cxf-wsdl-first-osgi-package EXAMPLE DOES NOT WORK
theozaf Mar 28, 2011 8:09 AM (in response to theozaf)Hello, does anyone has found out why we cannot use two different versions of fuse at the same server?
-
10. Re: Fuse 4.1.3 - cxf-wsdl-first-osgi-package EXAMPLE DOES NOT WORK
njiang Mar 28, 2011 9:19 PM (in response to theozaf)You can't start two different FUSE ESB instance without changing the configuration of the PAX-Web. With the default setting there could be a web container listen port conflict.
Willem