> Using the wsdl-first example as a model
Which example? The one from the Logisticx demo or from one of the other distribution example subdirs? What version of the code base?
I note that your version strings do not contain "fuse" at the end - and they should. For instance, the example poms all say something like:
Can you please compare the example pom to what you have created? I downloaded/configured and ran the logisticx demo today on my machine and it works without any errors.
Thanks for your reply. I am using the latest version of FUSE ESB, 4.1. I am referring to the cfx-wsdl-first example (fuse-esb-184.108.40.206/examples/cfx-wsdl-first), not the Logisticx demo.
I did, in fact, get the cfx-wsdl-first example working, but when I modified the Binding Component Service Unit to use my own WSDL, it failed to start (with the same error I originally saw for the cfx-wsdl-first example when I was using an old JDK). I see that several other users also reported No DestinationFactory errors for FUSE Services Framework when they upgraded from older to newer versions without changing their code. Answers to those posts suggested adding http-jetty to the classpath, so I added that as a dependency in my POM, but it did not help.
You suggest than any project I create needs to have -fuse in the version? Why is this? Are you just referring to the examples?
regarding the "-fuse" in the version strings... what I mean is, if you are using our code as a starting point, our code has "*-fuse" as a version string. And if you are making modifications to that example, then you must continue to use the version string as-is. This means the version string would have to end in "-fuse".
It is unclear to me if you have taken the sample code and made modifications to it, or if you only used the sample code as a model and created all your files from scratch.
Can you please attach your project? I will try to reproduce the problem here - that will make it much easier for me to then advise you how to work around the problem you are seeing.
The version numbers without -fuse version would try to pull Apache CXF artifacts that is what Lorinda was referring to.
you should be using 220.127.116.11-fuse version of FUSE Services Framework as your dependency.
both cxf-rt-transports-http-jetty and cxf-rt-transports-http shoudl have verison number 18.104.22.168-fuse.
Can you attach the failing project (zipped up) so that we can help you further quickly?
Thanks for your responses! I copied the cxf-wsdl-first example and used it as a model for my code.
I am working in FUSE ESB 4.1, not FUSE Services Framework. I actually got a similar piece of code working just fine in Services Framework. My project requires me to use FUSE ESB instead, since I'll also be developing a JMS topic data feed.
I haven't done much to the client, but the server side binding component and service engine have been updated. Everything compiles and installs in the maven repository. I am even able to install the OSGI bundle, but the bundle never starts because of the Destination Factory error on the binding component.
Thanks a lot for your help,
Edited by: chirino on May 28, 2009 7:16 PM
Removed the attachment per user request.
please see response in the support case / confirm you received the messages about this forum thread being exchanged for a support case.